Natural System Error Messages 0700-0749

NAT0700: Keyword "SET" missing or invalid range-variable specified.

Text
Keyword "SET" missing or invalid range-variable specified.
Explanation
In the SQL UPDATE statement after the table specification, either
the keyword "SET" is missing, or the range-variable is incorrect.
Action
Correct error in program.

NAT0701: Invalid assignment clause in SQL UPDATE statement.

Text
Invalid assignment clause in SQL UPDATE statement.
Explanation
The specified column does not exist in the referenced table that is
to be updated; or the equal sign (=) after the column specification
is missing; or the scalar-expression after the equal sign contains
an error.
Action
Correct error in program.

NAT0702: With a view, only "SET *" is allowed in SQL UPDATE.

Text
With a view, only "SET *" is allowed in SQL UPDATE.
Explanation
When a view is referenced in an SQL UPDATE statement,
"SET *" must be specified; an explicit assignment list is
only allowed and required when a DDM is referenced in the
SQL UPDATE statement.
Action
Correct error in program.

NAT0703: Invalid range-variable specified in SQL INSERT/DELETE.

Text
Invalid range-variable specified in SQL INSERT/DELETE.
Explanation
In an SQL INSERT or SQL DELETE statement, an invalid range-variable
(identifier) has been specified after the DDM (table) name.
Action
Correct error in program.

NAT0704: Opening or closing parenthesis missing in INSERT.

Text
Opening or closing parenthesis missing in INSERT.
Explanation
In an INSERT statement, either the list of field names or
the list of values is not correctly enclosed in parentheses.
Action
Correct error in program.

NAT0705: Field to be INSERTed is not in specified DDM/table.

Text
Field to be INSERTed is not in specified DDM/table.
Explanation
The field specified in the column list of the INSERT statement
does not exist in the referenced DDM/table.
Action
Correct error in program.

NAT0706: Invalid value specified in VALUES clause of INSERT.

Text
Invalid value specified in VALUES clause of INSERT.
Explanation
Values specified in the VALUES clause of an INSERT statement must
be one of the following:
- the keyword "NULL" (to assign a null value);
- a special register (USER, CURRENT TIMEZONE, CURRENT DATE,
                     CURRENT TIME, CURRENT TIMESTAMP);
- a constant or a user-defined variable.
Action
Correct error in program.

NAT0708: VALUES clause missing or invalid SELECT clause specified.

Text
VALUES clause missing or invalid SELECT clause specified.
Explanation
In an INSERT statement, either a valid VALUES clause or a
valid SELECT clause must be specified.
Action
Correct error in program.

NAT0709: Incorrect usage of index range field.

Text
Incorrect usage of index range field.
Explanation
1) When an array range is used as a parameter in an
   SQL statement (e.g. SELECT, INSERT), the Natural
   array property DYNAMIC is not supported.
2) The data type of a field specified with an index range
   must be alphanumeric or binary, unless COMPOPT DB2ARRY=ON
   has been set.
3) Arrays must be one-dimensional. That is, arrays that are
   defined in DEFINE DATA as (A10/1:3;1:5) are not permitted.
4) Variable index ranges, such as (1:I), are not permitted.
Action
Check syntax and correct error.

NAT0710: The CLSID was not found in the registry (DCOM code :1:).

Text
The CLSID was not found in the registry (DCOM code ...).
Explanation
The CLSID associated with the given class name was not found
in the registry.
Action
Make sure that  the class name used in the CREATE OBJECT statement
is correctly registered.

NAT0711: The object could not be created (DCOM code :1:).

Text
The object could not be created (DCOM code ...).
Explanation
The object of the class specified in the CREATE OBJECT statement
could not be created. Common reasons are:
1) The class is not correctly registered.
2) You are not authorized to create the object.
3) The specified node does not exist or could not be reached.
Action
Check if one of the above conditions applies.

NAT0712: A library name must be specified for Natural Security.

Text
A library name must be specified for Natural Security.
Explanation
If Natural Security is installed, the system commands REGISTER and
UNREGISTER can only be used for a single library. Therefore the
library name must not be "*".
The library name can be omitted when applying the commands to all
classes of the current logon library. If the commands are to be
applied to classes in another library, the name of this library has
to be specified.
Action
Either omit the library name or enter the name of an existing library.

NAT0714: Internal error (DCOM code :1:).

Text
Internal error (DCOM code ...).
Explanation
An internal error occurred because of one of the following reasons:
1) A string could not be converted from Ansi to Unicode.
2) An automation interface function failed to execute.
3) The default dispatch interface was not returned during
   object creation.
4) Analyzing the type information failed.
5) A dispatch interface could not be retrieved.
Action
Check if the used class is correctly registered.

NAT0715: Registry entry could not be changed.

Text
Registry entry could not be changed.
Explanation
Natural could not change or create entries in the system registry
which are needed to register the DCOM class.
Action
Check, if you have permission to change the system registry.
If this is not the case, you cannot register classes.

NAT0716: Registry entry could not be deleted.

