These build scripts are developed using pseudo-JCL, a form of JCL with some restrictions and a few extensions, as described in Pseudo-JCL syntax.
The build server reads the pseudo-JCL and processes it to invoke the build program against the data sets specified in the program. Because the build scripts reference data sets that contain the location of the DB2 preprocessor, the CICS translator, the COBOL compiler, and the z/OS linkage editor, you need to modify the shipped build scripts to at least specify the actual locations of these code-preparation components.
The following examples show common modifications that you can make to EGL build scripts.
It is likely that the PDS naming conventions for the compiler, linkage editor, and database libraries are not the same as those used in the EGL build scripts. To change the default values, you must modify the VARS statement in the EGL build scripts. The following example shows the VARS statement for the default CICS and COBOL compiler libraries:
//DEFAULTS VARS EZEPID=USER,
// COBCICS=SYS1.SCEECICS,
// COBCOMP=SYS1.IGY.SIGYCOMP,
// COBLIB=SYS1.SCEELKED,
...
To change the high level qualifier for these libraries to MYSYS, you would use the following syntax to change the VARS statement:
//DEFAULTS VARS EZEPID=USER,
// COBCICS=MYSYS.SCEECICS,
// COBCOMP=MYSYS.IGY.SIGYCOMP,
// COBLIB=MYSYS.SCEELKED,
...
Alternatively, you can leave the values of COBCICS, COBCOMP, and COBLIB set to the defaults in the build scripts and set the corresponding predefined symbolic parameters COBCICS, COBCOMP, and COBLIB in the EGL build descriptor parts to the values you need.
You can make similar updates for the EGL libraries (ELA substitution variable) and the database libraries (DSNEXIT and DSNLOAD substitution variables) either in the build scripts or by setting the corresponding predefined symbolic parameters in the EGL build descriptor parts.
//*UPLOAD EXEC PGM=IEFBR14
//*EZESRC DD DSN=&EZEPID..&SYSTEM..EZESRC,DISP=SHR,CCUEXT=CBL
//UPLOAD EXEC PGM=IEFBR14
//EZESRC DD DSN=&EZEPID..&SYSTEM..EZESRC,DISP=SHR,CCUEXT=CBL
In EGL build scripts, certain preparation options are required if you are using DB2 UDB, the CICS translator, or the COBOL compiler for z/OS.
The DBCS option is required for the CICS translator when DBCHAR or MBCHAR variables or literals are used. The build scripts automatically include this option based on the setting of the predefined symbolic parameter EZEDBCS, which in turn is set based on the use of DBCHAR or MBCHAR
Also, the DBCS option is required for the COBOL compiler when DBCHAR or MBCHAR variables or literals are used. The build scripts automatically include this option based on the setting of the predefined symbolic parameter EZEDBCS, which in turn is set based on the use of DBCHAR or MBCHAR.
EGL requires the NODYNAM compiler option so that all CALL LITERAL statements are treated as static calls.
Produces an assembler language expansion of the COBOL source code.
Produces a listing of information from the COBOL DATA DIVISION, including a DATA DIVISION map, global tables, literal pools, nested program structure map, and program attributes.
Produces a cross-reference listing of the hexadecimal offsets in the module and the corresponding COBOL statement number. This is recommended to help you while you are debugging your program in the runtime environment.
Provides runtime subscript checking. NOSSRANGE eliminates runtime subscript checking. Because using NOSSRANGE can result in better performance, specify NOSSRANGE when you move the program to production.
Produces object code that enables Debug Tool to perform batch and interactive debugging in your runtime environment.
For details on COBOL compiler options, refer to your compiler documentation.
The COBOL compiler option NAME is not supported.