When a MAKE procedure is created as a part of remote file installation, the location tokens are replaced with the actual library name where CA Gen generated components are stored when a remote file is installed.
All Location tokens are populated from the data entered on the Location screen of the Installation Tool. Location tokens are identified by the prefix LOC or LIB. (Library tokens are a form of Location token.)
The following table describes Location tokens. Location tokens can occur at target, model, and business system levels. Set the values for these tokens using the Location Screens in the Installation Tool.
|
Token Name |
Description |
|---|---|
|
Source_lib |
The location of generated source split from remote files. |
|
Ncal_load_lib* |
The location of unresolved load modules (output from compilation step). |
|
Exe_load_lib* |
The location of executable load modules (fully resolved load modules). |
|
Impl_load_lib* |
The location of implemented load modules. The install step copies modules from the Exec loadlib to the Impl loadlib. |
|
DBRM_lib |
The location of DBRMs created by the DB2 compiler. |
|
Inst_ctl_lib |
The location of load module ICM split from remote files. |
|
Listing_lib |
The location of compiler listings (optional). |
|
Clist_lib |
The location of generated MAKE procedures. |
|
Tranmap_file |
The IEFAE file that associates trancodes to load modules. |
|
Appl_clist_lib |
The location of generated commands to invoke an application under IEFAE (one command for each clear screen trancode). |
|
MFS_source_lib |
The location of generated MFS code split from remote files. |
|
Bndctl_lib |
The location of the binder control cards (optional). |
|
Batch_JCL_lib |
This token is reserved for future use. |
|
Idcams_ctl_lib |
The location of IDCAMS control statements split from DDL remote files. |
|
DDL_lib |
The location of DDL statements split from DDL remote files. |
|
RI_source_lib |
The location of source code for RI triggers split from RI trigger remote files. |
|
RI_load_lib* |
The location of NCAL load modules created by compiling RI triggers. |
|
RI_DBRM_lib |
The location of DBRMs for RI triggers. |
|
RI_listing_lib |
The location of compiler listings for RI trigger modules (optional). |
|
RI_Exec_lib* |
The location of RI executable load modules. |
|
RI_Bndctl_lib |
The location of the RI Triggers binder control cards (optional). |
|
Batch_Exec_lib |
The location of the Batch executable dynamic and zlib load modules (optional). |
|
Batch_Bndctl |
The location of the Batch executable binder control cards (optional). |
|
Batch_RI_lib |
The location of the Batch executable dynamic RI Trigger load modules (optional). |
|
Batch_RI_Bctl |
The location of the Batch dynamic RI Triggers binder control cards (optional). |
|
Static_ncal_lib* |
The location of unresolved load modules (output from compilation step) for action blocks statically called by modules marked for Compatibility. |
|
Static_list_lib |
The location of compiler listings for action bocks statically called by modules marked for Compatibility (optional). |
|
Static_RI_ncal_lib* |
The location of NCAL load modules created for RI triggers compiled with the NODLL compiler option. |
|
Static_RI_list_lib |
The location of compiler listings for RI trigger modules compiled with the NODLL compiler option (optional). |
Note: * Data set must be created as a PDSE (DSNtype=library) data set.
Library tokens are an alternate token resolution structure available that concatenates all location occurrences into a search sequence. When the MAKE file executes, each location is searched in sequence until the component is located or the list is exhausted. This capability is limited to three components and is very useful for ensuring that common or system level components do not have to be copied into CA Gen specific locations before they are accessed.
Library tokens are identified by the prefix LIB. LIB tokens are used to support multiple External Action Block libraries, multiple External Action Block DBRM libraries, and multiple system load libraries. The following table describes Library tokens:
|
Token Name |
Description |
|---|---|
|
Ext_ab_libs* |
The location of load libraries containing External Action Blocks. There is a maximum of 12 libraries. |
|
Ext_DBRM_libs |
The location of DBRM libraries containing External Action Block DBRMs. There is a maximum of 12 libraries. |
|
Sys_load_libs* |
The location of load libraries containing site-specific load modules that are linked into CA Gen application load modules (site version of the help exit). There is a maximum of 12 libraries. |
|
Static_ext_ab_libs* |
The location of load libraries containing External Action Blocks that are statically called by modules marked for Compatibility. There is a maximum of 12 libraries. |
Note: * Data set must be created as a PDSE (DSNtype=library) data set.
Location tokens can be divided into four categories:
The default hierarchy logic in the Installation Tool searches for a location at the lowest (most specific) level first, then moves up one level at a time to more general levels until it finds a location specification. The search order for the directory hierarchy looks like this:
This search order is transparent when you are viewing a script. In some cases, it may be necessary to use a specific location rather than resolving a token through the location hierarchy.
For example, if CA Gen is looking for a location to replace the location token called SOURCE_LIB in the MAKE file it is creating, it searches through the three levels in the following manner until it finds a location specification:
When the first location specification is found, AAAC.IEF.COBOL, is used to replace the location token in the MAKE file being created. In the example, the location specification is at the Target level. Because the Installation Tool automatically searches through the location hierarchy until a location is found, you can define locations with generic location tokens rather than separate tokens for each level. In the script, you do not need to include all the possible token names under which a location can be stored.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|