Component Type Terms

Identifying Components

Component versions are identified by the Application to which they belong and the Component Type that classifies them. While the Application code controls the physical processing environment including levels and datasets, the Component Type tells ISPW how to process this type of component (for example, Is it to be generated? What technology is it?).

Defining Component Types

Component Types are first defined globally to ISPW and then to the Applications which will use them.

Initial Component Types

When ISPW is installed, a standard set of Component Types is provided. This set is a sample of commonly used ones. For example, COB, ASM, and so forth can be easily expanded to provide support for different technologies within an organization. More Component Type examples are provided for the special technologies in the ISPW Interfaces Guide.

Relating Component Types to Applications

Each Application in ISPW has its own set of valid Component Types defined to it. Part of the definition includes the physical datasets associated with that Application-to-Component Type relationship. When a user wants to add a new component for an Application, they will only be able to choose Component Types that have been predefined for that Application.

Component Type Domain

Component Types can be grouped together into a Domain. This allows different Component Types to share the same dataset (for example, a load library), while still maintaining component name uniqueness within ISPW. An example might be that a site wants to maintain name uniqueness across COB, ASM, and FORT components but allow the same named components between ISPF Panels and Skeletons.

Component Type Class

It is possible to further define a Component Type by Class. The Class allows the same type to be used for different datasets within a single Application.

An example of this would be to have a single Component Type LOAD but have a class of CICS to define a CICS load library and a class of BTCH to define the batch one. Depending upon the generate parameters (for example, the target environment for a compile), ISPW would be able to determine which class of component type to use, and subsequently place the load module into the correct library.

Commonly Used Component Types

The following table shows a list of suggested values for commonly used Component Types. Other technology-specific values are documented in the ISPW Interfaces Guide.

Commonly Used Component Types

Component Type	Description
ASM	Assembler Source
AMAC	Assembler Macro
C	C Source
CLST	TSO CLIST
COB	COBOL Source
COPY	Copybooks
DOC	Documentation
FORT	Fortran Source
H	C Header
JCL	JCL
LIST	Program Listing
LOAD	Program Load
MAN	Manual
MSGS	ISPF Messages
PANL	ISPF Panels
PARM	PARMLIB member
PROC	JCL PROC
REXX	REXX exec
SKEL	ISPF Skeleton

Associated Component Types

Associations are Component Types that have some relationship with another base Component Type. They are defined to Source Component types (for example, COB or ASM) and are used by ISPW to understand and manage all of the parts of a Component.

The following table shows the four categories of associated Component Types.

Associated Component Types

Association	Description
Control Information	This association defines control information required to generate the source Component Type. Link-edit control cards fall into this category.
Generate	This association defines the types of components that are created when the source 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 source Component Type is generated.
Include	This association defines component types that are input to the generation processing of the source Component Type. Copylibs, DCLGENs, and SYSLIBs fall into this association category.
Related	This association defines Component Types which are added to an Assignment automatically when the source Component Type is added. They have the same Task Name and Application as the source Component Type. Related Module Types are used as reminders. They can be deleted from the Assignment if not required. This association category may include documentation items such as DOC (program documentation) Component Type.

Associations are defined as part of an Application Definition (option M.AD). See Reference-Data-Options for detailed information.