SQL/MP Messages Manual

File-System Messages
HP NonStop SQL/MP Messages Manual—427720-006
16-3
SQL 579
Cause. The record size specified 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 on the file
creation request. The largest supported record size in a format II file is slightly less
than in a standard format file for a given block size.
SQL 580
Cause. A relative, entry sequenced, or unstructured file having a potential size of over
four gigabytes was attempted to be opened without use of the special indicator that the
program will use 64-bit keys instead of 32-bit keys.
Effect. The requested operation is not performed.
Recovery. Update the application to use 64-bit keys. This involves changing usages
of 32-bit key values to 64-bit, replacing calls to 32-bit procedures (such as POSITION)
with calls to equivalents (e.g. FILE_SETPOSITION_), and setting a 64-bit indicator in
the FILE_OPEN_ call.
If the file does not contain nor need to contain more than 2GB of data, an alternative is
to reduce the maximum file size, for instance by reducing the maximum number of
extents.
SQL 581
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 which got the
error with an equivalent which accepts use of 64-bit keys. Alternatively, turn off the
FILE_OPEN_ indicator specifying use of 64-bit keys (but then the application will not
be able to access non-key-sequenced files which are 4GB or larger).
579 The record size specified is too large for the given
block size, file type and format.
580 An open failed because the file was oversize and the
opener did not specify use of 64-bit primary keys.
581 An operation involving 32-bit primary keys was attempted
on an open which specified use of 64-bit keys.