Open System Services Management and Operations Guide (G06.25+, H06.03+)

Operating the OSS Environment
Open System Services Management and Operations Guide—527191-002
2-39
Using the NetBatch Product
•
The general form of the TACL OSH command for batch execution of a program in
the OSS environment is:
OSH <- >>out_file 2>>err_file -p program_path program_args
<-
indicates that the OSS shell started by the command ignores its standard input
(stdin) file.
>>
indicates that the OSS shell appends normal output to the identified file instead
of the standard output (stdout) file.
out_file
is the OSS pathname of the file to receive normal output.
If the initial working directory is not the current working directory, relative
pathnames are resolved from the initial working directory. When the initial
working directory is a Guardian subvolume and only a relative pathname is
specified, the specified pathname must be a Guardian file identifier and normal
output is saved in a file-code-180 file in that subvolume.
2>>
indicates that the OSS shell appends exception output to the identified file
instead of the standard error (stderr) file.
err_file
is the OSS pathname of the file to receive exception output.
If the initial working directory is not the current working directory, relative
pathnames are resolved from the initial working directory. When the initial
working directory is a Guardian subvolume and only a relative pathname is
specified, the specified pathname must be a Guardian file identifier and
exception output is saved in a file-code-180 file in that subvolume.
-p
explicitly runs a program file in the OSS environment. Note that -P (uppercase
P) is not a valid command option.
program_path
specifies the OSS pathname for the program to be run.
If the initial working directory is not the current working directory, relative
pathnames are resolved from the initial working directory. When the initial
working directory is a Guardian subvolume and only a relative pathname is