Making variables flexible

We recommend that you make your TOM object definitions as flexible as possible. You can do so by using variables in the object definition. For detailed information about using variables, see Using-variables-on-the-TOM-dialogs. 

You can use the following types of variables or symbols in an object definition:

  • SHARED variables in the local PAS
  • Static system symbols
  • TOM object reference variables

Shared variables

SHARED variables are located in the shared variable pool in the local BMC AMI Ops Automation PAS. You can use shared variables for custom automation in Rules and EXECs, and also reference them in an object definition. Shared variables pass information between different pieces of automation. 

Important

Shared variables last only for the life of the IPL.

For more information about shared variables, see SHARED-variables-usage-and-pools and Using-advanced-automation-with-BMC-AMI-Ops-Automation. 

Related topics

Mass-editing-the-definition-base-by-using-MAMEXPRT

Updating-definitions-in-batch

Using-advanced-automation-with-BMC-AMI-Ops-Automation

How-variables-are-resolved

Using-variables-on-the-TOM-dialogs

SHARED-variables-usage-and-pools

BBPARM-member-BBIVAR00-parameters

List-of-object-reference-variables

To use shared variables to start objects as part of the IPL process, use the BBIVARxx member in the UBBPARM data set. You can use this member to define shared variables in batch in the shared pool of the local PAS at initialization of OpsA. For more information about how to use this parameter member, see BBPARM-member-BBIVAR00-parameters. 

Static system symbols

Static system symbols are defined in IBM z/OS for the local system. Like shared variables, you can use symbols to start objects as part of the IPL process.

By using static system symbols, such as &&SYSNAME and &&SYSCLONE, you can find information about the system release level, the sysplex name, and so on. You can also use the IBM z/OS command DISPLAY SYMBOLS, which displays what you have defined in the list for the local system.

For more information about system symbols and the IEASYMxx member, see the IBM manual z/OS MVS Initialization and Tuning Reference. 

Object reference variables

You can use variables, which are resolved at the time of usage, to change your object definitions. For example, you can set a variable to change the object dependency chain based on your needs. You can also use variables in the text of a command to start or stop an object in many ways. An object reference variable takes the value from one field in the object definition and allows another field to reference that value. 

The following examples show how you can use reference variables.

Example 1

If the STC name field of an object definition has the value TSO, you can use the object reference variable &@STCNAME to populate another field. Any time you enter &@STCNAME in a different field in the same object definition, the reference variable inserts TSO.

Example 2

If the STC name field of an object definition has the value TSO and you have specified the start command as S &@STCNAME, you can use the S TSO start command at runtime.

Example 2

If you need only a portion of a variable's value, use the following substring function:

<variable_name>:<start_location>:<length>

If the &&SYSNAME symbol has the value SYSA , and you have defined the substring S &&SYSNAME:2:3 in a start command, the variable value would be S YS.

For more information about object reference variables, see How-variables-are-resolved and List-of-object-reference-variables.

 

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