Allocating the problem determination aid (PDA) log data sets

Figure 1 shows how to allocate and catalog the problem determination log data sets. These data sets have been allocated for a single DFSMShsm-host as part of the starter set.

Figure 1. Sample JCL Job that Allocates and Catalogs the PDA Log Data Sets

 /***********************************************************************/
 /* SAMPLE JOB THAT ALLOCATES AND CATALOGS THE PDA LOG DATA SETS.       */
 /***********************************************************************/
 /* 
 //ALLOPDO JOB MSGLEVEL=1,TYPRUN=HOLD 
 //STEP1   EXEC PGM=IEFBR14 
 //DD1     DD DSN=&UID..?HOSTID..HSMPDOX,DISP=(,CATLG),UNIT=?TRACEUNIT., 
 //           VOL=SER=?TRACEVOL.,SPACE=(CYL,(20)) 
 //DD2     DD DSN=&UID..?HOSTID..HSMPDOY,DISP=(,CATLG),UNIT=?TRACEUNIT., 
 //           VOL=SER=?TRACEVOL.,SPACE=(CYL,(20)) 
 /*

Change the User ID (?UID.), the processing unit ID (?HOSTID.),the trace unit (?TRACEUNIT.), and the volume serial number (?TRACEVOL.) parameters to names that are valid for your environment. The LRECL and RECFM fields will be set by DFSMShsm when the data set is opened and are not required in the JCL. These data sets must be variable blocked physical sequential and must not be striped. Both data sets must be allocated to the same volume. If you allocate them as SMS-managed data sets they must be associated with a storage class having the GUARANTEED SPACE attribute. They should not be associated with a storage class that will conflict with the required data set attributes. If you are using the starter set, the two DD statements (DD1 and DD2) that you need are already allocated.

Attention: If you allocate the problem determination log data sets as SMS-managed data sets, they must be associated with a management class that prohibits backup and migration. If you allocate them as non-SMS-managed data sets, they must be on a volume that DFSMShsm does not process for backup or migration.