CASMQ error messages
- CASMQ1001I Connection to MQ series re-established.
- The MQSeries trigger monitor program (CKTI) has re-established the connection to the MQ server. CKTI will continue triggering transactions
- System action: None
- User response: None
- Destination: Console
- Module: dfhtmqgw
- CASMQ1002E Connection to MQ series lost, RC =
reason-code, retrying...
- The MQSeries trigger monitor program (CKTI) has lost the connection to the MQ server. CKTI will retry to connect in the background
- System action: None
- User response: None
- Destination: Console
- Module: dfhtmqgw
- CASMQ1003E Failed to start transaction
transaction from CKTI
- The MQSeries trigger monitor program (CKTI) has failed to start the CICS transaction specified from the initiation queue message process definition.
- System action: None
- User response: None
- Destination: Console
- Module: dfhtmqgw
- CASMQ1004E Unexpected error reason from MQGET in CKTI, RC =
reason-code
- The MQSeries trigger monitor program (CKTI) has received an unexpected reason code from a MQGET API call.
- System action: None
- User response: None
- Destination: Console
- Module: dfhtmqgw
- CASMQ1005E Unable to start trigger transaction
trans-id, reason =
reason-code
- The MQSeries trigger monitor program (CKTI) could not start the transaction defined in the MQSeries trigger process definition. The transaction may not be defined to the local system.
- System action: No transaction will be started.
- User response: Make sure that the transaction is defined correctly within the MQSeries process definition and is defined as a local transaction to the CICS region
- Destination: Console
- Module: dfhtmqgw
- CASMQ1006E Unexpected message format (msg-format) on MQGET in CKTI
- The MQSeries trigger monitor program (CKTI) was expecting a trigger message (MQFMT-TRIGGER) but received an unexpected format.
- System action: Trigger transaction will not be started.
- User response: Check the MQSeries Process definition.
- Destination: Console
- Module: dfhtmqgw
- CASMQ1007E Unexpected application type (appltype) on MQGET in CKTI
- The MQSeries trigger monitor program (CKTI) was expecting an application type of CICS (MQAT-CICS) but received an unexpected appltype.
- System action: Trigger transaction will not be started.
- User response: Check the MQSeries Process definition.
- Destination: Console
- Module: dfhtmqgw
- CASMQ1008I IMS Trigger Monitor initialization completed
- The IMS MQSeries Trigger Monitor successfully initialized
- System action: None
- User response: None
- Destination: Console
- Module: csq4trmn
- CASMQ1009I IMS Trigger Monitor is ready, initiation queue:
initiation-queue-name
- The IMS MQSeries Trigger Monitor is ready to process user requests
- System action: None
- User response: None
- Destination: Console
- Module: csq4trmn
- CASMQ1010I IMS Trigger Monitor terminated
- The IMS MQSeries Trigger Monitor terminated
- System action: None
- User response: None
- Destination: Console
- Module: csq4trmn
- CASMQ1011E Unexpected error while connecting to queue manager
queue-manager-name in IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor received an error trying to connect to the Queue Manager
- System action: The IMS Trigger Monitor is terminated
- User response: Ensure that the Queue Manager in the Trigger Monitor startup JCL is correct
- Destination: Console
- Module: csq4trmn
- CASMQ1012E Unexpected error while opening initiation queue
initiation-queue-name in IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor received an error trying to open the initiation queue
- System action: The IMS Trigger Monitor is terminated
- User response: Ensure that the initiation queue in the Trigger Monitor startup JCL is correct and that the initiation queue has been defined
- Destination: Console
- Module: csq4trmn
- CASMQ1013E Unexpected error while getting message from the initiation queue
initiation-queue-name in IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor received an error retrieving a message token from the initiation queue that is being monitored
- System action: The message token on the initiation queue will not be processed
- User response: Check the completion and reason code to determine the cause of the error displayed in the message
- Destination: Console
- Module: csq4trmn
- CASMQ1014E Unexpected error while closing initiation queue
initiation-queue-name in IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor could not close the initiation queue during termination
- System action: None
- User response: Check the completion and reason code to determine the cause of the error
- Destination: Console
- Module: csq4trmn
- CASMQ1015E Unexpected error while disconnecting from queue manager
queue-manager-name in IMS Trigger Monitor, status:
status-code
- An error was received during termination when the IMS Trigger Monitor attempted to disconnect from the Queue Manager
- System action: None
- User response: Check the completion and reason code to determine the cause of the error
- Destination: Console
- Module: csq4trmn
- CASMQ1016E Unexpected application type
appltype on MQGET in IMS Trigger Monitor
- The IMS MQSeries Trigger Monitor was expecting an application type of IMS (MQAT-IMS) but received an unexpected appltype.
- System action:The transaction specified in the MQSeries process definition will not be started.
- User response: Check the MQSeries Process definition.
- Destination: Console
- Module: csq4trmn
- CASMQ1017E Unexpected MQ message version
message-version in IMS Trigger Monitor
- The IMS MQSeries Trigger Monitor program (CSQ4TRMN) was expecting an MQ message version 1 (MQTM-VERSION-1) but received an unexpected version.
- System action: Trigger transaction will not be started.
- User response: Check the MQSeries Process definition.
- Destination: Console
- Module: csq4trmn
- CASMQ1018E Unexpected MQ message structid
mqtm-strucid in IMS Trigger Monitor
- The IMS MQSeries Trigger Monitor program (CSQ4TRMN) was expecting a message with mqtm strucid of (MQTM-STRUC-ID) but received an unexpected mqtm strucid.
- System action: Trigger transaction will not be started.
- User response: Check the MQSeries Process definition.
- Destination: Console
- Module: csq4trmn
- CASMQ1019E Unexpected error from IMS SYNC call, status code:
status-code
- An IMS SYNC issued by the IMS Trigger Monitor has failed.
- System action: None
- User response: Check the status code to determine the cause of the error
- Destination: Console
- Module: csq4trmn
- CASMQ1020E Unexpected error from IMS CHNG call, status code:status-code
- An IMS CHNG issued by the IMS Trigger Monitor has failed.
- System action: Trigger transaction will not be started
- User response: Check the status code to determine the cause of the error
- Destination: Console
- Module: csq4trmn
- CASMQ1021E Unexpected error from IMS ISRT call, status code:
status-code
- An IMS ISRT call issued by the IMS Trigger Monitor has failed.
- System action: Trigger transaction will not be started
- User response: Check the status code to determine the cause of the error
- Destination: Console
- Module: csq4trmn
- CASMQ1022E Unexpected error from IMS PURG call, status code:
status-code
- An IMS PURG call issued by the IMS Trigger Monitor has failed
- System action: None
- User response: Check the status code to determine the cause of the error
- Destination: Console
- Module: csq4trmn
- CASMQ1023I Missing queue manager name, will try using the default queue manager
- A MQSeries Queue Manager name was not specified in the IMS Trigger Monitor startup JCL
- System action: The IMS Trigger Monitor will try using the default queue manager
- User response: Specify a valid MQSeries Queue Manager name in the IMS Trigger Monitor startup JCL
- Destination: Console
- Module: csq4trmn
- CASMQ1024E Missing initiation queue name
- A MQSeries initiation queue name was not specified in the IMS Trigger Monitor startup JCL
- System action: The IMS Trigger Monitor is not started
- User response: Specify a valid MQSeries initiation queue name in the IMS Trigger Monitor startup JCL
- Destination: Console
- Module: csq4trmn
- CASMQ1025E Unexpected error while connecting to queue manager
queue-manager-name in the IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor received an error trying to connect to the Queue Manager
- System action: The IMS Trigger Monitor is not terminated
- User response: Ensure that the Queue Manager in the Trigger Monitor startup JCL is correct
- Destination: Console
- Module: csq4trmn
- CASMQ1026E Unexpected error while opening initiation queue
initiation-queue-name in the IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor received an error trying to open the initiation queue
- System action: The IMS Trigger Monitor is not terminated
- User response: Ensure that the initiation queue in the Trigger Monitor startup JCL is correct and that the initiation queue has been defined
- Destination: Console
- Module: csq4trmn
- CASMQ1027E Unexpected error while putting message into the initiation queue
initiation-queue-name in IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor received an error placing a message token into the initiation queue that is being monitored
- System action: The message token will not be placed into the initiation queue
- User response: Check the completion and reason code to determine the cause of the error displayed in the message
- Destination: Console
- Module: csq4trmn
- CASMQ1028E Unexpected error while closing initiation queue
initiation-queue-name in IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor could not close the initiation queue during termination
- System action: None
- User response: Check the completion and reason code to determine the cause of the error
- Destination: Console
- Module: csq4trmn
- CASMQ1029E
error-message
- An error message generated from the IMS Trigger Monitor
- System action: None
- User response: Check the error message and take appropriate action
- Destination: Console
- Module: csq4trmn
- CASMQ1030E Unexpected error while issuing MQCMIT call
queue-manager-name in IMS Trigger Monitor, status:
status-code
- The IMS Trigger Monitor could not successfully issue a call to commit the MQSeries trigger token message after invoking the end user IMS program
- System action: None
- User response: Check the completion and reason code to determine the cause of the error
- Destination: Console
- Module: csq4trmn
