Document revision date: 19 July 1999

Press Ctrl/Y to abort a UETP run. Note, however, that cleanup of files and network processes in the [SYSTEST] directory might not be complete.

If you are running an individual test image, pressing Ctrl/Y interrupts the current UETP test and temporarily returns control to the command interpreter. While the test is interrupted, you can enter a subset of DCL commands that are executed within the command interpreter and do not cause the current image to exit.

17.5.2 Using DCL Commands

The OpenVMS User's Manual contains a table of commands that you can use within the command interpreter. In addition, you can enter any of the following commands:

• The CONTINUE command continues the test from the point of interruption (except during execution of the cluster test).
• The STOP command terminates the test; the test aborts and control returns to the command interpreter.

  Note Using the STOP command can prevent cleanup procedures from executing normally. You should use the EXIT command if you want the image to do cleanup procedures before terminating.

• The EXIT command executes cleanup procedures and terminates the test (except during execution of the cluster test); control returns to the command interpreter.

If you enter any DCL command other than those that execute within the command interpreter, the test does cleanup procedures and terminates, and the DCL command executes.

17.5.3 Using Ctrl/C

Press Ctrl/C to interrupt a UETP run. You cannot continue the same test phase after you press Ctrl/C. UETP automatically goes to the next phase in the master command procedure.

Some UETP phases react to Ctrl/C by cleaning up all activity and terminating immediately. These tests display the following message when they are started:

%UETP-I-ABORTC, 'testname' to abort this test, type ^C

The phases that do not display the previous message terminate all processes they have started. These processes might not have a chance to complete normal cleanup procedures.

If you are running an individual test image, however, you can use Ctrl/C to terminate the execution of the image and complete cleanup procedures.

Note that Ctrl/C does not complete cleanup procedures for the cluster test.

17.6 Troubleshooting: An Overview

This section explains the role of UETP in interpreting operational errors in an OpenVMS operating system. See Section 17.7 for a discussion of common errors that can appear in a UETP run and describes how to correct them.

17.6.1 Error Logging and Diagnostics

When UETP encounters an error, it reacts like a user program. It either returns an error message and continues, or it reports a fatal error and terminates the image or phase. In either case, UETP assumes the hardware is operating properly and it does not attempt to diagnose the error.

If the cause of an error is not readily apparent, use the following methods to diagnose the error:

• OpenVMS Error Log utility (ERROR LOG)---Run ERROR LOG to obtain a detailed report of hardware and system errors. ERROR LOG reports provide information about the state of the hardware device and I/O request at the time of each error. For information about running ERROR LOG refer to the OpenVMS System Management Utilities Reference Manual.
• Diagnostic facilities---Use the diagnostic facilities to test exhaustively a device or medium to isolate the source of the error.

You can monitor the progress of UETP tests at the terminal from which they were started. This terminal always displays status information, such as messages that announce the beginning and end of each phase and messages that signal an error.

The tests send other types of output to various log files, depending on how you started the tests. (See Section 17.6.7.) The log files contain output generated by the test procedures. Even if UETP completes successfully, with no errors displayed at the terminal, it is good practice to check these log files for errors. Furthermore, when errors are displayed at the terminal, check the log files for more information about their origin and nature.

Each test returns a final completion status to the test controller image, UETPHAS00, using a termination mailbox. This completion status is an unsigned longword integer denoting a condition value. As a troubleshooting aid, UETPHAS00 displays the test's final completion status using the $FAO and $GETMSG system services.

Sometimes, however, the $FAO service needs additional information that cannot be provided using the termination mailbox. When this happens, UETP displays an error message similar to the following one:

UETP-E-ABORT, !AS aborted at !%D

When UETP displays these types of error messages, check the log files for more information. You can also run the individual test to attempt to diagnose the problem.

The error messages that appear at the terminal and within the log files have two basic sources:

• UETP tests
• System components that are tested

