Implementing an Instance of the CA7 Server for AAI

Once you have installed the CA7 Server for AAI and you have performed all the preparation activities, you can start implementing it. Implementing the server means creating and configuring as many instances as you need. You do this using the IMS.

For more information about the implementation preparations tasks, see Preparing for Implementation of the CA7 Server for AAI

Tip:

Make sure to have the completed Implementation Checklists (CA7 Server for AAI) at hand when implementing the instance.

Implementing the CA7 Server for AAI involves the following tasks:

Starting the IMS

During the installation of the CA7 Server for AAI, three pre-tailored CLISTs are created in the yourHLQ.CUSTLIB library: AIZCPRIM, AI7CPRIM and AITCPRIM. Use either the AIZCPRIM or AI7CPRIM CLISTs to start the IMS (Instance Management System). The CLIST AITCPRIM is only for the IWS/z integration.

To Start the IMS Using the AIZCPRIM Member

  1. Select option 6 from the ISPF.

  2. Start the IMS for IWSz in one of the following ways:

    METHOD 1

    Use a command to open the Scheduler Selection Menu:

    EX ‘yourHLQ.CUSTLIB(AIZCPRIM)’

    Screenshot of the zOS Data Providers for AAI Scheduler Selection menu

    Select CA 7 Workload Automation to start the IMS for CA7.

    Note:

    This method would be used in an environment where both the CA7 Server for AAI and the IWSz Server for AAI are going to be used.

    METHOD 2

    Use the following command to bypass the initial Scheduler Selection panel and start the IMS directly for CA7 Scheduler definitions:

    EX ‘yourHLQ.CUSTLIB(AI7CPRIM)’

  3. The CA7 Server for AAI panel is displayed, where you add, configure, update and work with the instances you have defined:

    Screenshot of the CA7 Server for AAI - IMS main menu.

    Since you can add up to eight instances per CA7 Server for AAI, this panel contains eight available menu slots.

    You can color-code the instance name and LPAR ID to make the instances easier to recognize.

    Note:

    The previous screenshot shows an environment with two instances. If you have not defined any instances yet, the IMS bypasses the Instance Selection panel and opens Add Instance.

  4. The next step is to add instances of the CA7 Server for AAI.

Creating an Instance

Use the A - ADD New Instance Entry option in an unused menu slot and define the instance. This consists of two tasks:

  • Defining the menu details

  • Allocating the execution datasets

Defining the Menu Details

You define the menu details on the CA7 Server for AAI - Add Instance screen:

Enter the following values:

CA7 System Settings

  • CA7 Instance

    The 4-character CA7 Instance ID as specified on the SVCNO statement in the CA7 INIT Deck.

    If the XTMNAME= parameter is specified on the SVCNO statement, then that value should be specified here. Otherwise, use the value from the CA7= parameter.

    This name will be used as a parameter when executing the CCITERM (CAL2X2WB) program to reference the correct CA7 system.

  • LPAR ID

    If you have installed the data provides package on just one LPAR, this fields is pre-populated with the SMF ID of that LPAR (up to 4 characters).

    If you have deployed the package on multiple LPARs, you must select the SMF ID on the LPAR that this instance will be executing on.

    Later on you can overwrite this name and use any 4-character name that makes the identification of the instance easier (the name of the instance is displayed on the Instance Selection menu). For example, if the system has been deployed to an LPAR with an SMF ID of SYST, but which is more commonly known as TEST, then you can replace SYST with TEST. Changing the name here does not affect the actual SMF ID value that the Instance is associated with, which is maintained internally.

AAI System

  • AAI Instance ID

    The 3-character name of the target AAI system for this instance. This is the name given to the AAI system upon installation. This name must be unique.

    Tip:

    You can freely define the AAI Instance ID. You may want to use the same name as used for the AAI system itself for display and identification purposes. Alternatively, if it makes more sense in your environment, you may want to use a different name. For example, the AAI system itself may have been installed with the AAI default name but can be specified here as PRD.

Menu Display Settings

  • Menu #

    Menu entry that will be used to display this Instance from the 8 entries available.

    This value is pre-populated by one of the following:

    • The menu entry used for the A - ADD Instance option

    • 1 if this is the first Instance being created.

This can be overwritten by any other unused menu entry number. An error message will occur if a menu entry number selected is already in use

  • Name

    Up to 20 characters. This is the descriptive name for this instance that will be displayed on the Instance Selection menu screen. If not specified, the system automatically generates a name with the following:

    xxxx Feed for yyy

    where xxxx” is the CA7 instance ID and yyy is the AAI Instance name.

    Fill in your own descriptive name of up to 20 characters to replace the automatically generated name

  • Name Color and Reverse

    Color in which the name will be displayed. Use the numbers 1 through 7 to define the color and whether this will be displayed using Reverse Video or colored text.

  • LPAR Color and Reverse

    Color in which the LPAR ID value will be displayed. Use the numbers 1 through 7 to define the color and whether this will be displayed using Reverse Video or colored text.

Allocating the Execution Datasets

