Specify Target Environment for HE › Construction Libraries in HE › Internal Libraries

Internal Libraries

The Internal Libraries store the objects that are created during system generation.

You are responsible for creating the internal libraries before CA Gen uses them. CA Gen does not create or allocate the libraries.

CA Gen requires that the internal libraries have certain characteristics. Some libraries are required, and some are required only when the application is installed locally.

The following list summarizes the Data Control Block (DCB) characteristics to specify when allocating each library, if the library is required, the recommended blocksizes (BLKSIZE) for IBM 3380 disk drives. All storage devices use PO organization (ORG) and logical record length (LRECL) of 80 unless otherwise noted. Record format (RECFM) is for all storage devices.

Generated source code - Required

RECFM: FB

BLKSIZE: 9440

NCAL load modules (see Note 3) - Required to install application locally

RECFM: U

BLKSIZE: 19069

Executable load modules (see Note 1) - Required to install application locally

RECFM: U

BLKSIZE: 19069

Executable batch dynamic action block library (see Note 1) – Optional to capture dynamic batch modules

RECFM: U

BLKSIZE: 19069

DB2 Database Request Modules (see Note 2) - Required to install application locally

RECFM: FB

BLKSIZE: 3120

Installation Control - Required

RECFM: FB

BLKSIZE:3120

Binder Control Cards - Optional

RECFM: FB

Batch Binder Control Cards - Optional

RECFM: FB

Generated MFS Source - Required to use MFS

RECFM: FB

BLKSIZE:3120

Generated batch JCL – Required to generate JCL

RECFM: FB

BLKSIZE:3120

Compile listings (see Note 3) -Optional

RECFM:FBA

LRECL: 133

BLKSIZE: 23408

Static non-DLL NCAL modules (see Note 3) - Required for Compatibility application that includes static Action Blocks installed locally

RECFM: U

BLKSIZE: 19069

Static non-DLL NCAL listings (see Note 3) – Optional, used only for Compatibility application that includes static Action Blocks installed locally

RECFM: FBA

LRECL: 133

BLKSIZE: 23408

Notes:

• The DCB characteristics for the internal load library is the same as those used to allocate the System Load Library that is defined when CA Gen is installed and the CA Gen Load Library in which CA Gen itself resides.
• The DCB characteristics for the internal DB2 DBRM Library is the same as those of the System DB2 DBRM Library that is defined when CA Gen is installed and the CA Gen DB2 DBRM Library in which CA Gen DB2 DBRMs reside.
• The Static non-DLL NCAL modules library is only used to store the NCAL modules that are produced by the NODLL compile (and ensuing NCAL link) of action blocks that are statically linked into Compatibility modules. In addition, these same action blocks are compiled with the DLL option so they can be used by DLL applications. The NCALs resulting from this DLL compile are stored in the NCAL load modules library. The compile listings are stored in the corresponding listings libraries, if a library is specified.

You are responsible for monitoring the space utilization of the data sets using the ISPF utility. If system generation terminates abnormally with a D37 or B37 system abend, it is likely that the data sets ran out of space or directory blocks.

The following panel shows CA Gen internal libraries that you can specify:

                            Specify Internal Libraries
Command ===>

Enter or verify the following business system library specifications:

 Generated source code . . .   'AAAC.TEST.COBOL'_____________________
 NCAL load modules . . . . .   'AAAC.TEST.NCAL'______________________
 Executable load modules . .   'AAAC.TEST.LOAD'______________________
 Exec batch dynam AB library   'AAAC.TEST.LOAD.BATCH'________________
 DB2 DBRM modules  . . . . .   'AAAC.TEST.DBRM'______________________
 Installation control  . . .   'AAAC.TEST.INSTCTL'___________________
 Binder control cards  . . .   'AAAC.TEST.BNDCTL'____________________
 Batch binder control cards    'AAAC.TEST.BNDCTL.BATCH'______________
 Generated MFS/DECforms  . .   'AAAC.TEST.MFSSRC'____________________
 Generated batch JCL . . . .   'AAAC.TEST.IDCAMS'____________________
 Compile listings  . . . . .   'AAAC.TEST.LISTING'___________________

You can also specify Static non-DLL NCAL modules and listings.

Generated Source Code Library

