Customizing CA SMF Director › Defining a Configuration to CA SMF Director

Defining a Configuration to CA SMF Director

A CA SMF Director configuration definition can be produced through the execution of the batch program. The following example shows how a configuration is defined to this product. See member CASFCTL1 in the CASFJCL library, loaded during the installation process.

//CASFUTIL JOB ... MSGLEVEL=(1,1),CLASS=A
//STEP1  EXEC PGM=SMFD,REGION=512K
//SCDS    DD DISP=SHR,DSN=CORP.SMFD.SCDS
//SYSPRINT DD SYSOUT=*
//SYSXDIAG DD SYSOUT=*
//SYSIN    DD *
   COMPILE CONFIGURATION STORE.
     OPTIONS AUTODEL DYNAM MAXLINES(56) SDAY(0600).              (2)
      BEGIN CONFIG(050) SID(XAD1) NAME('CORPORATE-NAME').        (1)
           DUMPOPTIONS COPIES(2) CATLG SCRATCH NOVERIFY
             RETPD(730) PREFIX(SYS2.SMFDATA)                     (3)
             ARETPD(90) APREFIX(SYS3.SMFDATA).
      END CONFIG(050).
   COMPILE CONFIGURATION STORE.
      BEGIN CONFIG(052) SID(H001)  NAME('CORP TEXT SYSTEM-1').
           DUMPOPTIONS COPIES(1) CATLG SCRATCH NOVERIFY          (4)
           LSNAME(IFASMF.ACCT IFASMF.RMFDATA IFASMF.TCPIP        (5)
                IFASMF.CICS IFASMF.DB2 IFASMF.OTHER)
           RETPD(90) PREFIX(SYS2.H001.SMFDATA).
      END CONFIG(052).
   COMPILE CONFIGURATION STORE.
      BEGIN CONFIG(053) SID(H002)  NAME('CORP TEXT SYSTEM-2').
           DUMPOPTIONS COPIES(1) CATLG SCRATCH NOVERIFY          (4)
           LSNAME(IFASMF.ACCT IFASMF.RMFDATA IFASMF.TCPIP        (5)
                IFASMF.CICS IFASMF.DB2 IFASMF.OTHER)
           RETPD(90) PREFIX(SYS2.H002.SMFDATA).
      END CONFIG(053).
/*
//

Note:

1. In this example, configurations for three z/OS systems with the SMF IDs of XAD1, H001 and H002 are defined.
2. The OPTIONS control statement allows the setting of product options, such as the maximum number of lines per page, and what time of day is considered to be the beginning of a logical work day.
3. The XAD1 configuration retains history file data sets with the high level qualifiers of 'SYS2.SMFDATA' for 2 years, and 90 days with the high level qualifier of "SYS3.SMFDATA".
4. Since the configurations specify SCRATCH, any available scratch tape volume will be used to dump SMF data. However, once a tape volume is started, future dumps will go to that tape volume until it is full, or until the maximum number of dumps on a single volume is reached.
5. If CA SMF Director is going to archive and manage SMF data that is being recorded to logstreams, these logstreams must be named in the LSNAME operand in the DUMPOPTIONS control statement. If a logstream is being shared between two or more systems, it must be named in all of the configurations for all of the systems that are recording data to that logstream.
6. If CA SMF Director is going to archive and manage SMF data that is being recorded to substreams, these substreams must be named in the SUBNAME operand in the DUMPOPTIONS control statement.