Natural System Error Messages 6950-6999

NAT6950: Library could not be dynamically loaded.

Text
Library could not be dynamically loaded.
Explanation
A library required at run time could not be found or could not be
loaded.
Check system search path for dynamically loaded libraries. Has this been
changed in any way since Natural was installed? If not, it could be that
you are trying to access a component which was not installed.
If this is also not the case, contact SAG support.
Action
see explanation

NAT6951: Procedure in dynamically loaded library could not be found.

Text
Procedure in dynamically loaded library could not be found.
Explanation
A procedure required at run time could not be found in a dynamically
loaded library.
Action
Check system search path for dynamically loaded libraries. In
particular, check that the system is not loading any libraries from a
different Natural version to the one which is currently running.

NAT6952: Natural Reporter function did not complete successfully.

Text
Natural Reporter function did not complete successfully.
Explanation
The Natural Reporter failed to carry out the requested function
successfully.
Check the documentation to ensure that the requested function is being
used correctly. Can the series of operations being performed by the
program be carried out successfully by hand from within the Reporter
when used standalone? If so, has OLE been installed correctly? If the
cause of the problem still cannot be found, contact Software AG support.
Action
see explanation

NAT6953: Natural/Reporter Interface not initialized.

Text
Natural/Reporter Interface not initialized.
Explanation
An attempt was made to call a Natural/Reporter interface function
without first initializing the interface. Either no initializing
call has been made, or a call to terminate the interface has been
performed, in which case the interface needs to be re-initialized.
Note that it is only necessary to initialize and terminate the
Natural/Reporter interface once per Natural session.
Action
Modify program to include a statement to (re-)initialize the
Natural/Reporter interface.

NAT6954: Requested report could not be found.

Text
Requested report could not be found.
Explanation
If the report is specified by name (i.e., an OPEN request), the
specified report could not be located in the file system. Otherwise,
the specified report ID is not valid.
Check that the report name contains no path or file extension
information, is not longer than 8 characters, and exists in the
NATGUI̲BMP path as specified in the SAG.INI file. Or check that the
report ID corresponds to a valid ID, as returned by a previous OPEN
(for example, check the response code from the OPEN to verify that
the report was opened correctly). Confirm that no CLOSE request has
been issued against this report in the meantime!
Action
see explanation

NAT6955: Too many active reports.

Text
Too many active reports.
Explanation
The maximum number of reports concurrently maintainable by the
Natural/Reporter Interface has been reached.
Action
Modify program to issue a CLOSE request for each report as soon as it
is no longer needed, or if it will probably not be used again for a
significant length of time.

NAT6956: Invalid parameter(s).

Text
Invalid parameter(s).
Explanation
This error can have various causes:
   - the number of parameters supplied is incorrect
   - one or more mandatory parameters were not supplied
   - one or more parameters were specified with an incorrect format
     and/or length
Action
Check the parameters used in the program against the documentation.

NAT6957: Invalid print device.

Text
Invalid print device.
Explanation
Either the specified printer has not been set up in the Configuration
utility, or it is not associated with the TTY print method.
Action
Check the printer settings in the Configuration Utility ->
Global Configuration File -> Printer Profiles.

NAT6958: Invalid work file.

Text
Invalid work file.
Explanation
Either the specified work file has not been set up (statically in
the Configuration utility or dynamically via DEFINE WORK FILE), or the
file does not exist, or it is not a Natural CONNECTION (*.NCD) work
file.
Action
Check the work file name against the above criteria.

NAT6959: Failed to save resources to private resource file.

Text
Failed to save resources to private resource file.
Explanation
Along with the dialog source, resources needed to be saved. This action
failed.
Possible reasons:
- Problems to access the current library
- Problems accessing/creating the resource directory in the
  current library
- Problems writing/appending to the private resource file
- Problems executing dynamic functions
- Memory problems
Action
Check the subdirectories of the library the dialog was saved in. If you
cannot solve the problem there, contact Software AG support.

NAT6960: Unable to import (private) resource :1: into library :2:.

Text
Unable to import (private) resource ... into library ....
Explanation
The importing of a resource failed. If the resource is a private
resource, the corresponding object to which the private resource belongs
must be present in the library and its type must be the same as
the type of the private resource.
Action
Resolve the type conflict by either importing the appropriate resource
and/or  by  first replacing the corresponding Natural object in the
target library. If in doubt, contact Software AG support.

NAT6970: Natural RPC initialization failed. RPC not available.

Text
Natural RPC initialization failed. RPC not available.
Explanation
This error message is preceded by an initialization error message.
On the client side, the following features are not available:
- execution of a remote CALLNAT,
- SYSRPC functions SM, XC and PM,
- local use of conversations and context variables.
On the server side, the termination of the Natural RPC server session
is enforced by an implicit ITERM=ON.
Action
Check the previous initialization error.

