Endevor's guidelines for setting diagnostic DD names.

Products

• Endevor

Issue/Introduction

When an issue is under investigation, in order to get some extra information, Broadcom Support may request to have some DDs statements added to the job, such as: 

 

//BSTERR DD SYSOUT=*

//EN$TROPT DD SYSOUT=*    (Endevor Options Trace)

//EN$PPRT    DD SYSOUT=*    (Print Endevor Processor) 

//EN$TRAUI DD SYSOUT=*      (Endevor ALTID Trace) 

//EN$TRESI DD SYSOUT=*      (Endevor ESI Trace)  

Environment

All supported Releases 

Resolution

To have the DDs statements added, please follow the procedure below:

1) Rerun the job with the following DDs statements.
Please note, the following DD statements need to be added to the 'outer' JCL, in the program that runs the jobstep.
Very often it is EXEC PGM=NDVRC1, but others are also possible, BSTXCOPY for example.

//BSTERR   DD SYSOUT=*
//EN$TROPT DD SYSOUT=*
//EN$PPRT  DD SYSOUT=*
//EN$TRAUI DD SYSOUT=*

In case submitting the job via Endevor panels (no JCL to update), do the following:
- Reproduce the actions. BEFORE submitting the JCL, add TYPRUN=COPY to the 'Job Statement Information' field. (Doing so the job is not executed but copied to the output queue instead) 


- Submit the job.
- Go to the output management tool (SDSF / SYSVIEW) and check for the job submitted.
- Do a SJ next to it, and it will open the JCL to be edited. This time EXEC PGM=NDVRC1 should be there.
- Add the required DDs inside EXEC PGM=NDVRC1, for example:



- Remove TYPRUN=COPY
- Submit the job.

2) Send the complete output (with all the instances - JESMSGLG, JESJCL, JESYMSG, LOG) for review.
Use the following Article 224412 - JCL sample to TERSE & UPLOAD files to Broadcom support case for reference.

3) Once the tests are done, remember to remove TYPRUN=COPY from the 'Job Statement Information' field. 

Additional Information

For more information, please refer to Endevor Trace Facilities.