SERVERMANAGER summary report

Figure 1. Example: SERVERMANAGER summary report

    ***** SERVERMANAGER 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.............. Available
        Application Environment Counts
          Total target............................. xxxxxxxx
          Total bound.............................. xxxxxxxx
          Number of starting servers............... xxxxxxxx
          Number of connected servers.............. xxxxxxxx
        Application Environment Limits
          Maximum.................................. xxxxxxxx
          Minimum.................................. xxxxxxxx
          Spread minimum across transaction env.... YES|NO

          Server Information
          ------------------

          Server ASID.............................. X'002F'
          Server Jobname........................... PAYROLL
          Server State............................. Bound
          Time of Last Server State Change......... 08/18/1995 17:20:25
          Server Binding........................... AQISSLOW
          Server Address Space Counts
            Temporal Affinities.................... xxxxxxxx
          Selected Work Table
          -------------------

          Number Of Entries In Use................. xxxxxxxx
          Selected Work Entries
            User Data............ xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

            User Data............ xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

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

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

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

      Application Environment Name......... PAYROLL
        Subsystem Type............................. DB2
        Procedure Name............................. DB2PAY

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 because the operator issued 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 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 Limits

Describes the limits existing for the application environment.

Maximum
Represents the maximum number of servers WLM is allowed to start for all transaction environments in this application environment.
Minimum
Represents the minimum number of servers which should be up and running all the time for this application environment.
Spread minimum across transaction env
YES - indicates that the minimum number of servers will be distributed as evenly as possible to all service classes being used to execute work requests.

NO - indicates that the minimum number of servers will be distributed to service classes as needed in order to meet goals.

Server Information

The server information section describes a specific server that is managed by Server Environment Manager. Note that if no server information exists then this section is not shown.

Server ASID

The ASID of the server environment address space.

Server Jobname

The jobname of the server environment address space.

Server State

The current state of the server: Undefined, Starting, Initializing, Connected, Bound, Unbound, Terminating, Disconnected, A/S Termed, ASCRE Retry, or Routing Ready.

Time of last server state change

The time when the server changed into the current state.

Server Binding

The service class of the transaction environment to which the server is bound. If the server is bound to a transaction environment that is not associated with one service class, then this field will contain '********' to indicate that the transaction environment may contain work classified to more than one service class. The transaction environment is considered to be non-partitioned in this case.

Server Address Space Counts

Describes further properties of the server address space.

Temporal Affinities: Represents the number of temporal affinities which exist for the server address space.

Selected Work Table Information

The selected work table section describes the work which has been selected by a server, to be executed by that server. Note that if no selected work table information exists then this section is not shown. For sysplex routing servers, there is no Selected Work Table.

Number of entries in use

Represents the number of work units currently being executed in parallel by the server. If 0 is shown then no entries are currently in use which means there are no server tasks between IWMSTBGN and IWMSTEND.

Selected work entries

Describes each slot in the table.

User data: Represents the work unit (USERDATA on IWMQINS) as it was provided to WLM by the inserting subsystem. WLM does not use this information, but it has been provided for assistance in debugging problems on the exploiting subsystem's side of the interfaces.

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.
Server Instance Target
Represents the number of clients which route their work requests directly to this server region.

Transaction environment work queue

Describes the Empty/Not Empty state of the transaction environment's work queue.

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.