This section describes the preparation for and installation of Adabas on systems running under the Fujitsu Technology Solutions BS2000 operating system.
Information for your specific installation is contained in the BS2000 Product Installation Package distributed with the System Installation Aid.
The following list provides an overview of the Adabas installation procedure on BS2000 systems.
| Step | Description | Additional Information |
|---|---|---|
| 1 | Provide disk space for the Adabas libraries. | The libraries are restored from the installation tape into these libraries. Refer to the section Adabas Library Disk Space Requirements. |
| 2 | Allocate disk space for the Adabas database. | For better performance, distribute the database files over multiple devices and channels. Refer to the section Disk Space Requirements for the Database. |
| 3 | Specify the address space for running the Adabas nucleus. | Refer to the section Adabas Nucleus Address Space Requirements. |
| 4 | Install the product license file (job I010, steps 0010 and 0011). | For more information, read Step 1: Check, Prepare, and Install the Product License File (SMA job number I010) |
| 5 | Allocate and format the Adabas database with the ADAFRM utility job (job I030, steps 0010 to 0018). | |
| 6 | Define the global database characteristics with the ADADEF utility job (job I030, steps 0020 and 0021). | |
| 7 | Start the Adabas nucleus and test the Adabas communications with the ADANUC job. | |
| 8 | Load the demonstration files
ADAvrs.EMPL/MISC/VEHI/PERS/PERL with the ADALOD
utility (performed in job I050 steps 0001 to 0003).
Note: |
|
| 9 | If appropriate, test Adabas address space communications by running ADAREP (job I050 step 9999). | |
| 10 | If appropriate, load the Adabas Online System (AOS) selectable unit into a Natural system file by running the ADAINPL job. Alternatively, install the AOS demo version delivered with Adabas (job I061, steps 0111 and 0112). | |
| 11 | Terminate the Adabas nucleus with an ADAEND operator command. | |
| 12 | Back up the database by running the ADASAV utility job. |
The following table describes most of the libraries included on the release tape. Once you have unloaded the libraries from the tape, you can change these names as required by your site, but the following lists the names that are delivered when you purchase Adabas for BS2000 environments.
| Library Name | Description |
|---|---|
| ADAvrs.ECnn | The Adabas library containing character encoding members to support various languages and Unicode. The vrs in the library name represents the version of Adabas. The nn letters in the library name represents a number from "00" to "99", assigned by Software AG. |
| ADAvrs.EMPL | The Employees demo file, containing dummy employee data you can use for testing Adabas. The vrs in the library name represents the version of Adabas. |
| ADAvrs.ERRN | Error messages for the Adabas Triggers and Stored Procedures Facility. These messages can be viewed using the Natural SYSERR utility. The vrs in the library name represents the version of Adabas. |
| ADAvrs.INPL | The code for Adabas Online System, Adabas Caching Facility, Triggers and Stored Procedures Facility, and various add-on demo products. The vrs in the library name represents the version of Adabas. |
| ADAvrs.JOBS | The sample job library for Adabas. The vrs in the library name represents the version of Adabas. |
| ADAvrs.MISC | The Miscellaneous demo file, containing dummy miscellaneous data you can use for testing Adabas. The vrs in the library name represents the version of Adabas. |
| ADAvrs.MOD | The load library for Adabas. The vrs in the library name represents the version of Adabas. |
| ADAvrs.PERC | The Personnel demo file, containing
uncompressed dummy personnel data you can use for testing Adabas. This demo
file includes fields that make use of the extended and expanded features of
Adabas 8, include large object (LOB) fields. The vrs
in the library name represents the
version
of Adabas.
Note: |
| ADAvrs.SRC | The source library for Adabas. The
vrs in the library name represents the
version
of Adabas.
For a complete list of the time zones supported by Adabas in any given release, refer to the TZINFO member in this Adabas library. |
| ADAvrs.TZ00 | The time zone library for Adabas. The
vrs in the library name represents the
version
of Adabas. Adabas bases its time zone library on the time zones defined in the
public domain tz database, also known as the
zoneinfo or Olson database.
For a complete list of the time zones supported by Adabas in any given release, refer to the TZINFO member in the Adabas source library (ADAvrs.SRC). |
| ADAvrs.VEHI | The Vehicles demo file, containing dummy vehicle data you can use for testing Adabas. The vrs in the library name represents the version of Adabas. |
| APSvrs.Lnnn | A Software AG internal library. The vrs in the library name represents the version of the internal library code, which is not necessarily the same as the version of Adabas. |
| APSvrs.LIB | A Software AG internal library. The vrs in the library name represents the version of the internal library code, which is not necessarily the same as the version of Adabas. |
| MLCvrs.JOBS | The sample job library for Software AG's common mainframe license check software. The vrs in the library name represents the version of the license check software, which is not necessarily the same as the version of Adabas. |
| MLCvrs.MOD | The load library for Software AG's common mainframe license check software. The vrs in the library name represents the version of the license check software, which is not necessarily the same as the version of Adabas. |
| WALvrs.MOD | The load library for Adabas components shared by Adabas and other Software AG products, such as Entire Net-Work. The vrs in the library name represents the version of Adabas. |
| WALvrs.SRC | The source library for Adabas components shared by Adabas and other Software AG products, such as Entire Net-Work.The vrs in the library name represents the version of Adabas. |
| WCAvrs.LIB | The load library for Entire Net-Work Administration, used by some of the Adabas add-on products. The vrs in the library name represents the version of Entire Net-Work Administration. |
This section provides information related to activities required prior to Adabas installation.
Before you install Adabas in a BS2000 system, you must:
define a BS2000 logon ID for Adabas that permits loading from a release or installation tape;
enable all privileges for the logon ID to allow optional operations. This includes such capabilities as priority, T/P class, and maximum virtual memory size.
When allocating direct access files, private volumes are preferred to avoid the space fragmentation that can occur with public volumes.
The Software AG internal product libraries (APS - operating system layer) are required if you intend to enable a database for universal encoding service (UES) support. For UES support, the following library must be loaded and included in the BLSLIB concatenation: APSvrs.LIB (internal product application server), updated with the last patch level (APSvrs.Lnnn).
Note:
Newer APS module libraries are updates of the original. We
advise you to copy the original, merge the new library into it, and reference
the merged library in your JCL. The new merged library must be provided twice,
with the link-name APSLIB and with the link-name BLSLIB.
Also for UES support, the following library must be loaded and included with the link name DDECSOJ in the session execution JCL: ADAvrs.ECnn, where vrs is the version of Adabas (for example, "812").
The Adabas files and libraries require the following disk space in PAM pages where vrs is the Adabas version:
| File Name | Size | Description |
|---|---|---|
| ADAvrs.MOD | 3468 | Module library |
| ADAvrs.SRC | 768 | Adabas source, macros, and example jobs |
| WALvrs.SRC | 192 | Adabas limited source, macros, and example jobs |
| WALvrs.MOD | 384 | BS2000-dependent modules for Adabas limited |
| ADAvrs.ECnn | 6816 | UES code pages |
| ADAvrs.TZnn | 768 | Time zone elements |
The Adabas database size is based on user requirements. For more information, refer to the Adabas DBA Tasks documentation. The following are suggested 2300 device cylinder and PAM page sizes for an initial Adabas database, allowing for limited loading of user files and the installation of Natural:
| Database Component | Cylinders | PAM Pages |
|---|---|---|
| ASSOR1 (Associator) | 50 | 7700 |
| DATAR1 (Data Storage) | 250 | 38000 |
| WORKR1 (Work space) | 50 | 7700 |
| TEMPR1 (temporary work space) | 25 | 3850 |
| SORTR1 (sort work space) | 25 | 3850 |
The following requirements are for internal work storage in the temporary file area. The temporary files on the link names shown below will be created automatically by the Adabas software. This applies to the Adabas nucleus, utilities, and client applications accessing the database with the DDCARD/DDKARTE data in the job deck:
| Link Name | PAM Pages on Temporary Disk |
|---|---|
| DDCARDX | 3 |
| DDKARTX | 3 |
The typical Adabas nucleus requires at least 800-1024 KB of storage to operate. The size of the nucleus partition address space may have to be larger, depending on the ADARUN parameter settings. The address space parameters for the BS2000 user ID’s JOIN entry must also be adequate. Parameter settings are determined by the user.
The minimum disk space requirements on the disk for the internal product libraries delivered with this version of Adabas are as follows:
| Library | PAM Pages |
|---|---|
| APSvrs.LIB | 2304 |
The following restrictions apply to Adabas components when located on DAB-supported volumes:
| Component | Recommendations/Restrictions |
|---|---|
| ASSO | not recommended for read caching; prohibited for write caching |
| DATA | not recommended for read caching; prohibited for write caching |
| WORK | no restrictions for read caching; prohibited for write caching |
| CLOG/PLOG/RLOG | no restrictions for read caching; prohibited for write caching |
| SORT/TEMP | no restrictions |
| Sequential input | no restrictions |
| Sequential output | no restrictions |
Use the ADACNV utility to migrate existing databases to new releases of Adabas. See Adabas Utilities for more information.
The time zone library for Adabas has been delivered containing elements with version numbers. Attempts to read these will result in the following error message:
ADANTZ .... Error Opending DD TZINFO(....)
To avoid this, remove the version numbers by issuing the following BS2000 commands:
MOD-FILE-ATTR ADAvrs.TZ00,AC=W STA-LMS O ADAvrs.TZ00,U M-E-AT (,*,*),N=(V=*U) END MOD-FILE-ATTR ADAvrs.TZ00,AC=R
Adabas release tapes available to Software AG affiliates contain all Adabas product options. The affiliates use these release tapes to create custom installation tapes for customers according to contract agreements.
For specific information about your particular release tape, refer to the Installation Notes delivered with the installation tape.
If you are installing Adabas using the Software AG System Maintenance Aid (SMA) , refer to the System Maintenance Aid documentation and to the information provided with the installation tape for specific installation instructions.
Copy the files (data sets) from the supplied installation medium to your disk before you perform the individual installation procedure for each component to be installed.
The way you copy the files depends on the installation method and the medium used:
If you use System Maintenance Aid (SMA), refer to the copy job instructions provided in the System Maintenance Aid documentation.
If you are not using SMA and want to copy the files from CD-ROM, refer to the README.TXT file on the CD-ROM.
If you are not using SMA and want to copy the files from tape, follow the instructions in this section.
This section explains how to copy all files from tape to disk.
This step is not necessary if you have already copied the library
SRVvrs.LIB from another Software AG
installation tape. For further information, refer to the element
#READ-ME in this library. The library
SRVvrs.LIB is stored on the tape as a
sequential file named SRVvrs.LIBS
containing LMS commands. The current version
vrs can be obtained from the
Software AG Product Delivery Report.
Execute the following commands to convert
SRVvrs.LIBS into an LMS library:
/IMPORT-FILE SUPPORT=*TAPE(FILE-NAME=SRVvrs.LIBS,- / VOLUME=volser, DEV-TYPE=tape-device) /ADD-FILE-LINK LINK-NAME=EDTSAM, FILE-NAME=SRVvrs.LIBS,- / SUPPORT=*TAPE(FILE-SEQ=3), ACC-METH=*BY-CAT,- / BUF-LEN=*BY-CAT, REC-FORM=*BY-CAT, REC-SIZE=*BY-CAT /START-EDT @READ '/' @SYSTEM 'REMOVE-FILE-LINK EDTSAM' @SYSTEM 'EXPORT-FILE FILE-NAME=SRVvrs.LIBS' @WRITE 'SRVvrs.LIBS' @HALT /ASS-SYSDTA SRVvrs.LIBS /MOD-JOB-SW ON=1 /START-PROG $LMS /MOD-JOB-SW OFF=1 /ASS-SYSDTA *PRIMARY
where:
tape-device is the device
type of the tape, for example, TAPE-C4, and
volser is the VOLSER of the
tape (see the Software AG Product Delivery
Report).
Call the procedure P.COPYTAPE in the library
SRVvrs.LIB to copy the procedure
COPY.PROC to disk:
/CALL-PROCEDURE (SRVvrs.LIB,P.COPYTAPE), - / (VSNT=volser, DEVT=tape-device)
If you use a TAPE-C4 device, you can omit the parameter
DEVT.
Enter the procedure COPY.PROC to copy all product files to
disk:
/ENTER-PROCEDURE COPY.PROC, DEVT=tape-device
If you use a TAPE-C4 device, you can omit the parameter
DEVT.
The result of this procedure is written to the file
L.REPORT.SRV.
Once you have installed the Adabas installation tape, you can:
Migrate an existing Adabas database to the new version; or
Install a new version of the Adabas database.
Messages or codes that occur during the installation are described in the Adabas Messages and Codes; utilities are described in the Adabas Utilities.
Use the ADACNV utility to migrate existing databases to new releases of Adabas (SMA job number I021). See Adabas Utilities for more information.
You must install a valid license file on all mainframe platforms in which your Software AG mainframe product is installed. The license file is provided as an XML document (encoding is US-ASCII) and must remain in that format -- even on the mainframe. It must not be modified. Any modification of the license file will invalidate the digital signature and the license check will fail. In the event of a check failure, please contact your Software AG technical support representative.
Note:
Thirty days before the license expires, license check failure
messages are produced. Your software product will still function, but these
messages warn you that it is time to obtain a new license.
In this step, you will prepare the license file (obtain it from e-mail or the installation tape and store it on your BS2000 system) and then install it:
The product license file is supplied on the individual customer installation tape or separately via an e-mail attachment. Before you can install the license, you must transfer it from e-mail or the installation tape and store it on a BS2000 system. This section describes how to do this for a license distributed either by e-mail or on the installation tape.
To prepare the license file from an e-mail attachment,
complete the following steps:
Transfer the license to BS2000, as described in Transferring a License File from PC to a BS2000 Host Using FTP.
Verify that the transferred license file is stored in an Adabas source library (with RECFM=F or FB and LRECL=80), taking care to preserve its format as ASCII.
To prepare the license file from the installation tape,
complete the following steps:
Verify that the license file is stored from the tape into an Adabas source library (with RECFM=F or FB and LRECL=80), taking care to preserve its format as ASCII.
Once the license file has been prepared, you can install it:
To install the product license file once it has been
transferred:
Run the LICMAKE license conversion job to load the license file into a library and assemble it.
Store the assembler output module ADALIC(R) in the job library and add this to your BLSLIB concatenation.
Note:
The Adabas 8 nucleus needs a license file to start up.
Either the license file is assembled as an object by ADALIC(R) into a library
in the DDLIB/BLSLIB chain or the license is read from the link name DDLIC. If
neither of these is the case, the nucleus will end with a DMS0A4F error because
it cannot find a link name on DDLIC.
Customize and run the ADAFRM utility job to allocate and format the Adabas database. The following must be customized:
File names for the database and libraries;
Volumes for libraries and files for the database;
Space allocation for files for the database;
The Adabas database ID and database device type(s);
Sizes of the files for each ADAFRM statement.
Customize and run the ADADEF utility job to define the global definition of the database. The following must be customized:
File names of the database and libraries;
The Adabas database ID and database device type(s);
ADADEF parameters.
Customize and run the job:
ADALODE to load the sample demo file EMPL;
ADALODV to load the sample demo file VEHI;
ADALODM to load the sample demo file MISC; and
ADALODP to compress and load the sample Personnel (PERC) demo file and its associated LOB demo file.
Note:
The Personnel demo file must be installed on a
UES-enabled database because it includes wide-character format (W)
fields.
For each job, the following items must be customized:
File names for the database and libraries;
The Adabas database ID and database device type(s);
ADALOD parameters.
Customize and run the job ADAINPL to load the Adabas Online System (AOS) into a Natural system file using the appropriate batch version of Natural (read the Adabas Online System documentation to determine its Natural requirements). The following items must be customized:
File names of the database and libraries;
The Adabas database ID and device type(s);
The Natural INPL parameters and system file number.
Alternatively, install the AOS demo version delivered with Adabas: see the section Installing the AOS Demo Version.
Customize and run the ADASAV utility job to back up the database. The following must be customized:
File names of the database and libraries;
The Adabas database ID and device type(s);
ADASAV parameters.
The member DEFAULTS in the Adabas job library can be modified to set the ADARUN defaults. The following must be customized:
File names of the database and libraries;
ADARUN user defaults:
Device type(s) (default: 2300)
Database ID (default: 1)
ID Table Name (default: ADABAS5B)
Customize and run the DEFAULTS job to set the ADARUN defaults using the zap utility.
Refer to the section Installing Adabas With TP Monitors for a description of the TP link routine procedure.
The installation of a supervisor call (SVC) to provide a communication environment for Adabas is not required on BS2000 systems. Adabas uses the BS2000 executive services common memory pool and eventing for interprocess communication.
If the common memory pool should not be the default, set the ADARUN or DDLNKPAR IDTNAME parameter or reassemble SSFB2C after setting the parameter IDTNAME in the macro B2CONFIG.
The rules to determine which IDTNAME is used are as follows:
If it is a client program and the link name DDLNKPAR is present, the IDTNAME is taken from this file.
Otherwise (if the condition in #1 is not met), if the link name DDCARD is present, the IDTNAME is taken from this file.
Otherwise (if the conditions in #1 and 2 are not met), the IDTNAME is taken from module SSFB2C.
Note:
If the application is running in a subtask, for example, the
Natural program in triggers and stored procedures, this file must be a
permanent (not a temporary) file.
The router functions are implemented in the form of subroutines contained in the module ADARER. ADARER is loaded into common memory pool during nucleus initialization, and is shared by all user tasks that issue Adabas calls.
For those systems running an earlier Adabas WAL library but that wish to run with the environment from the current version, the current version's system must be started first in order to create the router (ADARER) required for the current version's nucleus.
The new default device type is 2300. All devices have standard block sizes that are a multiple of 4 and rounded to a 2K boundary. Thus they can be used on NK4 disks and D3475-8F devices.
If you do not wish to migrate the default device used by prior
releases of Adabas (device 2000) to the new default (device 2300), then the JCL
will need to include DEVICE=2000 in the ADARUN
cards.
Spanned record files are those loaded with the ADALOD SPAN option.
Writing a record over a block boundary in such a file requires an extra 50 to 100 bytes in the Work file block. In such cases, the Work file needs to have a block size of 50 to 100 bytes larger than the Data block size.
The default device 2300 has Data and Work block sizes of 8192 bytes. Therefore, there are not enough spare bytes in default device 2301 to span records over blocks. Device 2301, however, has Data and Work block sizes of 16384 bytes, so this device can be used.
Every effort has been made to make Adabas operating system independent. However, Adabas development is done in an IBM environment and corrections and changes are prepared in this environment.
As a result, corrections are applied to Adabas modules with IMASPZAP, which determines the syntax of any zaps. When corrections must be applied to a module library at BS2000 locations, the zaps must be revised to the LMS format. The following example shows how this can be done:
To revise a zap to LMS format:
Assuming a zap in the following LMS format:
/EXEC LMS LIB ADAvrs.MOD,BOTH UPDR ADAEXAMP (a) *COR ADAEXAMP,12BC,X’47B0A123’=X’4720BAEE’ (b,c) *END END
where:
a specifies corrections to module ADAEXAMP.
b verifies the contents at location X’12BC’. The correction is applied only if the content of this location is X’47B0A123’.
c specifies a replacement value X’4720BAEE’ for the location X’12BC’.
To verify the original data at location X’12BC’ on the BS2000 system, perform the following:
/LOAD (ADAEXAMP,ADAvrs.MOD) Load module /DISPLAY L’12BC’.(L=4) Display original content %D C=ADAEXAMP.H’12BC’%XL4 (AID)
If the data displayed is different from the value given on the original VER statement, do not continue with step 3.
Run the LMS procedure.
To ensure that the last step was performed properly, perform step 2 again. This procedure should also be used for ADARUN and ADALNK zaps, described later in this section.
The control job variable (JV) is filled automatically if the statement
/DEL-JV name /SET-JOB-STEP /CRE-JV name /SET-JV-LINK *ADA,name
—is contained in the nucleus startup job control statements. The JV layout is as follows:
| Positions | Length | Representation | Contents |
|---|---|---|---|
| 1 - 128 | 128 | undefined | unused |
| 129 - 136 | 8 | alphanumeric | program name |
| 137 - 140 | 4 | numeric | user abend code |
| 141 - 145 | 5 | numeric | error number (parameter or utility) |
| 146 - 150 | 5 | numeric | Adabas response code |
| 151 - 157 | 7 | numeric | CPU time, program-related (sec.) |
| 158 - 158 | 1 | alphanumeric | blank |
| 159 - 165 | 7 | numeric | elapsed time, program-related (sec.) |
| 166 - 178 | 13 | alphanumeric | blank, reserved |
Adabas uses job switch 10. The job switch is set by ADARUN and reset if the nucleus or utility session terminates normally. It can be used for session control to indicate whether or not a termination is normal. When ADARUN is called with PROGRAM=USER, no switches are set or reset.
One or two user exits may be linked to or loaded with ADALNK:
UEXITB (pre-command) receives control before a command is passed to a target by the router 04 call.
Note:
Special commands emanating from utilities and from Adabas
Online System are marked as physical calls. These calls must be bypassed in
user exits. These calls have X‘04’ in the first byte (TYPE field) of the
command’s Adabas control block (ACB). UEXITB must check this byte and return if
it is set to X‘04’. Be sure to reset R15 to zero on return.
UEXITA (post-command) receives control after a command has been completely processed by a target, the router, or by ADALNK itself.
 |
Warning: UEXITB and UEXITA are sample user programs and are not supported under any maintenance contract agreement. |
At entry to the exit(s), the registers contain the following:
| Register | Content |
|---|---|
| 1 | Address of the UB. If the flag bit UBFINUB is reset, the contents of the halfword at Adabas + X’86’ have been moved to UBLUINFO. If those contents are greater than zero, the two bytes starting at UBINFO (UB+X’40’) have been set to zero. If UBFINUB is set, no changes can be made to the UB or ACB (except for ACBRSP). |
| 13 | Address of an 18-word save area |
| 14 | Return address |
| 15 | Entry point address: UEXITA or UEXITB |
Any registers except register 15 that are modified by the user exits must be saved and restored; the address of a save area for this purpose is in register 13.
If at return from UEXITB register 15 contains a value other than zero, the command is not sent to the target but is returned to the caller. The user exit should have set ACBRSP to a non-zero value to indicate to the calling program that it has suppressed the command: response code 216 (ADARSP216) is reserved for this purpose.
The UEXITB exit may set the UB field UBLUINFO to any lesser value, including zero; an abend occurs if the user exit sets UBLUINFO to a greater value. The UBLUINFO length cannot be changed when any other exit is used; for example, Adabas Review.
The user information received by a UEXITA exit may have been modified; this modification may include decreasing its length, possibly to zero, by any of the ADANUC user exits.
Important:
If an ADALNK batch link routine has been linked or modified
by Software AG product modules or user exits, it cannot be used in any
application startups of Adabas utility jobs or Adabas, Entire System Server,
Adabas Review Hub, or Entire Net-Work nuclei.
An exit in ADALNK for the Natural Optimizer is provided in BS2000 environments. The exit is called before the UEXITA (user exit A). The source module OPTEXIT(S) is supplied in the ADAvrs.SRC library and is already bound to the supplied ADALNK. If it is to be changed, it will have to be replaced.
By formatting a database container, the size of it is physically defined. The following rules apply:
The highest PAM Page of the database container must be less than
the HIGH-US-PA allocation in the SHOW-FILE-ATTRIBUTES
container,ALL command output.
Otherwise, accessing those pages higher than that physical limit will result in
an I/O error DMS0922. For more information, read
Device and File
Considerations.
The Associator (ASSO) must have a top RABN that is greater than 30. Data Storage (DATA) must have a top RABN that is greater than 2.
The SORT and TEMP containers need not be formatted if they are being used with the access mode OUTIN.
The time zone library is delivered with Adabas as ADAvrs.TZ00 and contains many elements of type X. If you need to load new elements into this library, modify and run job TZUPLOAD provided in ADAvrs.SRCE. This job can be adapted to load the new time zone element into the library in the correct format.
The loaded time zone element should contain the default version number (*U). If it does not, the following error occurs:
ADANTZ .... Error Opening DD TZINFO(....)
To resolve this problem, read Removing Version Numbers from Time Zone Library Elements.
Adabas User Exit 2 for BS2000 permits two methods for specifying the /ENTER-JOB job:
using a job variable containing the complete /ENTER-JOB job command;
defaulting to an ENTER-JOB RES.E.xLCO startup command.
For more information, see the description of User Exit 2 in the user exit and hyperdescriptor exit documentation.
When running Adabas, some BS2000 I/O error messages may indicate that a parameter is missing or is incorrect. These errors can be shown online by entering:
HELP-MESSAGE DMS <message-id>
The following table lists the message IDs that can occur and their explanations in an Adabas environment:
| Message | Description |
|---|---|
| 0922 | The SAM file (for example, for DDOUT1) primary and secondary allocation must be a multiple of both the standard block size (16) and of the allocation unit (3). The smallest multiple allowed is 48. The standard block size may have been changed using the ADARUN parameter QBLKSIZE. If so, the standard block size is determined by dividing the sum of the QBLKSIZE value and 2047, by 2048. |
| 0BBB | The application is using an illegal record length. The target file may need a larger block size. |
| 0D33 | While working with the link names DDCARDX or DDKARTX, the system was unable to create the temporary file allocated to these link names. Adabas uses these files as an internal repository. If permanent files are assigned to link names DDCARD and DDKARTE, this problem will not occur. Otherwise, verify that the ID in which the job is running is allowed to assign temporary files and that there is enough disk space to do so. |
| 0D99 | Parallel access to a PAM file (for example, DATA) was attempted, but the PAM file has been opened by another application. |
| 0DB1 | Refer to the 0922 description above. |
| 0DC2 | SHARUPD=YES was specified for a SAM file (for example, DDSIBA). |