The construction libraries, which are PDS and PDSEs, store the objects that are created during system generation. The generated objects are the PDS and PDSE members.
You are responsible for selecting the libraries to be used during construction, identifying these libraries to CA Gen, and creating the libraries. CA Gen does not create or allocate the libraries. This must be done outside CA Gen, before the libraries are used.
The construction libraries are allocated with SHR disposition but enqueues are performed to prevent corruption of the PDS and PDSE. Use a unique library for each type of CA Gen generated output. That is, use different libraries for the generated source, JCL, load modules, and so forth.
No construction libraries are needed for database generation because no permanent data sets are created by database generation. Database generation creates the JCL and the DDL used to define a model's DB2 databases, and the IDCAMS data set allocation statements that define the VSAM data set allocation for the DB2 database (table spaces and index spaces). This information is stored in a temporary sequential data set that can be saved.
CA Gen uses construction libraries that are specified for a business system, System Load Libraries, and CA Gen Libraries. The System Load Libraries and CA Gen Libraries are defined during the CA Gen installation. You cannot modify them through the CA Gen Construction Library panels.
The System Load Libraries are external product libraries to run CA Gen-generated applications. For example, the system load libraries typically contain the runtime components for products such as COBOL, PL/I, DB2, IMS, CICS, and TSO.
CA Gen Libraries are the libraries in which CA Gen itself resides. They include one load library and one DB2 DBRM library.
There are two categories of construction libraries - internal and external libraries.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|