z/OS CICS TDC Messages and Codes › Message Descriptions

Message Descriptions

TITD001E Invalid MQSeries Trigger Record - Execution Terminated

Reason:

The trigger record retrieved contains invalid data. The task abends with code TDR.

Action:

Verify that the TDC (TITD transaction) was started by the MQS trigger monitor transaction, or another TDC. If it was, save the transaction dump, and contact Technical Support.

TITD201E Unable to Obtain Trigger Record - Execution Terminated

Reason:

The retrieve of the trigger record failed. Message TITD299I follows this message showing the failing command and return codes, and the task abends with code TDTR.

Action:

Verify that the TCD (TITD transaction) was started by the MQS trigger monitor transaction, or another TDC. If it was, note the failing command and return codes, save the transaction dump, and contact Technical Support.

TITD202W User Exit TIRMQTDX Not Found - Continuing With Default Parameters

Reason:

TIRMQTDC was unable to load the user exit TIRMQTDX. Message TITD299I follows this message with the failing command and return codes. Processing continues using the default values.

Action:

Generally, none. If you coded TIRMQTDX, verify that the program is defined to CICS and available in DFHRPL. Use the information in the accompanying message TITD299I to determine the cause of the failure.

TITD203E Unable to Obtain Buffer Storage - Execution Terminated

Reason:

TIRMQTDC was unable to obtain dynamic CICS storage for processing. Message TITD299I follows this message with the failing command and return codes. The task abends with code TDST.

Action:

Verify that sufficient DSA storage is available to the task. If so, note the failing command and return codes, save the transaction dump, and contact Technical Support.

TITD204E Slowdown Delay Value Invalid - Continuing to Process

Reason:

The task has entered slowdown mode, but CICS has rejected the delay value. Processing continues with slowdown mode effectively nullified. Message TITD299I follows this message with the failing command and return codes.

Action:

If you are overriding the slowdown delay with TIRMQTDX, verify that the value supplied is valid. Otherwise, note the failing return codes, and contact Technical Support.

TITD205E Unable to Write Temporary CFB - Server Manager Not Started

Reason:

A failure occurred while attempting to write the message to the selected temporary storage medium. A 619 “Unknown server error” is returned to the requester and processing continues. Message TITD299I follows this message with the failing command and return codes.

Action:

Verify that the selected temporary storage medium is available and has sufficient resources available. Verify that the messages being sent by the requester do not exceed 32KB in length. Otherwise, note the failing command and return codes, and contact Technical Support.

TITD206E Server Manager Start Failed - Unable to Process Message

Reason:

An attempt to start the server manager indicated in the message failed. A 619 “Unknown server error” is returned to the requester, and processing continues. Message TITD299I follows this message showing the failing command and return codes.

Action:

Use the accompanying TITD299I message to determine the cause of the failure. Ensure that proper authorization was granted to the TDC. Otherwise, note the failing command and return codes, and contact Technical Support.

TITD207W Unable to Issue Inquire - Bypassing System Status Processing

Reason:

An attempt to obtain CICS system statistics has failed. Processing continues with slowdown mode nullified. Message TITD299I follows this message showing the failing command and return codes.

Action:

Use the accompanying TITD299I message to determine the cause of failure. Ensure that proper authorization was granted to the TDC. Otherwise, note the failing command and return codes, and contact Technical Support.

TITD299I Exec CICS xxxxxxxx Failed EIBRESP = nnnn EIBRESP2= nnnn

Reason:

This message is produced along with TITD2nnx messages. It indicates the failing CICS command ( xxx ...) along with the EIBRESP and EIBRESP2 fields ( nnnn ) in decimal format.

Action:

See the associated TITD2nnx message.

TITD301W MQSeries Queue Not Shareable - Multi-Processing Disabled

Reason:

The MQSeries queue being processed is marked non-shareable. Processing continues, but no additional TDC processes will be spawned, regardless of their queue depth.

Action:

If multi-processing is desired for this queue, redefine it with the shareable attribute.

TITD302W MQSeries Trigger Type Not EQ FIRST or EVERY - Multiprocessing Disabled

Reason:

The MQSeries queue being processed is using a trigger type other than FIRST or EVERY. Processing continues, but no additional TDC processes will be spawned, regardless of their queue depth.

Action:

If multi-processing is desired for this queue, redefine it with triggering set to FIRST or EVERY.

TITD303I MQSeries Connect to Queue Manager Failed - Processing Continues

Reason:

