Trace Facilities

The trace facilities help you isolate problems by monitoring selected processes. When a trace facility is active, information is recorded in a system trace output file.
The trace facilities help you isolate problems by monitoring selected processes. When a trace facility is active, information is recorded in a system trace output file.
The trace formats of all traces are subject to change at any time. Therefore, we recommend that you 
do not
 use trace output in a production setting or write programs that interpret the trace output. Also, you should be selective in which traces you enable, because activating traces that are not needed results in unnecessary overhead.
To enable a trace facility, use the following syntax depending on whether you want to trace batch or foreground processing:
  • For foreground, use:
    alloc f(
    ) sysout(*)
  • For batch, use:
To route the output of the trace to a data set, replace sysout as follows:
  • For foreground, use:
    alloc f(
    ) da(
  • For batch, use:
    ,DISP=SHR //ddname DD DSN=
    Set the DSN attributes for the trace DSN as follows:
  • DDnames
    Specifies the name of the trace. The following traces are valid:
    • EN$TRALC
      Traces dynamic allocation.
    • EN$TRAUI
      Traces the Alternate ID. Also traces logon and logoff information.
    • EN$TRESI
      Traces ESI (Endevor External Security).
    • EN$TRFPV
      Traces component validation.
    • EN$TRITE
      Traces if-then-else evaluation.
    • EN$TRLOG
      Traces logon and logoff information.
    • EN$TROPT
      Traces Endevor table definitions.
      Writes SMF records. This trace requires the following dsname:
      //EN$TRSMF DD DISP=SHR,DSN=....,LRECL=27994,BLKSIZE=27998,RECFM=VB //* Writes SMF records to //EN$TRSMF. //* Requires DCB or existing file !
    • EN$TRSYM
      Traces symbolic resolution.
    • EN$TRXIT
      Traces Exits.
In cases of abnormal software termination (ABEND), a calling path trace back is generally produced. The trace back data is written to an output media selected from the following list in order of availability:
  1. File BSTERR (not available to T/P monitors) if provided
  2. User's Terminal (IDMS, TSO, CMS...)
  3. System console log
You should have this trace information available when you call your
CA Endevor
Trace Back Data
The following example shows a typical trace as shown on a terminal:
: F000
BC1PSM10: F000 ABEND CODE=MACR NUMBER=3009 BST PRODUCT: ENDEVOR VERSION: X.X RELEASE: XNNNN OPERATING SYSTEM: MVS/XA RELEASE: 038 TASK/JOB/USERID: DA1FB22 CALL FROM $FUNC=$BABEND EPA=00051BA8 R1=00058948 R14=80051E7C STACK=000588FO CSECT=BSTPMPGM 06/17/01 CALL FROM $FUNC=BSTPOPSV EPA=0004E5E8 R1=00058818 R14=8004E67A STACK=00058890 CALL FROM $FUNC=RESCHECK EPA=0004E6E8 R1=00058818 R14=8004E7D4 STACK=000587C0 CALL FROM $FUNC=BSTPOPSV EPA=0004E5E8 R1=00000000 R14=8004E68C STACK=00058760 CSECT=BSTPOPSV 06/17/01 CALL FROM $FUNC=BC1PINIT EPA=03A3BD98 R1=000586F8 R14=83A3BFC8 STACK=00058698 CSECT=BC1PINIT 09/09/01 CALL FROM $FUNC=INITCALL EPA=03A36DE8 R1=00058660 R14=83A36E74 STACK=00058608 CALL FROM $FUNC=BC1PSM10 EPA=03A36A08 R1=00057658 R14=83A36B3E STACK=000575F8 CALL FROM PROGM=BC1PSM10 ASM DT=08/20/01 VERS=0002 EPA=83A36998 RET=83A369FC IEA995I SYMPTOM DUMP OUTPUT USER COMPLETION CODE=3009 TIME=09.47.22 SEQ=55966 CPU=0000 ASID=01B9 PSW AT TIME OF ERROR 078D1000 80051EAO ILC 2 INTC OD ACTIVE LOAD MODULE=BSTPMOPS ADDRESS=0004E538 OFFSET=00003968 DATA AT PSW 00051E9A - 00181610 0A0D47FO C3001812 GPR 0-3 80000000 80000BC1 00000BC1 D4C1C3D9 ***
The call trace displays the modules and subfunctions at the point of ABEND. The fields in bold type vary with each trace, and are explained as follows:
  • BC1PSM10 
    Identifies the module that produced the abend.
    Identifies the abend code.
  • NUMBER=3009
    Identifies the user abend number associated with the abend.