Limitations and Restrictions

#### Search Results

Search

# Limitations and Restrictions

The following limitations and restrictions exist in this version of Adabas. Enhancements to resolve these limitations may be considered in a future release.

1. The following restrictions and limitations apply to large object (LB) fields in this release:

   - At this time, character conversion of LB field values from one code page to another is not supported. This functionality may be considered in a future release.

   - Some utility parameters are not supported for files containing LB fields. For more information, refer to the documentation for the utility and to the utility limitations and restrictions, provided later in this document.

   - At this time, large object (LB) fields can be define only with format A.

2. The new format buffer length indicator is only supported for LA and LB fields. Future versions of Adabas will consider supporting the specification of the length indicator for other fields too. For more information about the format buffer length indicator, read Length Indicator (L).

3. The prefetch feature is not supported in ACBX interface direct calls -- it will not support ACBX calls with multiple buffers; you should use the multifetch feature instead. However, the prefetch feature still supports ACB interface direct calls.

4. At this time, system files do not support spanned records or the extended MU and PE field counts.

5. At this time, fields defined with the NB option must also be defined with either the NU or NC option.

6. The following restrictions and limitations apply to spanned records in this release:

   - The ADAULD utility does not support spanned records on ADAULD SAVETAPE runs.

   - At this time, ADAM files do not support spanned records.

   - System files do not support spanned records at this time.

   - The number of records that comprise a spanned record is limited. The Adabas nucleus allows up to five physical records (one primary record and four secondary records) in a spanned record. If you need more space, try relocating the Data Storage of the file to a different device type with a larger block size.

   For more information about spanned record support in Adabas, read Spanned Record Support.

7. At this time, Adabas Review Pulse reports do not support ADARUN CLOGLAYOUT=8.

8. The following table lists restrictions and limitations of the Adabas utilities:

   Utility | Restrictions or Limitations
   --- | ---
   ADACMP | At this time, LB fields cannot be specified in the FORMAT parameter for either ADACMP COMPRESS or ADACMP DECOMPRESS if the LOBVALUES parameter is set to YES.
   ADACNV | ADACNV will not allow you to REVERT the database to Adabas 8.2 if any of the following apply: The database contains a Security file in which a password is or was defined that applies to more than 191 files or relates to more security-by-value criteria than fit into a single data storage record. (This condition persists even if that password is deleted.) The database contains a file in which a system field of type SECUID is defined. For information about reverting back to versions prior to Adabas 8.2, refer to the Adabas 8.2 Release Notes. To access a copy of these, read Documentation and Other Online Information.
   ADALOD | The MIXDSDEV parameter is not supported in an ADALOD LOAD run if the file you are loading is a LOB file or may contain spanned records. You cannot use the DDISN or DELISN parameters in an ADALOD UPDATE function to delete records in a LOB file. Furthermore, you can only use these parameters to delete records in a base file of a LOB group if the records to be deleted contain no references to LOB values longer than 253 bytes which are stored in the LOB file. (ADALOD will terminate with an error if such a LOB value is encountered.)

9. BS2000 database communication can support a maximum of 32,767 buffers in the ABD list. Read Adabas Buffer Descriptions (ABDs) for more information. ABD lists with more than 32,767 buffers will result in a response code 152.