G – Generate
This section provides information about Generate.
G – Definition
The G (Generate) command is used to submit a compile or generate. The module must be checked out (using the C operation), but does not need to be edited for generate to be valid. The example shown in the following figure is for program TSUBR20.
Using the G Command
Site-definable Generate Options Screen
The preceding figure (Using the G Command) shows the Generate Options input screen on the ISPW Demo/Training system. Each ISPW customer site will have its own version of this screen depending on its own compile, link, and bind parameters.
Sample Generate Parameters
Some sample Generate Parameters with their valid values are:
Value | Description |
|---|---|
Program | Y = Executable module N = Subroutine/non-executable module |
SQL used? | Y = Contains SQL N = No SQL |
Package used? | Y = Db2 Package for DBRM N = No Package used |
Do Binds? | Y = Compile/Link/Bind N = Compile/Link only B = Bind only |
Generate Outputs
The G (Generate) operation may create executable code. On the z/OS environment, these may be standard load modules or may be executables, such as MarkIV file definitions.
Generate Submits a Batch Job
The G operation typically submits a batch job, which may do a program compile/linkedit/bind, for example.
The G operation can, in fact, be very broadly defined to perform a “generate” process on any “generatable” type of component, as defined in ISPW’s repository.
Generate Concatenation
Libraries are concatenated for the compiles and links. In the ISPW Demo System, for example, ISPW concatenates DEV1 before STG1, then QA, then PRD. Concatenation is automatic, so ISPW users don’t need to know what libraries to include or which compile/link parameters to use.
Application Compile Defaults
Typically, an Application has a default profile for its compiles and links—such as COBOL for MVS—with certain compile/link parameters. Within ISPW, Applications are normally set up to use the default, except for the exception cases which are input to ISPW the first time a module is compiled and retained by ISPW thereafter.
Compile/Link Data is Persistent
From the first compile forward, the compile/linkedit/bind information is saved in ISPW’s repository so it does not need to be input again.
Generate Required at Least Once
Typically, executables are generated in the update environment and at least once more depending on the change cycle structure. Generates may be forced where intersecting change cycle paths come together, for instance, and may also happen automatically as part of the Promote process.
Status is IP (In Process)
The following figure shows the Task List as it appears when ISPW submits the compile. The Status column shows the Generate is In Process (IP) by KARYNS.
Status is IP
Op, User, and Date/Time are Updated
The last step of the Generate process updates the module’s statistics and clears the Status In Process flag. Users can instantly see if the Generate worked successfully.
The Status field displays any Generate errors. Use the J (Job Output) command to view the batch job results.