Customizing CA SMF Director › Placing Existing SMF Data under CA SMF Director Control › Placing a Multiple System Archive under Control

Placing a Multiple System Archive under Control

The architecture of the CA SMF Director historical archive requires that the SMF data be managed by a single SMF ID. For sites that have archives of SMF data with multiple SMF IDs, you must separate the data by SMF ID before it can be added to the CA SMF Director archive.

The most efficient way to do this is to set up a multiple-step job that reads the archived data with IFASMFDP. IFASMFDP can then be directed to create one temporary output data set for each SMF ID that you want to migrate. Then, in subsequent steps, CA SMF Director can be invoked for each system in the manner described above.

As an example, suppose one of your archives contains SMF data from two systems with the SMF IDs SYSP and SYST. The JCL to migrate this data would look like this:

 //         JOB
 //STEP001  EXEC PGM=IFASMFDP,REGION=0M
 //SYSPRINT DD   SYSOUT=*
 //SMFIN    DD   DSN=your.archive.data.set,DISP=SHR
 //SYSPOUT  DD   DSN=&&SYSP,DISP=(NEW,PASS),STORCLAS=TEMP,
 //              SPACE=(CYL,(200,100),RLSE),
 //              DCB=*.SMFIN
   INDD(SMFIN,OPTIONS(DUMP))
   OUTDD(SYSPOUT)
   SID(SYSP)
 /*
 //STEP002  EXEC PGM=SORT,REGION=6M
 //SYSPRINT DD  SYSOUT=*
 //SYSOUT   DD  SYSOUT=*
 //STEPLIB  DD  DSN=SYS1.SORTLIB,DISP=SHR
 //SORTWK01 DD  SPACE=(CYL,(300,50)),UNIT=SYSDA
 //SORTWK02 DD  SPACE=(CYL,(300,50)),UNIT=SYSDA
 //SORTWK03 DD  SPACE=(CYL,(300,50)),UNIT=SYSDA
 //SORTWK04 DD  SPACE=(CYL,(300,50)),UNIT=SYSDA
 //SORTIN  DD  DSN=&&SYSP,DISP=SHR
 //SORTOUT DD  DSN=&&SYSPS,DISP=(NEW,PASS),STORCLAS=TEMP,
 //             DISP=(NEW,CATLG,DELETE),
 //             SPACE=(CYL,(200,100),RLSE),
 //             DCB=*.SORTIN
 //SYSIN   DD   *
  SORT FIELDS=(11,4,PD,A,7,4,BI,A)
 /*
 //STEP003  EXEC PGM=IFASMFDP,REGION=0M
 //SYSPRINT DD   SYSOUT=*
 //SMFIN    DD   DSN=your.archive.data.set,DISP=SHR
 //SYSTOUT  DD   DSN=&&SYST,DISP=(NEW,PASS),STORCLAS=TEMP,
 //              SPACE=(CYL,(200,100),RLSE),
 //              DCB=*.SMFIN
 //SYSIN    DD   *
   INDD(SMFIN,OPTIONS(DUMP))
   OUTDD(SYSTOUT)
   SID(SYST)
 /*
 //STEP004  EXEC PGM=SORT,REGION=6M
 //SYSPRINT DD  SYSOUT=*
 //SYSOUT   DD  SYSOUT=*
 //STEPLIB  DD  DSN=SYS1.SORTLIB,DISP=SHR
 //SORTWK01 DD  SPACE=(CYL,(300,50)),UNIT=SYSDA
 //SORTWK02 DD  SPACE=(CYL,(300,50)),UNIT=SYSDA
 //SORTWK03 DD  SPACE=(CYL,(300,50)),UNIT=SYSDA
 //SORTWK04 DD  SPACE=(CYL,(300,50)),UNIT=SYSDA
 //SORTIN  DD  DSN=&&SYST,DISP=SHR
 //SORTOUT DD  DSN=&&SYSTS,DISP=(NEW,PASS),STORCLAS=TEMP,
 //             DISP=(NEW,CATLG,DELETE),
 //             SPACE=(CYL,(200,100),RLSE),
 //             DCB=*.SORTIN
 //SYSIN   DD   *
   SORT FIELDS=(11,4,PD,A,7,4,BI,A)
 /*
 //*
 //STEP005  EXEC PGM=SMFD,REGION=0M
 //STEPLIB  DD   DSN=CAI.CASFLOAD,DISP=SHR
 //SCDS     DD   DSN=CAI.SMFD.SCDS,DISP=SHR
 //SYSPRINT DD   SYSOUT=*
 //SYSXDIAG DD   SYSOUT=*
 //SMFIN    DD   DSN=&&SYSPS,DISP=SHR
 //SYSIN    DD   *
  SOURCE DUMP(SMFIN).
  DUMP.
 //*
 //STEP006  EXEC PGM=SMFD,REGION=0M
 //STEPLIB  DD   DSN=CAI.CASFLOAD,DISP=SHR
 //SCDS     DD   DSN=CAI.SMFD.SCDS,DISP=SHR
 //SYSPRINT DD   SYSOUT=*
 //SYSXDIAG DD   SYSOUT=*
 //SMFIN    DD   DSN=&&SYSTS,DISP=SHR
 //SYSIN    DD   *
  SOURCE DUMP(SMFIN).
  DUMP.
 //

Note that this example assumes the following:

• The history files are being written to tape or to a virtual tape subsystem (VTS).
• The DYNAM option is set so that the history files will be allocated dynamically by CA SMF Director.
• The original recording method for the SMF data was to a MAN file. If the SMF data was originally from a logstream file, it can be imported and archived with the correct logstream using the LSNAME and SID operands on the SOURCE statement.

Once the older SMF data archive has been placed under the control of CA SMF Director, the old archive can be deleted or migrated offsite. There is no need to keep the original archive.