The Generated Source Code Library contains source members CA Gen creates during system generation. CA Gen generates source members for Dialog Managers, Batch Managers, Server Managers, screens, procedure steps, and action blocks.

NCAL Load Modules Library

The NCAL Load Library stores the compiled load modules that are created by CA Gen local install process, except for the modules that are produced by the NODLL compile of action blocks that are statically linked into Compatibility modules. The linkage editor creates these members using the NCAL (no-call option). Therefore, they contain unresolved external references and are not executable. The library member name is the component member name. The library member name for the Manager is the load module name.

Using this library allows you to specify a separate library for compiled NCAL load modules. This is useful when relinking the load module for execution in an IMS or CICS environment after testing in the CA Gen Test Facility (TS0).

Important! Do not give the NCAL Load Modules Library the same library name as the Static non-DLL NCAL Modules Library because these are mutually exclusive. Do not give the NCAL Load Modules Library the same library name as the Executable Load Modules Library. Keep the NCAL load modules separate from executable load modules to eliminate the need to regenerate the Manager after changing environment variables.

Executable Load Modules Library

The Install option in system generation is used to create an executable load module. All external references are resolved during installation. The executable load modules are stored in the Executable Load Modules Library. The member name is the load module name.

Executable Batch Dynamic Action Block Library

The batch versions of dynamic action blocks including the z/OS Library DLLs are stored in the Executable Batch Dynamic Action Block library if specified. The member name is the fully executable dynamic action block name or z/OS Library DLL name.

Important! Do not give the Executable Batch Dynamic Action Block Library the same library name as the Executable Load Modules Library.

DB2 DBRM Library

The DB2 DBRM Library stores the Database Request Modules that are generated by the DB2 precompiler. CA Gen generates a DB2 DBRM for each procedure step and action block in a load module that accesses a DB2 table.

Installation Control Library

The Install option automatically creates the installation control information for the load module and stores it in the Installation Control Library. The library member name is the load module name.

The Local Install option of system generation uses the control information to create an executable load module and to bind the DB2 Plan for DB2 targets, or the Remote Install option uses the control information to create a remote file.

Binder Control Cards Library

The Install option automatically creates the binder control cards information for the load module and for each of its components that are built as fully resolved executables in the Binder Control Cards Library. The library member name is the load module name, or the component name.

CA Gen generates the binder control cards information during local application installation. It is a copy of SYSLIN DD used during link edit.

Batch Binder Control Cards Library

This library contain the binder control cards for batch processing. If not specified, a temporary library is used.

Important! Do not give the Batch Binder Control Cards Library the same library name as the Binder Control Cards Library.

Generated MFS Source Library

If the application uses MFS, an MFS Source Library must be specified. This library contains MFS source members that are created during source code generation.

Generated Batch JCL Library

This library contains the generated JCL for the batch procedures.

Compile Listings Library

The Listings Library contains the listings that are created by the compiler for all but the NODLL compiled action blocks that are statically called by modules that are marked for Compatibility. Use of this library is optional, and is recommended.

The following illustration shows CA Gen internal compatibility libraries that you can specify:

                     Specify Internal Compatibility Libraries
COMMAND ===>

Enter or verify the following library specifications:
Static non-DLL NCAL modules  'AAAC.TEST.COMPAT.NCAL'_______________________
Static non-DLL NCAL listings 'AAAC.TEST.COMPAT.LISTING'____________________

Note: These libraries must be different from the corresponding libraries
specified on the Internal Libraries panel.

Static non-DLL NCAL Modules Library

The Static non-DLL NCAL Modules Library stores only the compiled load modules that are created by CA Gen local install process for modules that are produced by the NODLL compile of action blocks statically linked into Compatibility modules. The linkage editor creates these members using the NCAL (no-call option). Therefore, they contain unresolved external references and are not executable. The library member name is the static action block name.

Important! Do not give the Static non-DLL NCAL Modules Library the same name as the NCAL Load Modules Library or the Executable Load Modules Library.

Static non-DLL NCAL Listings Library

The Static non-DLL NCAL Listings Library contains only the listings that are created by the NODLL compile of action blocks statically linked into modules that are marked for Compatibility. Use of this library is optional, and is recommended.

More information:

System Generation and Installation