Platform-Specific Functionality
x
The Adapter for Adabas on UNIX, Windows, and OpenVMS, has more
restrictions than on z/OS. These restrictions are described below.
On all platforms, if an error occurs while Adabas commands
are being processed, then the communication block (CB) is returned
along with the Response Code (RC) Additions 2 field, in 2 or 4 bytes
binary format. The Additions 2 field indicates the specific reason
for the Response Code. The Adapter for Adabas displays both RC and Additions
2 fields in the message. This information is available in the trace
as well.
x
Reference: Functionality on z/OS
The
following conditions apply when using the adapter on z/OS platforms:
- Sub/super descriptors defined with "NC=YES" and "MISSING=ON" parameters
cannot be used to search for SQL NULL values, as that causes an
Adabas RC 61.
- If you assign Server or Application Administrator privileges
to user IDs other than the one used to install the server, to allow
these additional administrators to create metadata for Adabas data
sources, you must do one of the following:
- Include the Adabas
load library in your SYS1.PARMLIB(LNKLSTnn) member.
- Use the STEPLIBLIST feature and add the Adabas load library
to the sanctioned list file. For full details on the STEPLIBLIST
feature, see the IBM publication UNIX System Services Planning
Guide. Tip: To locate the information in that document,
search for STEPLIBLIST.
x
Reference: Functionality on UNIX and Windows
The
following conditions apply when using the adapter on UNIX and Windows
platforms:
- You cannot
use non-descriptor fields as search criteria.
- The parameter NDFIND is automatically set to the OFF value if
the adapter is executed in a non-mainframe environment. If non-descriptor
fields are used as key fields, the entire database is read.
- If the Master File non-descriptor field is declared as an indexed
field (INDEX=I or FIELDTYPE=I) and used as a key field, the result
from Adabas is RC 61.
- If an occurrence of an MU (multi-value) field is deleted, the
adapter shifts all other occurrences into its place and assigns
an empty value for the last occurrence. If this field has an NU
(null suppression) option, the last occurrence will be automatically deleted
by Adabas.
- DBNO must be assigned to a valid numeric value for the existing
database.
x
Reference: Functionality for OpenVMS Platform
Adabas
on OpenVMS does not allow a direct request for sub/superdescriptors
values. For this reason, there are some limitations on using these fields
(with TYPE=NOP/SPR in ACX) in server requests to Adabas:
- NOP fields cannot be printed or
displayed, even if they are alphanumeric.
- NOP/SPR fields cannot be used in functions (MIN, MAX, and so
on).
- If NOP/SPR fields are used in the IF/WHERE criteria, then CALLTYPE=RL
is automatically changed to CALLTYPE=FIND. It can change the sequence
of returning data rows on OpenVMS in comparison with sequence on
other platforms.
- NOP fields cannot be used in a complex IF/WHERE clause.
- NOP fields cannot be used for joining.