QUEUEMANAGER detail report

The following is an example of the QUEUEMANAGER detail report:
    ***** QUEUEMANAGER DETAIL REPORT *****

      Global Information
      -------------------------------

      Application Environment Table Object......... xxxxxxxx
      Server Manager Mode.......................... Goal

      Queue Manager Information
      -------------------------------

      QEB CELL POOL ID ............................ xxxxxxxx
      Last Transaction Environment Sequence Number. xxxxxxxx
      Last Work Unit Sequence Number............... xxxxxxxx
      Dynamic Area CPOOL For PC Services........... xxxxxxxx
      TCB Defined For WLM QM Initialization Task... xxxxxxxx

      Work Manager Information
      ------------------------

      Subsystem Type............................... DB2
      Subsystem Name............................... DB2A
      Work Manager State........................... Active
      Work Manager Flags
        xxxxxxxxxxxxxxxxxxxxxxxx
      Work Manager Queues
        First application environment.............. xxxxxxxx
        Last application environment............... xxxxxxxx
      XDAT Connection.............................. xxxxxxxx

        Application Environment Information
        -----------------------------------

        Application Environment Name........ PAYROLL
        Application Environment State.............. Active
        Application Environment Counts
          Total target............................. xxxxxxxx
          Total bound.............................. xxxxxxxx
          Number of starting servers............... xxxxxxxx
          Number of connected servers.............. xxxxxxxx
        Application Environment Flags
          xxxxxxxxxxxxxxxxxxx
        Application Environment Queues    ......... xxxxxxxx
          First server............................. xxxxxxxx
          Last server.............................. xxxxxxxx
          First transaction environment............ xxxxxxxx
          Last transaction environment............. xxxxxxxx

          Transaction Environment Information
          -----------------------------------

          Transaction Environment Service Class.... AQISSLOW
          Transaction Environment Counts
            Target................................. xxxxxxxx
            Bound.................................. xxxxxxxx
          Transaction Environment Work Queue....... Empty
          Transaction Environment Flags
            xxxxxxxxxxxxxxxxx
          Transaction Environment Queues
            First work unit........................ xxxxxxxx
            Last work unit......................... xxxxxxxx
            First suspended server................. xxxxxxxx
            Last suspended server.................. xxxxxxxx
            Work Queue Information
            ----------------------

            Work Unit User Data .....xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
            Work unit Flags
              xxxxxxxxxxxxxxxxxx
            Work Unit Etoken....................... xxxxxxxx xxxxxxxx
            Work Unit Userid....................... xxxxxxxx

      Application Environment Table Information
      -----------------------------------------

      Application Environment Name......... PAYROLL
        Subsystem Type............................. DB2
        Procedure Name............................. PAYROLL
        Start Parameters


        Limit on starting server address spaces
          Single address space per sysplex
        Local System Data
          System State............................. Available
          Time Of Last State Change................ 05/10/1996 09:37:08
          Name Of System Coordinating System State. ********
          Local Work Unit ID....................... xxxxxxxx xxxxxxxx
        Server Failure Data
          Number of unexpected server failures..... 00000002
          Server Failure Flags
            xxxxxxxxxxxxxxxxxxxxxxxx
          Server Failure Times
            Most Recent Failure Time............... 05/10/1996 10:52:36
               ...                  ............... 05/10/1996 10:52:13
               ...                  ............... None
               ...                  ............... None
            Oldest Failure Time.................... None
Global Information
The global environment management information section represents data that is global to all system processing done by the WLM Server Environment Manager.
Application environment table object
Represents the pointer to the Application Environment Table (AET).
Server Manager mode
Represents the WLM mode that the server environment manager is using. A value of Goal corresponds directly with the goal mode of WLM.
Queue Manager Information
The queue manager section shows global data used by the WLM queue manager to manage the function.
QEB CELL POOL ID
The CELL POOL ID of the queue manager's work unit pool.
Last transaction environment sequence number
Represents the last sequence number assigned to a new transaction environment.
Last work unit sequence number
Represents the last sequence number assigned to a new work unit.
Dynamic Area CPOOL ID For PC Services
Represents the id of the dynamic area used by queue manager service routines.
TCB Defined For WLM QM Initialization Task
The TCB address of the task that initialized the queue manager function.
Work Manager Information
The work manager section shows each work manager that is using Server Environment Manager services in the system. Note that if no work manager information exists then this section is not shown (also applicable sections under it are not shown).
Subsystem Type
The work manager's WLM subsystem type.
Subsystem Name
The work manager's WLM subsystem name.
Work Manager State
The work manager's state.
  • Active

    Indicates a work manager that is connected to WLM and has not terminated.

  • Inactive

    Indicates a work manager that is terminating or has terminated, and may no longer be connected to WLM.

