IMS adapter messages (CSQQ...)

IMS/TM iiii connected to queue manager qqqq

This message is produced at the IMS master terminal when the IMS control region for IMS system iiii has successfully connected to queue manager qqqq.

IMS/TM iiii not connected to queue manager qqqq. Notify message accepted

This message is produced at the IMS master terminal when the IMS control region for IMS system iiii has tried to connect to queue manager qqqq but the queue manager is not yet ready to make connections.

The queue manager has accepted the notify message from IMS and when it is ready to make connections it will issue the z/OS® command MODIFY IMS to cause IMS to attempt to make the connection again. IMS applications cannot access IBM® MQ resources until the connection is made.

Resolve any other IBM MQ problems.

IMS/TM iiii failed to connect to queue manager qqqq, MQRC=mqrc

This message is produced at the IMS master terminal when the IMS control region for IMS system iiii has failed to connect to queue manager qqqq. mqrc is the IBM MQ reason code for the failure.

The IMS control region, and dependent regions are not connected to the queue manager. Any request from IMS applications for IBM MQ resources will fail.

Refer to API completion and reason codes for information about mqrc to determine the nature of the error.

IMS/TM iiii create thread failed while connecting to queue manager qqqq, MQRC=mqrc

This message is produced at the IMS master terminal when the IMS control region for IMS system iiii has failed to connect to queue manager qqqq. mqrc is the IBM MQ reason code for the failure from theIBM MQ create thread function.

The IMS control region, and dependent regions are not connected to the queue manager. Any request from IMS applications for IBM MQ resources will fail.

Refer to API completion and reason codes for information about mqrc to determine the cause of the problem.

IMS/TM iiii inquire indoubt failed while connecting to queue manager qqqq, MQRC=mqrc

This message is produced at the IMS master terminal when the IMS control region for IMS system iiii has failed to connect to queue manager qqqq. mqrc is the IBM MQ reason code for the failure from the IBM MQ inquire indoubt function.

The IMS control region, and dependent regions are not connected to the queue manager. Any request from IMS applications for IBM MQ resources will fail.

Refer to API completion and reason codes for information about mqrc to determine the nature of the error.

IMS/TM iiii establish exit failed while connecting to queue manager qqqq, MQRC=mqrc

This message is produced at the IMS master terminal when the IMS control region for IMS system iiii has failed to connect to queue manager qqqq. mqrc is the IBM MQ reason code for the failure from IBM MQ establish exit function.

The IMS control region, and dependent regions are not connected to the queue manager. Any request from IMS applications for IBM MQ resources will fail.

Refer to API completion and reason codes for information about mqrc to determine the cause of the error.

IMS/TM iiii resolve indoubt failed while connecting to queue manager qqqq, MQRC=mqrc

This message is produced at the IMS master terminal when the queue manager has failed to resolve indoubt units of recovery during the connection process. mqrc is the IBM MQ reason code for the resolve in-doubt function failure.

The IMS control region, and dependent regions are connected to the queue manager. IMS applications can access IBM MQ resources.

For information about resolving the IBM MQ unit of recovery associated with the in-doubt IMS unit of work, see Recovering IMS units of recovery manually.

nn units of recovery are still in doubt in queue manager qqqq

This message is produced at the IMS master terminal when the queue manager has units of recovery still in doubt after all the IMS units of work have been resolved.

The IMS control region, and dependent regions are connected to the queue manager. IMS applications can access IBM MQ resources.

See How in-doubt units of recovery are resolved from IMS for information about resolving the IBM MQ unit of recovery associated with the in-doubt IMS unit of work.

Error resolving unit of recovery uuuu (OASN nnnn) in queue manager qqqq, MQRC=mqrc

This message is produced at the IMS master terminal when the queue manager is unable to resolve an indoubt unit of recovery. uuuu is the unit of work identifier in the same format as the reply from the DISPLAY THREAD command. nnnn is the IMS OASN (origin application sequence number), in decimal format.

The IMS control region, and dependent regions are connected to the queue manager. IMS applications can access IBM MQ resources.

See the How in-doubt units of recovery are resolved from IMS for information about resolving the IBM MQ unit of recovery associated with the in-doubt IMS unit of work.

IMS/TM iiii terminate identify failed for connection to queue manager qqqq, MQRC=mqrc

This message is produced at the IMS master terminal when the IMS control region for IMS system iiii has failed to disconnect from the queue manager qqqq. mqrc is the return code for the failure from the IBM MQ terminate identify function.

The IMS control region, and dependent regions are not connected to the queue manager. Any request from IMS applications for IBM MQ resources will fail.

Refer to API completion and reason codes for information about mqrc to determine the cause of the error.

MQ commands cannot be issued using the /SSR command

