QUEUEMANAGER summary report

Figure 1. Example: QUEUEMANAGER summary report
    ***** QUEUEMANAGER SUMMARY REPORT *****

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

      Server Manager Mode.......................... Goal

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

      Subsystem Type............................... DB2
      Subsystem Name............................... DB2A
      Work Manager State........................... Active

        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

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

          Transaction Environment Service Class.... AQISSLOW
          Transaction Environment Counts
            Target................................. xxxxxxxx
            Bound.................................. xxxxxxxx
          Transaction Environment Work Queue....... Empty

            Work Queue Information
            -----------------------------------

            Work Unit User Data..... xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

            Work Queue Information
            -----------------------------------

            Work Unit User Data..... xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

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

      Application Environment Name......... PAYROLL
        Subsystem Type............................. DB2
        Procedure Name............................. PAYROLL
Global Information
The global environment management information section represents data that is global to all system processing done by the WLM Server Environment Manager.
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.
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 since they do not exist).
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.

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 the application environment was quiesced by the operator issuing the V WLM,APPLENV=xxxxx,QUIESCE command.

  • Stopped

    Indicates that WLM stopped starting new servers in this 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 by SRM on the local system 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.

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.
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.
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.
Parent topic: WLMDATA queue manager report