Text |
Error ... with SQLSTATE ... from call to .... |
Explanation |
Each non zero SQLCODE is reported with this error message. |
Action |
Execute the program SQLERR to display the SQLCODE and the related tokens. See the relevant IBM literature for an explanation of the error condition. |
Text |
Natural SQL interface error with reason code .... |
Explanation |
Reason codes: nnnn: See corresponding Natural error message number; or one of the following: 100: HOST invalid function code 306: PRSS NATCVERT call failed 103: HOST error in GETMAIN 320: REQI internal save area full 104: HOST error in FREEMAIN 401: SQLP invalid function code 105: HOST error in ENQUEUE 402: SQLP invalid statement ID 106: HOST error in DEQUEUE 403: SQLP invalid statement number 201: REQI ADABAS command not emulated 404: SQLP command ID not found 202: REQI command ID not found 405: SQLP invalid statement CMCD 301: PRSS special SQL parse error 421: DB2P invalid function code 302: PRSS negative statement length 431: NSQO RDI coding > 254 303: DB2P special stmt not in NDBIOMO 432: NSQO MVC not found 305: PRSS special SQL parse error 433: NSQO LA not found |
Action |
Contact Software AG. |
Text |
Invalid packed field. |
Explanation |
Fields defined with packed format must be in the form "nn.m". "nn" represents the number of digits before the decimal point, and "m" represents the number of digits after the decimal point. The value of "m" must not exceed 29, and the sum of the values of "nn" and "m" must not exceed 29. |
Action |
Check program and correct error. |
Text |
Field modified by another user or row not found. |
Explanation |
1) The positioned UPDATE or DELETE command to DB2 checks if the record contents is still identical to what the user had read before. Because of the automatic "COMMIT" issued by IMS TM or CICS pseudo- conversational mode at terminal I/O time, the "hold" status of the record is lost and the record is free to be modified by another user. Natural then cancels the current transaction with this error message. 2) If sensitive dynamic scrollable cursors are used in an IMS TM or CICS pseudo-conversational environment across terminal I/Os, the sensitive dynamic scrollable cursor is implicitly closed upon terminal I/O. NDB re-opens the cursor after terminal I/O and tries to position the cursor to the row which was current before the terminal I/O. The number of re-positional fetches are limited by the parameter RETRYPO in each direction from the position noted before the terminal I/O. The default value of RETRYPO is 10. |
Action |
1)Retry this operation. 2)For sensitive dynamic scrollable cursors re-execute the program and increase the RETRYPO value if necessary. |
Text |
Update/repositioning not possible after automatic COMMIT. |
Explanation |
Natural tries to re-read a given DB2 record after a terminal I/O which has caused IMS TM or CICS in pseudo-conversational mode to issue an automatic COMMIT. This COMMIT loses the current record. The re-reading is only possible if the record can be identified via a unique index and the corresponding fields are all read into the data view. This error occurs also during repositioning of sensitive dynamic scrollable cursors after a terminal I/O if the desired row could not be repositioned due to a missing unique key column. |
Action |
Update the record before the automatic COMMIT, or add a unique-index field to your data view. |
Text |
File server error ... with reason x"...". |
Explanation |
The file server routine returned an error: 01 Global directory full. 16 Logical file already open. 02 Local directory full. 17 Logical file not open. 03 Global directory inconsistent. 18 Logical file not closed. 04 Dataset open error. 19 Logical file open output on read. 05 Dataset read error. 20 Logical file open input on write. 06 Dataset write error. 21 Invalid function code. 07 ENQUEUE failed. 22 Invalid open mode. 08 DEQUEUE failed. 23 Invalid re-read at top of file. 10 DB2SIZE parameter invalid. 24 Invalid read-back (top of file). 11 System GETMAIN failed. 25 Invalid buffer length. 12 System FREEMAIN faile. 26 User space exceeded. 14 Not enough space in dataset. 27 Global space map invalid. 15 Logical file not allocated. 28 Global directory invalid. |
Action |
Restart Natural and retry the operation. If the problem persists, contact your Natural administrator. |
Text |
Static program ... cannot be loaded. |
Explanation |
The static program referenced in the Natural SQL program cannot be loaded for one of the following reasons: - The static program is not contained in the load libraries currently defined to Natural. - There is not enough storage available for dynamic loading of a static program. - The limit for the number of dynamically loadable user programs was exceeded (parameter CDYNAM). - Under Com-plete, the program was neither defined as RESIDENTPAGE nor cataloged via ULIB. - Under Com-plete the thread into which the program is to be loaded is too small. - Under CICS a PPT entry for the program is missing. |
Action |
Check for the above error situations, or (as a by-pass) recatalog the program to clear the reference to the static program. |
Text |
Loaded static program does not match Natural program. |
Explanation |
The static program referenced in the Natural program has been loaded; however, either the static program was not generated for this Natural program, or its time-stamp is different from that of the Natural program. |
Action |
Replace the static program in the load library with the correct version, or re-generate the static program. |
Text |
Static program cannot handle current Natural statement. |
Explanation |
The loaded static program has no reference to the current Natural statement. |
Action |
Replace the static program in the load library by the correct version, or re-generate the static program. |
Text |
Not enough storage for static program. |
Explanation |
The static program needs an area of main memory in which to create the SQLDSECT. The area available, however, was not large enough. This can only happen if errors during the assembly of the static program have been ignored. |
Action |
Check the assembly of the static program for assembly errors concerning variables in the SQLDSECT. |
Text |
CICS/DB2 attachment facility is not active. |
Explanation |
Natural tried to access DB2 via the CICS/DB2 attachment facility, but this facility was not active. |
Action |
Ask your CICS administrator to start the CICS/DB2 attachment facility. |
Text |
Now it is too late for BACKOUT TRANSACTION. |
Explanation |
The program contains a design error: it attempts to backout updates which have already been committed. A terminal I/O has forced the end of the logical unit of work; nevertheless, the BACKOUT TRANSACTION has been issued. This means that the actual scope of the BACKOUT TRANSACTION is different from the expected one. |
Action |
Correct error in program. |
Text |
Natural SQL interface not active. |
Explanation |
The access to SQL is disabled for one of the following reasons: - The parameter DB2SIZE is set to 0. - During the initialization of Natural, the Natural SQL interface could not be initialized because of a (reported) error. |
Action |
Correct the error which occurred during the Natural initialization, or specify DB2SIZE > 0. |
Text |
Function code for DB2SERV must be "D", "E" or "P". |
Action |
Specify valid function code. |
Text |
Error :1: during :2: processing :3:, reason x":4:". |
Explanation |
Error code :1: occurred during the :2: processing of function :3:, and reason code :4: was returned. :2: is the name of the DB2 interface used, either CAF (call attachment facility) or RRSAF (resource recovery services attachment facility). :4: is the name of the failing function. |
Action |
See the relevant IBM literature for an explanation of the reason code. If more information is required, activate DSNTRACE. |
Text |
Error in Com-plete to DB2 connection, reason x"...". |
Explanation |
An error occurred when Com-plete tried to connect the user to DB2. Reason codes (set by Com-plete): 04 - DB2 interface not defined to Com-plete. 08 - DB2 interface could not be initialized by Com-plete. 12 - No DB2 thread within Com-plete available. |
Action |
Contact your Com-plete administrator. |
Text |
ISQL processor not installed. |
Explanation |
During the installation of the Natural SQL interface, the module NDBISQ was not included in the link-edit of the NDB nucleus. |
Action |
Contact your Natural administrator. Review the installation of the environment-independent NDB nucleus. |
Text |
Special SQL statement in error. |
Explanation |
The special SQL statement used in the PROCESS SQL command is - syntactically wrong - not supported because of the use of literals |
Action |
Correct the SQL statement and use Natural variables instead of literals. |
Text |
Special SQL statement found, not prepared. |
Action |
Contact Software AG |
Text |
Statement table overflow. |
Explanation |
No free DECLARE STATEMENT in the NDBIOMO is available to execute the SQL statement in dynamic mode. This will only happen if all STATEMENTS are actually used by open data base loops. |
Action |
Contact your Natural administrator. Increase the 2nd parameter in the generation of the NDBIOMO. |
Text |
Invalid SQL database type encountered during processing. |
Explanation |
The SQL database type encountered does not exist. |
Action |
Contact your Natural administrator. |
Text |
Buffer for ISQL processor (DB2SIZE5) could not be allocated. |
Explanation |
The ISQL processor requires an buffer of 8K which is allocated in the Natural thread but the Natural thread is not large enough to hold this buffer. |
Action |
Contact your Natural administrator. Reduce Natural"s total area size allocations, or increase the Natural thread. |
Text |
Too many nested database loops. |
Explanation |
An overflow occurred in the internal table which maintains the open (=nested) database loops. |
Action |
Contact your Natural administrator. Increase the MAXLOOP parameter in the generation of the NDBPARM. |
Text |
No more space available. |
Explanation |
During the execution of an SQL statement working storage is GETMAINed outside the Natural thread but there is not enough space available. |
Action |
Contact your Natural administrator. Increase the region size, or MEMRES (only Com-plete). |
Text |
Error in ET processing via TP driver, reason x"...". |
Explanation |
Under CICS and IMS TM, the ET is processed via the corresponding TP driver, but the ET failed. Under IMS TM, the reason is the hexadecimal representation of the DL/I status code. Under CICS, the reason is the hexadecimal representation of the EIBRCODE. |
Action |
Check the reason against the DL/I or CICS documentation. |
Text |
ET in message-driven IMS region could not be executed. |
Explanation |
In a message-driven IMS TM region (MPP or message-oriented BMP) no Natural programmed ET is executed. Depending on the setting of the parameter ETIGN in the NDBPARM, the ET is aborted with this error message, or ignored without any further notification. |
Action |
Check your program for obsolete ETs. |
Text |
Error during BT processing via TP driver, reason x"...". |
Explanation |
Under CICS and IMS TM, the BT is processed via the corresponding TP driver, but the BT failed. Under IMS TM, reason is the hexadecimal representation of the DL/I status code. Under CICS, reason is the hexadecimal representation of the EIBRCODE. |
Action |
Check the reason against the DL/I or CICS documentation. |
Text |
Error during ET/BT processing via NDL, reason x"...". |
Explanation |
In the DSNMTV01 environment, ET and BT calls are processed by the e Natural to DL/I interface, but the ET/BT failed. Reason contains the hexadecimal representation of the reported NDL error. |
Action |
Check reason. |
Text |
Invalid parameter for GET/SET GA. |
Action |
Contact Software AG. |
Text |
SQL statement "COMMIT" not allowed. |
Explanation |
The SQL statement "COMMIT" is not allowed with PROCESS SQL. |
Action |
Use the Natural statement COMMIT or END TRANSACTION. |
Text |
SQL statement "ROLLBACK" not allowed. |
Explanation |
The SQL statement "ROLLBACK" is not allowed with PROCESS SQL. |
Action |
Use the Natural statement ROLLBACK or BACKOUT TRANSACTION. |
Text |
Not enough cursors defined in NDBIOMO. |
Action |
Contact Software AG. |
Text |
No ... in NDBIOMO available. |
Explanation |
During runtime a Natural for DB2 user program requests one of the following features 1) "ALLOCATE CURSOR" (READ RESULT SET statement) 2) "CURSOR with RETURN" (SELECT WITH RETURN STATEMENT) 3) "CURSOR WITH HOLD" (SELECT WITH HOLD statement) but the appropriate DB2-environment parameter was not set correctly during NDBIOMO generation 1) DB2V5 2) DB2V5 3) DB2V23 |
Action |
Generate the NDBIOMO with the first parameter set to DB2V5/DB2V23 or remove the failing statement from the Natural program if you do not have the right DB2 environment. |
Text |
"CID" already in use. |
Action |
Contact Software AG. |
Text |
Invalid data type for Natural variable used in PROCESS SQL. |
Explanation |
Some special SQL statements which cannot be executed in dynamic mode are executed by NDBIOMO in static mode. As all host variables are predefined in the NDBIOMO, the corresponding Natural variables must be of the same data type. |
Action |
Correct the data type of your Natural variable. The correct definition for the variable can be found in the DB2 documentation. |
Text |
Invalid data length for Natural variable used in PROCESS SQL. |
Explanation |
Some special SQL statements which cannot be executed in dynamic mode are executed by NDBIOMO in static mode. As all host variables are predefined in the NDBIOMO, the length of the corresponding Natural variable must be - not longer for input variables (:U:) - not shorter for output variables (:G:) |
Action |
Correct the data length of your Natural variable The correct length for the variable can be found in the DB2 documentation. |
Text |
SQL statement in PROCESS SQL is not available in NDBIOMO. |
Explanation |
During the generation of the NDBIOMO the first parameter was not set to DB23 but one of the special DB2 2.3 SQL statements should be executed. |
Action |
Generate the NDBIOMO with the first parameter set to DB23 or don"t use an DB2 2.3 statement in the PROCESS SQL. |
Text |
NAT object STOWed under NDB ... but executed under .... |
Explanation |
The Natural object was STOWed using the NDB version in .1. but executed in the older version .2. |
Action |
Re-STOW your Natural program using version .2. . |
Text |
Natural interface ... for SQL system ... not installed. |
Explanation |
The Natural interface .1. for the requested SQL system .2. is not installed. |
Action |
Contact your Natural administrator. |
Text |
SQLDISCONNECT not allowed while a transaction is open. |
Explanation |
SQLDISCONNECT cannot be executed while a transaction is open. |
Action |
Issue END TRANSACTION or BACKOUT TRANSACTION before executing SQLDISCONNECT. |
Text |
Refresh of :1: failed with SQLCODE :2: |
Explanation |
The refresh of either CURRENT SERVER or CURRENT PACKAGESET or CURRENT SQLID failed with SQLCODE :2: during begin of DB2 Database transaction. |
Action |
Contact Customer Service. |
Text |
GETMAIN for dynamic SQL string failed with code X"...". |
Explanation |
Natural statement containing text variables failed due to GETMAIN problems during dynamic creation of the SQL string. |
Action |
Increase DB2SIZE or Natural threadsize or decrease size of SQL string containing text variables in program |
Text |
Logic error during creation of dynamic SQL string. |
Explanation |
During creation of the dynamic SQL string built from text variables an internal logical problem occurred. |
Action |
Contact Customer Service |
Text |
NDBPARM module could not be located. |
Explanation |
The runtime of Natural for DB2 failed to locate the NDBPARM module (ENTRY XCMSQLE) although the module could be located earlier during the Natural session. |
Action |
Contact Customer Service |
Text |
IF NO RECORDS not allowed in SELECT with SCROLL and GIVING. |
Explanation |
IF NO RECORDS FOUND is not allowed in a SELECT statement with SCROLL and GIVING clause. When using SCROLL and GIVING clauses the application requests to act on the returned SQLCODE in the GIVING variable. This causes the NO RECORDS FOUND block never to be executed. Therefore the NO RECORDS FOUND clause is useless and not allowed. |
Action |
Remove either the NO RECORDS FOUND clause or the GIVING clause from the SQL statement. |
Text |
NDB tools internal error. |
Action |
Contact Software AG |