Work Manager Flags
Flags representing work manager status. If none of the flags that are of interest are set then this header is not shown.
  • Operator Started

    Indicates that the existence of this work manager was indicated to WLM by an operator command starting a server address space.

  • Queue Manager

    Indicates that the work manager is a queue manager.

  • Router

    Indicates that the work manager is a sysplex routing manager.

Work Manager Queues
The queues of objects which are anchored by the work manager
  • First application environment

    Represents the first application environment in use by this work manager.

  • Last application environment

    Represents the last application environment in use by this work manager.

XDAT Connection
Represents the XDAT object to which the work manager is connected.
Application Environment Information
The application environment section shows each application environment that is in use by the work manager above.
Application Environment Name
The application environment's name.
Application Environment State
Specifies the application environment's state.
  • Available

    Indicates that the application environment is defined to WLM and that it is ready for the associated subsystem(s) to connect to it.

  • Quiesced

    Indicates that WLM stopped starting new servers in this application environment because the operator issued the V WLM,APPLENV=xxxxx,QUIESCE command.

  • Stopped

    Indicates that WLM stopped starting new servers in the application environment because WLM detected a problem with the JCL procedure of the application environment or the server code.

  • Deleting

    Indicates that WLM is in the process of deleting this application environment.

  • Refreshing

    Indicates that WLM is in the process of refreshing all the servers in this application environment.

  • Quiescing

    Indicates that WLM is in the process of quiescing all the servers in this application environment.

Application Environment Counts
Describes the number of server address spaces in the following categories;
  • Total target

    Represents the total number of server address spaces requested on the local system by SRM for all transaction environments in this application environment. This is a total of all want counts in the transaction environments under this application environment.

  • Total bound

    Represents the number of servers that WLM has bound to transaction environments in this application environment. This is a total of all have counts in the transaction environments under this application environment.

  • Total number of starting servers

    Represents the number of servers that WLM has started, but have not yet connected to WLM.

  • Total number of connected servers

    Represents the number of servers that have connected to WLM, but have not selected any work in this application environment.

Application Environment Flags
Describes the flags which are set in the application environment. If none of the flags that are of interest are set then this header is not shown.
  • Operator started

    Indicates that the server was started by the operator (or some process other than WLM).

  • Logically deleted

    Indicates that the application environment is logically deleted.

Application Environment Queues
Describes the queues anchors in the application environment object.
  • First server

    Describes the first server object in this application environment.

  • Last server

    Describes the last server object in this application environment.

  • First transaction environment

    Describes the first transaction environment object in the application environment.

  • Last transaction environment

    Describes the last transaction environment object in the application environment.

Transaction Environment Information
The transaction environment section describes a unique queue of work that is known to WLM.
Transaction environment service class
Names the external service class to which the queued work has been classified. If the transaction environment is not associated with one service class, then this field may contain '********' to indicate that the transaction environment may contain more than one service class.
Transaction environment counts
Represents the number of server address spaces in the following categories.
  • Target

    Represents the number of servers on the local system that SRM wants bound to this transaction environment.

  • Bound

    Represents the number of servers that WLM has bound to this transaction environment.

Transaction Environment Work Queue
Describes the Empty/Not Empty state of the transaction environment's work queue.
Transaction Environment Flags
Describes the flags which are set in the transaction environment. If none of the flags that are of interest are set then this header is not shown.
  • Deleting

    Indicates that this transaction environment is being deleted.

  • Service class based

    Indicates that this transaction environment is serving only one service class.

