Generating the applications
After designing your applications, you must generate the corresponding COBOL code. The generation manager gives a global view of the generated files that are desynchronized with the design. You must use it to start a multiple or a global regeneration of the desynchronized files.
- Generation upgrade
The generation has been enhanced in Rational® Programming Patterns 9.6.1 for Programs, Screens, Servers, Folders, and Communication Monitors. The generated files must then be modified to integrate the new enhancements. - 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). In this context, a Server can also be a Communication Monitor or a Folder. 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
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 COBOL code, proxies, textual or COBOL descriptions according to the entities. - The Generation Manager
The generation manager lists all the instances that must be generated again in the location. A pdp file must exist for all of them. The generation manager indicates all the files whose code is desynchronized with the design of the instance itself or of an instance that is involved in its generation. You must use it to request a multiple or global regeneration of the desynchronized files in the local workspace. To limit the number of the required regenerations, you can force the resynchronization between the design and the generated code for non-functional design modifications. - Managing non-IBM COBOL code
You can manage the non-IBM COBOL code that is generated from the supported types of COBOL codes. These types of COBOL codes are listed in the help on the Definition tab of Programs, Screens, Servers, Database Blocks, and Copybooks. The non-IBM COBOL code differs from the IBM COBOL code by the syntax check and the build script.
Feedback