Skip to Content
Information

This site will undergo a brief period of maintenance on Thursday, 23 April at 2:30 AM Central/1:00 PM IST. During a 30 minute window, site availability may be intermittent.

Using sysplex variables

Related topic

Variables-in-REXX-EXECs

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.

Error
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.

You manage sysplex variables with the VPUT, VGET, VDEL functions and specifying the SHARED pool. 
 

After you enable support for sysplex variables, 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.

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. 

 

This section contains the following topics:

 

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

BMC AMI Ops Automation 8.4