Error Messages : Publisher Error Messages

Publisher Error Messages
SXF0000 – SXF0999
You specified a SHARE option that the FileAdapter does not support. Only levels 1 and 2 are supported.
<Delimiter> can not be used when useFieldWidth is true
You have specified both a delimiter character and useFieldWidth=true. Use only one of the parameters for each file type.
The parameter was specified with an invalid value. Correct the value. Ensure that the value is greater than zero.
messagesPerTransaction set to default value: <%d>
No value was specified in the configuration file for this parameter. Add this parameter if the default value is not the value you wish to be used.
Not a Certified Session. Cannot pre-register listener %s for subject %s
You specified pre-registration, but the session is not a certified session. Either specify a certified session, or omit the pre-registration entries.
The data set indicated was not found. Verify that the data set exists and is available to FilePublisher.
The library indicated was not found. Verify that the data set exists and is available to FilePublisher.
The specified directory was not found. Make sure that the specified directory exists and is available.
The format or value for a name/tag is not correct. A supplied value is incomplete; typically the value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure all values in the configuration file have matching quotes and braces, and that there are equal signs where required. Check the name/value tags in the section defined in the configuration file. Refer to the manual for the proper format.
Supplied VSAM start key is longer than 255 bytes
VSAM limits keys to 255 bytes. Go re-check the length of your key, because it exceeds VSAM's maximum length
VSAM limits keys to 255 bytes. Go re-check the length of your key, because it exceeds VSAM's maximum length
Supplied VSAM start key is longer than 510 nibbles
VSAM limits keys to 255 bytes (510 HEXADECIMAL nibbles). Go re-check the length of your key, because it exceeds VSAM's maximum length
Supplied VSAM end Hex key is longer than 510 nibbles
VSAM limits keys to 255 bytes (510 HEXADECIMAL nibbles). Go re-check the length of your key, because it exceeds VSAM's maximum length
A Max record count of zero is invalid. It says you want zero records from the file, which is meaningless.
Only the VSMA NRI and CR options are supported by the File Adapter.
The retransmissionDelay was previously specified. A duplicate entry was encountered, and will be ignored.
The %s contains the name of the FileAdapter parameter that has been set to an invalid value in the FileAdapter INI file.
Unable to malloc memory for ECMSubscriber entry
An out of memory error was reported by MVS. Raise the Job Limits (REGION size) to provide more memory for the FileAdapter to run.
Config error: ECMSubscriber defined without useExplicitConfirmation=true. ECMSubscriber ignored.
A mis-match in the configuration has been configured. Either also turn on the useExplicitConfirmation=true parameter, or eliminate the ECMSubscriber definition.
Unknown/Invalid configuration parameter <%s> at line %d. Ignored
The %s contains the name of the FileAdapter parameter that has been set to an invalid value in the FileAdapter INI file, and the Line number indicates which FileType or other definition contains the parameter in error.
Names used in File type PREFIX= definitions are limited to 8 bytes in length.
The dataSetType= parameter is not set to a legal value (e.g. SEQ, GDG, PDS, VSAM)
A VSAM RRN was to a negative value, which is invalid. A VSAM RRN must be zero of larger.
A VSAM ending RRN must be greater than zero, otherwise no records in the file will be processed.
VSAM only allows AltIndex names to be used if the file is defined as a KSDS dataset.
The %s contains the name of the FileAdapter parameter that is missing from the FileAdapter INI file.
Config ERROR: you have defined Record ECM and Block Mode ECM in the same Filetype. Config has been overriden to use Block Mode ECM.
You cannot use both Block mode and Record mode in the same FileType definition. Make the definition use one mode or the other.
File cannot be defined as BINARY yet have useFieldWidth=%s
Setting a file type to BINARY is mutually exclusive with useFieldWidth=No. Change one or the other parameter.
Input directory [%s] cannot be the same as the process directory.
The input directory and the process directory cannot be the same. Specify unique input and process directories.
Process directory [%s] cannot be the same as the output directory.
The output directory and the process directory cannot be the same. Specify unique output and process directories.
The specified input library name is invalid. Use a valid library name. Check for invalid characters. Name length is 10 characters maximum.
The specified library name is invalid. Use a valid library name. Check for invalid characters. Name length is 10 characters maximum.
The library name specified is invalid. Use a valid library name. Check for invalid characters. Name length is 10 characters maximum.
Pre-Register Sections appears before Options section near line %d
The Pre-Register section is specified in the configuration file in an invalid location. Specify the Pre-Register section after the Options section.
The section specified appears more than once in the configuration file. Correct the configuration file.
Config parse error near line %d, invalid section name: '%s'
A section name in the configuration file is incorrect. A section name must be one of Trace, Options, Pre-Register, or FileType. Check the spelling of the section names of the configuration file. Names are case sensitive.
In the configuration file, a section description, Trace, Options, PreRegister, or FileType, does not have a closing ']'. Check the configuration file and make sure that all section descriptions are formed correctly.
Config parse error near line %d, failed to find section
In the configuration file, a section description is not one of Trace, Option, Pre-Register, or FileType. Check the configuration file, and ensure that the section descriptions are valid. Descriptions are case sensitive.
Config parse error near line %d, failed to end expression
The configuration file does not have matching opening and closing '}'. Check the configuration file, and make sure that there are matching opening and closing '}'.
The configuration file is missing the specified section. You must specify the indicated section. Add the section to the configuration file.
The configuration file is missing the specified section. You must specify the indicated section. Add the section to the configuration file.
The configuration file is missing the specified section. You must specify the indicated section. Add the section to the configuration file.
The configuration file is missing the specified section option. You must specify the indicated option. Add the option to the configuration file.
The configuration file is missing the section option specified. You must specify the indicated option. Add the option to the configuration file.
The configuration file is missing the section option specified. You must specify the indicated option. Add the option to the configuration file.
The configuration file is missing the section option specified. You must specify the indicated option. Add the option to the configuration file.
The configuration file is missing the section option specified. You must specify the indicated option. Add the option to the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
*** CSI error: moduleid=0x%X%X reason=%d retcode=%d
The FileAdapter received an un-expected error from IBM's Catalog facility. Record this error information, and report it to TIBCO technical support.
FileType cannot be published. Specify Polling or Trigger.
A publishing method was not specified for this file type. Update the configuration file to provide a publishing method for this FileType.
The maximum number of field options has been exceeded. Correct the configuration file.
Failed to open TIBCO Rendezvous -- %s
Unable to start TIBCO Rendezvous TIBCO Rendezvous may not be active. Check with your TIBCO administrator that TIBCO Rendezvous is available.
Unable to create a network transport. TIBCO Rendezvous may not be active. Check with your TIBCO administrator that TIBCO Rendezvous is available.
Unable to start TIBCO Rendezvous. TIBCO Rendezvous may not be active. Check with your TIBCO administrator that TIBCO Rendezvous is available.
Unable to create a network transport session. TIBCO Rendezvous may not be active. Check with your TIBCO administrator that TIBCO Rendezvous is available.
Failed to initialize RVCM Transport session: %s
Unable to create a transport for certified delivery. TIBCO Rendezvous may not be active. Check with your TIBCO administrator that TIBCO Rendezvous is available.
Configuration File Error near line <%d> missing ',' or '\"'
There is an error in the configuration file. Verify that the configuration file is coded properly.
Found definitions for both Reliable and Certified mode
The configuration file contains definitions for both modes. The modes are exclusive. Use only one type of mode.
Found definitions for both Reliable and Certified mode
The configuration file contains definitions for both modes. The modes are exclusive. Use only one type of mode.
The configuration file is missing a required parameter. The error message indicates which parameter is missing. Check the configuration file, and correct the discrepancy.
The configuration file is missing a required parameter. The error message indicates which parameter is missing. Check the configuration file, and correct the discrepancy.
Memory allocation for MaxECMSubs failed for length=%d
A VSAM key cannot be longer than 255 bytes. Length=%d
VSAM limits keys to 255 bytes. Go re-check the length of your key, because it exceeds VSAM's maximum length.
GETMAIN failed when adding AltIndex name to Config List. Length=%d
An out of memory error was reported by MVS. Raise the Job Limits (REGION size) to provide more memory for the FileAdapter to run.
The File Adapter cannot find a valid entry for this file in the MVS catalog. It is either mis-spelled or has been deleted from the MVS catalog.
SFT and Record Mode ECM Transfers require that you specify an endPublishSubject
SFT and Record Mode ECM operation requires that a endPublishSubject= parameter be supplied in the FileType definition.
You used both a position and a fieldStart tag in a constraint parameter. Use only one of the tags to specify a field location.
You used both a position and a fieldStart tag in a constraint parameter. Use only one of the tags to specify a field location.
The configuration file is missing a required position parameter. The error message indicates which parameter is missing. Check the configuration file and correct the discrepancy.
The configuration file is missing a required length parameter. The error message indicates which parameter is missing. Check the configuration file and correct the discrepancy.
The configuration file is missing a required location parameter. The error message indicates which parameter is missing. Check the configuration file and correct the discrepancy.
Invalid data type <%s> between line <%d> and line <%d>
Config parse error between line %d and line %d, invalid precision: <%s>
The precision value is invalid. Ensure that the precision specified in the configuration file is entered correctly. The precision values must be numeric positive values, separated by a comma.
Config parse error between line %d and line %d, invalid precision: <%s>
The precision value is invalid. Ensure that the precision specified in the configuration file is entered correctly. The precision values must be numeric positive values, separated by a comma.
Config parse error between line %d and line, bad message token: '%s'
In the configuration file for FileSubscriber, a token is invalid in the FILE_LINE element of the FileType section. The invalid token is displayed. Correct or delete the invalid token.
Binary fields require a PRECISION definition tag
The configuration file does not have a "precision" tag for this field. Edit the configuration and supply a precision value for all Packed and Zoned fields.
The FileAdapter was expecting parameter or tag identified by %s in the configuration, and did not find it. Add that tag to the definition.
The FileAdapter was expecting parameter or tag identified by %s in the configuration, and did not find it. Add that tag to the definition.
The FileAdapter was expecting parameter or tag identified by %s in the configuration, and did not find it. Add that tag to the definition.
The FileAdapter was expecting parameter or tag identified by %s in the configuration, and did not find it. Add that tag to the definition.
Packed/Zoned/Binary/Float fields require a PRECISION definition tag
The configuration file does not have a "precision" tag for this field. Edit the configuration and supply a precision value for all Packed and Zoned fields.
Packed/Binary/Zoned/Float fields require Fixed field width processing
A FileType has a field type defined that requires a "binary" file specification. Specify isBinary="true" for this file type.
Packed/Binary/Zoned/Float fields can only be defined with BINARY files.
A FileType has a field type defined that requires a "binary" file specification. Specify isBinary="true" for this file type.
Msg Container Memory allocation failed, length=%d
Config parse error between line %d and line %d, failed to parse value for %s
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required.
Config parse error between line %d and line %d, missing container name
A message container does not have a name. Check the configuration file, and make sure that all message containers have a name=" " entry. Values are case sensitive.
Config parse error between line %d and line %d, bad message token: '%s'
In the configuration file for FileSubscriber, a token is invalid in the FILE_LINE element of the FileType. The invalid token is displayed. Correct or delete the invalid token.
Option Attributes: Memory re-allocation failed
RV Session Attributes: Memory allocation failed, length=%d
RV Session Attributes: Config parse error near line %d, failed to parse value
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required.
RVCM Session Attributes: Memory allocation failed, length=%d
RVCM Sess Attributes: Config parse error near line %d, failed to parse value
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required.
Config parse error near line %d, invalid option name: '%s'
One of the values in the Options section may be misspelled, or may not have the proper case. The invalid option is displayed. Check the spelling of the values in the Options section of the configuration file. Values must be in upper case
Config parse error near line %d, failed to parse Options line
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required.
FileType Attributes: Memory re-allocation failed
FileType Attributes: Memory allocation failed, length=%d
FileType Attributes: Config parse error between line %d and line %d, failed to parse value
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required.
MsgFields Attributes: Memory allocation failed, length=%d
FileType Attributes: Config parse error between line %d and line %d, failed to parse value
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required.
Config parse error between line %d and line %d, invalid option name: '%s'
One of the values in the Options section may be misspelled, or may not have the proper case. The invalid option is displayed. Check the spelling of the values in the Options section of the configuration file. Values must be in upper case.
Config parse error between line %d and line %d, failed to parse File Type line
In the configuration file, the Options section must have matching opening and closing '}'. Check the configuration file and make sure that the Options section has matching opening and closing '}'.
Config parse error near line %d, invalid Trace option name: '%s'
One of the values in the Options section may be misspelled, or may not have the proper case. The invalid option is displayed. Check the spelling of the values in the Options section of the configuration file. Values must be in upper case.
Config parse error near line %d, failed to parse Trace line
In the configuration file, the Options section must have matching opening and closing '}'. Check the configuration file and make sure that the Options section has matching opening and closing '}'.
Failed to pre-register listener %s for subject %s cause=%s
An invalid subject name was given, or there is a problem with TIBCO Rendezvous. Specify a valid subject name. If the problem continues, contact your TIBCO administrator.
The configuration file is missing a required parameter. The error message indicates which parameter is missing. Check the configuration file and correct the discrepancy.
The configuration file is missing a required parameter. The error message indicates which parameter is missing. Check the configuration file and correct the discrepancy.
You have specified too many pre-registered subscribers. Reduce the number of pre-registered listeners. The maximum is 126.
You have specified too many pre-registered subscribers. Reduce the number of pre-registered listeners. The maximum is 126.
Subscriber Attributes: Memory allocation failed, length=%d
Subscriber Attributes: Config parse error near line %d, failed to parse value
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required.
Config parse error near line %d, invalid Subscriber option name: '%s'
One of the values in the Options section may be misspelled, or may not have the proper case. The invalid option is displayed. Check the spelling of the values in the Options section of the configuration file. Values must be in upper case.
Config parse error near line %d, failed to parse options line
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required.
The specified section for this file type is missing. Add the definitions to the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
The data set indicated was not found. Verify that the data set exists and is available to FilePublisher.
The data set indicated was not found. Verify that the data set exists and is available to FilePublisher.
The specified section for this file type is missing. Add the definitions to the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
The library indicated was not found. Verify that the data set exists and is available to FilePublisher.
The library indicated was not found. Verify that the data set exists and is available to FilePublisher.
The specified section for this file type is missing. Add the definitions to the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
The specified directory was not found. Make sure that the directory specified exists and is available.
The specified directory was not found. Make sure that the directory specified exists and is available.
No Adapter name has been specified for this configuration. Correct the configuration file.
Unable to open the configuration file or the configuration file was not found. Make sure that the configuration file exists, and that the Adapter can find it.
Memory allocation for Max FileType failed, length=%d
MVS CSI problem. Incorrect file name or file not cataloged=<%.44s>
The File Adapter cannot find a valid entry for this file in the MVS catalog. It is either mis-spelled or has been deleted from the MVS catalog.
endPublishSubject is not used by Block Mode ECM. Parameter ignored.
endPublishSubject is not a valid parameter to use when defining Block Mode ECM file types.
Invalid value <%s> for DELETE_PUB_PRG_FILES. Parameter ignored.
The value specified for the DELETE_PUB_PRG_FILES. Is not correct. Go re-check the correct options in the manual.
File <%.44s> not found. Requested by user=% on Subject/Destination %s. File publish request Rejected.
The File Adapter cannot find a valid entry for this file in the MVS catalog. It is either mis-spelled or has been deleted from the MVS catalog.
Both Code Pages must be configured. Single code page config is ignored.
Normally, both HOSTCODEPAGE and NETWORKCODEPAGE should be specified when overriding the default code pages used by the File Adapter.
Code Page Setup failed: reason=<%s>. Will use defaults instead.
Unable set up the requested code pages. Verify that the code page settings are valid for your system and that TIBCO Rendezvous is active. Check with your TIBCO administrator.
Location value (%d) exceeds max allowed (%d), near line %d
The location= attribute tag exceeded the maximum field offset allowed in a record. Check the configuration file, and correct the discrepancy.
Total number of message item/container definitions (%d) exceeds max number of items allowed (%d), near line %d
The maximum number of message definitions for a given FileType has been exceeded. Correct the configuration file.
Missing Block Mode ECM Subscriber defs. FileType definition ignored
Block Mode ECM file type definitions require a EcmSubscriber definition. The Block mode definition is incorrect, because it lacks any EcmSubscriber definitions.
Missing Record Mode ECM confirmationSubject/endPublish Subject or TotalCount defs.
Record Mode ECM file type definitions require a confirmationSubject and a Total count. Supply those parameters.
Missing useExplicitConfirmation defs when using %s. FileType definition ignored
A config mismatch has been detected. When using the parameter identified by %s, a useExplicitConfirmation must also be used.
Config error near line %d ic=%d:\n contents=%s
A configuration error was detected in the INI file near the line specified. The %s contains the reason for the error.
Config error near line %d. Reading till next section is encountered
A configuration error was detected in the INI file near the line specified. The File Adapter will skip to the next section, because the current definition has too many severe config errors.
EMS Session Attributes: Memory allocation failed, length=%d
EMS Session Attributes: Config parse error near line %d, failed to parsevalue
A supplied value is incomplete, typically the supplied value is missing an opening or closing quote ("), brace ({ }), or an equal sign (=). Make sure that the values in the configuration file have matching quotes and braces, and that there are equal signs where required
Failed to create connection to the server. Reason :%s, exiting...
RV or EMS was unable to create the connection needed to communicate. The %s identifies the error it encountered.
Failed to create EMS session. Reason :%s, exiting...
Unable to create EMS session. The %s identifies the error it encountered.
EMS acknowledgement %s not allowed; changed to %s.
The specified EMS acknowledgement is not allowed. It has been changed to the value reported.
The EMS durable subscriber requires a destination type of TOPIC.
For EMS, a startNewMessage value of <false> is not allowed. It has been set to the only allowed value <true>.
SXF1000 – SXF1999
Failed to unsubscribe for trigger Subject/Destination <%s>: reason=%s
The Adapter was being shut down, and it encountered an error when trying to disconnect. The %s identifies the error it encountered.
Failed to unsubscribe for trigger Subject/Destination <%s>: reason=%s
The Adapter was being shut down, and it encountered an error when trying to disconnect. The %s identifies the error it encountered.
Invalid Publish Request for file <%s>: startKey > endKey. Request rejected.
A Trigger request was received that contained an invalid startKey/endKey combination. Fix the mis-match and re-submit the trigger request.
Failed to append %s to Job Queue file - storing in memory only
Unable to append an incoming Trigger request to the on-disk job queue file. Check the configuration file to ensure a valid job queue filename was set up, and check any associated MVS error messages to see if a B37 (out of space) or security access error occurred when trying to update the file.
Subject/Destination name %s does not match file type %d
A trigger was received for a file type that does not support the requested subject (or EMS) destination.
Unable to update a completed request in the on-disk Job Queue file. Check the configuration file to ensure a valid Job Queue filename was setup, and check any associated MVS error messages to see if a B37 (out of space) error occurred when trying to update the file.
Failed to process trigger for Subscriber %s, using fieldnames=%s and %s error message: %s
A trigger message was received that did not have the minimum required parameters (e.g. a field name of "DATA" or "fileName", or a user-defined "Trigger" file name). FileAdapter is unable to process the message. Fix the application that is sending the trigger message to include the required field.
No ALTINDEX name matches Trigger filename=<%s> on Subscriber=<%s>
FilePublisher received a trigger message, but was unable to process it because the specified parameter was invalid. Check that the input value for the parameter is correct, check that TIBCO Rendezvous is available, and re-submit the trigger message.
MAXRECORDS field %s on trigger message to %s is an invalid number. Rejected
FilePublisher received a trigger message, but was unable to process it because the specified parameter was invalid. Check that the input value for the parameter is correct, check that TIBCO Rendezvous is available, and re-submit the trigger message.
STARTKEY field <%s> on trigger message to %s is an invalid RBA/RRN. Rejected
FilePublisher received a trigger message, but was unable to process it because the specified parameter was invalid. Check that the input value for the parameter is correct, check that TIBCO Rendezvous is available, and re-submit the trigger message.
ENDKEY field <%s> on trigger message to %s is an invalid RBA/RRN. Rejected
FilePublisher received a trigger message, but was unable to process it because the specified parameter was invalid. Check that the input value for the parameter is correct, check that TIBCO Rendezvous is available, and re-submit the trigger message.
Security Check failed. UserId=<%s> is not allowed READ access to File=<%s> from Subject/Destination=<%s>. rc=%d subcode=0x%x VOLSER=<%s> %s. Trigger request rejected, File not published.
Security checking was requested, and the MVS security facility indicated the incoming Trigger request from the specified user, was not allowed access to publish that file. Contact your security people, to determine why the user is not authorized to publish that file.
Trigger request for file %s rejected because no UserId received on subject %s.
FilePublisher received a trigger message, but was unable to process it because Security checking is turned on, and no user id was included on the trigger message. FileAdapter is unable to process the message. Fix the application that is sending the trigger message to include the required field.
The RACF call failed for userId=<%s> File=<%s> from Subject/Destination=<%s>. Return code=<%d>. Volser=<%s>
Security checking was requested, and the MVS security facility indicated the incoming Trigger request from the specified user, was not allowed access to publish that file. Contact your security people, to determine why the user is not authorized to publish that file.
The RV Daemon being used by the FileAdapter disconnected, either due to a network crash or a crash of the daemon. The FileAdapter is unable to publish any more messages until the daemon (or its connection) is restored.
The RV Daemon being used by the FileAdapter disconnected, either due to a network crash or a crash of the daemon. The FileAdapter is unable to publish any more messages until the daemon (or its connection) is restored.
The File Adapter terminated due to the error specified by the %s reason code.
The File Adapter was unable to create a Heartbeat timer. The %d and %s indicate what the error was that caused the problem.
Error %d on Started Task cons check timer create: %s
The File Adapter was unable to create a Console timer. The %d and %s indicate what the error was that caused the problem.
Failed to create EMS/RV Heartbeat message: %s
Unable to create a heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to add the specified string to a heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to add the specified string to a heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to add the file prefix field to a heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to add the file extension to a heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to add the status string to the heartbeat timer message. Check with the TIBCO administrator.
Unable to add the numPublished string to the heartbeat timer message. Check with the TIBCO administrator.
Unable to add the progessLineNo string to the heartbeat timer message. Check with the TIBCO administrator.
Unable to add the progessLineNo string to the heartbeat timer message. Check with the TIBCO administrator.
Failed to set send Heartbeat target: cause=%s Subject/Destination=%s
An error was returned when the Adapter attempted to set the subject name in a heartbeat message to be published. Ensure that a valid subject name is specified in the configuration file.
Error in sending EMS/RV Heartbeat message: cause=%s Subject=%s
Unable to publish a heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to destroy a published heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
Config file not found in PARM= and no INIFILE DD. Will use default config filename <%s> instead.
No configuration file was specified in the startup JCL or STC procedure library. This is probably an error by the operator. Double-check that you really want to use the default configuration file.
Failed to get hostname from system. Error code returned by 'gethostname' is = %d
Unable to extract the host name being used by TCPIP. Probably indicates that TCP/IP is not up or not functioning.
Failed to get hostname from system. Error code returned by 'gethostname' is = %d
The MVS TCP Comm Server is unable to return the hostname of the current system. Contact the system programmer for the MVS Comm Server to try to determine what the problem is.
Error in sending EMS/RV Heartbeat message: cause=%s subject=%s
Unable to publish a heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
Failed to subscribe to Subject/Destination <%s>: %s
Unable to create a listener. TIBCO EMS/Rendezvous may be unavailable or may not be active. Check with your TIBCO administrator.
Failed to subscribe to Subject/Destination <%s>: %s
Unable to create a listener. TIBCO EMS/Rendezvous may be unavailable or may not be active. Check with your TIBCO administrator.
FilePoller Memory allocation failed for length=%d
Unable to create a file type object. At least one file type entry should be completely defined in the configuration file.
JobQueue element Memory allocation failed for length=%d
An out of memory error was reported by MVS. Raise the Job Limits (REGION size) to provide more memory for the FileAdapter to run.
JobQueue element Memory allocation failed for length=%d
An out of memory error was reported by MVS. Raise the Job Limits (REGION size) to provide more memory for the FileAdapter to run.
TriggerQue Memory allocation failed for length=%d
TriggerQue Memory allocation failed for length=%d
The File Adapter encountered an error while terminating. The %s details the reason for the problem.
Max_Dir FileList Memory allocation error for length=%d
Max_Dir FileList Memory allocation error for length=%d
The data set type is invalid for polling. The only data set that is supported for polling is PDS. Use a different method to publish the file.
Unable to create a timer. This is a system-level error. Check that TIBCO EMS/Rendezvous is available and functioning properly. Contact the TIBCO administrator.
FilePoller's Memory allocation of FileSender struct failed for length=%d
The Adapter attempted to create a callback function, but the timer callback function is NULL. This is a system-level message. Contact your TIBCO administrator.
Failed to subscribe to Subject/Destination <%s>: cause=%s
The File Adapter was unable to successfully subscribe to a given Subject. The %s details the reason for the problem.
Failed to subscribe to Subject/Destination <%s>: cause=%s
The File Adapter was unable to successfully subscribe to a given Subject. The %s details the reason for the problem.
setenv for EDC_ZERO_RECLEN Failed: %d %s. VB TEXT files exposed
A OMVS setenv() was issued to allow proper operation of VB files, and it failed due to the reason specified in %s. Review this issue with the MVS systems programmer. It probably indicates an OMVS configuration or authorization problem.
SXF2000 – SXF2999
A confirmation reply was received, but no such subscriber was found in the current configuration. It indicates some sort of configuration mis-match between the Publisher and the Subscriber.
A confirmation reply was received, but no such subscriber was found in the current configuration. It indicates some sort of configuration mis-match between the Publisher and the Subscriber.
A close on a file being published failed. Save the %s reason code and discuss the issue with the MVS Systems programmer.
ExecuteAfterProcess ignored because the file <%s> has been removed
An ExecuteAfterProcess was requested in the configuration, but the target file was removed/deleted, and not available for use.
<%s> Re-publishing EOF End Message to Subject/Destination=<%s> Block=%d idx=%d retry=%d #confBlks=%d isEOFblk=%d GUID=%s
The File Publisher did not receive a Block Mode or Record Mode ECM acknowledgement for the last block it sent. If this problem persists it may indicate a network problem. The Publisher will retry to send the block again.
A close on a file being published failed. Save the %s reason code and discuss the issue with the MVS Systems programmer.
<%s> Re-publishing to Subject/Destination=<%s> %s=%d idx=%d retry=%d #confBlks=%d GUID=%s Eofsm=%d empty=%d
The File Publisher did not receive a Block Mode or Record Mode ECM acknowledgement for the last block it sent. If this problem persists it may indicate a network problem. The Publisher will retry to send the block again.
Source file is retained while moving a file. Source file was in use by another process when the Adapter attempted to move the file. Remove the source file if it is not needed.
One of the input, process, or output libraries was not unique. Specify input, process and output libraries that are unique.
A file is being opened in Binary Mode with a linelength specified that may not match the file's actual length.
<%s> Move operation could not remove source file. cause=%d: %s
A remove operation on a file that was published failed. Save the %s reason code and discuss the issue with the MVS Systems programmer.
The indicates a configuration mis-match between the input or process files, and the output target files.
Failed to remove file: <%s> because there were errors during processing.
Unable to remove the file indicated. The file still exists on the system. Verify that FilePublisher has the proper authority to remove files.
<%s> Failed to remove 'AfterProcess' file=<%s>. Cause=%d %s
Unable to remove the file indicated. The file still exists on the system. Verify that FilePublisher has the proper authority to remove files.
<%s> Failed to remove file=<%s>. Cause=%d %s
Unable to remove the file indicated. The file still exists on the system. Verify that FilePublisher has the proper authority to remove files.
Failed to extract nested msg. field <%s> to form Subject/Destination name.
Unable to construct the subject from the field data. Check the configuration file for this message.
Failed to extract field <%s> to form Subject/Destination name.
Unable to construct the subject from the field data. Check the configuration file for this message.
<%s> File pointer is NULL in publishBlock invoked from timer callback!
The file pointer for a timer function is NULL. Report this to the TIBCO administrator. This portends a system error.
File pointer is NULL in pubRecord callback! No file opened.
The file pointer for a timer function is NULL. Report this to the TIBCO administrator.
Failed to remove file: <%s> because there were errors during processing.
Unable to remove the file indicated. The file still exists on the system. Verify that FilePublisher has the proper authority to remove files.
Unable to remove the file indicated. The file still exists on the system. Verify that FilePublisher has the proper authority to remove files.
The file still exists on the system. Verify that FilePublisher has the proper authority to remove files.
Configuration error. No fields were found in the file specified. Correct the configuration file.
Configuration error. The specified constraint could not be found in the input file. Correct the configuration file.
The move operation failed. Check that the target directory is available and that there are no authority problems.
The move operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Move failed: could not open source file using mode=%s. cause=%d: %s
The move operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Move failed: could not open target file using mode=%s. cause=%d: %s
The move operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Move failed: Unable to close source file cause=%d: %s
The file specified could not be moved. Be sure that FilePublisher has the proper authority.
<%s> Move failed: Write error on output file. cause=%d: %s
Unable to move a file. Ensure that FilePublisher has the authority to move the specified file.
<%s>Move failed: Data loss while flushing the output file
Unable to complete moving a file. Ensure that FilePublisher has the authority to move the specified file.
<%s> Move failed: Error renaming input file
The File Adapter was unable to successfully rename a CWK file to the target filename used by the FileType. The second %s details the reason for the problem.
The File Adapter was unable to successfully rename a CWK file to the target filename used by the FileType. A second related error message will detail why the move failed.
The File Adapter was unable to successfully rename a CWK file to the target filename used by the FileType. A second related error message will detail why the move failed.
<%s> Move failed: Error renaming input file cause=%d: %s
The File Adapter was unable to successfully rename a CWK file to the target filename used by the FileType. The second %s details the reason for the problem.
Failed to extract message <%s> for adding container: cause=%s
Possible mismatch between the received message and the configuration file.
Failed to Add message <%s> to container: cause=%s
Possible mismatch between the received message and the configuration file.
Failed to Update message <%s> to container: cause=%s
Unable to update one or more fields in a container message. Check the configuration file. The message may have exceeded the maximum buffer length, or TIBCO EMS/Rendezvous may be unavailable.
An attempt to add a field to an RV message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Probably a configuration mismatch. Check the configuration file and ensure that the configuration matches the received message.
Failed to Add Opaque/Binary to Data message: cause=%s
An attempt to add a field to an RV message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
The data in a PACKED field is not valid. Ensure that the file data being published is of the right format.
The data in a PACKED field is not valid. Ensure that the file data being published is of the right format.
Unable to add the specified field to a data message. Check with the TIBCO administrator.
Zoned field <%s> contains invalid character <%c>. Zeros sent
A ZONED field contains invalid data. Check the file data to ensure that it is of the proper type.
Unable to add the specified field to a data message. Check with the TIBCO administrator.
Unable to destroy a timer after publishing a message. Check with the TIBCO administrator.
A deallocate for a GDG file failed. Review the %s error message with your MVS Systems programmer.
Failed to unsubscribe to confirmation Subject/Destination: cause=%s
During shutdown, the FileSubscriber was unable to terminate the subscription to a Subject. The cause %s specifies what the problem was
The JCL specified for executeAfterProcess or executeBeforeProcess did not execute properly. Check the JCL specified, and ensure that it can execute properly.
The command identified did not complete successfully. Check the command specified for executeBeforeProcess or executeAfterProcess and ensure that the commands are valid.
JCL [%s] for File <%s> on Subject/Destination <%s> was not executed and the file was NOT removed because the file transfer failed.
The JCL specified for executeAfterProcess or executeBeforeProcess did not execute because (1) the file transfer failed, >and (2) the file's executeAfterProcess parameter was set to suppress running the JCL when file transfer failed.
JCL [%s] for File <%s> on Subject/Destination <%s> execution failed - %s.
The JCL specified for executeAfterProcess or executeBeforeProcess did not execute properly. Check the specified JCL, and ensure that it can execute properly.
The command identified did not complete successfully. Check the command specified for executeBeforeProcess or executeAfterProcess and make sure that the commands are valid.
Error from the svc99 De-Allocate/FREE GDG function <%s>
A deallocate for a GDG file failed. Review the %s error message with your MVS Systems programmer.
<%s> Remote Confirm msg indicates Subscriber I/O error. Terminating Block transfer to Sub=%s. Remaining Active Subs=%d.
A Block Mode ECM subscriber indicated that it received an out-space (B37/D37/E37) error, or some other kind of I/O error when writing to the work (CWK) file. The File Adapter will drop that subscriber and continue to publish to any other active subscriber.
<%s> Remote Confirm msg indicates Subscriber I/O error. Terminating Block transfer to Sub=%s.
A Block Mode ECM subscriber indicated that it received an out-space (B37/D37/E37) error, or some other kind of I/O error when writing to the work (CWK) file. There are not other active subscribers for that File, so the transfer is being terminated
An attempt to retrieve a field to an RV message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to retrieve Block Number from Confirm msg
An attempt to add a field to an RV message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> processing file <%s> set Subscriber %s offline. Its Max FlexECM retry limit was reached.
A Block Mode ECM subscriber exceed its maximum error count thresh-hold, and has been dropped from the list of active subscribers.
<%s> set Offline while sending file <%s>. All active ECM Subscribers failed, and Max FlexECM retry limit reached.
All the subscribers to a Block Mode ECM transfer have timed out. This normally indicates some sort of network problem.
A dynamic Open for a file failed. Verify that the file name is correct. If it is, review the %s error message with your MVS Systems programmer.
A dynamic Open for a file failed. Verify that the file name is correct. If it is, review the %s error message with your MVS Systems programmer.
<%s> Failed to close .PRG file=%s, aborting recovery
Unable to close the progress file. Check the process directory. The file may be corrupted.
<%s> Failed to remove .PRG file=%s, aborting recovery
Unable to remove the progress file. Check the process directory. The file may be corrupted or not properly cataloged.
<%s> Failed to read data in progress file=%s. Wrong number of fields (%d), aborting recovery
Unable to read the progress file. Check the process directory. The file may be corrupted.
<%s> Failed to close .PRG file=%s, aborting recovery
Unable to close the progress file. Check the process directory. The file may be corrupted.
<%s> Failed to remove .PRG file=%s, aborting recovery
Unable to remove the progress file. Check the process directory. The file may be corrupted or not properly cataloged.
<%s> Failed to read data in progress file=%s. Read of file failed, aborting recovery
Unable to read the progress file. Check the process directory. The file may be corrupted.
<%s> Failed to close .PRG file=%s, aborting recovery
Unable to close the progress file. Check the process directory. The file may be corrupted.
<%s> Failed to remove .PRG file=%s, aborting recovery
Unable to remove the progress file. Check the process directory. The file may be corrupted or not properly cataloged.
<%s> Failed to extract nested RV message for NT_ECM TEXT for ECM publish block. Reason: %s
FilePublisher was unable to extract the nested TEXT data field from a ECM block data message. Check with the TIBCO administrator.
<%s> Failed to create RV message of length=%d for ECM publish block. Reason: %s
Unable to create a TIBCO Rendezvous message. Contact the TIBCO administrator to ensure that TIBCO Rendezvous is functioning.
<%s> Failed to create RV message of length=%d: Reason: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO Rendezvous is functioning.
Unable to create a message. Contact the TIBCO administrator to be certain that TIBCO Rendezvous is functioning.
<%s> Failed to create nested RV message of length=%d: Reason: %s
Unable to create a nested message. Contact the TIBCO administrator to ensure that TIBCO Rendezvous is functioning.
<%s> Failed to update nested RV message of length=%d: Reason %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO Rendezvous is functioning.
<%s> Failed to add %s to EMS/RV message: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to add %s to EMS/RV message: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to add %s to EMS/RV message: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to add %s to EMS/RV message: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to add %s to EMS/RV message: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to add %s to EMS/RV message: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to add %s to EMS/RV message: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to create EndMsg RV message of length=%d: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO Rendezvous is up and running.
<%s> Failed to add %s to EMS/RV End message: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to add Filename to EMS/RV End message: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to add NumberOfMessage to EMS/RV End message: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to add %s to EMS/RV End message: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Failed to create Error EMS/RV message of length=%d: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Failed to set Error send subject/Destination: %s cause=%s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Failed to send error message: cause=<%s> Subject/Destination=%s
File Publisher was unable to send a message to the network. The %s cause details why. It may indicate a network or RV daemon problem.
File Publisher was unable to send a message to the network. The %s cause details why.
File name in configuration file was NULL (""). Check the configuration file, and supply a file name where it's missing.
Could not open output GDG file=<%s>. GDG error=%s
A open for a GDG file failed. It may be due to an invalid GD name. If the problem persists, review the %s error message with your MVS Systems programmer.
A open for a GDG file failed. It may be due to an invalid GD name. If the problem persists, review the %s error message with your MVS Systems programmer.
<%s> File open failed for file <%s> using mode '%s'. errno=%d R15=%d Fdbk=%d op=%d ab_sys=0x%X ab_rc=0x%X\n errno text=%s
Unable to open the file identified in the message. Correct the configuration file entry for this file, and be certain that the file is available for use.
Cannot open file <%s> because RLS function is inactive. SMSVSAM not up
Unable to open the file identified in the message. Correct the configuration file entry for this file, and ensure that the file is available for use.
Cannot open file <%s> because trying to output to a Recoverable Sphere
Unable to open the file identified in the message. Correct the configuration file entry for this file, and ensure that the file is available for use.
Cannot open file <%s> because RLS requires SMS files.File is not SMS managed
Unable to open the file identified in the message. Correct the configuration file entry for this file, and ensure that the file is available for use.
Cannot open file <%s> because RLS detected DISP=SHR vs DISP=OLD conflict.
Unable to open the file identified in the message. Correct the configuration file entry for this file, and ensure that the file is available for use.
<%s> Can not open file <%s> because OPEN flag still set on from previous run or another App is trying to share the file.
Unable to open the file identified in the message. Correct the configuration file entry for this file, and ensure that the file is available for use.
A deallocate for a GDG file failed. Review the %s error message with your MVS Systems programmer.
<%s> VSAM key flocate failed for file <%s>. Terminating request. errno=%d R15=%d Fdbk=%d op=%d ab_sys=0x%X ab_rc=0x%X\n errno text=%s
Unable to locate the requested VSAM record by key, in the file identified in the message. Correct the trigger parameters sent for this file, and be certain that the file is available for use.
Unable to open the file identified in the message. Correct the configuration file entry for this file, and ensure that the file is available for use.
<%s> Transfer aborted for file: <%s>. LRECL length %d > Transfer Blackest %d
Unable to process the file identified in the message because the LRECL of the file was longer than the ECM block size specified for the transfer. Correct the configuration file entry for this file to make blockTransferSize equal to or larger than the file's LRECL.
Failed to open .PRG file '%s' errno=%d errtext=%s
Unable to open the progress .PRG file identified in the message. Check to see that the .PRG file is available for use.
<%s> TransactionDelay Timer creation failed: %s
Unable to create a timer. This is a system level error. Check that TIBCO EMS/Rendezvous is available and functioning properly. Contact the TIBCO administrator.
<%s> ConfBlock - Failed to create message of length=%d: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is up and running.
Failed to set EMS/RV send destination/ subject: %s
An error was returned when the Adapter attempted to publish a message. Ensure that a valid destination/subject name is specified in the configuration file.
Failed to set EMS/RV reply destination/ subject: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Error in sending RVCM message: cause=%s Subject/Destination=%s
An error occurred when sending an RVCM message. The Adapter may not be active. Contact your TIBCO administrator and report this error.
<%s> Error in sending RV message: cause=%s Subject=%s. OR <%s> Error in sending EMS message: cause=%s Destination=%s
An error occurred when sending an EMS/RV message. The Adapter may not be active. Contact your TIBCO administrator and report this error.
<%s> Failed to create EMS/RV message of length=%d: %s
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to initialize EMS/RV message of length=%d: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to destroy rvMsg: %s OR <%s> Failed to destroy emsMsg: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Unable to terminate an RV timer. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
Unable to create a message. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
Unable to create a message. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
<%s> Cannot append to message, failed to find start
Unable to append a field onto an existing message. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
Unable to append a field to an existing message. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
Unable to create a message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Cannot append RBA/RRN I32 to message: %s
Unable to append a field to an existing message. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
Unable to free memory. Contact the TIBCO administrator to ensure that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to create Start message of length=%d: %s
Unable to create a message. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to append FileName parm to Start message: %
Unable to add the filename field to the Start File Publish message. Check the configuration file to ensure that a valid file name was specified. Make sure that TIBCO EMS/Rendezvous is available.
<%s> Failed to create Tracking message of length=%d: %s
An attempt to create a RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to create Trig Reply message of length=%d: %s
An attempt to create a RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to append fields to Trig Reply message: %s
Unable to add one or more fields to a Trigger Reply message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to create a RV Listener. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to add String Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add String Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add Bool Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add Time Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add I16 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add U16 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add I32 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add U32 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add F32 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
<%s> Failed to add F64 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and ensure that the configuration matches the message to be sent.
An invalid message description was encountered. Check that the configuration file matches the message received, and that TIBCO EMS/Rendezvous is available.
An invalid message description was encountered. Check that the configuration file matches the message received, and that TIBCO EMS/Rendezvous is available.
<%s> Failed to add String Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add String Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add String Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add Bool Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add Time Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add I16 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add U16 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add I32 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add U32 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add F32 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
<%s> Failed to add F64 Data Field to message at col %d: %s
This is either a configuration mismatch or an out of memory problem. Check the configuration file, and be certain that the configuration matches the message to be sent.
An invalid message description was encountered. Check that the configuration file matches the message received, and that TIBCO EMS/Rendezvous is available.
Could not create a message. Check that TIBCO EMS/Rendezvous is available.
Probably a configuration mismatch. Check the configuration file, and be certain that the configuration matches the received message.
Unable to update one or more fields in a message to be published. Check the configuration file, the message may have exceeded the maximum buffer length, or TIBCO EMS/Rendezvous may be unavailable.
Unable to free memory. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
<%s> Move failed: Unable to close target file. cause=%d: %s
The file specified could not be moved. Be sure that FilePublisher has the proper authority.
<%s> Move failed: Unable to close source file. cause=%d: %s
The file specified could not be moved. Be sure that FilePublisher has the proper authority.
Move failed: copying source <%s> to target <%s>
Could not move the file specified to the directory indicated. Ensure that the file and directory exists, and that FilePublisher has the proper authority.
<%s> Block Buffer: Memory allocation failed for length=%d
<%s> ConfEndMsgAck Memory allocation failed for %d entries
<%s> Confirm Listen EventId Memory allocation failed for %d entries
<%s> ConfBlocks Memory allocation failed for length=%d
<%s> ConfBlock.MsgAck Memory allocation failed for length=%d
Failed to send error message: cause=<%s> Subject/Destination=%s
Unable to send a message. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
<%s> Block Buffer: Memory allocation failed for length=%d
Error in sending RVCM message: cause=%s Subject/Destination=%s
Unable to send a message. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
<%s> Error in sending message: cause=%s Subject/Destination=%s
Unable to send a message. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
Attempted to create a callback function, but the timer callback function is NULL. This is a system level error message, contact your TIBCO administrator.
Failed to subscribe to Subject/Destination <%s> cause=%s
Unable to create a Subscriber for that destination. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
<%s> Failed to subscribe to Subject/Destination <%s> cause=%s
Unable to create a Subscriber for that destination. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
<%s> no confirmation Subject/Destination specified for Record Mode ECM
Unable to create a Subscriber for that destination. Contact the TIBCO administrator to be certain that TIBCO EMS/Rendezvous is functioning.
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to add fileTransferDuration to Status message: %s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
There is an error in loading the configuration for this file type. Cannot publish file <%s>.
An error was discovered for the FileType associated with this subject, during configuration processing, and the file type was marked invalid and offline. Fix the error in the configuration file, and re-submit the publish request.
<%s> Re-publishing Queued Messages to Subject/Destination=<%s>: CurrBlk=%d CurrRec=%d RecovBlk=%d retry=%d #confBlks=%d Eofsm=%d ifactive=%d NtEcm=%d
The File Publisher did not receive a Block Mode or Record Mode ECM acknowledgement for the last block it sent. If this problem persists it may indicate a network problem. The Publisher will retry to send the block again.
Zoned field <%s> contains invalid character <%c>. Zeros sent
The data in the file to be published is invalid. Verify that the message definition is correct, and that the file is correctly formatted.
Error from the Svc99 function <%s>. File=<%s> Volser=<%s ...> Unit=%s Type_alloc=%s Mode=%s
An error occurred when dynamically opening a file. The first %s denotes what the error was. Save this message and consult with your MVS programmer.
Svc99 error: Duplicate Dataset Name=%s already exists on the system.
This normally indicates that two different file types are trying to use the same file. This is not allowed.
A PROGRESS file is being created on a VOLUME that has run out of space.
Svc99 error: RACF/ACF2 Security problem.
A PROGRESS file is being created and RACF has flagged an error (e.g. the Volume is password protected).
Svc99 error: Cannot put a non-SMS dataset on an SMS volume.
A VOLSER has been specified for a Progress file that exists on a SMS managed volume
Svc99 error: Catalog error - program not authorized to perform operation
A PROGRESS file is being created and RACF has flagged an error (e.g. the Volume is password protected).
Svc99 error: RACF/ACF2 Security problem (Not Auth) or SMS error
A PROGRESS file is being created and RACF has flagged an error (e.g. the Volume is password protected).
Svc99 error: File=<%s> already allocated and the tasks' usage attributes of 'a' and 'w' conflict
This normally indicates that two different file types are trying to use the same file. This is not allowed.
Output File <%s> could not be opened using DD=<%s> mode=<%s> Type_alloc=%s errno=%d %s
The specified file could not be opened. The errno %s specifies the specific cause of the problem.
Append Output File <%s> might not be currently cataloged on VOLSER=<%s ...
The VOLSER parameter specified in the INI file may be incorrect for that file. Contact your MVS systems programmer.
<%s> Msg Acked. Re-Publishing successful on Subject/Destination=%s after %d retries
Indicates that blocks that were previously being re-published have now been acknowledged. Whatever network condition was causing the problem has been corrected.
Svc99 error: Invalid file name %s was rejected by Allocate
The FILENAME parameter specified in the INI file were incorrect. Contact your MVS systems programmer.
Svc99 error: Invalid VolSer list was rejected by Allocate
The VOLSER parameter specified in the INI file were incorrect. Contact your MVS systems programmer.
Svc99 error: Invalid UNIT name %s was rejected by Allocate
The UNIT parameter specified in the INI file were incorrect. Contact your MVS systems programmer.
Svc99 error: Invalid length was rejected by Allocate. Probably due to incorrect length on File name, Volser, or Unit
The FILENAME, UNIT, or VOLSER parameters specified in the INI file were incorrect. Contact your MVS systems programmer.
Svc99 error: UNIT %s and Volser %s are incompatible or missing and were rejected by Allocate
The UNIT and VOLSER parameters specified in the INI file were incompatible for the file being processed. Contact your MVS systems programmer.
<%s> Failed to create nested EPM Payload message of length=%d: %s
An attempt to create an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to read data from input process file. Next Block # %d
An attempt to retrieve a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Error adding field to EPM message: cause=%s Subject/Destination=%s
An attempt to add a field to an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Invalid null pointer for pFileSender. Terminating Publisher
An unexpected condition has been detected. The Publisher will be terminated.
Invalid null pointer for pFileOptions. Terminating Publisher
An unexpected condition has been detected. The Publisher will be terminated.
Invalid null pointer for %s. pFileSender=%08X timer_kick=%d
Only one durable subscriber can be defined per FileOption section
Subscribe <%s> and Generate <%s> Destination names need to be equal for Guaranteed Delivery.
If guaranteed delivery of EMS messages is used and if generateFileDestinationName is specified, then subscribeDestinationName must equal generateFileDestinationName
SXF3000 – SXF3999
<%s> Unable to get reply Subject/Destination for Subscriber=%s
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
<%s> Unable to locate Subscriber=%s. Not registered.
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
<%s> No subscriber name found in msgType=%s msg. Unable to reply
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
<%s> Ignoring Activate from Subscriber=%s until current file completed.
A recovery race occurred. When the current file is complete, the recovery sequence will be completed.
<%s> Received unknown ECM Admin Subscriber request %d
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
<%s> No reply subject/Destination for Subscriber=%s on msgtype=%d.
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
<%s> Unable to locate Subscriber=%s. Not registered.
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
<%s> No subscriber name found on msgType=%d. Not registered.
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
<%s> Received unknown ECM Admin Subscriber reply %d.
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
An attempt to create an RV or EMS timer failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> set Subscriber %s offline. It's Max FlexECM retry limit was reached during Activation.
A Block Mode ECM subscriber exceed its maximum error count thresh-hold, and has been dropped from the list of active subscribers.
<%s> set Offline. Not all ECM Subscribers Active, Max FlexECM retry limit reached, and .PRG file <%s> failed.
A Block Mode ECM subscriber exceed its maximum error count thresh-hold, and has been dropped from the list of active subscribers.
<%s> set Offline. No ECM Subscribers Active, and Max FlexECM retry limit reached.
All the subscribers to a Block Mode ECM transfer have timed out. This normally indicates some sort of network problem.
<%s> %d subscribers set Offline, because Max FlexECM retry limit reached.
A group of subscribers to a Block Mode ECM transfer have timed out. This normally indicates some sort of network problem.
An attempt to create an RV or EMS message failed. The %s identifies the specific cause. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> Failed to append MsgType to Admin message: %s
Unable to add the MsgType field to an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s> Failed to append MsgId/Guid to Admin message: %s
Unable to add the MsgId/Guid field to an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
Unable to add the Version field to an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
Unable to add the bool flag field to an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s> Failed to append NumRetries to Admin message: %s
Unable to add the NumRetries field to an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
An error was returned when the Adapter attempted to set the ECM Admin Subject name in a message to be published. Ensure that a valid subject name is specified in the configuration file.
An error was returned when the Adapter attempted to set the ECM Admin Reply Subject name in a message to be published. Ensure that a valid subject name is specified in the configuration file.
<%s> Failed to send RV Admin msg: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s> Failed to subscribe to Admin Request subject <%s> cause=%s
An error was returned when the Adapter attempted to subscribe to an ECM Admin Subject name. Ensure that a valid subject name is specified in the configuration file. Check that TIBCO EMS/Rendezvous is available.
<%s> Failed to subscribe to Admin Reply subject <%s> cause=%s
An error was returned when the Adapter attempted to subscribe to an ECM Admin Subject Reply name. Ensure that a valid subject name is specified in the configuration file. Check that TIBCO EMS/Rendezvous is available.
A error was detected in the ECM Admin Timer callback support. Check that TIBCO EMS/Rendezvous is available. If so, and the problem persists, contact TIBCO technical support.
FilePublisher was unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
File <%s> can't be deleted. UserId=<%s> does not have ALTER access privileges on the file.
A "removeFile=true" was specified in a FileType definition, but when a Trigger request came in for that File, the requesting user is not authorized to delete the field.
<%s> will not be deleted when Publishing complete. UserId=<%s> does not have ALTER access privileges on the file
A "removeFile=true" was specified in a FileType definition, but when a Trigger request came in for that File, the requesting user is not authorized to delete the field.
SXF4000 – SXF4999
A TIBCO API failed. Note the return code and contact your TIBCO administrator.
A Trigger request was received, and the file it was requesting to publish was not present in the Process Input directory.
A copy of the requested file to be published already exists in the Process file. This means that the file is already being published or recovered, and the duplicate publish request is being rejected.
A TIBCO API failed. Note the return code and contact your TIBCO administrator.
Could not find the library specified. Supply a name of a library that exists on the system.
The input file specified does not exist. Correct the file name, or the library name.
The specified file already exists in the process directory. Move the specified file out of the process directory to prevent the Adapter from overwriting the file.
File Adapter is reporting an error it encountered. The %s details the cause of the error.
File Adapter is reporting an error it encountered. The %s details the cause of the error.
A library needed by the FileAdapter is missing. Re-check the STEPLIB definitions used in the File Adapter JCL.
Failed to open Pub log file <%s>: cause %d %s. File logging turned off...
The File Adapter was unable to open the trace log file. The second %s details the cause of the problem.
Error renaming Pub log file <%s> to <%s>: cause %d %s. File logging turned off...
The File Adapter was unable to open the trace log file. The second %s details the cause of the problem.
Failed to open Pub log file <%s>: cause %d %s. File logging turned off...
The File Adapter was unable to open the trace log file. The second %s details the cause of the problem.