This message is issued as a result of the D GRS,ANALYZE
command. The message has three different formats, depending on which
parameters were specified on the command. The system displays the
following lines when a DISPLAY GRS, ANALYZE,BLOCKER command is entered:
LONG BLOCKER ANALYSIS: request specification
BLOCKTIME SYSTEM JOBNAME E/S SCOPE QNAME RNAME
hh:mm:ss sysname jobname * scope qname rname[T]
r*
others
The first line
defines the format of the table. For each blocker that matches the
input specifications on the command, the information identified by
the header will be displayed. Starting with the longest blocker, the
displayed information includes:
- how long this request has been blocking the resource
- the system on which this request is running
- the jobname under which this request is running
- the type of enqueue, exclusive (E) or shared (S) (the asterisks
are used to help visually separate the lines of the messages)
- the scope of the request (SYS or SYSS)
- the resource qname and rname
- how many other requests are blocking this resource
- how many other requests are waiting for this resource.
The system displays the following lines when a DISPLAY
GRS, ANALYZE,WAITER command is entered:
LONG WAITER ANALYSIS: request specification
WAITTIME SYSTEM JOBNAME E/S SCOPE QNAME RNAME
hh:mm:ss sysname jobname * scope qname rname[T]
r*
BLOCKER sysname jobname r [others]
The first
line defines the format of the table. For each waiter that matches
the input specifications on the command, the information identified
by the header will be displayed. Starting with the longest waiter,
the displayed information includes:
- how long this request has been waiting for the resource
- the system on which this request is waiting for the resource
- the jobname under which this request is running
- the type of enqueue, exclusive (E) or shared (S) (the asterisks
are used to help visually separate the lines of the message)
- the scope of the request (SYS or SYSS)
- the resource qname and rname
- the longest blocker of this resource
- how many other requests are blocking this resource
- how many other requests are waiting for this resource.
The system displays the following lines when a DISPLAY
GRS,ANALYZE,DEPENDENCY command is entered:
DEPENDENCY ANALYSIS: request specification
descriptor
WAITTIME SYSTEM JOBNAME E/S SCOPE QNAME RNAME
hh:mm:ss sysname jobname * scope qname rname[T]
r*
BLOCKER sysname jobname r
The first line identifies
the element of the analysis that is being displayed. The second line
defines the format of the table.
For each element, each waiting
unit of work is reflected by the third line. The fourth line indicates
the top blocker of the resource. The third and fourth lines are repeated
until the analysis is completed. The displayed information includes:
- how long this request has been waiting for the resource
- the system on which this request is waiting for the resource
- the jobname under which this request is running
- the type of enqueue, exclusive (E) or shared (S) (the asterisks
are used to help visually separate the lines of the message)
- the scope of the request (SYS or SYSS)
- the resource qname and rname
- the longest blocker of this resource
The system displays the following lines when a DISPLAY
GRS, ANALYZE,BLOCKER,DETAIL command is entered:
LONG BLOCKER ANALYSIS: request specification
BLOCKER SYSTEM: sysname
JOBNAME: jobname (ASID=asid TCB=tcbaddr)
REQUEST: reqtype [(WITH nn OTHERS)]
state hh:mm:ss SYSTEM[S]RESOURCE
qname rname [T]
The
blocker for that resource and the number of other blockers and waiters
for the resource is displayed.
The system displays the following
lines when a DISPLAY GRS,ANALYZE,WAITER,DETAIL command is entered:
LONG WAITER ANALYSIS FOR request specification
WAITER SYSTEM: sysname
JOBNAME: jobname (ASID=asid TCB=tcbaddr)
REQUEST: reqtype [(WITH nn OTHERS)]
state hh:mm:ss SYSTEM[S]RESOURCE
qname rname [T]
The
waiter for that resource and the number of other blockers and waiters
for the resource is displayed.
The system displays the following
lines when a DISPLAY GRS,ANALYZE,DEPEND,DETAIL command is entered:
DEPENDENCY ANALYSIS: request specification
descriptor
SYSTEM: sysname
JOBNAME: jobname (ASID=asid TCB=tcbaddr)
REQUEST: reqtype [(WITH nn OTHERS)]
state hh:mm:ss SYSTEM[S]RESOURCE
qname rname [T]
The
first line identifies the long waiter number or resource owner number nn. For
each subsequent resource request, the first five lines are repeated.
Each resource request is dependent on the resource request identified
by the next five lines.
In the message text:
- request specification
- reflects the input specified by the command issuer, where:
- ENTIRE SYSPLEX
- is displayed if no additional parameters were specified.
- SYSTEM=sysname
- is displayed if SYSTEM was specified.
- SYSTEM=sysname ASID=asid
- is displayed if SYSTEM and ASID were specified.
- SYSTEM=sysname JOBNAME=jobname
- is displayed if SYSTEM and JOBNAME were specified.
- SYSTEM=sysname ASID=asid[
TCB=tcbaddr]
- is displayed if SYSTEM, ASID, and [,TCB tcbaddr]
were specified.
- SYSTEM=sysname JOBNAME=jobname
TCB=tcbaddr]
- is displayed if SYSTEM, JOBNAME, and [,TCB tcbaddr]
were specified.
- SCOPE=SYSTEMS RESOURCE
- qname rname[T]
- is displayed if DEPENDENCY, RES and SCOPE=SYSTEMS were
specified.
- SCOPE=SYSTEM RESOURCE SYSTEM=sysname
- qname rname[T]
- is displayed if DEPENDENCY, RES, SCOPE=SYSTEM,
and SYSTEM were specified.
- hh:mm:ss
- is the length of time the resource request has been in that state. hh:mm:ss could
have **:**:** when the value exceeds 100 hours.
- sysname
- is the resource requester's system name.
- jobname
- is the resource requester's jobname.
- r
- is the enqueue request type E (for exclusive) or S (for
shared).
- scope
- is the requested enqueue scope SYSTEM or SYSTEMS
- qname
- is the requested qname.
- rname
- is the requested rname. T indicates that rname is
truncated.
- others
- OTHER BLOCKERS: nn WAITERS:nn will
appear when there are additional blockers and waiters for the resource.
- descriptor
- indicates which element of the analysis is being displayed when
the DEPENDENCY keyword is specified, where:
- ----- LONG WAITER # nn
- is the nnth waiter element.
- ----- RESOURCE OWNER # nn
- is the nnth owner of the specified
resource.
- asid
- is the resource requester's address space ID (hexadecimal).
- tcbaddr
- is the resource requester's TCB address.
- reqtype
- is the enqueue request type, EXCLUSIVE or SHARED.
- state
- is the requester's state, WAITING or BLOCKING.
This only appears when the DETAIL keyword is specified.
- ANALYSIS ENDED: reason
- indicates that the analysis ended because of reason:
- THIS UNIT OF WORK IS NOT WAITING
- the unit of work at the end of the dependency chain is not waiting
for GRS—managed resources.
- A DEADLOCK WAS DETECTED
- an apparent deadlock between multiple units of work has
been detected. None of the units of work in the list will proceed
until one or more of them are ended.
Note: It is possible that a true
deadlock does not exist if one of the units of work passed the responsibility
to DEQ to a different unit of work. It is also possible that the apparent
deadlock resolves if one of the units of work specified an ECB and
issues a DEQ before waiting to be posted.
- INTERNAL ERROR
- the DISPLAY GRS,ANALYZE command processor failed. A dump is produced
to document the problem.
- UNABLE TO COMMUNICATE WITH BLOCKER SYSTEM
- the DISPLAY GRS,ANALYZE command is unable to communicate with
the system where the blocking job is running.
- GQSCAN FOR ANALYSIS FAILED
- the DISPLAY GRS,ANALYZE command is unable to obtain the blocker
from the GQSCAN service.
- SYSPLEX IS MIGRATING TO STAR MODE
- the DISPLAY GRS,ANALYZE command is unable to gather data during
the migration to STAR mode. Reissue the command when migration is
complete.
- PROCESSING ENDED: reason
- reason may be one of the following:
- COULD NOT OBTAIN STORAGE
- the DISPLAY GRS,ANALYZE command could not obtain sufficient storage
to process the command.
- COULD NOT SEND XCF MESSAGE
- the DISPLAY GRS,ANALYZE command was unable to send a message via
XCF. A dump will be produced to document the failure.
- INTERNAL ERROR
- An error occurred during processing. A dump is produced to document
the failure.
- GQSCAN REQUEST FAILED
- The DISPLAY GRS,ANALYZE command is unable to obtain the blocker
from the GQSCAN service.
- SYSPLEX IS MIGRATING TO STAR MODE
- The DISPLAY GRS,ANALYZE command is unable to gather data during
the migration to STAR mode. Reissue the command when migration is
complete.
- UNABLE TO COMMUNICATE WITH SYSTEM sysname:
- reason
- reason may be one of the following:
- THE SYSTEM DOES NOT SUPPORT GRS ANALYSIS
- The system is not at a high enough level to respond to a GRS ANALYSIS
command.
- THE SYSTEM IS NOT A MEMBER OF THE SYSPLEX
- A system that is not a member of the sysplex cannot respond to
a GRS ANALYSIS command.
- THE SYSTEM DID NOT RESPOND TO THE ANALYSIS REQUEST
- The system did not respond to the request for analysis data. It
could be down or unable to respond.
The following lines may also appear in the message
text:- DATA MAY BE INCOMPLETE, NOT ALL SYSTEMS SUPPORT GRS ANALYSIS
- All systems in the sysplex are not at the same level.
- THERE ARE NO {BLOCKING|WAITING} TASKS MATCHING THE INPUT SPECIFICATION
- The DISPLAY GRS,ANALYZE command found no tasks that matched the
options specified on the command.
- GQSCAN FOR THE FOLLOWING RESOURCE FAILED: RC=rc RSN=rsn
- The DISPLAY GRS,ANALYZE command attempted to use the GQSCAN service
and failed with return code rc and reason code rsn.