Explanation
This message is issued as a result of the D GRS,ANALYZE,LATCH
command. The format of this message depends on which parameters are
specified on the command.
Text is:
- Output for DISPLAY GRS,ANALYZE,LATCH,BLOCKER
The system displays
the following lines when a DISPLAY GRS,ANALYZE,LATCH,BLOCKER command
is entered:
LONG BLOCKER ANALYSIS: request specification
OWNTIME JOBNAME E/S CASID LSETNAME/LATCHID
hh:mm:ss jobname *r* casid lsetname
latchId
OTHER BLOCKERS: nn WAITERS: nn2
- Output for DISPLAY GRS,ANALYZE,LATCH,WAITER
The system displays
the following lines when a DISPLAY GRS,ANALYZE,LATCH,WAITER command
is entered:
LONG WAITER ANALYSIS: request specification
WAITTIME JOBNAME E/S CASID LSETNAME/LATCHID
hh:mm:ss jobname *r* casid lsetname
latchId
BLOCKER jobname2 r2 OTHER BLOCKERS: nn
- Output for DISPLAY GRS,ANALYZE,LATCH,DEPENDENCY
The system displays
the following lines when a DISPLAY GRS,ANALYZE,LATCH,DEPENDENCY command
is entered:
DEPENDENCY ANALYSIS: request specification
descriptor
WAITTIME JOBNAME E/S CASID LSETNAME/LATCHID
hh:mm:ss jobname *r* casid lsetname
latchId
BLOCKER jobname2 r2
ANALYSIS ENDED: analysis outcome
- Output for DISPLAY GRS,ANALYZE,LATCH,BLOCKER,DETAIL
The system
displays the following lines when a DISPLAY GRS, ANALYZE,LATCH,BLOCKER,DETAIL
command is entered:
LONG BLOCKER ANALYSIS: request specification
BLOCKER JOBNAME: jobname (ASID=asid, TCB|WEB=wuaddr)
REQUEST: reqtype [(WITH nn OTHERS)] LT:latchtoken
BLOCKING hh:mm:ss RESOURCE (CREATOR ASID= casid)
lsetname LST:lsettoken
latchId
THERE ARE nn2 REQUESTS WAITING FOR THIS RESOURCE
- Output for DISPLAY GRS,ANALYZE,LATCH,WAITER,DETAIL
The system
displays the following lines when a DISPLAY GRS,ANALYZE,LATCH,WAITER,DETAIL
command is entered:
LONG WAITER ANALYSIS: request specification
WAITER JOBNAME: jobname (ASID=asid, TCB|WEB=wuaddr)
REQUEST: reqtype [(WITH nn OTHERS)] LT:latchtoken
WAITING hh:mm:ss FOR RESOURCE (CREATOR ASID= casid)
lsetname
LST:lsettoken
latchId
BLOCKER JOBNAME: jobname2 (ASID=asid2, TCB|WEB=wuaddr2)
REQUEST: reqtype2 [(WITH nn2 OTHERS)]
- Output for DISPLAY GRS,ANALYZE,LATCH,DEPEND,DETAIL
The system
displays the following lines when a DISPLAY GRS,ANALYZE,LATCH,DEPEND,DETAIL
command is entered:
DEPENDENCY ANALYSIS: request specification
descriptor
JOBNAME: jobname (ASID=asid, TCB|WEB=wuaddr)
REQUEST: reqtype [] LT:latchtoken
state hh:mm:ss FOR RESOURCE (CREATOR ASID= casid)
lsetname
LST:lsettoken
latchId
ANALYSIS ENDED: analysis outcome
- Error Output for DISPLAY GRS,ANALYZE,LATCH
The system displays
the following lines when a DISPLAY GRS,ANALYZE,LATCH command is entered
and encounters an error:
PROCESSING ENDED:
error_reason
In the message text:
- time
- The time the command was issued.
- request specification
- The input was specified by the command issuer, and can have a
combination of the following possible values:
- ASID=rsasid
- JOBNAME=rsjobname
- CASID=casid
- CJOBNAME=cjobname
- ASID=rsasid, TCB=rstcbaddr\
- ASID=rsasid,WEB=rswebaddr
- JOBNAME=rsjobname, TCB=rstcbaddr
- JOBNAME=rsjobname,WEB=rswebaddr
Note: ASID, JOBNAME, and XJOBNAME are mutually exclusive.
- hh:mm:ss
- The length of time the latch request has been in that state. For
blockers this is the time when it has owned the resource. For waiters
this is the time when it has been waiting.
- jobname, jobname2
- When the jobname can not be obtained, *UNAVAIL will be displayed.
This can be due to the address space having terminated or due to the
latch queues changing too quickly.
- casid
- The hexadecimal asid of the latch set creator.
- lsetname
- The requested latch set name. T indicates that the name has been
truncated.
- latchId
- The requested latch number and identity. If no latch identity
is provided, the latch number will be shown followed by "(ID NOT SPECIFIED)"
When DETAIL is requstested the ID will fill up to four lines and be
truncated after 255 characters. Non-DETAIL will use only one line.
- r, r2
- The latch request type: E for exclusive or S for shared.
- reqtype, reqtype2
- The latch request type: EXCLUSIVE or SHARED.
- descriptor
- LONG WAITER #xx
- LONG BLOCKER #xx
where xx is the long waiter or latch blocker number with
respect to the output message.- analysis outcome
- DATA NOT AVAILABLE - DIAG=xxxxxxxx yyyyyyyy
The
latch data was changing so rapidly that an accurate snapshot could
not be obtained.
- THIS UNIT OF WORK IS NOT WAITING.
The unit of work at the end
of the dependency chain is not waiting for a latch. The last requestor
shown is the fundamental blocker of this analysis. Determine why this
requestor is held up.
- A DEADLOCK WAS DETECTED.
An apparent deadlock between
multiple units of work has been detected. None of the units of work
in the list proceed until one or more of them
release ownership.
Note: It
is possible that a true deadlock does not exist if one of the units
of work passed the responsibility to release ownership 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 releases ownership
before waiting to be posted.
- INTERNAL ERROR
The DISPLAY GRS,ANALYZE,LATCH command processor
failed. A dump is produced to record the problem.
- nn,nn2
- The count of requests as specified by the surrounding text. The
count is decimal.
- tcbaddr, tcbaddr2, webaddr, webaddr2
- The tcb address or WEB address for SRBs of the latch requestor.
- asid, asid2
- The asid of the latch requestor. The asid and asid2 are hexadecimal.
- state
- BLOCKING or WAITING.
- lsettoken
- The token of the latch set.
- latchtoken
- The latch token for the longest blocker of the resource.
- error_reason
- The error is caused by one of the following reasons:
- COULD NOT OBTAIN GRS PRIVATE STORAGE
- INTERNAL ERROR
System action
The system continues processing.
Operator response
Contact System Programmer.
System programmer response
- INTERNAL ERROR: Search problem reporting databases for a fix for
the problem. If no fix exists, contact the IBM® Support Center.
- DATA NOT AVAILABLE - DIAG=xxxxxxxx yyyyyyyy:
If there was an INTERNAL ERROR, try the request again. If this is
a consistent response, search problem reporting databases for a fix
for the issue. If no fix exists, contact the IBM Support Center.
- COULD NOT OBTAIN GRS PRIVATE STORAGE: Determine the cause of the
storage constraint. If the error was “INTERNAL ERROR,” collect the
dump generated by GRS and search problem reporting databases for a
solution. If one is not found, contact IBM support.
- For other cases: If there is an indication of a problem with a
GRS managed latch, the system programmer can choose to take an action
against one or more jobs or units of work. For more information about
diagnosing system related latch usage, see z/OS MVS Diagnosis: Reference.
Source
Global resource serialization