Simple variables and compound variable - Documentation for Impact Integration for z/OS - License Add On 8.1

Compound variables – indicated when an ampersand sign (&) and an exclamation point (!) prefix text in a field, and, the variable name contains periods.

Note

The exclamation mark (!) might have a different representation when used on international keyboards. As a substitute, use the equivalent symbol for the hexadecimal value X'5A'.

The Rule Processor resolves a compound variable based on its stem and the order of variables. The first node that precedes the first period is called the stem. For example, in the variable &!ABC.MYNAME, the stem is ABC.

When resolving compound variables, the Rule Processor does not resolve the stem and makes two passes of the variables.

For example, suppose you have the following three variables and values:

• ABC = FIRST

• MYNAME = SECOND

• ABC.SECOND = THIRD

The Rule Processor resolves the compound variable &!ABC.MYNAME as THIRD. The resolving proceeds according to the following sequence:

1. The Rule Processor does not resolve the stem, ABC.

2. During the first pass, the variable following the stem resolves and MYNAME becomes SECOND.

3. After the first pass, the Rule Processor defines the variable value as ABC.SECOND.

4. During the second pass, the variable ABC.SECOND resolves to THIRD.

   Therefore, the Rule Processor resolves the compound variable of &!ABC.MYNAME to THIRD.

If the Rule Processor cannot find a value for the variable, it resolves as a null value. For example, if the Rule Processor cannot find a value for variable &ABC, the Rule Processor assumes it is a null value.

For compound variables, if the variable &!CICS.SYSA does not have a value, the Rule Processor also assumes it is a null value.

However, if you have the following variables and values:

&!SHIFT1.CICSTAT = SCHEDULED

CICSTAT = not defined

The Rule Processor resolves the compound variable &!SHIFT1.CICSTAT to SCHEDULED.