Previous Topic: Target DefinitionNext Topic: Duplicate a Target


Add a Target

Follow these steps:

  1. With the IT window displayed, select Option 1. The Installation Tool window is displayed.
  2. Select Option 3, Maintain Configuration Information. The Select Script List screen is displayed.

    Note: The Select Script screen is automatically displayed when a target configuration does not exist. After a target is configured, the Select Script screen is replaced with the Selection List screen.

  3. Select the script that you want to associate with the target configuration and press Enter. The Target Definition screen is displayed.
  4. Tab to the Target field. Type a logical name for the target configuration you are defining.
  5. Tab to the Desc field. This information field is used to further define the logical name specific in the Target field (Step 4).
  6. For DB2 scripts, tab to the DB2Sys field and type the DB2 subsystem ID. This is used during DDL installation and DB2 bind steps.
  7. For DB2 scripts, tab to the Target Test Facility field. Select YES or NO. Selecting YES causes all applications installed into this environment to be installed under the Application Test Facility.
  8. Press Enter to add the Target. The system responds with the message:
    Processing has completed normally
    
  9. Press F5 to display the Specify Locations screen. This screen is used to specify target level data sets for the different components of the target environment. For a description of locations, usage, and data set attributes, use the following table.

Contents of File

Usage

Data Set Attributes

source Lib

Contains generated source split from Implementation Packages (IPs).

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Ncal Load Lib*

Contains unresolved load modules output from compile process.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

Exe Load Lib*

Contains fully resolved executable load modules.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

Impl Load Lib*

Contains implemented load modules; the install step copies modules from the exe loadlib to the Impl loadlib.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

DBRM Lib

Contains DBRMs created by the DB2 pre-compiler.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Inst Ctl Lib

Contains load module ICMs split from IPs.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Listing Lib

Contains compiler listings (optional).

PO, RECFM=FBA, LRECL=133, BLKSIZE=13300

Clist Lib

Contains generated MAKE procedures.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Tranmap File

The IEFAE file that associates trancodes to load modules.

PS, RECFM=FB, LRECL=80, BLKSIZE=27920

Appl Clist Lib

Contains generated commands to invoke an application under IEFAE (one command for each clear screen trancode).

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

MFS Source Lib

Contains generated MFS code split from IPs.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Bndctl Lib

Contains binder control cards information. It is a copy of SYSLIN DD used during linkedit.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Batch JCL Lib

Reserved.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Idcams Ctl Lib

Contains IDCAMS control statements split from DDL IPs.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

DDL Lib

Contains DDL statements split from DDL IPs.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

RI Source Lib

Contains source code for RI triggers split from RI trigger IPs.

PO, RECFM=FB, LRECL=80,
BLKSIZE-27920

RI Load Lib*

Contains NCAL load modules created by compiling RI triggers.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

RI DBRM Lib

Contains DBRMs for RI triggers.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

RI Listing Lib

Contains compiler listings for RI trigger modules.

PO, RECFM=FBA, LRECL=133, BLKSIZE=13300

RI Exec Lib*

Contains executable RI load modules for fully resolved RI load modules.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

RI Bndctl Lib

Contains binder control cards information for RI Triggers.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Batch Exec Lib*

Contains executable Batch load modules for fully resolved dynamic and/or zLib load modules.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

Batch Bndctl

Contains binder control cards information for dynamic and zlib modules linked for batch processing.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Batch RI Lib*

Contains executable Batch Dynamic RI Trigger load module.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

Batch RI Bctl

Contains binder control cards information for dynamic RI Trigger modules linked for batch processing.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Ext Ab Libs*

The maximum of 12 load libraries containing external action blocks.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

Ext DBRM Libs

The maximum of 12 DBRM libraries containing external action block DBRMs.

PO, RECFM=FB, LRECL=80, BLKSIZE=27920

Sys Load Libs*

The maximum of 12 load libraries containing site-specific load modules that are linked into CA Gen application load modules (for example, site version of the help exit).

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

Static NCAL Lib*

Contains the unresolved load modules (that is, output from compile step) created for the Action Blocks statically linked into Compatibility modules.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

Static LIST Lib

Contains compiler listings (optional) created for Action Blocks statically linked into Compatibility modules.

PO, RECFM=FBA, LRECL=133, BLKSIZE=13300

Static RI NCAL*

Contains NCAL load modules created by compiling RI triggers with the NODLL option so that the triggers can be used by Compatibility modules.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

Static RI LIST

Contains compiler listings for RI trigger modules created for the NODLL compile.

PO, RECFM=FBA, LRECL=133, BLKSIZE=13300

Static Ext Ab*

The maximum of 12 load libraries containing external action blocks created by compiling with the NODLL option so that they can be used by Compatibility modules.

PO, RECFM=U, LRECL=0, BLKSIZE=19069, DSNTYPE=LIBRARY

* Data set must be created as a PDSE (DSNtype=library) data set.

Note: A data set name can be up to 44 characters long. Quotes are required. Data set name validation is not performed. All data sets must be created outside the Installation Tool. Data set names can be deleted or changed by overwriting the existing values.

  1. Press Enter to process the changes. The system responds with the following message:
    Location updates were successful.
    
  2. Press F3 to display the Installation Tool window.