An attempt to connect to the MQSeries queue manager has failed. Since CICS is connected to a queue manager by default, processing continues and an open for the queue is attempted. Message TITD399I follows this message showing the failing command and return codes.

TITD304E MQSeries Open Failed for Input Queue - Processing Terminated

Reason:

An attempt to open the MQSeries queue has failed. The task abends with code TDMQ. Message TITD399I follows this message showing the failing command and return codes.

Action:

Verify that MQSeries was active and available at the time of the failure. If so, note the failing command and return codes, save the transaction dump, and contact Technical Support.

TITD305W MQSeries Inquire Failed for Input Queue - Multi-Processing Disabled

Reason:

The TDC was unable to obtain MQSeries status for the queue. Processing continues, but no additional TDC processes will be spawned regardless of the queue depth. Message TITD399I follows this message showing the failing command and return codes.

Action:

Verify that the TDC is properly authorized to perform this function. Otherwise, note the failing command and return codes, save the transaction dump, and contact Technical Support.

TITD306E MQSeries Get Failed for Input Queue - Processing Terminated

Reason:

An attempt to read the MQSeries queue has failed. The task abends with code TDMQ. Message TITD399I follows this message showing the failing command and return codes.

Action:

Verify that MQSeries was active and available at the time of the failure. If so, note the failing command and return codes, save the transaction dump, and contact Technical Support.

TITD307W MQSeries Put Failed for Reply To Queue - Unable to Notify Client of Server Failure

Reason:

The TDC attempted to reply to the requester directly and that reply has failed. Message TITD299I follows this message showing the failing command and return codes. Processing continues, but the requester is notified of the failure that precipitated this action.

Action:

Verify that MQSeries was active and available at the time of the failure. If so, note the failing command and return codes, save the transaction dump, and contact Technical Support.

TITD308W MQSeries Get Received Invalid Message Buffer - Message Bypassed

Reason:

MQSeries reported an invalid message to the TDC. The message is bypassed and processing continues. Message TITD299I follows this message showing the failing command and return codes.

Action:

Ensure that no non-CA Gen messages are posted to this queue, and that no messages exceed a size of 32KB. Otherwise, note the failing command and return codes, and contact Technical Support.

TITD309E MQSeries Get Warning Threshold Exceeded - Processing Terminated

Reason:

MQSeries reported five consecutive invalid messages to the TDC. The task abends with code TDMQ. Message TITD299I follows this message showing the failing command and return codes.

Action:

Ensure that no non-CA Gen messages are posted to this queue, and that no messages exceed a size of 32KB. Otherwise, note the failing command and return codes, save the transaction dump, and contact Technical Support.

TITD301E MQSeries Close Failed For Input Queue - Processing Terminated

Reason:

An attempt to close the queue has failed. The task abends with code TDMQ. Message TITD299I follows this message showing the failing command and return codes.

Action:

Verify that MQSeries was active and available at the time of the failure. If so, note the failing command and return codes, save the transaction dump, and contact Technical Support.

TITD311E Unable to Set Triggering - Verify Security for TITD

Reason:

An attempt to set triggering for the queue has failed. Processing continues. Message TITD399I follows this message showing the failing command and return codes.

Action:

Verify that proper authorization was granted to the TITD transaction. Otherwise contact Technical Support.

TITD399I MQSeries Call xxxx Failed CC= nnnn RC= nnnn

Reason:

This message is produced along with TITD3nnx messages. It indicates the failing MQSeries call ( xxx ...), along with the condition and return code fields ( nnnn ) in decimal format.

Action:

See the associated TITD3nnx message.

TITD998I Transaction Dispatcher Completed Normally - Statistics Follow

Reason:

An instance of the TDC completed normally. A statistical summary is printed for the task under message TITD999I.

TITD999I

This ID represents one of the following messages:

Task: nnnn MQS Queue Name: xxxx

Reason:

The TDC task number nnnn completed using MQSeries queue xxxx .

Task: nnnn Messages Processed: mmmm Server Managers Started: ssss

Reason:

The TDC task number nnnn completed, processing mmmm messages and starting ssss server managers.

Task: nnnn Server Managers Errors: eeee Times Slowdown Entered: dddd

Reason:

The TDC task number nnnn completed, observing eeee server manager errors and entering slowdown mode dddd times.

Task: nnnn TDCS Spawned By This Task: tttt Max Observed Queue Depth: qqqq

Reason:

The TDC task number nnnn completed, and tttt additional TDCs were spawned by this task. The maximum observed queue depth was qqqq. This message appears only for the parent task.