Version 6.3.8 for OpenVMS
 —  Messages and Codes  —

Natural System Error Messages 4651-4700

NAT4651: Enter "UC" (upper case) or "LC" (lower case).

Text Enter "UC" (upper case) or "LC" (lower case).
Expl. "UC" indicates that input will be converted to upper case.
"LC" indicates that lower-case input will not be converted
to upper case.
Actn. Enter a valid code ("UC" or "LC").

NAT4652: Enter "Y" (yes) or "N" (no).

Text Enter "Y" (yes) or "N" (no).
Expl. The only possible values for this field are "Y" (yes) and "N" (no).
Actn. Enter "Y" or "N".

NAT4653: Array dimension must be 0 to 3.

Text Array dimension must be 0 to 3.
Actn. Specify valid array dimension.

NAT4654: Control character must be a special character.

Text Control character must be a special character.
Expl. Only special characters may be used as the control character.
The default control character is ".".
Actn. Enter a valid control character.

NAT4655: Enter "R" or "L" for right- or left-justified.

Text Enter "R" or "L" for right- or left-justified.
Expl. 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.
Actn. Enter a valid code ("R" or "L").

NAT4656: Delimiter settings are ambiguous.

Text Delimiter settings are ambiguous.
Expl. Either the same delimiter is defined more than once,
or more than one delimiter is defined for the same class/attribute.
Actn. Check the delimiter settings and correct error.

NAT4657: Variable field has to be named.

Text Variable field has to be named.
Expl. 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.
Actn. Use either post assignment or extended field editing to
assign a name to the field.

NAT4658: Select either "WRITE" or "INPUT".

Text Select either "WRITE" or "INPUT".
Expl. This error message may be caused by the following:
- Neither WRITE nor INPUT has been marked.
- Both WRITE and INPUT have been marked.
Actn. Correct error.

NAT4659: Dynamic layout contains user-defined variables.

Text Dynamic layout contains user-defined variables.
Expl. A map which is used as dynamic layout map must not contain
user-defined variables.
Actn. Delete the user-defined variables from the dynamic layout map,
or use another map as dynamic layout map.

NAT4660: Conflict between layout and map settings.

Text Conflict between layout and map settings.
Expl. 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.
Actn. Check map and layout settings and correct error.

NAT4661: Profile already exists.

Text Profile already exists.
Expl. The ADD function was applied to a profile which already exists.
Actn. Use the MODIFY function or use another profile name.

NAT4662: Profile does not exist.

Text Profile does not exist.
Expl. The MODIFY or DELETE function was applied to a profile which does not
exist.
Actn. Use the correct profile name.

NAT4663: Profile "SYSPROF" must not be changed.

Text Profile "SYSPROF" must not be changed.
Expl. It is not possible to change the default profile "SYSPROF" with the
maintenance function.
Actn. Define a user profile by using the ADD function.

NAT4664: Delimiter must differ from control and decimal character.

Text Delimiter must differ from control and decimal character.
Expl. A delimiter must not be the same character as the control character
or the decimal character defined in the profile settings.
Actn. Use another special character as the delimiter.

NAT4665: "DY" option is invalid.

Text "DY" option is invalid.
Expl. 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 )
Actn. Correct error.

NAT4666: Warning: Conflict between current profile + map profile.

Text Warning: Conflict between current profile + map profile.
Expl. The map to be edited was initialized with a profile other
than the current profile.
Actn. Press PF10 to obtain the correct profile name or ignore.

NAT4667: Editing completed successfully.

Text Editing completed successfully.
Expl. 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.
Actn. No action required.

NAT4668: Conflict between layout profile and enforced map profile.

Text Conflict between layout profile and enforced map profile.
Expl. 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.
Actn. Use another profile or another layout.

NAT4669: Do not use help-text layout for map, or vice versa.

Text Do not use help-text layout for map, or vice versa.
Expl. 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".
Actn. Use another layout or the other initialization function.

NAT4670: Print mode setting is incorrect.

Text Print mode setting is incorrect.
Expl. 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.
Actn. Correct error.

NAT4671: Invalid modification of map settings.

Text Invalid modification of map settings.
Expl. 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.
Actn. Check settings and correct error.

NAT4672: "Move" target is within command working range.

Text "Move" target is within command working range.
Expl. A "move" line command was issued for a block of lines
and the cursor was positioned to a line within that block.
Actn. Change cursor position or line range.

NAT4673: An object with the same name already exists.

Text An object with the same name already exists.
Expl. 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.
Actn. Change map name or scratch existing object.

NAT4674: Specified object does not exist, or is not a map/helptext.

