The following limitations and restrictions exist in Adabas 8. Enhancements to resolve these limitations may be considered in a future release.
At this time the LUIDX and LUIXNAM parameters of the LGBLSET macro (used to set default installation values for the Adabas link routines) are not supported, even though you may see them in the sample members in installation. The documentation for these parameters has been removed for now.
The following restrictions and limitations apply to large object (LB) fields in this release:
While LB fields are supported in Adabas 8, you can only store and retrieve an entire LB field in this release. The ability to read or write an LB field from left to right with multiple calls is an option being considered for a future Adabas version.
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.
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).
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).
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.
At this time, system files do not support spanned records or the extended MU and PE field counts.
At this time, fields defined with the NB option must also be defined with either the NU or NC option.
The following restrictions and limitations apply to spanned records in this release:
The ADACDC utility does not support spanned records at this time.
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.
At this time, Adabas Review Pulse reports do not support ADARUN CLOGLAYOUT=8.
The following table lists restrictions and limitations of the Adabas 8 utilities:
| Utility | Restrictions or Limitations |
|---|---|
| ADACDC | At this time, ADACDC cannot process spanned records. When spanned records are updated, only the changed records are written to the PLOG and WORK data sets. Since ADACDC presents the changes of the record in external form, it needs to decompress the logical record starting from the beginning. However, if some early piece is missing, the decompression will not work. |
| ADACMP |
At this time, LB fields cannot be specified in the FORMAT parameter for either ADACMP COMPRESS or ADACMP DECOMPRESS. |
| ADACNV |
You cannot use ADACNV CONVERT to convert a database directly from Adabas 7.1 to Adabas 8. To do this, you must first convert the database to Adabas 7.2 or 7.4 and then convert it to Adabas 8. Likewise, you cannot use REVERT to revert a database directly from Adabas 8 to Adabas 7.1; instead, you must first revert the database to Adabas 7.4 and then from 7.4 to 7.1. 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:
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:
Note: |
| 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. |
