Text |
CSECT ... is missing. |
Explanation |
This error may be caused by one of the following: - The module indicated in the message is missing in the link-edit stream. - The CSECT instruction is missing in the source of the module. - The module name in the CSECT instruction has been changed. |
Action |
Make sure that the module is included in the link-edit stream; make sure that the source of the module is complete/correct. |
Text |
INIT call failed with status code .... |
Explanation |
The Natural DL/I initialization routine issues an INIT call to inform IMS TM that it is prepared to accept status codes "BA" and "BB" regarding the unavailability of data. This call failed, and DL/I has returned the status code indicated in the message. |
Action |
Refer to the respective IBM documentation for a detailed explanation of the status code. |
Text |
Versions of NDLNUC and ... do not match. |
Explanation |
The modules included in the Natural DL/I link-edit must be of the same version. Module name: NDLSINIT |
Action |
Check NDLNUC, NDLSIO00 and NDLPARM. |
Text |
DLISIZE must be greater than .... |
Explanation |
If DLISIZE is not "0", it must be large enough to hold all buffers that are required by Natural for DL/I. |
Action |
Set DLISIZE to the value indicated in the error message. |
Text |
Error ... in GETMAIN in Natural for DL/I buffer. |
Explanation |
An error occurred when Natural for DL/I attempted to acquire its buffer from the thread. |
Action |
Increase the size of the thread. |
Text |
Error ... in GETMAIN in Natural for DL/I subpool .... |
Explanation |
An error occurred when Natural for DL/I attempted to acquire the subpool (as indicated in the error message) from its buffer. |
Action |
Contact Software AG support. |
Text |
No DBID marked as DL/I in NTDB macro. |
Explanation |
Natural for DL/I has been invoked, but in the NTDB macro no database has been reserved for DL/I. |
Action |
If you do not wish to invoke Natural for DL/I, invoke Natural with DLISIZE=0; otherwise correct error in NTDB macro. |
Text |
XRST call failed with DL/I status code .... |
Explanation |
When starting a BMP, the Natural DL/I initialization routine issues an extended restart (XRST) call. This call failed, and DL/I returned the status code indicated in the message. |
Action |
Refer to the respective IBM documentation for a detailed explanation of the status code. |
Text |
No valid PSB name was provided. |
Explanation |
The address pointing to the PCB address list is blank or zero. This happens if a DLISIZE other than zero has been specified and 1) Natural is not running under the control of the DL/I region controller (DFSRRC00 for z/OS, DLZRRC00 for z/VSE); or 2) Natural is running under control of the DL/I region controller, but, due to an internal error, the PCB address list has not been passed to Natural for DL/I; or 3) the PSB name in the JCL does not match the PSB name on CMSYNIN. Module name: NDLSINIT. Problem determination: Check the JCL used to start Natural. |
Action |
For 1: Run Natural under the control of the DL/I region controller, or run Natural with DLISIZE=0. For 2: Contact Software AG support. For 3: Correct the PSB name in the JCL or in CMSYNIN. |
Text |
NSB ... not found on FDIC system file. |
Explanation |
The PSB which is used to start Natural has not been defined on the FDIC system file or could not be read (due to an unexpected return code from the database). Module name: NDLSINIT. Problem determination: Check if the correct system file has been assigned. |
Action |
Specify correct FDIC, or run NATPSB procedure to store the NSB on the FDIC system file. Set DLISIZE=0 if you do not want an NSB associated with the transaction (because it does not need to access DL/I). |
Text |
Error in loading global area. |
Explanation |
The NDPSGLBA module is not included the link step; therefore it cannot be loaded dynamically. Module name: NDPSGLBA Problem determination: Obtain a link-edit listing. |
Action |
Either include NDPSGLBA in the link step (batch and CICS) or specify it in the STEPLIB DD card (IMS TM). |
Text |
Natural for DL/I initialization failed. |
Explanation |
The reason for this failure is explained by the more detailed error message issued together with this error message. |
Action |
See explanation of detailed message. |
Text |
Error when loading NDB/NSB. |
Explanation |
The NDB, or the NSB, could not be loaded from the load library (under z/VSE, from the core image library). Module names: NDLBINDB, NDLBINSB. Problem determination: Item 11 or Item 12. |
Action |
1. Check whether the load (core) library contains the NDB/NSB. 2. Check the results of the assembly and link steps of the NATDBD/NATPSB procedures which produce the above modules. |
Text |
Error in END TRANSACTION command. |
Explanation |
Due to an error when issuing the "ET" command, the NDB (or the NSB) could not be stored into the Natural system file. The message "SYSDLI: 1004" contains the I/O response code received from the Natural I/O processor. The I/O codes are described in the Adabas or Natural documentation respectively. Module names: NDPBNDB1, NDPBNSB1. Problem determination: Item 11 or Item 12. |
Action |
Contact your database administrator. |
Text |
DBD has too many (over 468) DL/I fields. |
Explanation |
A DBD with more than 468 (13 * (26 + 10)) DL/I fields cannot be processed. This is a design restriction. Module name: NDPBSESH Problem determination: Items 4, 11. |
Action |
Reduce the number of DL/I fields. |
Text |
Error in acquiring a work area (storing NDB/NSB). |
Explanation |
An error message was returned by the GETMAIN/GETVIS macro after Natural DL/I attempted to acquire a work area while processing a logical DBD. Module name: NDPBNDB1 Problem determination: Item 11. |
Action |
Increase the partition/region size. |
Text |
Error when storing the NDB/NSB. |
Explanation |
During the STORE operation of an NDB/NSB, an error message was returned either by the Adabas "N1" command or by a VSAM "PUT". The error message "SYSDLI: 1103" contains the I/O response code received from the Natural I/O processor. The I/O codes are described in the Adabas or Natural documentation respectively. Module names: NDLBSNDB, NDLBSNSB. Problem determination: Item 11. |
Action |
Correct the condition that caused the I/O error. |
Text |
DBD/PSB name does not match the load module name. |
Explanation |
The NAME parameter in the DBD/PSB macro does not match the load module name in the load (in z/VSE, core) library which contains the output of the assembly and link steps of the NATDBD/NATPSB procedure. Module names: NDLBINDB, NDLBINSB. Problem determination: Items 4/5, 11/12. |
Action |
Check the name of the load module containing the output of the assembly step of the NATDBD/NATPSB procedure; change it accordingly to match the NAME parameter. Ensure that SAG macros are used during the assembly. |
Text |
NDB not found. |
Explanation |
Internal error. Module name: NDPBRNDB Problem determination: Items 1 (trace parameter = (CMD,REQ,SER)), 11. |
Action |
Contact Software AG support. |
Text |
Error in acquiring a work area. |
Explanation |
An error message was received from the GETMAIN/GETVIS macro while acquiring the I/O area into which the first slot of the old copy of the NDB being processed was to be read. Module name: NDPBRNDB Problem determination: Item 11. |
Action |
Increase the partition/region size. |
Text |
Error in acquiring a work area. |
Explanation |
An error message was received from the GETMAIN/GETVIS macro while acquiring the I/O area into which the old copy of the NDB being processed was to be read. Module name: NDPBRNDB Problem determination: Item 11 or item 12. |
Action |
Increase the partition/region size. |
Text |
Error in reading an NDB. |
Explanation |
The new NDB copy could not be stored on the Natural system file due to an error which occurred while reading the old copy. The error message "SYSDLI: 1004" contains the I/O response code received from the Natural I/O processor. The I/O codes are described in the Adabas or Natural documentation respectively. Module name: NDPBRNDB Problem determination: Item 11. |
Action |
Correct the condition that caused the I/O error. |
Text |
Error in reading an NDB. |
Explanation |
The new NDB copy could not be stored on the Natural system file due to an error which occurred while reading the old copy. The error message "SYSDLI: 1004" contains the I/O response code received from the Natural I/O processor. The I/O codes are described in the Adabas or Natural documentation respectively. Module name: NDPBRNDB Problem determination: Item 11. |
Action |
Correct the condition that caused the I/O error. |
Text |
Error in reading an NDB. |
Explanation |
An error occurred while the old copy of an existing NDB (or NSB) was being read for update. The error message "SYSDLI: 1004" contains the I/O response code received from the Natural I/O processor. The I/O codes are described in the Adabas or Natural documentation respectively. Module names: NDPBDNDB, NDPBDNSB. Problem determination: Item 11 or item 12. |
Action |
Correct the condition that caused the I/O error. |
Text |
Error in reading an NDB. |
Explanation |
An error occurred while the old copy of an existing NDB (or NSB) was being read for update. The error message "SYSDLI: 1004" contains the I/O response code received from the Natural I/O processor. The I/O codes are described in the Adabas or Natural documentation respectively. Module names: NDPBDNDB, NDPBDNSB. Problem determination: Item 11 or item 12. |
Action |
Correct the condition that caused the I/O error. |
Text |
Error in deleting an NDB. |
Explanation |
An error occurred while the old copy of an NDB was being deleted. The error message "SYSDLI: 1004" contains the I/O response code received from the Natural I/O processor. The I/O codes are described in the Adabas or Natural documentation respectively. Module name: NDPBDNDB Problem determination: Item 11. |
Action |
Correct the condition that caused the I/O error. |
Text |
NDB/NSB not found. |
Explanation |
This error occurs when an NDB (or NSB) is being read for update before being deleted. The error is originated by the "L3" command (Adabas system file) or by the VSAM GET (VSAM system file). The error message "SYSDLI: 1004" contains the I/O response code received from the Natural I/O processor. The I/O codes are described in the Adabas or Natural documentation respectively. Module names: NDPBDNDB, NDPBDNSB. Problem determination: Item 11 or item 12. |
Action |
Correct the condition that caused the I/O error. |
Text |
Error in building a logical NDB. |
Explanation |
The work area used for building a logical NDB is too small. Module name: NDPBNDBL Problem determination: Item 11. |
Action |
Contact Software AG support. Software AG will change YLOG in NDPBNDB1 and relink NDLB0001. |
Text |
Sequence-field error in building a logical NDB. |
Explanation |
More than one sequence field was found for a segment which is NOT a logical virtual child. Up to five sequence fields may be defined ONLY for logical virtual child segments. Module name: NDPBNDBL Problem determination: Items 4, 11. |
Action |
Ensure that the DBDGEN procedure was successfully executed for this DBD, as this error should be detected by DBDGEN. |
Text |
Error in building AIX links in a logical NDB. |
Explanation |
Internal error. Module name: NDPBNDBL Problem determination: Items 4, 11. |
Action |
Contact Software AG support. |
Text |
Error in acquiring a work area for a logical NDB. |
Explanation |
A GETMAIN/GETVIS macro was invoked to acquire a work area where a logical NDB was to be built. A non-zero response code was returned. Module name: NDPBNDB1 Problem determination: Item 11. |
Action |
Increase the partition/region size. |
Text |
Segment referred to as source was not found. |
Explanation |
While processing a segment with a SOURCE parameter, the specified segment was not found in the NDB corresponding to the DBD specified in the SOURCE keyword. Module name: NDPBNDBL Problem determination: Item 11. |
Action |
Ensure that the ACBGEN procedure was successfully executed for this DBD, as this error should be detected by ACBGEN. |
Text |
Error in acquiring a work area for a logical NDB. |
Explanation |
A GETMAIN/GETVIS macro was invoked to acquire a work area where a logical NDB was to be built. A non-zero response code was returned. Module name: NDPBNDB1 Problem determination: Item 11. |
Action |
Increase the partition/region size. |
Text |
NDB not found in Natural system file. |
Explanation |
While processing a segment with a SOURCE parameter, the NDB corresponding to the DBD specified in the SOURCE keyword was not found in the Natural system file. Module name: NDPBNDBL Problem determination: Item 11. |
Action |
Ensure that the DBDGEN procedure was successfully executed for this DBD, as this error should be detected by DBDGEN. |
Text |
Inhibit flag of segment in "SOURCE" keyword set to "ON". |
Explanation |
The procedure NATDBD is executed for a logical DBD. This DBD contains a SOURCE=((segname,,dbname)) statement to identify segment type "segname" in physical database "dbname". However, the NDB corresponding to "dbname" contains one or more segment types which are marked as inhibited. These segment types were inhibited by Natural during the execution of NATDBD against "dbname" because not all references to the real logical child segment type could be resolved. Module name: NDPBNDBL Problem determination: Item 11. |
Action |
Before executing NATDBD for a logical DBD, execute NATDBD for all physical DBDs referred to. If the logical relationship is the result of a recursive structure, run NATDBD for the physical DBD at least twice. |
Text |
Overflow of source error table. |
Explanation |
The table which contains the list of segments with an error flag is too small. Module name: NDPBNDBL Problem determination: Item 4. |
Action |
Contact Software AG support. |
Text |
Physical NDB referenced as source was not found. |
Explanation |
While processing a segment with a SOURCE parameter, the NDB corresponding to the DBD specified in the SOURCE keyword was not found in the Natural system file. (The NDB has been stored in the Natural system file with some segments having the inhibit flag set to "ON".) Module name: NDPBNDBL Problem determination: Item 4. |
Action |
Re-execute the NATDBD procedure. For details, see the section on logical databases in the Natural DL/I documentation. |
Text |
Error when scanning NSB (CMPAT=YES). |
Explanation |
Module name: NDPBNSB1 |
Action |
Check the PSB definition. |
Text |
Natural nucleus not found. |
Explanation |
When running NDL batch under z/VSE, NDLSINID tries to load the Natural phase whose name has been specified in the JCL. This phase was not found. Module name: NDLSINID |
Action |
Check the name of the Natural phase in the JCL. |
Text |
Not enough memory to load Natural nucleus. |
Explanation |
When running NDL batch under z/VSE, NDLSINID tries to load the Natural phase whose name has been specified in the JCL. This phase could not be loaded, because there was not enough memory available. Module name: NDLSINID |
Action |
Check the size of the Natural batch phase, and specify the SIZE parameter in the JCL accordingly. |