This message is produced at the IMS master terminal when the /SSR IMS command is used to issue an IBM MQ command; IBM MQ commands cannot be issued in this way.

None

Unit of recovery uuuu (OASN nnnn) was not committed in queue manager qqqq

This message is produced at the IMS master terminal when, following the abnormal termination of an application, the queue manager is unable to commit an indoubt unit of recovery as requested by IMS. uuuu is the unit of work identifier in the same format as the reply from the DISPLAY THREAD command. nnnn is the IMS OASN (origin application sequence number), in decimal format.

The IMS control region, and dependent regions are connected to the queue manager. IMS applications can access IBM MQ resources.

See How in-doubt units of recovery are resolved from IMS for information about resolving the IBM MQ unit of recovery associated with the in-doubt IMS unit of work.

Unit of recovery uuuu (OASN nnnn) was not backed out in queue manager qqqq

This message is produced at the IMS master terminal when, following the abnormal termination of an application, the queue manager is unable to back out an indoubt unit of recovery as requested by IMS. uuuu is the unit of work identifier in the same format as the reply from the DISPLAY THREAD command. nnnn is the IMS OASN (origin application sequence number), in decimal format.

The IMS control region, and dependent regions are connected to the queue manager. IMS applications can access IBM MQ resources.

See How in-doubt units of recovery are resolved from IMS for information about resolving the IBM MQ unit of recovery associated with the in-doubt IMS unit of work.

psb-name region-id Processing queue manager name

This message identifies the queue manager that this instance of the IMS trigger monitor is connected to. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQQ110I, indicating the name of the initiation queue.

psb-name region-id Cannot open the initiation queue, MQCC=mqcc MQRC=mqrc

CSQQTRMN has attempted to open an initiation queue, but the attempt was unsuccessful (for example, because the queue was not defined). mqcc and mqrc give the reason for the problem. region-id is the last four digits of the region identifier, or blank.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc, determine the cause of the problem, and restart CSQQTRMN.

psb-name region-id An IMS dl1-function call returned pcb-status

A trigger message has been retrieved from the initiation queue which defines an IMS transaction to be started. However, the transaction cannot be started (for example, it cannot be found). region-id is the last four digits of the region identifier, or blank. pcb-status is the status code returned by IMS from the last dl1-function call.

The trigger message is sent to the dead-letter queue. CSQQTRMN processes the next message.

See the IMS/ESA® Application Programming: Data Communication manual for information about pcb-status. Examine the trigger message on the dead-letter queue to find the IMS transaction name. Determine the reason for the problem, and restart the transaction.

psb-name region-id CSQQTRMN read a trigger message with an incorrect MQTM-StrucId of struc-id

A trigger message has been retrieved, but the structure identifier of the message is not MQTM_STRUC_ID and so is not compatible with this version of CSQQTRMN. region-id is the last four digits of the region identifier, or blank.

The trigger message is sent to the dead-letter queue. CSQQTRMN processes the next message.

Check the header of the message on the dead-letter queue. This will tell you where the trigger message came from. Correct the process that created the trigger message.

psb-name region-id CSQQTRMN does not support version version

A trigger message has been retrieved, but the version identifier in MQTM is not version 1, and so is not compatible with this version of CSQQTRMN. region-id is the last four digits of the region identifier, or blank.

The trigger message is sent to the dead-letter queue. CSQQTRMN processes the next message.

Check the header of the message on the dead-letter queue. This will tell you where the trigger message came from. Correct the process that created the trigger message.

psb-name region-id CSQQTRMN cannot start a process type of type

A trigger message has been retrieved, but the process type in MQTM is not IMS, and so cannot be processed by this version of CSQQTRMN. region-id is the last four digits of the region identifier, or blank.

The trigger message is sent to the dead-letter queue. CSQQTRMN processes the next message.

Check the header of the message on the dead-letter queue. This will tell you where the trigger message came from. Correct the process that created the trigger message.

psb-name region-id MQGET error, MQCC=mqcc MQRC=mqrc. CSQQTRMN will end

An attempt to issue an MQGET call on the initiation queue has been unsuccessful. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQQ110I, indicating the name of the queue.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem. Restart CSQQTRMN.

psb-name region-id Cannot connect to the queue manager, MQCC=mqcc MQRC=mqrc

An attempt by the trigger monitor to connect to the queue manager identified in message CSQQ100I was unsuccessful. region-id is the last four digits of the region identifier, or blank.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.

psb-name region-id LTERM lterm-name not available. Switched to MASTER

The LTERM specified to receive diagnostic messages cannot be used.

Messages are sent to the master terminal.

Resolve why lterm-name was not available.

psb-name region-id MQCLOSE error, MQCC=mqcc MQRC=mqrc

An attempt has been made to close a dead-letter queue, but the MQCLOSE call was unsuccessful. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQQ110I, indicating the name of the queue.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.

