EGL Reference Guide for iSeries

Predefined symbolic parameters for EGL generation

All of the EGL generator's symbolic parameters, whether predefined or user-defined, are passed as environment variables to the build server when you build a generated COBOL program. Environment variables passed to the build server supply values for build script substitution variables of the same name. The environment variable values override any default values defined for the substitution variables.

The next table shows the predefined symbolic parameters.


Name Description
BUILD_SCRIPT_LIBRARY Allows overriding the name of the PDS from which the build server reads the build scripts.

This symbolic parameter is useful when exception build processing is needed. For example, you can use a separate build script PDS if a special test system is needed with a separate database, COBOL libraries, or CICS libraries. The build scripts could have different default substitution variables or different compile options.

An alternative approach is to start a build server on a different port and to allocate a different build script PDS.

DATA A flag that specifies whether you want to allocate working storage with 24- or 31- bit addresses. The value supplied for this symbolic parameter is passed in the DATA parameter for the COBOL compiler and the z/OS linkage editor. The parameter's value is taken from the build descriptor option data.
EZEALIAS The member name used to store the currently generated member in its associated PDS. If an alias property was specified for the currently generated member, the value of that property, truncated to 8 characters if necessary, is used. If no alias property is specified, then the part name, truncated to 8 characters if necessary, is used. When a form group is the current member, and the form group has print forms included, the format module name is truncated to 6 characters rather than 8, and the characters FM are appended.
EZEGDATE The date on which a program is generated. The format is mm/dd/yy, where mm is the two-digit month, dd is the two-digit day of the month, and yy is the last two digits of the year.
EZEGMBR The name of the program part that was specified to start generation.
EZEMBR The name of the program that was generated. The value will be the same as the value of the MBR parameter unless you specified the alias property for the program generated, or the name of the generated program is longer than 8 characters.
EZEPID The high-level qualifier that is used for the PDSs that receive the generated and built outputs. The parameter's value is taken from the build descriptor option projectID.
EZESQL An indicator as to whether or not the generated part performs SQL I/O. "Y" indicates yes; "N" indicates no.
EZETIME The time at which a program is generated. The format is hh:mm:ss, where hh is the hour, mm is the minute, and ss is the seconds portion of the time.
EZEEXTNM The external name, if any, that is specified in the program part's alias property. This symbolic parameter is available only during generation of bind control and link edit files. It is not available when build scripts are being executed. If the external name is not specified, the name of the part is used but is truncated (if necessary) to the maximum number of characters allowed in the run-time environment.
MBR The external name given to the generated source code. The external name is the same as the EGL program name unless an alias property was specified for the program or the program name is longer than 8 characters. If the alias property was specified, its value is placed in the MBR environment variable. Otherwise, if the program name is longer than 8 characters, the program name is truncated to 8 characters and the result is placed in the MBR environment variable.
SYSTEM The target system for which the EGL program was generated; for example, ZOSCICS or ISERIESC. The parameter's value is taken from the build descriptor option system.

In addition to these predefined symbolic parameters, you can define your own symbolic parameters that are passed to the build server as environment variables. If the build script contains a substitution variable whose name matches the symbolic parameter name, the build server uses the value of the symbolic parameter in the build script, in place of the substitution variable.


Related concepts


Generation


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]