| SXT5101E
|
RV-Type is undefined
|
| Explanation: The Rendezvous Type field is not on the list of fields that can be processed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5102E
|
RV-ARRAYs are not supported
|
| Explanation: The Rendezvous array types are not supported.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5103E
|
RV-User types are not supported
|
| Explanation: Rendezvous user types are not supported.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5104E
|
Receiving field too short
|
| Explanation: The receiving field is too short for the input data.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5105E
|
Receiving field too long
|
| Explanation: The incoming data field is greater than 8 bytes which is the maximum for a binary number.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5106E
|
Receiving field has invalid length
|
| Explanation: The receiving field has an invalid length.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5107E
|
Numeric overflow
|
| Explanation: The receiving numeric field is too small for the input data.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5108E
|
String or Text overflow
|
| Explanation: The receiving string or text field is too small for the input data.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5109E
|
Input value is not numeric
|
| Explanation: The input value is not numeric.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5110E
|
Input float value invalid
|
| Explanation: The value of a float field is invalid.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5111E
|
Date-Time conversion error
|
| Explanation: An error occurred during the conversion to or from a date-time value.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5112E
|
U64 with high-order bit on
|
| Explanation: U64 with high-order bit is on.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5113E
|
Decimal adjust error
|
| Explanation: An error occurred during the adjustment of the placement of the decimal point.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5114E
|
Input string too large to pack
|
| Explanation: An input string is too large to pack into a packed decimal field.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5115E
|
Packed operation too large
|
| Explanation: A packed value contains too many significant digits.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5116E
|
Unknown buffer field type
|
| Explanation: The buffer definition contains an unknown type field.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5117E
|
Input RV-MSG not supported
|
| Explanation:
RV-MSG is not supported at the field level.
User Response: Correct the definition or input data.
System Action: The Input field is not processed.
|
| SXT5118E
|
Input ENCRYPT not supported
|
| Explanation: The Rendezvous type
ENCRYPT is not supported.
User Response: Correct the definition or input data.
System Action: The Input field is not processed.
|
| SXT5119E
|
Input NONE not supported
|
| Explanation: The Rendezvous type
NONE is not supported.
User Response: Correct the definition or input data.
System Action: The Input field is not processed.
|
| SXT5120E
|
Input XML not supported
|
| Explanation: The Rendezvous type XML is not supported.
User Response: Correct the definition or input data.
System Action: The Input field is not processed.
|
| SXT5121E
|
Cannot convert OPAQUE to PACKED
|
| Explanation: Conversion of
OPAQUE to
PACKED has failed.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5122E
|
Cannot convert OPAQUE to ZONED DECIMAL
|
| Explanation: Conversion of
OPAQUE to
ZONED DECIMAL has failed.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5123E
|
Cannot convert OPAQUE to UNSIGNED BINARY
|
| Explanation: Conversion of
OPAQUE to
UNSIGNED BINARY has failed.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5124E
|
Cannot convert OPAQUE to BINARY
|
| Explanation: Conversion of
OPAQUE to
BINARY has failed.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5125E
|
Cannot convert OPAQUE to FLOATING POINT
|
| Explanation: Conversion of
OPAQUE to
FLOATING POINT has failed.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5126E
|
Cannot convert IPADDR32 to PACK
|
| Explanation: Conversion of
IPADDR32 to
PACK has failed.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5127E
|
Cannot convert IPADDR32 to ZDEC
|
| Explanation: Conversion of
IPADDR32 to
ZDEC has failed.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5128E
|
Cannot convert IPADDR32 to FLOAT
|
| Explanation: Conversion of
IPADDR32 to
FLOAT has failed.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5129E
|
Cannot convert OPAQUE to U-PACKED
|
| Explanation: Conversion from
OPAQUE to Unsigned packed is not supported.
User Response: Correct the conversion rule or input message.
System Action: The conversion is marked as error.
|
| SXT5130E
|
Cannot convert OPAQUE to UZ-DEC
|
| Explanation: Conversion from
OPAQUE to Unsigned zoned decimal is not supported.
User Response: Correct the conversion rule or input message.
System Action: The conversion is marked as error.
|
| SXT5131E
|
Cannot convert IPADDR32 to UPACK
|
| Explanation: Conversion from
IPADDR32 to Unsigned packed is not supported.
User Response: Correct the conversion rule or input message.
System Action: The conversion is marked as error.
|
| SXT5132E
|
Cannot convert IPADDR32 to UZDEC
|
| Explanation: Conversion from
IPADDR32 to Unsigned zoned decimal is not supported.
User Response: Correct the conversion rule or input message.
System Action: The conversion is marked as error.
|
| SXT5201E
|
RV-Type is undefined
|
| Explanation: The Rendezvous Type field is not on the list of fields that can be processed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5202E
|
RV-ARRAYs are not supported
|
| Explanation: The Rendezvous array types are not supported.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5203E
|
RV-User types are not supported
|
| Explanation: The Rendezvous user types are not supported.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5205E
|
Receiving field has invalid length
|
| Explanation: The receiving field has an invalid length
User Response: Correct recipe definition.
System Action: The Input field is not processed.
|
| SXT5206E
|
Numeric overflow
|
| Explanation: The receiving numeric field is too small for the input data.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5207E
|
Input value is not numeric
|
| Explanation: The input value is not numeric.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5208E
|
Input float value invalid
|
| Explanation: The value of a float field is invalid.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5209E
|
Decimal adjust error
|
| Explanation: An error occurred during the adjustment of the placement of the decimal point.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5210E
|
Input string too large to pack
|
| Explanation: An input string is too large to pack into a packed decimal field.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5211E
|
Sending field too long
|
| Explanation: The sending field is too long.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5212E
|
Sending length is not positive
|
| Explanation: The sending field is described by a nonpositive length.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5213E
|
IPADDR32 string is invalid
|
| Explanation: The sending field is not in the proper IPADDR32 format.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5214E
|
Unknown buffer field type
|
| Explanation: The buffer definition contains an unknown type field.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5215E
|
Output RV-MSG not supported
|
| Explanation:
RV-MSG is not supported at the field level.
User Response: Correct the recipe definition or input data.
System Action: The Input field is not processed.
|
| SXT5216E
|
Output ENCRYPT not supported
|
| Explanation: The Rendezvous type ENCRYPT is not supported.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5217E
|
Output NONE not supported
|
| Explanation: The Rendezvous type NONE is not supported.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5218E
|
Output XML not supported
|
| Explanation: The Rendezvous type
XML is not supported.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5219E
|
Cannot convert [STRING | TEXT] to DATETIME
|
| Explanation: Conversion of
STRING or
TEXT to
DATETIME failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5220E
|
Cannot convert PACK to IPADDR32
|
| Explanation: Conversion of
PACK to
IPADDR32 has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5221E
|
Cannot convert ZDEC to IPADDR32
|
| Explanation: Conversion of
ZDEC to
IPADDR32 has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5222E
|
Cannot convert FLOAT to IPADDR32
|
|
Explanation: Conversion of
FLOAT to
IPADDR32 has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5223E
|
Cannot convert OPAQUE to DATETIME
|
| Explanation: Conversion of
OPAQUE to
DATETIME has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5224E
|
Cannot convert OPAQUE to binaries
|
| Explanation: Conversion of
OPAQUE to binary fields has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5225E
|
Cannot convert OPAQUE to any float
|
| Explanation: Conversion of
OPAQUE to floating point fields has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5226E
|
Cannot convert OPAQUE to BOOL
|
| Explanation: Conversion of
OPAQUE to
BOOL has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5227E
|
Cannot convert OPAQUE to IPPORT16
|
| Explanation: Conversion of
OPAQUE to
IPPORT16 has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5228E
|
Cannot convert OPAQUE to IPADDR32
|
| Explanation: Conversion of
OPAQUE to
IPADDR32 has failed.
User Response: Correct the recipe definition.
System Action: The Input field is not processed.
|
| SXT5229E
|
Cannot convert UNSIGN-PACK to IPADDR32
|
| Explanation: Conversion from Unsigned Packed to
IPADDR32 is not supported.
User Response: Correct the conversion rule.
System Action: The conversion is marked as error.
|
| SXT5230E
|
Cannot convert UNSIGN-ZDEC to IPADDR32
|
| Explanation: Conversion from Unsigned Packed to
IPADDR32 is not supported.
User Response: Correct the conversion rule.
System Action: The conversion is marked as error.
|
| SXT5231E
|
OPAQUE cannot be zero length
|
| Explanation: The source field in the buffer resolved to a zero length, which is not supported in an
OPAQUE field type.
User Response: Correct the conversion rule or data.
System Action: The conversion is marked as error.
|
| SXT5306E
|
Required and not found
|
| Explanation: The field is defined in the recipe as required but is not in the input message.
User Response: Review the recipe definition.
System Action: The remainder of the fields in the message are processed and then the message is rejected.
|
| SXT5309E
|
Required and not found
|
| Explanation: The field is defined in the recipe as required but is not in the input message.
User Response: Review the recipe definition.
System Action: The remainder of the fields in the message are processed and then the message is rejected.
|
| SXT5319E
|
Addfield failed
|
| Explanation: While constructing an output message, a messaging API call failed.
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: The field is not added to message.
|
| SXT5324E
|
Field must be type RVMSG
|
| Explanation: The recipe step defines the field as
RVMSG but the input message field is of some other type.
User Response: Review the recipe definition.
System Action: Processing of the message terminates.
|
| SXT5325E
|
SubMsg create failed
|
| Explanation: While processing an output message with embedded submessages, a call to API
Func to create a submessage failed.
Func:
tibrvMsg_Create for Rendezvous message,
tibemsMapMsg_Create, or
tibemsStreamMsg_Create for EMS message
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: Processing of the submessage terminates.
|
| SXT5328I
|
For CICS: U-Trc(RR) UoW:uow-number Task:task-number Idx:idx-number TID:Token-Id
For IMS: U-Trc(RR) UoW:number TID:Token-Id
|
Explanation: While processing an outbound back-end request/reply message, this message is produced if trigger trace level is 2 or greater.
- uow-number is the unit of work ID assigned to this message.
- task-number is the CICS task number generating the message.
- idx-number is the CICS request/reply slot being used.
- token-id is the value for tibss-envelope.
User Response: Review the log for information on the request/reply process that might be of use for debugging.
System Action: Processing continues.
|
| SXT5330E
|
Invalid Optional Special field
|
| Explanation: A special field defined in the recipe is not in the message. Though optional, that field is not a valid special field for input.
User Response: Review the recipe definition.
System Action: The remaining fields in the message are processed and then the message is rejected.
|
| SXT5333E
|
SubMsg AddMsg failed
|
| Explanation: While processing an output message with embedded sub-messages, a call to API Func for a sub-message failed.
Func:
tibrvMsg_AddMsg for Rendezvous message,
tibemsMapMsg_SetMapMsg,
tibemsMapMsg_SetStreamMsg,
tibemsStreamMsg_WriteMapMsg, or
tibemsStreamMsg_WriteStreamMsg functions for EMS message
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: Processing of the submessage terminates.
|
| SXT5334W
|
SubMsg Destroy failed
|
| Explanation: While processing an output message with embedded submessages, the
tibrvMsg_Destroy function for a submessage failed.
User Response: Contact TIBCO Support.
System Action: Processing continues.
|
| SXT5342E
|
Invalid Optional Special field
|
| Explanation: A Special field defined in the recipe is not in the message. Though optional, that field is not a valid special field for input.
User Response: Review the recipe definition.
System Action: The remaining fields in the message are processed and then the message is rejected.
|
| SXT5343E
|
Invalid Attributes
|
| Explanation: An input special field is not of the correct type or size.
User Response: Review the recipe definition.
System Action: The remaining fields in the message are processed and then the message is rejected.
|
| SXT5344E
|
Special Field not for Input
|
| Explanation: An input special field is not of the correct type or size.
User Response: Review the recipe definition.
System Action: The remaining fields in the message are processed and then the message is rejected.
|
| SXT5346E
|
Special Field not for Input
|
| Explanation: A special field that is defined in an input conversion cannot be an input field.
User Response: Review the recipe definition.
System Action: The remaining fields in the message are processed and then the message is rejected.
|
| SXT5347E
|
Add Envelope failed
|
| Explanation: While constructing an outbound message, the recipe requested the special field Envelope.
Func failed.
Func:
tibrvMsg_AddOpaque for Rendezvous message,
tibemsMapMsg_SetBytes, or
tibemsStreamMsg_WriteBytes functions for EMS message
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: The field is not added to the message.
|
| SXT5348E
|
Add config id failed
|
| Explanation: While constructing an outbound message, the recipe requested the special field config ID.
Func failed.
Func:
tibrvMsg_AddString for Rendezvous message,
tibemsMapMsg_SetString, or
tibemsStreamMsg_WriteString functions for EMS message
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: The field is not added to the message.
|
| SXT5349E
|
Add SS-id failed
|
| Explanation: While constructing an outbound message, the recipe requested the special field SS-id.
Func failed.
Func:
tibrvMsg_AddString for Rendezvous message,
tibemsMapMsg_SetString, or
tibemsStreamMsg_WriteString functions for EMS message
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: The field is not added to the message.
|
| SXT5350E
|
Spec Fld not for output
|
| Explanation: While constructing an outbound message, the recipe requested a Special field that cannot be used for output.
User Response: Review the recipe or trigger definition.
System Action: The field is not added to the message.
|
| SXT5351E
|
Add Envelope by bit failed
|
| Explanation: While constructing an outbound message, a bit setting requested the special field Envelope.
Func failed.
Func:
tibrvMsg_AddOpaque for Rendezvous message,
tibemsMapMsg_SetBytes, or
tibemsStreamMsg_WriteBytes functions for EMS message
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: The field is not added to the message.
|
| SXT5365E
|
F-Name Input Bytes size
size greater than buffer
bufsize
|
|
Explanation: In an EMS Bytes message, the data included is larger than the receiving buffer.
User Response: Correct the recipe or input message.
System Response: Transaction is rejected with an error message.
|
| SXT5406E
|
No destination for output
|
| Explanation: While sending a response message, the reply failed and no response subject was specified.
User Response: Specify one or more output destinations.
System Action: This error is added to the error submessage. The entire response message is sent to the error subject, if specified.
|
| SXT5414E
|
Msg_Detach failed
|
| Explanation: The call to
tibrvMsg_Detach has failed.
User Response: Contact TIBCO Support.
System Action: Processing of this message is terminated and responses are sent.
|
| SXT5416E
|
No thread specific info found
|
| Explanation: The call to
pthread_getspecific has returned a
null pointer.
User Response: Contact TIBCO Support.
System Action: Processing of this message is terminated and responses are sent.
|
| SXT5418E
|
No open entry in UOW list
|
| Explanation: No UOW entry is available to process with this message.
User Response: Enlarge the UOW list or slow the pace of input.
System Action: Processing of this message is terminated and responses are sent.
|
| SXT5423E
|
Failure in UOW Storage request
|
| Explanation: No user area is available to service this message.
User Response: Contact TIBCO Support.
System Action: Processing of this message is terminated and responses are sent.
|
| SXT5431E
|
Backend interface:
Applid not responding Rsn:
RSN
|
| Explanation: The nonzero return code
RSN is sent to
QandDispatch_Work.
User Response: Contact TIBCO Support.
System Action: Processing of this message is terminated and responses are sent.
|
| SXT5445E
|
BES data size less than required CFGID data size
|
| Explanation: During the processing of a trigger, the user data area in the COMMAREA was found to be smaller than the buffer size defined in the configuration file.
User Response: Adjust the buffer sizes in the configuration file and ensure that
TRIG-MAXSIZE in the CICS Interface parameters file is large enough.
System Action: Processing of this message is terminated and responses are sent.
|
| SXT5464E
|
BES RC
RC rsn
RSN Unknown failure
|
| Explanation: The back-end processor has returned code
RC with reason code
RSN.
User Response: Review the definition of the back-end processor.
System Action: Processing of this message is terminated and responses are sent.
|
| SXT5476E
|
Create Msg failed rc
RC
|
| Explanation: While processing a trigger, the call to
Func failed with return code
RC.
Func:
tibrvMsg_Create for Rendezvous message or
tibemsMapMsg_Create for EMS message
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: Processing of the trigger’s definition terminates.
|
| SXT5480E
|
Create Msg failed rc
RC
|
| Explanation: The call to
Func failed with return code
RC.
Func:
tibrvMsg_Create for Rendezvous message or
tibemsMapMsg_Create for EMS message
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
System Action: Processing of this message is terminated and responses are sent.
|
