Text |
Invalid :1: service pack :2: must be at least :3:. |
Explanation |
The service pack of the component (:1:) must be at least as indicated. |
Action |
Contact your Natural administrator. Install the correct service pack. |
Text |
The Natural for DB2 parameter module is not linked. |
Explanation |
This may also indicate that you are using an old version of the Natural parameter module (must be at least 2.2.4). |
Action |
Contact your Natural administrator. Link the Natural for DB2 parameter module to your Natural environment. |
Text |
Natural SQL interface not active. No SQL calls can be processed. |
Explanation |
This error message is preceded by an initialization error message. |
Action |
Check for previous initialization error. |
Text |
Natural SQL interface active without file server. |
Explanation |
This error message is preceeded by an initialization error of the file server. The file server is not available for this Natural session but SQL statements will be processed as normal. |
Text |
... not linked / not found. |
Explanation |
The required module ... is not linked to your Natural environment. |
Action |
Contact your Natural administrator. Check your installation. |
Text |
DB2SIZE parameter must be set to at least .... |
Explanation |
The area specified with the DB2SIZE parameter is too small to accommodate all buffer areas required by Natural DB2 / Natural SQL/DS. |
Action |
Set DB2SIZE to the value as indicated in the error message; then invoke Natural again. |
Text |
GETMAIN for DB2SIZE failed. |
Explanation |
During Natural initialization, the GETMAIN for the buffer area specified by the DB2SIZE parameter failed. The probable reason is that not enough free storage is available or that the thread is too small. |
Action |
Reduce Natural's total area size allocations, or increase the region size. |
Text |
File server initialization error .... |
Explanation |
The initialization of the file server failed, returning the reason code as indicated in the error message. Possible reason codes and their meanings are: 01 - Global directory full. 04 - Dataset open error. 05 - Dataset read error. 06 - Dataset write error. 07 - ENQUEUE failed. 08 - DEQUEUE failed. 10 - DB2SIZE too small. 11 - System GETMAIN failed. 12 - System FREEMAIN failed. 13 - WAIT request failed. 14 - Not enough space in dataset. |
Action |
Contact your Natural administrator. |
Text |
Load of DB2COMRE failed. |
Explanation |
During initialization of the Natural SQL interface under Com-plete, the Com-plete to DB2 interface DB2COMRE could not be loaded. Typically DB2COMRE is not defined as RESIDENTPAGE. |
Action |
Contact your Com-plete administrator. |
Text |
Natural must be started via NDLSINIB in DSNMTV01. |
Explanation |
In the DSNMTV01 environment all ET/BT calls are to be processed by NDLSINIB, but Natural has not been started via the NDLSINIB bootstrap module. |
Action |
Start Natural via the NDLSINIB bootstrap module. |
Text |
User area has been modified. |
Explanation |
Natural checks the contents of the user area at regular intervals. When this area has been overwritten, Natural cannot guarantee correct continuation of the Natural session. |
Action |
Restart Natural. |
Text |
System file has been modified. |
Explanation |
Natural checks the integrity of the Natural system file. If Natural detects a discrepancy, this error message is issued. The DBA should try to find out who or why data have been modified in the system file without proper authorization. |
Action |
Re-INPL the Natural system file. |
Text |
Natural nucleus Service Pack does not agree with system file. |
Explanation |
During startup, Natural checks whether the system file agrees with the Natural nucleus in major version, minor version and service pack. If these versions do not agree, it is highly likely that some system programs will not work. |
Action |
Restart Natural with the correct system file. |
Text |
Natural system file information missing. |
Explanation |
1) During startup, Natural checks the system file information for validity. Natural could not find any system file information. Either the system file specified with the profile parameter FNAT is not a valid system file, or the system file has been corrupted by unauthorized access. 2) If this error occurs using the Natural editor, there may be a locking problem because your NDV installation may not be completed. Re-start your Natural session with a valid FDIC system file defined. |
Action |
Restart Natural with a correct system file. |
Text |
Value for dynamic parameter missing. |
Explanation |
Invalid syntax in dynamic parameters. Probably an equal sign (=) or a keyword value is missing. |
Action |
Restart the Natural session with correct specification of dynamic parameters. |