Work Manager/Resource Manager State Section

This section defines subsystem work manager delay arrays per service class period. Value R723CWMN in the Service Class Period data section gives the number of entries in this section per service class period.

Entry in the subsystem work manager delay array.

There are always two entries for a subsystem:
Offsets Name Length Format Description
0 0 R723RTYP 4 EBCDIC Subsystem type, as used in the classification rules specified in the WLM administrative application. The subsystem's documentation should explain the meaning that the product attributes to the various states.
4 4 R723RFLG 1 binary Work/Resource manager flags.
Bit
Meaning when set
0
States sampled in the begin_to_end phase of a transaction.
1
States sampled in the execution phase of a transaction.
2-7
Reserved.
5 5   3   Reserved.
8 8 R723RESS 4 binary Total number of transaction states sampled in the phase specified by R723RFLG.
12 C R723RACT 4 binary Total number of active state samples. Active indicates that there is a program executing on behalf of the work request, from the perspective of the work manager. This does not mean that the program is active from the base control program's perspective.
16 10 R723RRDY 4 binary Total number of ready state samples. Ready indicates that there is a program ready to execute on behalf of the work request described by the monitoring environment, but the work manager has given priority to another work request.
20 14 R723RIDL 4 binary Total number of idle state samples. Idle indicates that no work request is available to the work manager that is allowed to run.
24 18 R723RWLO 4 binary Total number of waiting for lock state samples.
28 1C R723RWIO 4 binary Total number of waiting for I/O state samples. Waiting for I/O indicates that the work manager is waiting for an activity related to an I/O request. This may be an actual I/O operation or some other function associated with the I/O request.
32 20 R723RWCO 4 binary Total number of waiting for conversation state samples. Waiting for conversation may have been used in conjunction with the WLM service IWMMSWCH to identify where the recipient of the conversation is located. In this case, only the switched state will be recorded.
36 24 R723RWDS 4 binary Total number of waiting for distributed request state samples. Waiting for distributed request indicates a high level that some function or data must be routed prior to resumption of the work request. This is to be contrasted with waiting for conversation, which is a low level view of the precise resource that is needed. A distributed request could involve waiting on a conversation as part of its processing.
40 28 R723RWSL 4 binary Total number of waiting for a session to be established locally samples. Waiting for a session to be established locally, i.e. on the current MVS™ image.
44 2C R723RWSN 4 binary Total number of waiting for a session to be established somewhere in the network samples.
48 30 R723RWSS 4 binary Total number of waiting for a session to be established somewhere in the sysplex samples.
52 34 R723RWTM 4 binary Total number of waiting for a timer samples.
56 38 R723RWO 4 binary Total number of waiting for another product samples.
60 3C R723RWMS 4 binary Total number of waiting for unidentified resource samples. Waiting for unidentified resource, possibly among another more specific category, but which may not be readily determined.
64 40 R723RSSL 4 binary Number of states representing transactions for which there are logical continuations on this MVS image. Subsystem work managers might set this state when they function ship a transaction to another component within the same MVS image.
68 44 R723RSSS 4 binary Number of states representing transactions for which there are logical continuations on another MVS image in the sysplex. Subsystem work managers might set this state when they function ship a transaction to another component on another MVS image within the sysplex.
72 48 R723RSSN 4 binary Number of states representing transactions for which there are logical continuations somewhere within the network. Subsystem work managers might set this state when they function ship a transaction to another component within the network.
76 4C R723RWST 4 binary Total number of waiting for SSL thread samples.
80 50 R723RWRT 4 binary Total number of waiting for regular thread samples.
84 54 R723RWWR 4 binary Total number of waiting for work table registration samples.
88 58 R723RAPP 4 binary Total number of active application state samples.
92 5C R723RWNL 4 binary Total number of state samples reflecting waiting for new latch.
96 60 R723RW01 4 binary Total number of samples waiting for resource type 1.
100 64 R723RW02 4 binary Total number of samples waiting for resource type 2.
104 68 R723RW03 4 binary Total number of samples waiting for resource type 3.
108 6C R723RW04 4 binary Total number of samples waiting for resource type 4.
112 70 R723RW05 4 binary Total number of samples waiting for resource type 5.
116 74 R723RW06 4 binary Total number of samples waiting for resource type 6.
120 78 R723RW07 4 binary Total number of samples waiting for resource type 7.
124 7C R723RW08 4 binary Total number of samples waiting for resource type 8.
128 80 R723RW09 4 binary Total number of samples waiting for resource type 9.
132 84 R723RW10 4 binary Total number of samples waiting for resource type 10.
136 88 R723RW11 4 binary Total number of samples waiting for resource type 11.
140 8C R723RW12 4 binary Total number of samples waiting for resource type 12.
144 90 R723RW13 4 binary Total number of samples waiting for resource type 13.
148 94 R723RW14 4 binary Total number of samples waiting for resource type 14.
152 98 R723RW15 4 binary Total number of samples waiting for resource type 15.
156 9C R723RBPM 4 binary Number of state samples representing buffer pool misses that resulted in I/O.
160 A0 R723RDNX 2 binary Index into resource delay type names table.
162 A2 R723RDNN 2 binary Number of entries in resource delay type names table.
164 A4   8   Reserved.