The VIEW option enables you to check the status of variables after a rule has been invoked.
Figure 19 Variables Committed for Rule Screen
-------<G>---------------- VARIABLES COMMITTED FOR RULE -----------------(BA.V)
COMMAND ===> SCROLL===> CRSR
O GROUP NAME --------- VARIABLE NAME ------ GENERATION ------------------------
INTRAC COST03 000
Value : 319302.000
User Key : Run Id :
Creation Date : 11/12/00 11:06:06 By User : M66 Type : B
-------------------------------------------------------------------------------
INTRAC INVAMT03 000
Value : 36874.810
User Key : Run Id :
Creation Date : 11/12/00 11:06:06 By User : M66 Type : B
-------------------------------------------------------------------------------
INTRAC COST02 000
Value : 541873.000
User Key : Run Id :
Creation Date : 11/12/00 11:06:06 By User : M66 Type : B
-------------------------------------------------------------------------------
INTRAC INVAMT02 000
Value : 679025.520
User Key : Run Id :
Creation Date : 11/12/00 11:06:06 By User : M66 Type : B
-------------------------------------------------------------------------------
07.34.54
This screen displays key information about any Database Variables that were affected by the execution of rule ARWARN4A.
In this example, the first variable listed is named COST03. It was updated with a value of 319302, and is currently generation 000, the most recent value of this variable.
Note: A rule always creates a variable value as generation 000. Any previous values existing for this variable then become the next older generation (001, 002, and so on).
Further down this screen are other variables that were updated by the rule. By entering UP and DOWN commands, or pressing the corresponding PF07/PF19 and PF08/PF20 keys, you can examine all the variables listed on this screen.
The next topic examines the Balancing Mission definition.
Parent Topic |