Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Using sysplex variables

The following topics describe sysplex variables and where you can use them in 

BMC AMI Ops Automation

 automation tasks.

For information about how to implement support for sysplex variables, see Implementing-support-for-sysplex-variables. 

Warning

Sysplex variables consume more CPU resources and are slower than SHARED variables, therefore, sysplex variables are not designed for storing static data or data that is referenced by only one BMC AMI OpsA BBI-SS PAS. This type of data is more efficiently stored as SHARED, PROFILE or TSO variables.

Sysplex variables are a subclass of SHARED variables, and are identified by a special prefix name in the variable name. After a VPUT command is issued to update a sysplex variable, the updated value is immediately seen by a subsequent VGET command on any BBI-SS PAS that shares the sysplex variables.

After support for sysplex variables is enabled, all BMC AMI OpsA subsystems that connect to the same Coupling Facility structure will share sysplex variables. By default, all BMC AMI OpsA BBI-SS PASs that are in the same AOAnywhere cross-system coupling facility (XCF) group will use the same Coupling Facility structure name. Non-sysplex SHARED variables will continue to work as they have in earlier releases.

This section contains the following topics:

Related topic

Variables-in-REXX-EXECs

 

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