Step 2. Collect SMF type 89 records

You can continue to use your installation's current SMF procedures for dumping and saving the type 89 records providing those procedures:

Collect SMF records from MVS™ images that you need.
Allow for the type 89 records to be saved long enough to be processed by the usage report program, IFAURP.

Because of the important role that type 89 records play in reporting on registered products and establishing software charges, installations can choose to modify existing SMF procedures to create and maintain unique SMF data sets that contain only type 89 records. An installation can separate the type 89 records at any of several steps in the current SMF process, including the initial SMF dump step that dumps the contents of the current full SMF data set(s) to another data set created by the installation.

The job step that performs this dumping and clearing process can selectively write the type 89 records to another SMF data set. Because the type 89 records are expected to need relatively little space, many installations might decide to manage type 89 records in separate data sets. The example that follows contains sample JCL, which shows how to write type 89 records to a separate data set as a part of the existing SMF dumping/clearing job step. Bold face type highlights the changes made to an existing SMF dump procedure to separate the type 89 records.

//STEP0    EXEC PGM=IFASMFDP
//SYSPRINT DD   SYSOUT=*
//DUMPIN1  DD   DSN=SYS1.MANx,DISP=SHR
//DUMPIN2  DD   DSN=SYS1.MANy,DISP=SHR
//DUMPOUT  DD   DSN=customer.usual.dump.dataset,DISP=.....
//USAGE    DD   DSN=customer.type89.dump.dataset,DISP=....
//SYSIN    DD   *
      INDD(DUMPIN1,OPTIONS(ALL))
      INDD(DUMPIN2,OPTIONS(ALL))
      OUTDD(DUMPOUT,TYPE(0:255))
      OUTDD(USAGE,TYPE(89))