CKTI has attempted to retrieve data from a CICS START command, but the retrieve was unsuccessful.
8
CKTI ends.
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.
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.
8
CKTI ends.
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.
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).
8
The trigger message is sent to the dead-letter queue. CKTI processes the next message.
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.
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.
4
The trigger message is sent to the dead-letter queue. CKTI processes the next message.
Check the header of the message on the dead-letter queue. This will tell you where the trigger message came from. Correct the process that created the trigger message.
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.
4
The trigger message is sent to the dead-letter queue. CKTI processes the next message.
Check the header of the message on the dead-letter queue. This will tell you where the trigger message came from. Correct the process that created the trigger message.
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.
4
The trigger message is sent to the dead-letter queue. CKTI processes the next message.
Check the header of the message on the dead-letter queue. This will tell you where the trigger message came from. Correct the process that created the trigger message.
An attempt to issue an MQGET call on the initiation queue has been unsuccessful.
8
CKTI ends.
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.
A request to end CKTI has been sent from the MQ CICS adapter. This is a normal completion of CKTI.
0
CKTI ends.
An attempt has been made to start CKTI, but not from CKCN or CKSQ. This is not allowed.
8
CKTI ends.
Start CKTI from either CKCN or CKSQ.
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.
8
An implicit close of the queue will take place when the transaction ends.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.
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.
8
This message is issued if the transaction CKTI receives a trigger message that does not match the MQTM control block.
8
The message is sent to the dead-letter queue.
Look at the message on the dead-letter queue to establish why it did not match MQTM.
An MQOPEN call has been unable to open a queue. This message is followed by message CSQC110I indicating the name of the queue.
8
CKTI ends.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.
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.
0
Processing continues.
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).
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.
8
CKTI ends.
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.
An MQOPEN call to the queue manager was unsuccessful.
8
CKTI ends.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.
An MQINQ call to the queue manager was unsuccessful.
8
CKTI ends.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.
This message follows message CSQC113I, indicating the hexadecimal identifier of the message that could not be processed.
0
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.
8
The trigger message is sent to the dead-letter queue, and CKTI continues processing the next message.
Investigate the reason for the IRC failure.
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.
8
CKTI ends.
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.
A dead-letter queue has not been defined for the queue manager.
8
The trigger message is discarded, and the process cannot be started.
Define a dead-letter queue if one is required.
CKTI was unable to close the queue manager after inquiring about the dead-letter queue.
8
CKTI ends.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem.
The dead-letter queue defined was not of type local. This message is followed by message CSQC110I, indicating the name of the queue.
8
The message is not put to the dead-letter queue.
Define the dead-letter queue as a local queue.
The dead-letter queue defined is not of usage type normal. This message is followed by message CSQC110I, indicating the name of the queue.
8
The message is not put to the dead-letter queue.
Define the dead-letter queue to have usage type normal.
An attempt to link to CSQCPARM was unsuccessful.
8
The connection process terminates, and control returns to CICS.
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.
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).
8
The connection process terminates, and control returns to CICS.
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.
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.
8
The connection process terminates, and control returns to CICS.
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.
A connection has been made to MQ, but CKTI cannot be started as no initiation queue name has been specified.
0
The queue manager is connected, but CKTI is not started.
Use the MQ CICS adapter control panels (the CKQC transaction) to start CKTI.
Add the initiation queue name to INITPARM statement if you want to start CKTI automatically next time you connect CICS to MQ.
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.
8
The connection process terminates, and control returns to CICS.
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.
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.
8
The connection process terminates, and control returns to CICS.
Use the MQ CICS adapter control panels (the CKQC transaction) to specify the correct initiation queue name, and retry the connection process.
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.
0
The queue manager is connected with a trace number of 0.
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.
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.
4
The queue manager is connected with a trace number of 0.
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.
An attempt to link to CSQCCON was unsuccessful.
8
The connection process terminates, and control returns to CICS.
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.
An attempt to link to CSQCQCON was unsuccessful.
8
The connection process terminates, and control returns to CICS.
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.
The CICS adapter is unable to receive input from the CKQC transaction.
8
The requested function is not performed.
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.
An attempt was made to issue an EXEC CICS RETURN TRANSID tran-id IMMEDIATE command, but it was unsuccessful.
8
The function terminates, and control returns to CICS.
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.
CICS cannot determine the identifier of the screen currently displayed. Because of this, it cannot interpret the screen contents (including any input fields).
8
The input is ignored, and the transaction finishes.
Resubmit CKQC to restart from the beginning of the CICS transaction.
If this problem occurs frequently, contact your IBM support center for help.
The display function was requested; this function can only be used from the MQ CICS adapter control panels (the CKQC transaction).
8
The request is ignored.
Use the MQ CICS adapter control panels to access the display functions.
The MQ CICS adapter control panels (the CKQC transaction) are not supported on the console.
8
The panel request is ignored.
Use a 3270 device to display the MQ CICS adapter control panels.
CKQC could not display the panel because it could not link to CSQCBASE.
8
CKQC ends.
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.
The request was issued by a task that was not associated with a terminal. This is not allowed.
8
The request is ignored.
Reissue the request from a task that has a 3270 device or console associated with it.
The system cannot receive input from the screen.
8
The input is ignored, and the transaction is finished.
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.
A connection request was issued with incorrect parameters specified.
8
The request is ignored.
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.
A request was made by a task that is not associated with a console or 3270 device.
8
The request is ignored.
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.
An attempt has been made to connect to MQ, but CICS is shutting down so the connection request has been rejected.
8
The connection process terminates, and control returns to CICS.
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.
8
The connection process terminates, and control returns to CICS.
To connect to the new queue manager, shut down the current connection and reissue the connection request.
The CICS API exit program CSQCAPX has been activated.
0
An attempt to issue an EXEC CICS EXTRACT EXIT CSQCTRUE command was unsuccessful.
8
The function terminates, and control returns to CICS.
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).
Module CSQCSERV has been loaded. address is the address of the entry point. You might find this information useful during problem determination.
0
An attempt to issue an EXEC CICS ENABLE CSQCTRUE command was unsuccessful during a connect process.
8
The connection process terminates, and control returns to CICS.
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.
An attempt to issue an EXEC CICS INQUIRE MAXTASKS command was unsuccessful.
8
The connection process terminates, and control returns to CICS.
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.
During the connection process, the MQ CICS adapter was unable to start CKTI.
8
The queue manager is connected, but CKTI is not started.
Issue the CKQC transaction, and use the panels to start CKTI after the cause of the problem has been corrected.
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.
The connection to queue manager qmgr-name was successful.
0
An attempt to connect to queue manager (qmgr-name) was unsuccessful because qmgr-name was not active.
0
The connection will be made when qmgr-name becomes active.
Check that you entered the correct queue manager name (qmgr-name). If required, either:
An attempt to connect to queue manager qmgr-name was unsuccessful.
8
The connection process terminates, and control returns to CICS.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc, and take the appropriate action.
An attempt to connect to a queue manager was unsuccessful because the queue manager is already connected.
8
The connection process terminates, and control returns to CICS.
During the connection process, the MQ CICS adapter was unable to start the alert monitor CKAM.
8
The queue manager is connected, but CKAM is not started so the function of the MQ CICS adapter is restricted.
Without the alert monitor, the MQ CICS adapter is unable to perform the following functions:
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.
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.
The MQ CICS adapter was unable to obtain storage for the CLOC control block.
8
The connection request is rejected.
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.
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.
The units of work will be resolved by the distributed queuing component when remote queuing starts.
0
See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt CICS unit of work.
This message appears when there are unresolved in-doubt units of work. Refer to message CSQC313I.
0
The MQ CICS 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.
8
The API-crossing exit is not used.
The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. If you are trying to use the API-crossing exit, use the data contained in these fields to resolve the problem.
This message is displayed if too many messages have been issued to be displayed on the screen.
0
Check the console for further messages.
This message is issued at connection time. The unit of work shown is in doubt.
0
See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt CICS unit of work.
An attempt to issue an EXEC CICS INQUIRE SYSTEM RELEASE command was unsuccessful.
8
The connection process terminates, and control returns to CICS.
The EIB fields contain information about the cause of the problem. See the CICS System Programming Reference manual for an explanation of these values, and take the appropriate action.
The version of CICS that you are running is not supported by the version of the MQ CICS adapter that you are using.
8
The connection process terminates, and control returns to CICS.
An attempt was made to shut down a connection, but there was no connection active. This could be caused by one of the following:
8
The request is ignored, and control returns to CICS.
A request to shut down the MQ CICS adapter was made, but it was rejected because the syntax of the shutdown request was not valid.
8
The request is ignored.
Issue the request again. See the WebSphere MQ for z/OS System Administration Guide for details of the correct syntax.
The request to connect or disconnect was received from terminal termid. The originating transaction was tranid (this could be CKAM). userid is the user ID of the operator who used the terminal to initiate the operation. This message is issued on the console for audit trail purposes.
0
A request to shut down the MQ CICS adapter was made, but it was rejected because a STOP FORCE shutdown had already been requested.
8
The request is ignored.
The version of CICS Transaction Server that you are running is not supported by the version of the MQ CICS adapter that you are using .
8
The connection process terminates, and control returns to CICS.
The MQ CICS adapter has been shut down. However, it was not able to disconnect from MQ (for example, because the queue manager had already shut down).
4
Look for other messages explaining why the MQ CICS adapter could not disconnect from MQ.
A request was made to shut down the MQ CICS adapter, but the queue manager has already shut down. For example, the operator shuts down both the queue manager and the MQ CICS adapter simultaneously. If the queue manager stops first, it cannot receive the disconnect request from the CICS adapter.
0
The adapter shutdown process continues.
If the queue manager is already shut down, you can ignore this message. Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc, and take the appropriate action.
A request has been made to disconnect from queue manager qmgr-name but it was unsuccessful.
8
The adapter shutdown process continues.
If the queue manager is already shit down, you can ignore this message. Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc, and take the appropriate action.
The shutdown process has completed successfully.
0
The command request was received from a PLT program. This message is issued on the console for audit trail purposes.
0
The request to shut down the MQ CICS 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.
0
Request request was received from the alert monitor (CKAM). This message is issued on the console for audit trail purposes.
0
The MQ CICS 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.
0
The API-crossing exit is not used.
If you wish to use the API-crossing exit:
The MQ CICS 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.
0
The API-crossing exit is not used.
If you wish to use the API-crossing exit:
An attempt to issue an EXEC CICS RETRIEVE RTRANSID was unsuccessful (for example, an unauthorized user has tried to start the alert monitor).
8
Processing continues (including the alert monitor if one is already running).
The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values.
An attempt was made to start the alert monitor by an unrecognized transaction.
8
The request is ignored.
An attempt to issue an EXEC CICS EXTRACT EXIT CSQCTRUE command was unsuccessful.
8
The alert monitor terminates.
The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values. Take the appropriate action, and use the MQ CICS adapter control panels (the CKQC transaction) to restart the MQ CICS adapter.
An attempt to perform an EXEC CICS WAIT EXTERNAL was unsuccessful.
8
The alert monitor terminates.
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.
There are no remaining active or deferred connections, so the alert monitor has terminated.
0
The alert monitor has detected that a deferred connection has been activated, but it cannot link to CSQCQCON.
8
The connection process is terminated, and control returns to CICS.
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 MQ CICS adapter control panels (the CKQC transaction) to make the connection.
The alert monitor has detected that the MQ CICS adapter is ready to shut down but cannot link to CSQCDSC.
8
The disconnection process is continued, and control returns to CICS.
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 MQ CICS adapter control panels (the CKQC transaction) to disconnect from MQ.
A pending event was not of the type expected by the alert monitor.
8
The pending event is discarded.
If this problem occurs frequently, collect the following diagnostic items, and contact your IBM support center for help:
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.)
8
The event is not processed until one of the other 99 events has expired.
If you want to clean up the system, shut down and restart CICS.
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.
8
The request is ignored.
Establish a connection, and reissue the request.
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.
8
The request is ignored.
Specify the queue name explicitly.
If you require a default queue name, specify one when you perform the connection process. See the WebSphere MQ for z/OS System Administration Guide for information about how to achieve this.
An attempt was made to start CKTI specifying the name of an initiation queue that is used by another CKTI being started.
8
The request is ignored.
Review the console for messages in the range CSQC100D through CSQC109D for further information, or use CICS operator commands (for example CEMT INQ TASK) to determine why the CKTI started earlier is not running.
An attempt was made to start CKTI specifying the name of an initiation queue that is already used by a CKTI which is still running.
8
The reqeust is ignored.
If required, use the MQ CICS adapter control panels (the CKQC transaction) to stop the existing CKTI, and restart.
Either:
8
The request is ignored.
Wait until the initiation queue has stopped, and then reissue the start request if required.
An attempt to stop CKTI was unsuccessful because the queue name specified was not found. This is because either:
8
The request is ignored.
Verify the name of the initiation queue, and reissue the request if necessary.
The MQ CICS adapter has processed the command request. However, the CICS 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.
0
The syntax of the CICS adapter request entered was incorrect.
8
The request is rejected.
See the WebSphere MQ for z/OS System Administration Guide for details of the correct syntax, or use the MQ CICS adapter control panels (the CKQC transaction) to request the function.
This message is issued to show which version of CICS Transaction Server you are using.
0
This message gives the connection name and the identifier of a unit of work and appears with one of the following messages:
You can use the connection name when using MQ commands (for example, RESOLVE INDOUBT).
0
The syncpoint coordinator has informed MQ that the unit of work indicated by the accompanying CSQC400I message has been committed.
0
The syncpoint coordinator has informed MQ that the unit of work indicated by the accompanying CSQC400I message has been backed out.
0
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.
8
The unit of work remains in doubt.
If you want to resolve the unit of work:
The syncpoint coordinator requested that resolution of the units of work be executed. However, MQ was unable to do this.
8
The units of work remain in doubt.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem. See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt CICS unit of work.
The syncpoint coordinator has been subjected to a cold start, and information regarding units of work has been lost (syncpoint state UERTDGCS). The coordinator cannot inform the MQ CICS adapter whether to commit or back out the unit of work indicated by the accompanying CSQC400I message.
For information about UERTDGCS, see the CICS Customization Guide.
8
The unit of work remains in doubt.
Determine how to resolve the in-doubt unit of work. See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt CICS unit of work.
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 CICS adapter whether to commit or back out the unit of work.
For information about UERTDGNK, see the CICS Customization Guide.
8
The unit of work remains in-doubt.
Determine how to resolve the in-doubt unit of work. See the WebSphere MQ for z/OS System Administration Guide for information about resolving the MQ unit of recovery associated with the in-doubt CICS unit of work.
Total resynchronization was not achieved; some units of work remain in doubt.
0
Action any messages received before this one which indicate units of work that have not been resolved. When there are no more in-doubt units of work you will receive message CSQC409I.
Resynchronization has completed successfully; all units of work have been resolved.
0
CICS has notified the MQ CICS adapter that it is shutting down immediately.
0
The MQ CICS adapter initiates an immediate shutdown. Any in-flight tasks using MQ are backed out when the connection is broken by CICS.
See the WebSphere MQ for z/OS System Administration Guide for more information about MQ CICS adapter shutdown.
CICS has notified the MQ CICS adapter that it has initiated a warm shutdown.
0
The MQ CICS adapter initiates a quiesced shutdown.
See the WebSphere MQ for z/OS System Administration Guide for more information about MQ CICS adapter shutdown.
The MQ CICS adapter detected a CICS abend.
0
The MQ CICS adapter is terminated.
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.
0
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 CICS abend codes, see the relevant CICS Messages and Codes manual.
The task with an identifier of id has been force purged by the operator, and abends with abend-code.
0
The outstanding task has been completed and, because it is not in a must-commit state, the MQ CICS adapter ends the task abnormally. For more information about the CICS abend code, see the CICS Messages and Codes manual.
The task with an identifier of id has been force purged by the operator.
0
The outstanding task has been completed but, because it is in a must-commit state (for example, syncpoint), the MQ CICS adapter does not end the task.
An address (address) passed from an application was out of range for one of the following reasons:
Because of this, the CICS trace facility is unable to trace the area.
0
This message is inserted into the CICS trace, and processing continues.
If the address is in error, correct the application.
This message is issued to show which version of CICS you are using.
0
An attempt to load CSQAVICM was unsuccessful.
8
The process terminates, and control returns to CICS.
The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values.
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.)
0
The task is ended abnormally with code QNST.
The program was unable to send map map-id from the map set CSQCMS to the screen.
8
The task is terminated.
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.
The cursor was not in the correct position when the enter key was pressed.
8
The input is ignored.
Use the tab key to move the cursor to a valid position.
An attempt was made to issue an EXEC CICS RETURN TRANSID CKBM command, but it was unsuccessful.
8
The transaction terminates, and control returns to CICS.
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.
An attempt to transfer control to program pgm-name was unsuccessful.
8
The transaction terminates, and control returns to CICS.
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.
The function key pressed was not valid for this panel.
8
The key is ignored.
Use one of the function keys shown at the bottom of the panel.
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.
8
The request is ignored.
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.
8
The transaction terminates.
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.
The action number specified was out of the range available.
8
The request is ignored.
Specify an action number in the range displayed.
The task number specified was out of the range requested.
8
The request is ignored.
Specify a task number in the range displayed.
The value entered was not 1, 2, 3, or 4.
8
The value is rejected.
Enter a value of either 1, 2, 3, or 4 on the pop-up screen.
The queue manager name was not specified on the connection parameter panel.
8
The connection request is rejected.
Enter the name of the required queue manager on the panel.
If a default name is required, specify the queue manager name in CSQCPARM. See the WebSphere MQ for z/OS System Setup Guide for information about how to do this.
The trace number entered was not numeric.
8
The request is ignored.
Enter a numeric trace number (in the range 0 through 199).
The trace number entered was not in the valid range.
8
The request is ignored.
Enter a trace number in the range 0 through 199.
Option 4 has been selected to change the trace number, but the new trace number has not been entered.
8
The request is rejected.
Either enter a new trace number (in the range 0 through 199), or choose another option.
The shutdown option number was not a valid value.
8
The request is ignored.
Specify either 1 or 2.
The program was unable to send map map-name from the mapset CSQCMSH to the screen.
8
The task is terminated.
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.
An attempt to issue an EXEC CICS RETURN TRANSID CKRT command was unsuccessful.
8
The command is ignored.
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.
An attempt to issue an EXEC CICS ENTER TRACENUM command was unsuccessful.
8
The trace number specified is accepted, but the adapter cannot perform tracing.
The EIB fields contain information about the cause of the problem. See the CICS Application Programming Reference manual for an explanation of these values.
A reset request was made, but no values were specified to indicate what should be reset.
8
Nothing is reset.
If you want to reset anything, specify values in the required fields.
A request was made to the reset function without using the MQ CICS adapter control panels, but the syntax was incorrect.
8
The request is ignored.
See the WebSphere MQ for z/OS System Administration Guide for details of the correct syntax.
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.
0
An attempt to issue an EXEC CICS WRITEQ TS command was unsuccessful.
8
The display function is terminated.
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.
A request was made to display tasks, but there are no current tasks using MQ services.
0
A request was made to display CKTI, but there were no instances of CKTI started.
0
An attempt was made to request a display function, but not using the MQ CICS adapter control panels. This is not supported.
8
The request is rejected.
Use the MQ CICS adapter control panels to request the display function.
An attempt was made to scroll forward, but the bottom of the display has already been reached.
0
An attempt was made to scroll backward, but the top of the display has already been reached.
0
An attempt was made to issue the internal transaction CKRT by direct terminal input, or in an otherwise invalid way.
8
The request is rejected.
Do not use CKRT in this way.
The MQ CICS adapter is being shut down, and the server task with TCB address address has been terminated.
0
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 CICS tasks will have been affected.
8
The server subtask terminates. The MQ CICS adapter continues without that particular server.
See the MVS Programming: Assembler Services Reference to determine the reason why the ESTAE call failed and take appropriate action if possible. Restart the connection using the CKQC transaction.
If you are unable to resolve the problem, contact your IBM support center.
The MQ CICS adapter is starting, and the server task with the TCB address address has made a connection to MQ.
0
This message is used as the title for an MQ CICS 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.
0
This message is used as the title for an MQ CICS adapter dump if an unexpected error occurs. frb-address is the address of the function request block.
0
This message is issued when the CICS bridge starts, and shows the release level.
Bridge monitor initialization completed successfully.
This confirms the bridge monitor start options. Although the WAIT parameter is supplied in seconds, Interval is shown in milliseconds; -1 implies WaitUnlimited.
An error occurred in a CICS call issued by the bridge.
See the CICS Application Programming manual for an explanation of eibfn, eibresp, and eibresp2.
The parameter at offset n in the start parameter string for the bridge monitor is invalid. The incorrect parameter is shown in message CSQC784E.
Correct the parameter and restart the bridge monitor.
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.
Choose a supported authentication option for the release of CICS and restart the bridge monitor.
The bridge is being run on a platform other than z/OS. This might work, but is not supported.
AUTH=VERIFY_UOW was requested. AUTH=VERIFY_UOW on CICS/ESA 3.3 requires that the bridge monitor is run at a terminal.
Restart the bridge monitor from a terminal or set AUTH=LOCAL.
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.
Redefine the terminal, or use a different one, before restarting the bridge monitor, or set AUTH=LOCAL.
An error occurred in an MQ API call issued by the bridge.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
The bridge queue specified is not known to the queue manager.
Check the bridge queue is defined correctly and specified on the Q= parameter of the bridge startup for CKBR.
Bridge monitor quiesce has been initiated. This would normally be because CICS or the queue manager is shutting down or because the operator has set the bridge queue GET(DISABLED).
Bridge monitor shutdown completed normally.
Bridge monitor is starting.
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.
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.
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.
Make sure that all messages within a multipart unit of work contain an MQCIH and rerun the unit of work.
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.
Correct the UOWControl field and rerun the unit of work.
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.
Correct the UOWControl field and rerun the unit of work.
An attempt has been made to start the bridge monitor with AUTH=IDENTIFY or VERIFY_ but security is not active for the CICS system.
Activate security, or choose a different authentication option.
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 StrucId, Version, or StrucLength is incorrect.
Check the version of the header and compare with the level supported by the bridge. Correct the format or the user data as appropriate.
The bridge queue specified is not defined as a local queue.
Redefine the bridge request queue as a local queue.
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.
The bridge queue is defined with NOHARDENBO.
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 CICS emergency restart.
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.
Alter the queue definition to set MSGDLVSQ(FIFO).
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.
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).
There is no dead-letter queue 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 queue.
Alter the queue manager to define a dead-letter queue if dead-letter processing is required.
The dead-letter queue 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 queue.
Refer to Appendix A. API completion and reason codes for information about mqrc.
An MQINQ call on the dead-letter queue failed. The bridge will be terminated if any error occurs that would result in a message being sent to the dead-letter queue.
Refer to Appendix A. API completion and reason codes for information about mqrc.
An MQPUT to the dead-letter queue 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.
Refer to Appendix A. API completion and reason codes for information about mqrc.
The dead-letter queue 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 queue.
Ensure the dead-letter queue is not defined as a transmission queue.
The maximum message length allowed for the dead-letter queue 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 queue.
Increase the MAXMSGL of the dead-letter queue 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.
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 CICS, the queue manager, or the bridge monitor are restarted.
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.
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.
Rerun the unit of work.
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.
Rerun the unit of work.
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.
Either:
The bridge task backed out a unit of work on receipt of a MQCUOWC_BACKOUT request.
An MQPUT call to the reply-to queue failed.
The response message will be sent to the dead-letter queue.
Refer to Appendix A. API completion and reason codes for information about mqrc.
A request message was received with an invalid value for the CCSID field in the MQMD.
Correct the MQMD and reissue the request.
A request message was received with an invalid value for the encoding field in the MQMD.
Correct the MQMD and reissue the request.
The bridge has sent this request message to the dead-letter queue during backout processing.
See the associated messages to determine the cause of the problem.
The bridge monitor is being run with AUTH=VERIFY_UOW or AUTH=VERIFY_ALL. An EXEC CICS SIGNON or EXEC CICS VERIFY PASSWORD command failed.
Check that the correct user ID was specified, and that the appropriate authorizations are defined for it.
An unexpected condition was detected by the bridge.
Contact your IBM support center if the problem persists.
An EXEC CICS LINK command for the user requested program failed.
See the CICS Application Programming manual for an explanation of eibresp and eibresp2.
The reply-to queue name in a request message is the same as the bridge-request queue name. This is not allowed.
Specify a different reply-to queue in the request.
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 CICS failure while this request was in progress. No attempt is made to process the request a second time.
Look at previous error messages for this message on the CSMT log to determine the cause for the previous failure, and rerun the request.
A bridge task terminated abnormally.
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.
The bridge request queue does not have the SHARE attribute.
Alter the queue definition and restart the bridge monitor.
The dead-letter queue 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 queue.
Redefine the dead-letter queue as a local queue.
The reply-to queue specified is not known to the queue manager.
Refer to Appendix A. API completion and reason codes for information about mqrc. Check you have provided the necessary queue definitions.
The bridge monitor is being run with the IDENTIFY or VERIFY authorization option. An EXEC CICS START command for the bridge task failed with NOTAUTH or USERIDERR because the user ID is not authorized to start bridge transactions or has been revoked.
See the CICS Application Programming manual for an explanation of eibresp and eibresp2. Correct the security definitions if this userid should be authorized to run requests using the bridge.
An request has been received to run the transaction listed but it is not defined to this CICS system.
Correct the request or define the transaction.
This message gives the identifier of a message to which a previous error message relates.
See the associated message.
This message gives the correlation identifier of a message to which a previous error message relates.
See the associated message.
This message gives the name of the queue to which a previous error message relates.
See the associated message.
This message gives the name of the queue manager to which a previous error message relates.
See the associated message.
A user ID 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 ID.
Correct the user ID and rerun the unit of work.
The bridge queue should be defined with an index type of CORRELID. This is required if the queue is a shared queue and stongly recommended for private queues.
If the bridge queue is shared, the bridge monitor does not start. Otherwise, processing continues.
Alter the queue definition to specify the required index type and restart the bridge monitor.
The backout-requeue queue defined to the bridge queue could not be opened.
Messages will be sent to the dead-letter queue instead.
Refer to Appendix A. API completion and reason codes for information about mqrc.
The backout-requeue queue is not defined as a local queue.
Messages will be sent to the dead-letter queue instead.
Redefine the backout-requeue queue as a local queue.
An MQINQ call on the backout-requeue queue failed.
Messages will be sent to the dead-letter queue instead.
Refer to Appendix A. API completion and reason codes for information about mqrc.
The backout-requeue queue is not defined correctly.
Messages will be sent to the dead-letter queue instead.
Ensure the backout-requeue queue is not defined as a transmission queue.
An MQPUT to the backout-requeue queue failed.
Messages will be sent to the dead-letter queue instead.
Refer to Appendix A. API completion and reason codes for information about mqrc.
The CICS 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.
The input messages are backed out to the backout-requeue queue or dead-letter queue.
Correct the FacilityLike field to specify the name of a terminal installed on the CICS system or install a terminal with the required name.
The CICS 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.
The input messages are backed out to the backout-requeue queue or dead-letter queue.
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.
The RemoteSysId field of the MQCIH message header is non-blank, but the specified name sys-name is not known to CICS or there is no active CICS connection to that remote system.
The input messages are backed out to the backout-requeue queue or dead-letter queue.
Ensure that the specified CICS system is running and that there is an active CICS Intersystem communication connection to it from the system running the bridge monitor.
The RemoteSysId field of the MQCIH message header is blank, but the specified Facility token is not known to CICS. The bridge monitor does not know which CICS 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.
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 CICS region, improve performance, and prevent the possibility of unprocessed messages.
The CICS 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 CICS system initialization parameter).
The input messages are backed out to the backout-requeue queue or dead-letter queue.
Ensure that the FacilityKeepTime field of the first message in a 3270 transaction sequence contains a value within the valid range.
The CICS Link3270 program DFHL3270 returned an unexpected return code.
The input messages are backed out to the backout-requeue queue or dead-letter queue.
Use the CICS 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 CICS External Interfaces Guide to determine the meaning of the return code from DFHL3270. Correct the input message accordingly.
A CICS abend occured in a transaction running under the CICS link bridge.
The input messages are backed out to the backout-requeue queue or dead-letter queue.
Determine the cause of the abend and correct the underlying problem using normal CICS diagnostic techniques.
The mapset name in a receive map vector does not match the name requested. The bridge task cannot interpret the application data structure.
The input messages are backed out to the backout-requeue queue or dead-letter queue.
Ensure the mapset name in the input message matches the name expected by the CICS transaction and returned in the preceding receive map request vector.
The map name in a receive map vector does not match the name requested. The bridge task cannot interpret the application data structure.
The input messages are backed out to the backout-requeue queue or dead-letter queue.
Ensure the map name in the input message matches the name expected by the CICS transaction and returned in the preceding receive map request vector.
The bridge input vector was invalid. Possible errors are:
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).
The input messages are backed out to the backout-requeue queue or dead-letter queue.
Ensure the map name in the input message matches the name expected by the CICS transaction and returned in the preceeding receive map request vector.
The CICS Link3270 program DFHL3270 returned code BRIHRC_DHFBRNSF_UNAVAILABLE, because the CICS bridge facility name space file, DFHBRNSF, was not available for use by CICS.
The input messages are backed out to the backout-requeue queue or dead-letter queue.
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.
This confirms the bridge monitor start options.
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.
Correct the parameter in error and restart the bridge monitor.
The CICS Link3270 program DFHL3270 returned code BRIHRC_ROUTING_BACKLEVEL_CICS, because the Link3270 request was routed to a CICS system that does not support Link3270.
Correct the CICS transaction routing definitions. The target CICS system must be CICS Transaction Server Version 2 Release 2 or higher.
For information about Link3270 see 'Bridging to 3270 transactions' in the CICS External Interfaces Guide.
The CICS 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.
Correct the CICS transaction routing definitions. The target CICS system must be active and connected.
For information about Link3270 see 'Bridging to 3270 transactions' in the CICS External Interfaces Guide.
The CICS Link3270 program DFHL3270 returned code BRIHRC_ROUTING_TERMERR, because the EXEC CICS LINK from the DFHL3270 to the target region failed with TERMERR.
Correct the CICS transaction routing definitions.
For information about Link3270 see 'Bridging to 3270 transactions' in the CICS External Interfaces Guide.
The CICS 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.
Correct the CICS transaction routing definitions.
For information about Link3270 see 'Bridging to 3270 transactions' in the CICS External Interfaces Guide.
The CICS 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.
Correct the CICS transaction routing definitions.
For information about the codes code and compcode from Link3270 see 'BRIH-RETURNCODE values' in the CICS External Interfaces Guide.
The CICS 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.
Check the state of the CICS system.
For information about Link3270 see 'Bridging to 3270 transactions' in the CICS External Interfaces Guide.
The length field in the header is less than the minimum header length or greater than the actual message message length.
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.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0406 |