When running an Endevor processor, the processor is not listed out and none of symbolic substitutions are listed in the execution report.
Is there a way to get a listing of the processor and see how the symbolics are getting resolved in the processor execution output?
All supported versions of Endevor
The reason that the processor and symbolic substitution message are not included in the processor execution output is the ENCOPTBL option - ENHOPT NO_PROC_PRINT , has been turned on.
***********************************************************************
* BYPASS THE JCL DISPLAY OF THE PROCESSOR EXECUTED DURING ACTIONS
* AND/OR BYPASS PRINTING C1G0007I AND/OR C1G0009I MESSAGES
* EXPLANATION :
* IF YOU WANT TO SUPPRESS THE PROCESSOR LISTING USE (ON,1) O0000324
* IF YOU WANT TO SUPPRESS MSGS C1G0007I USE (ON,2) O0001746
* IF YOU WANT TO SUPPRESS MSGS C1G0009I USE (ON,4) O0001746
* IF YOU WANT TO SUPPRESS A COMBINATION OF MSGS USE (ON,N), WHERE N
* EQUALS THE SUM OF THE PREVIOUSLY PROPOSED VALUES.
* EG : USE (ON,7) TO SUPPRESS ALL THESE MESSAGES.
*
* WHEN THIS OPTION IS ENABLED, YOU CAN TEMPORARILY OVERRIDE IT
* USING THE FOLLOWING DDNAME IN YOUR ENDEVOR JOB STREAM:
* //EN$PPRT DD DUMMY
*
*---------------------------------------------------------------------*
ENHOPT NO_PROC_PRINT=(ON,7)
C1G0007I and C1G0009I are the symbolic informational messages:
C1G0007I SYMBOLIC ADBSLIB DEFINED BY PROCESSOR:
C1G0007I SYMBOLIC CICSLIB DEFINED BY PROCESSOR:
C1G0009I ORIGINAL : &C1SI
C1G0009I SUBSTITUTED : T
Have ddname EN$PPRT allocated during Endevor initialization to override the NO_PROC_PRINT option
//EN$PPRT DD DUMMY * Ignore NO_PROC_PRINT
Note that the processor statements print only the very first time the processor is executed (when it is loaded). Subsequent executions of the processor will print only the symbolic substitution messages. This is something to bear in mind when several actions are performed in the same run.
Because of this, obtaining the processor statements may be problematic for Web Services clients. They will not print in the C1MSGS1 output returned to the client if the task that executes the action has loaded the processor in an earlier action for another client.
To override this limitation, you may want to temporarily disable STC pooling in the Web Services datasource definition. This way, each request from a client will start a new STC which will for sure need to load the processor so it will print in C1MSGS1.