Text
Registry entry could not be deleted.
Explanation
Natural could not delete entries in the system registry
which are no longer needed when the DCOM class is unregistered.
1. Check if you have permission to delete entries from the
   system registry. If this is not the case, you cannot
   unregister classes.
2. Check if the CLSID of the class to be unregistered
   was changed after registering the class. In this case it is not
   possible to find the class in the registry.
Action
See explanation.

NAT0717: Registry entry could not be read.

Text
Registry entry could not be read.
Explanation
Natural could not read entries in the system registry,
which is needed to register/unregister the DCOM class.
Action
Check, if you have permission to read the system registry.
If this is not the case, you cannot register/unregister the DCOM class.

NAT0718: Internal error during registration.

Text
Internal error during registration.
Explanation
Internal error during registration.
Action
Unregister the class first and try to register it again.

NAT0719: Registration files could not be created correctly.

Text
Registration files could not be created correctly.
Explanation
It was not possible to create the server and client
registration files (.reg) for the class.
Action
Check, if you have permission to create these files.

NAT0720: DCOM server message: :1:.

Text
DCOM server message: ....
Explanation
The DCOM server, which was called by the Natural client,
returns the message displayed above.
Action
None.

NAT0721: INCDIR error: :1:.

Text
INCDIR error: ....
Explanation
This message appears only if compiler option CHKRULE=ON is set.
During compilation, the DDM and field names referenced in INCDIR
statements are checked for existence. If either the DDM or the field
cannot be found, this message is issued.
INCDIR statements are automatically created if a database field is
included in a map. When the map is catalogued, these instructions will
effect an automatic incorporation of processing rules which might
exist for this field on Predict.
Action
1) Deactivate the message with CHKRULE=OFF.
2) Correct the DDM/field name in the INCDIR statement.

NAT0723: Interactive I/O not possible in server environment.

Text
Interactive I/O not possible in server environment.
Explanation
An attempt was made to execute an interactive I/O
(I/O to report 0), while Natural is acting as a server.
Action
Check and correct the program. Input data for the Natural INPUT
statement may be supplied via the Natural stack. Any output to
report 0 may be redirected using the MAINPR parameter.

NAT0724: Invalid object handle used.

Text
Invalid object handle used.
Explanation
An object handle can only be used after the object has been
created with a CREATE OBJECT statement, or after a valid handle
has been assigned to it.
Action
Make sure that the object has been successfully created before
it is used in a SEND METHOD statement or property access.

NAT0725: Invalid placement of :1: statement.

Text
Invalid placement of ... statement.
Explanation
An invalid statement has been specified in the current Natural object.
Possible reasons are, for example:
1. A DEFINE CLASS statement may only be specified in a
   Natural class object and only specified once per class object.
2. The first statement of a Natural function object must be
   DEFINE FUNCTION ... END-FUNCTION.
3. An END statement must not be used in a copycode object.
Action
Check the placement of the statement or check the object type.

NAT0726: Invalid :1: name specified.

Text
Invalid ... name specified.
Explanation
In a DEFINE CLASS statement the following rules apply to various names:
1. The class, interface, property or method name must not have more
   than 32 characters.
2. The class name may contain periods. Each identifier separated by a
   period must conform to the naming conventions for user-defined
   variables.
3. Interface, property or method names must conform to the naming
   conventions for user-defined variables.
   The interface name must not be identical to the class name.
4. The copy code or subprogram name must not have more than 8
   characters.
Action
Check the name and correct error.

NAT0727: :1: name is not defined.

Text
... name is not defined.
Explanation
In a PROPERTY statement
- the interface is not defined or
- the property name is not defined for the interface specified.
In a METHOD statement
- the interface name is not defined or
- the method name is not defined for the interface specified.
Concerning Natural functions
 - there is no return value defined in the RETURNS clause inside
  the function prototype.
Action
Check the name and correct the error.

NAT0728: Keyword :1: expected.

Text
Keyword ... expected.
Explanation
The appropriate keyword is expected.
Action
Check the keyword and correct error.

NAT0729: :1: name already defined.

Text
... name already defined.
Explanation
The interface name is not unique in the specified class or
the property or method name is not unique for the specified interface.
Action
Check the name and correct error.

NAT0730: Property and assigned object var. not data-transfer compatible.

Text
Property and assigned object var. not data-transfer compatible.
Explanation
The format/length specifications of the property and the assigned object
variable are not data-transfer compatible.
If the attribute READONLY is specified, the rule for data transfer
of the object variable as sending field and the property as receiving
field apply. Otherwise the data transfer rules for the property
and the assigned object variable as sending and receiving fields apply.
Action
Check the format/length specifications and correct error.

NAT0731: No object variable assigned to property :1:.

Text
No object variable assigned to property ....
Explanation
No object variable is assigned to the property.
Action
Assign an object variable to the property.

NAT0732: Invalid globally unique ID specified.

Text
Invalid globally unique ID specified.
Explanation
The specified value is not a valid globally unique ID.
Action
Check the value of the valid globally unique ID and correct error.

NAT0733: The type information of class :1: could not be retrieved :2:

