Text |
Edit mask too long or not specified correctly. |
Explanation |
Possible reasons for this error: - The specified edit mask contains no character that would cause any digit of the value to be output (e.g., for a numeric edit mask no 'Z' or '9' was specified; for an alphanumeric edit mask no 'X' was specified). - The number of output digits in a numeric edit mask exceeds 31. - The number of output characters resulting from the edit mask string exceeds the maximum size of 1073741824 characters. - The edit mask string you have specified is too long. It must not exceed 80 source characters on mainframes and 244 on open systems. - You have specified an edit mask at statement level in a DISPLAY, FORMAT, INPUT or WRITE statement. At statement level in these statements, you can only specify 'EM=OFF', but no specific edit mask. |
Action |
Correct edit mask specification. |
Text |
Element in WRITE/INPUT statement does not fit on 1 line. |
Explanation |
The size of an element specified in a WRITE/INPUT statement exceeds the current line size. |
Action |
Either increase the line size (parameter LS), or reduce the size of the element (for example, by using a REDEFINE statement). |
Text |
Page overflow, too many vertical entries. |
Explanation |
The number of vertical entries specified within one INPUT, WRITE or DISPLAY statement exceeded the current page size. |
Action |
Either increase the page size (parameter PS) or reduce the number of vertical entries. |
Text |
Invalid printer reference number. |
Explanation |
A printer number must be specified as a numeric constant or symbolic constant defined with DEFINE PRINTER enclosed in parentheses. There is no additional printer support within a map (processing rule). |
Action |
Check program and correct error. |
Text |
Text string must begin and end on the same line. |
Explanation |
A text string is initiated with an apostrophe and must be ended on the same line with another apostrophe. If a text string longer than one line is required, enter the text in two portions (each within apostrophes) in two consecutive lines and with a hyphen (-) between the two portions. At execution time, the two portions will be concatenated. |
Action |
Correct error in program. |
Text |
DO or DOEND either missing or misplaced. |
Explanation |
A group of statements initiated with a DO statement must be terminated with a DOEND statement. The omission of a DOEND statement may only be detected at the end of a source program. The position of the error in the program does not necessarily correspond to the position where the DOEND should be placed. |
Action |
Ensure that each DO statement has a corresponding DOEND statement. |
Text |
Loop in line ... not closed within conditional block. |
Explanation |
A processing loop which is initiated within a conditional statement
block must be closed within that block.
Valid example: Invalid example:
-------------- ----------------
IF ... IF ...
DO DO
FIND ... FIND ...
DISPLAY ... DISPLAY ...
LOOP DOEND
DOEND END
END |
Action |
Check program and correct error. |
Text |
Attempt to close a non-existent processing loop. |
Explanation |
The LOOP statement can only be used to close an active processing loop. Either the processing loop to be closed was not properly initiated, or the processing loop had already been closed. |
Action |
Check program and correct error. |
Text |
Invalid positioning of AT BREAK/END condition. |
Explanation |
An AT BREAK/END condition cannot be used within a block of
statements which is dependent on another special condition.
Blocks are: AT BREAK
AT END/TOP OF PAGE
AT START/END OF DATA
ON ERROR
IF |
Action |
Re-position the AT BREAK/END condition. |
Text |
AT END OF or AT BREAK requires active processing loop. |
Explanation |
An AT BREAK/END statement can only be used within an active processing loop. |
Action |
Check program and correct error. |
Text |
Error occurred in user exit for source/object programs. |
Explanation |
A non-zero response code was received from the user exit which is used to store source/object programs in a user-controlled file. |
Action |
Check the coding of the user exit (response code in register 15 when returning to Natural). |
Text |
Reference invalid in AT START/END OF DATA or AT BREAK. |
Explanation |
A reference number was used to refer one of the above conditional statements to a specific processing loop. However, the specified reference number refers to a line which does not contain the correct loop-initiating statement. |
Action |
Check program and correct error. |
Text |
Only one BEFORE BREAK/AT START OF DATA allowed in a loop. |
Explanation |
Only one AT START OF DATA condition can be specified for a single
processing loop. If multiple statements are to be made dependent
on the AT START OF DATA condition, use a DO/DOEND construction
(see example below).
Example:
READ ...
AT START OF DATA
DO IF ... DO ... DOEND
IF ... DO ... DOEND DOEND
DISPLAY
LOOP
END |
Action |
Check program and correct error. |
Text |
No more than one ON ERROR statement allowed per program. |
Explanation |
Only one ON ERROR condition can be specified in a given program.
To check multiple conditions in an ON ERROR condition, use IF
statements within the ON ERROR condition.
Example:
--------
READ ...
UPDATE ...
ON ERROR IF ... END-IF
IF ... END-IF
END-ERROR
END-READ
END |
Action |
Check program and correct error. |
Text |
Inconsistent usage of '/n/' clause. |
Explanation |
The notation '/n/' can be used to specify how many positions of a variable are to be examined in the evaluation of an AT BREAK statement or an IF BREAK condition. A '/n/' clause may only be specified for break variables of format alphanumeric, binary, numeric or packed. The value for 'n' cannot be greater than the number of positions defined for the variable, that is, the number of bytes (for an alphanumeric or binary break variable) or the number of digits (for a numeric or packed break variable). Moreover, the value specified must not exceed 253 for alphanumeric fields and 126 bytes for binary fields. |
Action |
Check program and correct error. |
Text |
Statement not permitted within specified condition. |
Explanation |
Certain restrictions exist for the use of statements within certain conditions. The specified statement is not allowed in this type of condition. Within an external subroutine object, for example, only DEFINE SUBROUTINE statements and DEFINE DATA statements are allowed. |
Action |
Check program and correct error. |
Text |
1 element (column width) must not exceed 250 characters. |
Explanation |
The maximum length of elements that can be output in a DISPLAY column is 250 characters. |
Action |
Redefine element into smaller elements, or have the fields displayed in vertical mode. |
Text |
'FULL VALUE' must not be specified in EXAMINE TRANSLATE. |
Explanation |
Unlike in an EXAMINE statement, 'FULL VALUE' must not be specified in an EXAMINE TRANSLATE statement. An EXAMINE TRANSLATE statement always processes the entire content of the field. |
Action |
Correct error in program. |
Text |
Argument for AVER, TOTAL, SUM must be numeric. |
Explanation |
The argument for the evaluation of the Natural system functions AVER, TOTAL and SUM must be defined with numeric format. |
Action |
Check program and correct error. |
Text |
Edit mask permitted for output elements only. |
Explanation |
In an INPUT statement, edit masks can only be used for output elements (attribute = M or O). For input elements (attribute = A), edit masks cannot be used. Note that if you use hexadecimal edit masks for output elements, you cannot use attribute M = modify. |
Action |
Check program and correct error. |
Text |
Type of variable invalid as system function argument. |
Explanation |
1) A Natural system variable cannot be used as an argument for a Natural system function. If a system function is to be evaluated from a system variable, assign the value of the system variable to a user-defined variable and use this variable as the argument. 2) A variable used as a password/cipher variable cannot be used as an argument for a Natural system function. If the same variable as used for password/cipher is to be used as an argument for a Natural system function, assign the value to a user-defined variable, and use that variable as the argument. |
Action |
Check program and correct error. |
Text |
ON ERROR statement not allowed within condition. |
Explanation |
An ON ERROR statement must not be placed within any of the following statement blocks: - AT START/END OF DATA - AT TOP/END OF PAGE - AT BREAK - BEFORE BREAK PROCESSING - IF - IF NO RECORDS FOUND - AT END OF FILE - DEFINE SUBROUTINE |
Action |
Check program and correct error. |
Text |
DOEND missing for DO statement in line .... |
Explanation |
A statement block initiated with a DO statement must be terminated with a DOEND statement. |
Action |
Correct error in program. |
Text |
Inconsistent naming of fields in the data dictionary. |
Explanation |
The same field name was used twice in a database view definition in the data dictionary. |
Action |
Inform your Natural administrator, or use the LIST FILE command to check the view definition. |
Text |
Numeric edit mask specifies no valid positions in value. |
Explanation |
The specified numeric edit mask does not contain any positions which actually exist in the value to which the edit mask is applied. |
Action |
Check program and correct error. |
Text |
Maximum number/length of sort fields exceeded. |
Explanation |
Either the total length of the fields to be sorted was greater than 253, or the total number of fields to be sorted was greater than 10. |
Action |
Reduce the size of the sort criteria. |
Text |
AT BREAK required with PERFORM BREAK PROCESSING. |
Explanation |
After a PERFORM BREAK PROCESSING statement, no AT BREAK statement was issued. This error can also occur if the PERFORM BREAK PROCESSING is within an IF condition and the PERFORM BREAK PROCESSING and subsequent AT BREAK are not explicitly bounded by DO and DOEND statements. |
Action |
Check program and correct error. |
Text |
AT END OF DATA specified more than once for a loop. |
Explanation |
Only one AT END OF DATA statement is allowed per processing loop. |
Action |
Check program and correct error. |
Text |
The parameters LC and IC cannot be used together. |
Explanation |
The LC and IC characters are mutually exclusive. |
Action |
Check program and correct error. |
Text |
Alphanumeric edit mask may not be used for numeric value. |
Explanation |
The error may be caused by an incorrect definition of the edit mask in the data dictionary. |
Action |
Check program or data dictionary and correct edit mask specification. |
Text |
Text string for SCAN must be enclosed within apostrophes. |
Explanation |
The text string to be used for a SCAN operation must be enclosed within apostrophes, and it must be contained on a single source code line. |
Action |
Check program and correct error. |
Text |
Field to be examined must be a variable if it is modified. |
Explanation |
In an EXAMINE statement, the field to be examined must not be a constant if it is to be modified, that is, if a DELETE/REPLACE clause is used. This error also occurs if a constant is specified in an EXAMINE TRANSLATE statement; the field to be TRANSLATEd must be a variable. |
Action |
Correct error in program. |
Text |
Format/length of translate table must be A2, B2 or U2. |
Explanation |
The format/length of the translate table specified in the USING clause of an EXAMINE TRANSLATE statement must be A2, B2 or U2. |
Action |
Correct error in program. |
Text |
A database field with no active reference was used. |
Explanation |
A database field can be referenced only within an active processing loop. If the processing loop has been closed, reference to fields made available by the processing loop is no longer allowed. |
Action |
Ensure that all references to database fields are contained within an active processing loop. |
Text |
No specific heading allowed for group names in WRITE. |
Explanation |
If a group name is used in a WRITE (or INPUT) statement, no specific header text may be specified for the group. |
Action |
Check program and correct error. |
Text |
Invalid tab setting; occupied column overlaid. |
Explanation |
The tabulation 'nT' can only be used to position forward in a line. The tabulator notation must not position the new value over an already occupied output position. |
Action |
Check program and correct error. |
Text |
Repetition factor for text string > 250 or invalid. |
Explanation |
The repetition factor may be used to cause a one-character text string to be repeated. The repetition factor must be a numeric integer constant enclosed in parentheses. The maximum repetition factor allowed is 250. |
Action |
Check program and correct error. |
Text |
AT BREAK not possible in this type of processing loop. |
Explanation |
The AT BREAK statement may only be used in processing loops that are initiated by a FIND, READ, HISTOGRAM or SORT statement. User-initiated break processing can be done with the statement PERFORM BREAK PROCESSING. |
Action |
Check program and correct error. |
Text |
Only literal of one character can be used for repetition. |
Explanation |
A character string that is to be repeated using a repetition factor may consist of only one single character. |
Action |
Check program and correct error. |
Text |
WRITE TITLE/TRAILER is not allowed within condition. |
Explanation |
A WRITE TITLE or WRITE TRAILER statement must not be placed within any of the following statement blocks: - IF - AT START/END OF DATA - AT TOP/END OF PAGE - AT BREAK - BEFORE BREAK PROCESSING - AT END OF FILE - ON ERROR - IF NO RECORDS FOUND - DEFINE SUBROUTINE |
Action |
Place WRITE TITLE/WRITE TRAILER outside such a statement block. |
Text |
Edit mask definition error in data dictionary. |
Explanation |
The edit mask for a database field, as defined in the data dictionary, is incorrect. |
Action |
Contact your Natural administrator. A temporary by-pass may be to override the edit mask definition in the program. |
Text |
Data definition module (DDM) ... cannot be loaded. |
Explanation |
The data definition module (DDM) for the requested file cannot be loaded, because the internal DDM load buffer could not be allocated with a sufficient size. |
Action |
Start Natural in a larger thread/partition/region/task environment. |
Text |
SORT statement must not be placed within condition. |
Explanation |
The SORT statement closes all existing processing loops and initiates a new processing loop to process all records after they have been sorted. Therefore, the SORT statement cannot be placed within any of the following statement blocks: - AT START/END OF DATA - IF - AT TOP/END OF PAGE - IF NO RECORDS FOUND - AT BREAK - ON ERROR - BEFORE BREAK PROCESSING - DECIDE - AT END OF FILE |
Action |
Check program and correct error. |
Text |
AT TOP/END OF PAGE must not be placed within condition. |
Explanation |
The statements AT TOP OF PAGE and AT END OF PAGE can only be used outside the following statement blocks: - AT START/END OF DATA - AT TOP/END OF PAGE - AT BREAK - BEFORE BREAK PROCESSING - AT END OF FILE - IF - IF NO RECORDS FOUND - ON ERROR - DEFINE SUBROUTINE |
Action |
Place AT TOP/END OF PAGE outside such a statement block. |
Text |
Invalid parameter value in (SET) GLOBALS statement/command. |
Explanation |
The value for a parameter specified in a SET GLOBALS statement (or GLOBALS command) was invalid. Possible values for the parameter in question are 'ON' and 'OFF' (or 'T' and 'F' respectively). |
Action |
Check program and correct error. |
Text |
Too many vertical entries in one INPUT/WRITE/DISPLAY. |
Explanation |
One INPUT, WRITE or DISPLAY statement can generate a maximum of 250 lines vertically. The row value in the notation 'X/Y' must not exceed 250. The number of header lines must not exceed 14. |
Action |
Check program and correct error. |