Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

script_out_file
is the OSS pathname of the file to receive normal output.
If the initial working directory is not the current working directory, a relative pathname is
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, a relative pathname is
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.
script_path
specifies the OSS pathname for the OSS shell script file to be run.
If the initial working directory is not the current working directory, a relative pathname is
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 the script file must be a file-code-180 or file-code-101 file in that
subvolume.
Site-written shell programs can also be used instead of the default OSS shell. See the osh(1)
reference page either online or in the Open System Services Shell and Utilities Reference Manual
for the syntax to use for nondefault shell programs.
• The general form of the NetBatch command for OSS use is:
BATCHCOM;SUBMIT JOB, IN filename, EVERY period * * * * when
filename
is the Guardian filename of a file containing the job statements.
period
indicates the time period between attempts to execute the OSS program or OSS shell script.
when
indicates the time span over which the schedule applies.
As an example of running an OSS program periodically, suppose:
• You want to run a Perl script every 60 minutes only on weekdays.
• Your site has Perl installed at /bin/usr/perl (Perl is not supplied with the OSS environment).
• You have created the script at /script/hourly.pl.
• You want to record normal output in the OSS file /script/hourly.log and error output
in the OSS file /script/hourly.err.
You would:
1. Create a valid job file for the NetBatch product, named \NODE.$SYSTEM.SYSTEM.HOURLY
and containing the following TACL command statement line:
OSH <- >>/script/hourly.log 2>>/script/hourly.err &
-p /bin/usr/perl /script/hourly.pl
2. Enter the following at a TACL prompt:
BATCHCOM;SUBMIT JOB, IN \NODE.$SYSTEM.SYSTEM.HOURLY, &
EVERY 60 * * * * mon-fri
78 Operating the OSS Environment