Previous Topic: Execute the Load Module MAKE FileNext Topic: Loading the Scripts


Install the Load Module

When installing the application in the IEFAE environment, the Application Execution Environment (AEENV) file, called the tranmap file, contains the transaction codes, called trancodes, that allow the IEFAE and the Application Test Facility to identify each load module in the target configuration. These transaction codes allow access to any load module installed in that target configuration.

The Installation Tool automatically updates the tranmap file with the transaction codes for the load modules installed, making the application immediately accessible through the IEFAE.

When installing the executable in the IEFAE environment, additional command files are built that allow access to the application using any clear screen trancode. CA Gen runtime DLLs must also be made available to the IEFAE environment where the application is being tested.

The tranmap (AEENV) file is not created if the load module is to be installed in CICS or IMS.

When installing the application in the CICS environment, you must define all program names and trancodes to CICS by updating the CICS program and table definitions. When installing the application in the IMS environment, you must define all program names and trancodes to IMS using the IMS TRANSACT and APPLCTN macros.

Note: For sample table definitions for CA Gen-generated applications and information about the runtimes required to execute the application in CICS or IMS, see the z/OS Installation Guide.

In the z/OS environment, the load module that results from the final link-edit is stored in the EXE loadlib location. When installing a load module, CA Gen copies it from the EXE loadlib location to the implementation load library location, that is Impl loadlib. Ensure that the EXE and Impl loadlibs are created as PDSE (DSNtype=library) data sets. You can specify the EXE loadlibs and Impl loadlibs during target configuration construction at the target, model, and business system levels. At least one of these loadlibs is required. The search order is business system, model, and last target level.

More information:

Testing, Production, and Maintenance