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.

    System programmer response

    For additional information, look up the reason code in IBM MQ for z/OS 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 IBM MQ, see Troubleshooting and support for information about identifying and reporting the problem.

    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 IBM 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 is 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:

      • z/OS batch job name
      • TSO user ID
      • CICS® APPLID
      • IMS region name
      • Channel initiator job name

      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) IBM 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) IBM 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 IBM 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 IBM MQ requests.

      thread-xref
      The recovery thread cross-reference identifier associated with the thread.

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

    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.

    CSQV406I
    INDOUBT THREADS -

    Explanation
    This message is 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:

      • z/OS batch job name
      • TSO user ID
      • CICS APPLID
      • IMS region name
      • Channel initiator job name

      thread-xref
      The recovery thread cross-reference identifier associated with the thread. See Connecting from the IMS control region 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.

    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.

    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.

    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 is no longer in an in-doubt state.

    System action

    Command processing continues.

    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.

    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 is no longer in an in-doubt state.

    System action

    Command processing continues.

    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.

    System action

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

    System programmer response

    If this situation occurs frequently, contact your IBM support center for assistance.

    CSQV432I
    ACTIVE THREADS -

    Explanation
    This message is 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:

      • z/OS batch job name
      • TSO user ID
      • CICS APPLID
      • IMS region name
      • Channel initiator job name

      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.

    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.

    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.

    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.

    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.

    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.

    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 want 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. For more information about cluster workload exits, see Cluster workload exit programming.

    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

    Severity
    8

    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.

    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.

    CSQV460I
    csect-name Cluster workload exits are disabled but CLWLEXIT is set.

    Explanation

    A CLWLEXIT value is on the queue manager when it is started, however cluster workload exits are not enabled, and are prevented from operating.

    System action

    Message CSQV461D is issued, but CLWLEXITs are not enabled.

    CSQV461D
    csect-name

    Reply Y to continue startup with CLWLEXIT not enabled, or N to shutdown.

    Explanation

    Issued after message CSQV460I. Due to a CLWLEXIT being set in the queue manager with cluster workload exits not enabled, a reply is required to continue startup with cluster workload exits not enabled.

    System action

    Queue manager startup waits for the reply from the operator. Replying Y allows the queue manager to continue startup with cluster workload exists not enabled. Replying N shuts down the queue manager with abend reason 00D40039.

    While cluster workload exits are not enabled, the CLWLEXIT value can only be changed to a blank value, and the exit will not function. You should use the IBM MQ supplied workload balancing algorithm and attributes, to alter how objects are selected, and remove the CLWLEXIT value. See Workload balancing in clusters for more information.

    For further information contact IBM Support.