UPS Utility Manual

2.3 Use of Files
UPSUTIL uses only two files in its operation.
It reads its commands from the Pascal INPUT file (job/session $STDIN file),
and writes its output (prompts for commands,
progress messages, error messages, and display information resulting from
command execution) to the Pascal OUTPUT file (job/session $STDLIST) file.
Revision of March 2000: Version 8:
UPSUTIL now also uses "UPS Monitor configuration files", as described in the NEWCONFIG command.
(Actually,
UPSUTIL does not, per se, "use" these files -- it never opens a UPS Monitor configuration
file; it simply acquires from the
user the file name of a configuration file,
and passes that file name to the UPS Monitor, which actually opens and uses the
file.)
Revision of December 2001: Version 9:
Introduction of the "user-specified UPS powerfail command file". This is an MPE/iX
CI command file that can be
specified by a configuration command within the UPS Monitor configuration file.
When so specified, this command file
will be executed by the MPE/iX CI at a user-
specified time following the detection by the UPS Monitor of a UPS device's
powerfail signal. UPSUTIL itself does not access
this file; it merely reports the file's specification (or lack thereof) in
UPSUTIL's STATUS display.
2.4 Product Restrictions & Limitations
Because UPSUTIL was conceived to be a simple-to-use service tool, intended primarily for use by HP support
personnel to help them to verify and troubleshoot the operation of the UPS Monitor/iX
subsystem, UPSUTIL is not a
"full-blown" MPE/iX software product implementation.
In its initial implementation, UPSUTIL has the following
restrictions and limitations. These could be alleviated by future enhancements if warranted.
2.4.1 Batch Mode Limitations
UPSUTIL is primarily intended to be operated interactively from an online user's terminal within an MPE/iX
session,
and although it can be operated within a batch job, it does not implement the file I/O functions that batch-
mode
applications usually possess.
In particular, UPSUTIL assumes that its Input and Output files comprise an MPE/iX "duplicative file set" (i.e.
input
records that are read from the Input file are automatically written to and appear on
the Output file), and so it makes no
checks for duplicative input/output files and no provision for echoing the input records to the output file
when the file set is
not duplicative, as is the case in a batch job.
So, while it is permissible to run UPSUTIL from a batch job, taking UPSUTIL's command inputs from $STDIN
(or from
a file-equated INPUT file) and writing UPSUTIL's output to $STDLIST (or to a file-
equated OUTPUT file), when
UPSUTIL is run in this fashion the commands read from INPUT will not be echoed to the OUTPUT file.
Page
8
of
48
UPS Utility
7/18/2008
http://jazz.external.hp.com/papers/upsutil.htm