Defining an external trace data set

Use the z/OS® DEFINE GENERATIONDATAGROUP command to define the GDG. The value that you specify for the NAME keyword in this command must match the data set name in the GDGDEF parameter of the EXTTRACE statement of the BPE configuration parameter member (BPECFG=) of the IMS PROCLIB data set.

Defining a GDG from an IDCAMS job

You can issue the z/OS DEFINE GENERATIONDATAGROUP command from an IDCAMS job, as shown in the following example.

//DEFGDG   JOB  ...
//STEP1    EXEC PGM=IDCAMS
//SYSPRINT DD   SYSOUT=A
//SYSIN    DD   *
   DEFINE GENERATIONDATAGROUP -
      (NAME(BPEEXTRC.GDG01) -
       NOEMPTY - 
       SCRATCH - 
       LIMIT(255))

Defining a GDG from a TSO session

You can issue the z/OS DEFINE GENERATIONDATAGROUP command from a TSO session, as shown in the following example.

DEFINE GENERATIONDATAGROUP (NAME(BPEEXTRC.GDG01) NOEMPTY SCRATCH LIMIT(255))

Defining a GDG from a TSO batch job

You can issue the z/OS DEFINE GENERATIONDATAGROUP command from a TSO command batch job, as shown in the following example.

//DEFGDG     JOB  ...
//STEP1      EXEC PGM=IKJEFT01
//SYSTSPRINT DD   SYSOUT=A
//SYSTSIN    DD   *
DEFINE GENERATIONDATAGROUP (NAME(BPEEXTRC.GDG01) NOEMPTY SCRATCH LIMIT(255))

For more information about the DEFINE GENERATIONDATAGROUP command, see z/OS DFSMS Access Method Services for Catalogs.

For additional information on trace data, see IMS Version 15 Diagnosis.