1.13;fascp (final_acceptance_test), revision 1.13, 84/10/02
FASCP (FINAL_ACCEPTANCE_TEST) -- Perform Final Acceptance Test on a Node
usage: FASCP [-ON node_identifier] [-LOGIN name password] [-FLP YES|NO|FMT]
[-SMD YES|NO|FMT] [-MT YES|NO]
[-QV|-QUICKVERIFY] [-NQ|-NOQUERY]
[-NLOG|-NOLOGFILE] [-LOG[FILE] name]
[-RN|-REMOTENODE nodespec] [-LOCAL]
[-UPDATE]
FORMAT
FASCP [options]
FASCP runs the user-level Final Acceptance Test on a specifed node. If errors
occur during test setup, the program reports the error(s) and terminates. If
errors occur during actual testing, the program presents a single-line message
indicating the problem, and terminates. Test details can be observed in the
logfiles `NODE_DATA/TEST_RESULTS_[L|R].LOG, where `NODE_DATA is the NODE_DATA
directory of the node being tested.
The Server Process Manager (SPM) and Mailbox Server (MBX_HELPER) processes
must be running on (both) the node specified for testing, and, if different,
on the node invoking FASCP.
For complete details, see the DOMAIN System Administrator' Guide.
OPTIONS
-ON node_id Specify remote node to be tested. 'node_id' can be either
a hexadecimal node ID (preceded by 0) or a node entry
directory name preceded by two forward slashes. If this
option is not specified, the local node is tested.
-LOGIN name ['password']
Specify an explicit login name and password for the test
programs to log in with. Secure networks may require that
the test programs have sys_admin privileges: this is the
only method for attaining them. If used, the password must
be enclosed in single quotes, for example: -LOGIN FOOBAR
'GUB' If this option is omitted, the test program runs
using the USER.NONE.NONE.% account.
-FLP {YES|NO|FMT}
Specify that the floppy disk drive is present and should be
tested (or not). If this option is omitted, FASCP will
prompt you about floppy disk testing. The FMT modifier
(used in place of YES) tells FASCP to assume the inserted
floppy disk is a scratch volume, and to initialize it
before testing.
-SMD {YES|NO|FMT}
Specify that a storage module disk drive is present and
should be tested (or not). If this option is omitted,
FASCP will prompt you about storage module testing. The
FMT modifier (used in place of YES) tells FASCP to assume
the inserted storage module is a scratch volume, and to
initialize it before testing. This option should not be
used if the storage module drive is also the boot volume.
-MT {YES|NO} Specify that a tape storage drive is present and should be
tested (or not). If this option is omitted, FASCP will
prompt you about tape storage drive testing.
-QV
-QUICKVERIFY Specify that a shorter version of the normal test sequence
should be run. QV tests provide less coverage than normal
test runs, but take significantly less time.
-NQ
-NOQUERY Specify that all command defaults should be taken (i.e. no
optional devices will be tested), and that no device
prompts should appear during program startup. If this
option is omitted, FASCP will query for all unspecified
hardware options.
-NLOG
-NOLOGFILE Override the default log files. No report (log) files will
be created if this option is specified. This option is not
recommended unless the node is critically short of disk
space.
-LOG[FILE] name
Specify the beginning portion of the logfile names.
(Everything from "_L.LOG" and "_R.LOG" onward is
automatically added). Pathnames can be specified using this
option. Specifying /SYSTEST in the pathname for the
logfiles is discouraged, as this will cause several tests
which copy the /SYSTEST tree to fail. If this option is
omitted, FASCP places the logfiles in
`NODE_DATA/TEST_RESULTS_L.LOG and
`NODE_DATA/TEST_RESULTS_R.LOG
-RN node_id
-REMOTENODE Specify the remote node used for network paging tests.
This is the node with which program pages will be exchanged
for test purposes. When running FASCP as an online
acceptance test (e.g. without the -LOCAL option), you MUST
specify a node OTHER THAN the one you are testing, which
will be used for this exchange. If this option is omitted,
FASCP will prompte you for a remote node name.
-LOCAL Specify that only LOCAL testing should be done (i.e. tests
which verify only the node itself). This option is intended
primarily for first-time installation of nodes. If this
option is omitted, FASCP tests network paging using another
node (see -RN).
-UPDATE Cause FASCP to catalog all reachable nodes in the network
root directory before running its test programs. This
option is intended primarily for first-time installation of
nodes.
EXAMPLES
$ FASCP
Starts the Final Acceptance test, to test the local node (the node running
FASCP). You will be prompted for all required parameters.
$ FASCP -ON //SPIDERS -FLP FMT -MT NO -LOGIN PORKEY 'WOMBAT'
Tells FASCP to execute its tests on node SPIDERS. Test programs should log
into user ID PORKEY, with a password of WOMBAT. A floppy disk is present and
should be formatted and tested, but no testing should be attempted on the
magnetic tape drive. Note that while the MT and Floppy prompts will not be
displayed during program startup, missing parameters (SMD status and network
paging node specification) are still required, so you will be prompted for
them.
$ FASCP -UPDATE -LOCAL -NQ
Instructs FASCP to begin testing the local node. All reachable nodes will be
catalogued in the network root directory before testing begins, and only local
Aegis functions will be tested. You will not be prompted for any hardware
options or a network paging node (ala -NQ), and all tests will be run under
user ID USER.NONE.NONE.%. A log of all test transactions can be found in
`NODE_DATA/TEST_RESULTS_L.LOG when the program stops running.
FASCP TEST PROGRESS MESSAGES
During test execution, FASCP will occasionally print test progress messages.
These messages are informational only and are meant to provide you with
information about which test is currently taking place, and also provide an
indication that tests are in fact progressing. Some of these progress messages
are:
Starting Final Acceptance Testing
Record current state of network and disk(s)
Testing compiler and binder
Testing local paging
Testing remote paging +
Testing floppy disk... *
Initializing floppy disk... *
Floppy initialization complete *
Floppy testing complete *
Testing storage module(s)... *
Initializing storage module(s)... *
Storage module initialization complete *
Storage module testing complete *
Testing magnetic tape... *
Magnetic tape testing complete *
(+) "remote" testing is not performed if -LOCAL was specified
(*) displayed only if the indicated device has been selected for testing
FASCP TEST COMPLETION MESSAGES
If FASCP completes all tests without encountering an error it prints the
message:
**** TESTING SUCCESSFULLY COMPLETED ****
**** Testing complete ****
If one or more of the tests failed, however, the message:
**** SYSTEM UNDER TEST HAS FAILED ****
Failure text follows:
(text which caused FASCP to abort will appear here...)
**** TEST SEQUENCE ABORTING -- PLEASE CORRECT ERROR AND RERUN TEST ****
will be printed, which includes the text line that caused the program to
declare an error.