Open System Services Shell and Utilities Reference Manual (G06.28+, H06.05+)

User Commands (m - o) osh(1)
terminal device names.
-- Specifies that there are no more options on the osh command line. Any informa-
tion following this option is either processed as redirection specifications or
passed to the child process as operands.
Redirection
The osh command initially routes the input, output, and error file information of the child process
to its own standard input, output, and error files. A change in routing is called redirection.
Files that can be redirected include OSS regular files, odd-unstructured Guardian Enscribe format
1 files (file code 180), and Guardian terminal simulation processes such as OSSTTY or Telserv
windows. Other Guardian processes cannot be specified as the source or destination of child pro-
cess redirection; this restriction applies to such processes as spoolers and home terminal emulators
(for example, $VHS cannot receive standard error output unless OSSTTY is used as an intermedi-
ate process). Guardian EDIT files (file code 101) can be used for redirection only when the type of
redirection allows them to be opened for read-only access.
You can redirect information routed to standard files by embedding either or both of the following
in the osh command line:
• Standard Guardian command RUN options (specifying an IN, OUT, or TERM parameter
with a Guardian file name between slashes in the command line)
• POSIX.2 standard file redirection specifications
When a RUN option is used by itself, the Guardian file-system object it specifies is used for the
corresponding standard file of both the osh process and the OSS application that it launches. The
following values are valid:
IN filename1 specifies where to find standard input file data. You can specify a Guardian termi-
nal simulation process (such as OSSTTY or a Telserv window), an odd-
unstructured Enscribe format 1 (file code 180) file, or an EDIT file (file code 101)
using a Guardian filename.
OUT filename2
specifies where to write standard output file data. You can specify a Guardian ter-
minal simulation process (such as OSSTTY or a Telserv window) or an odd-
unstructured Enscribe format 1 (file code 180) file using a Guardian filename.
TERM filename3
specifies where to write standard error file data. You can specify a Guardian ter-
minal simulation process (such as OSSTTY or a Telserv window) using a Guar-
dian filename. If you omit this option, the HOMETERM for your terminal session
is used.
When a POSIX.2 redirection specification is used by itself, it applies to the standard file of the
OSS application being launched by the osh command.
When both a RUN option and a POSIX.2 redirection specification for the same standard file are
used, the osh process determines from the file in the POSIX.2 redirection specification whether a
copy of OSSTTY should be started automatically to redirect the standard file data appropriately.
osh POSIX.2 redirection specifications are a subset of those defined for a POSIX-conformant shell.
The following rules apply:
• All pathnames specified must use OSS pathname syntax. Relative pathnames are resolved
(expanded) using the initial working directory specified in the OSS environment variable
PWD passed to the child process.
527188-007 Hewlett-Packard Company 6−99