![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Respond to the questions by pressing the Return key. After you respond to the first prompt, the program displays the expressions that determine the default number of simultaneous processes. The following definitions apply:
UETINIT00 also displays the specific values represented by the expressions. In this example, UETP selects 56 as the default for simulated user loads, because 56 is the minimum result of the three expressions.
You should deassign the logical name MODE before running UETP, unless you prefer to see the previous breakdown every time you run UETP.
Occasionally during the UETUNAS00 test, it is difficult to determine whether the problem reports concern the device under test or the remote device. The easiest way to ensure proper error reporting is to define a good turnaround. A good turnaround is a remote node that you know turns around Ethernet packets correctly and is up and waiting in the ready state.
You can make the UETUNAS00 test use a known good turnaround by performing the following actions. In the commands that follow, assume that the good device is on node BETA and that node BETA is already defined in the network database.
$ RUN SYS$SYSTEM:NCP NCP> TELL BETA SHOW EXECUTOR STATUS
Node Volatile Status as of 22-JUN-1996 16:13:02 Executor node = 19.007 (BETA) State = on Physical address = AA-00-03-00-76-D3 Active links = 6 Delay = 1
$ DEFINE/SYSTEM TESTNIADR AA00030076D3
$ DEASSIGN/SYSTEM TESTNIADR
UETP stores all information generated by all UETP tests and phases from its current run in one or more UETP.LOG files, and it stores the information from the previous run in one or more OLDUETP.LOG files. If a run of UETP involves multiple passes, there will be one UETP.LOG or one OLDUETP.LOG file for each pass.
At the beginning of a run, UETP deletes all OLDUETP.LOG files, and renames any UETP.LOG files to equivalent versions of OLDUETP.LOG. Then UETP creates a new UETP.LOG file and stores the information from the current pass in it. Subsequent passes of UETP create higher versions of UETP.LOG. Therefore, at the end of a run of UETP that involves multiple passes, there is one UETP.LOG file for each pass. In producing the files UETP.LOG and OLDUETP.LOG, UETP provides the output from the two most recent runs.
The cluster test creates a NETSERVER.LOG file in SYS$TEST for each pass on each system included in the run. If the test is unable to report errors (for example, if the connection to another node is lost), the NETSERVER.LOG file on that node contains the result of the test run on that node. UETP does not purge or delete NETSERVER.LOG files; therefore, you must delete them occasionally to recover disk space.
If a UETP run does not complete normally, SYS$TEST can contain other log files. Ordinarily these log files are concatenated and placed within UETP.LOG. You can use any log files that appear on the system disk for error checking, but you must delete these log files before you run any new tests. You can delete these log files yourself or rerun the entire UETP, which checks for old UETP.LOG files and deletes them.
This section is intended to help you identify and solve problems you can encounter running UETP. You should refer to this section if you need help understanding a system failure and isolating its cause. This section is not intended as a repair manual and is not expected to diagnose any flaws in your system. It should, however, help you to interpret and act upon the information in the error messages.
If you are unable to correct an error after following the steps in this section, you should contact your Multivendor Customer Services representative. Any information you can supply about the measures you have taken to isolate the problem will help your Multivendor Customer Services representative diagnose the problem.
The following are the most common failures encountered while running UETP:
The sections that follow describe these errors and offer the best course of action for dealing with each one.
If your assigned quotas or privileges do not match standard quotas and privileges for the SYSTEST account, UETP displays the following error message:
**********************
* UETINIT00 *
* Error count = 1 *
**********************
-UETP-W-TEXT, The following:
OPER privilege,
BIOLM quota,
ENQLM quota,
FILLM quota,
are nonstandard for the SYSTEST account and may result in UETP errors.
This message informs you that the OPER privilege and the BIOLM, ENQLM, and FILLM quotas either are not assigned correctly or are not assigned at all.
Note
UETP displays a similar message if you run the cluster integration test phase and the privileges and quotas for the SYSTEST_CLIG account are incorrect. The SYSTEST and SYSTEST_CLIG accounts require the same privileges and quotas. Take the action described in this section for both accounts.
Solution
To correct the problem, use the following procedure:
$ SET DEFAULT SYS$SYSTEM $ RUN SYS$SYSTEM:AUTHORIZE UAF> SHOW SYSTEST Username: SYSTEST Owner: SYSTEST-UETP Account: SYSTEST UIC: [1,7] ([SYSTEST]) CLI: DCL Tables: DCLTABLES Default: SYS$SYSROOT:[SYSTEST] LGICMD: LOGIN Login Flags: Primary days: Mon Tue Wed Thu Fri Sat Sun Secondary days: No access restrictions Expiration: (none) Pwdminimum: 8 Login Fails: 0 Pwdlifetime: 14 00:00 Pwdchange: 22-JUN-1996 10:12 Last Login: (none) (interactive), (none) (non-interactive) Maxjobs: 0 Fillm: 100 Bytlm: 65536 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 12 JTquota: 1024 Prclm: 12 DIOlm: 55 WSdef: 256 Prio: 4 ASTlm: 100 WSquo: 512 Queprio: 0 TQElm: 20 WSextent: 2048 CPU: (none) Enqlm: 300 Pgflquo: 20480 Authorized Privileges: CMKRNL CMEXEC SYSNAM GRPNAM DETACH DIAGNOSE LOG_IO GROUP PRMCEB PRMMBX SETPRV TMPMBX NETMBX VOLPRO PHY_IO SYSPRV Default Privileges: CMKRNL CMEXEC SYSNAM GRPNAM DETACH DIAGNOSE LOG_IO GROUP PRMCEB PRMMBX SETPRV TMPMBX NETMBX VOLPRO PHY_IO SYSPRV UAF> SHOW SYSTEST_CLIG . . . UAF> EXIT
| CMKRNL | CMEXEC | NETMBX | DIAGNOSE |
| DETACH | PRMCEB | PRMMBX | PHY_IO |
| GRPNAM | TMPMBX | VOLPRO | LOG_IO |
| SYSNAM | SYSPRV | SETPRV | GROUP |
| BIOLM: 18 | PRCLM: 12 |
| DIOLM: 55 | ASTLM: 100 |
| FILLM: 100 | BYTLM: 65536 |
| TQELM: 20 | CPU: no limit |
| ENQLM: 300 | PGFLQUOTA: 20480 |
| WSDEFAULT: 256 | WSQUOTA: 512 |
| WSEXTENT: 2048 |
If you are logged in to the wrong account, the following error message asks you to log in to the SYSTEST account:
$ @UETP
**********************
* UETINIT00 *
* Error count = 1 *
**********************
-UETP-E-ABORT, UETINIT00 aborted at 22-JUN-1996 14:24:10.13
-UETP-E-TEXT, You are logged in to the wrong account.
Please log in to the SYSTEST account.
$
You must run UETP from the SYSTEST account.
UETINIT01 failures are related to peripheral devices; this type of error message can indicate any of the following:
In some cases, the corrective action is specified explicitly in the error message. For example, you can receive a message from the operator communication manager (OPCOM) informing you of a problem and recommending a corrective measure:
%OPCOM, 22-JUN-1996 14:10:52.96, request 1, from user SYSTEST Please mount volume UETP in device _MTA0: %MOUNT-I-OPRQST, Please mount volume UETP in device _MTA0:
Other error messages can relate information in which the solution is specified implicitly:
%UETP-S-BEGIN, UETDISK00 beginning at 22-JUN-1996 13:34:46.03 ********************** * DISK_DRA * * Error count = 1 * ********************** -UETP-E-TEXT, RMS file error in file DRA0:DRA00.TST -RMS-E-DNR, device not ready or not mounted %UETP-S-ENDED, UETDISK00 ended at 22-JUN-1996 13:34:46.80
This message tells you that a disk drive is either not ready or not mounted. From this information, you know where to look for the cause of the failure (at the disk drive). If you cannot see the cause of the problem immediately, check the setup instructions in Section 17.3.
In other cases, the cause of a failure might not be obvious from the information in the message. The problem can be related to hardware rather than software. For example, the Ethernet adapter test may produce one of the following messages if UETP does not have exclusive access to the Ethernet adapter:
To run the self-test diagnostic on the Ethernet adapter successfully, UETP needs exclusive access to the adapter. As explained in Section 17.3.10, you must shut down DECnet and the LAT terminal server before running the UETP device test phase if you want to test the Ethernet adapter.
Solution
To determine where or when the failure occurs in the execution of UETP, use the following procedure:
UETP displays a message similar to the following to signal a vector processor failure:
**********************
* UETVECTOR *
* Error count = 1 *
**********************
%PPL-S-CREATED_SOME, created some of those requested - partial success
-UETP-E-SUBSPNERR, Error spawning subordinate process.
-UETP-E-SCHCTXERR, Error scheduling vector context test subprocess.
-UETP-E-VECCTXERR, Error encountered during vector context testing.
%UETP-I-ENDED, UETVECTOR_0000 ended at 22-JUN-1996 07:37:00.59
Solution
See Section 17.3.19 for the correct setup for vector processor testing.
If DECnet for OpenVMS software or the LAT software is running during the DEVICE phase, the UETUNAS00 test displays the following message:
-UETP-W-TEXT, Device is in use by DECnet or another application
Other UETP communication device tests display the following message:
SYSTEM-W-DEVALLOC, device already allocated to another user
Solution
If you want to run the device test on the Ethernet adapter, shut down DECnet and LAT software before beginning the test.
When you run continuous passes of UETP, log files accumulate on the disk from which UETP was run. These files reduce the amount of free disk space available for each successive pass. If the amount of disk space available becomes too small for the current load, the following error message appears:
%UETP-S-BEGIN, UETDISK00 beginning at 22-JUN-1996 08:12:24.34 %UETP-I-ABORTC, DISK_DJA to abort this test, type ^C ********************** * DISK_DJA * * Error count = 1 * ********************** -UETP-F-TEXT, RMS file error in file DJA0:DJA00.TST -RMS-F-FUL, device full (insufficient space for allocation) ********************** * DISK_DJA * * Error count = 2 * ********************** -UETP-F-TEXT, RMS file error in file DJA0:DJA01.TST -RMS-F-FUL, device full (insufficient space for allocation) %UETP-E-DESTP, DISK_DJA stopped testing DJA unit 0 at 08:12:36.91 %UETP-S-ENDED, UETDISK00 ended at 22-JUN-1996 08:12:37.98
Solution
Make more space available on the disk. You can do this by using one or more of the following techniques:
See Section 17.2.2 and Section 17.3.3 for a further discussion of disk space.
Most problems that can occur during the cluster-integration test are related to improper setup of the OpenVMS Cluster system or of UETP on the cluster. These problems are most likely to occur at the following stages of the cluster test:
The cluster test phase shows that various OpenVMS nodes in your cluster can simultaneously access files on selected nodes in the cluster. First, UETP tries to create a file on a disk drive that is accessible to the other selected nodes in the cluster. The following are the requirements for creating a file in the cluster test phase:
If UETP is unable to find a suitable device on a certain node, the test displays a warning message and proceeds to the next cluster node.
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:
**********************
* 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"
Disregard this message if OPA0 is set to NO BROADCAST.
Solution
Whenever you suspect a problem, examine the SYS$TEST:NETSERVER.LOG file that was created when the SYSTEST_CLIG process was created. This file can contain additional error information that could not be transmitted to the node running the test. If it was not possible to create the SYSTEST_CLIG process on some node, the system accounting file for that node might contain a final process status in a process termination record.
The following problems can occur during a cluster test:
%SYSTEM-F-INVLOGIN, login information invalid at remote node
A variety of errors can occur during the load test because the command procedures that are started during the tests run several utilities and do many functions. Tracking a problem can be difficult because UETP deletes the log files that are generated during the load test. (See Section 17.8.3.)
Solution
If a problem occurs during the load test and the cause is not obvious, you can modify UETP.COM to preserve the log files as follows:
$ TCNTRL UETLOAD00.DAT/PARALLEL_COUNT='LOADS/REPORT_TYPE='REPORT
$ DELETE UETLO*.LOG;*
Rerun the load test with these changes to try to re-create the problem.
If you re-create the problem, look at the contents of the appropriate log file. You can determine which log file to read by understanding the scheme by which the load test names its processes and log files. (The log file names are derived from the process names.)
The load test creates processes that are named in the following format:
UETLOADnn_nnnn
For example:
%UETP-I-BEGIN, UETLOAD00 beginning at 22-JUN-1996 15:45:08.97 %UETP-I-BEGIN, UETLOAD02_0000 beginning at 22-JUN-1996 15:45:09.42 %UETP-I-BEGIN, UETLOAD03_0001 beginning at 22-JUN-1996 15:45:09.63 %UETP-I-BEGIN, UETLOAD04_0002 beginning at 22-JUN-1996 15:45:10.76 %UETP-I-BEGIN, UETLOAD05_0003 beginning at 22-JUN-1996 15:45:11.28 %UETP-I-BEGIN, UETLOAD06_0004 beginning at 22-JUN-1996 15:45:12.56 %UETP-I-BEGIN, UETLOAD07_0005 beginning at 22-JUN-1996 15:45:13.81 %UETP-I-BEGIN, UETLOAD08_0006 beginning at 22-JUN-1996 15:45:14.95 %UETP-I-BEGIN, UETLOAD09_0007 beginning at 22-JUN-1996 15:45:16.99 %UETP-I-BEGIN, UETLOAD10_0008 beginning at 22-JUN-1996 15:45:19.32 %UETP-I-BEGIN, UETLOAD11_0009 beginning at 22-JUN-1996 15:45:19.95 %UETP-I-BEGIN, UETLOAD02_0010 beginning at 22-JUN-1996 15:45:20.20 %UETP-I-BEGIN, UETLOAD03_0011 beginning at 22-JUN-1996 15:45:21.95 %UETP-I-BEGIN, UETLOAD04_0012 beginning at 22-JUN-1996 15:45:22.99
Note that if more than 10 processes are created, the numbering sequence for the UETLOADnn portion of the process name starts over at UETLOAD02; however, the 4 digits of the _nnnn portion continue to increase.
Each load test process creates two log files. The first log file is created by the test controller; the second log file is created by the process itself. The log file to look at for error information on any given load test process is the one that was created by the test controller (the first log file).
The load test log file derives its file name from the process name, appending the last four digits of the process name (from the _nnnn portion) to UETLO. The test-controller log file and the process log file for each process use the same file name; however, the process log file has the higher version number of the two. For example, the log files created by the process UETLOAD05_0003 would be named as follows:
UETLO0003.LOG;1 (test-controller log file)
UETLO0003.LOG;2 (process log file)
Make sure that you look at the log file with the lower version number; that file contains the load test commands and error information.
After you have isolated the problem, restore UETP.COM to its original state and delete the log files from the load test (UETL0*.LOG;*); failure to delete these files can result in disk space problems.
A DECnet error message can indicate that the network is unavailable.
Solution
$ SHOW LICENSE
$ @SYS$UPDATE:VMSLICENSE
If you encounter other DECnet related errors, you should do the following:
If no errors are displayed at the console terminal or reported in the UETP.LOG file, you should run ERROR LOG to see if any errors were logged in the ERRLOG.SYS file. See the OpenVMS System Management Utilities Reference Manual for information about running the ERROR LOG.
The following error message indicates that no PCB or swap slots are available:
%UETP-I-BEGIN, UETLOAD00 beginning at 22-JUN-1996 07:47:16.50
%UETP-I-BEGIN, UETLOAD02_0000 beginning at 22-JUN-1996 07:47:16.76
%UETP-I-BEGIN, UETLOAD03_0001 beginning at 22-JUN-1996 07:47:16.92
%UETP-I-BEGIN, UETLOAD04_0002 beginning at 22-JUN-1996 07:47:17.13
%UETP-I-BEGIN, UETLOAD05_0003 beginning at 22-JUN-1996 07:47:17.35
%UETP-I-BEGIN, UETLOAD06_0004 beginning at 22-JUN-1996 07:47:17.61
%UETP-W-TEXT, The process -UETLOAD07_0005- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-TEXT, The process -UETLOAD08_0006- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-TEXT, The process -UETLOAD09_0007- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-TEXT, The process -UETLOAD10_0008- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-TEXT, The process -UETLOAD11_0009- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-ABORT, UETLOAD00 aborted at 22-JUN-1996 07:47:54.10
-UETP-W-TEXT, Aborted via a user Ctrl/C.
***************************************************
* *
END OF UETP PASS 1 AT 22-JUN-1996 07:48:03.17
* *
***************************************************
Solution
To solve this problem, use the following procedure:
If the keyboard does not responsd or the system disk is inactive, the system might be hung.
Solution
A system hangup can be difficult to trace; you should save the dump file for reference. To learn why the system hung, run the System Dump Analyzer as described in the System Dump Analyzer Utility Manual.
Reasons for a system hangup include the following:
If default FAL access is disabled at the remote node selected by UETP for DECnet testing (the adjacent node on each active circuit, or a node defined by the group logical name UETP$NODE_ADDRESS), messages similar to the following will appear:
%UETP-W-TEXT, The process -SVA019841_0001- returned a final status of: %COPY-E-OPENOUT, error opening !AS as output
6017P055.HTM OSSG Documentation 22-NOV-1996 14:22:37.55
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.