|
|
|
|
|
This group includes messages for the Control-O product.
Explanation: An error occurred while executing the indicated type of DO statement.
The DO action fails.
Corrective Action: Correct the DO statement in the rule.
Explanation: This information message indicates that a user message was activated by the SHOUT Facility. user is the user ID of the job order requesting the SHOUT statement.
Corrective Action: No action is required.
Explanation: An AutoEdit symbol within a DO statement in a Control-O rule definition could not be resolved.
DO statements within a rule definition are processed sequentially. If AutoEdit resolution of a symbol with a DO statement fails, the DO statement, and any subsequent DO statements within the rule definition, are cancelled. This default processing can be overridden by using the %%RESOLVE NO control statement in a previous DO SET statement. The statement will be resolved as far as possible before performing the DO statements.
The DO action in which the AutoEdit resolution failed, and any subsequent DO actions, are cancelled.
Corrective Action: Check the return code (rc) and reason code (rsn) in the following tables to determine the reason for the failure. Correct the symbol in the rule definition, and reorder the table. If the return code or reason code is not listed, the error is an internal error, and you should notify BMC Customer Support.
Return Code ( rc ) |
Reason Code ( rsn ) |
Explanation |
|---|---|---|
04 |
GETMAIN or FREEMAIN error |
|
|
1 through 6 |
GETMAIN failure Note: If you receive this error after the rule executes in wait mode, use the %%$LOCALPOOLSIZE system variable to try and solve the problem. For a list of events that cause a rule to enter wait mode, see the description of the WAITPR# parameter. |
|
7 through 10 |
FREEMAIN failure |
08 |
Variable not found |
|
|
13 |
Variable not found and RESOLVE flag is on. |
|
36 |
%%$COMMSYS value length error. |
|
68 |
%%$TIMEINT first argument is not a valid date. |
|
69 |
%%$TIMEINT second argument is not a valid date. |
|
74 |
%%$X2C argument length is greater than 4. |
|
88 |
%%$DOLIMIT first argument is not numeric. |
|
89 |
%%$RULE functions argument is out of rule stack. |
|
90 |
%%$RULE functions argument is not numeric. |
|
98 |
Global variable pool not found. |
|
100 |
ISGENQ returned a non-zero return code. |
|
980 |
Internal error - global pool or database not found |
|
982 |
Internal error - global pool or database not found |
|
983 |
$GLOBAL POOL NOT FOUND |
12 |
Syntax error or general error |
|
|
11 |
Empty SET command. |
|
15 |
Empty IF command. |
|
21 |
%% not found in SET command. |
|
22 |
Separator not found after %%. |
|
23 |
‘=’ not found in SET command. |
|
24 |
%%$TIMEOUT value not numeric. |
|
25 |
%%$RESPMSG or %%$TIMEOUT - invalid parentheses. |
|
26 |
%%$RESPMSG or %%$TIMEOUT - too many values. |
|
27 |
%%$WAITKSL or %%$TSO or %%$CMD - invalid value (not YES/NO). |
|
28 |
%%$TIMEOUT - value too large. |
|
29 |
%%$‘STATID value length error. |
|
30 |
%%$AUTOLOG value length error. |
|
37 |
%%$AUTOSYS value length error. |
|
41 |
Function arguments not separated. |
|
42 |
Too few function arguments. |
|
45 |
CTMLINE# PARAMETER NOT NUMERIC when trying to set %%$CTMLINE# to a non-numeric value. |
|
46 |
CTMLINE# > CTMLINES when trying to set %%$CTMLINE# to a value greater than %%$CTMLINES. |
|
47 |
CTMLINE# < 0 when trying to set %%$CTMLINE# to a value less than 0. |
|
52 |
%%$SUBSTR 2nd argument not numeric. |
|
53 |
%%$SUBSTR 3rd argument not numeric. |
|
54 |
%%$SUBSTR 2nd argument out of range. |
|
55 |
%%$SUBSTR 3rd argument out of range. |
|
56 |
%%$RESOLVE argument not recognized. |
|
57 |
%%$RANGE 1st argument not numeric. |
|
58 |
%%$RANGE 2nd argument not numeric. |
|
59 |
%%$RANGE 1st argument out of range. |
|
60 |
%%$RANGE 2nd argument out of range. |
|
61 |
%%$RANGE is too narrow. |
|
62 |
%%$CALCDATE 1st argument not in valid format. |
|
63 |
%%$CALCDATE 2nd argument not in valid format. |
|
64 |
%%$TIMEINT 1st argument is not 11 digits in length. |
|
65 |
%%$TIMEINT 1st argument is not numeric. |
|
66 |
%%$TIMEINT 2nd argument is not 11 digits. |
|
67 |
%%$TIMEINT 2nd argument is not numeric. |
|
71 |
More than one operator in one line. |
|
72 |
Less than two operands for an operator. |
|
73 |
More than two operands for an operator. |
|
75 |
%%$D2X argument length is greater than 10. |
|
76 |
%%$D2X argument is not numeric. |
|
77 |
%%$D2X argument number is greater than 2147483647 (2G). |
|
78 |
%%$X2D argument length is greater than 8. |
|
79 |
%%$X2D argument has an invalid character. |
|
81 |
First operand in arithmetic operation is not numeric. |
|
82 |
Second operand in arithmetic operation is not numeric. |
|
83 |
%%$DIV 2nd operand is 0. |
|
84 |
First operand is greater than 2G. |
|
85 |
Second operand is greater than 2G. |
|
86 |
Result of %%$PLUS case overflow. |
|
87 |
Result of %%$MINUS case overflow. |
|
91 |
Logical operand not numeric. |
|
92 |
Numeric logical operand out of range. |
|
93 |
Invalid logical operator. |
|
94 |
Logical atomic expression expected but not found. |
|
95 |
Unbalanced parentheses in logical expression. |
|
96 |
Too many nested parentheses in logical expression. |
|
97 |
Unbalanced quotes. |
|
99 |
%%$GLOBAL value length error. |
16 |
Errors reading the global member |
|
|
08 |
Insufficient memory. |
|
12 |
Member not found. |
|
16 |
DSN is not a library. |
|
20 |
DSN is not fixed. |
|
24 |
Logical record length is not 80. |
|
28 |
Data set in use. |
|
36 |
Data set not in catalog. |
|
40 |
Dynamic allocation failed. |
|
52 |
Error when opening/processing a directory |
|
56 |
An abend was intercepted. |
20 |
Errors writing the global member |
|
|
08 |
Insufficient memory. |
|
12 |
Member not found. |
|
16 |
DSN is not a library. |
|
20 |
DSN is not fixed. |
|
24 |
Logical record length is not 80. |
|
28 |
Data set in use. |
|
36 |
Data set not in catalog. |
|
40 |
Dynamic allocation failed. |
|
52 |
Error when opening/processing a directory |
|
56 |
An abend was intercepted. |
24 |
Program buffers shortage |
|
|
12 |
Not enough space in RSL buffer. |
|
32 |
Not enough space in VCB for name and value. Variable name and data are too long. |
|
43 |
Arguments too long (ARG buffer overflow). |
32 |
Program errors |
|
|
100 |
No last non-blank for non-blank value in SET command. |
|
101 |
No succeeding RSL for adjoining variables. |
|
102 |
Problems in PUTVAR while initiating. |
|
103 |
Too many arguments requested from PARSARGS. |
|
104 |
Problems calculating weekday. |
|
105 |
Invalid SET system variable. |
|
106 |
No local anchor was passed. |
|
107 |
No global anchor was passed. |
|
109 |
No MCT or SWT present in %%$IPLDATE for date formatting WO0816*. |
36, 40, and 44 |
Global variables errors |
|
|
04 |
Empty chain. |
|
08 |
End of chain. |
|
12 |
PNXH header error. |
|
16 |
PLBH header error. |
|
20 |
CTMMSK mash error, RC from IS is > 4. |
|
24 |
Pool is protected. |
|
32 |
Unable to get XAE information. |
|
33 |
Machine is not participating on XAE. |
|
34 |
Attempt made to set an XAE type 1 database variable in another system image. |
|
98 |
Pool not found. |
|
100 |
Timeout error. %%$DBROW = %%$DBSETVAR was used to set an IOAVAR variable but the action could not be serialized for 2 minutes. |
|
107 |
No global anchor was passed. Program error. |
|
108 |
Field not defined in database. |
|
109 |
Requested row is out of range or database has reached its maximum row count. |
|
110 |
Unable to lock the Global Variables pool. |
48 |
Parse errors |
|
|
08 |
Invalid type. |
|
12 |
Place holder error. |
|
16 |
Position specification too long. |
|
20 |
Non numeric. |
|
24 |
Position null. |
|
28 |
Invalid variable. Specified variable is greater than 256, or the variable name is too long. |
|
32 |
String error. |
|
36 |
Invalid TPE type. |
|
40 |
Section vector overflow. |
|
44 |
Variable buffer overflow. |
|
107 |
No global anchor was passed. |
Explanation: During rule processing, Control-O failed to resolve an AutoEdit variable, either because of a syntax error or because the AutoEdit variable was not found.
This message is usually followed by message WTO283E, which explains the reason for the error.
The rule is aborted.
Corrective Action: Check message WTO283E to determine why the AutoEdit variable did not resolve, and correct the problem accordingly.
Explanation: The rule identified in the message was suspended because it reached the rule threshold limit.
The rule threshold limit determines the maximum number of times a rule may be triggered. This limit is defined in one of the following ways:
The rule is suspended.
Corrective Action: Determine why the rule reached the limit, and if there is a problem correct it. Adjust the threshold limit value, if necessary, or use the Rule Status screen to release the rule from its SUSPEND state.
Explanation: A DO WAIT statement was encountered while in Command-Response mode. A DO WAIT statement is invalid when a rule is executing a DO COMMAND in the Command-Response mode.
The rule is aborted or ignored.
Corrective Action: Correct the rule so that it does not encounter a DO WAIT statement when in Command-Response mode.
Explanation: A rule executed more than 10,000 DO statements. This message is followed by another message containing the name of the problematic rule.
In order to avoid an infinite loop, only a limited number of DO statements can be executed. The default setting for this limit is 10,000. You can override this default by setting %%DOLIMIT to a higher value.
The rule is aborted.
Corrective Action: Either correct the rule to perform less than 10,000 DO statements, or set %%DOLIMIT to a higher value.
Explanation: The dateref field in the DO COND statement contains wildcard symbols ($$$$ or ****).
The rule is aborted or ignored.
Corrective Action: Specify a distinct date in the dateref field.
Explanation: The maximum number of nested rules executed in response to a DO RULE statement has been exceeded. Rules can be nested up to 20 deep.
The rule at the twenty-first level is aborted or ignored
Corrective Action: Correct the logic so that there are no more than 20 nesting levels for rules.
Explanation: The rule invoked using a DO RULE statement was not found in the specified, or default, table.
The rule is aborted or ignored
Corrective Action: Correct the DO RULE statement to contain a rule defined in the specified or default table, or define the rule in the specified table.
Explanation: A rule invoked another rule by using the DO RULE statement did not satisfy the Runtime Scheduling criteria.
Processing continues. The invoked rule is ignored.
Corrective Action: If this is not intentional, correct the invoked rule definition so that it satisfies the Runtime Scheduling criteria.
Explanation: A rule aborted because of an error. This message is preceded by another message that describes the cause of the error.
The rule is aborted at the point of error.
Corrective Action: Correct the error according to the preceding message.
Explanation: This warning message indicates that a problem occurred when processing a rule. This message is preceded by another message that describes the problem.
The rule is ignored. Processing continues.
Corrective Action: Correct the problem according to the preceding message.
Explanation: A nonzero return code was received from a called program or routine. During execution, detection of a nonzero return code caused this message to be issued.
Execution of the rule terminates
Corrective Action: Send a screen print of the rule and the a trace of its execution to BMC Customer Support.
Explanation: A DO DOM statement contains an invalid value for a message identification number (DOM ID). See the Control-O User Guide for a description of valid AutoEdit system variables that can be used to specify the desired message ID number.
The rule is aborted.
Corrective Action: Correct the DO DOM statement by specifying a valid message ID number (DOM ID).
Explanation: A rule that was required to wait could not, because no Wait element was available for it. A rule requires a Wait element to wait. In this case, the maximum number of Wait elements defined in the WAITPR# parameter of CTOPARM was already being used.
The rule is aborted.
Corrective Action: Adjust the WAITPR# and NUMCONS parameters in CTOPARM according to the instructions in the Control-O chapter of the INCONTROL for z/OS Installation Guide.
Explanation: A rule that was required to wait could not, because the Wait element was too small. A waiting rule stores its data in a Wait element. In this case, the Wait element is not large enough to store the rule data.
Rule is aborted.
Corrective Action: Either split the rule into two rules, or use less AUTOEDIT variables in it. When splitting the rule, do not define the second rule as an ON RULE, because it will use the same Wait element as the first rule.
Parent Topic |