Agent services messages (CSQV...)

 

CSQV086E
QUEUE MANAGER ABNORMAL TERMINATION REASON=reason-code
Explanation:

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.

System Action:

Abnormal termination processing continues.

Operator Response:

Notify the system programmer, and restart the queue manager.

System Programmer Response:

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.

Problem Determination:

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

  • Console output

  • Printout of SYS1.LOGREC

  • Any system dumps produced

CSQV400I
ARCHIVE LOG QUIESCE CURRENTLY ACTIVE
Explanation:

An ARCHIVE LOG MODE(QUIESCE) command is currently active. This message is part of the DISPLAY LOG or DISPLAY THREAD command report.

System Action:

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.

CSQV401I
DISPLAY THREAD REPORT FOLLOWS -
Explanation:

This message is issued as the title for the DISPLAY THREAD command report output. It precedes the other messages generated by this command:

  • Message CSQV402I provides the formatted report when the detailed status of active threads is requested using TYPE(ACTIVE).

  • Message CSQV432I provides the formatted report when the summary status of active threads is requested using TYPE(REGIONS).

  • Message CSQV406I provides the formatted report when the status of in-doubt threads is requested using TYPE(INDOUBT).

  • Message CSQV436I provides the formatted report when the status of in-doubt threads on another queue manager is requested using TYPE(INDOUBT) with QMNAME.

System Action:

Processing continues normally.

CSQV402I
ACTIVE THREADS -
Explanation:

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:

name

The connection name, which is one of the following:

s

Connection status code:

N

The thread is in IDENTIFY status.

T

The thread has issued CREATE THREAD.

Q

The CREATE THREAD request has been queued. The associated allied task is placed in a wait state.

C

The thread is queued for termination as a result of the termination of the associated allied task. If this thread is also the last (or only) MQ thread for the address space, the associated allied task is placed in a wait state.

D

The thread is in the process of termination as a result of the termination of the associated allied task. If this thread is also the last (or only) MQ thread for the address space, the associated allied task is placed in a wait state.

An asterisk is appended if the thread is active within MQ.

t

Connection type code:

B

Batch: From an application using a batch connection

R

RRS: From an RRS-coordinated application using a batch connection

C

CICS: From CICS

I

IMS: From IMS

S

System: From an internal function of the queue manager or from the channel initiator.

req

A wraparound counter to show the number of MQ requests.

thread-xref

The recovery thread cross-reference identifier associated with the thread. See the WebSphere MQ for z/OS System Administration Guide for more information.

userid

The user ID associated with a connection. If not signed-on, this field is blank.

asid

A hexadecimal number representing the ASID of the home address space.

urid

Unit of recovery identifier. This is the log RBA of the current unit of recovery associated with the thread. If there is no current unit of recovery, it is shown as 000000000000.

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.

System Action:

Processing continues normally.

Operator Response:

If the report was truncated, reissue the DISPLAY THREAD request specifying a specific connection name.

Problem Determination:

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.

CSQV406I
INDOUBT THREADS -
Explanation:

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:

name

The connection name, which is one of the following:

thread-xref

The recovery thread cross-reference identifier associated with the thread. See the WebSphere MQ for z/OS System Administration Guide for more information.

urid

Unit of recovery identifier. This is the log RBA of the current unit of recovery associated with the thread. (This is omitted if the command was issued from a z/OS console with a non-specific connection name.)

origin-id

The origin identifier, a unique token identifying the unit of recovery within the queue manager. This has the form origin-node.origin-urid, where:

origin-node

A name that identifies the originator of the thread. (This is omitted for batch RRS connections.)

origin-urid

The hexadecimal number assigned to the unit of recovery for this thread by the originating system.

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.

System Action:

Processing continues normally.

Operator Response:

If the report was truncated, reissue the DISPLAY THREAD request specifying a specific connection name.

CSQV410I
NO ACTIVE CONNECTION FOUND FOR NAME=connection-name
Explanation:

The DISPLAY THREAD command was unable to find any active connection associated with connection-name.

System Action:

Command processing continues.

CSQV411I
NO ACTIVE THREADS FOUND FOR NAME=connection-name
Explanation:

The DISPLAY THREAD command was unable to locate any active threads associated with connection-name.

System Action:

Command processing continues.

CSQV412I
csect-name NO INDOUBT THREADS FOUND FOR NAME=connection name
Explanation:

The DISPLAY THREAD command was unable to locate any in-doubt threads associated with connection name.

System Action:

Command processing continues.

CSQV413E
csect-name CONNECTION NAME MISSING
Explanation:

A connection name was not supplied with the command, and a default connection name cannot be determined.

System Action:

Command processing terminates.

Operator Response:

Reenter the command specifying a connection name.

CSQV414I
THREAD NID=origin-id COMMIT SCHEDULED
Explanation:

The thread specified by the recovery origin identifier origin-id is scheduled for COMMIT recovery action.

System Action:

Processing continues.

CSQV415I
THREAD NID=origin-id BACKOUT SCHEDULED
Explanation:

The thread specified by the recovery origin identifier origin-id is scheduled for BACKOUT recovery action.

System Action:

Processing continues.

CSQV416E
THREAD NID=origin-id IS INVALID
Explanation:

The RESOLVE INDOUBT command determined that the input format for the specified thread origin-id is invalid.

System Action:

Command processing continues.

Operator Response:

Ensure that the origin-id entered is in the correct format as specified on the RESOLVE INDOUBT command before reentering the command.

CSQV417I
THREAD NID=origin-id NOT FOUND
Explanation:

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.

System Action:

Command processing continues.

Operator Response:

Ensure that the thread still resides within an in-doubt state before reentering the command.

CSQV419I
NO ACTIVE CONNECTIONS FOUND
Explanation:

