Additional considerations for sysplex variables

For example, all of the MainView AutoOPERATOR subsystems could run the same startup EXEC or Rule that tests the environment and conditionally use the VPUT function to specify sysplex variables with different values.

You should carefully examine your automation needs and environment to first determine if your automation even requires the use of sysplex variables. As previously noted, static values or values used by only one MainView AutoOPERATOR subsystem should be stored in SHARED, PROFILE, or TSO variables.

If you decide to enable support for sysplex variables, and you have three MainView AutoOPERATOR systems (AO1, AO2, and AO3) in the sysplex, you must ensure that automation works correctly no matter which MainView AutoOPERATOR BBI-SS PAS starts first or if they all start at the same time.

To initialize your sysplex variables correctly, do not design automation where one BBI-SS PAS must start before subsequent BBI-SS PASs.

You should design and test any automation that uses sysplex variables so that any of the MainView AutoOPERATOR BBI-SS PAS can be started first.

Also test that all of the systems, (in this case, AO1, AO2, and AO3), can be started simultaneously and the sysplex variables have the correct values.

You can use EXECs with the IMFEXEC VENQ SCOPE(Global) command to protect or serialize operations across MainView AutoOPERATOR BBI-SS PASs in the sysplex.