Copyright © Cloud Software Group, Inc. All Rights Reserved

Examples of System Log Information

The following sections contain samples of the different types of output available. They use examples from the sample rule shown in System Log.

Location of the Error

Error detected in rule “NEWMANAGER” at action 3 FORALL
statement 2

In the rule called NEWMANAGER, the error occurred at the second line in the FORALL loop, and the FORALL statement is the third statement (or action) in the rule. The action sequence numbers are not referenced.

If the error occurs in the exception handler part of the rule, this is explained. The statement numbers begin counting from 1 for each exception handler.

Reason the Rule Stopped Executing

Access error on TABLE "EMPLOYEES"
REPLACE EMPLOYEES
Invalid number of parms supplied for table "EMPLOYEES"

Traceback of the Rules

Traceback of rules called at time of error
NEWMANAGER(96,10)
End of traceback

If the rule had been called by another rule, both rule names would appear in this section, starting with the most recently called rule. The traceback lists only the rules called that lead to the point of error.

List of Active Local Variables

No local variables

If local variables had been assigned values, messages similar to the following could appear:

Dump of local variables
X = 10

If the same local variable is declared in several rules, the value of the variable in the rule closest to the failure is the value displayed in the dump.

List of the Buffers for Active Tables

Dump of active tables
Table EMPLOYEES
EMPNO = 44385
LNAME = 'SOUZA'
POSITION = 'SALES'
MGR# = '44385'
DEPTNO = 10
SALARY = 719.00
ADDRESS = ''
CITY = ''
STATE_PROV = ''
ZP_CODE = ''
HIREDATE = *NULL*
End of table dump

Up to the Last Sixteen Rules Invoked

Last 16 rules called
NEWMANAGER
End of call list

The rules invoked in this transaction are listed starting with the rule that failed and proceeding in order from the most recently invoked rule to the least recently invoked rule.

If the failed transaction has parent transactions, this information is repeated for each transaction level, starting with the first-level transaction. Information for the next transaction level is indicated by a message similar to:

Transaction at depth 2

Copyright © Cloud Software Group, Inc. All Rights Reserved