A DISPLAY THREAD(*) TYPE(ACTIVE) or TYPE(REGIONS) command was issued for all threads, but no active connections were found.

System Action:

Command processing continues.

CSQV420I
NO INDOUBT THREADS FOUND
Explanation:

A DISPLAY THREAD(*) TYPE(INDOUBT) command was issued for all threads, but no in-doubt threads were found.

System Action:

Command processing continues.

CSQV423I
cmd MESSAGE POOL SIZE EXCEEDED
Explanation:

The storage requirement needed to generate responses for the command cmd exceeded the maximum size of the message buffer pool.

System Action:

Processing is terminated.

Operator Response:

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.

CSQV424I
THREAD ID=thread-xref COMMIT SCHEDULED
Explanation:

The thread specified by the recovery thread cross-reference identifier thread-xref is scheduled for COMMIT recovery action.

System Action:

Processing continues.

CSQV425I
THREAD ID=thread-xref BACKOUT SCHEDULED
Explanation:

The thread specified by the recovery thread cross-reference identifier thread-xref is scheduled for BACKOUT recovery action.

System Action:

Processing continues.

CSQV427I
THREAD ID=thread-xref NOT FOUND
Explanation:

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.

System Action:

Command processing continues.

Operator Response:

Ensure that the thread still resides within an in-doubt state before reentering the command.

CSQV428I
CURRENT THREAD LIMIT OF nnn EXCEEDED. CREATE THREAD FOR JOB jobname DEFERRED
Explanation:

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.

System Action:

The request for a connection is suspended, and waits until another connection ends.

Operator Response:

Notify your systems programmer if this occurs frequently.

System Programmer Response:

If this situation occurs frequently, consider changing the CTHREAD system parameter to increase the limit for connected threads.

CSQV432I
ACTIVE THREADS -
Explanation:

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:

name

The connection name, which is one of the following:

type

The connection type:

CICS

From CICS.

IMS

From IMS.

BATCH

From an application using a batch connection.

RRSBATCH

From an RRS-coordinated application using a batch connection.

CHINIT

From the channel initiator.

userid

The user ID associated with a connection. If not signed-on, this field is blank.

asid

A hexadecimal number representing the ASID of the home address space.

threads

The number of active threads associated with the connection. This excludes fixed internal threads, such as those for the CICS adapter tasks, or the channel initiator listeners.

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.

System Action:

Processing continues normally.

Operator Response:

If the report was truncated, reissue the DISPLAY THREAD request specifying a specific connection name.

CSQV433I
'QMNAME' NOT ALLOWED, NOT IN QUEUE-SHARING GROUP
Explanation:

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.

System Action:

Processing for the command is terminated.

Operator Response:

Reissue the command correctly.

CSQV434E
'QMNAME' ALLOWED ONLY WITH TYPE(INDOUBT)
Explanation:

A DISPLAY THREAD command specifying the QMNAME keyword was issued, but TYPE(INDOUBT) was not specified.

System Action:

Processing for the command is terminated.

Operator Response:

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.

CSQV435I
QMNAME(qmgr-name) IS ACTIVE, COMMAND IGNORED
Explanation:

A DISPLAY THREAD TYPE(INDOUBT) or RESOLVE INDOUBT command specifying the QMNAME keyword was issued, but the requested queue manager qmgr-name is active.

System Action:

Processing for the command is terminated.

Operator Response:

Reissue the command using CMDSCOPE(qmgr-name) instead of QMNAME(qmgr-name).

CSQV436I
INDOUBT THREADS FOR qmgr-name -
Explanation:

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.

System Action:

Processing continues normally.

Operator Response:

If the report was truncated, reissue the DISPLAY THREAD request specifying a specific connection name.

CSQV437I
CANNOT RESOLVE THREAD NID=origin-id, SOME RESOURCES UNAVAILABLE
Explanation:

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.

System Action:

The identified thread will remain in-doubt.

Operator Response:

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.

CSQV450I
csect-name Unable to open ddname data set
Explanation:

The ddname data set could not be opened, as reported in the preceding messages.

System Action:

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.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQV451I
csect-name Unable to get storage for exits, RC=return-code
Explanation:

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.

System Action:

Processing continues, but cluster workload user exits will not be available.

System Programmer Response:

See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.

CSQV452I
csect-name Cluster workload exits not available
Explanation:

Cluster workload user exit functions will not be available, because:

  • There is no CSQXLIB DD statement in the started task JCL procedure for the queue manager, xxxxMSTR

  • The EXITTCB system parameter is zero.

System Action:

Processing continues, but cluster workload user exits will not be available.

System Programmer Response:

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.

CSQV453I
csect-name Unable to load module-name, reason=ssssrrrr
Explanation:

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.

System Action:

Processing continues, but cluster workload user exits will not be available.

System Programmer Response:

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.

CSQV455E
csect-name Cluster workload exit exit-name timed out
Explanation:

A cluster workload user exit did not return to the queue manager within the allowed time, as specified by the EXITLIM system parameter.

System Action:

The exit is disabled until its load module in the CSQXLIB data set is refreshed.

System Programmer Response:

Investigate why your exit is not returning in time.

CSQV456E
csect-name Cluster workload exit error, TCB=tcb-name reason=sssuuu-reason
Explanation:

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

System Action:

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.

System Programmer Response:

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.

CSQV457E
csect-name Unable to establish ESTAE, RC=return-code
Explanation:

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.

Severity:

8

System Action:

The task does not start. Cluster workload user exits will be available providing at least one task starts.

System Programmer Response:

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.

CSQV459I
csect-name Unable to free storage for exits, RC=return-code
Explanation:

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.

System Action:

Processing continues.

System Programmer Response:

See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.