Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 .

Adding CAS definitions for the first time


Use the following procedure to add the first CAS definitions to a new CAS.

To maintain existing CAS definitions, see Managing-the-coordinating-address-space-CAS.

To enable cross-system communication between CASs, perform the following steps first on the local system, and then on each of the systems with which you want to communicate.

To enable cross-system communication between CASs

  1. Start the CAS by issuing the following command:S casname

  2. Start a BMC AMI Ops terminal session.

  3. On the BMC AMI Ops Selection Menu, select Option P, Plex Manager.

  4. On the COMMAND line, type CASDEF and press Enter to display the CASDEF view.

    Notes

    • When you display CASDEF on a system for the first time and no CAS definitions exist, a default definition is shown with the following information in the Description field:

      Use CASDEF to update

      In addition, the VTAM Appl Name field has a value of *NONE*.

    • If you are migrating from a previous product release, those definitions are shown when you display CASDEF. The same description appears for all definitions.
  5. On the COMMAND line, type EDIT and press Enter to obtain an edit lock.

  6.  On the COMMAND line, type ADD casname and press Enter, where casname is the name of the system image or some other unique name.

    Note

    When defining a CAS, you should use the same name as the system name (because only one CAS should run per system image, except in test situations where a production CAS is already running on the same system).

    You can use the Add New CAS System Definition dialog to define unique cross-system communication parameters to each CAS.

  7. In the Add New CAS System Definition dialog, complete the definition. For complete instructions, see Adding-CAS-definitions.

    Notes

    Once your CAS definitions are created, you can modify their parameters if required. For more information, see Changing-existing-CAS-definitions.

  8. When you are finished with the CAS definition, press or type END to return to the CASDEF view.

  9. On the COMMAND line, type SAVE to save the information in the BBPARM CAS definition member.

  10. For each cross-system CAS with which you want to establish communications, repeat Step 6 through Step 9.

  11. Stop the CAS by issuing the following command:P casname

  12.  To implement the new cross-system CAS definitions, start the CAS again by issuing the following command:S casname

    The definitions on the local CAS are now complete.

  13. To complete the CAS definitions on the remote systems, perform one of the following tasks, depending on your CAS configuration:
    • If each CAS has a separate and unique BBPARM library that it does not share with any other CAS, perform the following steps:
      1. Log off the current system.
      2. Log on to each remote system.
      3. Repeat Step 1 through Step 12.
    • If the CASs operate in a shared DASD and shared BBPARM environment, perform the following steps:
      1. Log off the current system.
      2. Log on to each remote system.
      3. Repeat Step 1 through Step 6.
      4. On the COMMAND line, enter INStall casname to update the cross-system communication parameters for the local CAS.
      5. Stop the CAS (P casname) and restart it (S casname) to initialize the CAS with the new cross-system CAS definitions.

 

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