SAX (System Acceptance Exerciser) Rev. 1.0
SAX [ -VERSION | -HELP | -USAGE | -CIT | -MAT | -SW |
[ [-AUTOCLose [Yes|No]] [-AUTOsizer [Yes|No]]
[-CONT_UPT] [-DELete [Yes|No]] [-DSPST [Yes|No]]
[-ERRor [Abort|Continue|max_err_cnt]
[-LOGfile [Yes|No|dir_pathname]] [-LOGIN [ppo password]] [-NOREFRESH]
[-NOSTOP] [-ON node_id] [-PAGEs num_pages] [-PARTner [node_id]]
[-PASS max_pass_cnt] [-REPARTner [Yes|No]] [-RUNtime hh:mm]
[-SERVER] [-SLAVE [Yes|No|<<cnt> [NODEs|SEConds]>]] [-SLF pathname]
[-WINDows [Yes|No]]
[ {-script_id [Yes|No]}... | -ONLY script_id [script_id...] ]
] ]
1. Abstract
SAX is online program this used to test all the hardware subsystems for interactive and
system loading failures. SAX may also be used to test layered software.
SAX consists of a controlling program and a series of utility programs and test scripts,
all residing in the /systest directory tree.
You may use either a Dialog or Command Line user interface. To invoke the Dialog user
interface, type
$ wd /systest
$ sax
To use the Command Line user interface, append the desired switches.
While SAX is running, it may be aborted by typing CTRL-Q in the Supervisor window.
2. Command Line
2.1 Documentation Conventions
The following symbolic conventions are used in the description of
the command line syntax:
UPPERCASE Uppercase words or characters represent command or keywords
that you must use literally. Where a word starts in uppercase
and ends in lowercase, then the uppercase portion is the minimum
that must be supplied to make a unique abbreviation.
lowercase Lowercase words or characters represent values that you must
supply.
[ ] Square brackets enclose optional items.
{ } Braces enclose a list from which you must choose an item.
| A vertical bar separates items in a list of choices.<HR>
... Horizontal ellipsis points indicate that the preceding item may be
repeated one or more times.
2.2 Command Line Switches
The SAX command line has the following format:
SAX { -MAT [badge_number] | -CIT | {switch_arg ...} }
Note that at least one switch must be specified. Otherwise, the Dialog
interface will be invoked. If neither -MAT (Manufacturing Acceptance
Test mode) or -CIT (Customer Installation Test mode) are supplied,
then Expert mode is assumed.
SAX utilizes "grouping" switches, which provide a shorthand method of specifying
a commonly used group of switches. When using grouping switches, succeeding
switches override preceeding switches.
The following switch_arg's are defined:
-AUTOCLose [Yes | No]
Specify whether or not to automatically close test process windows
when the test process completes the required number of passes.
Switch or argument omitted: Automatically close window
-AUTOsizer [Yes | No]
Specify whether or not to execute the Autosizer. If the Autosizer
is not executed, then the base configuration information will be used
to determine what subsystems exist beyond the memory and display.
Switch or argument omitted: Execute Autosizer
-CIT
Specify the mode to be Customer Installation Test. A syntax error
is generated if any other switches are supplied.
Switch or argument omitted: mode is either Manufacturing Acceptance
Test or Expert
-CONT_UPT
Continue on an unexpected (test) process termination.
Switch omitted: Abort SAX run on an unexpected (test) process termination.
-DELete [ Yes | No ]
Specify whether or not to delete the SAX working directory (where
all the log and temporary files are created). The SAX working directory
is never deleted if there are errors.
Switch or argument omitted: delete the SAX working directory if there
are no errors.
-DSPST [ Yes | No ]
Specify whether or not to invoke the DSPST (Display Process Statistics)
program, which appears in a window overlaying the Supervisor window.
You may not specify the "-DSPST" switch with the "-WINDows" switch.
Switch or argument omitted: invoke the DSPST program
-ERRor [ Abort | Continue | n ]
Specify what action to take when a hard error is encountered.
ABORT will cause SAX to terminate all processes and exit.
CONTINUE will cause SAX to continue the process that reported the error.
"n" is a number that indicates that SAX should abort after receiving the
nth error.
Switch or argument omitted: Abort on error
-HELP
Print the SAX revision level and build date, display this help file, and exit.
-LOGfile [Yes | No | directory_pathname]
Specify whether or not to create log files, or the directory in which
to create them. "-LOG" or "-LOG Yes" says to create log and temporary
files in the default SAX working directory ("/systest/sax_<<node_id>[.<<id>]").
"-LOG No" says not to create log files. Temporary files are placed
in the default SAX working directory. "-LOG directory_pathname" says
to create log and temporary files in the specified directory.
Switch or argument omitted: Create log and temporary files
in the default SAX working directory. If the directory does not exist,
it is created.
-LOGIN [ppo password]
Specify the person-project-organization (PPO, or "username") and password
to use when creating remote processes. This switch is used in conjunction
with the -ON switch.
Switch omitted: use current username (i.e., "CRP -ME")
Argument omitted: use "user.none.none", password "".
-MAT [Mfg_stage_name]
Specify the mode to be Manufacturing Acceptance Test. A syntax error
is generated if any other switches are supplied.
Switch omitted: mode is either Customer Installation Test or Expert
Argument omitted: SAX queries the user for the Manufacturing Stage name
-NOREFRESH
Do not refresh the screen every 30 seconds when running diskless.
Switch omitted: refresh the screen every 30 seconds when running diskless.
-NOSTOP
Grouping switch, equivalent to "-PASS 0 -ERROR CONTINUE -CONT_UPT".
Run infinite passes and continue on an error or unexpected process termination.
SAX will only stop on a fatal error or operator termination (i.e., quit fault).
-ON node_id
Specify a remote node to be tested. 'node_id' is either a
hex node ID or //node_name.
Switch omitted: use local node
-ONLY script_id [script_id...]
Specify exactly which scripts are to be executed. Any scripts not specified will
not be executed. If autosizing, only the devices corresponding to the specified
script ID's are sized.
This switch may not be used in conjunction with the -script_id switch.
Switch omitted: see description of -script_id switch.
-PAGEs num_pages
Specify the number of memory pages to be used by the memory test process.
(A page is 1024 bytes.) Specifying an amount greater than the physical memory
size will cause page swapping to occur.
Switch omitted: physical memory size
-PARTner [node_id]
Specify a target node for network testing (i.e., the "Paging Partner").
To be a Paging Partner, a node must allow network service requests
from remote nodes. (This can be determined by using the NETSVC shell
command.) 'node_id' is either a hex node ID or //node_name.
Switch or argument omitted: use the next available node downstream
-PASS n
Perform 'n' passes of the active Script List File. If 'n' = 0 then perform
an infinite number of passes. In the latter case, SAX must be terminated by
signalling a quit fault to the Supervisor (i.e., typing a CTRL-Q in the
Supervisor window).
Switch omitted: MAT mode: inifinite (run until stopped by operator)
Expert and CIT modes: 1 pass.
-REPARTner [Yes | No]
Allow SAX to select the next available node downstream as the new
Paging Partner when requested to do so by a test process. Typically,
this occurs after a failure in the Ring network test. For this switch
to be effective, you must select an error action other than (the default)
"Abort On Error".
Switch omitted: Repartnering is not allowed.
Argument omitted: Repartnering is allowed.
-RUNtime hh:mm
Perform enough passes of the active Script List File so that the elapsed
run time is at least 'hh' hours and 'mm' minutes.
Switch omitted: run the specified number of passes
-SERVER
Do not run any tests; instead, just handle start requests from slave nodes.
This mode of operation is only valid on disked nodes. This switch is not valid
with any other switches.
Switch or argument omitted: test the node as specified.
-SLAVEs [ Yes | No | <<cnt> [NODEs|SEConds]> ]
Specify whether or not slave nodes may start SAX, or how many slave nodes to wait for
before starting testing on the host. One of four algorithms are followed:
I. NO_SLAVES: No slaves may start SAX. The environment is "disked_only".
Attempting to start a slave will result in the slave receiving a STOP
message from the host.
II. SLAVES_NO_WAIT: Slaves are allowed to start SAX. However, the host
does not wait for any slave start requests. Instead, it immediately
starts testing in the "disked_only" environment. Starting slaves using
this method is very slow. Use this method when you don't expect to have
slave nodes started, but want to leave the option open.
III. SLAVES_WAIT: The host waits the specified number of seconds for slave
node start requests before starting testing. If any slave start requests
are received, the slaves are started and the initial environment is "host";
otherwise, the initial environment is "disked_only". Starting slaves using
this method is fast. Use this method when you are unsure of the number of
slaves to be started.
IV. SLAVES_COUNT: The host waits until the specified number ("<cnt>") of slave
start requests have been received. It then starts testing on the slaves
and host. The initial environment is "host". Starting slaves using this
method is very fast. Use this method when you know the exact number of
slaves to be started.
Switch omitted : MAT mode: SLAVES_WAIT, time = 90 seconds.
CIT or Expert modes: SLAVES_NO_WAIT
"-SLAVEs" or "-SLAVEs Yes" : SLAVES_WAIT, time = 90 seconds.
"-SLAVEs No" : NO_SLAVES
"-SLAVEs <cnt>" or "-SLAVEs <cnt> NODEs" : SLAVES_COUNT
"-SLAVEs <cnt> SEConds" : SLAVES_WAIT, time = <cnt> seconds.
This switch is only valid on disked nodes.
-SLF pathname
Specify the pathname of the active Script List File.
Switch or argument omitted: use the default Script List File
(see -SW switch, below).
-SW
Specify that the default Script List File is '/systest/sw.slf'.
Note: If this switch is supplied, the Dialog user interface
will still be invoked, and no other switches will be interpreted.
Switch or argument omitted: '/systest/sax.slf' is the default
Script List File.
-USAGE
Print the SAX revision level and build date, display this help file, and exit.
-VERSION
Print the SAX revision level and build date, and exit.
-WINDows [Yes | No]
Specify whether or not to create windows for the processes spawned
by the Supervisor. A syntax error will be generated if windows are
requested when running on a dumb terminal or as a remote process (via
CRP).
"-WINDows No" inhibits the DSPST and Tracker windows. You may not specify
the "-DSPST" switch with the "-WINDows" switch.
Switch or argument omitted: If SAX was invoked on a display, then create
windows; else, don't create windows.
{ -script_id [Yes | No] } ...
where "script_id" is any Script ID that appears in the active Script
List File (i.e., the default Script List File, unless otherwise specified
via the -SLF switch). For each script in the Script List File, that script
is executed if 1) the switch is not supplied and the corresponding subsystem
is available for testing, 2) the switch is supplied with no argument, or
3) the switch is supplied with the "Yes" argument. The script is not executed
only if the switch is supplied with the "No" argument. This switch may be
repeated for as many Script ID's as is defined in the active Script List File.
Any one Script ID may not be specified twice.
The "-script_id" switch is the method by which you disable or enable
sizing and testing of hardware subsystems when using the '/systest/sax.slf'
Script List File (e.g., "sax -ctape n" will run SAX for one pass, without
sizing or testing the Cartridge Tape subsystem). The first column in each
Script ID line in /systest/sax.slf is that test's Script ID.
The -script_id switch may not be used in conjunction with the -only switch.
Switch or argument omitted: see above