ADAICK Error Messages

The format indicator in the U3 element is "U" or "P", and the value in the "block-number" block is not a valid packed decimal number.

Each U3 element contains a value and an MI RABN. The first MI element (in the MI block pointed to by the U3 element) should contain the same value as the U3 element. If not, this message occurs.

This message also occurs if an MI element contains a value that does not agree with the value in the first NI element (in the NI block pointed to by the MI element).

The two-byte inclusive length at the beginning of each index block defines the logical end of that block. Each block contains variable length elements. The length of each element depends on the length of the value within the element (for NI blocks, it also depends on the ISN count).

In processing an index block (left to right), the end of each element is compared to the logical end of the block (as defined by the logical block length). If the end of the element is less than the logical end of the block, what follows is taken as the next element, and processing continues. If the block and element ends are equal, the block is considered to be correct. If the element end is greater than the block end, this message occurs.

Each MI element points to an NI block. If the first ISN in the ISN list for the first NI element in that NI block is the lowest ISN for that value, then the "MI ISN" (in the MI element) should be zero. If the MI element is not zero, this message occurs.

Each MI element points to an NI block. If the first ISN in the ISN list for the first NI element (in that NI block) is not the lowest ISN for that value, then that NI element should agree with the "MI ISN". If it does not agree, this message occurs.

In processing the index for one descriptor (in an L9 sequence), the NI block values should be in ascending sequence. This message occurs if either of the following occurs:

• The values within one block are not strictly increasing (equal values are considered an error);

• The first value in an NI, MI, or UI block is less than the last value in the previous block (equal values are allowed).

The ISN count in an NI element should not be zero.

The ISN list for one value in an NI block must be in strict ascending sequence. If not, this message occurs. This message also occurs if an ISN is not less than the "first unused ISN" specified in the file control block (FCB).

The third byte in the "block-number" block should contain the following value:

If the third byte does not contain the correct value, this message occurs.

An attempt was made to read a block outside the RABN limits specified by the general control block (GCB) Associator extents.

A "block-number" RABN is outside the RABN limits defined by the file control block (FCB) UI extents, or an NI RABN is outside the limits defined by the NI extents.

Data Storage (DS) RABN "rabn-number" appears in an address converter block and is outside the limits defined by the file control block (FCB) DS extents.

The file control block (FCB) contains the "top ISN" for each address converter (AC) extent. This is the ISN that corresponds to the last RABN in the last block for that extent. This ISN depends on the top ISN of the previous extent, on the number of blocks in the extent, and on the number of ISNs per block. If the top ISN value is incorrect, this message occurs.

Address converter elements which correspond to ISNs greater than or equal to the "first unused ISN" (specified in the FCB) must all contain 00000000 or FFFFFFFE. Otherwise, this message occurs. The ISN "isn-number" contains "value".

The requested file number, plus the RABN specified in file 1 FCB's GCB minus one, is assumed to be the FCB RABN for the requested file. The file number specified in that block does not agree with the requested file number.

The highest index level specified in the file control block (FCB) must range 3 through 15, inclusively.

The highest index RABN specified in the file control block (FCB) must be within the upper index extents (also specified in the FCB).

The extent just printed is invalid because the first RABN is greater than the last RABN.

The extent specified in the file control block (FCB) overlaps a free extent specified in the free space table (FST).

The return code "ret-code" (hexadecimal) was returned from ADAIOR after ADAICK attempted to either open the Associator or read the specified Associator block.

The file's MAXISN does not correspond to the MAXISN determined by the MAXISN value "allocated-maxisn" based on the allocated AC extents.

In performing the index check, a count is taken of the UI blocks read. The "number of blocks used" is the sum of the number of blocks used in each UI extent, which depends on the first RABN and first unused RABN for each extent. If the number of blocks processed exceeds the number used, at least one "ix-block-number" RABN occurs in more than one of that block type, because each "ix-block-number" RABN processed is checked to be sure it is within the used portion of some extent of the same index block type.

Each U3 element contains the field name for the descriptor. Field names must be in ascending sequence. "field-name" is the name of the field that is out of sequence.

Each upper-level index element contains the field name for the descriptor, and also points to a lower-level block. The field name in the first element in the lower-level block must agree with the field name in the higher-level element.

The forward pointer in an element of the empty NI/UI block chain contains an invalid RABN. This forward pointer should contain a RABN of another empty NI/UI block, or should contain a zero to indicate the end of the chain.

