Guardian Procedure Calls Reference Manual

– The address was in an extended data segment, but either the segment ID was not
allocated, the segment ID was an invalid segment number, or there was a bounds
error on the area.
– The total message size was too large (over 32.5 kilobytes for a TNS process or 50
kilobytes for a native process).
– An invalid combination of parameters occurred:
There was a count, but no buffer; or
there was a buffer, but no count; or
there was a buffer and a segment ID, but no count.
• Increased file limits for key-sequenced files
The CHECKPOINTX procedure can checkpoint the file synchronization blocks of file numbers
passed to it in the segment-idn parameters. In H06.28/J06.17 RVUs with specific SPRs and
later RVUs, the limits of the following file attributes for format 2 legacy key-sequenced files
and enhanced key-sequenced files have been increased, which can result in file synchronization
blocks with larger maximum sizes. (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 31).)
◦ The file synchronization blocks support synchronization IDs for a maximum of 127
partitions of an enhanced key-sequenced file; earlier RVUs only support a maximum of
64 partitions.
◦ The maximum key size for format 2 legacy key-sequenced files and enhanced
key-sequenced files is 2048 bytes, and the current key is part of the file synchronization
block; earlier RVUs only support a maximum key length of 255 bytes.
As a result of these increased limits, more memory may be required to checkpoint file
synchronization blocks, which can potentially reduce the number of file opens that can be
checkpointed in a single CHECKPOINTX call and cause “message too large” errors to occur
at lower thresholds than previously.
160 Guardian Procedure Calls (C)