After designing your applications, you must generate the
corresponding COBOL code.
The steps to generate the COBOL of a Program, Screen, or Server
You can generate a Program, Screen, or Server either in Pacbase or in Rational Programming
Patterns (local generation). If you generate in Pacbase, you obtain a complete
generated code. This code includes both the code produced by the generation
of the design, and the code produced by the generation of the specific
insertions. You must run the migration help function to migrate this
complete code to your local workspace. After the migration, the complete
source is available in your local workspace. The PDP COBOL editor clearly
differentiates the specific code from the generated code.
The generation target of a Program, Screen, Server, or Database Block
By default, the generated files are stored with the design
files in a folder whose default name can be changed. However, you
can separate them from the design files inside the generation project,
or even change the generation project and folder.
Starting the various generation types
You can generate the batch and online error messages, the Copybooks
that are related to a selected Data Structure, and the Pacbase generatable entities.
Generation command lines
With these command lines, you can generate a Program, Screen,
or Server, the error messages, Database Blocks, and Copybooks.
Managing non-IBM COBOL code
You can manage the non-IBM COBOL codes from the authorized
types of COBOL codes listed on this page. You can use the authorized
types of Database Blocks also listed on this page. There are two other
differences between the IBM and non-IBM COBOL codes: the syntax check
and the build script.