Skip to Content

AD (A) – Associations

Associations are Component Types that have some relationship with another Component Type. There are four categories of Associated Component Types:

  • Control Information Types
  • Generated Types
  • Included Types
  • Related Types.

Associations Definition Screen

The following figure is a list of Associations. It is the screen displayed after entering option AD, selecting an application version, and typing A beside it.

Associations Definition Screen

image2021-1-29_17-35-22.png

Field Descriptions

The following table describes each field for an association:

Field Descriptions

Field Name

Description

Component Type

A valid Component Type as defined in M.CT.

Component Class

This field is not currently used for Source Types.

Association

A code indicating the type of association the “related” Component Type has to the “base” Component Type.

Valid values:

  • C – for Control Information types. These are modules containing control information required to process the base Component Type. Linkedit control cards fall into this category.
  • G – for Generated types. These are components which are created when the base Component Type is generated (compiled/linked, etc.). This association category includes load modules, Db2 DBRM modules, and any other source or load modules that are produced when the base Component Type is generated.
  • I – for Included types. These are Component Types which are input to the generation processing of the base Component Type. COPYLIBs, DCLGENs, and SYSLIBs fall into this association category.
  • R – for Related types. These are Component Types which are added to an Assignment automatically when the base Component Type is added. They have the same Task Name and Application as the base Component Type. Related Component Types are used as reminders. They can be deleted from the Assignment if not required. This association category may include documentation items.

Target Environment

Can be used to specify a different class of dataset. This is set in the Generate Process.

Set

Set codes further define the Associations.

Valid values for Association = C (Control information types):

  • LKED – defines Linkedit control card modules.

Valid values for Association = G (Generated types):

  • GMT1 – defines GMT1 source and load
  • GMT2 – defines GMT2 source and load
  • GMT3 – defines GMT3 source and load
  • LOAD – defines the generated load module.

Valid values for Association = I (Included types):

  • MAC – defines macro (COPYLIB, etc.) datasets to the compile/assemble step
  • DCL – defines DCLGEN input datasets to pre-compiler step
  • SYS – defines SYSLIB input datasets to the linkedit step.

Sequence

A sequence of 1 for a GMT will refer to a “source” type and a sequence of 2 will refer to a “load” type. This allows up to 6 extra (in addition to the LOAD) generated objects to be associated with a Component Type. See Exit-Processing for a description of how these can be used.

For Association “I” the sequence number will determine the order in which libraries will be concatenated for a generate.

Associated Application

The application of the association component.

Associated Component Type

The Component Type of the associated component. Must be a valid Type defined for this Application.

Associated Component Class

This classifies the Generated Component Type. It allows for the situation where different target datasets (for example, LOADs) can be defined which are dependent upon the Target Environment. In Associations Definition Screen, a different Load library is specified (Class of “CICS”) when the Target Environment is “C”.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Compuware ISPW 18.02