2.7;fascp (final_acceptance_test), revision 2.7, 85/05/30
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]
[-CT YES|NO] [-QV|-QUICKVERIFY]
[-NQ|-NOQUERY] [-NLOG|-NOLOGFILE]
[-LOG[FILE] name]
[-RN|-REMOTENODE nodespec] [-LOCAL]
[-UPDATE] [-NOAUTO] [-NOPARTNER]
[-NOSTDIN] [-ENV]
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
from the test transcript, indicative of 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.
If possible, FASCP will determine the hardware configuration on the node you
wish to test, and will test those hardware options which are available for
testing. If this automatic determination is not possible, you must tell FASCP
which devices to test: otherwise, it will test only the basic system.
If possible, FASCP will locate another node to participate in network testing,
and will engage that node in network traffic tests. To qualify for automatic
recognition in this sense, a potential partner must contain the file
/SYSTEST/PARTNER_FILE, and further must be running the Server_Process_Manager
and MBX_Helper programs.
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 (unless automatic
configuration determination can be performed: see -NOAUTO).
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 or File Server
disk is present and should be tested (or not). If this
option is omitted, FASCP may prompt you about storage
module testing as noted previously. 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, as the storage module
will automatically be tested. Further, DO NOT attempt to
specify that a File Server disk be formatted by FASCP, as
that operation may require a special program.
-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.
-CT {YES|NO} Specify that a cartridge tape storage drive is present and
should be tested (or not). If this option is omitted, FASCP
will prompt you about cartridge 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.
optional devices may not 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 not found during automatic the hardware
configuration check.
-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 node_id
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), FASCP
will search the entire network for a node willing to assist
in these tests (this is known as auto-partner
determination). If FASCP cannot find a willing partner, you
should specify a node OTHER THAN the one you are testing,
which will be used for this exchange. If this option is
omitted, and auto-partnering is disabled (via -NOPARTNER,
see below), FASCP will prompt 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.
-NOAUTO This option prevents FASCP from attempting to determine the
testable hardware configuration of the specified node. If
this option is omitted, FASCP itself attempts to determine
the hardware configuration of the node under test, and
tests what it finds ready and available.
-NOPARTNER This option prevents FASCP from automatically attempting to
locate a partner node for network verification tests. If
used, the operator must specify a partner node explicitly,
or network verification tests will not be performed. If
this option is omitted, FASCP scans the network for a
network verification test partner.
-NOSTDIN Use this option to specify that the program is running
detached, ala "SH FASCP &" . If this option is omitted,
along with the following one, you must run FASCP from a
DM-level transcript pad.
-ENV Use this option to specify that the program is being tested
under the display ENV shell (e.g. NOT an SIO port, nor the
DM). If this option is omitted, along with the previous
one, you must run FASCP from a DM-level transcript pad.
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 -NOAUTO -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. Further, FASCP will not attempt to locate and identify
all remaining hardware on node //SPIDERS. 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 will, however, attempt to automatically find a
partner for network testing and, should none be found, would test only node
//SPIDERS, without performing the explicit network tests.
$ FASCP -UPDATE -LOCAL
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. as FASCP will attempt to determine these
matters automatically. 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 -NOAUTO -NOPARTNER -RN //US_GUBMENT
Instructs FASCP to begin testing the local node (-ON xxx not specified). FASCP
will NOT attempt to determine what hardware on the local node can be tested
(-NOAUTO); the operator will be prompted for all possible hardware options.
FASCP will NOT attempt to automatically find a partner for network testing
(-NOPARTNER). However, the node //US_GUBMENT will be used as a partner for
said network testing (-RN //US_GUBMENT).
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 *
Testing Performance Enhancement Board... *
Performance Enhancement Board testing complete *
Testing cartridge tape... *
Cartridge 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.