Skip to Content

How TapeSHARE is customized

BBPARM member AAOTSPxx, where xx is a two-character, user-defined suffix, contains parameters that you can edit to customize how TapeSHARE operates.

Each z/OS image can have only one TapeSHARE installed in a BBI-SS PAS, but the BBI-SS PAS might have multiple AAOTSPxx members associated with it. A single installation of TapeSHARE can also have multiple AAOTSPxx members that you can modify and activate under different circumstances.

Within a TapeSHARE PLEX, you can define that each TapeSHARE can have its own AAOTSPxx member associated with it. For example, you might want to specify that SYSA can share devices with SYSB but not with SYSC. For this situation, you define an AAOTSPxx member for each system and edit the parameters to make these specifications.

Related topic

Customizing-TapeSHARE-optional

Once you decide which z/OS images you want to have in a TapeSHARE PLEX, install TapeSHARE on each of the images by following the instructions in Customizing-BMC-AMI-Ops-Automation-after-installation. Then you can proceed to perform any of the following additional customization steps.

For example, you might want a TapeSHARE PLEX of SYSA, SYSB, and SYSC.

After TapeSHARE is installed into a BBI-SS PAS on each of these three systems, TapeSHARE checks to see if any partnerships are established. If you do not define special partnerships between the systems by editing the AAOTSPxx members, TapeSHARE assumes that all BBI nodes defined in the BBINOD00 member that has TapeSHARE installed is a partner within the PLEX.

To create more specific relationships between the partners and control how they interact to share tape devices, use the PASPARM view or the Dynamic Parameter Manager application to modify the AAOTSPxx member for the partners.

 

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

BMC AMI Ops Automation 8.4