Version 8.2.5	SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

The following limitations and restrictions exist in Adabas 8. 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. At this time, when specifying an Adabas buffer description (ABD), you must specify the same value for the number of bytes sent to Adabas (ABDXSEND field) as you specify for the maximum buffer size (ABDXSIZE field).

4. 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.

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

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

7. 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 8, read Spanned Record Support.

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

9. The following table lists restrictions and limitations of the Adabas 8 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.
   ADACNV	If a database makes use of any of the following extended features of Adabas 8.2, ADACNV will not allow you to REVERT the database to a version prior to Adabas 8.2: UQDE option of one or more fields of a file was removed. If a database makes use of any of the following extended features of Adabas 8, ADACNV will not allow you to REVERT the database to a version prior to Adabas 8: More than five ASSO, DATA, or DSST extents More than five file extents Files that allow spanned records Files that allow more than 191 MU and PE occurrences Files that make use of LB fields Files with fields that have the NB (no blank compression) option System files with two-byte file numbers. If you want to complete the backward conversion (reversion), you must first remove any file with these new features from the Adabas database. The use of the following other new features provided in Adabas 8 do not prevent backward conversion to Adabas 7.4, but, of course, the new features cannot be used in Adabas 7.4: Adabas commands issued via the ACBX interface (for example, with long or segmented buffers) Commands using the new format buffer features (for example, the length indicator). Note: There may be files in a database that are not loaded but that have a Field Definition Table (FDT) stored in the FDT blocks. If ADACNV encounters such FDTs while converting a database to Version 8, they are deleted as part of its cleanup processing.
   ADALOD	The MIXDSDEV parameter is not supported in an ADALOD LOAD run if the file you are loading is LOB file or contains spanned records or extended MU or PE fields. Spanned records are based on the data storage block size. If you use a mixture of device types (as allowed by the MIXDSDEV parameter), your spanned records would end up with different record lengths, which is not allowed. You cannot use the DDISN or DELISN parameters in an ADALOD UPDATE function to delete records in a LOB file. However, you can use these parameters against a base file of a LOB group unless one or more of the records to be deleted contain references to LOB values longer than 253 bytes which are stored in the LOB file (ADALOD will terminate with an error if such a request is made).
   ADAULD	For this release, you cannot unload from a SAVETAPE if the file you are trying to unload contains spanned records.

10. The BS2000 time zone library (ADAvrs.TZ00) has elements released with version numbers. The leads to the error:

    ADANTZ .... Error Opening DD TZINFO(....)

    This can be corrected as described in Removing Version Numbers from Time Zone Library Elements.

www.softwareag.com

Copyright © 1971-2013 Software AG, Darmstadt, Germany.

SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT