Adabas Interface

This message indicates that one or more of the following errors were the program's (named $1) ADABAS parameter list or ACB:

1. The location specified to contain the ADABAS parameter list was not within the area available to the application program.

2. One or more of the locations specified to contain the ACB or ADABAS buffers was not within the area available to the application program.

3. One or more of the lengths specified for the ADABAS buffers was too large or negative.

The application program is abnormally terminated and a dump is taken.

This error was caused by the application program. Contact the programmer responsible for the program in use when the error occurred.

Register 1 in the dump contains the address the program supplied for the ADABAS parameter list. Check this address, the buffer addresses, and the buffer lengths to determine which addresses or lengths are invalid.

This message is issued by the Com-plete ADABAS interface. It indicates that Com-plete was unable to successfully perform an ADABAS call for program $1 because there was insufficient room in the general buffer pool for the ADABAS buffers required by the interface.

The application program is abnormally terminated and a dump is taken.

The condition causing the error may be temporary and due to heavy use of ADABAS. Wait a few minutes and try again. If the problem persists, report the problem to the system programmer responsible as it indicates that insufficient space has been allocated at startup of Com-plete.

As this buffer is gotten from Com-plete's Adabas Buffer Pool, this message indicates that there is insufficient buffers available at certain times to satisfy all requests.

Register 1 in the dump contains the address of the ADABAS parameter list, which contains the address of the ACB and buffers. From this information, the ADABAS command can be determined and the amount of data being transferred to and/or from ADABAS can be verified. If the program issues an ADABAS call that requires an extremely large amount of data to be transferred, it may be possible to modify it to make more calls transferring a smaller amount of data with each call. If this modification cannot be made or if it is not felt that the amount of data being transferred is excessive, consult the Com-plete system programmer about increasing the size of Com-plete's region to allow for general buffer pool expansion.

This message is issued by the Com-plete ADABAS interface. It indicates that there were more ADABAS calls than specified in the ADALIMIT startup parameter after the last terminal I/O.

The application program is abnormally terminated and a dump is taken.

This error was caused by the application program. Contact the programmer responsible for the program in use when the error occurred.

Check the size specified for the ADALIMIT startup parameter. Please refer to the chapter 'Startup Options' in the Com-plete System Programmer's Manual.

This problem can arise if either the ADALIMIT parameter is too small or the application program does too much or too complex work in one dialog. Other reasons may be: increased amount of data within ADABAS or a loop in the application program.

Adabas SVC numbers must be declared to Com-plete using SYSPARM ADASVC. No SVC number has been declared for the DB ID as indicated by $1, neither has a default Adabas SVC number been defined.

The application program is terminated abnormally with a thread dump.

If the DB ID is valid, make sure you specify its SVC number using SYSPARM ADASVC.

Self-explanatory message.

The presence of at least one ADASVC= parameter in the Com-plete sysparms triggers the initialization of the Com-plete Adabas interface.

The program that issued the Adabas call is terminated abnormally.

If it is intented in this Com-plete to run programs that issue ASdabas calls, then make sure you specify the Adabas SVC number(s).