ELAXF* remote build procedures
Developer for z/OS® provides sample JCL procedures that can be used for the JCL generation, remote project builds, and remote syntax check features of CICS® BMS maps, IMS MFS screens, Assembler, C/C++, COBOL and PL/I programs. These procedures allow installations to apply their own standards, and ensure that developers use the same procedures with the same compiler options and compiler levels.
The sample procedures and their function are listed in Table 1.
| Member | Purpose |
|---|---|
| ELAXF | Include member that specifies variables used by the remote build procedures. |
| ELAXFADT | Sample procedure for assembling and debugging High Level assembler programs. |
| ELAXFASM | Sample procedure for assembling High Level assembler programs. |
| ELAXFBMS | Sample procedure for creating CICS BMS object and corresponding copy, dsect, or include member. (3) |
| ELAXFCOC | Sample procedure for COBOL compiling and doing Integrated CICS translate and integrated Db2® translate. (1) |
| ELAXFCOP | Sample procedure for Db2 preprocessing of EXEC SQL statements embedded in COBOL programs. |
| ELAXFCOT | Sample procedure for CICS translation for EXEC CICS statements embedded in COBOL programs. |
| ELAXFCPC | Sample procedure for C compiling. |
| ELAXFCPP | Sample procedure for C++ compiling. |
| ELAXFCP1 | Sample procedure for COBOL compiling with SCM preprocessor statements (-INC and ++INCLUDE). (1) |
| ELAXFDCL | Sample procedure for running a program in TSO mode. |
| ELAXFGO | Sample procedure for the GO step. |
| ELAXFLNK | Sample procedure for linking C/C++, COBOL, PL/I, and High Level Assembler programs. (1) (3) |
| ELAXFMFS | Sample procedure for creating IMS MFS screens. |
| ELAXFPLP | Sample procedure for Db2 preprocessing of EXEC SQL statements embedded in PLI programs. |
| ELAXFPLT | Sample procedure for doing CICS translation of EXEC CICS statements embedded in PLI programs. |
| ELAXFPL1 | Sample procedure for PL/I compiling, and integrated CICS translation and integrated Db2 translation. (1) |
| ELAXFPP1 | Sample procedure for PL/I compiling with SCM preprocessor statements (-INC and ++INCLUDE). (1) |
| ELAXFSP | Sample procedure to register a stored procedure to Db2. (2) |
| ELAXFSQL | Sample procedure to invoke SQL. (2) |
| ELAXFTSO | Sample procedure for running and debugging the generated Db2 code in TSO mode. |
| ELAXFUOP | Sample procedure for generating the UOPT step when building programs that run in CICS or IMS subsystems. |
All remote build procedures rely on the ELAXF include member for
the definition of common high-level qualifiers. Customize the sample include member,
FEL.#CUST.PROCLIB(ELAXF) as described within the member. You can use Table 2
and Table 3 to assist with this
customization.
FEL#CUST.PROCLIB(ELAXF*), and customize them if required. Some sample
ELAXF* procedures in Table 1 are marked with a footnote as
they are more likely to require customization:- These remote build procedures have commented out references to CICS and Db2 load libraries.
- These remote build procedures have a reference to a customized input file with SQL commands.
- These remote build procedures have miscellaneous customizable options.
The names of the procedures and the names of the steps in the procedures match the default properties that are included with the Developer for z/OS client. If the name of a procedure or the name of a step in a procedure is changed, the corresponding properties file on all of the clients must be updated. You should not change the procedure and step names.
| Product | Default HLQ | Value |
|---|---|---|
| Developer for z/OS | FEL | |
| Debugger | EQAW | |
| ADFz Common Components | IPV | |
| COBOL | IGY.V6R2M0 | |
| PL/I | PLI.V5R2M0 | |
| C/C++ | CBC | |
| LE | CEE | |
| XML Toolkit | SYS1 | |
| CICS | CICSTS54.CICS | |
| Db2 | DSNA12 | |
| IMS (site specific libraries) | IMS | |
| system LINKLIB | SYS1 | |
| system MACLIB | SYS1 | |
| system CSSLIB | SYS1 |
ELAXF* procedures reference data
set names that do not have fixed low-level qualifiers. An example
is the Db2 runtime library,
which holds Db2 utilities that
are compiled by your Db2 administrator.
Use Table 3 to map the default
data set names to the names used at your site.
| Product | Default DSN | Value |
|---|---|---|
| Developer for z/OS - SQL samples | FEL.#CUST.SQL |
|
| Db2 runtime libraries | DSNA12.RUNLIB.LOAD |
Once the ELAXF* members are customized, copy them to
SYS1.PROCLIB. Ensure that the ELAXF include member remains with
the ELAXF* build procedures. If the members cannot be copied into a system
procedure library, ask the Developer for z/OS users to add a
JCLLIB card (right after the JOB card) to the job properties on the client.
//MYJOB JOB <job parameters>
//PROCS JCLLIB ORDER=(FEL.#CUST.PROCLIB)