Text
The type information of class :1: could not be retrieved :2:
Explanation
In certain situations Natural needs type information about a
class to use it. The type information for the class could not
be found. A common reason is that the class is not correctly
registered on the server side.
Action
Make sure that the class is correctly registered and type
information exists.

NAT0735: The method or property :1: was not found (DCOM code :2:).

Text
The method or property :1: was not found (DCOM code :2:).
Explanation
The specified method or property was not found in any of the
object"s interfaces.
Action
Check the specified interface name (if any), the method or the
property name.

NAT0736: The Natural object of class :1: could not be created.

Text
The Natural object of class ... could not be created.
Explanation
With the class name specified in the CREATE OBJECT statement it
was not possible to create the object. A possible reason is that
the corresponding Natural class module was not found at the place
where it was registered.
Action
Check the class name used in the CREATE OBJECT statement and check
if the corresponding Natural class module is available.

NAT0737: The method or property :1: was not found.

Text
The method or property :1: was not found.
Explanation
The specified method or property was not found in any of the
object"s interfaces.
Action
Check the specified interface name (if any), the method or the
property name.

NAT0738: A class named :1: already exists as member :2:.

Text
A class named ... already exists as member ....
Explanation
You have used a class name which already exists in another
class module. Class names within a library must be unique.
Action
Change the class name.

NAT0739: READONLY property :1: must not be modified.

Text
READONLY property ... must not be modified.
Explanation
If a property is declared as read-only, it must not be modified.
Action
Correct error in program.

NAT0740: Invalid dispatch ID of :1: :2: in interface :3:.

Text
Invalid dispatch ID of ... ... in interface ....
Explanation
Methods and properties of classes have numeric identifiers,
called dispatch IDs, assigned. Normally these IDs
are assigned internally and automatically by Natural. If you
explicitly assign an ID to a method or property using the ID
clause, you have to assign the numbers uniquely
per interface. Dispatch IDs must be positive integer values.
Action
Assign a different ID to ensure uniqueness and correct format,
or do not assign an ID at all.

NAT0741: No globally unique ID defined for interface :1: of class :2:.

Text
No globally unique ID defined for interface ... of class ....
Explanation
The globally unique ID for the given interface is missing in the
Natural class definition. The ID is needed to enter information
for this interface in the registry.
Action
Define a globally unique ID for the interface.

NAT0742: Type Library creation for class :1: failed.

Text
Type Library creation for class ... failed.
Explanation
The type library (.TLB) which is created during registration
of a Natural class in the Natural etc directory could not
be created. A possible reason is that a type library for the given
class already exists and has been opened by another tool. So Natural
cannot modify it.
Action
Check, if the type library is being used by another tool.

NAT0743: No registry information entered for :1:.

Text
No registry information entered for ....
Explanation
If a Natural class is to be accessible with DCOM, it
must be entered in the registry. If the class is to be
used only locally in Natural, this is not necessary.
Action
If you do not want to use the class with DCOM, you can ignore this
error message. Otherwise, define a valid ID for the class and define at
least one interface for the class.

NAT0744: Conflicting number of parameters in SEND METHOD.

Text
Conflicting number of parameters in SEND METHOD.
Explanation
The number of parameters which are specified with the SEND METHOD
statement must be identical to both:
  - the number of parameters, that are defined in the method,
  - the number of parameters, that are declared in the
    method declaration of the DEFINE CLASS statement.
Action
Check the parameter definitions in the class module, in the method
and the parameters in the SEND METHOD statement.

NAT0745: Error during conversion of parameter :1: in SEND METHOD.

Text
Error during conversion of parameter ... in SEND METHOD.
Explanation
The parameter could not be converted to an appropriate
VARIANT format, or the VARIANT format returned from the
server could not be converted to an appropriate Natural format.
Some possible reasons are:
- A Natural variable of format "C" cannot be passed
  as a method parameter.
- Arrays passed as arguments must match the corresponding
  method parameter in number of dimensions and number of
  occurrences per dimension.
Action
Consult the data conversion rules in the NaturalX documentation.

NAT0746: Class name :1: already defined in the registry.

Text
Class name ... already defined in the registry.
Explanation
The class cannot be registered, because a class with the same
name but a different CLSID has been found in the system registry.
Action
Change the class name so that it is unique.

NAT0747: No classes are registered under server ID :1:.

Text
No classes are registered under server ID ....
Explanation
The UNREGISTER command was used to unregister all classes that are
registered under a given server ID, or under the current server ID.
Currently there are no classes registered under this server ID.
Action
None.

NAT0748: Error during conversion of property value or return value.

Text
Error during conversion of property value or return value.
Explanation
The property value or return value could not be converted
to an appropriate VARIANT format, or the VARIANT format passed
back from the server could not be converted to an appropriate
Natural format.
Some possible reasons are:
- A Natural variable of format "C" cannot be passed
  as property value or received as return value.
- Arrays passed as property value or received as return value
  must match the corresponding property or return parameter
  in number of dimensions and number of occurrences per dimension.
Action
Consult the data conversion rules in the NaturalX documentation.