Queue name = q-name

This message follows other messages and identifies the name of the queue in question. The accompanying messages indicate the event or problem associated with the queue.

psb-name region-id CSQQTRMN read a trigger message with an incorrect length of length

This message is issued if the transaction CSQQTRMN receives a trigger message that does not match the MQTM control block. region-id is the last four digits of the region identifier, or blank.

The message is sent to the dead-letter queue.

Look at the message on the dead-letter queue to establish why it did not match MQTM.

psb-name region-id MQOPEN error, MQCC=mqcc MQRC=mqrc

An MQOPEN call has been unable to open a queue. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQQ110I indicating the name of the queue.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.

psb-name region-id This message cannot be processed

When an attempt to process a message using an IBM MQ API call was unsuccessful, an attempt was made to put the message on the dead-letter queue. This was also unsuccessful and the message-id has been sent to the LTERM. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQ118I, indicating the message identifier.

Processing continues.

Check for previous messages explaining why the dead-letter queue was not available (if a dead-letter queue has not been defined, no other messages relating to the problem will have been issued).

psb-name region-id MQINQ error, MQCC=mqcc MQRC=mqrc

An attempt to use the MQINQ call to inquire about the attributes of a queue was unsuccessful. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQQ110I indicating the name of the queue.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine why an MQINQ call could not be made on the queue.

psb-name region-id Ending following termination of queue manager connection

CSQQTRMN has terminated because the connection to the queue manager is no longer available.

psb-name region-id Cannot open the queue manager, MQCC=mqcc MQRC=mqrc

An MQOPEN call to the queue manager was unsuccessful. region-id is the last four digits of the region identifier, or blank.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.

psb-name region-id Cannot query the queue manager, MQCC=mqcc MQRC=mqrc

An MQINQ call to the queue manager was unsuccessful. region-id is the last four digits of the region identifier, or blank.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.

MsgID=msg-id

This message follows message CSQQ113I, indicating the hexadecimal identifier of the message that could not be processed.

psb-name region-id Error rc from STORAGE OBTAIN

CSQQTRMN tried to obtain storage, but received return code rc from z/OS.

CSQQTRMN ends.

Determine the reason for the return code from the STORAGE OBTAIN request, and restart CSQQTRMN.

psb-name region-id MQPUT error, MQCC=mqcc MQRC=mqrc

An attempt was made to put a message on a queue with an MQPUT call, but the attempt was unsuccessful. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQQ110I indicating the name of the queue.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine why an MQPUT call could not be made for the queue.

psb-name region-id Dead-letter queue is not defined for the queue manager

A dead-letter queue has not been defined for the queue manager. region-id is the last four digits of the region identifier, or blank.

The trigger message is discarded, and the process cannot be started.

Define a dead-letter queue if one is required.

psb-name region-id Cannot close the queue manager, MQCC=mqcc MQRC=mqrc

CSQQTRMN was unable to close the queue manager after inquiring about the dead-letter queue. region-id is the last four digits of the region identifier, or blank.

CSQQTRMN ends.

Refer to API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.

psb-name region-id The dead-letter queue type is not QLOCAL

The dead-letter queue defined was not of type local. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQQ110I, indicating the name of the queue.

The message is not put to the dead-letter queue.

Define the dead-letter queue as a local queue.

psb-name region-id The dead-letter queue usage is not NORMAL

The dead-letter queue defined is not of usage type normal. region-id is the last four digits of the region identifier, or blank. This message is followed by message CSQQ110I, indicating the name of the queue.

The message is not put to the dead-letter queue.

Define the dead-letter queue to have usage type normal.

psb-name region-id No initiation queue identified

CSQQTRMN did not find the initiation queue name in the input parameters.

CSQQTRMN ends.

Examine the input parameters and look for other error messages to determine the reason for the failure. Restart CSQQTRMN.

psb-name region-id An IMS call call returned pcb-status

A status code of pcb-status was returned from a DLI call.

CSQQTRMN ends.

Determine the reason for the status code, and restart CSQQTRMN.

csect-name IBM WebSphere® MQ for z/OS Vn

This message is issued as part of the header to the report issued by the IMS trigger monitor program.

csect-name Trigger Monitor Input Report - date time

This message is issued as part of the header to the report issued by the IMS trigger monitor program.

csect-name Unable to OPEN CSQQUT1 data set

The IMS trigger monitor was unable to open the data set containing input control statements.

Default values are used for the options.

Examine the error message that has been sent to the JES log to determine the reason for the error. Check that the data set has been correctly specified.

csect-name First token is not a valid keyword

The input control statement does not start with a valid keyword.

The statement is ignored.

Correct the syntax for the statement.

csect-name Trigger monitor options:

The IMS trigger monitor has finished processing input control statements. The options that will be used follow.