The status of each system associated with the current global resource serialization complex is displayed. Some of the information displayed depends on whether you are running a global resource serialization ring or star complex. For instance, the status of the systems in the complex and the manner in which the systems are connected are different for a ring and a star complex.
The contents of the RESERVE conversion, SYSTEMS exclusion, and SYSTEM inclusion resource name lists (RNLs).
Information on resources for which there is contention or information about a specific resource.
A list of the units of work involved in contention for GRS-managed resources (both ENQ and Latch). This display can focus on the units of work that are waiting for the resources or those blocking the resources. In addition, the installation can display dependencies between requestors of GRS-managed resources. The display command provides both generic Contention and Analyze Contention functions. The Analyze function is recommended because it detects dependencies (including deadlock) between requestors, provides a complex wide view of System and Systems ENQ resources, and takes time into consideration to highlight the possible root cause of the contention. The Contention function only provides an alphabetical list of the resources that are in contention. The Contention function is not like the Analyze function in that a sysplex wide view of SYSTEM level ENQs is not provided in the former one. In addition to the SYSTEMS level ENQs, only the SYSTEM level ENQs that were requested from the issuing system are displayed. Also, time and dependencies are not considered. The Contention function is not like the Analyze function in that the former displays only System level ENQs that were requested from the issuing system and does not consider both time and dependencies.
When the keywords CONTENTION, RES=, RNL=, or any combination of them are specified together, the system will display a separate section for each keyword specified. Specifying the ALL keyword will override any parameters specified on the RNL= keyword.
The complete syntax for the DISPLAY GRS command is:
D GRS |
---|
|
When the global resource serialization ring complex is using XCF signalling, the display shows that XCF paths are used.
Specify HEX if you want the resource names displayed in EBCDIC and in hexadecimal. If the global resource serialization complex is inactive, the display does not contain system information, CTC link information, or the contents of RNLs. If the system did not start or join an active global resource serialization ring at IPL, the display does not contain system, link, and RNL information. When an RNL change is in progress, the display shows DELAY and SUSPEND information.
Specify LATCHID or LID when you want to identify latch id information (displayed with the latch number in the output message ISG343I). The latch id can help with problem diagnosis when the latch creator has provided each latch number a name.
Specify HEX if you want resource names displayed in EBCDIC and in hexadecimal.
The following are the various combinations of the CONTENTION, ENQ, JOBNAME, and LATCH parameters, and the information each produces:
A resource name must consist of a qname (major name) and can include an rname (minor name). If you specify an asterisk (*) as the last character in the resource name, then the system treats the name as a generic name; the display includes all resources with names that match the portion of the name specified before the asterisk. For example, SYSV* indicates that set of resources whose names begin with SYSV. If you specify major name without a minor name, the system displays just a list of the specified major names of those resources that have requestors. You can specify a generic qname with a specific rname, and conversely, a specific qname with a generic rname.
Specify the HEX operand if you want the resource names to be displayed in EBCDIC and hexadecimal. Use it when you have resource names that contain characters that will not appear on your console (that is, those characters that are not defined in the figure, “;English (U.S) I/O Interface Code for 3277,” which appears in IBM 3270 Information Display System).
How you specify qname (the major name) depends on the characters in the name.
How you specify rname (the minor name) depends on the characters in the name.
The default scope for the analysis is the entire sysplex.
The default scope for the analysis is the entire system.
If you omit this operand, the display is presented in the first available display area or the message area of the console through which you enter the command.
Example 1:
D GRS,RES=(*,*)
Performance implication: This command gives you data about every allocated ENQ/RESERVE resource on all systems in the global resource serialization complex; therefore, there might be a very large display. If this command produces a large amount of output, the command output might fill WTO buffers, and degrade system response time. If the display exceeds the current supply of WTO buffers, an ABEND 09A with reason code 46FA will occur.
ISG343I 15.08.31 GRS STATUS
NOT ENOUGH STORAGE TO COMPLETE THE REQUEST
Example 2:
D GRS,RES=(SYSDSN,*)
Example 3:
D GRS,DELAY
ISG343I 01:32:21 GRS STATUS
DELAY REASONS ON SYSTEM SYSA
JOBNAME ASID QNAME RNAME
USERJB1 0044 SYSDSN SYS1.XYZ
CATALOG 0007 SYSDSN SYS1.CHANGING.RESOURCE2
Example 4:
D GRS,SUSPEND
ISG343I 01:32:21 GRS STATUS
JOBS BEING SUSPENDED DUE TO RNL CHANGE ON SYSTEM SYSA
JOBNAME ASID QNAME RNAME
USERNM3 0089 SYSDSN SYS1.DATASET.CHANGING
USERNM4 0245 SYSDSN SYS1.XYZ.ABC
Example 5:
D GRS,RES=(SYSCTLG,*),HEX
SYSCTLG
EEECEDC
2823337
D GRS,RES=(GRJGQE07,*),HEX
ISG343I 15.17.06 GRS STATUS
S=SYSTEMS GRJGQE07 TESTCASE#SERIALIZATION#ENQ
CDDCDCFF ECEECCEC7ECDCCDCECECDD7CDD
79178507 35233125B2599139913965B558
SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS
S1 MAINAS11 001F 007DEB90 EXCLUSIVE OWN
Example 6:
D GRS,LATCH,CONTENTION
ISG343I 23.00.04 GRS LATCH STATUS 886
LATCH SET NAME: MY.FIRST.LATCHSET
CREATOR JOBNAME: APPINITJ CREATOR ASID: 0011
LATCH NUMBER: 1
REQUESTOR ASID EXC/SHR OWN/WAIT WORKUNIT TCB ELAPSED TIME
MYJOB1 0011 EXCLUSIVE OWN 006E6CF0 Y 00:00:40.003
DATACHG 0019 EXCLUSIVE WAIT 006E6B58 Y 00:00:28.001
DBREC 0019 SHARED WAIT 006E6CF0 Y 00:00:27.003
LATCH NUMBER: 2
REQUESTOR ASID EXC/SHR OWN/WAIT WORKUNIT TCB ELAPSED TIME
PEEKDAT1 0011 SHARED OWN 007E6CF0 Y 00:01:00.002
PEEKDAT2 0019 SHARED OWN 007F6CF0 Y 00:00:32.040
CHGDAT 0019 EXCLUSIVE WAIT 007D6CF0 Y 00:00:07.020
LATCH SET NAME: SYS1.FIRST.LATCHSET
CREATOR JOBNAME: INITJOB2 CREATOR ASID: 0019
LATCH NUMBER: 1
REQUESTOR ASID EXC/SHR OWN/WAIT WORKUNIT TCB ELAPSED TIME
MYJOB2 0019 SHARED OWN 006E6CF0 Y 00:01:59.030
LATCH NUMBER: 2
REQUESTOR ASID EXC/SHR OWN/WAIT WORKUNIT TCB ELAPSED TIME
TRANJOB1 0019 SHARED OWN 006E7B58 Y 01:05:06.020
TRANJOB2 0019 EXCLUSIVE WAIT 006E9B58 Y 00:01:05.003
ISG343I 23.00.04 GRS LATCH STATUS 886
NO LATCH CONTENTION EXISTS
Example 7:
D GRS,L,JOB=LISTCHK or D GRS,LATCH,JOBNAME=LISTCHK
ISG343I 23.00.04 GRS LATCH STATUS 886
LATCH DISPLAY FOR JOB LISTCHK
LATCH SET NAME: SYS2.PAYROLLAPP.LATCHSET
CREATOR JOBNAME: INITJOB1 CREATOR ASID: 0011
LATCH NUMBER: 1
REQUESTOR ASID EXC/SHR OWN/WAIT WORKUNIT TCB ELAPSED TIME
GETDAT1 0011 EXCLUSIVE OWN 007E6CF0 Y 00:01:07.030
GETDAT2 0019 EXCLUSIVE WAIT 007A6CF0 Y 00:00:31.050
SHOWDAT 0019 SHARED WAIT 007E6CF0 Y 00:00:25.010
LATCH NUMBER: 2
REQUESTOR ASID EXC/SHR OWN/WAIT WORKUNIT TCB ELAPSED TIME
LISTREC 0011 SHARED OWN 007B6CF0 Y 00:03:07.040
FINDBLK 0019 SHARED OWN 007C6CF0 Y 00:02:07.030
CHNGBLK 0019 EXCLUSIVE WAIT 007F6CF0 Y 00:02:03.002
Example 8:
D GRS,L,C,JOB=FINDREC or
D GRS,LATCH,CONTENTION,JOBNAME=FINDREC
Example 9:
D GRS,E,C or D GRS,ENQ,CONTENTION
Example 10:
D GRS,RNL=ALL
ISG343I 18.10.38 GRS STATUS
LIST TYPE QNAME RNAME
INCL GEN SYSDSN
INCLPATT SYSDSN SYS1.*.*
EXCL SPEC SYSDSN PASSWORD
EXCL PATT SYSDSN SYS?.*.*LIB
EXCL PATT SYSDSN SYS?.TEST
EXCL PATT SYSDSN SYS1.*.LOGREC
EXCL PATT SYSDSN SYS1.*.MANX
EXCL SPEC SYSDSN SYS1.BRODCAST
CON PATT* *
Note the use of wildcard characters in this example.