The queue manager is ending abnormally, because an error that cannot be corrected has occurred. This message, which is not automatically deleted from the operator console, is issued during abnormal termination. reason-code is the termination reason code. If this abnormal termination is invoked multiple times, the termination reason code that accompanies this message is the reason associated with the first invocation.
Abnormal termination processing continues.
Notify the system programmer, and restart the queue manager.
For additional information, look up the reason code in Codes.
This message is accompanied by one or more dumps. Obtain a copy of SYS1.LOGREC after the queue manager completely terminates, and the dumps. If you suspect an error in WebSphere MQ, see the WebSphere MQ for z/OS Problem Determination Guide for information about identifying and reporting the problem.
You might find the following items useful in resolving the problem:
An ARCHIVE LOG MODE(QUIESCE) command is currently active. This message is part of the DISPLAY LOG or DISPLAY THREAD command report.
This message is issued as information only. It indicates that the ARCHIVE LOG MODE(QUIESCE) command has not completed and, consequently, updates against MQ resources have been temporarily suspended. This might result in active threads being suspended awaiting termination of the quiesce period. Processing otherwise continues normally.
This message is issued as the title for the DISPLAY THREAD command report output. It precedes the other messages generated by this command:
Processing continues normally.
This message comprises the response to the DISPLAY THREAD TYPE(ACTIVE) command. It provides the status information for each active thread, as follows:
NAME S T REQ THREAD-XREF USERID ASID URID name s t req thread-xref userid asid urid
·
·
·
DISPLAY ACTIVE REPORT COMPLETE
where:
An asterisk is appended if the thread is active within MQ.
Exceptionally, the last line might be:
DISPLAY ACTIVE TERMINATED WITH MAX LINES
if the report was generated in response to a command from a z/OS console and more than 252 response messages were generated. Only 252 response messages are returned.
Processing continues normally.
If the report was truncated, reissue the DISPLAY THREAD request specifying a specific connection name.
If you have active threads with C or D status codes, the information in message CSQ3201E can be used to diagnose a possible MQ problem.
This message comprises the response to the DISPLAY THREAD TYPE(INDOUBT) command. It provides the status information for each in-doubt thread, as follows:
NAME THREAD-XREF URID NID name thread-xref urid origin-id
·
·
·
DISPLAY INDOUBT REPORT COMPLETE
where:
Exceptionally, the last line might be:
DISPLAY INDOUBT TERMINATED WITH MAX LINES
if the report was generated in response to a command from a z/OS console and more than 252 in-doubt threads were eligible for display.
Processing continues normally.
If the report was truncated, reissue the DISPLAY THREAD request specifying a specific connection name.
The DISPLAY THREAD command was unable to find any active connection associated with connection-name.
Command processing continues.
The DISPLAY THREAD command was unable to locate any active threads associated with connection-name.
Command processing continues.
The DISPLAY THREAD command was unable to locate any in-doubt threads associated with connection name.
Command processing continues.
A connection name was not supplied with the command, and a default connection name cannot be determined.
Command processing terminates.
Reenter the command specifying a connection name.
The thread specified by the recovery origin identifier origin-id is scheduled for COMMIT recovery action.
Processing continues.
The thread specified by the recovery origin identifier origin-id is scheduled for BACKOUT recovery action.
Processing continues.
The RESOLVE INDOUBT command determined that the input format for the specified thread origin-id is invalid.
Command processing continues.
Ensure that the origin-id entered is in the correct format as specified on the RESOLVE INDOUBT command before reentering the command.
The RESOLVE INDOUBT command was unable to locate the thread specified by the recovery origin identifier origin-id to be scheduled for recovery. Either the thread identifier is incorrect, or the thread no longer resides within an in-doubt state.
Command processing continues.
Ensure that the thread still resides within an in-doubt state before reentering the command.
A DISPLAY THREAD(*) TYPE(ACTIVE) or TYPE(REGIONS) command was issued for all threads, but no active connections were found.
Command processing continues.
A DISPLAY THREAD(*) TYPE(INDOUBT) command was issued for all threads, but no in-doubt threads were found.
Command processing continues.
The storage requirement needed to generate responses for the command cmd exceeded the maximum size of the message buffer pool.
Processing is terminated.
If the command was DISPLAY THREAD, reissue the request specifying either TYPE(INDOUBT) or TYPE(ACTIVE) and a specific connection name, location, luw-id, or combination thereof as appropriate to further constrain the display.
If the command was RESOLVE INDOUBT, reissue the request to resolve the remaining indoubt threads. The threads which have been successfully resolved are indicated by the preceding CSQV414I or CSQV415I messages.
The thread specified by the recovery thread cross-reference identifier thread-xref is scheduled for COMMIT recovery action.
Processing continues.
The thread specified by the recovery thread cross-reference identifier thread-xref is scheduled for BACKOUT recovery action.
Processing continues.
The RESOLVE INDOUBT command was unable to locate the thread specified by the recovery thread cross-reference identifier thread-xref to be scheduled for recovery. Either the thread identifier is incorrect, or the thread no longer resides within an in-doubt state.
Command processing continues.
Ensure that the thread still resides within an in-doubt state before reentering the command.
A job requested a connection to the queue manager, but the current number of connections is the maximum allowed, as specified in the CTHREAD system parameter of the queue manager.
The request for a connection is suspended, and waits until another connection ends.
Notify your systems programmer if this occurs frequently.
If this situation occurs frequently, consider changing the CTHREAD system parameter to increase the limit for connected threads.
This message comprises the response to the DISPLAY THREAD TYPE(REGIONS) command. It provides the status information for each active connection, as follows:
NAME TYPE USERID ASID THREADS name type userid asid threads
·
·
·
DISPLAY ACTIVE REPORT COMPLETE
where:
Exceptionally, the last line might be:
DISPLAY ACTIVE TERMINATED WITH MAX LINES
if the report was generated in response to a command from a z/OS console and more than 252 response messages were generated. Only 252 response messages are returned.
Processing continues normally.
If the report was truncated, reissue the DISPLAY THREAD request specifying a specific connection name.
A DISPLAY THREAD TYPE(INDOUBT) or RESOLVE INDOUBT command specifying the QMNAME keyword was issued, but the requesting queue manager qmgr-name is not in a queue-sharing group or the requested queue manager qmgr-name is not a member of the queue-sharing group.
Processing for the command is terminated.
Reissue the command correctly.
A DISPLAY THREAD command specifying the QMNAME keyword was issued, but TYPE(INDOUBT) was not specified.
Processing for the command is terminated.
See the WebSphere MQ Script (MQSC) Command Reference manual for information about the correct syntax of the command. Correct the command syntax, and re-enter the command.
A DISPLAY THREAD TYPE(INDOUBT) or RESOLVE INDOUBT command specifying the QMNAME keyword was issued, but the requested queue manager qmgr-name is active.
Processing for the command is terminated.
Reissue the command using CMDSCOPE(qmgr-name) instead of QMNAME(qmgr-name).
This message comprises the response to the DISPLAY THREAD TYPE(INDOUBT) command when the QMNAME keyword was specified. It provides the status information for each in-doubt unit-of-work on the requested queue manager; the information is displayed in the same format as in message CSQV406I.
Processing continues normally.
If the report was truncated, reissue the DISPLAY THREAD request specifying a specific connection name.
The RESOLVE INDOUBT command was unable to schedule the thread specified by the recovery origin identifier origin-id for recovery, because not all the resources necessary for recovery were available.
The identified thread will remain in-doubt.
The most likely cause of this is unavailable page sets. Check for the CSQP047E message at the previous checkpoint. Follow the guidance for this message to bring the required page sets online. Once all the page sets are available the RESOLVE INDOUBT command can be re-issued to resolve the thread.
The ddname data set could not be opened, as reported in the preceding messages.
Processing continues, but functions that require the data set will be inhibited. For example, if the exit library data set CSQXLIB cannot be opened, cluster workload user exits will not be available.
Investigate the problem reported in the preceding messages.
An attempt to obtain some storage for use by exits failed. return-code is the return code (in hexadecimal) from the z/OS STORAGE service.
Processing continues, but cluster workload user exits will not be available.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.
Cluster workload user exit functions will not be available, because:
Processing continues, but cluster workload user exits will not be available.
If you wish to use cluster workload exits, add the required statement to the queue manager started task JCL procedure and specify a non-zero value for the EXITTCB system parameter. See the WebSphere MQ for z/OS System Setup Guide for more information.
The queue manager was unable to load a module required for exits. ssss is the completion code and rrrr is the reason code (both in hexadecimal) from the z/OS LOAD service.
Processing continues, but cluster workload user exits will not be available.
Check the console for messages indicating why the module was not loaded. See the MVS Programming: Assembler Services Reference manual for information about the codes from the LOAD request.
Ensure that the module is in the required library, and that it is referenced correctly. The queue manager attempts to load this module from the library data sets under the STEPLIB DD statement of its started task JCL procedure xxxxMSTR.
A cluster workload user exit did not return to the queue manager within the allowed time, as specified by the EXITLIM system parameter.
The exit is disabled until its load module in the CSQXLIB data set is refreshed.
Investigate why your exit is not returning in time.
The exit subtask using TCB tcb-name is ending abnormally because an error that cannot be corrected has occurred in a cluster workload user exit. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
The subtask ends abnormally, and a dump is normally issued. The exit is disabled until its load module in the CSQXLIB data set is refreshed.
User completion codes are generally the result of errors detected by the exit itself. If a system completion code is shown, see the MVS System Codes manual for information about the problem in your exit.
During startup processing, the recovery environment for a cluster workload user exit task could not be set up. return-code is the return code (in hexadecimal) from the z/OS ESTAE service.
8
The task does not start. Cluster workload user exits will be available providing at least one task starts.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the ESTAE request. If you are unable to solve the problem, contact your IBM support center for assistance.
An attempt to release some storage that was used by exits failed. return-code is the return code (in hexadecimal) from the z/OS STORAGE service.
Processing continues.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0418 |