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

Change the User ID (?UID.), z/OS system image 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 DFSMSrmm when the data set is opened and are not required in the JCL. Do not add the RLSE parameter to the DD statement.

The EDGPDOX and EDGPDOY data sets must be allocated to the same volume. The EDGPDOX and EDGPDOY data sets must be cataloged, variable blocked physical sequential and must not be striped. The data sets are required only if you want to keep a permanent history of the trace data on DASD. Begin with an initial data set size of 30 cylinders. You can adjust the size as you gain more experience with the amount of activity that is traced in your installation. 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.

You must define a pair of trace output data sets for each z/OS image. Do not share the trace data sets with multiple DFSMSrmm systems or with other system components.