Build scripts
- A build script written in pseudo-JCL transforms a COBOL source file into an object file, and in some cases the build script transforms one or more object files into a load module. This build script is used by the z/OS® build server.
- A Java™ compiler or other .exe (binary) file or a .bat (text) file is available to a build server on the development system or is sent to a build server on a remote Windows™ 2000/NT/XP.
- A script (.scr file) or some binary code is sent to a USS build server.
You can specify the address of a remote build server by setting the destHost build descriptor option.
COBOL build script for iSeries®
The build script for iSeries® is a REXX™ program named FDAPREP and is described in the IBM® Rational® Business Developer EGL Server Guide for IBM® i, which is available in the help system.
COBOL build scripts for z/OS®
When generating COBOL for a z/OS® environment, you can use build scripts to start the z/OS® COBOL compiler and the z/OS® linker. If a generated program is targeted for a CICS® environment, you can use a build script that calls the CICS® translator as well. If the generated program contains SQL, the build script starts the DB2® preprocessor and starts a DB2® database bind.
The z/OS® build scripts that allow you to perform all these tasks are shipped with the z/OS® build component and are installed in the z/OS® build server's pseudo-JCL PROCLIB library.
You need to customize these scripts for your working environment. For details, see Modifying EGL build scripts for z/OS.
Java™ build script
To prepare Java™ code for execution, EGL puts the javac (Java™ compiler) command and its parameters in the build plan. The build plan then sends the javac command to the build server, along with the input required by the command.