A Log Stream can be defined to the IBM System Logger as resident in the Coupling Facility or as DASDONLY. When defined as resident in the Coupling Facility a single Log Stream can be defined for all the CA Vtape Subsystems running on LPARs that share that coupling facility. When defined as DASDONLY, each Subsystem must have a different Log Stream defined for it.
We recommend that DASDONLY Log Streams be used.
The operating system will keep the External Logger data in VSAM linear data sets (LDS) for the period of time specified when the Log Stream is defined. The LDSs are managed by the operating system and are never referenced in JCL to read the logger data.
To access the data in a Log Stream, the IBM LOGR subsystem is used. You code a DD in your JCL with a DSN parameter containing the Log Stream name and a SUBSYS parameter pointing to LOGR. Data selection criteria can also be coded as part of the SUBSYS parameter. Sample JCL to access Log Stream data and write it to a sequential data set can be found in HLQ.CCUUJCL(GENLOGR).
You can customize GENLOGR to select the previous days Log Stream data and copy it to a CA Vtape set of Virtual Volumes. By scheduling this job to run daily, Log Stream data can be kept for days, weeks, or months and used for historical reporting and troubleshooting.
The IPCS utility is the reporting tool for both the Internal and External Logger. Sample JCL can be found in HLQ.CCUUJCL(IPCS).
Note: For more information about the IPCS utility, see the chapter “Troubleshooting” in the Administration Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|