CICS adapter messages (CSQC...)

 

CSQC100D
cics-applid csect-name Cannot retrieve data from a START command. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2
Explanation:

CKTI has attempted to retrieve data from a CICS START command, but the retrieve was unsuccessful.

Severity:

8

System Action:

CKTI ends.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. Use the data contained in these fields to resolve the problem, and retry.

CSQC101D
cics-applid csect-name Cannot open the initiation queue. MQCC=mqcc MQRC=mqrc
Explanation:

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

Severity:

8

System Action:

CKTI ends.

Operator Response:

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

CSQC102D
cics-applid csect-name Cannot start the CICS transaction tran-id. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2
Explanation:

A trigger message has been retrieved from the initiation queue which defines a CICS transaction to be started. However the transaction cannot be started (for example, it cannot be found).

Severity:

8

System Action:

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

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. Determine the reason for the problem, and restart the transaction.

CSQC103E
cics-applid csect-name CKTI has 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 CSQCTASK.

Severity:

4

System Action:

The trigger message is sent to the dead-letter queue. CKTI 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.

CSQC104E
cics-applid csect-name CKTI does not support version version-id
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 CSQCTASK.

Severity:

4

System Action:

The trigger message is sent to the dead-letter queue. CKTI 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.

CSQC105E
cics-applid csect-name CKTI cannot start a process type of process-type
Explanation:

A trigger message has been retrieved, but the process type in MQTM is not CICS, and so cannot be processed by this version of CSQCTASK.

Severity:

4

System Action:

The trigger message is sent to the dead-letter queue. CKTI 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.

CSQC106D
cics-applid csect-name MQGET failure. CKTI will end. MQCC=mqcc MQRC=mqrc
Explanation:

An attempt to issue an MQGET call on the initiation queue has been unsuccessful.

Severity:

8

System Action:

CKTI 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, and use CKQC to restart CKTI.

CSQC107I
cics-applid csect-name A request to end CKTI has been received. CKTI ended
Explanation:

A request to end CKTI has been sent from the MQ CICS adapter. This is a normal completion of CKTI.

Severity:

0

System Action:

CKTI ends.

CSQC108D
cics-applid csect-name Unexpected invocation. CKTI terminated
Explanation:

An attempt has been made to start CKTI, but not from CKCN or CKSQ. This is not allowed.

Severity:

8

System Action:

CKTI ends.

Operator Response:

Start CKTI from either CKCN or CKSQ.

CSQC109D
cics-applid csect-name MQCLOSE failed. MQCC=mqcc MQRC=mqrc
Explanation:

An attempt has been made to close a queue, but the MQCLOSE call was unsuccessful. This message is followed by message CSQC110I, indicating the name of the queue.

Severity:

8

System Action:

An implicit close of the queue will take place when the transaction 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.

CSQC110I
cics-applid csect-name Queue name = q-name
Explanation:

This message is issued to indicate the queue in error if an operation on a queue (for example, an MQOPEN) is unsuccessful. The accompanying messages indicate the cause of the problem.

Severity:

8

CSQC111D
cics-applid csect-name CKTI has read a trigger message with an incorrect length of length
Explanation:

This message is issued if the transaction CKTI receives a trigger message that does not match the MQTM control block.

Severity:

8

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.

CSQC112A
cics-applid csect-name MQOPEN error. MQCC=mqcc MQRC=mqrc
Explanation:

An MQOPEN call has been unable to open a queue. This message is followed by message CSQC110I indicating the name of the queue.

Severity:

8

System Action:

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

CSQC113I
cics-applid csect-name 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 system console.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

Check the console 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).

CSQC114A
cics-applid csect-name MQINQ failed. MQCC=mqcc MQRC=mqrc
Explanation:

An attempt to use the MQINQ call to inquire about the attributes of a queue was unsuccessful. This message is followed by message CSQC110I indicating the name of the queue.

Severity:

8

System Action:

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

CSQC116A
cics-applid csect-name Cannot open the queue manager. MQCC=mqcc MQRC=mqrc
Explanation:

An MQOPEN call to the queue manager was unsuccessful.

Severity:

8

System Action:

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

CSQC117A
cics-applid csect-name Cannot query the queue manager. MQCC=mqcc MQRC=mqrc
Explanation:

An MQINQ call to the queue manager was unsuccessful.

Severity:

8

System Action:

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

CSQC118I
cics-applid csect-name MsgID=msg-id
Explanation:

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

Severity:

0

CSQC119A
cics-applid csect-name CICS detected an IRC failure. Cannot start transaction tran-id
Explanation:

A trigger message was retrieved from the initiation queue which defined a CICS transaction to be started, and the transaction is defined to run in a remote CICS region. The EXEC CICS START request for this transaction ended abnormally because of a failure in the IRC connection between the local and remote CICS regions.

Severity:

8

System Action:

The trigger message is sent to the dead-letter queue, and CKTI continues processing the next message.

System Programmer Response:

Investigate the reason for the IRC failure.

CSQC120A
cics-applid csect-name MQPUT failed. 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. This message is followed by message CSQC110I indicating the name of the queue.

Severity:

8

System Action:

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

CSQC121A
cics-applid csect-name No dead-letter queue defined for queue manager
Explanation:

A dead-letter queue has not been defined for the queue manager.

Severity:

8

System Action:

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

System Programmer Response:

Define a dead-letter queue if one is required.

CSQC122A
cics-applid csect-name Cannot close the queue manager. MQCC=mqcc MQRC=mqrc
Explanation:

CKTI was unable to close the queue manager after inquiring about the dead-letter queue.

Severity:

8

System Action:

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

CSQC123A
cics-applid csect-name The dead-letter queue is not of type local
Explanation:

The dead-letter queue defined was not of type local. This message is followed by message CSQC110I, indicating the name of the queue.

Severity:

8

System Action:

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

System Programmer Response:

Define the dead-letter queue as a local queue.

CSQC124A
cics-applid csect-name The dead-letter queue is not of usage normal
Explanation:

The dead-letter queue defined is not of usage type normal. This message is followed by message CSQC110I, indicating the name of the queue.

Severity:

8

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.

CSQC211D
cics-applid csect-name Unable to LINK to program CSQCPARM. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

An attempt to link to CSQCPARM was unsuccessful.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. Determine the reason for the problem, and use the MQ CICS adapter control panels (the CKQC transaction) to retry the connection process.

CSQC212D
cics-applid csect-name CSQCPARM missing in SIT/SIT Override INITPARM
Explanation:

CSQCQCON attempted to connect to MQ, but the attempt was unsuccessful because the CSQCPARM keyword in the INITPARM statement was not found in the system initialization table (SIT) (or the SIT override INITPARM statement).

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

Add CSQCPARM keyword to the INITPARM statement of the SIT table (or the SIT override), restart CICS, and use the MQ CICS adapter control panels (the CKQC transaction) to retry the connection process. See the WebSphere MQ for z/OS System Setup Guide for information about the system initialization table.

CSQC213D
cics-applid csect-name Queue manager name missing in CSQCPARM. Command rejected
Explanation:

An attempt was made to connect to MQ, but it was unsuccessful because the CSQCPARM keyword in the INITPARM statement did not contain the name of the required queue manager.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

Use the MQ CICS adapter control panels (the CKQC transaction) to specify the queue manager name, and retry the connection process. See the WebSphere MQ for z/OS System Setup Guide for information about CSQCPARM.

CSQC214E
cics-applid csect-name Initiation queue name not found. CKTI not started
Explanation:

A connection has been made to MQ, but CKTI cannot be started as no initiation queue name has been specified.

Severity:

0

System Action:

The queue manager is connected, but CKTI is not started.

Operator Response:

Use the MQ CICS adapter control panels (the CKQC transaction) to start CKTI.

System Programmer Response:

Add the initiation queue name to INITPARM statement if you want to start CKTI automatically next time you connect CICS to MQ.

CSQC216D
cics-applid csect-name Queue manager name invalid. Connection rejected
Explanation:

An attempt has been made to connect to MQ, but it was unsuccessful because the queue manager name given was more than 4 characters long.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

Use the MQ CICS adapter control panels to specify the correct queue manager name, or correct the CSQCPARM keyword in the INITPARM statement, and retry the connection process. See the WebSphere MQ for z/OS System Setup Guide for information about INITPARM and CSQCPARM.

CSQC217E
cics-applid csect-name Initiation queue name invalid. CKTI not started
Explanation:

An attempt has been made to connect to MQ, but it was unsuccessful because the initiation queue name given was more than 48 characters long.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

Use the MQ CICS adapter control panels (the CKQC transaction) to specify the correct initiation queue name, and retry the connection process.

CSQC218I
cics-applid csect-name No trace number specified in CSQCPARM. The default of 0 will be used
Explanation:

A connection has been made to MQ but no trace number was specified in the CSQCPARM keyword of the INITPARM statement. The default of 0 will be used.

Severity:

0

System Action:

The queue manager is connected with a trace number of 0.

System Programmer Response:

Use the MQ CICS adapter control panels (the CKQC transaction) to specify the required trace number. Add the trace number to the CSQCPARM keyword of the INITPARM statement to set it automatically next time you connect CICS to MQ.

CSQC219E
cics-applid csect-name Trace number specified in CSQCPARM is not valid. The default of 0 will be used
Explanation:

A connection has been made to MQ but the trace number specified in the CSQCPARM keyword of the INITPARM statement was not valid. The default of 0 will be used.

Severity:

4

System Action:

The queue manager is connected with a trace number of 0.

System Programmer Response:

Use the CICS adapter control panels (the CKQC transaction) to specify the required trace number. Correct the trace number in the CSQCPARM keyword of the INITPARM statement to set it automatically next time you connect CICS to MQ.

