HP 3000 Manuals HP 3000 Manuals
Accessing a File by Its File Name
MPE/iX intrinsics that access a file by its file name require that you
pass the file name string in the formaldesignator parameter. Some of
these intrinsics have additional parameters that either pass or return
file name strings. Most, but not all, parameters have been enhanced to
accommodate HFS syntax.
Enhanced intrinsic parameters
The following MPE/iX intrinsics have been enhanced to accommodate a file
name string that uses either MPE syntax or HFS syntax.
Table 4-4. Intrinsic Parameter Enhancements
--------------------------------------------------------------------------------------------
| | |
| Intrinsic | Enhancement |
| | |
--------------------------------------------------------------------------------------------
| | |
| FFILEINFO | Item number 80 (new) |
| | |
--------------------------------------------------------------------------------------------
| | |
| FLABELINFO | formaldesignator parameter and item number 38 (new) |
| | |
--------------------------------------------------------------------------------------------
| | |
| FOPEN | formaldesignator parameter |
| | |
--------------------------------------------------------------------------------------------
| | |
| FRENAME | formaldesignator parameter |
| | |
--------------------------------------------------------------------------------------------
| | |
| HPACDINFO | Item number 1 |
| | |
--------------------------------------------------------------------------------------------
| | |
| HPACDPUT | Item numbers 1, 2, and 15 |
| | |
--------------------------------------------------------------------------------------------
| | |
| HPFOPEN | Item numbers 2, 41, 51, and 52 (filereference parameter |
| | only) |
| | |
--------------------------------------------------------------------------------------------
| | |
| STACKDUMP | formaldesignator parameter. However, pathname must |
| | resolve to an MPE group. |
| | |
--------------------------------------------------------------------------------------------
In the above intrinsics, file names specified using HFS syntax must
conform to HFS syntax rules, described in Chapter 2.
For additional information about these intrinsics, refer to the
appropriate intrinsic descriptions located in the MPE/iX Intrinsics
Reference Manual (32650-90028).
Special enhancements to HPFOPEN
The HPFOPEN intrinsic provides an optional exception to the rule for
specifying file names using HFS syntax. HPFOPEN item number 41 enables
you to pass a value that indicates how HPFOPEN should interpret a file
name passed in item numbers 2 or 51. The following table describes item
number 41:
Table 4-5. HPFOPEN Item Number 41
--------------------------------------------------------------------------------------------
| | |
| Value | Meaning |
| | |
--------------------------------------------------------------------------------------------
| | |
| 0 MPE-Escaped | Default. If the first character is either a dot "." or a slash |
| | "/", use HFS syntax to interpret the pathname. Otherwise, use |
| | MPE syntax to interpret the file name. |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1 MPE only | Use only MPE syntax to interpret the file name. The name must |
| | be in the MPE name space. |
| | |
--------------------------------------------------------------------------------------------
| | |
| 2 HFS | Use HFS syntax to interpret the pathname. |
| | |
--------------------------------------------------------------------------------------------
A dot (".") is not required to indicate a relative pathname (a pathname
relative to the current working directory), although it is allowed. File
name strings are interpreted literally as HFS pathnames (that is, no
upshifting occurs, and HFS nonalphanumeric characters are allowed).
For example, if the process's current working directory pathname is
/dir1/dir2/dir/ and the specified pathname is dir4/dir5/Myfile, HPFOPEN
prepends the current working directory pathname to the specified pathname
prior to pathname resolution and searches for the file using the pathname
/dir1/dir2/dir/dir4/dir5/Myfile.
For additional information, refer to the HPFOPEN intrinsic description
located in the MPE/iX Instrinsics Reference Manual (32650-90028).
Restricted intrinsic parameters
The following MPE/iX intrinsics have not been enhanced to accommodate a
file name string that uses HFS syntax. File names must be specified
using only MPE syntax.
Table 4-6. Restricted Intrinsics
--------------------------------------------------------------------------------------------
| | |
| Intrinsic | Restriction |
| | |
--------------------------------------------------------------------------------------------
| | |
| CATOPEN | File name string passed in formaldesignator parameter must |
| | use MPE syntax |
| | |
--------------------------------------------------------------------------------------------
| | |
| FFILEINFO | Item number 1 |
| | |
--------------------------------------------------------------------------------------------
| | |
| FGETINFO | formaldesignator parameter |
| | |
--------------------------------------------------------------------------------------------
| | |
| FLABELINFO | Item number 1 |
| | |
--------------------------------------------------------------------------------------------
| | |
| FPARSE | formaldesignator parameter |
| | |
--------------------------------------------------------------------------------------------
For additional information about these intrinsics, refer to the
appropriate intrinsic descriptions located in the MPE/iX Intrinsics
Reference Manual (32650-90028).