If you set the genRunFile build descriptor option to YES for z/OS® batch and IMS™ BMP environments, EGL creates sample runtime JCL for running the program. The file name is alias.jcx, where alias is set by the alias property for the program, and is truncated to 8 characters; or if the alias property is not specified, it is the program name, truncated to 8 characters. You can tailor the sample runtime JCL after it is transferred to the z/OS host. Alternatively, before you generate the output code, you can customize the templates that EGL uses to provide the basic pattern for the sample runtime JCL as described in Modifying the runtime JCL templates for z/OS.
Environ- |
Program | SQL | DL/I | Calls CICS® EXCI? | Template | Procedure called by template |
|---|---|---|---|---|---|---|
| z/OS batch | Main | Yes | Yes | n/a | fda2mebb | DLIBATCH |
| z/OS batch | Main | No | Yes | n/a | fda2mebc | DLIBATCH |
| z/OS batch | Main | Yes | No | No | fda2mebd | |
| z/OS batch | Main | Yes | No | Yes | fda2mesx | |
| z/OS batch | Main | No | No | No | fda2mebe | |
| z/OS batch | Main | No | No | Yes | fda2mebx | |
| z/OS batch | Called | The use of the template is not affected by SQL or DL/I usage. | * | * | fda2meba |
Each of the JCL templates contains a ?DD? line that starts in column one. This line indicates where the generation function is to insert the DD statements for files and databases used by the program. Move this line within the JCL template to control where the DD statements are placed. If you remove the line that contains ?DD?, the DD statements are not included in the generated JCL.
An exception to the above is the fda2meba template. For called programs, libraries and services the fda2meba template only includes the DD statements. You can incorporate these DD statements into the sample runtime JCL of any main program that calls the generated program, or uses the library or service.
| Environment | Program | SQL | Template | Procedure called by template |
|---|---|---|---|---|
| IMS BMP | Main | Yes | fda2meia | IMSBATCH |
| IMS BMP | Main | No | fda2meib | IMSBATCH |
| IMS BMP | Called | * | fda2meba | |
Note: * The use of the template
is not affected by SQL usage.
|
||||
For called programs, libraries and services, the fda2meba template only includes the DD statements. You can incorporate these DD statements into the sample runtime JCL of any main program that calls the generated program or uses the library or service.
| Record type | Input or output | Associated file type | JCL template for z/OS batch |
|---|---|---|---|
| DL/I segment | Input or output | fda2mdli | |
| Indexed Relative Serial | Input | VSAM, VSAMRS | fda2mvsi |
| Indexed Relative Serial | Output | VSAM, VSAMRS | fda2mvso |
| Serial | Input | SEQ, SEQRS | fda2msdi |
| Serial | Output | SEQ, SEQRS | fda2msdo |
| Serial | Input | GSAM | fda2mgsi, fda2mims |
| Serial | Output | GSAM | fda2mgso, fda2mims |
The generated sample runtime JCL for a program must be modified to include DD statements for files referenced using the record-specific variable record-name.resourceAssociation or the converseVar.printerAssociation system variable, or for files and databases used by programs that are called or transferred-to from the initial program in the run unit.
The following table shows the templates that generate comments in the sample runtime JCL to indicate the place where DD statements can be included.
| Program function | JCL template for MVS batch or IMS BMP |
|---|---|
| Program uses sysVar.transferName or a variable name as the target program in a call, transfer to program, or transfer to transaction statement | fda2meza |
| Program uses a specific program name as the target program in a call, transfer to program, or transfer to transaction statement | fda2mcal |
| Program sets the record-specific variable record-name.resourceAssociation or the converseVar.printerAssociation system variable | fda2mezd |