7.9 Tools

< Day Day Up >

The following are tools that are useful to control the system logger environment:

7.9.1 DUMP command parmlib member

IEADMCxx enables you to supply DUMP command parameters through a parmlib member and to specify the collection of dump data without having to remember and identify all the systems, address spaces and dataspaces involved.

The following is a recommended sample for the DUMP command to identify all the required documentation you need to collect to debug a system logger problem.

Example 7-16: IEADMC parmlib member sample

 TITLE  =(DUMP OF LOGGER AND RELATED DATA), JOBNAME=(IXGLOGR,XCFAS,ALLOCAS,SMS*,CATALOG,GRS,DFHSM), DSPNAME=('XCFAS'.*,'IXGLOGR'.*,'GRS'.*,'SMS*'.*), SDATA  =(COUPLE,ALLNUC,LPA,LSQA,PSA,SWA,RGN,SQA,TRT,CSA,GRSQ,          XESDATA,SUM), STRLIST=(STRNAME=&STRNAME.&STRNAME2.,LOCKENTRIES,ACC=NOLIM,          (LISTNUM=ALL,ENTRYDATA=SERIALIZE,ADJUNCT=CAPTURE)), REMOTE =(SYSLIST=*('IXGLOGR','XCFAS','ALLOCAS','SMS*',          'CATALOG','GRS','DFHSM'),DSPNAME,SDATA)

You can use the IEADMC parmlib member facility, prepare the member in parmlib and at the time of the error, simply enter the DUMP TITLE=(LOGGER PROBLEM),PARMLIB=xx command or you can use the standard DUMP command with all the above mentioned parameters.

For further information on how to set up the IEADMC parmlib member, refer to z/OS MVS Initialization and Tuning Reference, SA22-7592.

7.9.2 SMF88

System logger report data through SMF88. To collect SMF88 records, you need to request them through the parmlib member SMFPRM in the SYS and SUBSYS keywords either specifically or as part of a range of SMF records. If you want to change the recording after IPL, remember to issue the SET SMF=xx (where xx is the suffix of the SMFPRM member) command to activate the parmlib changes. The following is an example of an SMFPRM member to collect the logger SMF88:

Example 7-17: SMFPRM member

 NOBUFFS(MSG)                /* DEFAULT TO MESSAGE SYS(TYPE(30,70:79,88,89,100,101,110), EXITS(IEFU83,IEFU84,IEFU85,IEFACTRT,       IEFUJV,IEFUSI,IEFUJP,IEFUSO,IEFUTL,IEFUAV),       INTERVAL(SMF,SYNC),NODETAIL) SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84,IEFU85,IEFUJP,IEFUSO,        IEFACTRT),        INTERVAL(SMF,SYNC),        TYPE(30,70:79,88,89,100,101,110))

7.9.3 IXGRPT1

IXGRPT1 is available in SYS1.SAMPLIB. This program can help you analyze system logger SMF88 data for the systems in a sysplex. IXGRPT1 provides the following:

System logger interim storage related I/O activity
Nearness of the STRUCTURE FULL condition
Selected capacity planning information

The input to IXGRPT1 should be sorted by timestamp and log stream name. For sorting purposes, analysis programs should use timestamp field SMF88LTD (note that this field is in GMT format), created when the ENF signal was issued, rather than fields SMF88TME and SMF88DTE, which indicate when a particular record was written. If IXGRPT1 detects a sorting error in the input, an error message is produced and the program ends.

When you use the IXGRPT1 program, make sure to include type 88 subtype 1 records and indicate whether or not you wish to include DASD-only log stream information in this report or coupling facility data only.

Follow the instructions in the prolog of IXGRPT1 to run the utility or refer to JCL sample IXGRPT1J to run the utility.

The following is a list of information that can be obtained through the IXGRPT1 tool to document the interim storage I/O activity:

Number of bytes written by users via IXGWRITE during the interval (SMF88LWB)
Number of bytes written to interim storage during the interval (SMF88SWB)
Number of bytes written to DASD during the interval (SMF88LDB)
Number of bytes deleted from interim storage during interval without having been written to the log data set (SMF88SIB)
Number of deletes from interim storage during interval without having been written to the log data set (SMF88SII)
Number of bytes written to the DASD log data set and then deleted from interim storage during the interval (SMF88SAB)
Number of deletes from interim storage during interval written to the DASD log data set and then deleted (SMF88SAI)
Number of times the log stream was offloaded during interval (SMF88EO)
Number of times a request was made by system logger to write log stream data to DASD during the expiring SMF interval (SMF88LIO)
Number of times system logger had to suspend before writing log stream data to DASD because a previously-initiated write to DASD had not yet completed during the expiring SMF interval (SMF99LIS).

IXGRPT1 gives you also information about the nearness of STRUCTURE FULL condition for coupling facility log streams as follows. By analyzing the following fields, you can have an idea if the storage for the coupling facility structure needs to be tuned. These informations apply only to coupling facility log streams; for DASD-only log streams, these fields will be zeros.

Number of IXGWRITE invocations of completion type-1 (structure fullness in "normal" range)
Number of IXGWRITE invocations of completion type-2 (structure fullness in "warning" range)
Number of IXGWRITE invocations of completion type-3 (structure fullness in "critical" range)
Number of times all log stream in structure offloaded during interval
Number of times the structure full condition was actually reached

7.9.4 LOGR Couple Data Set Audit Tool

At the moment, there are no tool to audit the content of the LOGR CDS and compare it against the catalog to validate the existence of the offload data sets and highlight any discrepancies. If an installation has this need, something has to be manually built comparing the output of the IXCMIAPU LIST command and the LISTCAT report.

< Day Day Up >