| < Day Day Up > |
|
In this section we discuss maintaining the System Logger component and what documentation should be collected when a problem occurs to speed up problem diagnosis.
Depending on the problem, the following seven methods may be used to collect the documentation needed to diagnose a System Logger problem. This documentation should be collected before contacting the IBM support center; for more information, see the System Logger chapter in z/OS MVS Diagnosis: Reference, GA22-7588: amongst other things, this chapter tells you how to set up a component trace for System Logger and how to interpret the output from an IXCMIAPU report.
Obtain a dump of the System Logger address space and any address spaces connected to the log stream you are experiencing a problem with. Refer to "DUMP command parmlib member" on page 260 for sample on the dump keywords.
Use the D LOGGER command to display the following information:
IXGLOGR address space status
D LOGGER,ST
Log stream, CF structure, and connection information.
D LOGGER,L
D LOGGER,STR
D LOGGER,C
Sysplex status for log streams.
D LOGGER,C,SYSPLEX
Specifics for DASD-only log streams.
D LOGGER,C,DASDONLY
D LOGGER,L,DASDONLY
Use IDCAMS to print the offload data sets for a log stream using the JCL shown in Example 2-11.
Example 2-11: IDCAMS job to print offload data sets.
//IDCAMS1 JOB (0,0),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID //*----------------------------------------------------------*/ //* PRINT contents of System Logger offload data set */ //* ---------------------------------------------------------*/ //* //PRINTIT EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //OFFLOAD DD DSN=hlq.xxx.A00000yyy.DATA,DUSP=SHR //SYSIN DD * PRINT INFILE(OFFLOAD) /*
Notes |
|
Obtain offload data set characteristics. You can use the sample JCL in Example 2-12 to display the characteristics of the data set you are dumping.
Example 2-12: IDCAMS sample JCL to show DS characteristics
//IDCAMS2 JOB (0,0),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID //PRINTIT EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * LISTCAT ALIAS ALL LISTCAT ALIAS ALL CAT('SROCAT.CATALOG') LISTCAT ENT('USER.CATALOG.NAME') ALL CAT('USER.CATALOG.NAME') LISTCAT LVL('HLQ_NAME') ALL /*
This job will:
Display all alias names specified in the master catalog, along with the associated user catalog for each alias.
Display all alias names defined in a specified catalog.
Display the contents of a user catalog and the volume on which it resides.
Display all information related to data sets with a particular high level qualifier.
Obtain a System Logger inventory detailed listing by running an IXCMIAPU LIST report as shown in Example 2-13.
Example 2-13: Sample IXCMIAPU report job
//LOGRRPT JOB (999,POK),'LOGR POLICY',CLASS=A,REGION=4M, // MSGCLASS=X,TIME=10,MSGLEVEL=(1,1),NOTIFY=&SYSUID //STEP1 EXEC PGM=IXCMIAPU //SYSPRINT DD SYSOUT=* //SYSABEND DD SYSOUT=* //SYSIN DD * DATA TYPE(LOGR) REPORT(YES) LIST LOGSTREAM NAME(logstreamname) DETAIL(YES) /*
If you suspect that the LOGR CDS is corrupted, print its contents using the job shown in Example 2-14.
Example 2-14: Sample job to dump the LOGR CDS
//DUMPCDS JOB (0,0),CLASS=A,MSGCLASS=X,NOTIFY=SYSUID //******************************************************/ //* RUN ADRDSSU to dump off the LOGR Couple Data set */ //******************************************************/ //STEP1 EXEC PGM=ADRDSSU,REGION=4M //SYSPRINT DD SYSOUT=* //DD1 DD DISP=SHR,VOL=SER=xxxxxx,UNIT=SYSDA //SYSIN DD * PRINT DATASET(logr.couple.dataset) INDDNAME(DD1) TOL(ENQF) /*
Note | As we discussed in 2.5, "Log streams" on page 22, specifying DIAG(YES) on the log stream definition will provide additional documentation in certain error cases that could not be otherwise collected. |
Set a SLIP trap. Your IBM support representative will provide you with the information you need to set the appropriate SLIP for the problem you are experiencing. See z/OS MVS Diagnosis: Tools and Service Aids, GA22-7589 for more information on this.
To avoid rediscovering problems that already have a fix available, it is important that you keep your System Logger component up to date. Therefore, we recommend you apply all PTFs for:
HIPER APARs
APARs with the keyword LOGRSERVICE in the APAR description
APARs with the keyword CFDUPLEX in the APAR description
| < Day Day Up > |
|