Text |
Enter 'UC' (upper case) or 'LC' (lower case). |
Explanation |
'UC' indicates that input will be converted to upper case.
'LC' indicates that lower-case input will not be converted
to upper case. |
Action |
Enter a valid code ('UC' or 'LC'). |
Text |
Enter 'Y' (yes) or 'N' (no). |
Explanation |
The only possible values for this field are 'Y' (yes) and 'N' (no). |
Action |
Enter 'Y' or 'N'. |
Text |
Array dimension must be 0 to 3. |
Action |
Specify valid array dimension. |
Text |
Control character must be a special character. |
Explanation |
Only special characters may be used as the control character. The default control character is '.'. |
Action |
Enter a valid control character. |
Text |
Enter 'R' or 'L' for right- or left-justified. |
Explanation |
Only the following codes may be specified: R - Default justification of variable fields is right-justified. L - Default justification of variable fields is left-justified. |
Action |
Enter a valid code ('R' or 'L'). |
Text |
Delimiter settings are ambiguous. |
Explanation |
Either the same delimiter is defined more than once, or more than one delimiter is defined for the same class/attribute. |
Action |
Check the delimiter settings and correct error. |
Text |
Variable field has to be named. |
Explanation |
A field which is defined directly on the screen (i.e., not selected from a view) must be subsequently assigned the attributes of a view field (post assignment); or must be assigned a name directly, using the extended field editing function. |
Action |
Use either post assignment or extended field editing to assign a name to the field. |
Text |
Select either 'WRITE' or 'INPUT'. |
Explanation |
This error message may be caused by the following: - Neither WRITE nor INPUT has been marked. - Both WRITE and INPUT have been marked. |
Action |
Correct error. |
Text |
Dynamic layout contains user-defined variables. |
Explanation |
A map which is used as dynamic layout map must not contain user-defined variables. |
Action |
Delete the user-defined variables from the dynamic layout map, or use another map as dynamic layout map. |
Text |
Conflict between layout and map settings. |
Explanation |
This error message may be caused by one of the following: - The layout contains ATTRIBUTE/CLASS combinations in the delimiter settings which are not defined with the current map. - PAGESIZE or LINESIZE of layout and map are different. - COMP settings of layout and map are not identical. - KEYSTD settings of layout and map are not identical. - HELP names of both layout and map are not blank and are not identical. |
Action |
Check map and layout settings and correct error. |
Text |
Profile already exists. |
Explanation |
The ADD function was applied to a profile which already exists. |
Action |
Use the MODIFY function or use another profile name. |
Text |
Profile does not exist. |
Explanation |
The MODIFY or DELETE function was applied to a profile which does not exist. |
Action |
Use the correct profile name. |
Text |
Profile 'SYSPROF' must not be changed. |
Explanation |
It is not possible to change the default profile 'SYSPROF' with the maintenance function. |
Action |
Define a user profile by using the ADD function. |
Text |
Delimiter must differ from control and decimal character. |
Explanation |
A delimiter must not be the same character as the control character or the decimal character defined in the profile settings. |
Action |
Use another special character as the delimiter. |
Text |
'DY' option is invalid. |
Explanation |
The 'DY' option must consist of alternating escape characters
and attribute/color codes.
Valid escape characters are all special characters and
hexadecimal elements.
Examples: <i> (intensify by '<' )
<re> (red by '<' )
<bl:re> (blue by '<', red by ':' )
'27p'28 (protected by '27 ) |
Action |
Correct error. |
Text |
Warning: Conflict between current profile + map profile. |
Explanation |
The map to be edited was initialized with a profile other than the current profile. |
Action |
Press PF10 to obtain the correct profile name or ignore. |
Text |
Editing completed successfully. |
Explanation |
This message indicates: - In parameter mode, the prototype INPUT USING MAP statement was generated at the beginning of the map. - In non-parameter mode, all variables were checked to determine if they were assigned. - The validation rules were sorted by validation rank and by positions of the variables. |
Action |
No action required. |
Text |
Conflict between layout profile and enforced map profile. |
Explanation |
The layout map was initialized with a profile other than the current profile; the current profile is marked with the 'ENFORCE' option; and some attributes of the current profile have been changed in the meantime. |
Action |
Use another profile or another layout. |
Text |
Do not use help-text layout for map, or vice versa. |
Explanation |
This message may be caused by one of the following: - The layout was initialized with 'H' and the current map with 'I'. - The layout was initialized with 'I' and the current map with 'H'. |
Action |
Use another layout or the other initialization function. |
Text |
Print mode setting is incorrect. |
Explanation |
The following codes may be chosen for print mode: I - inversion of print direction C - alternate character set N - field will not appear in hardcopy D - double-byte character mode. Attribute combinations may be used. |
Action |
Correct error. |
Text |
Invalid modification of map settings. |
Explanation |
This error message may be caused if a class/attribute combination for delimiters was specified in the old map settings and is not specified in the new settings. |
Action |
Check settings and correct error. |
Text |
'Move' target is within command working range. |
Explanation |
A 'move' line command was issued for a block of lines and the cursor was positioned to a line within that block. |
Action |
Change cursor position or line range. |
Text |
An object with the same name already exists. |
Explanation |
During initialization of a map or a helptext, a name was specified which is already used by another object in the library. This error may also occur in the STOW or SAVE function, if a name is explicitly specified. |
Action |
Change map name or scratch existing object. |
Text |
Specified object does not exist, or is not a map/helptext. |
Explanation |
The specified map name is wrong. A map or a helptext with the specified name does not exist; or the referenced object is neither a map nor a helptext. |
Action |
Change map name or use initialize function. |
Text |
Device specification is missing. |
Explanation |
The device specified with the device check field was not defined using the maintenance function; or the MODIFY or DELETE function was used for a non-existing device specification. |
Action |
Specify the device attributes using the maintenance function. |
Text |
Device specification already exists. |
Explanation |
The specification of the device already exists. |
Action |
Use the MODIFY function. |
Text |
Device name is missing. |
Explanation |
The name of the device specification to be added, modified or deleted is missing. |
Action |
Enter a device name. |
Text |
Attribute does not match device characteristics. |
Explanation |
The device check was enabled by entering a device name which does not support the defined attributes. The cursor is positioned to the attribute which is in conflict with the specified device. |
Action |
Change attribute or disable device check. |
Text |
Layout does not exist. |
Explanation |
A layout map or a layout help text was specified in the map settings or the profile, but the layout does not exist as a source map. |
Action |
Correct error. |
Text |
Only 'H' or 'V' possible. |
Explanation |
The direction of the secondary index can only be horizontal (H) or vertical (V). |
Action |
Enter valid direction. |
Text |
Only output class possible with 'WRITE'. |
Explanation |
A delimiter or an AD attribute was specified with a field class equal to input (A) or modify (M). This is not possible if a WRITE statement is to be generated as a result of the map definition process. |
Action |
Check program or map settings, and correct error. |
Text |
Conflict in array dimensions. |
Explanation |
A DDM array was post-assigned to an array and one or more dimensions of the DDM array are smaller than the predefined array. |
Action |
Check array dimensions and correct error. |
Text |
Attribute control variable is missing. |
Explanation |
A delimiter with attribute 'Y' was used, but no attribute control variable (CV=name) was defined in the map settings. An AD attribute 'Y' was defined, but no attribute control variable (CV=name) was defined at the field level or in the map settings. |
Action |
Define the attribute control variable. |
Text |
Validation rule priority already exists. |
Explanation |
An attempt was made to change the priority of a validation rule, but a validation rule for this field with the specified priority already exists. |
Action |
Use another priority. |
Text |
Field is not an array. |
Explanation |
Before applying index parentheses to a field name, the field must be defined as an array by using the command '.A' or '..A'. |
Action |
Remove index parentheses. |
Text |
Do not apply '.A' command to a scalar value. |
Explanation |
The array field command or the array line command cannot be used with elementary database fields or with system variables. Validation rules are not allowed for system variables. |
Action |
Do not use an array, or define a user-defined variable. |
Text |
Helproutine for a helptext or WRITE map is not allowed. |
Explanation |
A helproutine name may only be specified with maps, not with helptexts. If the map is to be used in a WRITE USING MAP statement, a helproutine name must not be specified. |
Action |
Correct error. |
Text |
STOW command executed successfully. |
Explanation |
The map was successfully saved and cataloged. |
Action |
No action required. |
Text |
Direct command was executed. |
Explanation |
The specified direct command was executed successfully. |
Action |
No action required. |
Text |
Invalid edit mask. |
Explanation |
The specified edit mask is not a valid Natural edit mask. For information on valid edit masks, you may invoke the help facility. |
Action |
Use valid edit mask. |
Text |
Decimal character conflict. |
Explanation |
The map uses a decimal character which is in conflict with the decimal character defined for the current session. |
Action |
Change session profile, using GLOBALS command. |
Text |
Feature not available. |
Explanation |
The desired feature is only available if the Predict dictionary system is installed. |
Action |
Do not use this feature. |
Text |
Conflict between processing rules. |
Explanation |
This error occurs if a field was first defined as a user-defined or or undefined field, and processing rules were assigned to that field by the user; if this field is then post-assigned to a database field, and the dictionary contains processing rules for that database field on ranks which are already occupied by the user-defined rules, this conflict occurs. |
Action |
Check user rules. |
Text |
Consistency error in dictionary. |
Explanation |
During definition or retrieval of processing rules, a consistency error within the dictionary's processing rules was discovered. |
Action |
Contact your dictionary administrator. |
Text |
Processing rule already exists. |
Explanation |
The name specified for the processing rule which is to be added to the dictionary already exits. |
Action |
Use another name for the processing rule. |
Text |
Specification of prefix not allowed here. |
Explanation |
A new prefix may not be introduced with extended field editing. Existing prefixes may only be changed to correspond with program labels. |
Action |
Use the post-assign facility to specify new prefixes. |
Text |
Page size must be 3 - 250. |
Explanation |
If Standard Keys are set to Y, the minimum page size is 3. |
Action |
Specify correct page size. |
Text |
Modification rejected by user exit. |
Explanation |
User exit activated in Predict DDA services. |
Action |
Please contact your DBA to allow the modification of free rules. |
Text |
Number of occurrences has to be greater than zero. |
Action |
Set number of occurrences to a value greater than '0'. |
Text |
DDM does not exist, or you are not allowed to access it. |
Explanation |
The specified DDM does not exist or is protected by Natural Security. The DDM can also be used in the data area of a program and the program is included in the map editor. |
Action |
Enter valid DDM name or check program; or contact your Natural Security administrator. |