CSQC220D
cics-applid csect-name Unable to LINK to program CSQCCON. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

An attempt to link to CSQCCON was unsuccessful.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. Determine the reason for the problem, and use the MQ CICS adapter control panels (the CKQC transaction) to retry the connection process.

CSQC223D
cics-applid csect-name Unable to LINK to program CSQCQCON. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

An attempt to link to CSQCQCON was unsuccessful.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. Determine the reason for the problem, and use the MQ CICS adapter control panels (the CKQC transaction) to retry the connection process.

CSQC230D
cics-applid csect-name Unable to receive input. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

The CICS adapter is unable to receive input from the CKQC transaction.

Severity:

8

System Action:

The requested function is not performed.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values, and take the appropriate action.

CSQC232D
cics-applid csect-name Unable to RETURN TRANSID tran-id IMMEDIATE. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

An attempt was made to issue an EXEC CICS RETURN TRANSID tran-id IMMEDIATE command, but it was unsuccessful.

Severity:

8

System Action:

The function terminates, and control returns to CICS.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values, and reissue the command.

CSQC235D
cics-applid csect-name Unrecognizable screen. Re-submit CKQC
Explanation:

CICS cannot determine the identifier of the screen currently displayed. Because of this, it cannot interpret the screen contents (including any input fields).

Severity:

8

System Action:

The input is ignored, and the transaction finishes.

System Programmer Response:

Resubmit CKQC to restart from the beginning of the CICS transaction.

Problem Determination:

If this problem occurs frequently, contact your IBM support center for help.

CSQC236A
cics-applid csect-name Display functions only supported using panel interface
Explanation:

The display function was requested; this function can only be used from the MQ CICS adapter control panels (the CKQC transaction).

Severity:

8

System Action:

The request is ignored.

Operator Response:

Use the MQ CICS adapter control panels to access the display functions.

CSQC237A
cics-applid csect-name Panel interface not supported on console
Explanation:

The MQ CICS adapter control panels (the CKQC transaction) are not supported on the console.

Severity:

8

System Action:

The panel request is ignored.

Operator Response:

Use a 3270 device to display the MQ CICS adapter control panels.

CSQC239D
cics-applid csect-name Unable to LINK to program CSQCBASE. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

CKQC could not display the panel because it could not link to CSQCBASE.

Severity:

8

System Action:

CKQC ends.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. Determine the reason for the problem, and retry the operation.

CSQC240D
cics-applid csect-name Task not associated with a terminal. Request rejected
Explanation:

The request was issued by a task that was not associated with a terminal. This is not allowed.

Severity:

8

System Action:

The request is ignored.

Operator Response:

Reissue the request from a task that has a 3270 device or console associated with it.

CSQC241D
cics-applid csect-name Unable to receive input. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

The system cannot receive input from the screen.

Severity:

8

System Action:

The input is ignored, and the transaction is finished.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. Determine the reason for the problem, and retry the operation.

CSQC242D
cics-applid csect-name Invalid input. Connect rejected
Explanation:

A connection request was issued with incorrect parameters specified.

Severity:

8

System Action:

The request is ignored.

Operator Response:

Use the MQ CICS adapter control panels (the CKQC transaction) to request the function, or check the request syntax in the WebSphere MQ for z/OS System Administration Guide and enter it again.

CSQC243D
cics-applid csect-name Unsupported terminal type. Must be a console or 3270 device
Explanation:

A request was made by a task that is not associated with a console or 3270 device.

Severity:

8

System Action:

The request is ignored.

Operator Response:

Check that you have the correct level of the CICS adapter for the version of CICS that you are using.

Reissue the request from a task that has a 3270 device or console associated with it.

CSQC244E
cics-applid csect-name CICS is being quiesced. Connect rejected
Explanation:

An attempt has been made to connect to MQ, but CICS is shutting down so the connection request has been rejected.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

CSQC300D
cics-applid csect-name Already connected to queue manager qmgr-name. Connect rejected
Explanation:

An attempt has been made to connect to a queue manager, but CICS is already connected to another queue manager so the connection request has been rejected.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

Operator Response:

To connect to the new queue manager, shut down the current connection and reissue the connection request.

CSQC301I
cics-applid csect-name API exit CSQCAPX found and will be used
Explanation:

The CICS API exit program CSQCAPX has been activated.

Severity:

0

CSQC302D
cics-applid csect-name Unable to EXTRACT EXIT CSQCTRUE. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

An attempt to issue an EXEC CICS EXTRACT EXIT CSQCTRUE command was unsuccessful.

Severity:

8

System Action:

The function terminates, and control returns to CICS.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values, and take the appropriate action (for example, use CKQC to restart the connection).

CSQC303I
cics-applid csect-name CSQCSERV loaded. Entry point is address
Explanation:

Module CSQCSERV has been loaded. address is the address of the entry point. You might find this information useful during problem determination.

Severity:

0

CSQC304D
cics-applid csect-name Failed to ENABLE CSQCTRUE. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

An attempt to issue an EXEC CICS ENABLE CSQCTRUE command was unsuccessful during a connect process.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values, and take the appropriate action.

CSQC305D
cics-applid csect-name Unable to INQUIRE MAXTASKS. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

An attempt to issue an EXEC CICS INQUIRE MAXTASKS command was unsuccessful.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values, and take the appropriate action.

CSQC306E
cics-applid csect-name Unable to START transaction CKTI. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

During the connection process, the MQ CICS adapter was unable to start CKTI.

Severity:

8

System Action:

The queue manager is connected, but CKTI is not started.

Operator Response:

Issue the CKQC transaction, and use the panels to start CKTI after the cause of the problem has been corrected.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values, and take the appropriate action.

CSQC307I
cics-applid csect-name Successful connection to queue manager qmgr-name
Explanation:

The connection to queue manager qmgr-name was successful.

Severity:

0

CSQC308D
cics-applid csect-name Queue manager qmgr-name is stopped. Connect request deferred
Explanation:

An attempt to connect to queue manager (qmgr-name) was unsuccessful because qmgr-name was not active.

Severity:

0

System Action:

The connection will be made when qmgr-name becomes active.

Operator Response:

Check that you entered the correct queue manager name (qmgr-name). If required, either:

  • Start the queue manager (the connection will then be made automatically)

  • Use CKQC to connect to an active queue manager.

CSQC309D
cics-applid csect-name Unable to connect to queue manager qmgr-name. MQCC=mqcc MQRC=mqrc
Explanation:

An attempt to connect to queue manager qmgr-name was unsuccessful.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc, and take the appropriate action.

CSQC310D
cics-applid csect-name Duplicate connect to queue manager qmgr-name. Connect rejected
Explanation:

An attempt to connect to a queue manager was unsuccessful because the queue manager is already connected.

Severity:

8

System Action:

The connection process terminates, and control returns to CICS.

CSQC311D
cics-applid csect-name Unable to start alert monitor CKAM. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

During the connection process, the MQ CICS adapter was unable to start the alert monitor CKAM.

Severity:

8

System Action:

The queue manager is connected, but CKAM is not started so the function of the MQ CICS adapter is restricted.

Operator Response:

Without the alert monitor, the MQ CICS adapter is unable to perform the following functions:

  • It cannot handle a deferred connection

  • It cannot respond to a queue manager failure

  • It cannot perform a warm or immediate shutdown if it needs to wait (that is, the last task carries out shutdown)

It is recommended that you use CKQC to terminate the connection using a forced shutdown of the CICS adapter, and refer to the System Programmer Response.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. When the error has been corrected, use the CKQC transaction to reinitiate the connection.

CSQC312E
cics-applid csect-name Unable to GETMAIN CLOC storage. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

The MQ CICS adapter was unable to obtain storage for the CLOC control block.

Severity:

8

System Action:

The connection request is rejected.

System Programmer Response:

The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. This is probably a CICS 'short on storage' problem. Use the procedure followed at your installation to resolve the problem.

CSQC313I
cics-applid csect-name *UOWID=conn-name.uow-id is in doubt
Explanation:

This message is issued at connection time. The unit of work shown is in doubt. An asterisk character preceding the unit-of-work identifier indicates that the unit of work will not be resolved automatically.

System Action:

The will be resolved by the component when remote queuing starts.

units of workdistributed queuing
Severity:

0

System Programmer Response:

See the for information about resolving the MQ unit of recovery associated with the in-doubt unit of work.

WebSphere MQ for z/OS System Administration GuideCICS
CSQC314I
cics-applid csect-name UOWIDs highlighted with * will not be automatically resolved
Explanation:

This message appears when there are unresolved in-doubt . Refer to message CSQC313I.

units of work
Severity:

0

CSQC315E
cics-applid csect-name Unable to LOAD API exit CSQCAPX. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

The MQ adapter is unable to use the API-crossing exit program CSQCAPX. This can be a normal situation if you do not intend to use the API-crossing exit, and have disabled the program CSQCAPX.

CICS
Severity:

8

System Action:

The is not used.

API-crossing exit
System Programmer Response:

The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values. If you are trying to use the , use the data contained in these fields to resolve the problem.

CICS Application Programming ReferenceAPI-crossing exit
CSQC316I
cics-applid csect-name More messages. Check console for full display
Explanation:

This message is displayed if too many messages have been issued to be displayed on the screen.

Severity:

0

Operator Response:

Check the console for further messages.

CSQC318I
cics-applid csect-name UOWID=conn-name.uow-id created by Transid trans-id Taskid task-id is in doubt.
Explanation:

This message is issued at connection time. The unit of work shown is in doubt.

Severity:

0

System Programmer Response:

See the for information about resolving the MQ unit of recovery associated with the in-doubt unit of work.

