Guardian Procedure Calls Reference Manual
if present, returns a block of five words that might contain information about the entity designated
by name. Note that some of the fields do not apply to all kinds of entities. (None of them apply
to nodes.) The fields are:
Device type.[0]
Device type.[1]
Device-specific information. When the device type is 3 (disk), the meanings are:[2:4]
Object type. If greater than 0, this is an SQL object; if equal to 0, this is a non-SQL disk file; if equal to
-1, this is an entire volume or subvolume.
[2]
File type. If the entity is a disk file, this is the file type (0 = unstructured, 1 = relative, 2 = entry-sequenced,
3 = key-sequenced); otherwise it is -1.
[3]
File code. If the entity is a disk file, this is the file code given to the file; otherwise it is -1.[4]
For other device types, words [2:4] are not currently defined.
tag
input
(for FILENAME_FINDNEXT_)INT(32):value
(for FILENAME_FINDNEXT64_)INT(64):value
specifies a tag value that, when the procedure is used in a nowait manner, is returned in the
completion message. If this parameter is omitted for FILENAME_FINDNEXT_, the value 0D is
used. If this parameter is omitted for FILENAME_FINDNEXT64_, the value 0F is used. If the
procedure is not used in a nowait manner, this parameter is ignored. For details, see Nowait
Considerations.
Returned Value
INT
A file-system error code that indicates the outcome of the call; error 1 (end of file) indicates that
no more names are available.
Considerations
• EpTAL callers must set the toggle _64BIT_CALLS before sourcing the FILENAME_FINDNEXT64_
procedure section from EXTDECS.
• The sequence of names returned by the FILENAME_FINDNEXT[64]_ procedures does not have
any specific order; in particular, the names might not come back in alphabetical order. Each
kind of name part (for example, node or subvolume) has some order that is consistent for any
RVU but might change from RVU to RVU.
• For a certain class of errors, you have the option of continuing the search even though some
of the names cannot be returned. (This includes generic offline errors. For a discussion of
generic offline errors, see the FILENAME_FINDSTART_ Procedure (page 578).) Errors of this
class can be recognized by the fact that even though an error is indicated by the returned
error value, a name is still returned in name and name-length is nonzero.
For these errors, the name returned is that of the entity associated with the error (for example,
the node or device). It is generally not a name of the form being searched for but is a name
to be used for error-reporting purposes. If you continue the search after one of these errors
occurs by again calling FILENAME_FINDNEXT[64]_, the set of names subordinate to the entity
in error is skipped and the search proceeds to the next entity at that level. For example, if a
device caused the error, a further search skips all subdevices on that device and proceeds to
the next device.
576 Guardian Procedure Calls (F)