Text Specified object does not exist, or is not a map/helptext.
Expl. 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.
Actn. Change map name or use initialize function.

NAT4675: Device specification is missing.

Text Device specification is missing.
Expl. 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.
Actn. Specify the device attributes using the maintenance function.

NAT4676: Device specification already exists.

Text Device specification already exists.
Expl. The specification of the device already exists.
Actn. Use the MODIFY function.

NAT4677: Device name is missing.

Text Device name is missing.
Expl. The name of the device specification to be added, modified or
deleted is missing.
Actn. Enter a device name.

NAT4678: Attribute does not match device characteristics.

Text Attribute does not match device characteristics.
Expl. 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.
Actn. Change attribute or disable device check.

NAT4679: Layout does not exist.

Text Layout does not exist.
Expl. 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.
Actn. Correct error.

NAT4680: Only "H" or "V" possible.

Text Only "H" or "V" possible.
Expl. The direction of the secondary index can only be
horizontal (H) or vertical (V).
Actn. Enter valid direction.

NAT4681: Only output class possible with "WRITE".

Text Only output class possible with "WRITE".
Expl. 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.
Actn. Check program or map settings, and correct error.

NAT4682: Conflict in array dimensions.

Text Conflict in array dimensions.
Expl. A DDM array was post-assigned to an array and one or more dimensions
of the DDM array are smaller than the predefined array.
Actn. Check array dimensions and correct error.

NAT4683: Attribute control variable is missing.

Text Attribute control variable is missing.
Expl. 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.
Actn. Define the attribute control variable.

NAT4684: Validation rule priority already exists.

Text Validation rule priority already exists.
Expl. 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.
Actn. Use another priority.

NAT4685: Field is not an array.

Text Field is not an array.
Expl. Before applying index parentheses to a field name, the field must be
defined as an array by using the command ".A" or "..A".
Actn. Remove index parentheses.

NAT4686: Do not apply ".A" command to a scalar value.

Text Do not apply ".A" command to a scalar value.
Expl. 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.
Actn. Do not use an array, or define a user-defined variable.

NAT4687: Helproutine for a helptext or WRITE map is not allowed.

Text Helproutine for a helptext or WRITE map is not allowed.
Expl. 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.
Actn. Correct error.

NAT4688: STOW command executed successfully.

Text STOW command executed successfully.
Expl. The map was successfully saved and cataloged.
Actn. No action required.

NAT4689: Direct command was executed.

Text Direct command was executed.
Expl. The specified direct command was executed successfully.
Actn. No action required.

NAT4690: Invalid edit mask.

Text Invalid edit mask.
Expl. The specified edit mask is not a valid Natural edit mask.
For information on valid edit masks, you may invoke the help facility.
Actn. Use valid edit mask.

NAT4691: Decimal character conflict.

Text Decimal character conflict.
Expl. The map uses a decimal character which is in conflict
with the decimal character defined for the current session.
Actn. Change session profile, using GLOBALS command.

NAT4692: Feature not available.

Text Feature not available.
Expl. The desired feature is only available if
the Predict dictionary system is installed.
Actn. Do not use this feature.

NAT4693: Conflict between processing rules.

Text Conflict between processing rules.
Expl. 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.
Actn. Check user rules.

NAT4694: Consistency error in dictionary.

Text Consistency error in dictionary.
Expl. During definition or retrieval of processing rules, a consistency
error within the dictionary"s processing rules was discovered.
Actn. Contact your dictionary administrator.

NAT4695: Processing rule already exists.

Text Processing rule already exists.
Expl. The name specified for the processing rule which is to be added to the
dictionary already exits.
Actn. Use another name for the processing rule.

NAT4696: Specification of prefix not allowed here.

Text Specification of prefix not allowed here.
Expl. A new prefix may not be introduced with extended field editing.
Existing prefixes may only be changed to correspond with program labels.
Actn. Use the post-assign facility to specify new prefixes.

NAT4697: Page size must be 3 - 250.

Text Page size must be 3 - 250.
Expl. If Standard Keys are set to Y, the minimum page size is 3.
Actn. Specify correct page size.

NAT4698: Modification rejected by user exit.

Text Modification rejected by user exit.
Expl. User exit activated in Predict DDA services.
Actn. Please contact your DBA to allow the modification of free rules.

NAT4699: Number of occurrences has to be greater than zero.

Text Number of occurrences has to be greater than zero.
Actn. Set number of occurrences to a value greater than "0".

NAT4700: DDM does not exist, or you are not allowed to access it.

Text DDM does not exist, or you are not allowed to access it.
Expl. 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.
Actn. Enter valid DDM name or check program;
or contact your Natural Security administrator.

Top of page