Guardian Procedure Calls Reference Manual

Considerations
• Invalid file names
It is the responsibility of the program calling FNAMECOLLAPSE to pass a valid file name in
internal-name. Invalid file names cause unpredictable results such as retrieving information
from the wrong file.
• Passing a bad sysnum value
If internal-name is in network form, and the system number in the second byte does not
correspond to any system in the network, FNAMECOLLAPSE supplies "??" as the system name.
• System names as filenames
The procedure does not always produce system names that will work properly as a file name.
For example, the internal file name for an unnamed process produces a printable string;
however, the string is not acceptable as a file name.
Example
In the following example, if INTNAME is passed in local internal form, for example:
$SYSTEM SUBVOL MYFILE
it converts to the external local form:
$SYSTEM.SUBVOL.MYFILE
If INTNAME is passed in network form, for example:
\sysnumSYSTEMSUBVOL MYFILE
it converts to the external network form:
\system-name.$SYSTEM.SUBVOL.MYFILE
LENGTH := FNAMECOLLAPSE ( INTNAME , EXTNAME );
614 Guardian Procedure Calls (F)