JCL To Have TSSOERPT Read LOGSTREAM Structures Instead of SYS1.MAN datasets.
Article ID: 52946
Updated On:
Products
CA Cleanup
CA Datacom - DB
CA Datacom
CA Datacom - AD
CA Datacom - Server
CA CIS
CA Common Services for z/OS
CA 90s Services
CA Database Management Solutions for DB2 for z/OS
CA Common Product Services Component
CA Common Services
CA Datacom/AD
CA ecoMeter Server Component FOC
CA Easytrieve Report Generator for Common Services
CA Infocai Maintenance
CA IPC
Unicenter CA-JCLCheck Common Component
CA Mainframe VM Product Manager
CA Chorus Software Manager
CA On Demand Portal
CA Service Desk Manager - Unified Self Service
CA PAM Client for Linux for zSeries
CA Mainframe Connector for Linux on System z
CA Graphical Management Interface
CA Web Administrator for Top Secret
CA CA- Xpertware
CA Top Secret
CA Top Secret - LDAP
CA Top Secret - VSE
Issue/Introduction
Description:
When using the LOGSTREAM structures for SMF collection (instead of the SYS1.MAN datasets), can the TSSOERPT read the LOGSTREAM structures? If yes, what needs to be coded in the JCL?
Solution:
For z/OS 1.9 and above, SMF data may be sent to the LOGGER services controlling the writing of SMF data in the LOGSTREAM structures. SMF data will not be recorded in the usual SYS1.MANx data sets.
The RECxxxxx DD used to read the data has the format:
//RECxxxxx DD DSN=IFASMF.DATA.LOGSTRM,DISP=SHR, // SUBSYS=(LOGR,IFASEXIT,subsys-options1,subsys-options2)
Description of SUBSYS options-1 includes:
[FROM={({[yyyy/ddd][,hh:mm[:ss]]}) | OLDEST}]
[TO={({[yyyy/ddd][,hh:mm[:ss]]}) | YOUNGEST}]
[,DURATION=(nnnn,HOURS)]
[,VIEW={ACTIVE|ALL|INACTIVE}]
[,GMT|LOCAL]
The subsys-options1 parameters used by the IBM IFASEXIT are the same as those used by the IFBSEXIT. For information on the parameters for IFBSEXIT, see IBM's MVS Diagnosis: Tools and Service Aids.
Environment
Release:
Component: AWAGNT
Component: AWAGNT
Feedback
Powered by