NAT6971: Connection error on :1:, reason :2: :3:.

Text
Connection error on ..., reason ... ....
Explanation
Reason: 1: No transport layer.
        2: Connection timed out.
        3: Conversation timed out.
        4: No space for working storage of broker stub.
           Increase Natural thread or region size by 35 KB.
        5: Data have been truncated. Increase MAXBUFF on server side.
        6: Location transparency no longer supported.
        7: Node not active.
        8: Server not active.
        9: Error from transport layer; issue RPCERR for details.
After the reason, the message displays the server/node in question.
With AUTORPC=ON this error may also occur instead of a local NAT0082
error on the client side.
Action
Proceed depending on above reason.

NAT6972: Directory error on :1:, reason :2: :3:.

Text
Directory error on ..., reason ... ....
Explanation
A directory error has occurred. Possible reasons are:
1 - No directory.
2 - Invalid directory.
3 - No space to load directory. Increase the RPC size.
4 - No server found in service directory for the subprogram/library
    whose names are indicated in the error message.
5 - Recursive RPC with the two subprograms whose names are
    indicated in the error message.
6 - A Natural error has occurred during loading of NATCLTGS.
    The error number is indicated in the error message.
With AUTORPC=ON this error may also occur instead of a local NAT0082
error on the client side.
Action
Proceed depending on above reason.

NAT6973: Conversation error on :1:, reason :2: :3:.

Text
Conversation error on ..., reason ... ....
Explanation
Reason: 1: Too many subprograms for OPEN CONVERSATION.
        2: Invalid subprogram name.
        3: RPC size overflow. Increase RPC size.
        4: Mixed local/remote CALLNAT within one conversation (program).
           It is not possible to execute subprograms that are members
           of one conversation partially remote and local.
        5: Recursive conversation. It is not possible to execute a
           subprogram that is a member of a conversation while you
           are executing a subprogram within that conversation.
        6: Conversation to be closed not found.
        7: Conversation ID to be closed is not valid.
        8: CLOSE CONVERSATION executed inside a local conversation.
           It is not possible to close a conversation while you are
           executing a subprogram within that conversation.
Action
           executing a subprogram within that conversation.
Proceed depending on above reason.

NAT6974: Conversion error on :1:, reason :2: :3:.

Text
Conversion error on :1:, reason :2: :3:.
Explanation
Reason: 1: Variables of type CONTROL and HANDLE and extensible lower
           bounds in X-arrays not supported.
        2: Error converting to external format of parameter :3:.
        3: Error converting to internal format of parameter :3:.
        4: No space for conversion to internal format of parameter :3:.
           Increase MAXBUFF on :1: side.
        5: No space for conversion to external format of parameter :3:.
           Increase MAXBUFF on :1: side.
        6: Format buffer error for parameter :3:.
        7: No space. Increase region/thread size (MF) or USIZE (LUW).
        8: No MAXBUFF defined on client side, but RPC is used.
       10: AD=M (inout) or AD=A (in) parameter used with reliable RPC.
       11: The used interface object does not support reliable RPC.
           Regenerate interface object with latest Natural version.
Action
           Regenerate interface object with latest Natural version.
Proceed depending on above reason.

NAT6975: Security error on :1:, reason :2: :3:.

Text
Security error on ..., reason ... ....
Explanation
Reason: 1: Logon data required by the Natural RPC server.
        2: Invalid logon data received by the Natural RPC server.
           After the reason, diagnostic information is indicated
           in the message.
        3: Invalid offset to the logon data in the RPC meta data.
        4: Impersonation failed for the user indicated in the message.
           The external security system has rejected the logon attempt
           of the user. The reason is shown in the Natural RPC server
           trace and in the system log of the server.
Action
Reason: 1:   Pass logon data from the client to the Natural RPC server.
        2,3: Contact Software AG support.
        4:   Pass logon data that is valid for your security system.

NAT6976: Context error on :1:, reason :2: :3:.

Text
Context error on ..., reason ... ....
Explanation
Reason: 1: Context size overflow.
           The storage for the variables of the DEFINE DATA CONTEXT
           statement could not be allocated.
           On mainframe computers, the CONTEXT buffer could not be
           allocated or increased. This is either caused by storage
           restrictions of the operating or TP system, or by Natural
           environment constraints (Natural profile parameter OVSIZE,
           NATCONFG table entry NTBUFID for CONTEXT buffer).
           On Windows and UNIX systems, the USIZE buffer was not large
           enough to fulfil the storage request.
        2: Conflict in format/length definition of a variable.
           The context variable whose name is shown in the error message
           was defined in a previous program with a different
           format/length.
