JCL To Have TSSOERPT Read LOGSTREAM Structures Instead of SYS1.MAN datasets.

Products

• Cleanup
• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ecoMeter Server Component FOC
• EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA On Demand Portal
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Top Secret
• Top Secret - LDAP
• 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