Skip to Content

AD (N) – Names

This option is used to enter the physical dataset names associated with the Application Level and Component Type.

Names Screen

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

Names Screen

image2021-1-29_17-9-51.png

VSAM Considerations

The following figure shows the External Names used for KSDS storage Types, which are defined in the M.AD Table for the Applications that use them. The definition of a KSDS name can include the symbolic variable <MEMBER>, which will be replaced with the ISPW Component Name at run time.

Warning

Important

Library type must be KSDS.

If the KSDS datasets are to be deployed, the target names will be defined in the M.DV tables. Refer to the ISPW Deploy Reference for information on how this should be defined.

VSAM Considerations

image2021-1-29_17-11-41.png

Field Descriptions

The following table describes each field for a Name:

Field Descriptions

Field Name

Description

Type

A valid Component Type as defined in option CT.

Class

This further classifies a generated component type. It can be used to specify different dataset names for the same component type, dependent upon the value specified for the Target Environment (in conjunction with the Associations definitions).

Level

The name of the level.

Storage Type

The type of dataset for this Component Type.

Valid values:

  • PDS – A standard TSO partitioned dataset
  • HFS – Hierarchical File System files
  • KSDS – VSAM Keyed Sequential Dataset. For when a component is used to represent the whole KSDS.

An “*” to the left of this field indicates that the Primary Storage for this type is in the ISPW Warehouse (defined in M.ST). If a Dataset Name is specified, ISPW will keep a copy of the component externally in that dataset.

Library Name

The dataset for this level must be a fully qualified dataset name with no quotes.

Encoding

Defines the Encoding used for the Storage if encoding other than the default is required at this level.

Valid Values:

  • A – ASCII
  • E – EBCDIC
  • U – Unicode
  • blank – default for type and platform.

The default value is determined by the attribute Content Type specified in M.CT and the system type of the server. Example usage would be if HTML needed to be stored in ASCII even though it is being stored in HFS files on USS. In this case, a value of “A” would be required.

Server

Defines the Server where the Storage is located.

Valid Values:

  • Server Name – must be defined in the M.SV table
  • Blank – used to identify the central MVS server
  • WORKSTN – used to identify a Workstation Level.

Type

A valid Component Type as defined in option CT.

Class

This further classifies a generated component type. It can be used to specify different dataset names for the same component type, dependent upon the value specified for the Target Environment (in conjunction with the Associations definitions).

Level

The name of the level.

Storage Type

The type of dataset for this Component Type.

Valid values:

  • PDS – A standard TSO partitioned dataset
  • HFS – Hierarchical File System files
  • KSDS – VSAM Keyed Sequential Dataset. For when a component is used to represent the whole KSDS.

An “*” to the left of this field indicates that the Primary Storage for this type is in the ISPW Warehouse (defined in M.ST). If a Dataset Name is specified, ISPW will keep a copy of the component externally in that dataset.

 

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

BMC Compuware ISPW 18.02