Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (F)
Guardian Procedure Calls Reference Manual—522629-013
5-191
FILENAME_MATCH_ Procedure
-2 Missing pattern parameter
-3 Length error on
filename parameter
-4 Length error on
pattern parameter
-5 Bounds error on
generic-set parameter
filename:length input:input
STRING .EXT:ref:*, INT:value
is one or more contiguous sections of a valid file name that is to be tested for a
match with
pattern. The value of filename must be exactly length bytes
long. It must have the same level of left-hand qualification as
pattern or else a
match cannot result (for example, if
pattern starts with a node-name section,
filename must have a node name). See caution under “Considerations.”
pattern:length input:input
STRING .EXT:ref:*, INT:value
is one or more contiguous sections of a valid file-name pattern to be matched. The
value of
pattern must be exactly length bytes long. Refer to Appendix D, File
Names and Process Identifiers for the definition of file-name pattern. See caution
under “Considerations.”
generic-set output
INT .EXT:ref:1
if
status is 0, returns a value indicating whether filename is a member of, falls
before, or falls after the generic set of names defined by
pattern. A name is part
of the generic set if it matches
pattern up to the first wild-card character (* or ?).
Valid values are:
-1 The name falls before the first possible match.
0 The name falls within the set of possible matches.
1 The name falls after the last possible match.
Considerations
•
filename and pattern must have the same level of left-hand qualification. For
example, if
pattern has a node-name section, filename matches only if it
contains a node name. FILENAME_MATCH_ does not support file-name
resolution with current default values; you can use the FILENAME_RESOLVE_
procedure to resolve partially qualified file names prior to calling
FILENAME_MATCH_.
•
Matching is syntactic only and does not involve lookups of actual processes, logical
devices, or other entities.
Caution. Passing an invalid file name or file-name pattern to this procedure can result in a
trap, a signal, or data corruption. To verify that a file name or file-name pattern is valid, use the
FILENAME_SCAN_ procedure.