Use the Resource Requests attributes to display the System Automation Manager's view of requests for resources in the SA z/OS subplex denoted by the managed system name.
ORIGINNODE
The
name of the SA z/OS subplex,
that is, the group of systems controlled by a single primary automation manager and
configured to the same XCF group. The valid format is a character
string with a maximum length of 32 bytes and the following syntax:
sysplex:saplex:SA
RSCNAME
The
name of the resource that the request was made against.RSCTYPE
The
type of an automation resource, that is, the second qualifier of the
resource name in automation manager notation.
The valid types are:SYSNAME
The name of the system
where the resource resides. Blank for sysplex resources.REQACT
The action requested for
this resource and the scope of this action. The scope specifies whether
the action affects the resource itself or its descendants, or both.
The list of possible actions are:REQCTIME
The
date and time when the request was made.REQSRC
Indicates who made the request.
It is normally OPERATOR or AUTOOPS, but can also be anything else.
If the request was made by an operator it also shows the operator
ID. Note that each source can have only one active request of each
type against each resource. While votes relating to other requests
are propagated to the resource, if the source makes a second request
directly against the resource, it will replace the first request.REQPRIO
The hexadecimal priority
of the request. It determines the importance of this request relative
to other requests within the resource structure. The higher this value,
the higher is the request's priority.REQSTAT
The status of the request.
A request can be pending (P), winning (W), or losing (L). Requests
can furthermore be satisfied (S), unsatisfied (U), or timed out (T).
The status is a combination of these attributes, for example W/S/T
represents a satisfied winning request that timed out.REQMOD
An
optional request modifier that can be specified in combination with
the timeout: The default behavior is 'Message'. Only set when a timeout has been specified.
REQOVERR
Possible override options
passed with the request. The override options can be used to bypass
the conditions and settings that would otherwise prevent a resource
from starting or shutting down. It can be 'NO', 'ALL', or a combination
of the following options:USERID
The operator ID that issued
the request, if applicable.COMMENT
A comment that is associated
with the request.APPLPARM
Optional
application parameters that can be specified with the request. If
the text is longer than 32 characters, it is truncated and ends with
"...".REQAREM
Optional
specification of observed states that, when seen, cause the automatic
removal of this request. The observed states that can be specified
are a combination of AVAILABLE, DEGRADED, SYSGONE, and UNKNOWN.RESTART
Specifies whether the resource
should be restarted automatically after it has been shut down completely.REQTYPE
An
optional start or stop type for the request. Start types can be NORM
or any other customer-defined start types. The standard stop types
are NORM, IMMED, and FORCE.REQTTIME
Optional
time when the request will time out (GMT).REQETIME
Optional
time when the request will expire (GMT).CTWSTART
Count
is set to 1 if this request is a winning start request.CTWSTOP
Count
is set to 1 if this request is a winning stop request.CTLSTART
Count
is set to 1 if this request is a losing start request.CTLSTOP
Count
is set to 1 if this request is a losing stop request.CTOPERR
Count
is set to 1 if this request is an operator request.REQPRIOC
The
priority class is set according to the hexadecimal priority string
denoted by the Priority attribute. It can have the following values:
NA, Low, High, and Force.RSCRUNM
The runmode name for a runmode request.RSCRUNTOKEN
The list of runtokens for a runmode
request.