Guardian Procedure Errors and Messages Manual

Cause The specified block size is too large.
Effect The requested operation is not performed.
Recovery Reduce the block size specified in the file creation request to an acceptable value. For
format 1 files and other file types, the largest allowed value is 4096 bytes. However, for format
2 key-sequenced files, the largest allowed value is 32,768 bytes.
579 (%1103) The record size specified is too large for the
given block size, file type and format.
Cause The specified record size is too large for the given block size, file type and format.
Effect The requested operation is not performed.
Recovery Increase the block size or reduce the record size specified in the file creation request.
The largest supported record size for a format 1 file is 4062 bytes. For a format 2 file, the largest
supported record size is 27,648 bytes in H06.28/J06.17 RVUs with specific SPRs and later RVUs.
Otherwise, it is 4040 bytes in H06.27/J06.16 and earlier RVUs.
For a list of the required H06.28/J06.17 SPRs, see “SPR Requirements for Increased Enscribe
Limits for the H06.28/J06.17 Release” (page 15).
580 (%1104) An open failed because the file was oversize and
the opener did not specify use of 64-bit
primary keys.
Cause An open failed because the file was a format 2 file and the opener did not specify use of
64-bit primary keys. An attempt was made to open a relative file, an entry-sequenced file, or an
unstructured file with a potential size of over 4 gigabytes without use of a special indicator specifying
that the program was using 64-bit keys rather than 32-bit keys.
Effect The requested operation is not performed.
Recovery Update the application to use 64-bit keys. This involves changing the use of 32-bit key
values to 64-bit values, replacing calls to 32-bit procedures (such as POSITION) with equivalent
procedure calls (for example, FILE_SETPOSITION_), and setting a 64-bit indicator in the FILE_OPEN_
procedure call. If the file does not contain and does not need to contain 4 GB of data, an alternative
is to reduce the maximum file size (for example, reducing the maximum number of extents).
581 (%1105) An operation involving 32-bit primary keys was
attempted on an open which specified use of
64-bit keys.
Cause An operation involving 32-bit primary keys was attempted on an open which specified use
of 64-bit keys.
Effect The requested operation is not performed.
Recovery Correct the application by replacing the 32-bit procedure call that caused the error with
an equivalent procedure call that accepts the use of 64-bit keys. Alternatively, turn off the
FILE_OPEN_ procedure indicator that specifies the use of 64-bit keys. The second option does not
allow the application to access non-key-sequenced files that are 4 GB or larger.
582 (%1106) Alternate key information could not be returned
because it cannot be expressed in the superseded
format of the parameter.
Cause Alternate key information was not returned because it cannot be expressed in the superseded
format of the parameter. For instance, if an alternate key field has an offset greater than 4095,
Error Code Descriptions 69