Looking for step by step instructions to setup the Endevor trace in classic Endevor or Quickedit
All supported releases
1) Determine what traces you want to turn on. Refer to Endevor Trace Facilities for details on trace options. You may have been requested to turn on certain ones by your Broadcom support engineer.
2) Determine mode to execute trace …. Batch or Foreground.
For Batch:
Add Endevor Trace DDs to the JCL step that runs ( PGM=NDVRC1,PARM=’C1BM3000’)
//BSTERR DD SYSOUT=*
//EN$TRxxx DD SYSOUT=* <= Add any additional EN$TRxxx DD statements depending on the traces you want turned on
For Foreground:
Determine where you want the trace output to go and allocate DDs.
If you want your output to go to a dataset, allocate trace output file(s) for each of the traces you are activating - prior to getting into Endevor or Quickedit. Use the following attributes...
LRECL=133, BLKSIZE=1330, RECFM=FB and DSORG=PS
From the command line in ISPF issue command TSO ALLOC F(EN$TRxxx) DA('FILE.NAME') SHR for the file.name(s) you created for each type of trace
If you want your trace output to go to Jes output – Issue command TSO ALLOC FI(EN$TRxxx) SYSOUT(X) for each trace you are activating
Note: You can confirm the allocation by issuing the TSO ISRDDN command.
3) Go into classic Endevor or Quick Edit and perform the action(s) required to recreate the problem scenario. Exit Endevor application and review file(s).
Note: to stop foreground traces... TSO FREE DD(EN$TRxxx) <hit enter> do for each trace activated.
4) For Foreground – Find ddname EN$TRxxx among the JES2 outputs from your active TSO session.
For Batch – Job output in Jes will contain all the trace data.
5) Collect/view the full output. If attaching to a case; download as text format, CRLF option 133 length. Name output file with .TXT suffix.