If you need help interpreting the messages, use the OpenVMS Help Message utility (Help Message) or refer either to the OpenVMS System Messages and Recovery Procedures Reference Manual or to the manual that describes the individual system component.

17.6.3 Displaying Information on Your Screen

Several parts of UETP, such as some device tests, UETINIT00.EXE, UETCLIG00.EXE, and UETDNET00.COM, let you obtain additional information concerning the progress of the test run or the problems the test encounters. Because this information is usually insignificant, it is not displayed on the screen.

To view the information, enter the following command to define the logical name MODE and run the program:

$ DEFINE MODE DUMP

17.6.4 Example Screen Display (VAX Only)

The following example shows the output for UETINIT00.EXE on a MicroVAX 3600 system:

$ RUN UETINIT00 Welcome to VAX/VMS UETP Version 7.1 %UETP-I-ABORTC, UETINIT00 to abort this test, type ^C You are running on a MicroVAX 3600 Series CPU with 65536 pages of memory. The system was booted from _DUA0:[SYS0.]. Run "ALL" UETP phases or a "SUBSET" [ALL]? How many passes of UETP do you wish to run [1]? The default number of loads is the minimum result of 1) CPU_SCALE * ((MEM_FREE + MEM_MODIFY) / (WS_SIZE * PER_WS_INUSE)) 2.50 * (( 28126 + 312) / ( 1024 * 0.20)) = 347 2) Free process slots = 197 3) Free page file pages / Typical use of page file pages per process 96920 / 1000 = 96 How many simulated user loads do you want [96]? Do you want Long or Short report format [Long]? UETP starting at 22-JUN-1998 09:08:26.71 with parameters: DEVICE LOAD DECNET CLUSTER phases, 1 pass, 96 loads, long report. $

This program does not initiate any phase; it displays the equation used by UETP to determine user load and the specific factors that are employed in the current run.

Respond to the questions by pressing Return. After you respond to the first prompt, the program displays the expressions that determine the default number of simultaneous processes. The following definitions apply:

• CPU_SCALE refers to the relative processing power of the CPU in relation to a VAX 11/780 computer. For example, a MicroVAX 3600 computer has a CPU_SCALE of 2.5 because it has 2.5 times the processing power of a VAX 11/780 (1.0) computer.
• MEM_FREE represents memory in pages available to users.
• MEM_MODIFY represents memory pages on the modified page list.
• WS_SIZE represents working set size.
• PER_WS_INUSE represents typical percentage of the working set in active use for each process.

UETINIT00 also displays the specific values represented by the expressions. In this example, UETP selects 96 as the default for simulated user loads, because 96 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.

17.6.5 Example Screen Display (Alpha Only)

The following example shows the output for UETINIT00.EXE on an Alpha system:

$ RUN UETINIT00.EXE Welcome to OpenVMS Alpha UETP Version 7.1 %UETP-I-ABORTC, UETINIT00 to abort this test, type ^C You are running on a DEC 4000 Model 610 CPU. The system was booted from _COB3$DKA0:[SYS0.]. Run "ALL" UETP phases or a "SUBSET" [ALL]? How many passes of UETP do you wish to run [1]? The default number of loads is the minimum result of 1) (MEM_FREE + MEM_MODIFY) / ( WS_SIZE ) ( 215696 + 11136) / ( 4000) = 56 2) Free process slots = 281 3) Free page file pages / Typical use of blocks per process 199936 / 1000 = 199 How many simulated user loads do you want [56]? Do you want Long or Short report format [Long]? UETP starting at 22-APR-1998 12:20:01.32 with parameters: DEVICE LOAD DECNET CLUSTER phases, 1 pass, 56 loads, long report. $

This program does not initiate any phase; it displays the equation used by UETP to determine user load and the specific factors that are employed in the current run.

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:

• MEM_FREE represents memory in pagelets available to users.
• MEM_MODIFY represents memory pagelets on the modified page list.
• WS_SIZE represents working set size in pagelets.

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.