Every empty NI/UI block chained in the empty block chain must have a logical block size of X'0005'. This includes the length field itself (two bytes) and the logical forward pointer to the next block in the chain (three bytes).

The forward pointer in an element of the empty NI/UI block chain contains an invalid RABN. This forward pointer should contain either a RABN of another empty NI/UI block, or a zero to indicate the end of the chain. However, there is an invalid forward pointer value causing the chain to return into itself.

A descriptor was found in a U3 block that is not in the field definition table (FDT). Every field in the index must be a descriptor, a sub-/super-/hyper- or phonetic descriptor, or a coupling descriptor if the file is coupled.

Every descriptor, sub-/super-/hyper- or phonetic descriptor, or coupling descriptor must have at least one entry in a U3 block. If there are no values for this descriptor, an empty element is stored (value length=0, ISN=0, RABN=0).

A discrepancy was found between the address converter and Data Storage. For better analysis of the problem, run the ADAACK utility.

The physical ISN found in a Data Storage record is either zero or is greater than the permitted maximum for the file.

While decompressing a Data Storage record, ADAICK reached the end of the field definition table (FDT) before finding the end-of-record. This indicates that the compressed record has an incorrect structure.

Either the block length of a Data Storage block is wrong, or the length of a record stored within this block is wrong. The sum of all record lengths, plus 4, should equal the logical block size of the Data Storage block.

A periodic group count in a compressed Data Storage record is either 0 or greater than 191.

A multiple-value field count in a compressed Data Storage record is either 0 or greater than 191.

The value for an empty field counter is a compressed Data Storage record that contains X'C0'. Any value from X'C1' through X'FF' is permitted.

The length of a value in a compressed Data Storage record is wrong. A valid length value is either X'01' through X'7F' or X'8001' through X'80FF'.

A packed value within a compressed Data Storage record contains invalid digits.

If a descriptor has no values/ISNs, a value of X'00' is stored in the U3 block to indicate an empty descriptor. The following values for MIRABN and ISN must be zero.

The value for the rotating ISN must be less than or equal to the highest ISN, plus 1.

There are at least two U3 entries for an empty descriptor. Each descriptor has at least one entry on the U3 level. There may be several entries for one descriptor when the descriptor spans several MI blocks, because each MI block has an entry on the U3 level. Although there are no MI blocks for an empty descriptor, there must be one (and only one) U3 entry.

The field descriptor table (FDT) contains an entry pointing to the last parent field of a super- or hyperdescriptor. The pointer contains the wrong value.

An index block exists that is neither used nor in the unused RABN chain.

No immediate action is needed; however, the RABN block cannot be used until either the Associator is reordered or an UNLOAD/LOAD sequence is performed.

An error occurred while the collation descriptor user exit was being initialized.

Investigate the cause of the error; correct it; and rerun the job.

The collation descriptor user exit requested is not loaded.

Load the exit and rerun the job.

The value for number of ISNs per address converter (AC) block must be the AC block size in bytes divided by the size of the ISN: either 3 or 4 bytes.

Correct the value provided in the file control block (FCB).

The upper index blocks contain index entries for one or more descriptors. The first element for a given descriptor contains the first element bit or FE BIT. A missing FE bit can result in incorrect index positioning or Adabas response codes.

Document the error. Try to fix the error as soon as possible, for example by reinverting the descriptor where the error occurred.

An FDT and index control byte mismatch occurred for the description (dd) listed in the message. The comparison of the two compares the control byte IXUCTL of the index with the control byte FDTF of the FDT.

When this error occurs, dump and print the FDT using the ADAICK FDTPRINT utility. Then contact your Software AG support representative for assistance.

The length fields found in FDTHLL and YFDTL are not equal. The file number is given in the message.

When this error occurs, dump and print the FCB using the ADAICK FCBPRINT utility for the file listed in the message. Then contact your Software AG support representative for assistance.

This error can have two different messages, as described in the following table:

These messages may occur after an ADAICK DATAPRINT or ADAICK DSCHECK run.

For either error message, run ADAICK GCBPRINT. If you receive the second message (RABN rabn NOT IN EXTENT, FILE file), also run ADAICK FCBPRINT for the file named in the message.

Then contact and send the output from these runs (as appropriate) to your Software AG support representative for assistance.