Naming Conventions

Datasets

To ensure that each instance of the CA 7 Data Provider for AAI R1.5 system is unique in a shared catalog, multi-LPAR environment, we recommend that you use the following dataset naming conventions for the execution datasets. This way, it is posible to support the data feed requirements from multiple CA7 systems running on multiple LPARs, feeding multiple AAI Server systems.

your_HLQ.AIS7.zzzzyyyx.DSNNAME

Where:

  • your_HQL is any assigned High Level Qualifier of your choice.

  • AIS7 is fixed with this value to indicate this is a CA 7 Data Provider for AAI dataset.

  • zzzz is a 4 character identifier for the LPAR the owning CA 7 Data Provider for AAI system is running on. This can be the actual LPAR id or any other suitable unique value.

  • yyy is a 3 character identifier for the AAI Server to which the owning CA 7 Data Provider for AAI is delivering the datafeed. This can be the 3 character id of the AAI Server itself, by default this is AAI or any other suitable value that uniquely identifies the AAI Server.

  • x is the last character from the name of the CA7 instance that this CA 7 Data Provider for AAI is operating for. This name is the value specified in the CA7= parameter of the SVCNO statement in the CA7 INIT Deck (usually CA71 through CA78), although an alias name can also be assigned. For a CA71 system, this character would be 1; for an alias name of U7QA, this character would be A.

  • DSNNAME is the fixed last level name of each of the execution datasets used by the CA 7 Data Provider for AAI and is specified in the JCL for allocating these datasets. These last level names should not be altered from what is specified in the JCL for each dataset.

The three character yyy identifier for the AAI Server together with the one character x identifier from the CA7 instance name are combined by the CA 7 Data Provider for AAI to create its own unique instance code.

Example: An AAI instance called PRD receives data from a CA72 instance of CA7. The generated instance code would be PRD2 for the CA 7 Data Provider for AAI that is delivering that data.

This instance code must be used as part of the Started Task procedure name to uniquely identify each CA 7 Data Provider for AAI STC (see Library Member Naming below).

Library Member Naming

The CAI7CLS0 and CAI7JCL installation libraries contain sample members. You can use them to create the instance-specific versions required for each instance of the CA 7 Data Provider for AAI. The naming convention for these members is AI7?YYYX, where

  • AI7 identifies this as a library member for the CA 7 Data Provider for AAI.

  • ? is a unique single character identifying the member function/type.

  • YYYX is a value to be replaced by the instance code previously described.

Example:

Following our previous example where the generated instance code was PRD2, the CAI7JCL member AI7AYYYX is the sample JCL used to allocate the execution datasets for an instance of the CA 7 Data Provider for AAI.

When creating the execution datasets for an instance called PRD2, make a copy of the AI7AYYYX member and call it AI7APRD2. Then modify this instance-specific copy to set the size of the SRVRRPTS and ADDDRPTS dataset needed for the CA72 instance of CA7.

Use the CAI7JCL member AI7SYYYX as basis to create an instance-specific copy of the primary STC procedure for that CA 7 Data Provider for AAI. Call the copy AI7SPRD2 and modify it as needed.

Use the CAI7JCL member AI7CYYYX as basis to create an instance-specific copy of the secondary STC procedure used by Automation to issue Control commands to the primary STC.

Similarly, in the CAI7CLS0 library is the sample CLIST member called AI7CYYYX used to start the ISPF-based Control System User Interface. For instance code PRD2, make a copy called AI7CPRD2 and modify as described later.

See also: