This header indicates that the following information shows multisystem
enclave information. Note that the information is presented according
to the system table and export table structure, as follows:
- System Table Entries
- A sysplex can be comprised of up to 32 systems (1 to 32). Multisystem
enclave information is presented for each system defined in a Coupling
Facility Manager system table. Each system is referred to with the
header System Table Slot xx where xx is the slot in the system
table for a system.
- Export Table Entries
- An export table is comprised of 256 slot entries (0 to 255). Multisystem
enclaves are distributed across the export table slots. Each export
table is referred to with the header Export Table Slot xx where
xx is the slot in the export table. For each export table slot that
has a valid address, the related multisystem enclaves are displayed.
Here are the specific fields that appear under the Multisystem
Enclaves Information header:
- System Table Slot xx
- Header name that indicates that the following data represents
multisystem enclaves for a particular system.
- Export Table Slot xx
- Header name that indicates an export table slot. Only export
table slot headers are shown that have valid multisystem enclaves.
- Multisystem Enclave Local Data
- This header indicates that the following information is local
to the z/OS system.
- Queue ID
- Indicates whether the element is on the queue.
- Export Token
- Unique identifier for the multisystem enclave in the parallel
sysplex.
- Enclave Token
- Enclave token for the local enclave.
- Multisystem Enclave
- Address of the local cache entry buffer containing the multisystem
enclave.
- Update Version Number
- Update version number copied from the multisystem enclave the
last time it was successfully read from or written to the CF.
- Exporter Queue Head
- Exporter queue head.
- Exporter Queue Tail
- Exporter queue tail.
- Importer Queue Head
- Importer queue head.
- Importer Queue Tail
- Importer queue tail.
- Flags
- Header for CCB flags. The following list the flags that can be
displayed.
- Cache Entry Exists In The Cache Structure
- The cache entry exists in the cache structure, i.e. its deletion
hasn't been detected
- Undo Processing Has Started
- Undo-export or undo-import processing has started.
- Import Service Successfully Updated MSE In CF
- The import service successfully updated the multisystem enclave
in the coupling facility to show this system is a participant.
- Update Processor Currently Working On MSE
- The update processor is currently working on the multisystem enclave
This flag should help us not to trip over same multisystem enclave
in case of bad data. If a failure occurs during update processing
while the flag is on, the multisystem enclave will not be looked at
during subsequent update cycles.
- Export/Import Processing Complete
- The export/import processing is complete. This flag is used to
examine whether export/import processing has successfully created
the multi system enclave. If update processor trips over the customs
block with this flag off, it will remove the customs block and other
associated structures.
- Error Reason Code from XES
- Error reason code from last invocation of a XES service.
- Time This System Last Read MSE
- Time (STCK value) that this system last read the multisystem enclave
from the coupling facility. If no time exists then ‘None’ appears.
- Time This System Last Wrote MSE
- Time (STCK value) that this system last wrote the multisystem
enclave to the coupling facility. If no time exists then ‘None’ appears.
- Previous CPU Time
- Previous CPU Time that was accumulated on this system for this
multisystem enclave (STCK value). This will occur if a work manager
does multiple sequential imports. If no time exists then ‘None’ appears.
- Entry Number In FEAD Vector
- Entry number where the system entry for the current system is
created in the Foreign Enclave Acct Data (FEAD) vector.
- Multisystem Enclave
- This header indicates that the following information represents
a specific multisystem enclave.
- Header Section
- This header indicates that the following information represents
the MSE header data.
- Functionality Level
- The functionality level identifies incompatible changes to the
entry format. A downlevel system fails an import request for a cache
entry that has an uplevel functionality level. The level values for
a multisystem enclave have no relationship to the level values for
a service definition.
- MSE Length
- Actual control block length in bytes.
- Cache Entry Length In Bytes
- Cache entry length in bytes — actual length rounded up to the
next cache element boundary.
- Export Token
- Unique identifier for the multisystem enclave in the parallel
sysplex.
- Originating System Name
- Originating system name.
- Update Version Number
- Version number incremented each time the multisystem enclave is
written to the CF. Used in a compare-and-swap fashion to prevent one
system from overwriting another system's updates.
- Control Section Offset
- Offset to the control section.
- Control Section Length
- Length of the control section.
- Participant Section Offset
- Offset to the participant section.
- Participant Section Length
- Length of the participant section.
- Participant Section Number
- Number of participant section entries.
- Classify Section Offset
- Offset to the classification attributes section.
- Classify Section Length
- Length of the classification attributes section.
- FEAD Section Offset
- Offset to the foreign enclave resource data section.
- FEAD Section Length
- Length of the foreign enclave resource data section.
- Control Section
- This header indicates that the following information represents
the MSE control data.
- Service
- This is the total service of the original enclave and all foreign
enclaves. It is kept as a doubleword to avoid overflow. For performance
reasons it is not constantly updated. It is updated only as frequently
as necessary to support period switch and inflight projections.
- Arrival Time
- The original enclave‘s arrival time (STCK value). If no time
exists then ‘None’ appears.
- Service Class Name
- The original enclave's service class name.
- Classification Token
- The original enclave's classification token.
- Policy Activate Time
- This is the originating system's view of the time when the current
WLM service policy was activated. If no time exists then ‘None’ appears.
- Stoken
- Stoken of the address space which created the original enclave.
- Jobname
- Jobname of the address space which created the original enclave.
- Transaction Trace Token
- Transaction trace token.
- Control Section Flags
- Header for multisystem enclave control flags. The following list
the flags that can be displayed.
- Original Enclave Is Dependent
- The original enclave is dependent.
- Owner Was Reset To New Service Class Or Quiesced
- The owner of the original enclave was reset to a new service class
or quiesced — applies only if the original enclave is dependent.
- Owner Is Reset Quiesced
- The owner of the original enclave is reset quiesced — applies
only if the original enclave is dependent.
- Owner Was Created With The ASCRE HIPRI Attribute
- The owner of the original enclave was created with the ASCRE HIPRI
attribute, i.e. OucbxWasHiDp is on — applies only if the original
enclave is dependent.
- Owner Is Or Was Privileged
- The owner of the original enclave is or was privileged, i.e. OucbxWasPriv
is on — applies only if the original enclave is dependent.
- Owner Is A System Task
- The owner of the original enclave is a system task, i.e. OucbSyst
is on — applies only if the original enclave is dependent.
- Original Enclave Restarted By Policy Activation
- The original enclave was last restarted due to a policy activation.
- One or More Local Enclaves Reached Last Period
- At least one of the local enclaves has reached last period.
- Original Enclave Was Reset To New Service Class Or Reset Quiesced
- The original enclave (of this multisystem enclave) was either
reset to another service class or reset quiesced. If reset quiesced,
then the message described below is also shown.
- Original Enclave Was Reset Quiesced
- The original enclave (of this multisystem enclave) was reset quiesced.
This message is shown only in conjunction with the message described
above.
- Participant Section
- This header indicates that the following information represents
the MSE participant data.
The participant section contains information
for each system that is using a multisystem enclave. It is a fixed-size
array of 32 entries — the maximum number of systems in a sysplex.
A system uses its XCF system number (wmvt_system_number) to index
to its own entry in the array.
Only participant entries that
contain information are displayed.
- Participant Entry xx or No Participant Entries
- This header identifies the participant entry slot number or indicates
if no participant entries exist. If participant entries exist (Participant
Entry xx shown) then the following is displayed.
- System Token
- System token of participating system. Filled in on importing
systems only.
- Service
- Service accumulated by the enclave on this system.
- Creation Time
- Creation time of the local enclave in SRM format.
- Classification Section
- This header indicates that the following information represents
the MSE classification data. The classification data represents the
attributes (and possibly lengths) that can be specified via the IWMCLSFY
service. See the IWMCLSFY chapter in z/OS MVS Programming: Workload Management Services for
more information.
- Collection Length
- Correlation Length
- Procedure Name Length
- Process Name Length
- Subsystem Type
- Subsystem Name
- Transaction Name
- Userid
- Transaction Class
- Connection Type
- Correlation Identifier
- Logical Unit Name
- Network ID
- Plan Name
- Package Name
- Perform Value
- Subsystem Priority
- Scheduling Environment
- Subsystem Collection Name