IMS adapter messages (CSQQ...)

 

CSQQ000I

IMS/TM iiii connected to queue manager qqqq

Explanation:

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.

Severity:

0

CSQQ001I

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

Explanation:

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.

Severity:

0

System Action:

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 can not access MQ resources until the connection is made.

Operator Response:

Look for other errors in MQ that might prevent it becoming ready, and notify the system programmer.

System Programmer Response:

Resolve any other MQ problems.

Problem Determination:

You might find the following items useful in resolving the problem:

• Symptom string

• Printout of SYS1.LOGREC

• Queue manager job log

• PSW and registers at point of failure

• Copy of the IMS log

CSQQ002E

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

Explanation:

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 MQ reason code for the failure.

Severity:

12

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

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

Problem Determination:

You might find the following items useful in resolving the problem:

• Symptom string

• Printout of SYS1.LOGREC

• Queue manager job log

• Copy of the IMS log

CSQQ003E

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

Explanation:

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 MQ reason code for the failure from the MQ create thread function.

Severity:

12

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

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

Problem Determination:

You might find the following items useful in resolving the problem:

• Printout of SYS1.LOGREC

• Queue manager job log

• Copy of the IMS log

CSQQ004E

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

Explanation:

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 MQ reason code for the failure from the MQ inquire indoubt function.

Severity:

12

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

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

Problem Determination:

You might find the following items useful in resolving the problem:

• Printout of SYS1.LOGREC

• Queue manager job log

• Copy of the IMS log

CSQQ005E

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

Explanation:

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 MQ reason code for the failure from MQ establish exit function.

Severity:

12

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

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

Problem Determination:

You might find the following items useful in resolving the problem:

• Printout of SYS1.LOGREC

• Queue manager job log

• Copy of the IMS log

CSQQ007E

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

Explanation:

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 MQ reason code for the resolve in-doubt function failure.

Severity:

4

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

See the WebSphere MQ for z/OS System Setup Guide for information about resolving the MQ unit of recovery associated with the in-doubt IMS unit of work.

Problem Determination:

You might find the following items useful in resolving the problem:

• Symptom string

• Printout of SYS1.LOGREC

• Queue manager job log

• IMS and MQ log records

CSQQ008I

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

Explanation:

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.

Severity:

4

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt IMS unit of work.

Problem Determination:

You might find the following items useful in resolving the problem:

• IMS and MQ log records

CSQQ010E

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

Explanation:

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.

Severity:

4

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt IMS unit of work.

Problem Determination:

You might find the following items useful in resolving the problem:

• IMS and MQ log records

• Queue manager job log

CSQQ011E

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

Explanation:

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 MQ terminate identify function.

Severity:

12

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

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

Problem Determination:

You might find the following items useful in resolving the problem:

• Printout of SYS1.LOGREC

• Queue manager job log

• Copy of the IMS log

CSQQ013I

MQ commands cannot be issued using the /SSR command

Explanation:

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

Severity:

4

System Action:

None

Operator Response:

Issue the MQ command from the z/OS console.

CSQQ014E

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

Explanation:

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.

Severity:

4

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt IMS unit of work.

Problem Determination:

You might find the following items useful in resolving the problem:

• IMS and MQ log records

• Queue manager job log

CSQQ015E

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

Explanation:

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.

Severity:

4

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt IMS unit of work.

Problem Determination:

You might find the following items useful in resolving the problem:

• IMS and MQ log records

• Queue manager job log

CSQQ100I

psb-name region-id Processing queue manager name

Explanation:

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.

Severity:

0

CSQQ101E

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

Explanation:

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.

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ102E

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

Explanation:

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.

Severity:

4

System Action:

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

System Programmer Response:

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.

CSQQ103E

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

Explanation:

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.

Severity:

4

System Action:

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

System Programmer Response:

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.

CSQQ104E

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

Explanation:

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.

Severity:

4

System Action:

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

System Programmer Response:

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.

CSQQ105E

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

Explanation:

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.

Severity:

4

System Action:

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

System Programmer Response:

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.

CSQQ106E

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

Explanation:

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.

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ107E

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

Explanation:

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.

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ108I

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

Explanation:

The LTERM specified to receive diagnostic messages cannot be used.

Severity:

4

System Action:

Messages are sent to the master terminal.

System Programmer Response:

Resolve why lterm-name was not available.

CSQQ109E

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

Explanation:

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.

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ110I

Queue name = q-name

Explanation:

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.

Severity:

0

CSQQ111E

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

Explanation:

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.

Severity:

4

System Action:

The message is sent to the dead-letter queue.

System Programmer Response:

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

CSQQ112E

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

Explanation:

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.

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ113I

psb-name region-id This message cannot be processed

Explanation:

When an attempt to process a message using an 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.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

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).

CSQQ114E

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

Explanation:

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.

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ115I

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

Explanation:

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

Severity:

0

CSQQ116E

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

Explanation:

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

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ117E

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

Explanation:

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

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ118I

MsgID=msg-id

Explanation:

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

Severity:

0

CSQQ119E

psb-name region-id Error rc from STORAGE OBTAIN

Explanation:

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

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ120E

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

Explanation:

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.

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ121E

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

Explanation:

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.

Severity:

4

System Action:

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

System Programmer Response:

Define a dead-letter queue if one is required.

CSQQ122E

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

Explanation:

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.

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ123E

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

Explanation:

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.

Severity:

4

System Action:

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

System Programmer Response:

Define the dead-letter queue as a local queue.

CSQQ124E

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

Explanation:

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.

Severity:

4

System Action:

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

System Programmer Response:

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

CSQQ125E

psb-name region-id No initiation queue identified

Explanation:

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

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ126E

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

Explanation:

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

Severity:

8

System Action:

CSQQTRMN ends.

System Programmer Response:

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

CSQQ150I

csect-name IBM WebSphere MQ for z/OS version

Explanation:

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

Severity:

0

CSQQ151I

csect-name Trigger Monitor Input Report - date time

Explanation:

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

Severity:

0

CSQQ152I

csect-name Unable to OPEN CSQQUT1 data set

Explanation:

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

Severity:

8

System Action:

Default values are used for the options.

System Programmer Response:

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.

CSQQ153I

csect-name First token is not a valid keyword

Explanation:

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

Severity:

8

System Action:

The statement is ignored.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about the correct syntax required for the statement.

CSQQ159I

csect-name Trigger monitor options:

Explanation:

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

Severity:

0