| Text | Command not applicable in remote environment. |
| Expl. | The issued command cannot be executed in a remote (server) environment. |
| Actn. | Use the appropriate Natural Studio command or tool. In case of a file-operation command, use an equivalent "Object Menu" operation or "right mouse button" operation to achieve the desired result. |
| Text | Command not applicable within the application context. |
| Expl. | The issued command cannot be executed within the context of an application. |
| Actn. | Use the appropriate command in the library workspace, or use the
right mouse button "Unlink" command, if you want to unlink an object from the application. |
| Text | Command not applicable in local environment. |
| Expl. | The issued command cannot be executed in a local (client) environment. |
| Actn. | Use the appropriate Natural Studio command or tool. In case of a file operation command, use an equivalent "Object Menu" operation or "right mouse button" operation to achieve the desired result. |
| Text | Message from server: .... |
| Expl. | The server has sent a message to indicate a special situation. E.g., if, when deleting/renaming a library, one or more objects could not be deleted or renamed (primarily caused by locked objects), the server reports this to the client. |
| Text | Error during session reconnect. |
| Expl. | The Natural Development Server cannot reconnect your session for remote development. Possible reasons are: - Corrupted session directory of Natural Development Server. - Server address space exceeds specified limit of subtasks. - Region size (memory below 16 MB) is too small. - Natural Studio requests a reconnect with an invalid session identifier. |
| Actn. | Examine Natural Development Server trace file for additional
error information. |
| Text | Cannot create new session directory entry or subtask. |
| Expl. | The Natural Development Server cannot create a new entry in its
session directory or cannot create a new subtask to process remote development. Possible reasons are: - Server address space exceeds specified limit of subtasks. - Region size (memory below 16 MB) is too small. |
| Actn. | Examine Natural Development Server trace file for additional
error information. |
| Text | New session cannot be initialized. |
| Expl. | The Natural Development Server cannot perform the basic
initialization of a new subtask. Possible reason is shortage of memory above 16 MB. |
| Actn. | Examine Natural Development Server trace file for additional
error information. |
| Text | Session execution failed. |
| Expl. | The Natural Development Server cannot locate the Natural session
in its session directory. Possible reasons are: - The session was cancelled using the server monitor. - The session directory is corrupted. - The Natural Studio requests a reconnect with an invalid session identifier. |
| Actn. | Examine Natural Development Server trace file for additional
error information. |
| Text | I/O execution not allowed. |
| Expl. | The remote Natural session executes an I/O, although I/O
execution is not permitted. I/O execution is not permitted during session initialization and Natural Security logon processing. |
| Actn. | Locate the I/O buffer in the Natural Development Server trace
file and contact Software AG Support. |
| Text | Nat. Development Server error - reserved for future use. |
| Text | Error during I/O execution. |
| Expl. | The Natural Studio returns invalid data for the terminal I/O, or there is not enough memory available above 16 MB. |
| Actn. | Examine the Natural Development Server trace file for additional
error information and contact Software AG Support. |
| Text | Protocol element missing. |
| Expl. | For the processing of Natural Development Server (NDV) requests,
the NDV requires protocol data; these were not sent by the Natural Studio. |
| Actn. | Examine the Natural Development Server trace file for additional
error information and contact Software AG Support. |
| Text | NDV not installed on Natural system file. |
| Expl. | The Natural Development Server (NDV) cannot locate the NDV transaction-processor modules on the FNAT system file. The Natural Development Server installation is incomplete. |
| Actn. | Check whether the Natural Development Server INPL has been
executed on the specified FNAT system file. |
| Text | Library undefined, LOGON required. |
| Expl. | The logon library of the Natural Development Server session is undefined. This usually happens if the system command LOGOFF is executed, of if a Natural program executes a RETURN statement and no SETUP record is found. |
| Actn. | Enter a LOGON command to a valid library of your remote
environment; or click any library within your remote tree view to continue. |
| Text | Adaptation of conversion table failed - .... |
| Expl. | During the NDV session initialization the NDV server adapts the character conversion table for ASCII/EBCDIC conversion (TABA1/TABA2) according to the provided ASCII code page of the client. This function failed. Possible reasons: - An unknown ICU response code. Contact Natural support. - The client code page is not defined. Use a code page which is defined to Natural. - The client code page is not SBCS. The ASCII/EBCDIC translation cannot support code pages with multi-byte character sets. |
| Actn. | If you run Natural with CP=OFF, the TABA1/TABA2 adaptation is
omitted. |
