The SOA Gateway Adabas driver employs the Adabas "Multifetch" feature to reduce IPC (Inter-Process Communication) with the Adabas database server for maximum performance.
For a LIST or SELECT request a default of 64 records to be "multifetched" is applied, an Adabas response code 152 is returned when the buffer areas required to return 64 records of the size determined by the SOA Gateway XRD for the WebService in question exceed the Adabas LU parameter.
Resolution:
Increase the Adabas LU parameter
Reduce the size of the data to be transferred per record, for example by lowering the "maxOccurs" setting for MU and/or PE fields within the XRD
Use the SOAP header option SOAGateway_Internal_Adabas_Multifetch_Limit to specify a value, lower than the default of 64, that results in a transfer buffer size small enough to not exhaust the LU parameter setting.
A -2053 means that the SOA Gateway cannot access the Natural INI file. This can occur if the Software AG environment file, (e.g /opt/software/sagenv.new) cannot be accessed. It can also occur if some of the Natural files or directories cannot be accessed due to permissions problems.
Regardless of how the SOA Gateway Apache is started, the threads that handle requests are run as a user specified in the configuration. To determine what this user is, look at [install_home]/apache2/conf/adabas_soa_gw.conf file, and search for the "User" directive. This user must have access to the Software AG environment file, and Natural files and directories.
A -2016 means the SOA Gateway server can't access the Natural bufferpool "Unable to open buffer pool; contact the Natural system administrator." Is the bufferpool up ? Can you start a Natural session interactively ? If yes, it might be an authorization problem, i.e. the user assigned to the SOA Gateway Server not having the rights to talk to the Natural Bufferpool Server, or the Natural parameter module you are using specifying a bufferpool which isn't up.
