HP OpenVMS System Manager's Manual, Volume 2:... |
Testing the System with UETP |
|
|
| |
Setting Up the Devices to Be Tested
Check Your Devices ![]()
Examine all devices that UETP will use to be sure that the
following conditions exist:
Note that some communications devices discussed in this section must be set up by a HP support representative.
System Disk Space Required ![]()
Before running UETP, be sure that the system disk has at least
1200 blocks available. Note
that systems running more than 20 load test processes can require
a minimum of 2000 available blocks. If you run multiple passes of
UETP, log files will accumulate in the default directory and further
reduce the amount of disk space available for subsequent passes.
If disk quotas are enabled on the system disk, disable them before you run UETP.
How UETP Works on
Disks ![]()
The disk test phase of UETP uses most of the available free
space on each testable disk in the following manner:
By creating and extending fragmented files in this way, UETP exercises the disk. This allows the test to check for exceeded quotas or a full disk, and to adjust for the amount of available disk space.
As with other disks, shadow sets and volume sets can be tested with UETP; the expectation is that the individual members will be listed as untestable during UETINIDEV (initialization of UETP). UETINIDEV lists errors when testing using a shadow set during the system disk (UETDISK00) pass, however, the shadow set is listed as testable. When testing using a volume set, errors will be noted against all but relative volume number 1, and all but relative volume 1 will be listed as untestable at the end of UETINIDEV.
Prepare Disk Drives ![]()
To prepare
each disk drive in the system for UETP testing, use the following
procedure:
This command initializes DUA1 and assigns the volume label TEST1 to the disk. All volumes must have unique labels.$INITIALIZE DUA1: TEST1
This command mounts the volume labeled TEST1 on DUA1. The /SYSTEM qualifier indicates that you are making the volume available to all users on the system.$MOUNT/SYSTEM DUA1: TEST1
This command creates a [SYSTEST] directory on DUA1 and assigns a user identification code (UIC) of [1,7]. The directory must have a UIC of [1,7] to run UETP.$CREATE/DIRECTORY/OWNER_UIC=[1,7] DUA1:[SYSTEST]
If the disk you have mounted contains a root directory structure, you can create the [SYSTEST] directory in the [SYS0.] tree.
Magnetic Tape Drives ![]()
Set up magnetic
tape drives that you want to test by performing the following steps:
Magnetic tapes must be labeled UETP to be tested. As a safety feature, UETP does not test tapes that have been mounted with the MOUNT command.$INITIALIZE MUA1: UETP
If you encounter a problem initializing the magnetic tape or if the test has a problem accessing the magnetic tape, refer to the description of the INITIALIZE command in the HP OpenVMS DCL Dictionary.
Tape Cartridge
Drives ![]()
To set up tape
cartridge drives you want to test, perform the following steps:
Tape cartridges must be labeled UETP to be tested. As a safety feature, UETP does not test tape cartridges that have been mounted with the MOUNT command.$INITIALIZE MUA0: UETP
If you encounter a problem initializing the tape cartridge, or if the test has a problem accessing the tape cartridge, refer to the description of the DCL INITIALIZE command in the HP OpenVMS DCL Dictionary.
During the initialization phase, UETP sets a time limit of 6 minutes for a TLZ04 unit to complete the UETTAPE00 test. If the device does not complete the UETTAPE00 test within the allotted time, UETP displays a message similar to the following one:
-UETP-E-TEXT, UETTAPE00.EXE testing controller MKA was stopped ($DELPRC)
at 16:23:23.07 because the time out period (UETP$INIT_TIMEOUT)
expired or because it seemed hung or because UETINIT01 was aborted.To increase the timeout value, enter a command similar to
the following one before running UETP:This example defines the initialization timeout value to 8 minutes.$DEFINE/GROUP UETP$INIT_TIMEOUT "0000 00:08:00.00"
Compact Disc Drives ![]()
To run UETP on a compact disc drive, you must first load the
test disc that you received with your compact disc drive unit.
Optical Disk Drives ![]()
To run UETP on an RV60 drive, set up the RV64 optical disk-storage
system, perform the following steps:
UETP tests all the RV60s present in the RV64 simultaneously. Unlike the tape tests, UETP does not reinitialize the optical disks at the end of the test.
Terminals and Line Printers ![]()
Terminals and line printers must be turned on and on line
to be tested by UETP. Check that
line printers and hardcopy terminals have enough paper. The amount
of paper required depends on the number of UETP passes that you
plan to execute. Each pass requires two pages for each line printer
and hardcopy terminal.
Check that all terminals are set to the correct baud rate and are assigned appropriate characteristics. (Refer to the user's guide for your terminal.)
Spooled devices and devices allocated to queues fail the initialization phase of UETP and are not tested.
DR11-W Data Interface (VAX Only) ![]()
The DR11-W data interface uses an internal logical
loopback mode that tests all features except that of module connectors,
cables, and transceivers.
| Only an HP support representative can set up the DR11-W data interface for UETP testing. |
To test the DR11-W data interface properly, the E105 switchpack must be set as follows:
|
Switch 1
|
Switch 2
|
Switch 3
|
Switch 4
|
Switch 5
|
|
Off
|
On
|
Off
|
Off
|
On
|
When UETP testing is completed, restore the DR11-W data interface to the proper operating configuration.
DRV11-WA Data Interface (VAX Only) ![]()
The DRV11-WA data interface is a general-purpose,
16-bit, parallel, direct memory access (DMA) data interface.
| Only an HP support representative can set up the DRV11-WA data interface for UETP testing. |
When UETP testing is completed, restore the DRV11-WA to the proper operating configuration.
DR750 or DR780 (DR32 Interface) (VAX Only) ![]()
The DR32 (DR750 or DR780) device is an interface adapter that
connects the internal memory bus of a VAX processor to a user-accessible
bus called the DR32 device interconnect (DDI).
| Only an HP support representative can set up the DR750 or DR780 for UETP testing. |
When UETP testing is completed, restore the DR750 or the DR780 to the proper operating configuration.
Second LPA11-K Device ![]()
If you have two LPA11-K devices, be sure that each
is given a systemwide logical name in the SYS$MANAGER:LPA11STRT.COM
file. The logical name for the first LPA11-K device should
be LPA11$0, and the logical name for the second LPA11-K
device should be LPA11$1.
Devices That Are Not Tested ![]()
UETP does not test the following devices; their status has
no effect on UETP execution:
UETP does not have specific tests for UDA, HSC, or CI devices; they are tested implicitly by the disk, magnetic tape, and DECnet for OpenVMS tests.
UETP also does not test the console terminal or console drives. If you boot the system, log in, and start UETP, you have shown that these devices can be used.
OpenVMS Cluster Testing ![]()
Before you run UETP in an OpenVMS Cluster environment, check
the SYSTEST_CLIG account. The SYSTEST_CLIG account parallels SYSTEST
except that it is dedicated to running the cluster-integration test.
The requirements for the SYSTEST_CLIG account are as follows:
| The SYSTEST_CLIG account is disabled when it is created. You must enable the SYSTEST_CLIG account and give it a null password before you run UETP. |
$SET DEFAULT SYS$SYSTEM$RUN AUTHORIZEUAF>MODIFY /FLAGS=NODISUSER /NOPASSWORD SYSTEST_CLIGUAF>EXIT
| HP recommends that you disable the SYSTEST_CLIG account after testing has completed. |
$SET DEFAULT SYS$SYSTEM$RUN AUTHORIZEUAF>MODIFY /FLAGS=DISUSER SYSTEST_CLIGUAF>EXIT
UETP requires little additional preparation for the cluster-integration test phase beyond the requirements for other UETP test phases. The additional requirements for cluster integration testing are as follows:
Nodes on which the operator's terminal (OPA0) is set to the NO BROADCAST terminal characteristic will generate the following error message during the cluster test:$SET TERM/BROADCAST/PERM OPA0:
**********************
* UETCLIG00master *
* Error count = 1 *
**********************
-UETP-E-TEXT, 0 operator consoles timed out on the cluster test warning
and 1 operator console rejected it.
-UETP-E-TEXT, Status returned was,
"%SYSTEM-F-DEVOFFLINE, device is not in configuration or not
available"$DEFINE/GROUP UETP$CTMODE ALL
Testing a Small-Disk
System ![]()
After you install the OpenVMS operating system on a small
system disk (for example, an RZ23L), you might not have the 1200
blocks of free disk space required to run UETP successfully. If
you do not have 1200 free blocks on your system disk, use VMSTAILOR
to remove some files from the system disk before you run UETP. For
instructions on using VMSTAILOR, refer to the OpenVMS upgrade and
installation manual for your system.
DECnet for OpenVMS Phase ![]()
The DECnet for OpenVMS phase of UETP uses more system resources
than other tests. You can, however, minimize disruptions to other
users by running the test on the least busy node.
By default, the file UETDNET00.COM specifies the node from which the DECnet test will be run. To run the DECnet test on a different node, enter the following command before you invoke UETP:
This command equates the group logical name UETP$NODE_ADDRESS to the node address of the node in your area on which you want to run the DECnet phase of UETP.$DEFINE/GROUP UETP$NODE_ADDRESS node_address
For example:
You can also run the DECnet for OpenVMS test on a different node by entering the following command before you invoke UETP:$DEFINE/GROUP UETP$NODE_ADDRESS 9.999
$DEFINE/GROUP UETP$NODE_NAME "node""username password""
| When you use the logical name UETP$NODE_ADDRESS, UETP tests only the first active circuit found by NCP (Network Control Program). Otherwise, UETP tests all active testable circuits. |
%NCP-F-CONNEC, Unable to connect to listener -SYSTEM-F-REMRSRC, resources at the remote node were insufficient %NCP-F-CONNEC, Unable to connect to listener -SYSTEM-F-NOSUCHNODE, remote node is unknown
DECnet
Phase 5 Logical ![]()
For a DECnet Phase 5 system, you must define the UETP$NODE_NAME
logical and include login information. You cannot specify the node
by number (because a period (.) causes confusion).
Use the following commands to define the UETP$NODE_NAME logical:$ DEFINE/SYSTEM UETP$NODE_NAME "gamev5""systest""" <password>$ @UETP
Welcome to OpenVMS UETP Version X9Y4-SSB
%UETP-I-ABORTC, UETINIT00 to abort this test, type ^C
You are running on a AlphaServer 2100 5/250 CPU.
The system was booted from _$21$DKA100:[SYS1.].
Run "ALL" UETP phases or a "SUBSET" [ALL]? S
You can choose one or more of the following phases:
DEVICE, LOAD, DECNET, CLUSTER Phase(s): dec
How many passes of UETP do you wish to run [1]?
Do you want Long or Short report format [Long]?
UETP starting at 5-SEP-2003 14:10:17.71 with parameters:
DECNET phases, 1 pass, 10 loads, long report.
%UETP-I-BEGIN, UETDNET00 beginning at 5-SEP-2003 14:10:17.86
%UETP-I-BEGIN, UETDNET00_00000 beginning at 5-SEP-2003 14:10:17.94
**** UETDNET00 BEGINNING AT 5-SEP-2003 14:10:18.22 ****
%UETP-I-TEXT, Testing remote node gamev5
%UETP-I-BEGIN, Remote circuit testing beginning at 5-SEP-2003 14:10:20.21
%UETP-I-BEGIN, UETDNET01 beginning at 5-SEP-2003 14:10:20.31
%UETP-I-BEGIN, GAMEV5TST_00000 beginning at 5-SEP-2003 14:10:20.51
%UETP-I-BEGIN, GAMEV5TST_00001 beginning at 5-SEP-2003 14:10:20.66
%UETP-W-TEXT, The process -GAMEV5TST_00000- returned a final status of:
%DELETE-W-SEARCHFAIL, error searching for !AS
%UETP-I-ENDED, GAMEV5TST_00000 ended at 5-SEP-2003 14:10:30.06
%UETP-W-TEXT, The process -GAMEV5TST_00001- returned a final status of:
%DELETE-W-SEARCHFAIL, error searching for !AS
%UETP-I-ENDED, GAMEV5TST_00001 ended at 5-SEP-2003 14:10:30.07
%UETP-I-ENDED, UETDNET01 ended at 5-SEP-2003 14:10:30.24
%UETP-I-ENDED, Remote circuit testing ended at 5-SEP-2003 14:10:30.28
%UETP-I-ENDED, UETDNET00_00000 ended at 5-SEP-2003 14:10:31.13
%UETP-I-ENDED, UETDNET00 ended at 5-SEP-2003 14:10:31.19
***************************************************
* *
END OF UETP PASS 1 AT 5-SEP-2003 14:10:31.59
* *
***********************************************************
Vector Processors and the VVIEF (VAX Only) ![]()
UETP automatically
loads all installed and enabled vector processors during the load
phase, and automatically tests all installed and enabled vector
processors during the device test phase.
If vector processors are available on the system, check for the VP number by entering the following commands:
Multiply the value of x by 3. If the result is greater than the account PRCLM value, then you must increase the SYSTEST account PRCLM quota to match the returned result. For more information, see Managing Special Processing Environments$x = F$GETSYI ("VP_NUMBER")$SHOW SYMBOL x
However, UETP cannot load the VAX Vector Instruction Emulation facility (VVIEF) during the load phase, and will not automatically test VVIEF. To test VVIEF, you must perform the following steps before running UETP:
Y Y UETVECTOR.EXE "DEVICE_TEST"
If the system displays a value of 1, VVIEF is loaded; if the system displays a value of 0, VVIEF is not loaded.$X = F$GETSYI("VECTOR_EMULATOR")$SHOW SYMBOL X
You can execute the VVIEF test as an individual test using the RUN command, as described in Device Test Phase.
|
|