Skip to Content

How sysplex variables are named in BMC AMI Ops Automation

Sysplex variables are different from other SHARED variables by the presence of a one- to sixteen-character prefix. The default prefix is AOSPLX_.

When BMC AMI Ops Automation encounters variable processing where the SHARED variable begins with the AOSPLX_ prefix, BMC AMI OpsA treats the variable operation as a sysplex variable operation.

Related topic

Using-sysplex-variables


Warning

Important

To specify a different sysplex variable prefix, enter a one to sixteen-character value in BBPARM member AAOPRMxx for the SPLXREF parameter as shown in the following example:

SPLXPREF=(1 to 16-character user_specified_prefix)

See the Customizing-BMC-AMI-Ops-Automation-after-installation for more information about implementing support for sysplex variables and additional administrative tasks.

In addition to using a specific prefix to identify sysplex variables, BMC AMI OpsA supports two kinds of sysplex variables:

  • Sysplex variables with a one- to sixteen-character prefix and a one- to fifteen-character name; for example: AOSPLX_123456789A12345

    This format for sysplex variables is valid for the following IMFEXEC and AOEXEC commands:

    • VDEL
    • VGET
    • VLST
    • VPUT

  • Long sysplex variables with one- to sixteen-character prefix and a one- to thirteen-character name; for example: AOSPLX_123456789A123

    This format for long sysplex variables is valid for the following IMFEXEC and AOEXEC commands:

    • VDELL
    • VGETL
    • VLSTL
    • VPUTL

This section contains the following topic:

 

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

BMC AMI Ops Automation 8.4