17.6.6 Defining a Remote Node for UETP Ethernet Testing

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.

1. Find the address of the good Ethernet node by using the Network Control Program (NCP). To use NCP, the following conditions must apply:
   • DECnet for OpenVMS must be up and running on the system.
   • The account you are using must have TMPMBX and NETMBX privileges.
   
   Enter the following commands and press Return:

   $ RUN SYS$SYSTEM:NCP NCP> TELL BETA SHOW EXECUTOR STATUS

   
   If node BETA has not been defined in your network database, NCP displays an error message. In this event, specify another good node and retry the command. Otherwise, see your system or network manager.
   NCP displays information similar to the following messages:

   Node Volatile Status as of 22-JUN-1998 16:13:02 Executor node = 19.007 (BETA) State = on Physical address = AA-00-03-00-76-D3 Active links = 6 Delay = 1

2. Use the displayed physical address (in this case, AA00030076D3) to define the logical name TESTNIADR to point to the good turnaround. Note that you do not specify the hyphens (-).
   First, log in to the SYSTEST account. Then enter the following command:

   $ DEFINE/SYSTEM TESTNIADR AA00030076D3

3. Run UETP.
4. When UETP has completed, deassign the logical name TESTNIADR by entering the following command:

   $ 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.

17.7 Troubleshooting: Possible UETP Errors

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 a Compaq support representative. Any information you can supply about the measures you have taken to isolate the problem will help your a Compaq support representative diagnose the problem.

17.7.1 Summary of Common Failures

The following problems are the most common failures encountered while running UETP:

• Wrong quotas, privileges, or account
• UETINIT01 failure
• UETVECTOR failure (VAX computers only)
• Ethernet device allocated or in use by another application
• Insufficient disk space
• Incorrect cluster setup
• Problems during the load test
• DECnet for OpenVMS error
• Errors logged but not displayed
• No process control block (PCB) or swap slots
• System hangups
• Lack of default access for the file access listener (FAL) object
• Bugchecks and machine checks

The sections that follow describe these errors and offer the best course of action for dealing with each one.

17.7.2 Wrong Quotas, Privileges, or Account

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.

Solution

To correct the problem, use the following procedure:

1. Display all privileges and quotas in effect for the SYSTEST account using the Authorize utility (AUTHORIZE) as follows:

   $ 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-1998 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

2. Make sure the default privileges and quotas assigned to the account match the following list:
   Privileges

   CMKRNL	CMEXEC	NETMBX	DIAGNOSE
   DETACH	PRMCEB	PRMMBX	PHY_IO
   GRPNAM	TMPMBX	VOLPRO	LOG_IO
   SYSNAM	SYSPRV	SETPRV	GROUP

   
   Quotas

   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

3. If any privileges or quotas are incorrect, run AUTHORIZE to correct them.

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-1998 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.

17.7.3 UETINIT01 Failure

UETINIT01 failures are related to peripheral devices; this type of error message can indicate any of the following problems:

• Device failure
• Device not supported or not mounted
• Device allocated to another user
• Device write locked
• Lost vacuum on a magnetic tape drive
• Drive off line

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-1998 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-1998 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-1998 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:

• Intermodule cable unplugged
• Self-test failure code 0000000

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:

• Run the device test individually. (See Section 17.4.1.) By doing this, you can determine if the failure can be re-created, and you can isolate the cause of the problem by reproducing it using the least amount of software possible.
  For example, if the failure occurs only when you run the entire device phase, and not when you run the affected device test individually, you can conclude the problem is related to device interaction. Conversely, if you can re-create the error by running the single device test, then you have proved that the error is not related to device interaction.
• Run the device test with different media. If your run of the single device test succeeded in reproducing the error, the magnetic tape or disk media could be defective. Running the same test with different media determines whether the original media caused the problem.
• Call a Compaq support representative. If you have tried all the previous steps without solving the problem, you should contact a Compaq support representative.

	privacy and legal statement
6017PRO_077.HTML