AOF Rule Tools › AOF Variables › Static Variables

Static Variables

Static variables maintain their value across multiple executions of a single rule, which means that data can be shared between executions of the same AOF rule.

For example, consider the following rule logic:

)MSG $HASP373
)INIT
COUNT=0
)PROC
/************************************************************/
/* Rule Purpose :     Keep a running total of HASP373 jobs  */
/* $HASP373 jobname   STARTED                               */
/************************************************************/
COUNT= COUNT + 1                         /* Add to counter  */
)TERM
LOGIT = OPSSEND('*','B','OPSAUTO4 TOTAL 373 = 'COUNT)

The variable COUNT is a static variable that retains its value each time this rule processes a $HASP373 message.

Review the following additional facts about static variables:

• Static variables are rule-specific and must be defined (initialized) in the )INIT section.
• The same static variable name used in the initialization sections of two different rules refers to two different static variables.
• A static variable cannot be a compound symbol (for example, JOB.COUNT).
• The name of a static variable can be up to 50 characters in length.
• The value assigned to a static variable can be up to 256 bytes in length. Any value assigned with a length greater than 256 is truncated.
• A static variable is deleted when the rule is disabled.
• Access to static variables is not serialized. If serialization is needed, then use OPS/REXX global variables and the OPSVALUE function of OPS/REXX.