Guardian Procedure Calls Reference Manual

infosize
output
INT .EXT:ref:1
returns the size in bytes of the information stored in the infobuf parameter.
Returned Value
INT
A file-system error code that indicates the outcome of the call.
Considerations
• In H06.28/J06.17 RVUs with specific SPRs and later RVUs, the value returned by the infomax
parameter, which indicates the size of the file synchronization block for the specified filenum
, has been increased to support enhanced key-sequenced files and format 2 legacy
key-sequenced files that use increased key size limits. (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).)
◦ For nondisk files, except the Transaction Monitoring Facility (TMF) transaction pseudofile
(TFILE), the size must be at least 10 bytes. For the TMF product, the size must be at least
30 bytes.
◦ For non-key-sequenced disk files with 16 or less partitions, the size must be at least 44
bytes.
◦ For legacy key-sequenced files without alternate keys, the size must be the sum of the
primary-key length and 44 bytes.
◦ For legacy key-sequenced files with alternate keys, the size must be at least the primary-key
length plus the maximum alternate-key length and 44 bytes. The primary-key length is
eight bytes for non-key-sequenced files, and the maximum alternate-key length is the
maximum value of all the alternate keys for the file.
◦ For enhanced key-sequenced files without alternate keys, the size must be the sum of the
primary-key length and 100 bytes.
◦ For enhanced key-sequenced files with alternate keys, the size must be at least the
primary-key length plus the maximum alternate-key length and 100 bytes. The maximum
alternate-key length is the maximum value of all the alternate keys for the file.
◦ For any supported file type, an infomax value of 4196 is sufficient. The maximum
possible value is an enhanced key-sequenced file with 128 partitions, a maximum
primary-key length of 2048, and a maximum alternate-key length of 2048 (100 bytes +
2048 bytes + 2048 bytes = 4196 bytes).
• For earlier RVUs, the size of the infomax parameter must meet these limits:
For nondisk files, except the Transaction Monitoring Facility (TMF) transaction pseudofile
(TFILE), the size must be at least 10 bytes. For the TMF product, the size must be at least
30 bytes.
◦
◦ For non-key-sequenced disk files, the size must be at least 44 bytes.
◦ For key-sequenced files, the size must be the sum of the primary-key length and 44 bytes.
◦ For files with alternate keys, the size must be at least the primary-key length plus the
maximum alternate-key length and 44 bytes. The primary-key length is 8 bytes for
448 Guardian Procedure Calls (F)