GRS EQDQ Monitor
This chapter describes the new enhancements to GRS EQDQ that monitor capture ENQ/DEQ diagnostics for problem determination while minimizing the effect to system performance.
7.1 EQDQ Monitor overview
Monitoring and diagnosing ENQ-related errors in z/OS might be difficult without built-in tracing options. The use of GRS EQDQ monitor (ISGAUDIT) provides tracing at the cost of ENQ performance.
New enhancements to GRS EQDQ monitor capture ENQ/DEQ diagnostics for problem determination while minimizing the effect to system performance. It also uses SMF 87 and is more cohesive, understandable filtering than EQDQ Monitor.
7.1.1 Changes in z/OS V2R2
Before you can use new GRS EQDQ capabilities, you must activate SMF Tracing of Type 87 in SMFPRMxx. The following subtypes that can be traced for specific information:
•SYS(TYPE(87(1))) for subtype 1 only: QSCAN
•SYS(TYPE(87(2))) for subtype 2 only: ENQ/DEQ
•SYS(TYPE(87)) for all subtypes
SMF 87 Recording in V2R2 drives SMF exit IEFU84 switching from IEFU85 with OA42221.
In z/OS V2R2, SMF 87 records are no longer cut under the caller’s thread. Instead, SMF type 87 subtype 1 is cut whenever global generic queue scan is issued while subtype 2 has multiple ENQ/DEQ requests per record that are cut within one SMF interval.
Because new records are tracked by SMF, consider planning SMF resources for the new data stream and consider the use of a separate log stream for type 87s to avoid running out of space for other types because SMF 87 subtype 2s can be cut in much greater frequency.
The following subtypes are available in SMF 87:
•SMF 87 Subtype 1 - QSCAN:
– SMF87RHS: Header
– SMF87DEF: Self-defining section
– SMF87REQ: Requester section
– SMF87QSCAN: Queue scan section
These subtypes are cut whenever global generic queue scan is issued and are introduced to help track queue scan abusers.
•SMF 87 Subtype 2 - ENQ/DEQ:
– SMF87RHS: Header section
– SMF87DEF: Self-defining section
– SMF87REQ 1 - n: Requester section; includes items, such as PSW, JOBNAME, ASID, TCB, and time of request. New fields added that are specific to ENQ/DEQ.
– SMF87ENQ 1 - n: Data Section; includes QNAME, RNAME, SCOPE, and other information about the request parameters.
You can set up the filters you want to include or exclude from monitoring in GRSMONxx member. The * and ? wildcard characters can be used in the definition of the filters and the filters can be defined in any sequence. Also, Exclude list trumps Include list.
Example 7-1 shows a sample configuration of GRSMONxx member. Long RNAMEs are supported up to 255 characters.
Example 7-1 Sample GRSMONxx member
FILTER INCLUDE ENQDEQ QNAME(SYSDSN) RNAME(*)
SCOPE(SYSTEMS)
FILTER EXCLUDE ENQDEQ QNAME(*) RNAME(*)
JOBNAME(MYJOB)
FILTER INCLUDE QSCAN GENERIC(YES) XSYS(YES)
FILTER INCLUDE ENQ QNAME(*) RNAME(*)
RNLMATCH(YES)
|
Note: Avoid FILTER INCLUDE ENQ QNAME(*) RNAME(*) without other modifier because it produces too much data. For more information, see SYS1.SAMPLIB(ISGMON00).
|
After you enable SMF type 87 records and define the monitor filters, you can control GRS monitoring by using one of the following commands:
•SETGRS MONITOR=YES
Enables the GRS Monitoring with existing filtering.
•SETGRS MONITOR=NO
Disables the GRS monitoring.
•SETGRS GRSMON=xx
Changes the active filters and activates, where xx corresponds to GRSMONxx.
•MONITOR(YES|NO) keyword in GRSCNFxx
No GRSMON(xx) analog in GRSCNFxx.
•Display GRS[,SYSTEM]
Shows MONITOR status and current GRSMONxx.
There are no migration and coexistence considerations because this solution is a single-system solution.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.