After adding and configuring the menu entries, you allocate all the datasets required by the CA7 Server for AAI.

Screenshot showing the Allocate Execution Datasets panel in IMS.

If an error occurs during the allocation of any of the execution datasets, you can re-display this panel by selecting U – UPDATE Instance Entry and then selecting A – ALLOCATE Instance Datasets. This will then attempt to create any of the datasets that do not already exist and can therefore be used multiple times until the correct values have been specified. To re-create datasets that have already be created you must first delete those datasets manually.

Enter the values in the following fields to identify the datasets that the server needs:

  • Default HLQ

    Use this field to generate dataset names with a standard format that ensures that each Instance execution dataset are unique. By using this, you avoid clashes with existing Instance datasets. The standard format dataset names that will be used for the Instance you are creating is shown in yellow above the field.

    The standard format consists of the following:

    • A prefix of the value specified in this field. It can be one or more levels.

    • AIS7, the version identifier level for the CA7 Server for AAI instance.

    • Instance code followed by the LPAR ID.

      The instance code is generated from the AAI Server name plus the last character of the CA7 instance.

      This code format is also used to identify the tailored JCL members that will be created for each instance in the yourHLQ.CUSTLIB library.

    • The xxxxxxxx last level in the standard format represents the various different datasets that will be created using that format prefix, such as SRVRSCFG, SRVRSREQ, and so forth.

  • Override HLQ

    Use this field to create datasets with a non-standard format HLQ. Only the last level (xxxxxxxx as above) is generated automatically for each dataset.

    Important!

    • Make sure that the datasets are unique for all instances.

    • Any value specified here will be used regardless of any value specified in the Default HLQ field.

  • SMS and Non-SMS Settings

    Use these fields to direct the allocation of the execution datasets. If these fields are left blank the location of the execution datasets will be determined by your sites standards.

    Note:

    If you leave the VOLSER field blank and the system is unable to find a default volume, you might encounter the following error:

    IDC3506I REQUIRED VOLUMES AND/OR DEVICETYPES HAVE BEEN OMITTED

    If this happens, you must specify the VOLSER.

  • zFS Volume Name

    The Override DSN field allows the specification of an alternative name for the zFS volume Cluster to be defined that can be used if site standards require VSAM Clusters to have specific HLQ. Any value specified here will be used as the complete zFS volume name. If this is left blank, then the default HLQ specified above will be used and the default zFS volume name that will be created is shown in yellow. If the Override HLQ is specified, then the Override DSN must also be specified.

  • zFS Space Allocation

    Specify the Primary space in cylinders for the CA7 Server for AAI zFS volume to be mounted to the Instance-specific zFS Data Path USS directory that will be used for the data generation location. Use the value obtained from following the instructions in the section on zFS Volume Sizing.

Canceling the Allocation to Use Existing Datasets

Use PF3 to cancel the Allocate Execution Datasets step and to return to the Instance Selection main menu. You might need to do this if, for example, the execution datasets already exist or if the datasets from another Instance of a similar size were copied and renamed.

A warning message that the instance is incomplete is displayed. Use the U - UPDATE Instance Entry function to specify the HLQ of the existing datasets and to complete the instance entry.

Created Instance JCLs and Their Naming Structures

After successfully creating an instance of the CA7 Server for AAI, the IMS automatically creates several tailored JCL members that are specific for that instance in the yourHLQ.CUSTLIB library.

The JCL names have the format AI7vyyyx, where

  • AI = the standard prefix for all AAI members

  • 7 = the indicator that this is a CA7 scheduler type

  • v = the JCL version, where

    • R = Request STC

    • S = Server STC

    • K = Kill (shut down)

    • T = Delivery Test

    • M = Mount statement

    • L = History analysis

    • P = Data pre-load

  • yyyx = the unique instance code

The following tailored JCLs are created for the CA7 Server for AAI:

  • AI7Ryyyx

    Request STC JCL procedure primarily used by automation.

  • AI7Syyyx

    Primary STC JCL procedure to start the CA7 Server for AAI instance.

  • AI7Kyyyx

    Secondary JCL procedure to kill (shut down) a CA7 Server for AAI instance.

  • AIZTyyyx

    Delivery Test STC JCL to test the selected data delivery method.

  • AI7Myyyx

    Mount statement JCL that must be added to the BPXPM00 member in SYS1.PARMLIB to ensure the zFS volume is mounted to the USS Data Directory after each IPL. This member is generated after Configuring the Instance process is completed.

    Important!

    Before mounting the zFS file, make sure that the following are true :

    • The directory exists on USS where the zFS file will be mounted to per the TSO command. If it does not exist, you must create it manually.

    • The user that will be used to execute the server STC has permissions to write to this directory.

  • AI7Lyyyx

    History Log Analysis Job JCL

  • AI7Pyyyx

    History Event Data Pre-Load STC JCL

Next Step

You are ready to start configuring the instance of the CA7 Server for AAI that you have just defined. For more information about how to do it, see Configuring an Instance of the CA7 Server for AAI.

See also: