Dumping SMF Records

Older model IBM® VTS controllers (pre-TS7700) write statistical data to SMF Type 94 records and this is source for all data displayed for these devices in OMEGAMON® for Storage. If you are reporting a problem with this component of the product and the matrix instructs you to collect SMF records as part of the documentation you submit, you can do so by first switching the SMF data sets and then running a job to extract the Type 94 records from the most current copy of the MAN data set.

Before you issue the SWITCH command, you should issue DISPLAY SMF to be sure you have an alternate dataset available. You will also want to issue the DISPLAY to verify the name of the active data set.

D SMF

The system will respond similar to this:

IEE974I 15.43.10 SMF DATA SETS 605
NAME             VOLSER SIZE(BLKS) %FULL STATUS
P-RS22.MAN1      SFP100     18000    0   ALTERNATE
S-RS22.MAN2      SFP101     18000    84  ACTIVE
S-RS22.MAN3      SFP101     18000    0   ALTERNATE

In this case, the active data set is the one named RS22.MAN2. After the switch is issued, the system will close that data set and begin writing to another (probably RS22.MAN3). At that point, you may run your extract job against the previously active MAN data set (RS22.MAN2 in this case). Here’s a sample of the JCL you should use to extract the data.

//DUMP      EXEC PGM=IFASMFDP
//SYSPRINT  DD SYSOUT=*
//SMFIN     DD DISP=SHR,DSN=input_man_dataset
//SMFOUT    DD DSN=output_smf_extract,
//          DISP=(NEW,CATLG,DELETE),
//          SPACE=(CYL,(10,10),RLSE),
//          DCB=(LRECL=4096,BLKSIZE=32760,RECFM=VB)
//SYSIN     DD *
 INDD(SMFIN,OPTIONS(DUMP))
 OUTDD(SMFOUT,TYPE(94))
/*

Make appropriate changes to the data set names. The data set created by SMFOUT is the one you should TERSE and send to IBM support.