Figure 1. Example:
WORKMANAGER detail report ***** WORKMANAGER DETAIL REPORT *****
DETAIL OF WORK REQUEST ACTIVITIES
---------------------------------
Total number of associated address spaces.. 6
Total number of monitoring envs in system.. 885
ASID....................................... X'0032'
Total number of monitoring envs owned... 0
ASCB Address............................ 00F5ED00
Connect token........................... 07CE0158
DETAIL OF CONNECTION SUB-REPORT
-------------------------------
Subsystem type.......................... IMS
Connection flags
xxxxxxxxxxxxx
Subsystem name.......................... IMSU
Number of associated ASCBs.............. 3
Connector's TCB address................. 006EE848
Connector's protect key................. 07
Associated ASCB address................. 00F5ED00
Associated ASCB address................. 00F4C700
Associated ASCB address................. 00F77E80
ASID....................................... X'0033'
Total number of monitoring envs owned... 166
ASCB Address............................ 00F5EB80
Connect token........................... 07CE00D8
DETAIL OF CONNECTION SUB-REPORT
-------------------------------
Subsystem type.......................... CICS
Subsystem name.......................... CICSDAU1
Number of associated ASCBs.............. 0
Connector's TCB address................. 006D8B00
Connector's protect key................. 08
DETAIL OF MONITORING ENVIRONMENT SUB-REPORT
-------------------------------------------
Monitoring token........................ FF70BDA8
Control token........................... 06DFD2C0
Owner's TCB address..................... 006D8B00
Subsystem type.......................... CICS
Subsystem name.......................... CICSDTU1
State of work request................... WAIT TIMER
Switch continuation information......... N/A
Abnormal condition...................... NONE
Service class token status.............. OLD
Service class........................ ********
Report class......................... ********
Protect key............................. 08
Owner data.............................. A0000000
Owner token............................. 00000000
Work request arrival time............... 02/14/1996 15:19:42
Work request execution start time....... 02/14/1996 15:19:43
Dispatching unit TCB.................... 00000000
Dispatching unit ASCB................... 00F5E400
Parent monitoring token................. 00000000
Parent control token.................... 00000000
Dependent monitoring token.............. 00000000
Dependent control token................. 00000000
Userid.................................. CICSUSER
Transaction name........................ CSSY
Transaction class....................... ********
Source LU name.......................... ........
- Total number of associated address spaces
- Decimal value indicating the total number of address spaces associated
with WLM in the system. This field represents the number of outstanding
address spaces which have either created a PB (IWMMCREA) or connected
to WLM (IWMCONN) at some point.
- Total number of monitoring envs in system
- Decimal value indicating total number of PBs in the system. This
field represents the number of outstanding PBs created via IWMMCREA
which are still in existence.
- ASID
- The value of this field is the ASID of the address space that
owns the XDAT.
- Total number of monitoring envs owned
- Decimal value indicating total number of PBs currently owned by
the address space.
- ASCB address
- The ASCB address associated with the address space.
- Connect token
- The connect token associated with the work manager who has connected
to WLM. This field is zero when there is no associated connect token.
- Subsystem Type
- The subsystem type specified on the connect service. This is the
generic product identifier associated with the code which connected
to WLM.
- Connection flags
- Specifies the connection flags. The xxxxxxxxxxxxx flag is one
of the following. If no flag is set, the header for the connection
flags is not displayed.
- Used by SRM for system managed subsystem type
- Connection uses WLM work management services
- Connection uses WLM work queuing services
- Connection uses WLM work balancing services
- Connection uses WLM work execution services
- Connection uses WLM routing services
- Associated server is WLM started
- Subsystem name
- The subsystem name specified on the connect service. This is the
identifier of the specific instance associated with the code which
connected to WLM.
- Number of associated ASCBs
- The number of address spaces associated with this subsystem which
are not associated with PBs and which provide service to work running
within the subsystem.
- Connector's TCB address
- The TCB address associated with the connector.
- Connector's protect key
- The key for connector.
- Associated address space ASCB address
- The ASCB address in the topology list. This represents an address
space which is part of the subsystem servicing work which would not
be visible through monitoring environments.
- Monitoring token
- The value of this field is the PB address in storage.
- Control token
- The PBDE address in storage.
- Owner's TCB address
- The TCB address associated with the owner of the performance block.
- Subsystem Type
- The subsystem type associated with the performance block. This
is the generic product identifier associated with the code which obtained
the PB.
- Subsystem name
- The subsystem name associated with the performance block. This
is the identifier of the specific instance associated with the code
which obtained the PB.
- State of work request
- The state of the work request as shown in the performance block.
This field can be: FREE, ACTIVE, READY, IDLE, WAIT DISTRIBUTED, WAIT
CONVERSATION, WAIT SESSION LOCALMVS, WAIT SESSION SYSPLEX, WAIT SESSION
NETWORK, WAIT OTHER PRODUCT, WAIT MISCELLANEOUS, WAIT LOCK, WAIT I/O,
or UNKNOWN.
- Switch continuation information
- The switch information about the work request in the performance
block. This field can be: N/A(not switched), LOCALMVS, SYSPLEX, or
NETWORK. The latter three refer to the expectation of where the continuation
of the work request will be found.
- Abnormal condition
- One of the following:
- NONE - indicates that there exists no abnormal condition.
- SYSPLEX - indicates that abnormality affects all MVS™ images in sysplex.
- LOCALMVS - indicates that abnormality restricted to current MVS image.
- Service class token status
- One of the following:
- N/A - indicates that the service definition did not define a service
class for this work request.
- NORMAL - indicates that service class token is valid.
- OLD - indicates that service class token is not associated with
the current policy.
- NOT VALID - indicates that service class token is not valid.
- Service class
- If the service class token status is NORMAL then this is the service
class name associated with the work request. Otherwise this field
contains “********”.
- Report class
- If the service class token status is NORMAL then this field is
the report class name associated with the work request. Otherwise
this field contains “********”.
- Protect key
- The key in which the user of the monitoring environment runs.
- Owner data
- The value of this field is data specified by the owner/user. The
format of this data is unknown to MVS.
- Owner token
- The value of this field is token specified by the owner/user.
The format of this data is unknown to MVS.
- Work request arrival time
- Arrival time for work request in MM/DD/YYYY HH:MM:SS format. This
field contains all asterisks if the arrival time is not available.
- Work request execution start time
- Execution start time for work request in MM/DD/YYYY HH:MM:SS format.
This field contains all asterisks if the start time is not available.
- Dispatchable unit TCB
- Address of the TCB associated with the dispatchable unit serving
the work request attributes or character string “SRB” signifying an
SRB.
- Dispatchable unit ASCB
- Address of the ASCB associated with the dispatchable unit serving
the work request.
- Parent monitoring token
- The token for the parent monitoring environment or ASID for parent
when parent is an address space, which is set as a result of IWMMRELA
FUNCTION(CONTINUE).
- Parent control token
- The value of this field is token for the parent control environment,
which is set as a result of IWMMRELA FUNCTION(CONTINUE).
- Parent token ASID
- This message is issued when the parent control token is non-zero
and the ASID of the owning address space can be obtained to display
the ASID of the owner.
- Dependent monitoring token
- The token for the dependent monitoring environment related to
this environment, which is set as a result of IWMMXFER FUNCTION(CONTINUE).
- Dependent control token
- The token for the dependent control environment, which is set
as a result of IWMMXFER FUNCTION(CONTINUE).
- Dependent token ASID
- This message is issued when the dependent control token is non-zero
and the ASID of the owning address space can be obtained to display
the ASID of the owner.
- Userid
- The user ID associated with the work request. This field contains
all asterisks if the user ID is not available.
- Transaction name
- The transaction name associated with the work request. This field
contains all asterisks if the transaction name is not available.
- Transaction class
- The transaction class associated with the work request. This field
contains all asterisks if the transaction class is not available.
- Source LU name
- The source LU name associated with the work request. This field
contains all asterisks if the source lu name is not available.
- No monitoring environment to report on
- This message is issued when there is no PB to report on for this
address space.