Micro Focus Enterprise Developer 3.0 for Visual Studio 2013
>
Deployment
>
Configuration and Administration
>
Enterprise Server Reference
>
Error Messages
>
Enterprise Server Error Messages
>
CASMQ Error Messages
>
CASMQ1001 - CASMQ1009
CASMQ1001 - CASMQ1009
CASMQ1001I Connection to WebSphere MQ re-established.
The WebSphere MQ trigger monitor program (CKTI) has re-established the connection to the MQ server. CKTI will continue triggering transactions.
CASMQ1002E Connection to WebSphere MQ lost, RC = reason-code, retrying...
The WebSphere MQ trigger monitor program (CKTI) has lost the connection to the MQ server. CKTI will retry to connect in the background.
CASMQ1003E Failed to start transaction transaction from CKTI
The WebSphere MQ trigger monitor program (CKTI) has failed to start the CICS transaction specified from the initiation queue message process definition.
CASMQ1004E Unexpected error reason from MQGET in CKTI, RC = reason-code
The WebSphere MQ trigger monitor program (CKTI) has received an unexpected reason code from a MQGET API call.
CASMQ1005E Unable to start trigger transaction trans-id, reason = reason-code
The WebSphere MQ trigger monitor program (CKTI) could not start the transaction defined in the WebSphere MQ trigger process definition. The transaction may not be defined to the local system.
CASMQ1006E Unexpected message format (msg-format) on MQGET in CKTI
The WebSphere MQ trigger monitor program (CKTI) was expecting a trigger message (MQFMT-TRIGGER) but received an unexpected format.
CASMQ1007E Unexpected application type (appltype) on MQGET in CKTI
The WebSphere MQ trigger monitor program (CKTI) was expecting an application type of CICS (MQAT-CICS) but received an unexpected appltype.
CASMQ1008I IMS Trigger Monitor initialization completed
The IMS WebSphere MQ Trigger Monitor successfully initialized.
CASMQ1009I IMS Trigger Monitor is ready, initiation queue: initiation-queue-name
The IMS WebSphere MQ Trigger Monitor is ready to process user requests.
Parent topic:
CASMQ Error Messages
