SMF start-up guidelines

The following steps indicate the major activities required to set up SMF data collection for the first time. These steps establish an SMF environment that collects both the SMF type 89 subtype 1 records required for measured usage charges and the type 89 subtype 2 records required for product registration reporting. Installations wishing to collect additional SMF records must make appropriate changes. See z/OS MVS System Management Facilities (SMF) for additional examples and a complete explanation of each of the following steps:

Allocate and format at least two SMF data sets (VSAM clusters) that are large enough to contain all the type 89 records generated between regular dumps of these data sets.
Type 89 records require relatively small amounts of DASD space. You might start with an initial allocation of 5 tracks per day for subtype 1 and subtype 2 records, then monitor the data set and adjust the size to reflect actual usage.
Establish procedures and jobs to dump and clear the SMF data sets on a regular basis.
These procedures involve dumping and clearing the SMF data sets after they have been made inactive either because they are full or because an operator entered the SWITCH SMF command. CBIPO provides sample SMF dumping procedures and corresponding jobs.
Depending on the volume of data and the size of the SMF data sets, you can run the SMF dump job daily or weekly. Because the space required to store type 89 records is relatively small, installations that collect only the type 89 record might consider scheduling weekly rather than daily dumps. The following example contains sample JCL to dump and clear one of the SMF data sets, SYS1.MANX.
```
//STEP0    EXEC PGM=IFASMFDP
//SYSPRINT DD   SYSOUT=*
//MANX     DD   DSN=SYS1.MANX,DISP=SHR
//USAGE    DD   DSN=customer.type89.dump.dataset,DISP=....
//SYSIN    DD   *
      INDD(MANX,OPTIONS(ALL))
      OUTDD(USAGE,TYPE(89))  
```
Note: If you want to collect other SMF records in addition to type 89 records, do not use this JCL.
If you want to collect only type 89 subtype 1 records, change the OUTDD statement in the example as follows:
```
      OUTDD(USAGE,TYPE(89(1)))  
```
Create an SMFPRMxx parmlib member that contains the SMF parameters you need for measured usage pricing.
The following example lists the parameters that must appear in the active SMFPRMxx member to enable measured usage pricing.
```
ACTIVE                         /* ACTIVATE SMF RECORDING       */
DSNAME(SYS1.MANX,SYS1.MANY)    /* USE DATASETS MANX AND MANY   */
SYS(TYPE(89))                  /* COLLECT TYPE 89 RECORDS      */  
```
Note: If you want to collect only type 89 subtype 1 records, change the SYS option in the example as follows:
```
     SYS(TYPE(89(1)))  
```

Once these steps are complete, continue with the changes listed in Guidelines for installations already collecting SMF data. Note that step 1 of this next section can be bypassed, because it was already completed in this section.