CT – Component Type Definition

Each component type and its attributes are defined. ISPW uses this information to determine how to process each different type of component.

Component Type Definition Screen

The following figure is a list of Component Types. It is the first screen displayed after entering option CT and selecting a version.

Component Type Definition Screen

General Notes

All values set under this option affect all occurrences of the component type across the organization. Some of the values may be overridden by Application Definitions values (option AD) or even negated using the keyword DUMMY. These values are:

Generate Skeleton
Generate Table
Generate Job
Test Generate Panel
Hold Generate Panel
Custom Generate Panel
Prod Move Job
Model.

This allows default values for a component type to be set and, in exceptional cases, to be overridden for an application.

Example

If one team needs a special compiler for its COBOL programs, the general skeleton can be identified in option CT and the override skeleton identified in that particular application’s AD entry.

Detail Screen

The following figure shows the Component Type details displayed when a specific Component Type is selected from the Component Type List screen.

Detail Screen

Field Descriptions

The following table describes each field for a Component Type definition:

Field Descriptions

Field Name	Description
Component Type	User-defined code for the type of component. Example: COB for COBOL programs.
Name Length	The maximum length for Component Names of this type. If Name Length is greater than 8 bytes, you must set ISPW Type to XNAM.
Description	A short description of the component type.
Technology	This field can be used to group together component types that use the same set of ISPW exits throughout the entire production cycle. Then one entry can be used in the exit table (M.EX) instead of one for each component type. Any values required by standard ISPW processing are identified for the Special Technologies in the ISPW Interfaces Guide.
ISPW Type	The particular ISPW component type, which is used to distinguish component types of the same technology. This allows the component types to be any name suited to the organization while still allowing ISPW to recognize the component type for its special processing considerations. Valid values: LIST - Generated listing types. Using the ISPW Type LIST will enable proper listing support in Topaz. Any values required by standard ISPW processing are identified for the Special Technologies in the ISPW Interfaces Guide.
Cycle Flag	Indicates whether the component type can move through the application levels or whether the component type exists only at the production level and is edited directly. Valid values: Y – types that cycle through application levels. N or blank – non-cycle types.
Base Component Type	This field is used by the Component Reference system to determine which Component Reference routine to use when scanning the task and is used as an input parameter in the Analysis option. This field must have a related value in the Base Component Type table. The valid values are recognized by the ISPW scan routines. Valid values: ASM – all Assembler Component Types. This type is translated internally into PROG. AMAC – all Assembler macros. CLST – all CLIST Component Types. COB – all COBOL Component Types. This type is translated internally into PROG. COPY – all COBOL Copy Component Types. INCL – all PL/I Include Types. JOB – all JCL Component Types (but not Procs). PANL – all ISPF Panels. PL1 – PL/I Component Types. This type is translated internally into PROG. PROC – all JCL Proc Component Types. SKEL – all ISPF Skel Component Types. blank – no component reference scanning. Other values may be used for your site’s custom scan routines. These values must exist in the Base Component Type table in the Base Component Type field. See Component-Reference and M.XR for more detailed information.
Generate Flag	Indicates whether the component type can be generated. Valid values: Y – generate types. N or blank – non-generate types.
Case Sensitive	Determines whether the Component Name can be mixed case or just upper case. Valid values: Y – Component Name can be mixed case. N – Component Name is upper case.
Content Type	Defines the encoding for the component type. Valid values: T – Platform Specific Text U – Unicode Text B – Binary.
Generate Skeleton	The name of the ISPF skeleton used to generate the component type. It should be blank if a generate is not required.
Test Generate Panel	The name of the panel displayed for generate processing in a TEST environment. If no TEST panel is required, this value can be set to 'DUMMY'.
Generate Table	The name of the table used to store processing information when a component is generated. When a HOLD generate is submitted from the user’s address space (as opposed to a generate requested via a set), generate information for the component is looked up from this table. Each generate table is referenced by one specific generate job in its SYSTSIN DD parm information. If no job submission is required for a generated component type, set this value to 'DUMMY'.
Hold Generate Panel	The name of the panel displayed to verify the processing options and job card information on a generate in a HOLD environment. If no job submission is required for a generate-able Component Type, this value can be set to 'DUMMY'.
Custom Generate Panel	The name of the dialog displayed by Topaz Workbench that contains the Generate parameters.
Generate Job	The name of the job that is executed for HOLD generates which are requested from a user’s address space (as opposed to a generate requested via a set). If no job submission is required for a generate-able component type, set this value to 'DUMMY'.
Move Job	This field is not used.
Librarian Language	This field is not used.
ISPW Exit Type	This field is not used.
Execution Environment	The execution environment of the component type. Valid values: REFR – a reference-only Component Type that is used only for other Component Type processing. It cannot be added to Assignments or Releases and will not appear in the Component Type lists in the special browse or Assignment/Release Task Add functions. I – used for TELON Component Types to indicate an IMS environment for TELON export utility processing. C – used for TELON Component Types to indicate a CICS environment for TELON export utility processing. B – used for TELON Component Types to indicate a Batch environment for TELON export utility processing.
Model	The skeleton or model which is copied into TEST for a brand new task. Must be a fully qualified dataset and member name, no quotes.
File Extension	The Extension to be appended to the Component Name for distributed and HFS files.