WebSphere MQ for z/OS System Administration GuideCICS
CSQC319D
cics-applid csect-name Unable to INQUIRE SYSTEM RELEASE. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
Explanation:

An attempt to issue an EXEC INQUIRE SYSTEM RELEASE command was unsuccessful.

CICS
Severity:

8

System Action:

The connection process terminates, and control returns to .

CICS
System Programmer Response:

The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

CICS System Programming Reference
CSQC320E
cics-applid csect-name Version version Release release is not supported
CICS
Explanation:

The version of that you are running is not supported by the version of the MQ adapter that you are using.

CICSCICS
Severity:

8

System Action:

The connection process terminates, and control returns to .

CICS
CSQC321D
cics-applid csect-name There is no active connection. Stop connection rejected
Explanation:

An attempt was made to shut down a connection, but there was no connection active. This could be caused by one of the following:

  • A connection had not been made

  • The connection had already been shut down

  • The connection is still being made (that is, it is pending)

    • Severity:

    8

    System Action:

    The request is ignored, and control returns to .

    CICS
    CSQC322D
    cics-applid csect-name Invalid input. Stop connection rejected
    Explanation:

    A request to shut down the MQ adapter was made, but it was rejected because the syntax of the shutdown request was not valid.

    CICS
    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Issue the request again. See the for details of the correct syntax.

    WebSphere MQ for z/OS System Administration Guide
    CSQC323I
    cics-applid csect-name command received from TERMID=termid TRANID=tranid =userid
    USERID
    Explanation:

    The request to connect or disconnect was received from terminal termid. The originating transaction was tranid (this could be CKAM). userid is the of the operator who used the terminal to initiate the operation. This message is issued on the console for audit trail purposes.

    user ID
    Severity:

    0

    CSQC326D
    cics-applid csect-name Connection status status is not valid for command. Command rejected
    Explanation:

    A request to shut down the MQ adapter was made, but it was rejected because a STOP FORCE shutdown had already been requested.

    CICS
    Severity:

    8

    System Action:

    The request is ignored.

    CSQC330E
    cics-applid csect-name Transaction Server Version version Release release is not supported
    CICS
    Explanation:

    The version of Transaction Server that you are running is not supported by the version of the MQ adapter that you are using .

    CICSCICS
    Severity:

    8

    System Action:

    The connection process terminates, and control returns to .

    CICS
    CSQC331I
    cics-applid csect-name Adapter shutdown completed
    Explanation:

    The MQ adapter has been shut down. However, it was not able to disconnect from MQ (for example, because the queue manager had already shut down).

    CICS

    Severity:

    4

    Operator Response:

    Look for other messages explaining why the MQ adapter could not disconnect from MQ.

    CICS
    CSQC332I
    cics-applid csect-name Queue manager qmgr-name is already stopped. MQCC=mqcc MQRC=mqrc
    Explanation:

    A request was made to shut down the MQ adapter, but the queue manager has already shut down. For example, the operator shuts down both the queue manager and the MQ adapter simultaneously. If the queue manager stops first, it cannot receive the disconnect request from the adapter.

    CICSCICSCICS
    Severity:

    0

    System Action:

    The adapter shutdown process continues.

    Operator Response:

    If the queue manager is already shut down, we can ignore this message. Refer to for information about mqcc and mqrc, and take the appropriate action.

    Appendix A. API completion and reason codes
    CSQC333E
    cics-applid csect-name Unable to disconnect from queue manager qmgr-name. MQCC=mqcc MQRC=mqrc
    Explanation:

    A request has been made to disconnect from queue manager qmgr-name but it was unsuccessful.

    Severity:

    8

    System Action:

    The adapter shutdown process continues.

    Operator Response:

    If the queue manager is already shut down, we can ignore this message. Refer to for information about mqcc and mqrc, and take the appropriate action.

    Appendix A. API completion and reason codes
    CSQC334I
    cics-applid csect-name Adapter shutdown successful
    Explanation:

    The shutdown process has completed successfully.

    Severity:

    0

    CSQC336I
    cics-applid csect-name command received from a PLT program
    Explanation:

    The command request was received from a PLT program. This message is issued on the console for audit trail purposes.

    Severity:

    0

    CSQC341I
    cics-applid csect-name shutdown-type requested by alert monitor CKAM
    Explanation:

    The request to shut down the MQ adapter was issued by the alert monitor CKAM. shutdown-type is either STOP or STOP FORCE. This message is issued on the console for audit trail purposes.

    CICS
    Severity:

    0

    CSQC342I
    cics-applid csect-name request received from alert monitor
    Explanation:

    Request request was received from the alert monitor (CKAM). This message is issued on the console for audit trail purposes.

    Severity:

    0

    CSQC350I
    cics-applid csect-name Unable to LOAD API exit CSQCAPX. Program not found
    Explanation:

    The MQ adapter is unable to use the API-crossing exit program CSQCAPX because it cannot be found. This is a normal situation if you do not intend to use the API-crossing exit.

    CICS
    Severity:

    0

    System Action:

    The is not used.

    API-crossing exit
    System Programmer Response:

    If you wish to use the :

    API-crossing exit

  • Ensure that CSQCAPX is in the DFHRPL concatenation.

  • Issue the command CEMT SET PROGRAM(CSQCAPX) NEWCOPY ENABLE.
    • CICS

  • Activate the exit using the Modify Connection option of the CKQC transaction.

    • CSQC351I
    cics-applid csect-name Unable to LOAD API exit CSQCAPX. Program is disabled
    Explanation:

    The MQ adapter is unable to use the API-crossing exit program CSQCAPX because it is disabled. This is a normal situation if you do not intend to use the API-crossing exit, and have therefore disabled the program CSQCAPX.

    CICS
    Severity:

    0

    System Action:

    The is not used.

    API-crossing exit
    System Programmer Response:

    If you wish to use the :

    API-crossing exit

  • Ensure that CSQCAPX is in the DFHRPL concatenation.

  • Issue the command CEMT SET PROGRAM(CSQCAPX) NEWCOPY ENABLE.
    • CICS

  • Activate the exit using the Modify Connection option of the CKQC transaction.

    • CSQC360D
    cics-applid csect-name Unable to RETRIEVE RTRANSID. Monitor terminated. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    An attempt to issue an EXEC RETRIEVE RTRANSID was unsuccessful (for example, an unauthorized user has tried to start the alert monitor).

    CICS
    Severity:

    8

    System Action:

    Processing continues (including the alert monitor if one is already running).

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values.

    CICS Application Programming Reference
    CSQC361D
    cics-applid csect-name Unexpected invocation. Monitor terminated
    Explanation:

    An attempt was made to start the alert monitor by an unrecognized transaction.

    Severity:

    8

    System Action:

    The request is ignored.

    CSQC362D
    cics-applid csect-name Unable to EXTRACT EXIT CSQCTRUE. Monitor terminated. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    An attempt to issue an EXEC EXTRACT EXIT CSQCTRUE command was unsuccessful.

    CICS
    Severity:

    8

    System Action:

    The alert monitor terminates.

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values. Take the appropriate action, and use the MQ adapter control panels (the CKQC transaction) to restart the MQ adapter.

    CICS Application Programming ReferenceCICSCICS
    CSQC363D
    cics-applid csect-name Unable to perform WAIT EXTERNAL. Monitor terminated. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    An attempt to perform an EXEC WAIT EXTERNAL was unsuccessful.

    CICS
    Severity:

    8

    System Action:

    The alert monitor terminates.

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

    CICS Application Programming Reference
    CSQC364I
    cics-applid csect-name Monitor terminated normally
    Explanation:

    There are no remaining active or deferred connections, so the alert monitor has terminated.

    Severity:

    0

    CSQC365E
    cics-applid csect-name Unable to LINK to program CSQCQCON. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    The alert monitor has detected that a deferred connection has been activated, but it cannot link to CSQCQCON.

    Severity:

    8

    System Action:

    The connection process is terminated, and control returns to .

    CICS
    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values. Use the MQ adapter control panels (the CKQC transaction) to make the connection.

    CICS Application Programming ReferenceCICS
    CSQC366E
    cics-applid csect-name Unable to LINK to program CSQCDSC. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    The alert monitor has detected that the MQ adapter is ready to shut down but cannot link to CSQCDSC.

    CICS
    Severity:

    8

    System Action:

    The disconnection process is continued, and control returns to .

    CICS
    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values. Use the MQ adapter control panels (the CKQC transaction) to disconnect from MQ.

    CICS Application Programming ReferenceCICS
    CSQC368E
    cics-applid csect-name Invalid PEB type type at location location. PEB ignored
    Explanation:

    A pending event was not of the type expected by the alert monitor.

    Severity:

    8

    System Action:

    The pending event is discarded.

    Problem Determination:

    If this problem occurs frequently, collect the following diagnostic items, and contact your IBM support center for help:

  • A note of the values returned in the message

  • Any trace information collected

    • CSQC369E
    cics-applid csect-name More than 99 notify messages outstanding. This message is postponed temporarily
    Explanation:

    More than 99 pending events have been established. (For example, attempts have been made to connect to more than 99 systems that are not running.)

    Severity:

    8

    System Action:

    The event is not processed until one of the other 99 events has expired.

    Operator Response:

    If you want to clean up the system, shut down and restart .

    CICS
    CSQC380D
    cics-applid csect-name No active connection. command rejected
    Explanation:

    An attempt to start or stop CKTI or to use the DISPLAY/RESET function, was unsuccessful because there was no active connection between MQ and .

    CICS
    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Establish a connection, and reissue the request.

    CSQC381D
    cics-applid csect-name No name specified at connect time. command rejected
    initiation queue
    Explanation:

    An attempt was made to start or stop CKTI using the default queue name, but the default queue name was not found. This was because the current connection does not have an initiation queue name associated with it.

    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Specify the queue name explicitly.

    System Programmer Response:

    If you require a default queue name, specify one when you perform the connection process. See the for information about how to achieve this.

    WebSphere MQ for z/OS System Administration Guide
    CSQC382D
    cics-applid csect-name CKTI with the same name is being started. command rejected
    initiation queue
    Explanation:

    An attempt was made to start CKTI specifying the name of an that is used by another CKTI being started.

    initiation queue
    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Review the console for messages in the range CSQC100D through CSQC109D for further information, or use operator commands (for example CEMT INQ TASK) to determine why the CKTI started earlier is not running.

    CICS
    CSQC383D
    cics-applid csect-name Another CKTI with the same name is still running. command rejected
    initiation queue
    Explanation:

    An attempt was made to start CKTI specifying the name of an that is already used by a CKTI which is still running.

    initiation queue
    Severity:

    8

    System Action:

    The reqeust is ignored.

    Operator Response:

    If required, use the MQ adapter control panels (the CKQC transaction) to stop the existing CKTI, and restart.

    CICS
    CSQC384D
    cics-applid csect-name Another CKTI with the same name is being stopped. command rejected
    initiation queue
    Explanation:

    Either:

  • An attempt was made to start CKTI with an name the same as the one that is currently being stopped.
    • initiation queue

  • An attempt was made to stop an that was already in the process of stopping.
    • initiation queue

    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Wait until the has stopped, and then reissue the start request if required.

    initiation queue
    CSQC385D
    cics-applid csect-name CKTI not found. command rejected
    Explanation:

    An attempt to stop CKTI was unsuccessful because the queue name specified was not found. This is because either:

  • The name of the was specified incorrectly
    • initiation queue

  • The CKTI has already stopped

    • Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Verify the name of the , and reissue the request if necessary.

    initiation queue
    CSQC386I
    cics-applid csect-name command initiated from TERMID=term-id TRANID=tran-id =user-id and is accepted
    USERID
    Explanation:

    The MQ adapter has processed the command request. However, the task might not have completed its processing yet (for example, CKTI could be waiting for a certain event to occur before it can be stopped). command can be either STARTCKTI, STOPCKTI, or RESET.

    CICSCICS
    Severity:

    0

    CSQC389D
    cics-applid csect-name Invalid input. Start/Stop CKTI rejected
    Explanation:

    The syntax of the adapter request entered was incorrect.

    CICS
    Severity:

    8

    System Action:

    The request is rejected.

    System Programmer Response:

    See the for details of the correct syntax, or use the MQ adapter control panels (the CKQC transaction) to request the function.

    WebSphere MQ for z/OS System Administration GuideCICS
    CSQC390I
    cics-applid csect-name Transaction Server is Vversion Release release
    CICS
    Explanation:

    This message is issued to show which version of Transaction Server you are using.

    CICS
    Severity:

    0

    CSQC400I
    cics-applid csect-name UOWID=conn-name.uow-id
    Explanation:

    This message gives the and the identifier of a unit of work and appears with one of the following messages:

    connection name

  • CSQC402I

  • CSQC403I

  • CSQC404E

  • CSQC405E

  • CSQC406E

  • CSQC407E

    • We can use the when using MQ commands (for example, RESOLVE INDOUBT).

    connection name
    Severity:

    0

    CSQC402I
    cics-applid csect-name Resolved with COMMIT
    Explanation:

    The syncpoint coordinator has informed MQ that the unit of work indicated by the accompanying CSQC400I message has been committed.

    Severity:

    0

    CSQC403I
    cics-applid csect-name Resolved with BACKOUT
    Explanation:

    The syncpoint coordinator has informed MQ that the unit of work indicated by the accompanying CSQC400I message has been backed out.

    Severity:

    0

    CSQC404E
    cics-applid csect-name Resolve failed. MQCC=mqcc MQRC=mqrc
    Explanation:

    The syncpoint coordinator requested that the unit of work indicated by the accompanying CSQC400I message be committed or backed out. However, MQ was unable to do this.

    Severity:

    8

    System Action:

    The unit of work remains in doubt.

    System Programmer Response:

    If you want to resolve the unit of work:

  • Diagnose the cause of the problem and correct it (refer to for information about mqcc and mqrc)
    • Appendix A. API completion and reason codes

  • Disconnect MQ.

  • Use the MQ adapter control panels (the CKQC transaction) to reconnect MQ.
    • CICS

    CSQC405E
    cics-applid csect-name Execute resolve failed. MQCC=mqcc MQRC=mqrc
    Explanation:

    The syncpoint coordinator requested that resolution of the be executed. However, MQ was unable to do this.

    units of work
    Severity:

    8

    System Action:

    The remain in doubt.

    units of work
    System Programmer Response:

    Refer to for information about mqcc and mqrc to determine the cause of the problem. See the for information about resolving the MQ unit of recovery associated with the in-doubt unit of work.

    Appendix A. API completion and reason codesWebSphere MQ for z/OS System Administration GuideCICS
    CSQC406E
    cics-applid csect-name Cannot resolve, syncpoint lost
    disposition
    Explanation:

    The syncpoint coordinator has been subjected to a cold start, and information regarding has been lost (syncpoint state UERTDGCS). The coordinator cannot inform the MQ adapter whether to commit or back out the unit of work indicated by the accompanying CSQC400I message.

    units of workCICS

    For information about UERTDGCS, see the .

    CICS Customization Guide
    Severity:

    8

    System Action:

    The unit of work remains in doubt.

    Operator Response:

    Determine how to resolve the in-doubt unit of work. See the for information about resolving the MQ unit of recovery associated with the in-doubt unit of work.

    WebSphere MQ for z/OS System Administration GuideCICS
    CSQC407E
    cics-applid csect-name Cannot resolve, syncpoint unknown
    disposition
    Explanation:

    The syncpoint coordinator cannot find a decision about resolving the unit of work indicated by the accompanying CSQC400I message (syncpoint state UERTDGNK). The coordinator cannot inform the MQ adapter whether to commit or back out the unit of work.

    CICS

    For information about UERTDGNK, see the .

    CICS Customization Guide
    Severity:

    8

    System Action:

    The unit of work remains in-doubt.

    Operator Response:

    Determine how to resolve the in-doubt unit of work. See the for information about resolving the MQ unit of recovery associated with the in-doubt unit of work.

    WebSphere MQ for z/OS System Administration GuideCICS
    CSQC408I
    cics-applid csect-name Only partial resynchronization achieved. Check above messages
    Explanation:

    Total resynchronization was not achieved; some remain in doubt.

    units of work
    Severity:

    0

    Operator Response:

    Action any messages received before this one which indicate that have not been resolved. When there are no more in-doubt units of work you will receive message CSQC409I.

    units of work
    CSQC409I
    cics-applid csect-name Resynchronization completed successfully
    Explanation:

    Resynchronization has completed successfully; all have been resolved.

    units of work
    Severity:

    0

    CSQC410I
    cics-applid csect-name detected. Adapter terminated
    CICSimmediate shutdown
    Explanation:

    CICS has notified the MQ adapter that it is shutting down immediately.

    CICS
    Severity:

    0

    System Action:

    The MQ adapter initiates an . Any in-flight tasks using MQ are backed out when the connection is broken by .

    CICSimmediate shutdownCICS
    Operator Response:

    See the for more information about MQ adapter shutdown.

    WebSphere MQ for z/OS System Administration GuideCICS
    CSQC411I
    cics-applid csect-name CICS warm shutdown detected. Adapter is quiescing
    Explanation:

    CICS has notified the MQ adapter that it has initiated a warm shutdown.

    CICS
    Severity:

    0

    System Action:

    The MQ adapter initiates a .

    CICSquiesced shutdown
    Operator Response:

    See the for more information about MQ adapter shutdown.

    WebSphere MQ for z/OS System Administration GuideCICS
    CSQC412I
    cics-applid csect-name CICS abend detected. Adapter terminated
    Explanation:

    The MQ adapter detected a CICS abend.

    CICS
    Severity:

    0

    System Action:

    The MQ adapter is terminated.

    CICS
    CSQC413I
    cics-applid csect-name Task ID id force purge deferred until its current request has completed
    Explanation:

    The task with an identifier of id is being force purged by the operator while it is waiting for an outstanding request to complete. The force purge will not be processed until the outstanding request completes.

    Severity:

    0

    System Action:

    If the task reaches a must-complete state (for example, syncpoint) the task is not ended after the request has been completed. Otherwise, it will terminate with an abend code of AEXY. For more information about these abend codes, see the relevant manual.

    CICSCICS Messages and Codes
    CSQC414I
    cics-applid csect-name Abending task ID id abend-code
    Explanation:

    The task with an identifier of id has been force purged by the operator, and abends with abend-code.

    Severity:

    0

    System Action:

    The outstanding task has been completed and, because it is not in a must-commit state, the MQ adapter ends the task abnormally. For more information about the abend code, see the manual.

    CICSCICSCICS Messages and Codes
    CSQC415I
    cics-applid csect-name Task ID id will continue. Force purge ignored
    Explanation:

    The task with an identifier of id has been force purged by the operator.

    Severity:

    0

    System Action:

    The outstanding task has been completed but, because it is in a must-commit state (for example, syncpoint), the MQ adapter does not end the task.

    CICS
    CSQC416I
    cics-applid csect-name Address address is out of range. Area of length length is not traced
    Explanation:

    An address (address) passed from an application was out of range for one of the following reasons:

  • The address plus the length of the area to be traced exceeds the 2GB addressing limit

  • The address is not within the private area storage of the region as regarded by z/OS
    • CICS

    Because of this, the trace facility is unable to trace the area.

    CICS
    Severity:

    0

    System Action:

    This message is inserted into the trace, and processing continues.

    CICS
    System Programmer Response:

    If the address is in error, correct the application.

    CSQC417I
    cics-applid csect-name is Vversion Release release
    CICS
    Explanation:

    This message is issued to show which version of you are using.

    CICS
    Severity:

    0

    CSQC418D
    cics-applid csect-name Unable to LOAD program CSQAVICM. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    An attempt to load CSQAVICM was unsuccessful.

    Severity:

    8

    System Action:

    The process terminates, and control returns to .

    CICS
    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values.

    CICS Application Programming Reference
    CSQC419I
    cics-applid csect-name No server subtasks available. Task will abend
    Explanation:

    A task has issued an MQ API call that requires task switching, but there are no server subtasks available. This might be because the subtasks have not yet started, or did not start successfully. (Message CSQC472I is issued for each subtask started; there should be eight subtasks.)

    Severity:

    0

    System Action:

    The task is ended abnormally with code QNST.

    CSQC420D
    cics-applid csect-name Unable to send map map-id mapset CSQCMS. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    The program was unable to send map map-id from the map set CSQCMS to the screen.

    Severity:

    8

    System Action:

    The task is terminated.

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

    CICS Application Programming Reference
    CSQC421A
    cics-applid csect-name Tab cursor was not on a valid object
    Explanation:

    The cursor was not in the correct position when the enter key was pressed.

    Severity:

    8

    System Action:

    The input is ignored.

    Operator Response:

    Use the tab key to move the cursor to a valid position.

    CSQC422D
    cics-applid csect-name Unable to RETURN TRANSID CKBM. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    An attempt was made to issue an EXEC RETURN TRANSID CKBM command, but it was unsuccessful.

    CICS
    Severity:

    8

    System Action:

    The transaction terminates, and control returns to .

    CICS
    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

    CICS Application Programming Reference
    CSQC423D
    cics-applid csect-name Unable to XCTL to program pgm-name. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    An attempt to transfer control to program pgm-name was unsuccessful.

    Severity:

    8

    System Action:

    The transaction terminates, and control returns to .

    CICS
    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

    CICS Application Programming Reference
    CSQC424D
    cics-applid csect-name Invalid key entered
    Explanation:

    The function key pressed was not valid for this panel.

    Severity:

    8

    System Action:

    The key is ignored.

    Operator Response:

    Use one of the function keys shown at the bottom of the panel.

    CSQC425D
    cics-applid csect-name No parameter window for this function
    Explanation:

    An attempt was made to display a parameter window. There are no parameters for the function selected, so there is no parameter window to display.

    Severity:

    8

    System Action:

    The request is ignored.

    CSQC430D
    cics-applid csect-name Unknown map name map-name. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    CICS was unable to locate the map specified (for example, because the map was not defined during the installation procedure). map-name is the name of the map in question.

    Severity:

    8

    System Action:

    The transaction terminates.

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

    CICS Application Programming Reference
    CSQC431D
    cics-applid csect-name Invalid action number. Re-enter
    Explanation:

    The action number specified was out of the range available.

    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Specify an action number in the range displayed.

    CSQC432D
    cics-applid csect-name Invalid task number. Re-enter
    Explanation:

    The task number specified was out of the range requested.

    Severity:

    8

    System Action:

    The request is ignored.

    System Programmer Response:

    Specify a task number in the range displayed.

    CSQC433D
    cics-applid csect-name Invalid option. Must be 1, 2, 3 or 4
    Explanation:

    The value entered was not 1, 2, 3, or 4.

    Severity:

    8

    System Action:

    The value is rejected.

    Operator Response:

    Enter a value of either 1, 2, 3, or 4 on the pop-up screen.

    CSQC434D
    cics-applid csect-name missing. Must be entered
    Queue manager name
    Explanation:

    The queue manager name was not specified on the connection parameter panel.

    Severity:

    8

    System Action:

    The connection request is rejected.

    Operator Response:

    Enter the name of the required queue manager on the panel.

    System Programmer Response:

    If a default name is required, specify the queue manager name in CSQCPARM. See the for information about how to do this.

    WebSphere MQ for z/OS System Setup Guide
    CSQC435D
    cics-applid csect-name Invalid trace number. Must be numeric
    Explanation:

    The trace number entered was not numeric.

    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Enter a numeric trace number (in the range 0 through 199).

    CSQC436D
    cics-applid csect-name Invalid trace number. Must be < 200
    Explanation:

    The trace number entered was not in the valid range.

    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Enter a trace number in the range 0 through 199.

    CSQC438D
    cics-applid csect-name Trace number missing. Must be entered
    Explanation:

    Option 4 has been selected to change the trace number, but the new trace number has not been entered.

    Severity:

    8

    System Action:

    The request is rejected.

    Operator Response:

    Either enter a new trace number (in the range 0 through 199), or choose another option.

    CSQC439D
    cics-applid csect-name Invalid Stop option. Must be 1 or 2
    Explanation:

    The shutdown option number was not a valid value.

    Severity:

    8

    System Action:

    The request is ignored.

    Operator Response:

    Specify either 1 or 2.

    CSQC440D
    cics-applid csect-name Unable to send map map-name mapset CSQCMSH. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    The program was unable to send map map-name from the mapset CSQCMSH to the screen.

    Severity:

    8

    System Action:

    The task is terminated.

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

    CICS Application Programming Reference
    CSQC443D
    cics-applid csect-name Unable to RETURN TRANSID CKRT. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    An attempt to issue an EXEC RETURN TRANSID CKRT command was unsuccessful.

    CICS
    Severity:

    8

    System Action:

    The command is ignored.

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

    CICS Application Programming Reference
    CSQC450E
    cics-applid csect-name Unable to ENTER TRACENUM. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode
    Explanation:

    An attempt to issue an EXEC ENTER TRACENUM command was unsuccessful.

    CICS
    Severity:

    8

    System Action:

    The trace number specified is accepted, but the adapter cannot perform tracing.

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values.

    CICS Application Programming Reference
    CSQC451I
    cics-applid csect-name Nothing to reset. Reset completed
    Explanation:

    A reset request was made, but no values were specified to indicate what should be reset.

    Severity:

    8

    System Action:

    Nothing is reset.

    Operator Response:

    If you want to reset anything, specify values in the required fields.

    CSQC452D
    cics-applid csect-name Invalid input. Reset rejected
    Explanation:

    A request was made to the reset function without using the MQ adapter control panels, but the syntax was incorrect.

    CICS
    Severity:

    8

    System Action:

    The request is ignored.

    System Programmer Response:

    See the for details of the correct syntax.

    WebSphere MQ for z/OS System Administration Guide
    CSQC453I
    cics-applid csect-name Status of connection to qmgr-name is status. number tasks are in-flight
    Explanation:

    This message is issued as the reply to the CKQC DISPLAY request, and gives the status of the connection to queue manager qmgr-name and the number of tasks that are in-flight on that connection.

    Severity:

    0

    CSQC455D
    cics-applid csect-name Unable to WRITEQ TS. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2 EIBRCODE=eibrcode. Queue name is q-name
    Explanation:

    An attempt to issue an EXEC WRITEQ TS command was unsuccessful.

    CICS
    Severity:

    8

    System Action:

    The display function is terminated.

    System Programmer Response:

    The EIB fields contain information about the cause of the problem. See the manual for an explanation of these values, and take the appropriate action.

    CICS Application Programming Reference
    CSQC456I
    cics-applid csect-name No tasks found. Display completed
    Explanation:

    A request was made to display tasks, but there are no current tasks using MQ services.

    Severity:

    0

    CSQC457I
    cics-applid csect-name No CKTI found. Display rejected
    Explanation:

    A request was made to display CKTI, but there were no instances of CKTI started.

    Severity:

    0

    CSQC458D
    cics-applid csect-name Invalid input. Display rejected
    Explanation:

    An attempt was made to request a display function, but not using the MQ adapter control panels. This is not supported.

    CICS
    Severity:

    8

    System Action:

    The request is rejected.

    System Programmer Response:

    Use the MQ adapter control panels to request the display function.

    CICS
    CSQC460I
    cics-applid csect-name Bottom of display
    Explanation:

    An attempt was made to scroll forward, but the bottom of the display has already been reached.

    Severity:

    0

    CSQC461I
    cics-applid csect-name Top of display
    Explanation:

    An attempt was made to scroll backward, but the top of the display has already been reached.

    Severity:

    0

    CSQC462D
    cics-applid csect-name Invalid input. Request rejected
    Explanation:

    An attempt was made to issue the internal transaction CKRT by direct terminal input, or in an otherwise invalid way.

    Severity:

    8

    System Action:

    The request is rejected.

    System Programmer Response:

    Do not use CKRT in this way.

    CSQC470I
    cics-applid csect-name Server subtask (TCB address=address) terminated
    Explanation:

    The MQ adapter is being shut down, and the server task with TCB address address has been terminated.

    CICS
    Severity:

    0

    CSQC471A
    cics-applid csect-name Server subtask (TCB address=address) unable to establish ESTAE, RC=rc
    Explanation:

    The server subtask was trying to establish a z/OS ESTAE but failed with return code rc. This error occurred while the server subtask was undergoing its initialization phase, so no tasks will have been affected.

    CICS
    Severity:

    8

    System Action:

    The server subtask terminates. The MQ adapter continues without that particular server.

    CICS
    System Programmer Response:

    See the to determine the reason why the ESTAE call failed and take appropriate action if possible. Restart the connection using the CKQC transaction.

    MVS Programming: Assembler Services Reference

    If you are unable to resolve the problem, contact your IBM support center.

    CSQC472I
    cics-applid csect-name Server subtask (TCB address=address) connect successful
    Explanation:

    The MQ adapter is starting, and the server task with the TCB address address has made a connection to MQ.

    CICS
    Severity:

    0

    CSQC480I
    cics-applid csect-name MQCC=mqcc MQRC=mqrc QRPL at qrpl-address FRB at frb-address
    Explanation:

    This message is used as the title for an MQ adapter dump if an unexpected error occurs. qrpl-address is the address of the queue request parameter list and frb-address is the address of the function request block.

    CICS
    Severity:

    0

    CSQC481I
    cics-applid csect-name Unexpected error. MQCC=mqcc MQRC=mqrc FRB at frb-address
    Explanation:

    This message is used as the title for an MQ adapter dump if an unexpected error occurs. frb-address is the address of the function request block.

    CICS
    Severity:

    0

    CSQC700I
    transid taskid IBM WebSphere MQ for z/OS version - bridge
    CICS
    Explanation:

    This message is issued when the bridge starts, and shows the release level.

    CICS
    CSQC702I
    transid taskid Monitor initialization complete
    Explanation:

    Bridge monitor initialization completed successfully.

    CSQC703I
    transid taskid Auth=auth-option, WaitInterval=interval, Q=q-name
    Explanation:

    This confirms the bridge monitor start options. Although the WAIT parameter is supplied in seconds, Interval is shown in milliseconds; -1 implies WaitUnlimited.

    CSQC704E
    transid taskid EXEC call error. EIBFN=eibfn EIBRESP=eibresp EIBRESP2=eibresp2
    CICS
    Explanation:

    An error occurred in a call issued by the bridge.

    CICS
    System Programmer Response:

    See the manual for an explanation of eibfn, eibresp, and eibresp2.

    CICS Application Programming
    CSQC705E
    transid taskid Parameter at offset n in input string is invalid
    Explanation:

    The parameter at offset n in the start parameter string for the bridge monitor is invalid. The incorrect parameter is shown in message CSQC784E.

    System Programmer Response:

    Correct the parameter and restart the bridge monitor.

    CSQC706E
    transid taskid Authentication option invalid for this release of CICS
    Explanation:

    The authentication option requested is not supported. CICS/ESA 3.3 only supports the LOCAL and VERIFY_UOW authentication options. Other versions of the bridge can only support LOCAL.

    System Programmer Response:

    Choose a supported authentication option for the release of and restart the bridge monitor.

    CICS
    CSQC707I
    transid taskid Bridge not supported on non-z/OS platforms. Results are unpredictable
    Explanation:

    The bridge is being run on a platform other than z/OS. This might work, but is not supported.

    CSQC708E
    transid taskid Monitor must run at a terminal to use AUTH=VERIFY_UOW on CICS/ESA V3
    Explanation:

    AUTH=VERIFY_UOW was requested. AUTH=VERIFY_UOW on CICS/ESA 3.3 requires that the bridge monitor is run at a terminal.

    System Programmer Response:

    Restart the bridge monitor from a terminal or set AUTH=LOCAL.

    CSQC709E
    transid taskid Preset security not valid for AUTH=VERIFY_UOW on CICS/ESA V3
    Explanation:

    AUTH=VERIFY_UOW was requested. AUTH=VERIFY_UOW on CICS/ESA 3.3 requires that the bridge monitor is run at a terminal, but that terminal might not have preset security.

    System Programmer Response:

    Redefine the terminal, or use a different one, before restarting the bridge monitor, or set AUTH=LOCAL.

    CSQC710E
    transid taskid mq-call failed, MQCC=mqcc MQRC=mqrc
    Explanation:

    An error occurred in an MQ API call issued by the bridge.

    System Programmer Response:

    Refer to for information about mqcc and mqrc.

    Appendix A. API completion and reason codes
    CSQC711E
    transid taskid Unable to open bridge queue, q-name
    Explanation:

    The bridge queue specified is not known to the queue manager.

    System Programmer Response:

    Check the bridge queue is defined correctly and specified on the Q= parameter of the bridge startup for CKBR.

    CSQC712I
    transid taskid Bridge quiescing
    Explanation:

    Bridge monitor quiesce has been initiated. This would normally be because or the queue manager is shutting down or because the operator has set the bridge queue GET(DISABLED).

    CICS
    CSQC713I
    transid taskid Bridge terminated normally
    Explanation:

    Bridge monitor shutdown completed normally.

    CSQC714I
    transid taskid Bridge task starting
    Explanation:

    Bridge monitor is starting.

    CSQC715E
    transid taskid Invalid COMMAREA length length in message
    Explanation:

    The COMMAREA length calculated by the bridge is not valid. It probably exceeds the maximum of 32767. This error can also occur if a negative length was calculated.

    System Programmer Response:

    If OutputDataLength is set within the MQCIH, check it does not exceed 32759 (allowing 8 bytes for the program name). If it is not set, check the total request message length (also allowing 8 bytes for the program name). The length of any MQCIH must not exceed 32767. Note that the length of the MQCIH is taken from the MQCIH length field.

    CSQC716E
    transid taskid MQCIH required for UOW middle and last messages
    Explanation:

    A bridge task has received a message for a second or subsequent MQGET call within a multipart unit of work. The correlation identifier matches the message identifier of the first message within the unit of work, but the message does not contain an MQCIH. The unit of work is backed out.

    System Programmer Response:

    Make sure that all messages within a multipart unit of work contain an MQCIH and rerun the unit of work.

    CSQC717E
    transid taskid UOW first or only received when UOW middle or last expected
    Explanation:

    A bridge task has received a message for a second or subsequent MQGET call within a multipart unit of work. The correlation identifier matches the message identifier of the first message within the unit of work, but the UOWControl field within the MQCIH is invalid. It is set to MQCUOWC_FIRST or MQCUOWC_ONLY when MQCUOWC_MIDDLE, MQCUOWC_LAST, MQCUOWC_COMMIT, or MQCUOWC_BACKOUT is required. The unit of work is backed out.

    System Programmer Response:

    Correct the UOWControl field and rerun the unit of work.

    CSQC718E
    transid taskid UOW middle or last received when UOW first or only expected
    Explanation:

    The bridge monitor has received a request message for a new unit of work, the correlation identifier is set to MQCI_NEW_SESSION but the UOWControl field within the MQCIH is set to something other than MQCUOWC_FIRST or MQCUOWC_ONLY.

    System Programmer Response:

    Correct the UOWControl field and rerun the unit of work.

    CSQC720E
    transid taskid Authentication option IDENTIFY or VERIFY_ requires a security manager to be active
    Explanation:

    An attempt has been made to start the bridge monitor with AUTH=IDENTIFY or VERIFY_ but security is not active for the system.

    CICS
    System Programmer Response:

    Activate security, or choose a different authentication option.

    CSQC721E
    transid taskid Invalid MQCIH
    Explanation:

    A message has been received by the bridge with an MQMD format field of MQFMT_CICS but the data does not begin with a valid MQCIH. Either the , Version, or is incorrect.

    StrucIdStrucLength
    System Programmer Response:

    Check the version of the header and compare with the level supported by the bridge. Correct the format or the user data as appropriate.

    CSQC724E
    transid taskid Bridge queue q-name not defined as local
    Explanation:

    The bridge queue specified is not defined as a local queue.

    System Programmer Response:

    Redefine the bridge request queue as a local queue.

    CSQC725I
    transid taskid Messages on bridge queue are not persistent by default
    Explanation:

    The bridge queue is defined with DEFPSIST(NO). Request messages should be persistent to guarantee that they will be processed. The message is for information only.

    CSQC726I
    transid taskid Bridge queue backout count not hardened
    Explanation:

    The bridge queue is defined with NOHARDENBO.

    System Programmer Response:

    Alter the queue definition to set HARDENBO. The queue should be defined with HARDENBO to ensure that the bridge does not try to process a unit of work a second time following a emergency restart.

    CICS
    CSQC727I
    transid taskid Bridge queue defined with MSGDLVSQ(PRIORITY), but should be for efficiency
    FIFO
    Explanation:

    The bridge queue is defined with PRIORITY message delivery sequence. Processing of high priority messages could be delayed if they are added to the queue ahead of the bridge monitor's browse cursor.

    System Programmer Response:

    Alter the queue definition to set MSGDLVSQ().

    FIFO
    CSQC728E
    transid taskid Bridge queue already open. Check no CKBR or bridge tasks are active for this queue
    Explanation:

    An MQINQ call for the bridge queue found that another process had the queue open for input. This is not allowed when the bridge monitor starts.

    System Programmer Response:

    Check that no bridge monitor task (CKBR) is already active for this queue. Message CSQC703I can be used to check which queue a bridge monitor is servicing. If no bridge monitor is active, check if any bridge tasks that were started by a previous bridge monitor are still active (see CSQC743I messages).

    CSQC729I
    transid taskid No defined to queue manager
    dead-letter queue
    Explanation:

    There is no defined to the queue manager. The bridge will be terminated if any error occurs that would result in a message being sent to the .

    dead-letter queuedead-letter queue
    System Programmer Response:

    Alter the queue manager to define a if dead-letter processing is required.

    dead-letter queue
    CSQC730I
    transid taskid Unable to open , MQRC=mqrc
    dead-letter queue
    Explanation:

    The defined to the queue manager could not be opened. The bridge will be terminated if any error occurs that would result in a message being sent to the .

    dead-letter queuedead-letter queue
    System Programmer Response:

    Refer to for information about mqrc.

    Appendix A. API completion and reason codes
    CSQC731I
    transid taskid Unable to inquire on , MQRC=mqrc
    dead-letter queue
    Explanation:

    An MQINQ call on the failed. The bridge will be terminated if any error occurs that would result in a message being sent to the .

    dead-letter queuedead-letter queue
    System Programmer Response:

    Refer to for information about mqrc.

    Appendix A. API completion and reason codes
    CSQC732I
    transid taskid Unable to put message to , MQRC=mqrc
    dead-letter queue
    Explanation:

    An MQPUT to the failed. If this error occurs in a bridge task, the unit of work is backed out. If this error occurs in the bridge monitor, it will be abnormally terminated.

    dead-letter queue
    System Programmer Response:

    Refer to for information about mqrc.

    Appendix A. API completion and reason codes
    CSQC733I
    transid taskid not defined with USAGE(NORMAL)
    Dead-letter queue
    Explanation:

    The is not defined correctly. The bridge will be terminated if any error occurs that would result in a message being sent to the .

    dead-letter queuedead-letter queue
    System Programmer Response:

    Ensure the is not defined as a transmission queue.

    dead-letter queue
    CSQC734I
    transid taskid max message length length is too small
    Dead-letter queue
    Explanation:

    The maximum message length allowed for the is less than the size of the dead-letter header, MQDLH. The bridge will be terminated if any error occurs that would result in a message being sent to the .

    dead-letter queuedead-letter queue
    System Programmer Response:

    Increase the of the to at least the size of the MQDLH but, to be effective, make it large enough to hold the largest request message expected plus the MQDLH.

    MAXMSGLdead-letter queue
    CSQC735I
    transid taskid or queue manager quiesced before bridge task started
    CICS
    Explanation:

    The bridge task received a quiescing return code from an MQOPEN call of the request queue or an MQGET call for the first message within a unit of work.

    The request will be processed when , the queue manager, or the bridge monitor are restarted.

    CICS
    CSQC736I
    transid taskid Bridge quiesced before task started
    Explanation:

    The bridge quiesced before a bridge task could get the first message within a unit of work.

    The request will be processed when the bridge monitor is restarted.

    CSQC737E
    transid taskid or queue manager quiesced, bridge task backed out
    CICS
    Explanation:

    The bridge task received a quiescing return code from an MQGET for a second or subsequent message within a unit of work. The unit of work is backed out and the bridge task terminated.

    System Programmer Response:

    Rerun the unit of work.

    CSQC738E
    transid taskid Bridge quiesced, task backed out
    Explanation:

    The bridge task quiesced while a bridge task was waiting to get a second or subsequent message within a unit of work because the queue was not enabled for getting messages. The unit of work is backed out and the bridge task terminated.

    System Programmer Response:

    Rerun the unit of work.

    CSQC739E
    transid taskid Bridge terminated, timeout interval expired before middle or last UOW message received
    Explanation:

    The bridge task did not receive a second or subsequent message for a unit of work within the wait interval specified (or as overridden on the first request for the unit of work) at bridge monitor startup.

    System Programmer Response:

    Either:

  • Increase the WAIT parameter on bridge monitor startup.

  • Correct the program that failed to send a subsequent request for a unit of work.

  • Set the UOWControl field correctly for the previous request.

    • CSQC740E
    transid taskid Client application requested backout
    Explanation:

    The bridge task backed out a unit of work on receipt of a MQCUOWC_BACKOUT request.

    CSQC745E
    transid taskid Unable to put message to reply queue, MQRC=mqrc
    Explanation:

    An MQPUT call to the reply-to queue failed.

    System Action:

    The response message will be sent to the .

    dead-letter queue
    System Programmer Response:

    Refer to for information about mqrc.

    Appendix A. API completion and reason codes
    CSQC746E
    transid taskid Invalid CCSID, ccsid expected, ccsid received
    Explanation:

    A request message was received with an invalid value for the CCSID field in the MQMD.

    System Programmer Response:

    Correct the MQMD and reissue the request.

    CSQC747E
    transid taskid Invalid encoding, encoding expected, encoding received
    Explanation:

    A request message was received with an invalid value for the encoding field in the MQMD.

    System Programmer Response:

    Correct the MQMD and reissue the request.

    CSQC748E
    transid taskid Message removed from the request queue during backout processing
    Explanation:

    The bridge has sent this request message to the during backout processing.

    dead-letter queue
    System Programmer Response:

    See the associated messages to determine the cause of the problem.

    CSQC749E
    transid taskid Authentication error, userid user-id
    Explanation:

    The bridge monitor is being run with AUTH=VERIFY_UOW or AUTH=VERIFY_ALL. An EXEC SIGNON or EXEC CICS VERIFY command failed.

    CICSPASSWORD
    System Programmer Response:

    Check that the correct was specified, and that the appropriate authorizations are defined for it.

    user ID
    CSQC750E
    transid taskid Bridge monitor internal error
    Explanation:

    An unexpected condition was detected by the bridge.

    System Programmer Response:

    Contact your IBM support center if the problem persists.

    CSQC751E
    transid taskid Unable to LINK to program program-name, EIBRESP=eibresp EIBRESP2=eibresp2
    Explanation:

    An EXEC LINK command for the user requested program failed.

    CICS
    System Programmer Response:

    See the manual for an explanation of eibresp and eibresp2.

    CICS Application Programming
    CSQC752E
    transid taskid Bridge queue cannot be used for reply-to queue
    Explanation:

    The in a request message is the same as the bridge-request queue name. This is not allowed.

    reply-to queue name
    System Programmer Response:

    Specify a different reply-to queue in the request.

    CSQC753E
    transid taskid Message has been processed previously and returned to the queue using backout
    Explanation:

    The bridge already attempted to process this request but the request failed and was backed out. This could be because backout processing failed for a bridge task that ended abnormally or because there was a failure while this request was in progress. No attempt is made to process the request a second time.

    CICS
    System Programmer Response:

    Look at previous error messages for this message on the CSMT log to determine the cause for the previous failure, and rerun the request.

    CSQC754E
    transid taskid Bridge task abend abend-code in program program-name
    Explanation:

    A bridge task terminated abnormally.

    System Programmer Response:

    The associated transaction dump can be used to assist problem determination. Correct the problem and rerun the unit of work. If the program name begins with CSQCB and the problem persists, contact your IBM support center.

    CSQC755E
    transid taskid Bridge queue is not shareable
    Explanation:

    The bridge request queue does not have the SHARE attribute.

    System Programmer Response:

    Alter the queue definition and restart the bridge monitor.

    CSQC756E
    transid taskid not defined as local
    Dead-letter queue
    Explanation:

    The is not defined as a local queue. The bridge will be terminated if any error occurs that would result in a message being sent to the .

    dead-letter queuedead-letter queue
    System Programmer Response:

    Redefine the as a local queue.

    dead-letter queue
    CSQC757E
    transid taskid Unable to open reply-to queue, q-name MQRC=mqrc
    Explanation:

    The reply-to queue specified is not known to the queue manager.

    System Programmer Response:

    Refer to for information about mqrc. Check you have provided the necessary queue definitions.

    Appendix A. API completion and reason codes
    CSQC758E
    transid taskid Unable to START bridge task, userid user-id not authorized. EIBRESP=eibresp EIBRESP2=eibresp2
    Explanation:

    The bridge monitor is being run with the IDENTIFY or VERIFY authorization option. An EXEC START command for the bridge task failed with NOTAUTH or USERIDERR because the is not authorized to start bridge transactions or has been revoked.

    CICSuser ID
    System Programmer Response:

    See the manual for an explanation of eibresp and eibresp2. Correct the security definitions if this userid should be authorized to run requests using the bridge.

    CICS Application Programming
    CSQC759E
    transid taskid Transaction transid not defined to CICS
    Explanation:

    An request has been received to run the transaction listed but it is not defined to this system.

    CICS
    System Programmer Response:

    Correct the request or define the transaction.

    CSQC760I
    transid taskid MsgId=MsgId
    Explanation:

    This message gives the identifier of a message to which a previous error message relates.

    System Programmer Response:

    See the associated message.

    CSQC761I
    transid taskid CorrelId=CorrelId
    Explanation:

    This message gives the correlation identifier of a message to which a previous error message relates.

    System Programmer Response:

    See the associated message.

    CSQC762I
    transid taskid Queue name q-name
    Explanation:

    This message gives the name of the queue to which a previous error message relates.

    System Programmer Response:

    See the associated message.

    CSQC763I
    transid taskid Queue manager queue-manager-name
    Explanation:

    This message gives the name of the queue manager to which a previous error message relates.

    System Programmer Response:

    See the associated message.

    CSQC764E
    transid taskid Invalid userid, user-id expected, user-id received
    Explanation:

    A is required in all request messages when AUTH=VERIFY_ALL is being used; this must be the same for all requests within a unit of work. This message is issued because the bridge task detected a missing or changed .

    user IDuser ID
    System Programmer Response:

    Correct the and rerun the unit of work.

    user ID
    CSQC766I
    transid taskid Bridge queue not defined with INDXTYPE(CORRELID)
    Explanation:

    The bridge queue should be defined with an index type of CORRELID. This is required if the queue is a and stongly recommended for private queues.

    shared queue
    System Action:

    If the bridge queue is shared, the bridge monitor does not start. Otherwise, processing continues.

    System Programmer Response:

    Alter the queue definition to specify the required index type and restart the bridge monitor.

    CSQC767I
    transid taskid Unable to open backout-requeue queue, MQRC=mqrc
    Explanation:

    The backout-requeue queue defined to the bridge queue could not be opened.

    System Action:

    Messages will be sent to the instead.

    dead-letter queue
    System Programmer Response:

    Refer to for information about mqrc.

    Appendix A. API completion and reason codes
    CSQC768E
    transid taskid Backout-requeue queue not defined as local
    Explanation:

    The backout-requeue queue is not defined as a local queue.

    System Action:

    Messages will be sent to the instead.

    dead-letter queue
    System Programmer Response:

    Redefine the backout-requeue queue as a local queue.

    CSQC769I
    transid taskid Unable to inquire on backout-requeue queue, MQRC=mqrc
    Explanation:

    An MQINQ call on the backout-requeue queue failed.

    System Action:

    Messages will be sent to the instead.

    dead-letter queue
    System Programmer Response:

    Refer to for information about mqrc.

    Appendix A. API completion and reason codes
    CSQC770I
    transid taskid Backout-requeue queue not defined with USAGE(NORMAL)
    Explanation:

    The backout-requeue queue is not defined correctly.

    System Action:

    Messages will be sent to the instead.

    dead-letter queue
    System Programmer Response:

    Ensure the backout-requeue queue is not defined as a transmission queue.

    CSQC771I
    transid taskid Unable to put message to backout-requeue queue, MQRC=mqrc
    Explanation:

    An MQPUT to the backout-requeue queue failed.

    System Action:

    Messages will be sent to the instead.

    dead-letter queue
    System Programmer Response:

    Refer to for information about mqrc.

    Appendix A. API completion and reason codes
    CSQC772E
    transid taskid Invalid FacilityLike value (xxx) in message
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_FACILITYLIKE_INVALID, because the FacilityLike field of the MQCIH header in the input message was invalid. It must correspond to an installed terminal that is to be used as a model for the bridge facility.

    CICS
    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Correct the FacilityLike field to specify the name of a terminal installed on the system or install a terminal with the required name.

    CICS
    CSQC773E
    transid taskid Invalid or expired Facility token in message
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_INVALID_FACILITYTOKEN or BRIHRC_FACILITYTOKEN_IN_USE, because the Facility field of the MQCIH header in the input message was invalid. The value must be zero on the first request of a sequence of 3270 bridge messages, and the value that is returned in the reply message must then be used in subsequent messages. The token expires after the time specified in the FacilityKeepTime field of the first message. The token cannot be used by more than one sequence of bridge messages.

    CICS
    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Check the application to ensure that the correct Facility token is being used and that it has not expired. If necessary, increase the FacilityKeepTime so that the token does not expire before the sequence of messages has been processed.

    CSQC774E
    transid taskid Unable to start transaction on system sys-name
    CICS
    Explanation:

    The RemoteSysId field of the MQCIH message header is non-blank, but the specified name sys-name is not known to or there is no active connection to that remote system.

    CICSCICS
    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Ensure that the specified system is running and that there is an active Intersystem communication connection to it from the system running the bridge monitor.

    CICSCICS
    CSQC775I
    transid taskid Unable to start transaction on this system
    CICS
    Explanation:

    The RemoteSysId field of the MQCIH message header is blank, but the specified Facility token is not known to . The bridge monitor does not know which system allocated the token and so leaves the message on the queue for another bridge monitor to process. If the token is invalid or expired this may result in the message never being processed.

    CICSCICS
    System Programmer Response:

    Ensure that the RemoteSysId field of all messages except the first of a sequence contains the RemoteSysId returned in the previous reply message. This will ensure messages are routed directly to the correct region, improve performance, and prevent the possibility of unprocessed messages.

    CICS
    CSQC776E
    transid taskid Invalid FacilityKeepTime value (nnn) in message
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_INVALID_KEEPTIME, because the FacilityKeepTime field of the MQCIH message header was zero or greater than the maximum allowed keep time (as controlled by the BRMAXKEEPTIME system initialization parameter).

    CICSCICS
    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Ensure that the FacilityKeepTime field of the first message in a 3270 transaction sequence contains a value within the valid range.

    CSQC777E
    transid taskid Link3270 error, RC=code
    Explanation:

    The Link3270 program DFHL3270 returned an unexpected return code.

    CICS
    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Use the COBOL copy book DFHBRIHO to find the symbolic name of the return code from the numeric value code reported in the message. Then refer to 'BRIH-RETURNCODE values' in the to determine the meaning of the return code from DFHL3270. Correct the input message accordingly.

    CICSCICS External Interfaces Guide
    CSQC778E
    transid taskid Abend abend-code in transaction tran-id
    Explanation:

    A abend occured in a transaction running under the link bridge.

    CICSCICS
    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Determine the cause of the abend and correct the underlying problem using normal diagnostic techniques.

    CICS
    CSQC779E
    transid taskid Mapset does not match, mapset-id expected, mapset-id received
    Explanation:

    The mapset name in a receive map vector does not match the name requested. The bridge task cannot interpret the application data structure.

    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Ensure the mapset name in the input message matches the name expected by the transaction and returned in the preceding receive map request vector.

    CICS
    CSQC780E
    transid taskid Map name does not match, map-id expected, map-id received
    Explanation:

    The map name in a receive map vector does not match the name requested. The bridge task cannot interpret the application data structure.

    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Ensure the map name in the input message matches the name expected by the transaction and returned in the preceding receive map request vector.

    CICS
    CSQC781E
    transid taskid Invalid bridge vector
    Explanation:

    The bridge input vector was invalid. Possible errors are:

  • The vector length is greater than the message length

  • The vector type is not recognized

  • A field length is greater than its defined length

  • A field input data length is greater than the defined length of the field

    • The ErrorOffset field of the MQCIH header indicates the position within the message where the error was detected (although the actual error may have caused by a problem earlier in the message).

    System Action:

    The input messages are backed out to the backout-requeue queue or dead-letter queue.

    System Programmer Response:

    Ensure the map name in the input message matches the name expected by the transaction and returned in the preceeding receive map request vector.

    CICS
    CSQC782E
    transid taskid File DFHBRNSF not available
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_DHFBRNSF_UNAVAILABLE, because the bridge facility name space file, DFHBRNSF, was not available for use by .

    CICSCICSCICS
    System Action:

    The input messages are backed out to the backout-requeue queue or .

    dead-letter queue
    System Programmer Response:

    Ensure the DFHBRNSF file is defined and avaliable to .

    CICS

    For information about defining this file, see 'Defining the bridge facility' in the .

    CICS External Interfaces Guide
    CSQC783I
    transid taskid Msg=msgdest, PassTktA=applid
    Explanation:

    This confirms the bridge monitor start options.

    CSQC784E
    transid taskid Input=parm_string
    Explanation:

    An error was found in the bridge start input parameters. parm_string shows the input parameters starting at the point where the error was detected.

    System Programmer Response:

    Correct the parameter in error and restart the bridge monitor.

    CSQC785E
    transid taskid Link3270 routing failed - not supported by system
    CICS
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_ROUTING_BACKLEVEL_CICS, because the Link3270 request was routed to a system that does not support Link3270.

    CICSCICS
    System Programmer Response:

    Correct the transaction routing definitions. The target system must be CICS Transaction Server V2 Release 2 or higher.

    CICSCICS

    For information about Link3270 see 'Bridging to 3270 transactions' in the .

    CICS External Interfaces Guide
    CSQC786E
    transid taskid Link3270 routing failed - connection error
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_ROUTING_CONNECTION, because a connection error did not allow the Link3270 request to be routed to the remote region.

    CICS
    System Programmer Response:

    Correct the transaction routing definitions. The target system must be active and connected.

    CICSCICS

    For information about Link3270 see 'Bridging to 3270 transactions' in the .

    CICS External Interfaces Guide
    CSQC787E
    transid taskid Link3270 routing failed - TERMERR
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_ROUTING_TERMERR, because the EXEC LINK from the DFHL3270 to the target region failed with TERMERR.

    CICSCICS
    System Programmer Response:

    Correct the transaction routing definitions.

    CICS

    For information about Link3270 see 'Bridging to 3270 transactions' in the .

    CICS External Interfaces Guide
    CSQC788E
    transid taskid Link3270 routing failed - TRANDEF error
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_ROUTING_TRANDEF_ERROR, because the TRANSACTION resource definition in the routing region did not allow the transaction to be routed to the chosen target region.

    CICS
    System Programmer Response:

    Correct the transaction routing definitions.

    CICS

    For information about Link3270 see 'Bridging to 3270 transactions' in the .

    CICS External Interfaces Guide
    CSQC789E
    transid taskid Link3270 routing failed - URM error, RC=code =compcode
    CompCode
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_ROUTING_URM_LINK_FAILED or BRIHRC_ROUTING_URM_REJECTED, because the link to the dynamic routing User Replaceable Module (URM) failed or was rejected by the URM.

    CICS
    System Programmer Response:

    Correct the transaction routing definitions.

    CICS

    For information about the codes code and compcode from Link3270 see 'BRIH-RETURNCODE values' in the .

    CICS External Interfaces Guide
    CSQC790E
    transid taskid Transaction not running
    Explanation:

    The Link3270 program DFHL3270 returned code BRIHRC_TRANSACTION_NOT_RUNNING, because there was no transaction currently running on the bridge facility so the data from the MQ message could not be passed to the transaction.

    CICS
    System Programmer Response:

    Check the state of the system.

    CICS

    For information about Link3270 see 'Bridging to 3270 transactions' in the .

    CICS External Interfaces Guide
    CSQC791E
    transid taskid Invalid header format found in message
    Explanation:

    The length field in the header is less than the minimum header length or greater than the actual message message length.

    System Programmer Response:

    Ensure that the input message contains only valid MQ headers. Only MQH-type headers with standard header-chaining fields may appear in a bridge message before the MQCIH header and/or application data.