Previous Topic: Logstream Dump Process User Exit

Next Topic: Overlapping SMF Data

SMF Record Processing

Once SMFDLS is invoked to perform the logstream archive processing, it does the following:

SMFD has been modified for the logstream environment to process as a subtask to SMFDLS. The process by which records are archived in history files and indexed is different: the dump index entries for logstreams are managed by both SMF ID and logstream name.

At this point, the processing of the logstream SMF data is very similar to the MAN file processing, with the exception that the data is not being read in directly by SMFD, but rather it is passed to SMFD by an IFASMFDL user exit. The history records are written to history files and archived; then the index is updated just as before.

The following is a sample of the CASFDUML procedure:

//CASFDUML PROC LS=JCL.ERROR,A=A
//********************************************************************
//* CASFDUML - Logstream Dumping Procedure
//*
//* If automated dumping of SMF data recorded to logstreams is
//* being performed, modify a copy of this procedure and copy it
//* to a PROCLIB that contains started tasks.
//*
//* Modifications to be made (see notes in parentheses in the JCL):
//*
//* (1) Change the DSN to your Authorized CA SMF Director Load
//*     Library
//*
//* (2) The SMFDOUT DD is needed to drive the user exits used by
//*     the SMFDLS wrapper in the IFASMFDL utility.  While the
//*     default is to set the DD up as a DUMMY, it can also be
//*     allocated to a disk or tape output dataset at your
//*     discretion.
//*
//* (3) Change the DSN to the name of your SMF Control Data Set
//*     (SCDS)
//*
//* (4) Change the dataset name and member name to point to the
//*     required CA SMF Director Control Statement File. The
//*     shipped default contains the following statement:
//*
//*     DUMP.
//*
//* (5) Change the dataset name and member name to point to the
//*     required CA SMF Director logstream dump utility control
//*     statement file. The shipped default contains the following
//*     statements:
//*
//*        UNIT(SYSDA)
//*     *  STORCLAS(TEMP)
//*        JCL
//*
//*       Note: In the above example STORCLAS is a comment.
//*
//* (6) Change the value of UNIT to indicate a temporary DASD
//*     location, or, if SMS is in use, change the UNIT parameter
//*     to STORCLAS and indicate a temporary DASD location
//*
//*
//********************************************************************
//DUMP    EXEC PGM=SMFDLS,REGION=0M,TIME=1440
//STEPLIB  DD  DISP=SHR,DSN=CASFLOAD                  (1)
//SMFDLSPR DD  SYSOUT=&A.                **PRINT FROM SMFDLS
//SYSPRINT DD  SYSOUT=&A.                **PRINT FROM IFASMFDL
//CAIPRINT DD  SYSOUT=&A.                **PRINT FROM SMFD
//SYSXDIAG DD  SYSOUT=&A.
//SMFDOUT  DD  DUMMY                                  (2)
//SCDS     DD  DISP=SHR,DSN=CORP.CASMF.SCDS           (3)
//CAIIN    DD  DISP=SHR,DSN=CORP.CASMF.CNTL(SMFDDUMP) (4)
//SMFDLSIN DD  DISP=SHR,DSN=CORP.CASMF.CNTL(SMFDIN)   (5)
//CAILSNM  DD  DISP=(NEW,DELETE),SPACE=(TRK,1),       (6)
//             UNIT=SYSDA,DSN=&LS.

The variables in the procedure allow a SYSOUT class to be set by the START command as well. The LS operand is typically the only one set.

The CAIIN file contains the control statements for SMFD, and the SMFDLSIN file contains the control statements for SMFDLS. Typically, the CAIIN file should only contain the DUMP statement as well as any desired SPLIT statements.

The SMFDLSIN will typically have two statements in this environment:

For more information on the SMFD or SMFDLS control statements, see the User Guide.