Transaction Environment Queues
Describes the queues anchors in the application environment object.
  • First work unit

    Describes the first work unit to be executed.

  • Last work unit

    Describes the last work unit to be executed.

  • First suspended server

    Describes the first server object with suspended server tasks.

  • Last suspended server

    Describes the last server object with suspended server tasks.

Work Queue Information
The work queue section describes each unique work unit that has been inserted to WLM but not yet selected for execution.
Work Unit User Data
Represents the work unit as it is known by the subsystem that inserted the work.
Work Unit Flags
Describes the flags which are set in the work unit. If none of the flags that are of interest are set then this header is not shown.
Userid is valid
Indicates that the work unit user ID was supplied when the work unit was inserted.
Work unit EToken
A token representing the enclave token under which the work is executing.
Userid
The user ID that owns the work unit.
Application Environment Table Information
The application environment table information section describes all the application environments known to WLM. The application environments are defined using the WLM ISPF application or through the IWMDINS(install)/IWMPACT(activate) interfaces. Note that if no application environments exist then only the header is shown.
Application Environment name
Names the application environment.
Subsystem Type
Names the subsystem type that is assigned to this application environment.
Procedure Name
Names the JCL procedure used for this application environment.
Start Parameters
Shows the start parameter information used by WLM when starting a server environment address space in this application environment.
Limit on starting server address spaces
A header line that indicates that one of the subsequent lines is a limit for the current application environment.
  • No limit
  • Single address space per system
  • Single address space per sysplex
Local System Data
A header line that indicates that information indented under this line is used by the local/current system to manage the application environment.
System State
Indicates the application environment state as known by the current system.
  • Available

    Indicates that the application environment is defined to WLM and that it is ready for the associated subsystem to connect to it.

  • Refreshing

    Indicates that the application environment is being refreshed because the operator issued a V WLM,APPLENV=xxxxx,REFRESH command.

  • Quiescing

    Indicates that this system has finished working on an operator issued V WLM,APPLENV=xxxxx,QUIESCE command.

  • Quiesced

    Indicates that this system has finished working on an operator issued V WLM,APPLENV=xxxxx,QUIESCE command.

  • Resuming

    Indicates that this system is working on an operator issued V WLM,APPLENV=xxxxx,RESUME command.

  • Internally-Refreshing

    Indicates that this system is working on an internally generated refresh action.

  • Internally-Stopping

    Indicates that this system is working on an internally generated stop action.

  • Internally-Stopped

    Indicates that this system has finished working on an internally generated stop action.

  • Deleting

    Indicates that WLM is in the process of deleting this application environment.

  • Deleted

    Indicates that WLM has finished the process of deleting an application environment.

  • No State

    Indicates that the application environment state does not exist.

  • Unknown

    Indicates that the application environment state is not any of the above, therefore it is unknown. For this case we most likely have bad data.

Time Of Last State Change
The last time the application environment state was changed.
Name Of System Coordinating Application Environment State
Indicates which system in the sysplex is coordinating the application environment state that is shown. Coordination is required for any transitional state such as deleting/quiescing and possibly the 'no state' condition. Note that if no system is coordinating the system state then ******** is shown.
Local Work Unit ID
The work-unit-id of the current action (if application environment state is transitional, like deleting) or the last action that was performed for this application environment
Server Failure Data
A header line that groups data collected by Server Environment Manager relating to unexpected server terminations in this application environment. If there is no failure data to display, this entire section will be skipped by the IPCS formatter.
Number of unexpected server failures
The number of unexpected server terminations detected by Server Environment Manager on this system in this application environment
Server Failure Flags
Groups flags that are set in this section of the AET.
Internal Stop has been initiated
Indicates that Server Environment Manager has detected 5 unexpected terminations within 10 minutes of each other and that Server Environment Manager has initiated an internal-stop of the application environment.
Server Failure Times
Displays the date and time of the most recent unexpected termination to the oldest unexpected termination (maximum of 5 in the history). If the most recent and the oldest are within 10 minutes of each other then Server Environment Manager will initiate an internal-stop of the application environment.