Setting up tracing for BPE-managed address spaces

The member of the IMS PROCLIB data set that you specify using the BPECFG= parameter in the execution parameters for the BPE-managed address spaces defines configuration parameters to the Base Primitive Environment (BPE), including trace levels.

1. To set the trace level for BPE-managed trace tables in the CQS, IMS Connect, ODBM, OM, RM, RS, SCI, and BPE-based DBRC address spaces, use the TRCLEV= statement in the BPE configuration parameter member of the IMS PROCLIB data set.
   The TRCLEV= parameter is used in the BPE configuration member of the IMS PROCLIB data set to specify the trace level for a trace table and, optionally, the number of pages of storage allocated for the trace table. You can specify one TRCLEV= parameter for each trace table type that BPE, CQS (common queue server), ODBM (Open Database Manager), OM (Operations Manager), RM (Resource Manager), Repository Server (RS), SCI (Structured Call Interface), IMS Connect, and BPE-based Database Recovery Control (DBRC) support.

   Trace tables are written to internal memory in the BPE address space unless you enable BPE external tracing for the trace table.

2. Enable BPE external tracing (writing trace data to an external data set as well as to memory).
   You must complete both of the following tasks:
   1. Define, or modify, the BPE configuration parameter member (BPECFG) of the IMS PROCLIB data set to include the external trace parameters:
      1. Add the EXTTRACE statement to the BPE configuration parameter member (BPECFG) of the IMS PROCLIB data set. This statement defines the external trace data set to IMS.
      2. Optional: update the TRCLEV statement for each trace table that is to be externalized by adding the EXTERNAL=YES keyword in the BPE configuration parameter member (BPECFG) of the IMS PROCLIB data set. This keyword causes the specified tables to be written to the external trace data set from the beginning of the address space. The default is EXTERNAL=NO. BPE trace tables can also be set to be written to the external trace data sets dynamically, by issuing the BPE UPDATE TRACETABLE command with the EXTERNAL(YES) parameter after the address space has started.
   2. Define a generation data group (GDG) for the external trace data set.
      Use the IDCAMS 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. If the data control block (DCB) characteristics of a GDG data set are not defined anywhere on the system, you must also define a prototype data set with the appropriate DCB characteristics on the volume containing the system catalog. Here is an example of how that JCL would look:

      //PROTOTYP JOB ...
      //STEP1 EXEC PGM=IEFBR14
      //BLDDSCB DD DSN=BPEEXTRC.GDG01,
      // DISP=(NEW,KEEP),
      // UNIT=SYSDA,
      // VOL=SER=PAGE01, <=System catalog volume
      // SPACE=(TRK,(0)),
      // DCB=(DSORG=PS,RECFM=VB,BLKSIZE=24580,LRECL=24576) 

      You can issue the IDCAMS DEFINE GENERATIONDATAGROUP command from an IDCAMS job, a TSO session, or a TSO command batch job, as shown in the following three examples, respectively.

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

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

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