HP NonStop G-Series - Manual (Page 70)

NOE
Causes the /E directory to be invisible to the specified command.
NOG
Causes the /G directory to be invisible to the specified command.
NOG:NOE
Causes both /E and /G directories to be invisible to the specified command.
NOTE: The value NOE:NOG is not valid and is ignored.
For example, enter the following command to specify that the Expand directory (/E) and the
Guardian directory (/G) are to be invisible to the command chgrp.
export UTILSGE=NOG:NOE
chgrp -R SUPER.SUPER/
In this example, the group of all the files on the local node is being changed to the super ID. The
recursive flag (-R) must be specified and the initial directory must be the root directory for this
command to be effective.
The chgrp, chmod, chown, cp, find, ls, mv, pax, and rm commands also accept the -W NOE
and -W NOG flags, which have the same effect as the NOE and NOG values for UTILSGE,
respectively:
chgrp -W NOE -W NOG -R / SUPER.SUPER/
The following command performs a recursive search of the / directory without searching the /G
and /E directories:
find / -W NOG -W NOE -name abc*
Other products running in the OSS environment might also have recursive behavior. For example,
the grep, egrep, fgrep, tar, and cpio utilities should not be used on the / directory because
of the scope of the files involved.
See “Environment Variables” (page 45) for information about how to set environment variables.
See the Open System Services Shell and Utilities Reference Manual for more information on the
use of the -W NOG and -W NOE flags with a specific command.
Guardian File Types
From the OSS environment using OSS utilities you can access only a subset of the Guardian files;
these are Guardian EDIT files (file type 101) and odd unstructured files (file type 180). Other
Guardian files are structured files and can contain record separators. Structured files are not
accessible with OSS utilities.
OSS Pathname to Guardian Filename Translation
Because of differences between Guardian filenames and OSS filenames, the following name
changes occur when files are transferred between Guardian and OSS environments. OSS names
that are longer than eight characters are truncated to the first valid eight characters. For example,
an OSS filename like abcde.fghi is converted to the Guardian name ABCDEFGH. This can cause
confusion and make identification of files difficult if you are not expecting it. OSS filenames that
are similar can be converted to the same Guardian filename, which could result in one file
overwriting another file. Files stored in the Guardian environment cannot have pathnames that
contain more than three levels of hierarchy. A pathname can only consist of a volume name,
subvolume name, and file identifier.
From the OSS environment, specify Guardian and Expand filenames as follows:
/G/volumename/subvolumename/fileid
or
/E/nodename/G/volumename/subvolumename/fileid
70 Interoperability Between OSS and Guardian Environments