Determining the source of generated JCL
Developer for z/OSĀ® generates a symbolic parameter, FELJOB, at the top of generated JCL so that you can determine the context of the JCL and the action that caused the JCL to be generated. By examining this parameter, you can distinguish between, for example, JCL generated by a remote syntax check and JCL generated by a Compile/Link/Go request .
Querying the value of FELJOB
Developer for z/OS provides a sample REXX program named FELIF in the SFELPROC sample library. In the comments in the REXX member contain sample JCL that demonstrates how to make use of FELIF. Custom JCL based on this sample can be added to customized ELAXF* procedures to query the value of FELJOB.
For information about customizing JCL procedures, see Basic Customization.
Supported actions
SET FELJOB
statement:// SET FELJOB=CMP// SET FELJOB= |
Action |
|---|---|
| CMP |
|
| CMPLNK |
|
| CMPLNKGO |
|
| CMPLNKDB |
|
| CMPLNKCC |
|
| RMTCHECK |
|
| SHOWDPND |
|
Limitations
The following JCL generation and build actions are not supported and do not generate an
FELJOB SET statement. This list provides suggestions for working around these
limitations
- CARMA/Endevor Actions
- Manually update the default jobcard or the user-specific jobcard with a SET statement with a value such as ENVRBLD.
- DBB User Build
-
- Update the groovy build scripts to manually add a SET statement with a value such as DBBUBLD.
- Select different build scripts: one for ZUnit test cases and one for standard COBOL programs.
- EWM User Build
- Manually add a
SET FELJOB=EWMUBLDstatement to the JCL job card in the page, as in the following example: