Error Messages : Subscriber Error Messages

Subscriber Error Messages
SXF5000 – SXF5999
WARNING: VSAM RLS Share Options 3 and 4 are not supported
You specified a SHARE option that the FileAdapter does not support. Only levels 1 and 2 are supported.
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.
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.
A VSAM key cannot be longer than 255 bytes. Length=%d
For VSAM files, a key cannot be more than 255 characters. Change the configuration value supplied to the proper length.
The file mode specified for a VSAM is incorrect. It must be either INSERT, UPSERT, or REPLACE. Change the configuration value supplied to a valid value.
The share mode specified for a VSAM is incorrect. Change the configuration value supplied to a valid value.
Unknown/Invalid configuration parameter <%s> at line %d. Ignored
In the FileSubscriber configuration file, a token is invalid in the FileType section. The invalid token is displayed. It could either be a misspelled option name, or an obsolete keyword. Change the configuration file for the associated FileType, to either correct the spelling of the option, or to remove an obsolete or unsupported option.
The file type value supplied must not be more than 8 characters. Change the value supplied to the proper length.
The file type specified a VSAM file name that could not be located in the MVS catalog. Verify that the file is actually a VSAM file, and ensure that the spelling of the file name is correct in the configuration file.
VSAM log name has been defined, but no vsamUseLog= has been specified
The file type indicated a VSAM log name, but did not have a corresponding vsamUseLog option to denote how the log should be used. Add a vsamUseLog parameter, or else remove the VSAM log name parameter from the configuration file.
Logging for VSAM file is enabled, but no VSAM log name has been defined
The file type has a vsamUseLog parameter specified, but no corresponding VSAM log name. Add a VSAM log name, or remove the vsamUseLog parameter from the configuration file.
Block Mode Transfer requires that you specify an genFileSubjectName.
You specified blockTransferMode without specifying a genFileSubjectName. For standard block mode or record-mode ECM, specify a genFileSubjectName.
A file type other than PDS, GDG, SEQ, or VSAM was entered in the configuration file. Correct the file type entry, use only PDS, GDG, SEQ, or VSAM. Value must be in upper case.
For VSAM files, a key must be specified. Change the configuration file to supply the proper length.
VSAM REUS files are not supported by Tibco Subscriber
FileSubscriber does not process VSAM files that have the REUS attribute. Redefine the file to NOREUS mode.
Process directory [%s] cannot be the same as the output directory.
The process directory name is the same as the output directory. Use a unique name for the process and the output directory.
The output library name is not a valid MVS dataset name. Correct the name.
The output library name specified is invalid. Use a valid library name. Check for invalid characters. Maximum length is 10 characters.
The process library name specified is invalid. Use a valid library name. Check for invalid characters. Maximum length is 10 characters.
non-Block Mode ECM FileSubscriber must have a file output method
A "standard" block-mode transfer that does not use ECM must specify a AutoGenerate file count or subject name. Supply a valid AutoGenerate parameter in the FileType section of the configuration file.
The configuration file is missing a required constraint parameter. The error message indicates which parameter is missing. Check the configuration file.
The configuration file uses both a position and a fieldStart tag. Use only one of the tags to specify a field location.
The configuration file uses both a position and a fieldStart tag. Use only one of the tags to specify a field location.
Config parse error near line %d, invalid precision: <%s>
The value for the precision tag is not correct. Check the precision tag in the configuration file. Refer to the manual for the proper format.
Config parse error near line %d, invalid precision: <%s>
The value for the precision tag is not correct. Check the precision tag in the configuration file. Refer to the manual for the proper format.
A invalid field type was specified. Specify a valid field type for conversion to numeric.
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.
Field <%s> in <%s %s> must have a position definition...
A position tag was not supplied. Check the configuration file for the field identified, and add a position tag.
Field <%s> in <%s %s> must have a precision definition for %s conversion...
A precision tag was not supplied. Check the configuration file for the field identified, and add a precision tag.
Field <%s> in <%s %s> has invalid convertTo value: <%s>...
An invalid conversion value was specified. Only "true" or "false" may be specified for the convertTo tag.
Field <%s> in <%s %s> has invalid input type: <%s>...
A invalid field type was specified. Specify a valid field type for conversion to numeric.
Field <%s> in <%s %s> is defined as %s, but FileType must be binary...
The FileType must be binary. Add an isBinary="true" parameter to the file type.
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.
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.
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, 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'
A value 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
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, 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, 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'
A value 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 file type line
In the configuration file, the FileType does not have the proper framing, or is missing required parameters. Check the FileType section of the configuration file and make sure that the section is complete, and that there are matching opening and closing braces ({ }).
Config parse error near line %d, invalid option name: '%s'
A value 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.
You have specified too many File Types in the configuration file. Reduce the number of File Type definitions
Config parse error near line %d, invalid section name: '%s'
A section name in the configuration file is incorrect. The section name must be one of Trace, Options, 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, 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'
A section name in the configuration file is missing. The section name must be one of Trace, Options, or FileType. Check the spelling of the section names in the configuration file. Names are case sensitive.
Config parse error near line %d, failed to terminate expression
A section was not properly configured in the configuration file. Check the configuration file and correct the error.
A section name in the configuration file is missing. The section name must be one of Trace, Options, or FileType. Check the spelling of the section names in the configuration file. Names are case sensitive.
A section name in the configuration file is missing. The section name must be one of Trace, Options, or FileType. Check the spelling of the section names in the configuration file. Names are case sensitive.
A section name in the configuration file is missing. The section name must be one of Trace, Options, or FileType. Check the spelling of the section names in the configuration file. Names are case sensitive.
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 configuration file is missing the section option specified. You must specify the indicated option. Add the option to the configuration file.
An input directory has not been specified for this file type. Correct the configuration file.
The specified section for this file type is missing. Add the definitions to the configuration file.
The GDG model for the specified file was not found. Make sure that the GDG file was properly specified.
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 specified directory exists and is available.
The specified directory was not found. Make sure that the specified directory exists and is available.
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 specified directory exists and is available.
The specified directory was not found. Make sure that the specified directory exists and is available.
Unable to open the configuration file or the configuration file was not found. Make sure that the configuration file exists, and that it can be found by the Adapter.
MVS CSI problem. Incorrect file name or 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.
Unable to start TIBCO Rendezvous TIBCO Rendezvous may not be active. Check with your TIBCO administrator that TIBCO Rendezvous is available.
Failed to create EMS/RV Transport session: service=%s network=%s daemon=%s. EMS/RV Error=%s
Unable to start TIBCO Rendezvous TIBCO Rendezvous may not be active. Check with your TIBCO administrator that TIBCO Rendezvous is available.
Failed to open TIBCO Rendezvous CM -- %s
Unable to start TIBCO Rendezvous, it may be inactive. Check with your TIBCO administrator.
Unable to create a network transport. TIBCO Rendezvous may be inactive. Check with your TIBCO administrator.
Unable to create a network transport. TIBCO Rendezvous may be inactive. Check with your TIBCO administrator.
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 mutually exclusive. Specify only one mode in the configuration file.
Found definitions for both Reliable and Certified mode
The configuration file contains definitions for both modes. The modes are mutually exclusive. Specify only one mode in the configuration file.
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.
Cannot specify both vsamReplaceRecords and vsamUpsertRecords =true
The FileType definition has both parameters specified. This is not allowed. Choose one or the other.
A FileType is using a VSAM file. VSAM files require a KeyOffset definition in the FileType.
Memory allocation error of LineField struct. Length=%d
lineBuff Option Memory allocation failed. Length=%d
An attempt to allocate memory failed. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
lineBuff Option Memory allocation failed. Length=%d
lineBuff Option Memory allocation failed. Length=%d
lineBuff Option Memory allocation failed. Length=%d
The GDG base for the specified file was not found. Make sure that the GDG file was properly specified.
No Adapter name has been specified. Add the definition(s) to the configuration file.
An attempt to allocate memory failed. 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 the configuration file. Verify that the configuration file is coded properly.
A request to access the MVS Catalog service failed. Save the error message and contact your MVS Systems programmer.
Caution: Binary files must always be Fixed Block. usedFixedRecordFile=false parameter is ignored.
The Adapter requires that binary files must use fixed block (FB) format. Correct the configuration file.
There is a config error. reading till next section is encountered :[%d]
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.
There is an error while parsing the name value pairs. exit parsing
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.
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.
blkSizeAlloc <%d>, is not a multiple of lineLength [%d] for fixed block
The value specified for blkSizeAlloc= is not a multiple of the record length (lineLength). Recheck the RECL and BLKZSIZE attributes of the file on your system, and set blkSizeAlloc to a valid multiple of the RECL.
blkSizeAlloc <%d>, is not a multiple of lineLength [%d] for variable block
The value specified for blkSizeAlloc= is not a correct multiple of the record length (lineLength). It must be (RECL * n) + 4. Re-check the RECL and BLKZSIZE attributes of the file on your system, and set blkSizeAlloc to a valid multiple+4 of the RECL.
Target file <%.48s> not found. Requested by user=%s on Subject/Destination=%s.
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.
Config ERROR: you have defined both record-mode ECM and Block-Mode ECM parms in the same Filetype. Configuration has been overriden to use Block Mode ECM.
You specified parameters for both Block Mode ECM and record-mode ECM versions of ECM block mode. Determine which version of the ECM protocol you, then remove the parameters that apply to the other version of the protocol.
Config ERROR: you have defined both forcePublishedFileName and generateFileOnNumberOfMessag es=%d parms. This combination is not allowed.
The file type has been defined with both forcePublishedFileName and generateFileOnNumberOfMessages parameters. Remove one of the parameters from the configuration file.
Config ERROR: you must define retryInterval > 0 if Locked File retry is enabled with noOfRetries > 0
There is an error in the configuration file. Verify that the configuration file is coded properly.
Only one durable subscriber can be defined per FileOption section
SXF6000 – SXF6999
The File Adapter encountered an error while terminating. If the problem persists, contact TIBCO technical support.
Could not remove SIGTERM signal handler: %s
The File Adapter encountered an error while terminating. If the problem persists, contact TIBCO technical support.
The File Adapter encountered an error while terminating. If the problem persists, contact TIBCO technical support.
The File Adapter encountered an error while terminating. If the problem persists, contact TIBCO technical support.
Error in sending Heartbeat message: cause=%s Subject/Destination=%s
An error occurred when sending a TIBCO heartbeat message. The Adapter may not be active. Contact your TIBCO administrator.
Error in sending Heartbeat message: cause=%s Subject/Destination=%s
An error occurred when sending a TIBCO heartbeat message. The Adapter may not be active. Contact your TIBCO administrator.
Failed to unsubscribe for exit Subject/Destination <%s>: cause=%s
The File Adapter encountered an error while terminating. If the problem persists, contact TIBCO technical support.
Failed to unsubscribe for refresh options Subject/Destination <%s>: %s
The File Adapter encountered an error while terminating. If the problem persists, contact TIBCO technical support.
The File Adapter encountered an error while terminating. If the problem persists, contact TIBCO technical support.
Failed to send error message: cause=<%s> Subject/Destination=%s
File Adapter was unable to send a message to the network. The %s cause details why. It may indicate a network or RV daemon problem.
An attempt to allocate memory failed. 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 subscribe to Subject/Destination <%s> cause=%s
Unable to create a listener. TIBCO EMS/Rendezvous may be unavailable. Check with your TIBCO administrator.
FileHandler Memory allocation failed for new [FileType]. Length=%d
An attempt to allocate memory failed. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
Memory allocation failed for SaveTimer entry. Length=%d
An attempt to allocate memory failed. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
HeartBeat Msg Memory allocation failed. Length=%d
An attempt to allocate memory failed. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
HeartBeat Nested Msg Memory allocation failed. Length=%d
An attempt to allocate memory failed. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
FileSubscriber was unable to create a heartbeat message. Check that TIBCO EMS/Rendezvous is available.
Unable to add the specified string to a heartbeat message. Check that TIBCO EMS/Rendezvous is available.
Unable to add the specified string to a heartbeat message. Check that TIBCO EMS/Rendezvous is available.
Unable to add the file prefix field to a heartbeat message. Check that TIBCO EMS/Rendezvous is available.
Unable to add the file extension to a heartbeat message. Check 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 Begin Time string to the heartbeat timer message. Check with the TIBCO administrator.
Unable to add the NumMsgs string to the heartbeat timer message. Check with the TIBCO administrator.
Unable to add the BlockNum string to the heartbeat timer message. Check with the TIBCO administrator.
Unable to add the LineNum string to the heartbeat timer message. Check with the TIBCO administrator.
Too many previous AddMessage errors forced the FileSubscriber to abandon sending a heartbeat timer message. Check with the TIBCO administrator.
Failed to set Heartbeat send Subject/Destination: %s cause=%s
An error was returned when the Adapter attempted to set the subject/destination name in a Heartbeat message to be published. Ensure that a valid subject/destination name is specified in the configuration file.
Unable to destroy a published heartbeat message. Make sure that TIBCO EMS/Rendezvous is available.
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.
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 Adapter was unable to send a message to the network. The %s cause details why. It may indicate a network or RV daemon problem.
File Adapter encountered an error when destroying. If it persists, contact TIBCO technical support.
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
Unable to extract the host name being used by TCPIP. Probably indicates that TCP/IP is not up or not functioning.
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.
Security mapping file %s has invalid data: Line=%d <%s>
There is an error in the security mapping file. Verify that the configuration file is coded properly.
GETMAIN failed while processing Security mapping file %s at Line=%d
An attempt to allocate memory failed. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
TIBCO EMS/Rendezvous may be unavailable or may not be active. Check with your TIBCO administrator.
TIBCO EMS/Rendezvous may be unavailable or may not be active. Check with your TIBCO administrator.
Failed to subscribe to Subject/Destination <%s> reason: %s
TIBCO EMS/Rendezvous may be unavailable or may not be active. Check with your TIBCO administrator.
Failed to create the Priority Admin RV queue-- reason: %s
TIBCO EMS/Rendezvous may be unavailable or may not be active. Check with your TIBCO administrator.
SXF7000 – SXF7999
The open of a TEXT file failed. The cause contains the reason for the failure.
The open of a BINARY file failed. The cause contains the reason for the failure.
A target file is being generated, but data has been lost or truncated. This indicates either a B37/D37 out of space error, or a configuration (incorrect file size) error.
<%s> Exiting because of file save error. Deleted PRP and PRG
A target file could not be properly saved and closed. The File Adapter was configured to shutdown in such a case.
<%s> close failed during trailer append. errno=%d errtext=%s
The close of a file failed after file trailer data was added. The cause contains the reason for the failure.
<%s> close failed during header append. errno=%d errtext=%s
The close of a file failed after file header data was added. The cause contains the reason for the failure.
<%s> Recovery mode: Generating error file=<%s> due to %s
The File Adapter is performing recovery after a shutdown or crash, and is generating an ERR file because of an error encountered.
<%s> File transfer: Generating error file=<%s> due to %s
The File Adapter is was generating a file but received an error, so it is converting it to an ERR file.
<%s> remove of PREV file failed because PREV file does not exist. errno=%d errtext=%s
A file type was configured to REPLACE an existing file, but there was a problem with the old file it was replacing, as described in the errtext portion.
A file type was configured to REPLACE an existing file, but there was a problem with the old file it was replacing, as described in the errtext portion.
<%s> GDG dataset=<%s> close failed. errno=%d errtext=%s
The close of a GDG file failed. The errtext contains the reason for the failure.
The close of a GDG file failed. The errtext contains the reason for the failure.
<%s> GDG fclose failed during recovery. cause=%d: %s
<%s> Recovery GDG fopen failed using file=<%s> mode=<%s>.\n cause=%d: %s
<%s> Recovery SEQ fopen failed using file=<%s> mode='r'. cause=%d: %s
<%s> SEQ fclose failed during recovery. cause=%d: %s
The close of a file failed during Recovery/Restart processing. The cause contains the reason for the failure.
<%s> Truncating TEXT data - discarded %d bytes. expectnl=%d
The data received for a FileType exceeds the max length configured for the File Type. The data has been truncated.
<%s> Truncating TEXT data - discarded %d bytes. expectnl=%d
The data received for a FileType exceeds the max length configured for the File Type. The data has been truncated.
Retry timer pop: retry # %d trying to move .CWK to target file=<%s>. (timer interval=%d secs)
A target file is temporarily locked by another job. This indicates when the File Adapter attempts to again try to see if the file is now free.
Move operation could not remove file <%s>. Deleting PRP and PRG
Could not remove the specified file. The transfer is being aborted. See the previous error message in the trace log for the cause of the problem.
<%s> ### Continuing to accept data in working file
New data has been received into the CWK file after a previous error (e.g. failed Generate). The File Adapter will continue to try to process the incoming data.
<%s> Retry limit=<%d> for Target File Locked <%s> has been reached. Deleting PRP and PRG files too.
A target file that was temporarily locked by another job has exceeded its max retry limit. The received new file data will be converted to an ERR file.
A target file could not be properly saved and closed. The File Adapter was configured to shutdown in such a case.
<%s> ### Continuing to accept data in working file
New data has been received into the CWK file after a previous error (e.g. failed Generate). The File Adapter will continue to try to process the incoming data.
Encountered an invalid variable name. Correct identified invalid variable name in the configuration file.
The configuration parser program was unable to properly parse a variable. Check the configuration file for adding header or trailer records. These must be framed with '%'.
<%s> Move operation could not remove workfile: cause=%d: %s. Caller=%s
Could not remove the specified file. The transfer is being aborted. The cause contains the reason for the error.
Unable to convert a TIME value from a received message, and it will use the current system time for the TIME field in an output record. Check the configuration file to ensure that the field identified contains a TIME value.
Unable to construct the subject/destination from the message node. Check the configuration file for this message.
Failed to extract field <%s> to form Subject/Destination name
Unable to construct the subject/destination from the field data. Check the configuration file for this message.
Failed to write data from file <%s> - wrote %d out of %d
A file write failed. It is usually due to a B37/D37 out of space error. See the previous error message in the trace log for the exact cause.
Could not remove the specified file. The transfer is being aborted. See the previous error message in the trace log for the cause of the problem.
Could not remove the specified file. The transfer is being aborted. See the previous error message in the trace log for the cause of the problem.
<%s> Block number %d arrived before IFACTIVE_REPLY Ack, Discarding the block.
A timing race occurred between Block Mode ECM Publisher and Subscriber at startup. The message block will be discarded and re-transmitted once the startup handshake sequence is complete.
<%s> Dup Block number %d matches previous block (%d), skipping write for workfile
FileSubscriber has received a block of data that has already been received. The block is ignored.
<%s> Block number %d is not next in sequence. Expected blk=%d
<%s> TEXT file write fixed width Field failed for workfile
A file write failed. It is usually due to a B37/D37 out of space error. See the previous error message in the trace log for the exact cause.
A file write failed. It is usually due to a B37/D37 out of space error. See the previous error message in the trace log for the exact cause.
Unable to convert a TIME value from a received message, and it will use the current system time for the TIME field in an output record. Check the configuration file to ensure that the field identified contains a TIME value.
Source file is retained while moving a file. It is possible that the 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.
<%s> Move operation could not remove workfile: cause=%d: %s
Source file is retained while moving a file. It is possible that the 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.
<%s> Move operation could not remove workfile: cause=%d: %s
Source file was in use by another process when the Adapter attempted to remove the file
<%s> Timer: Move operation could not remove workfile. Deleting PRP and PRG
Source file was in use by another process when the Adapter attempted to remove the file
A message was received that does not match the configuration file. The configuration file/field specification for a received message does not correspond to the message received. Correct the file/field specification for the subject/destination being subscribed to, or check the source that published the message.
A message was received that does not match the configuration file. The configuration file/field specification for a received message does not correspond to the message received. Correct the file/field specification for the subject/destination being subscribed to, or check the source that published the message.
Failed to unsubscribe to Subject/Destination <%s>: cause=%s
During shutdown, the FileSubscriber was unable to terminate the subscription to a Subject. The cause %s specifies what the problem was
Failed to unsubscribe to Subject/Destination <%s>: cause=%s
During shutdown, the FileSubscriber was unable to terminate the subscription to a Subject. The cause %s specifies what the problem was
Failed to unsubscribe to Subject/Destination <%s>: cause=%s
During shutdown, the FileSubscriber was unable to terminate the subscription to a Subject. The cause %s specifies what the problem was
Failed to unsubscribe to Subject/Destination <%s>: cause=%s
During shutdown, the FileSubscriber was unable to terminate the subscription to a Subject. The cause %s specifies what the problem was
During shutdown, the FileSubscriber was unable to terminate the RV or EMS. The cause %s specifies what the problem was
Vsam LOG write failed. Abending File Adapter
The write operation on the log file has failed and the Adapter is abending. This happens when the vsamUseLog parameter is set to "StopOnFull".
Vsam LOG write failed on <%s>. Abending File Adapter
<%s> reached B37/E37 file out of space. Terminating processing for that file
The VSAM file has reached an out of space condition. Any subsequent data destined for that file is rejected and discarded.
<%s> reached B37/E37 file out of space. Terminating processing for that file
The VSAM file has reached an out of space condition. Any subsequent data destined for that file is rejected and discarded.
%s Data set type (PDS) is not supported in this application
The data set supported for this application must not be PDS. PDS data sets cannot be used for FileSubscriber, you must use either SEQ or GDG data sets. Change the data set type to SEQ or GDG.
Unable to allocate memory to create a new message. Report this error to your TIBCO administrator.
Compression block Memory reallocation failed. Length=%d
An attempt to re-allocate memory failed. It normally indicates insufficient memory for the REGION. If increasing the REGION size does not solve the problem, then contact TIBCO technical support.
<%s> 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.
An error occurred when sending a message. The Adapter may not be active. Contact your TIBCO administrator.
Failed to subscribe to Subject/Destination <%s>: cause=%s
Unable to create a listener. TIBCO EMS/Rendezvous may be unavailable. Check with your TIBCO administrator.
Failed to subscribe to Subject/Destination <%s>: cause=%s
Unable to create a listener. TIBCO EMS/Rendezvous may be unavailable. Check with your TIBCO administrator.
Failed to subscribe to Subject/Destination <%s>: cause=%s
Unable to create a listener. TIBCO EMS/Rendezvous may be unavailable. Check with your TIBCO administrator.
Failed to subscribe to Subject/Destination <%s>: cause=%s
Unable to create a listener. TIBCO EMS/Rendezvous may be unavailable. Check with your TIBCO administrator.
<%s> Error moving workfile to target file=%s. Reason=%s. erron=%d file_rc=%d secur_rc=%d append=%d eof=%d
A target file could not be properly saved and closed. The reason code describes what the problem was.
<%s> File open failed for workfile using mode '%s'. errno=%d R15=%d Reason Fdbk=%d op=%d ab_sys=0x%X ab_rc=0x%X
A CWK work file could not be opened. The reason code describes what the problem was.
<%s> File was empty, now has data. Will re-open in non-LOAD mode
A VSAM data transfer encountered a target file that was completely empty. The File Adapter will re-open the file and treat the transfer as an initial LOAD of the VSAM file.
<%s> Can not open file because RLS function is inactive. SMSVSAM not up
A shared VSAM file could not be processed, because the MVS RLS function is not active. Contact your MVS systems programmer.
<%s> Can not open file because trying to output to a Recoverable Sphere
A shared VSAM file could not be processed because it was defined as being recoverable. Contact your MVS systems programmer.
<%s> Can not open file because RLS requires SMS files.File is not SMS managed
A shared VSAM file could not be processed, because it was not defined as SMS managed. Contact your MVS systems programmer.
<%s> Can not open file because RLS detected DISP=SHR vs DISP=OLD conflict
A shared VSAM file could not be processed, because of conflicting DISP attributes. Contact your MVS systems programmer.
<%s> Can not open file because OPEN flag still set on from previous run or another App is trying to share the file.
A VSAM file could not be opened because it's file flag is set indicating that it was not properly closed from a previous job. Contact your MVS systems programmer.
<%s> Failed to open workfile: errno=%d err text=%s
<%s> Failed to malloc TEXT LRECL buffer of 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.
File open failed for LOG 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
The open of a FileAdapter VSAM LOG file failed. The errno text contains the reason for the failure.
<%s> Failed to open Progress file: <%s> errno=%d errtext=%s
The open of a FileAdapter PRG progress file failed. The errtext contains the reason for the failure.
The JCL specified for executeAfterProcess or executeBeforeProcess did not execute properly. Check the JCL specified, and ensure that it can execute properly.
The JCL specified for executeAfterProcess or executeBeforeProcess did not execute properly. Check the JCL specified, and ensure that it can execute properly.
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.
<%s> Error saving next GDG generation number for GDG=<%s>
Creation of a new target GDG file failed. See the previous error message in the trace log for the cause of the error.
The free/deallocate of a GDG file failed. See the previous error message in the trace log for the cause of the error.
<%s> Error deallocating GDG=<%s>\n reason: %s
Unable to deallocate a dynamically allocated GDG file. Either the target data set is not available or is invalid. Provide a valid data set name in the configuration file. You must have the proper authority to create or modify data sets.
Unable to move a file. Either the target data set is not available or is invalid. Provide a valid data set name in the configuration file.
<%s> Error creating GDG file=<%s>, error=%s
File subscriber attempted to create a GDG file for output, but the file create failed. You must have the proper authority to create or modify data sets.
Unable to move a file. Either the target data set is not available or is invalid. Provide a valid data set name in the configuration file.
Unable to move a file. Either the target data set is not available or is invalid. Provide a valid data set name in the configuration file.
Unable to move a file. Either the target data set is not available or is invalid. Provide a valid data set name in the configuration file.
<%s> Failed to close .PRG file=%s, aborting genOutFile
Unable to close the progress file. Check the process directory. The file may be corrupted.
<%s> Failed to remove .PRG file=%s, aborting genOutFile
Unable to remove the progress file. Check the process directory. The file may be corrupted or not properly cataloged.
<%s> Failed to remove .PRG file=%s, aborting genOutFile
Unable to remove the progress file. Check the process directory. The file may be corrupted or not properly cataloged.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and be certain that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and be certain that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file and ensure that the configuration file matches the received message.
<%s> default Type mismatch while retrieving value: %s, pf_type: %d
The field type received does not match the expected data type that was configured. Correct the configuration file and ensure that the configuration file matches the received message.
Unable to extract a requested field from the message node. Check the configuration file for this message to ensure the fields in the message are correctly specified.
Log Write <%s> failed: errno=%d last_op=%d ab_syscode=0x%X ab_rc=%d err text=%s
The write operation to the log file has failed. This message gives the error codes and the text message of the error codes.
LOG file <%s> reached B37/E37 end of File. Wrapping to Begin of file.
The log file is complete and the vsamUseLog parameter is not set. After this message, the Adapter starts writing in the log from the beginning.
<%s> Output file failed: errno=%d last_op=%d R15=%d Fdbk=%d ab_syscode=0x%X ab_rc=%d\n svc99 inf=%d err=%d err text=%s
The write operation to the target file has failed. This message gives the error codes and the text message of the error codes.
<%s> Text File Write failed: errno=%d err text=%s
The write operation to the TEXT file has failed. This message gives the error codes and the text message of the error codes.
<%s> Binary File Write failed: errno=%d last_op=%d ab_syscode=0x%X ab_rc=%d\n err text=%s
The write operation to the BINARY file has failed. This message gives the error codes and the text message of the error codes.
VSAM key flocate failed for file %s. Record rejected R15=%d Fdbk=%d err=%s
VSAM key flocate failed because no such record (not found)
The subscriber received a record for a VSAM file operating in replace mode, and there is no corresponding record on the subscriber. The incoming record from the publisher is discarded. Verify that two VSAM systems are in sync with each other when using record level replacement.
Unable to open a CWK work file. It usually indicates an out of space B37/D37 problem, or a RACF authorization problem. The cause contains the exact cause of the error.
Unable to open a CWK work file. It usually indicates an out of space B37/D37 problem, or a RACF authorization problem. The cause contains the exact cause of the error.
<%s> Failed to close .PRG file=%s, aborting recovery
A close on a Progress PRG file being used failed. Save the %s reason code and discuss the issue with the MVS Systems programmer.
<%s> Failed to malloc TEXT LRECL buffer of length=%d
<%s> Unable to open .PRP file=%s, aborting recovery
Unable to open a CWK work file. It usually indicates an out of space B37/D37 problem, or a RACF authorization problem. The cause contains the exact cause of the error.
<%s> Failed to read data in PRP file, aborting recovery
Unable to read data cached in the partial record file. Check the process directory. The file may be corrupted.
<%s> Failed to read data in progress file, aborting recovery
Unable to read the progress file. Check the process directory. The file may be corrupted.
<%s> Failed to remove .PRG file=%s, aborting recovery
Unable to remove a file. Either the target data set is not available or is invalid. Report this error to your TIBCO administrator.
<%s> Failed to recover Work file=<%s>. fopen with Append failed. Cause=%d: %s
Unable to recover a work file. The file may be corrupted. Contact the TIBCO administrator.
<%s> Failed to mallet TEXT LRECL buffer of length=%d
<%s> No hostname supplied on message with Security check
Security is turned on for the Adapter, but an incoming message did not have a Publisher host name associated with it. The request is discarded. Verify that the Publisher is set up to automatically send the Publisher's host name to the Subscriber.
<%s> No User Id supplied on message with Security check
Security is turned on for the Adapter, but an incoming message did not have a User Id associated with it. The request is discarded. Verify that the Publisher is setup to automatically send the UserId to the Subscriber.
<%s> Failed to extract checksum from end-of-file message
Failed to write data from file <%s> - wrote %d out of %d
Could not add the data to the file, probably due to an out of space issue. Check the system log for related space problems.
<%s> Failed to retrieve sequence/block_id number from ECM msg. cause=%s on Subject/Destination=<%s>. field=%s
Unable to retrieve a block number from a block transfer file. Ensure that the file being subscriber to is being published in block mode.
Unable to retrieve unique GUID from a block transfer file. Ensure that the file being subscriber to is being published in block transfer mode.
<%s> Failed to retrieve block DATA for block # %d for workfile. cause=%s
Unable to retrieve data element from a block transfer file. Ensure that the file being subscriber to is being published in block transfer mode.
<%s> Write Failed for block num=%d on workfile. cause=%d: %s
Could not add the new block of data to the file, probably due to an out of space issue. Check the system log for related space problems.
<%s> TEXT file write delimiter %s failed for workfile
Could not add the delimiter data to the file, probably due to an out of space issue. Check the system log for related space problems.
<%s> Failed to retrieve field <%s> from message for workfile
Unable to retrieve field, possible configuration mismatch. Check the configuration file, and ensure that it matches the received message
Could not add the delimited value data to the file, probably due to an out of space issue. Check the system log for related space problems.
Could not add the padding data to the file, probably due to an out of space issue. Check the system log for related space problems.
<%s> Failed to retrieve field <%s> from message for workfile
Unable to retrieve field, possible configuration mismatch. Check the configuration file, and ensure that it matches the received message.
Could not add the value data to the file, probably due to an out of space issue. Check the system log for related space problems.
<%s> TEXT file write padded Field Value failed: <%s>
Could not add the value data to the file, probably due to an out of space issue. Check the system log for related space problems.
MVS signalled some sort of I/O error. Check previous message in trace log for more details on the cause.
<%s> Failed to retrieve embedded VSAM RRN field from message for file
Failed to retrieve field, possible configuration mismatch. Check the configuration file, and ensure that it matches a corresponding VSAM file at the publisher side.
<%s> Failed to retrieve field <%s> from message for workfile
Failed to retrieve field, possible configuration mismatch on the message definition. Check the configuration file, and ensure that it matches the received message.
Data value retrieved from file is invalid. Possible configuration mismatch on the message definition.
<%s> Failed to retrieve field <%s> from message for workfile
Failed to retrieve field, possible configuration mismatch. Check the configuration file, and ensure that it matches the received message.
The write operation to the BINARY file has failed. This message gives the error codes and the text message of the error codes.
<%s> BINARY file write failed details: errno=%d R15=%d Fdbk=%d op=%d ab_sys=0x%X ab_rc=0x%X\n errno text=%s
The write operation to the BINARY file has failed. This message gives the error codes and the text message of the error codes.
<%s> File write failed because duplicate record RRN or key already exists
The write operation to a VSAM RRDS file has failed. This message gives the error codes and the text message of the error codes.
<%s> Probably due to ALTINDEX Key mis-match (rcvd key != existing key)
The write operation to the VSAM KSDS file has failed. This message gives the error codes and the text message of the error codes.
<%s> Write Failed for block num=%d on workfile for %d TEXT records of max %d bytes each. Error=%d: %s
The write operation to the TEXT file has failed. This message gives the error codes and the text message of the error codes.
<%s> Unable to open .PRP file=%s, data exposure if crash
The open for a TEXT file's partial data buffer file has failed. This message gives the error codes and the text message of the error codes.
<%s> Unable to write to .PRP file=%s, data exposure if crash
The write operation to the TEXT file partial data buffer file has failed. This message gives the error codes and the text message of the error codes.
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 Block Num to Confirm message
Unable to add the BlockNumber field to an ECM Confirm message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to add the Status field to an ECM Confirm message. Make that TIBCO EMS/Rendezvous is available.
<%s> Failed to append Subscriber Name to Confirm message
Unable to add the Subscriber Name field to an ECM Confirm message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to add the GUID field to an ECM Confirm message. Make sure that TIBCO EMS/Rendezvous is available.
Unable to add the BlockNumber field to an ECM Confirm message. Make sure that TIBCO EMS/Rendezvous is available.
<%s> Failed to set RVCM send target: cause=%s Subject/Destination=%s
An error was returned when the Adapter attempted to publish a message. Ensure that a valid subject/destination name is specified in the configuration file.
Unable to set a time limit for a certified message. Check that TIBCO EMS/Rendezvous is available and operating properly.
<%s> 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.
<%s> Failed to set send target: cause=%s Subject/Destination=%s
An error occurred when sending an RVCM message. The Adapter may not be active. Contact your TIBCO administrator.
<%s> Error in sending message: cause=%s Subject/Destination=%s
An error occurred when sending an RVCM message. The Adapter may not be active. Contact your TIBCO administrator.
Unable to create a genFilePublish message. Ensure that TIBCO EMS/Rendezvous is available.
<%s> Failed to add filename to genFilePublish message: cause=%s
Unable to add the filename field to a genFilePublish 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 append num of lines to genFilePublish message: cause=%s
Unable to add the number of lines field to a genFilePublish message. Make sure that TIBCO EMS/Rendezvous is available.
<%s> Failed to append num of messages to genFilePublish message: cause=%s
Unable to add the number of messages field to a genFilePublish message. Make sure that TIBCO EMS/Rendezvous is available.
<%s> Failed to create Tracking 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 add filename to genFilePublish message: 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.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> NULL string contents while retrieving value: %s, type: %d
The field type expected a STRING value but the received data contained a NULL instead. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The specified field type does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Default Type mismatch while retrieving value: %s, from type=%d to type=%d
An attempt was made to retrieve a message, but the message type did not match the configuration file definition. Verify the type of field that was published.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Type mismatch while retrieving value: %s, type: %d
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported FLOAT conversion of type=%d for %s
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported PACKED conversion of type=%d for %s
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> String <%s> length is %d. Must be less than 19.
A string field was longer than 19 bytes. If a string field is to be used for numeric conversions, it must be less than 19 bytes.
<%s> Unsupported ZONED conversion of type=%d for %s
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported COMP/SHORT conversion of type=%d for %s
The field type specified does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported COMP/INTEGER conversion of type=%d for %s
The specified field type does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported COMP/LONGLONG conversion of type=%d for %s
The field type specified does not match the received data. Correct the configuration file, and be certain that the configuration file matches the received message.
<%s> Unsupported FLOAT conversion of type=%d for %s
The field type specified does not match the received data. Correct the configuration file, and be certain that the configuration file matches the received message.
<%s> Unsupported DISPLAY/INTEGER conversion of type=%d for %s
The specified field type does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported DISPLAY/UNSIGNED INTEGER conversion of type=%d for %s
The specified field type does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported DISPLAY/SHORT conversion of type=%d for %s
The specified field type does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported DISPLAY/UNSIGNED SHORT conversion of type=%d for %s
The specified field type does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Unsupported DISPLAY/INTEGER conversion of type=%d for %s
The specified field type does not match the received data. Correct the configuration file, and ensure that the configuration file matches the received message.
<%s> Error saving current status for workfile, into statfile=%s
A file I/O error occurred. If the problem persists, contact your MVS Systems programmer.
<%s> Could not malloc I/O buffer for move. cause=%d: %s
<%s> Move failed: could not open workfile: cause=%d: %s
The file specified could not be opened. Be sure that FilePublisher has the proper authority.
<%s> Move failed: could not open target file <%s> cause=%d: %s
The specified file could not be opened. Make sure that FilePublisher has the proper authority.
<%s> Move failed: could not close workfile: cause=%d: %s
The specified file could not be moved. Make sure that FilePublisher has the proper authority.
<%s> Move failed: Unable to close target file <%s> cause=%d: %s
The specified file could not be moved. Make sure that FilePublisher has the proper authority.
<%s> Move failed: could not close workfile: cause=%d: %s
The specified file could not be moved. Make sure that FilePublisher has the proper authority.
<%s> Move failed: could not open workfile. cause=%d: %s
The open operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Move failed could not open target file <%s> using mode=%s Cause=%d:
The open operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Move failed: Unable to close workfile: cause=%d: %s
The close operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Move failed: could not fwrite to target file<%s> Cause=%d: %s
The write operation failed. Check that the target directory is available and that there are no authority problems, and there is sufficient space on the volume.
<%s> Move failed: could not fprintf to target file <%s> cause=%d: %s
The write operation failed. Check that the target directory is available and that there are no authority problems, and there is sufficient space on the volume.
<%s> Move failed: could not write to target file <%s> Cause=%d: %s
The write operation failed. Check that the target directory is available and that there are no authority problems, and there is sufficient space on the volume.
<%s> Move failed: Unable to close target file <%s> cause=%d: %s
The close operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Move failed: Unable to close workfile: cause=%d: %s
The close operation failed. Check that the target directory is available and that there are no authority problems.
The GDG Deallocate operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Error moving working file to <%s>. Retry limit %d reached.
The target file was still locked out (in use by another job), after the max retry limit has been reached. The incoming file is converted to an ERR file, and trying to update the target file will be abandoned.
<%s> Failed to retrieve sequence/block_id number from msg. cause=%s on Subject/Destination=%s
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 extract Hostname from end-of-file message
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 extract UserId from end-of-file message
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> Error saving STERR num error status file=%s
A file write failed. It is usually due to a B37/D37 out of space error. See the previous error message in the trace log for the exact cause.
A VSAM file update failed. It is usually due to a B37/D37 out of space error. See the previous error message in the trace log for the exact cause.
<%s> VSAM fread for update failed for file.\n R15=%d Fdbk=%d op=%d ab_sys=0x%X ab_rc=0x%X\n errno=%d errno text=%s
The read of a VSAM file failed. The cause contains the reason for the failure.
<%s> VSAM update failed for file. R15=%d Fdbk=%d op=%d ab_sys=0x%X ab_rc=0x%X\n errno=%d errno text=%s
A VSAM file update failed. It is usually due to a B37/D37 out of space error. The cause contains the reason for the failure.
<%s> User=<%s> (Pub Id=%s) is not allowed WRITE access to target File=<%s>.
Security checking was requested, and the MVS security facility indicated the incoming File Transfer 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 write to that file.
<%s> Recovery for GDG file failed probably because Ops deleted CWK work file=%s. Progress file is being reset and recovery for that file has been abandoned. cause=%d: %s
Unable to recover a work file being used to update a GDG file. The file may be corrupted or may have been deleted. Contact the TIBCO administrator.
<%s> Recovery for SEQ file failed probably because Ops deleted CWK work file=%s. Progress file is being reset and recovery for that file has been abandoned. cause=%d: %s
Unable to recover a work file being used to update a Sequential file. The file may be corrupted or may have been deleted. Contact the TIBCO administrator.
Denotes that a file transfer is complete, and that the file type is being reset.
<%s> There is an error in the configuration for this FileType. Cannot create the subscriber %s
Unable to create a listener for a subscriber because of errors previously reported in the configuration processing phase. Check the trace log to determine the problem in the configuration file and correct it.
<%s> UserId=<%s> from node=%s was not found in Security Mapping Table. Request to update Subscriber file was rejected. Block# %d
Security checking was requested, and the MVS security facility indicated the incoming File Transfer 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 write to that file.
Denotes that a file transfer is complete, and that the PRG file for that file type is being deleted.
File Type <%s> Error encountered. Closing all .CWK, .PRG, and .PRP files
A severe I/O error occurred when processing a incoming file transfer. See the previous message in the trace log for the cause of the problem
<%s> Rename of workfile %s to .ERR error file %s failed for %.16s. Reason=%d: %s
The rename operation failed. Check that the target directory is available and that there are no authority problems.
<%s> Got I/O error on .PRG file=%s. Reason=%d: %s
A file write failed on a PRG progress file. It is usually due to a B37/D37 out of space error. See the previous error message in the trace log for the exact cause.
<%s> Error removing GDG file=<%s>. Reason=%d: %s
Unable to remove a file. Either the target data set is not available or it is invalid. Provide a valid data set name in the configuration file.
<%s> Failed to retrieve sequence/block_id number from Record ECM msg. cause=%s on Subject/Destination=<%s>. useNT=%d
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> Rename of workfile %s to target file %s failed. Reason=%d: %s
The specified file could not be renamed. Be sure that FilePublisher has the proper authority.
<%s> User=<%s> (Pub Id %s) is not allowed WRITE access to target File=<%s>. Rejected. RC=%d racf_rc=%d subcode=0x%x VOLSER=<%s> %s
A file is being written and RACF has flagged an error (e.g. the FileAdapter user does not have ALTER/Update authority to that dataset.). Contact your RACF systems programmer.
<%s> User=<%s> (Pub Id %s) is not allowed ALTER access to work file=<%s>. Rejected. RC=%d racf_rc=%d subcode=0x%x VOLSER=<%s> %s
A file is being written and RACF has flagged an error (e.g. the FileAdapter user does not have ALTER/Update authority to that dataset.). Contact your RACF systems programmer.
<%s> Unable to write to target=<%s> and 'File Locked' retry timer failed. cause=%d: %s
A file was locked and the File Adapter was unable to create a retry timer. This usually indicates an out of memory condition, or a failure/crash in the underlying RV support.
<%s> File open failed because unable to allocate dataset. Dataset is unavailable and/or allocated to another job. SVC99 codes=%d %d
The file is not available. The SVC99 codes contains the reason for the failure.
<%s> Error writing CWK workfile. GDG target file=<%s> not created. file_rc=%d
A file write failed. It is usually due to a B37/D37 out of space error. The file_rc code gives the cause of the error.
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 field types are trying to use the same file. This is not allowed.
Svc99 error: RACF/ACF2 Security problem
A 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 file that exists on a SMS managed volume
Svc99 error: Catalog error - program not authorized to perform operation
A 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 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 field 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.
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.
Output File <%s> could not be opened using mode=<%s> errno=%d %s
<%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> Unable to read source CWK file <%s> cause=%d: %s
The read operation failed. Check that the CWK workfile directory is available and that there are no authority problems.
<%s> Subscriber I/O error caused File Transfer Abort: %d %s
A file write failed. It is usually due to a B37/D37 out of space error. The Abort code contains the cause of the error. The File Transfer is aborted.
<%s> ConfBlock - Failed to create 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> File open, rename, or append write failed because unable to allocate dataset. Dataset is unavailable and/or allocated to another job. SVC99 codes=%d %d op=%d
A file open or rename failed. The SVC99 codes contains the cause of the error.
<%s> Discarding Block # %d because of previous ECM I/O Error.
A new block was received after an I/O error was signalled to the Publisher. The block will be discarded.
<%s> Failed to close .PRG file=%s, aborting renameByCopy. error=%d: %s
A file close failed for a PRG progress file. The errno contains the cause of the error. The file transfer will be aborted.
<%s> Failed to open Progress file during Lock Retry: <%s> errno=%d errtext=%s
A file open failed during a locked file retry. The errno contains the cause of the error.
<%s> There is an error in the configuration for this FileType. Will NOT perform the NT ECM Admin handshake for subscriber=%s ----
Check configuration phase error messages from FileAdapter startup and correct the error.
SXF8000 – SXF8999
FileType=<%s>: Subject=<%s> Unable to extract reply_subject back to Publisher
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
FileType=<%s>: Subject=<%s> Publisher indicates we are not registered for ECM mode. Flipping out to non-ECM mode.
This normally indicates a configuration mis-match between the Publisher and the Subscriber.
FileType=<%s>: Subject=<%s> Publisher rejected our VERIFY_IFACTIVE_REQUEST - we are not registered. Issuing SUB_ACTIVATION_REQUEST
This indicates either that the Progress file was deleted at the Publisher, or a configuration mis-match between Publisher and Subscriber.
FileType=<%s>: Subject=<%s> Publisher rejected our SUB_ACTIVATION_REQUEST
This indicates either that the Progress file was deleted at the Publisher, or a configuration mis-match between Publisher and Subscriber.
FileType=<%s>: Subject=<%s> Publishing ECM VERIFY_IFREGISTERED_
REQUEST handshake message with SubscriberName=%s using GUID=%s retry#%d
Message indicating that a restart/recovery sequence was performed between Publisher and Subscriber.
<%s> Listener setup Failed for Admin Request subject <%s> cause=%s
An attempt to create an RV or EMS listener 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> Listener setup Failed for Admin Reply subject <%s> cause=%s
An attempt to create an RV or EMS listener 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.
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
<%s>: Error on sending RV Admin message: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s>: Error on sending RV Admin message: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s>: Error on sending RV Admin message: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s>: Error on sending RV Admin message: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s>: Error on sending RV Admin message: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s>: Error on sending RV Admin message: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s>: Error on sending RV Admin message: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
<%s> Admin Timer creation failed for Subject <%s>: cause=%s
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.
FileType=<%s>: Received unknown ECM Admin config reply. msgtype=%d
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
FileType=<%s>: SUB_IS_REG_REPLY = False. Startup Handshake rejected
This normally indicates a configuration mis-match between the Publisher and the Subscriber.
FileType=<%s>: Received unknown ECM Admin config reply. msgtype=%d
This is a Block Mode ECM internal or recovery type error. Contact TIBCO technical support.
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
An attempt to add a new 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 append MsgId/Guid to Admin message: %s
An attempt to add a new 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 new 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 new 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 append NumRetries to Admin message: %s
An attempt to add a new 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 new 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 new 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 tech support.
<%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 create RV Admin SUB_ACTIVATION message: %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 append MsgType to Admin message: %s
An attempt to add a new 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 append MsgId/Guid to Admin message: %s
An attempt to add a new 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 append SubscriberName to Admin message: %s
An attempt to add a new 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 new 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 set RV Admin send subject: cause=%s subject=%s
An attempt to add a new 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 set RV reply subject: cause=%s subject=%s
An attempt to add a new 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 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 create RV Admin REG_SUB_ALIVE_REPLY message: %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 append MsgType to Admin message: %s
An attempt to add a new 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 append MsgId/Guid to Admin message: %s
An attempt to add a new 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 append SubscriberName to Admin message: %s
An attempt to add a new 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 new 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 set RV Admin send subject: cause=%s subject=%s
An attempt to add a new 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 set RV reply subject: cause=%s subject=%s
An attempt to add a new 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 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 create RV Admin VERIFY_IFACT message: %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 append MsgType to Admin message: %s
An attempt to add a new 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 append MsgId/Guid to Admin message: %s
An attempt to add a new 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 append SubscriberName to Admin message: %s
An attempt to add a new 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 new 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 set RV Admin send subject: cause=%s subject=%s
An attempt to add a new 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 set RV reply subject: cause=%s subject=%s
An attempt to add a new 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 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 create RV Admin VERIFY_IFREG message: %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 append MsgType to Admin message: %s
An attempt to add a new 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 append MsgId/Guid to Admin message: %s
An attempt to add a new 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 append SubscriberName to Admin message: %s
An attempt to add a new 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 new 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 set RV Admin send subject: cause=%s subject=%s
An attempt to add a new 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 set RV reply subject: cause=%s subject=%s
An attempt to add a new 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 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 create RV Admin VERIFY_IFACTIVE_REPLY message: %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 append MsgType to Admin message: %s
An attempt to add a new 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 new 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 new 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 set RV Admin send subject: cause=%s subject=%s
An attempt to add a new 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 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 create RV Admin SUB_ACTIVATION_REPLY message: %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 append MsgType to Admin message: %s
An attempt to add a new 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 new 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 append 'isactivated' to Admin message: %s
An attempt to add a new 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 set RV Admin send subject: cause=%s subject=%s
An attempt to add a new 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 send RV Admin msg: cause=%s subject=%s
Unable to publish an ECM Admin message. Check that TIBCO EMS/Rendezvous is available.
SXF9000 – SXF9999
A library needed by the FileAdapter is missing. Re-check the STEPLIB definitions used in the File Adapter JCL.
A TIBCO API failed. Note the return code and contact your TIBCO administrator.
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.
Could not find the specified library. 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.
An internal FileAdapter error occurred. 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.
An attempt to free an RV or EMS timer failed. If the problem persists, then contact TIBCO technical support.
Error renaming Sub log file <%s> to <%s> cause: %d %s. File logging turned off...
The File Adapter was unable to rename and open a new trace log file. The second %s details the cause of the problem.
Failed to open Sub 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.
Failed to open Sub 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.