Guardian Programmer's Guide

Table Of Contents
Using the File System
Guardian Programmer’s Guide 421922-014
2 - 4
Process Files and $RECEIVE
Process Files and $RECEIVE
The file system allows you to open and access processes as files. A process can open
another process using a process file name and then send data to the process by
writing to the open file.
A process can receive data from other processes by opening a file using the special
file name “$RECEIVE.” Through $RECEIVE, you can read not only messages from
other processes but also operating-system messages.
Section 6, Communicating With Processes, provides details on how processes
communicate with each other.
File Names
Every file has at least one unique name by which the file is accessed. (Devices other
than disks, but not subdevices, have two names—a regular file name and a logical
device number). The file name is used by a process when gaining access to (or
opening) a file. The file is named when the file is created.
The file name is unique not only on the system where the file is physically located but
also within the system’s network.
Some differences exist between the form of file name you use to access a file
programmatically and the form of file name you use interactively. The syntax
definitions given here apply to programmatic access.
The rules for naming a file depend on whether you are naming a disk file, a device file,
or a process file. The rules for each of these entities are given in the following
paragraphs. Generally, the following rules apply:
File names are made up of alphanumeric characters but can also include some of
the following special characters when used as delimiters:
\ $ # : .
File names are not case-sensitive; $OURVOL.MYSUBVOL.MYFILE refers to the
same file as $ourvol.mysubvol.myfile.
Permanent Disk-File Names
Permanent disk files are named when they are created. Once a permanent disk file is
created, it remains on disk until explicitly purged. File creation is discussed later in this
section.
The name of a disk file when fully qualified consists of four parts: the node name, the
volume, the subvolume, and the file ID. Periods separate the parts from each other.