Guardian Procedure Calls Reference Manual

Table 18 FILE_GETINFOLIST_ Item Codes (continued)
DescriptionSize (Bytes)Item
Code
Tape process: Length in bytes of attribute 3105. 0 if no tape is mounted or the tape does not
have labels.
23104
Tape process: Current labels Beginning-of-file-section label group (HDR1, HDR2) of the current
file.
up to 1603105
1
Item code 235 is supported only on systems running H-series or J-series RVUs.
Considerations
• Normally if an error is returned, the contents of the result parameter are undefined. However,
if the returned error code is 2 (operation invalid for file type), the result parameter contains
a combination of correct values (for valid items) and unchanged memory locations (for invalid
items because of the kind of file). The error-item value points to the first invalid item.
When error 2 occurs, any items prior to the one pointed to by error-item are returned
with correct values in the result parameter; following items might or might not be valid. If
a following item is known to be valid because of the kind of file involved, the correct result
value for the item can be accessed in the corresponding location in the result buffer. To
do so, the program will have to account for space in the buffer reserved for preceding invalid
items as well as for space for preceding valid items. (Preceding in this case refers to some
item that occurs before the item in question.) See Table 18 to determine the kinds of files for
which an item is valid.
Invalid items that are fixed-size will have the amount of space reserved in the result buffer, but
that section of buffer will be unchanged. Invalid items that are variable-sized have no space
reserved for them, but this should not be depended upon because they could become valid
in a future RVU and thus start occupying space. The programmer might want to place all the
items that could cause error 2 in the item list after those that are not expected to cause this
error.
• If a file number for which information is being retrieved was opened with the unstructured
access option, the provided information appears as if the file is an unstructured file without
partitions or alternate keys.
• The file system stores error information for the last operation that was not associated with a
file number (such as a purge, waited open, or failed create operation; the result of a preceding
awaitio[x] or alter operation is also stored). You can obtain this stored information from
FILE_GETINFOLIST_ by supplying a value of -1 for filenum. The error information is returned
in items 7 through 10. Valid values are also returned for items 19 and 20.
• The FILE_GETINFOLIST_ procedure should not be used to determine, the current-key-value
parameter for queue files (item code 15), because a current key position is not maintained
for queue files.
• Support for SQL files includes both format 1 and format 2 files.
• If the file being referenced is a format 2 file and the extent size exceeds 65535, item codes
will return -1 with no error indication.
• For all items in Table 18 that return some form of last modification time, creation time is
returned for an object that has never been modified. Similarly, for items that return some form
of last open time, creation time is returned for an object that has never been opened.
• Buffer considerations for format 2 key-sequenced files with increased limits
In H06.28/J06.17 RVUs with specific SPRs and later RVUs, format 2 legacy key-sequenced
files and enhanced key-sequenced files can be created with increased file limits. (For a list of
the required H06.28/J06.17 SPRs, see SPR Requirements for Increased Enscribe Limits for
FILE_GETINFOLIST_ Procedure 427