Action
           format/length.
Reason: 1: Decrease number of context variables and/or number of
           concurrent conversations, or remove storage contraints.
        2: Correct format/length of context variable.

NAT6977: EntireX RPC error on :1:, reason :2: :3:.

Text
EntireX RPC error on ..., reason ... ....
Explanation
An EntireX RPC error has occurred.
The reason shows the EntireX RPC error number, optionally followed by
additional diagnostic information.
This error can only occur if a Natural client is communicating with an
EntireX RPC server.
Action
Refer to the EntireX Communicator messages and codes.

NAT6978: RPC protocol error on :1:, reason :2: :3:.

Text
RPC protocol error on ..., reason ... ....
Explanation
Reason: 2: The Server does not support the RPC protocol version used by
           the RPC client.
           Or:
           The client does not support the RPC protocol version used by
           the client interface object (stub subprogram).
           After the reason, the unsupported version is shown
           in the message.
        3: The RPC protocol header or RPC format buffer is invalid.
           After the reason, the corresponding EntireX error number is
           shown in the message. In the case of format buffer errors,
           the erroneous element is appended to the error number.
Action
Use the correct RPC protocol version.
Refer to the EntireX messages.

NAT6979: Premature termination of a remote CALLNAT.

Text
Premature termination of a remote CALLNAT.
Explanation
The remote execution of a CALLNAT was prematurely terminated on the
server side and all data of the parameter area were lost. The reason
for this may be the use of one of the following Natural statements:
- STOP
- FETCH
- ESCAPE BOTTOM outside of a processing loop
- RUN
- TERMINATE
Note: These statements will be disabled in a remotely executed CALLNAT
in one of the next Natural versions.
Action
Do not use one of the listed statements in a remotely executed CALLNAT.

NAT6980: Invalid parameter.

Text
Invalid parameter.
Explanation
One or more invalid parameters were entered with the command.
Action
Check the DDE client program to ensure that all parameters are in the
proper order and are of the correct type.
Check the command description in the documentation for valid input.

NAT6981: Member or file already exists.

Text
Member or file already exists.
Explanation
An operation tried to update or replace an existing member or file.
Action
Check the command description in the documentation and reissue the
command using the "Replace" parameter.

NAT6982: Unable to read DDM transfer file.

Text
Unable to read DDM transfer file.
Explanation
Error while reading a DDM transfer file.
Action
Ensure that the file is not being accessed by another application
and that the file exists.

NAT6983: Editor is not active.

Text
Editor is not active.
Explanation
An editor command was issued for an editor which was not active.
Action
Start the editor and reissue the command.

NAT6985: Library not found.

Text
Library not found.
Explanation
A delete or rename command was issued for a library which does not
exist.
Action
Ensure that the name of the library and reissue the command.

NAT6986: Library already exists.

Text
Library already exists.
Explanation
The library cannot be renamed because a library by this name already
exists.
Action
Choose another name.

NAT6987: Unable to change type.

Text
Unable to change type.
Explanation
The editor was unable to change the type to the new type.
Action
Check to ensure that valid types are being used for the type of
editor and reissue the command.

NAT6989: Shutdown interrupted.

Text
Shutdown interrupted.
Explanation
The user cancelled the shutdown process by responding "No" or
"Cancel" to the shutdown prompt.

NAT6990: Invalid DDM type.

Text
Invalid DDM type.
Explanation
An invalid type or invalid information was found in a DDM transfer file.
Action
Check the documentation for valid DDM transfer options.

NAT6991: Editor is empty.

Text
Editor is empty.
Explanation
An attempt was made to perform a Natural command for an empty editor.

NAT6992: Editor is active.

Text
Editor is active.
Explanation
An attempt was made to perform a Natural command such as rename or
delete for an active editor.
Action
Close the editing session and reissue the command.

NAT6993: Editor list is empty.

Text
Editor list is empty.
Explanation
The list command was issued when no active editors were active.

NAT6994: Short name conflict.

Text
Short name conflict.
Explanation
A GenDDM transfer file was entered in which short names are missing.
Action
Ensure that the transfer file
   - contains a short name for every field or
   - contains no sort names in any field.

NAT6999: Internal DDE server error.

Text
Internal DDE server error.
Explanation
An internal DDE server error occurred.
Write down all information about how the error occurred and contact
technical support.
Please provide the following information:
1. Command and parameters issued which led to problem.
2. Member information (type, member, library) for which the command
   (above)  was issued.
3. Description of how error occurs (if reproducible).
4. Topics to which other clients or multiple connections were connected
   (if any were active).
5. If more than one client was active, whether they were performing
   operations simultaneously.
Action
   operations simultaneously.
See explanation