Digital PDFs

AA-D643A-TE-V01

August 1978

48 pages

Original

2.2MB

view download

OCR Version

2.1MB

view download

Document:	VAX/VMS UETP User's Guide
Order Number:	AA-D643A-TE
Revision:	V01
Pages:	48
Original Filename:

OCR Text

August 1978
This guide explains the function of the VAX/VMS User Environment
Test Package (UETP) and provides operating instructions for running

the UETP on a VAX/VMS system.

VAX/VMS
UETP User’s Guide
Order No. AA-D643A-TE

SUPERSESSION/UPDATE INFORMATION:

This is a new document for this release.

OPERATING SYSTEM AND VERSION:

VAX/VMS V01

SOFTWARE VERSION:

VAX/VMS V01

To order additional copies of this document, contact the Software Distribution

Center, Digital Equipment Corporation, Maynard, Massachusetts 01754

digital equipment corporation - maynard. massachusetts

First Printing,

August

1978

The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation.
Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.

The software described in this document is furnished under a license
and may only be used or copied in accordance with the terms of such
license.

No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by DIGITAL or its affiliated companies.

The postage-prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing

future documentation.

The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC

DECsystem~10
DECtape

MASSBUS
OMNIBUS

DECUS

EDUSYSTEM

PHA

UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM

FLIP CHIP
FOCAL
INDAC
LAB-8
DECSYSTEM-20

RSTS
RSX
TYPESET~-8
TYPESET-11
TMS-11

VAX

VMS

SBI

DECnet

IAS

PDP

ASSIST-11

DIBOL

RTS~-8

7/79-14

0s/8

ITPS-10

CONTENTS

Page

PREFACE

THE

the

[
!

UETP

Uses

UETP

ROLE

Who

THE

UETP

What

the UETP Tests
UETP's Relationship
and Diagnostics

The

UETP

WORKS

THE

The

|
AT
DA WWN

HOW

to Error Logging

Command Procedure

Master

Initialization Phase
The I/0 Device Test Phase
The Native Mode Test Phase

B o b b

The

System Load Test Phase
Compatibility Mode Test Phase
The Termination Phase

The

SYSTEM

the

System

)

THE

Booting

Setting Up Disk Drives
Setting

Up Magnetic Tape

Setting Up Terminals
Other Devices

The

Load

Single-Run Versus Continuous UETP Execution
FLX and VAX-1l RMS Magnetic Tape Tests

.
.
.

NEFEHFR

ENTIRE

Log

The

and CTRL/C

Files

INDIVIDUAL

Device

UETP

PHASES

The Logical Name

Tests

Test

The

UETPS$SCTRLNAME

Output

The Native Mode

Tests

System Services

Test

The Native Mode Utility
The VAX-11 RMS Test
The VAX-11
The

N -

UETP

THE

Using CTRL/Y
CTRL/Y
CTRL/C
UETP

[]

2
[

Log

Test

The

RUNNING

VARIABLES

Console

RUNNING

UETP

The

|
[
=

[]
*
]

& WN
e

DEFINING

Drives

and Line Printers

FORTRAN

Test

IV-PLUS

The

Load Test
Compatibility Mode

The

FLX

Test

PREPARING

INSTRUCTIONS

OPERATING

OUTPUT

NNOMNMNONNNNNODNONNDONMONDNNNDND NN

UETP

Logging In
Preparing Devices

BB WNNNNN
-

[

R R BB B RARERBRWWWWWNONNDNDN H R

o
&

0
.

UETP

NONMNONDNNNNOMNNODNONDNODMNONNODNODNONONNODNNNNMONODNNNDNDNDNDND

CHAPTER

INTERPRETING

THE

INTRODUCTION

HEHEWOOWO®IIIAAUTO
S D WN N

CHAPTER

System

Test

Output

iii

Test

Compiler

Test

(Cont.)

CONTENTS

Page

.
B W N

B
2

-B B

L]
*
L]
L]
BB B W

L[]
L
*
> W

.
.
L[] [ ]
L
RN NN

SUMMARY OF OPERATING INSTRUCTIONS
LOGGING

PREPARING DEVICES FOR TESTING
Disk Drives
Magnetic Tape Drives
Terminals and Line Printers
Other Devices
RUNNING THE

ENTIRE

UETP

RUNNING INDIVIDUAL UETP PHASES
The

Device

Tests

The Native Mode Tests
The System Load Test
The Compatibility Mode Test

FIGURES

1-1

The UETP Master Command Procedure

TABLES

TABLE

A-1
A-1
A-1
A-2

A-2
A-2

A-3
A-3
A-3
A-4
A-4
A-5

Index-1

INDEX

FIGURE

APPENDIX

)

FORMAT OF SYSTEM MESSAGES
ALPHABETICAL LIST OF MESSAGES

UETP

MESSAGES

CHAPTER

Device Names

Guideline for Selecting Number of Load Test

Users

The Device Tests

PREFACE

MANUAL

The

OBJECTIVES

purpose

the

VAX/VMS

UETP

User's

Guide

function
of the User Environment Test Package
UETP operating instructions.

and

explain

provide

the

complete

INTENDED AUDIENCE

The
major
audiences
for
manufacturing
technicians
support

personnel.

and

how

The

interpret

interpret what
customers

contained

STRUCTURE

THIS

role

them

how

The

guide

the UETP

choose

the

UETP
field

User's
service
run

also

the

test

allows

executes.

run

Guide
are
and software

1In

UETP

package

customers

addition,
by

the

following

guide.

DOCUMENT

contains

Chapter

tells

while

may

VAX/VMS
DIGITAL

results.

happening

themselves

This guide

guide

test

instructions

the
and

three

the

chapters

and

introduction

UETP,

the

way

one

appendix.

the

UETP

works,

that

discusses

and

the

output

the

produces.

Chapter

the

tests
®

UETP

provides detailed operating instructions for running
package automatically and for running individual UETP

separately.

Chapter

explains

all

the

messages

that

the

UETP

tests

can

return.

Appendix

explained

ASSOCIATED

DOCUMENTS

This

refers

guide

System

Messages

summary

in detail

description

Chapter

operating

instructions

several

other

and

Recovery

Procedures

VAX-11l

documents

Manual,

(the

VAX/VMS

particular).

For

information on these and other related documents, refer to the
VAX-1l
Information Directory.
The directory briefly describes all the VAX-11
documents and explains each document's intended audience.

CONVENTIONS USED IN THIS DOCUMENT

In examples of dialogues with the system, user input is printed in red
to distinguish it from text displayed by the system.
Usermame!

SYSTEST

When demonstrating the
optional

input

$ QUETP

Note,

For example:

format

in brackets

([]).

UETP

calls,

For

example:

are

required

the

guide

encloses

syntax

directory

[/OUTPUT=filespec]

however,

specifications,

that

such as

brackets

[SYSTEST].

CHAPTER 1

INTRODUCTION

This

chapter

Package

(UETP).

introduction
The

UETP

1is

TO THE

UETP

the VAX/VMS
a

User

collection

Environment

tests

Test

designed

demonstrate that the hardware and software
components
of
a
VAX/VMS
system are in working order.
DIGITAL software support representatives
run the UETP on a newly installed VAX/VMS system as the formal
sample

procedure.

three

sections,

UETP

the

topics:

The

®@

The

The way

The

UETP

first

role

in which

output

tests

type

the

are

from

the

(Section

simple

prompts.

tests

run.

invoke

discusses

the

following

1.1)

UETP works

the UETP

command

chapter

(Section
(Section

run

all

the UETP

1.3)

and

1.2)

them

then

respond

once,

you

several

Using the information you have provided, the
tests
proceed
automatically.
Alternatively, you can choose to run only one test at
a time;
you can select an individual
test
by
invoking
a
specific

image
or
command
procedure.
Chapter 2 of this gquide gives complete
instructions for running the collection of tests automatically and for

running

1.1

each

test on

its

own.

THE ROLE OF THE UETP

The UETP leads the system through a series of exercises;
at
the
of
the
series,
most
hardware
and
software
components
have
requested to perform one or more tasks.
The tests show not only

individual

components

together

The UETP attempts to
is,
the
tests make
that might originate
test

every

without

feature

encountering

ready

for

1.1.1

Who Uses

work

integrated

normal

that

the various

components work

simulate a normal timesharing environment;
that
demands on the system that are similar to demands
from everyday use.
The UETP does not attempt
to
exhaustively.

When

nonrecoverable

errors,

use.

the

but also

system.

end
been
that

the

UETP

runs

system

under

completion

test

UETP

The primary users of the UETP are
VAX/VMS
manufacturing
technicians
and
DIGITAL
field service and software support representatives.
The
UETP is an important part of the final assembly
and
test
(FA&T)
of
every
VAX/VMS system.
If you are a manufacturing technician, you run
the UETP many times on each system to ensure that it
works
properly.

INTRODUCTION TO THE UETP

The

UETP is the last of a thorough regimen of tests;

can be shipped to

customer,

diagnostic tests as well as the UETP.

must

successfully

before a system

complete

all

If you are a field service or software support representative, you run
By
the UETP after installing a VAX/VMS system at the customer site.
running the UETP, you can ensure that the system was not damaged in
transit and that the hardware and software have been correctly
in its role as the sample
Furthermore,
installed and generated.
the UETP demonstrates to the customer that the newly
procedure,
installed system is capable of doing useful work.

What the UETP Tests

1.1.2

With one exception, the UETP tests exercise devices and functions that
are common to all VAX/VMS systems. The package does not test optional
features such as high-level language compilers (other than the VAX-11
The system components
FORTRAN IV-PLUS compiler) or network devices.
tested

include:

All standard line

printers,

disks connected to the system

Most RSX-11M utilities

that

terminals,

run

magnetic

compatibility

tapes

and

mode

VAX/VMS

record
Various native mode functions such as system services,
management services (VAX-11 RMS), native mode utilities, and,
optionally, the VAX-11 FORTRAN IV-PLUS compiler

The system's multiuser capability

The UETP explicitly tests the features listed above; moreover, in the
process of running its tests, the UETP indirectly tests additional
command
the UETP uses
For example,
functions of the system.
The tests themselves
procedures to execute some of its tests.
therefore show how command procedures can be used for indirect job
various system commands are issued
addition,
In
processing.
the system load test, which
particular,
1In
tests.
the
throughout
demonstrates the system's multiuser capability, issues many commands
within a short time.

The UETP's Relationship to Error Logging and Diagnostics

1.1.3

Wwhen the UETP encounters an error, it reacts either by returning an
error message and proceeding or by reporting a fatal error and
1In either case, the UETP does not attempt to discover
terminating.
in other words, the tests react as normal
the cause of the error;
user

programs

do.

If the UETP encounters an error that you cannot immediately

you

can

diagnose,

turn to the VAX/VMS error logging and diagnostic facilities.

The system continuously maintains data on various kinds of errors.

running

the

SYE

error

report

generator, you can obtain a detailed

report of hardware and system errors that occurred while the UETP was
SYE reports optionally provide detailed information on the
running.
state of the system at the time each error occurred.

INTRODUCTION

THE

UETP

The diagnostic facilities can help in a different
way.
exhaustively
examine a device or medium to isolate the

These
tests
sources of any
errors.
If an error report covering
a
UETP
run
indicates
that
a
particular
device
1is consistently generating errors, you can run the
appropriate diagnostic to investigate the device.

The VAX/VMS Operator's Guide contains operating
SYE

report

1.2

instructions

for

the

generator.

HOW THE

UETP WORKS

You can run the UETP tests
@

Altogether

Individually by

in either one of two ways:

invoking a master command procedure

invoking a specific UETP test

The first method runs all the tests automatically.
A master
command
procedure
contains
commands
that
initiate each test phase in turn.
When you invoke the procedure, it begins by asking several
questions;
your
responses
provide
information
needed
by various test phases.
After you answer the questions, the tests run
to
completion
without
further

input

from you.

At certain times, you may prefer to run
only
one
test
phase.
The
modular
design
of
the
UETP
permits
you
to
run
each test phase
individually.
Furthermore, some phases consist of several tests which
can
also
be
run
independently.
For example, the device test phase

runs a different test for each type of device.
You
can
test
either
all the devices at once or only the devices associated with a specific
controller.

Chapter 2 explains both how to run the whole package of tests at

once

explains the structure of the test package and the

each

and

how to run each test individually.

test

phase.

1.2.1

The remainder of this section
function

The Master Command Procedure

The file UETP.COM is the master command procedure that you
invoke
to
Figure 1-1 below shows the principal
the whole package of tests.
run
commands within UETP.COM;
these are the commands that actually invoke
the
various test phases.
Additional commands within the file perform
1logical
defining
console,
from the
such tasks as asking for input
names,
and manipulating files generated by the tests.
The additional
commands are essential to making
the
UETP
package
as
automated
a
procedure as possible.

As the figure shows,
running an

image or

the procedure invokes each test phase

invoking another command procedure.

either

INTRODUCTION

THE

UETP

UETF.COM

O
$ RUN UETINITOI}

RUN

UETINITO

e
e
-» |nitialization
Phase

RUN

UETFIDEVO1

- |/O Device
Test Phase

RUN

UETNATVO1

PUETNATVOR?

RUETNRMS00

QUETFORTOO

RUN

QUETCOMFOO

» Compatibility Mode Test Phase

RUN

+Termination
Phase

Figure

1.2.2

The

UETLOADO1L

The

Initialization

1initialization
following ways:
Commands

» System Load Test Phase

UETTERMO1

1-1

The

—f———— Native Mode Test Phase

Master

prepares

the

master

the
terminal.
(Section
The input defines certain
of the UETP tests.
e

The

image

Procedure

for

command

the

actual

file

prompt

tests

for

input

the

from

2.2 explains the prompts in detail.)
variables that affect the
execution

gathers
information
on
all
the
in
the
system
and on their associated devices.
writes
the
information
into
a
file
called

UETINIDEV.DAT

and

then

displays

the

file

the

terminal.

Using the information in the file
UETINIDEV.DAT,
the
second
initialization
1image,
UETINITOl.EXE,
verifies
that all the
devices in the system are
operable
by
performing
a
simple
read/write
operation.
If
a
device
fails
this
test, the
device's

entry in UETINIDEV.DAT specifies that the
unavailable.
As
a result, subsequent UETP tests
device.

1.2.3

UETINITO0.EXE

controllers
The
image

Command

Phase

phase

within

UETP

The

device
is
ignore that

I/0 Device Test Phase

The I/0 device test phase includes separate tests
for
each
type
of
device
to
be
tested
(disks,
1line
printers,
magnetic
tapes
and
terminals).
For
each
controller
in
the
system,
the
image

UETPDEVO1.EXE

controller

passed.)
Each
examine all the
system

two

creates

name.

three terminal
controllers, the

processes

separate

2.4.1

detached

explains

test

controllers,

image

terminals,

one

creates
one

test disks.
By

creating

detached

phase
is
able
to
detached processes
deletes

been

each

tested.

process

how

and

passes

the

controller
name
the appropriate device test
devices.
For
example,
1if

detached
process
runs
controller's associated

has

disk

(Section

line

six
test

printer

detached
line

controller

processes:

printers,

and

is
to
a
and

three
two

processes to run the individual tests, this
test
exercise
many
devices
simultaneously;
all the
execute
concurrently.
The
image
UETPDEVO1l.EXE

process when

the

assigned

controller's

devices

have

all

INTRODUCTION

THE

UETP

The terminal tests and line printer tests perform
similar
exercises.
Both
generate
several pages or screens of output, where each page or
screen contains a header line and a test pattern of ASCII
characters.

A
header
the time,
On

each

line
and a

disk

contains the test's
test page number.

the

system,

the

it
randomly
writes blocks of
data for errors and erases the
The

magnetic

The

test

tape

test

creates

test

erases

1.2.4

The

the

Mode

Test

test

large

then

name,

the

date,

file

into

which

checks

tape drives
in
each mounted tape,

of varying
sizes.
tape, validates the

file.

Native

device's

the

writes multiple sequential records
the
records, the test rewinds the
and

The

all

file

the

allocates

data.
file.

exercises
large

name,

the written

the
into

system.
which

After
writing
written records

Phase

The native
mode
test
phase
exercises
software
services
provided
explicitly
for
VAX/VMS (in contrast to RSX-11M utilities that run in
compatibility mode).
This phase includes four separate tests:

The

UETNATVO1l.EXE

UETNATV02.COM

UETNRMS00.COM

UETFORT(00.COM

test

initiated

UETNATVO1l.EXE

issues

all

the

system

services

available to VAX/VMS programmers.
For each service, the test produces
both success and failure return codes.
For
the
success
codes,
the
test
verifies
that
the
service
worked
correctly.
Native
mode
utilities such as the VAX-11 Symbolic
Debugger
and
the
1Image
File

Patch utility,
test initiated
record

are tested by the command procedure UETNATV02.COM.
by the command procedure UETNRMS00.COM handles all

management

services

(VAX-11

RMS),

which

are

used

perform I/0.
The final part of the
if the system being tested includes
The command procedure UETFORT00.COM

native mode test
a VAX-11 FORTRAN
tests
various

VAX-11l

FORTRAN

the

1.2.5

The

(When

load

of
you

in your

system.

logged

same

The

type

load

at
of

creates

the

this way,
normal

real

the
a

The

the

load

detached

system

use.

effect on
creates

image

code

produces.

Each

can

within

processes

system

number

from

the

memory

user

are

succession,

analogous

environment

procedure

command

commands

detached

amount

the

terminal.

quick

their

procedure.

simulates

each
a

creates

command

process

enter

issuing

the

depends

execute

the

UETLOADOl.EXE,

execute

specify

commands

concurrently

test

object

all

number

user

processes

users

the

which
you

the

terminal;

the

Section 2.2.2.)
that

simultaneously.
of

UETP,

created;

See
a

directed

the

and

programs

phase
runs
only
IV-PLUS compiler.
features
of
the

Phase

processes,

commands

test

generally
number

test,

detached
initiate

processes

compiler

System Load Test

system

number

IV-PLUS

The
the

from

that

and

procedures

equal

terminals.

similar

INTRODUCTION TO THE UETP

1.2.6

The Compatibility Mode Test Phase

The compatibility mode test issues commands that 'call most RSX-11M
Compatibility
utilities running in compatibility mode on VAX/VMS.
mode utilities run on VAX/VMS with the aid of the Application
The command procedure UETCOMP00.COM issues
Migration Executive (AME).
several ¢ommands for each utility and then,

most

cases,

compares

the output from the commands with output that is known to be correct.
(Section 2.4.4 lists all the utilities that this phase tests.)

The Termination Phase

1.2.7

The master
The termination phase signals the end of the UETP package.
command procedure deletes temporary files and performs other cleanup
The image UETTERMO1l.EXE then displays the time at which the
activity.
UETP

run ended.

In addition, the master command procedure UETP.COM determines whether
(You can request multiple runs when
the UETP needs to be restarted.
To automatically
see Section 2.2.3.)
you start up the test package;
the procedure passes control directly to the
start up another run,
device

1.3

test phase.

INTERPRETING UETP OUTPUT

from
terminal
the
You can monitor the progress of the UETP tests at
status
displays
always
terminal
The
them.
invoked
you
which
and ending
information, such as messages that announce the beginning
The tests send other
each test and messages that signal an error.
of
issuing
types of output to various log files (which can include the
terminal)

depending on how you invoked the tests.

The log files contain output generated by the actual test

procedures.

For example, one log file contains the command output produced by the
another contains output created by the compatibility mode
load test;
(Section 2.3.2 contains a list of the log
utilities that are tested.
successfully, you need not refer to the
complete
tests
the
If
files.)
the terminal 1log provides sufficient information.
files;
log
the 1log files provide
However, when a test encounters an error,
further

information about the nature of

The error messages that appear at the
files have

two basic

the error.

terminal

and

within

the

1log

sources:

The UETP

tests themselves

The system components that are

tested

that the
Chapter 3 of this guide lists and explains all the messages
tested
the
by
sent
messages
clarify
to
However,
generate.
can
tests
to the VAX/VMS System
either
system components, you need to refer
to the manual that
Messages and Recovery Procedures Manual or
describes the

individual component.

1-6

CHAPTER
UETP

This

2.1

chapter

presents

the

OPERATING

INSTRUCTIONS

UETP operating

How

prepare

the

How

define

UETP

How

run

How to run individual UETP test phases

PREPARING

THE

the

system

for

instructions,

variables

whole

package

running

the

(Section

2.2)

(Section

2.3)

including:

UETP

(Section

2.1)

(Section 2.4)

SYSTEM

The images and command procedures that comprise the UETP are
included
in
the
distributed
VAX/VMS
system.
You can run the UETP any time
after
the
system
has
been
generated
and
booted.
This
section
describes the steps needed to set the system up for running the UETP.

2.1.1
To

Booting

prepare

for

the

System

the

UETP

Bootstrap
instructions
Installation Guide.

2.1.2

Logging

tests,

are

boot

the

system

contained

the

normal

VAX-1l1

manner.

Software

You

can log in from any terminal connected to the system.
If you have
a
choice
between
a
hard-copy terminal and a VDT terminal, consider
whether you want a copy of UETP output to the console.
Section
2.2.1
below
discusses
output
to the terminal in conjunction with the UETP
log files.
All UETP files reside in the [SYSTEST] directory on the
system
disk.
To
access
these
files, you must log in under the user name SYSTEST.
The password to this account in the distributed system is UETP.
Note
that because the SYSTEST account has powerful privileges, its password
should be changed after the VAX/VMS system has been installed
at
the

customer site.
The AUTHORIZE utility,
Manager's Guide, can be used to change

described in the VAX/VMS
account passwords.

System

UETP OPERATING

For

INSTRUCTIONS

example:

>
“RET
Username:

<RET:X

SYSTEST

>
“RET

Fasswords:
where
site.

the password is
(The
system

Password:

Note

UETP or a password determined
never
echoes
a string typed

by
the
customer
in response to the

prompt.)

that

the

SYSTEST

CMKRNL

account must

have

the

following

privileges:

PRMMBX

DETACH

PRMCEB

GRPNAM

GROUP

SYSNAM

LOG_IO

The SYSTEST account also must have

the

following quota allowances:

ASTLM:10

DIOLM:12
BIOLM:12
TQCNT:20

In the system distributed by DIGITAL, the SYSTEST account already
has
these privileges and quotas assigned to it.
To check that they remain
assigned,

issue

the

following

SHOW

FROCESS/FRIVILEGES

SHOW

FROCESS/QUOTAS

two

commands:

<RET:

In response to each command, the terminal displays all the
privileges
or
all
the
quotas
1in
effect
for
the
current
account.
If the
privileges and quotas listed above are not present, run the
AUTHORIZE
utility
to
add
them.
(The VAX/VMS System Manager's Guide describes
the AUTHORIZE

utility.)

The UETP tests can run while the
system
1is
processing
other
work;
however, you obtain better results if the tests run in isolation.
For
example, the UETP cannot test any device that is allocated to
another
process.

2.1.3

Preparing

After

logging

quick

in,

reference,

italics

2.1.3.1
perform

the

Devices

you must

each

set

preparatory

following

the

devices

tested.

below concludes with a

For

summary

steps.

Setting Up Disk Drives the

all

subsection

For

each disk drive

the

system,

steps:

Provide a disk that does not contain any data worth preserving
(that is, a scratch disk) and start up the drive.
If the disk
has not been initialized, use the INITIALIZE command to do so.
For

example:

INITIALIZE/UATA_CHECK

DMAO!?

TESTL

<RET:

This command initializes a disk
on
an
RK0O6
(DMAO:) and assigns the volume label TEST1 to
2-1

lists

the mnemonics

for

or
RKO7
the disk.
the various device types.

2-2

drive
Table

UETP

OPERATING

INSTRUCTIONS

Table 2-1
Device Names

Mnemonic

Note
®

that

Issue

For

Device

Type

RP04,

RP05,

RKO6,

RKO7

RM03

Disk

Line

Printer

TE16

Magnetic

Interactive

all

volumes

must

MOUNT

command

DMAO!

TESTIL

This

command

DMAO:.

the

volume

the

CREATE

when

mounts

The

Disk

Tape

Terminal

have

unique

labels.

connect

the

disk

the

file

example:

MOUNT/ZSYSTEM

RP06
Disk

the

volume

qualifier

available

volume

does

testing

the

all

For

DIIMAO!

TEST1

indicates

users

contain
set

disk.

CREATE/DIRECTORY

labeled

/SYSTEM

not

command

<RET:

the

up.

the

that

the
are

making

system.

directory
The

on
you

UETP

[SYSTEST],

uses

this

DIRECTORY

DRO1:CSYSTESTI
11305

2.
e
i8.

22-MAY~78
22-MAY~-78
22-MAY~78
22-MAY-78

LOADLLOGS

24.

LOAL.I.OG:8

39.

22-MAY~-78

LOAD.LOGS 7
LOAD.LOGS 6
LOAD.LOGHS
LOAD.LOGs 4
LOAL.LOG? 3

2
40,
17.
Se
96

22-MAY~78
22-MAY-78
22-MAY~-78
22-MAY~-78
22-MAY-78

LOAD.LOGS2
L.OAD.LOGS 1

2
D

22-MAY-78
22-MAY-78

TOTAL

Issue

the

21%5./297.

following

DELETE

2.4.4

BLOCKS

command

the

LOAD.LOG

files

<RET:

22-MAY~-78

LOAD.LOGs 12
LOADLLOGs 11
LOAD.LOGS10

shows
above.

12,

to delete

FILES

the

load

test

output

files:

LOAD.LOG#% <RET:

The Compatibility Mode Test

When the compatibility mode phase runs as part of the entire UETP,
it
tests
all
the
utilities
1listed
below.
When
vyou
run this phase
separately, you can choose to test all these
utilities
or
only
one
specific
utility.
The command procedure UETCOMP00.COM issues several
commands to each utility and
then,
in
most
cases,
uses
the
File
Compare (DIF) utility to compare the results of the test commands with
results

that

are

known

correct.

start up this phase, issue the following call to
command file, optionally specifying ALL or the name
e

where

MAGTAF!==device~rame

RUETCOMFOO

utility
ALL

(the

“RET>]

L/0UTFUT=filesrec]

one

the

default)

SLP

S0S

LBR

SRT

PAT

VFY

the

test

applies

you must
the test.

<RET>

values:

PIP

FLX

default,

Lutilitwl

following

DMP

however,
that
include FLX in

the
UETCOMP00.COM
of a utility:

all

explicitly

the

utilities

define

the

listed

global

here.

symbol

Note,

MAGTAP

UETP

OPERATING

INSTRUCTIONS

2.4.4.1

The FLX Test - The FLX test uses the global symbol MAGTAP
to
determine
which
tape
drive to use for testing.
When you start up a
complete run of the UETP, it asks you to specify the name
of
a
tape
drive
if
you want to test FLX (see Section 2.2.4).
If you specify a
drive, the UETP assigns the device name to the global
symbol
MAGTAP.
You
must
define
the
global
symbol
MAGTAP yourself if you run the
compatibility mode phase separately.
For example:
$

MAGTAF $==MTO:!
<RETX
<RET:

$ CUETCOMFOO

This

command

symbol

sequence

MAGTAP

and

assigns

then

the

invokes

device
the

invoke the tests without defining
the FLX test.

the

The

the

following

specifically

commands

invoke

the

define

FLX

MAGTAF ¢==MT1?

<RET>

QUETCOMFOO

<RET:>

FILLX

CUETCOMFOO

When

the
written

test

UETPLOG.LOG.

runs

symbol

MAGTAP,

global

the
the

/0UTFUT=UTILITY.LOG

This example directs
the file UTILITY.LOG

MTO:

to
the

symbol

the

tests.

phase

global
If

you

skips

MAGTAP

and

test:

2.4.4.2
Test Output - When you run
own,
it
sends
all
its output to
output file.
For example:
$

name

compatibility mode

compatibility mode test on its
terminal unless you specify an

«<RET:

the command procedure
on the system disk.

as part of the UETP
file called UCOMP.LOG,

to write

package,
which is

all

its

output

the utility output
is
duplicated in the file

CHAPTER
.

This

UETP

chapter

returned
messages

the

lists

the

returned

testing.

MESSAGES

alphabetical

UETP

tests

order

and

describes

themselves.

components

the

VAX/VMS

does

system

For

the

not
as

messages

describe

the

result

explanations of the latter type of message you must
refer to the VAX/VMS System Messages and Recovery Procedures Manual or
to
the manual that describes the part of the system that returned the

message.

For

example,

detect
an error,
clarify this message,

the

compatibility

the

utility

you

must

utility.
In

Section

3.2,

apostrophes.

READERR,

the
the

3.1
The

variable

For

example,

error

value 'input-file'
error.

FORMAT OF
general

system

parts

message

reading

mode

test

causes

utility

itself returns an error message.
consult the manual that
describes

the

each

message

are

program

that

enclosed

To
the

'input-file'

determined

the

encountered

SYSTEM MESSAGES

format

messages

displayed

the

component

that

VAX/VMS

is:

SFACILITY-L-CODE,

operating

TEXT

[~-FACILITY-L~CODE,

TEXT]

where:
FACILITY

1is

is a severity
values:

the

name

Code
S

the

system

level

has

one

the

message.
following

Meaning
Success

Information

Warning

Error

Fatal

Severity
System

indicator.

issues

severe

error

levels

are

defined

Messages

and

Recovery

in more detail
Procedures

Manual.

the

VAX/VMS

UETP

MESSAGES

CODE

is
an
abbreviation
of
descriptions
in Section
by this code.

TEXT

the explanation

[-FACILITY...]
is a

3.2

the
message
text;
3.2 of this manual are

the
message
alphabetized

the message.

related message.

ALPHABETICAL LIST OF MESSAGES

ABORT,

'testname'

aborted

[at

Explanation:

User

1Investigate

ABORTC,

action:

the

test

['date']

ended

'time']

abnormally.

the

reason

for

the

abnormal

termination

test.

'testname'

Explanation:

to abort this
The

image

test,

type

displaying

°C
this

message

responds

CTRL/C
by
terminating
gracefully
and
passing
control to the
command language interpreter.
You cannot restart the image after
typing CTRL/C.
Use CTRL/Y to temporarily interrupt an image.
User
ATPC,

action:
PC

None.

'location'

Explanation:
This message displays
a
further
information
about
an
error
accompanying messages.
User action:
If the error
1is
Software
Performance
Report

PC
location
to
provide
described
1in one or more

severe
or
reproducible,
wuse
(SPR)
to
describe
the
error

a
to

DIGITAL.

BADFIELD,

'record'

field

invalid at

Explanation:
The VAX-~11 RMS
record,
found
at
the
PC
itself

did

not

test detected a discrepancy
in
location specified, which VAX-11

internal

logic

error

Explanation:

User

Collect

Action:

Software

BADWORD,

as much
Report

'xxxxxxxx'

[at

internal

User

Collect as much

Report

recurs,
send
report it.

'location']

software error
as

occurred.

possible

and

send

DIGITAL.

'location'

unexpected word of

Performance

information

(SPR)

Explanation:

action:

if the
error
to DIGITAL to

detected

unexpected

Performance

invalid data

Software

the
RMS

detect.

User action:
Rerun the test and,
Software Performance Report (SPR)
BADLOGIC,

'location'

data was encountered.

information as possible

(SPR)

3-2

DIGITAL.

and

UETP

BEGIN,

'testname'

beginning

Explanation:

This

MESSAGES

'date'

message

'time'

announces

the

sysgened

into

test.

User
CONF,

action:

the

Explanation:

all

system.

= The

User

action:

DATAER,

data

good

short

DDB,

the

same

data

User

action:

UETINITOO

The

after

DDB

disk
was

the

device

The

cannot

message

generated
a

disk

Section

the

|if

you

file

2.2.1).

the

before

into

Otherwise,

tests.

back

difference

device

name
is

the

caused

the

message

the

and

the

memory.

error.

00000000

devices

name

tested

the

that

00000000

and

'location’

detected-

from

device

The

byte

from memory

'device-type'

device

'number'

'"XXXXXXXX'

displays

controllers

'testname'

(see

(UETDISKO00)

written

system.

None.

action:

this

initiated

unit

data

test

message

the

action:

User

specific

system

devices

appear

log

that

‘'controller'

The

all

therefore

list

that was written
it

describes

Explanation:

bad

Investigate

into

DESTP,

terminal

this

displays

and

'device-type'

data

Explanation:

DENOSU,

the

console

the

generated

User

and

'xxxxxxxxXx'

Explanation:

between

None.

error

data

UETINITO0

controllers

message

are

image

the

appear

devices

The

listing
requested

None.

following

they

beginning

the

not

controller
listing

that

system.

supported

message

UETP

part

(NET,

not

for

known

and

example) .

None.
stopped

testing

'controller'

unit

'number'

'time'

Explanation:

A device that passed the simple read/write test
in
1initial phase of the UETP could not complete its test in the
device test phase.
For example, this problem
can
occur
on
an
RKO6
disk
that is being used as the system disk;
the disk does
not have enough free space to hold the test files.

the

User

the

action:

UETP,

you

investigate

think

and

that

fix

the

device

problen;

should

otherwise,

tested

ignore

the

message.

DEUNUS,

'testname'

device

'device-name'

"XXXXXXXX'

unusable,

error

code

Explanation:
The specified device
failed
to
pass
the
simple
read/write
test
in
the
initial phase of the UETP.
Subsequent
tests in the UETP package will not attempt to
test
the
device.

Another

message

the

test.

not

mounted,

User

action:

message.

usually

Possible
not

follows

causes

are

initialized,

Either

make

that
or

the

not

explain
the

why

device

the
is

device

down,

failed

offline,

write-—-enabled.

device

usable

ignore

the

UETP MESSAGES

'testname' ended at 'date'

ENDED,

Explanation:

'time'

This message announces the completion of a specific

test.

User

action:

None.

ERBOX,

Error count =

'nnn'

Explanation:

This message assigns a sequence number to an

error

described in a subsequent message.

User

action:

None.

NOTRAN, no string translation performed

Explanation: The I/O device tests use the group 1logical name
UETPSCTRLNAME to obtain the name of a controller whose devices
are to be tested. The system load test uses the group logical
name UETPSUSERS to determine the number of detached processes to
be created. This message appears when you run either the 1/0
tests or the system 1load test separately and the
device
appropriate logical name has not been defined.

Define the group logical name UETPSCTRLNAME or
Note that you only need to
rerun the tests.
and
UETPSUSERS
define the logical names explicitly when you run the I/0 device
tests or system load test separately. See Section 2.4.1 for

User action:

further

information.

OPENIN, error opening 'input-file' as input

usually
is
message
This
Self-explanatory.
Explanation:
accompanied by a VAX-1l RMS message indicating the reason for the
failure.

User action:

Take corrective

action

based

the

associated

me ssage.

OPENOUT, error opening ‘output-file' as output

usually
is
message
This
Self-explanatory.
Explanation:
for the
reason
the
ing
indicat
message
RMS
accompanied by a VAX-11l
failure.

User action:

Take corrective

action

based

the

associated

me ssage.

READERR, error reading 'input-file'

usually
is
message
This
Self-explanatory.
Explanation:
for the
reason
the
ng
indicati
message
RMS
VAX-1l
a
by
ied
accompan
failure.

UETP

RMSERROR,

RMS

service

Explanation:

error

The VAX-11

VAX-11
RMS itself
then describes the
User action:
1If
error
described
and

Recovery

MESSAGES

RMS

test

encounters an
actual error.

returns

error.

this

message

subsequent

RMS

when

message

possible, correct the situation that caused
the
in the RMS message.
The VAX/VMS System Messages

Procedures

Manual

describes

all

the

VAX-11

RMS

messages.

SATSMS,

test

module

'testname'

'status'

Explanation:
This
message
announces
that
the
testing
of
a
specific system service has begun, ended successfully, or failed.
The message appears in the file SSLOG.LOG, which
is
<created
by
the native mode system service test (see Section 2.4.2.1).
User

action:

None

'status'

begun

successful.

However,

if
‘'status' is failed, the test supplies a series of messages to
describe
the
reasons
for
failure.
In
this
<case,
see
the
description of the TEXT message for suggested user action.
SYSERROR,

'testname'

system

Explanation:
A test
system service.

service

received

error

{[at

'location’']

unexpected

error

return

from

VMS

User

action:

services
the

error

occurred

suggestion

test

(see

that

caused

Dbecause

Section
this
a

run

the

2.4.2.1);

message
quota

native

the

test

appear.

privilege

mode

might
If

system

reproduce
the

violation,

error

refer

Section 2.1.2, which explains how to modify privilege
and
quota
allocations
for the SYSTEST account.
For other types of errors,
collect as much information
as
possible
and
send
a
Software
Performance Report (SPR) to DIGITAL.
SYSERRORPC,

'testname'

Explanation:
VMS

system

test

service

received

error

unexpected

'location'

error

return

from

service.

User action:
A suggestion is
to
run
the
native
mode
system
service test (see Section 2.4.2.1);
the test might reproduce the
error that caused this message to appear.
1If the error
occurred
because
of
a
quota
or
privilege
violation, refer to Section
2.1.2,
which
explains
how
to
modify
privilege
and
quota
allocations
for the SYSTEST account.
For other types of errors,
collect

Performance

much information
as
possible
Report (SPR)
to DIGITAL.

and

send

Software

UETP MESSAGES

TEXT,

"text'

Explanation:
Various UETP tests
use
this
message
to
provide
information,
usually
self-explanatory,
of one kind or another.
Specifically, the native mode system services test uses this type
of message to explain why a system service failed its test.

User action:
1In most cases, none.
However, note
the
following
suggested user actions if a TEXT message written to the SSLOG.LOG
file describes a system service
test
failure,
(1)
Check
the
quota
and
privilege
allocations for the SYSTEST account if the
message indicates a quota or privilege violation.
(The
message
indicates
such
a
violation by including the appropriate system
service
error
code.)
See
Section
2.1.2
for
information
on
examining
and
modifying
account
allocations
for
quotas
and
privileges.
(2) Forward a listing of
SSLOG.LOG
to
DIGITAL
if
other types of system service test failures are described and are
repeatable.

UETINITOO UCB 1

'unit-number'

'xxXXXXXX'

'"XXXXXXXX'

'Xxxxxxxx'

Explanation:
This
message
describes
a
device
unit
on
a
controller
named
in
a
preceding
DDB
message.
The
three
hexadecimal values are equal to the device characteristics
words
1,
2, and 3.
(The VAX/VMS I/O User's Guide contains information
on device characteristics words.)
User

action:

UNXPCTSTS,

None.

unexpected

status

detected

Explanation:
The VAX-11 RMS test encountered a
condition
other
than
End
of
File (EOF) when it expected to find EOF.
A VAX-1l
RMS message
follows
the
UNXPCTSTS
message
and
explains
the
condition actually encountered.

User action:
message
in

See the description of the accompanying VAX-11
RMS
the
VAX/VMS System Messages and Recovery Procedures

Manual.
USER,

UETLOADOl

'nnn'

user([s]

running

Explanation:
The image UETLOAD(Ql issues this message to announce
the number of users currently active in the system load test (see
Section 2.4.3).
User
WRITEERR,

action:
error

in writing

Explanation:

User action:
report

the

None.
'file-spec'

A test was unable to write to the

Remove the write lock

problem

Software Performance

(if

Report

(if any), retry the test,

reproducible)
(SPR).

specified file.

to DIGITAL by means of a

APPENDIX

SUMMARY OF OPERATING INSTRUCTIONS

This appendix summarizes the UETP operating instructions to provide a
those who are already familiar with
quick reference section for

information about any instructions
For further
running the UETP.
given below, see the appropriate section in Chapter 2, which explains
the

instructions

A.l

Log

LOGGING

in detail.

into the SYSTEST account as
“RET>

Usermname!
Fasswordg?

follows:

SYSTEST <RET>
~RET:>

Note that the system does not echo the password.

A.2

PREPARING DEVICES

FOR TESTING

This section tells you how to prepare different kinds of
testing

A.2.1

devices

the UETP.

Disk Drives

To prepare each disk for testing, perform the following steps:
e

Physically mount a scratch disk

Start up the drive

Issue one or more of the following commands as required:
$

INITIALIZE/DATA.CHECK

MOUNT/SYSTEM

CREATE/DIRECTORY

device-name!

device-mname:

label

device-mame:

[SYSTESTI

for

SUMMARY OF OPERATING

A.2.2
To

Magnetic

prepare

Tape

each

Drives

magnetic

tape

drive

the

device

steps:
®

Turn

Physically

power

feet

Position

Press

tape

ONLINE

the

MOUNT

Turn

Check

the

paper

pages

for

each

Press

the

ONLINE

Check
baud
rates
VAX-11/780 Hardware

Other

UETP

tape

the

tape

entering

the

not

test

Card

Network

the

Null

Mailboxes

The

console

The

terminal

Dialup

Nonstandard

600

command

lasbhel

printers

the

testing

performing

the

device

supply
pass

for

the

device

produces

hard

UETP)

copy

switch

and

terminal

User's

Guide,

characteristics

Order

No.

(see
the
EK-UG780-UG-PRE)

the

following

devices:

(DMClls)

devices

terminal
used

terminal

least

command

reader
devices

following

label

Devices

does

the

Printers

power

A.2.4

scratch

marker

entering

line

perform

BOT

device-name!

Line

and

testing,

switch

steps:

the

device-name!

and

for

write-enabled

initialize

tape

terminals

following

The

the

Terminals

Prepare

mount

INITIALIZE

Mount

A.2.3

necessary,
$

long

INSTRUCTIONS

lines

devices

and

the

initiate

console
the

floppy

UETP

tests

disk

SUMMARY OF OPERATING

A.3

RUNNING THE

initiate

command

ENTIRE UETP

the UETP

procedure

QUETPF

test package,

and

respond

L/0UTFUT=filesrec]

VAX/UMS

INSTRUCTIONS

UETF

STARTED

LOAD

enter

the

call

prompts

the

UETP

shown

below:

master

<RET:

dd-mmm-w3

TEST

three

USERS

hhimm

ENTER

NUMRER

ENTER
ENTER

NUMBER OF COMFLETE UETF RUNS CDJ! n <RET>»
SCRATCH MAGTAFE (E.G. MTO!) OR A «CR>»! device-name!

L[D1¢:

<RET>
<RET:

Sections

2.2.2, 2.2.3, and 2.2.4 explain the three prompts in
detail.
2-2
provides
a guideline for choosing the number of load test
according to the amount of memory in the
VAX/VMS
system
being

Table
users

tested.

Use

CTRL/Y

CTRL/C

interrupt

A.4

RUNNING

INDIVIDUAL UETP

This

section

shows

A.4.1

how

the

tests

initiate

individual UETP

RUN

that

the

file

2.4.1.1.

disks

test

$
$
where

UETINIDEV.DAT

only,

tapes

and

terminals

all

issue

the

must

exist

following

the

system

disk;

see

commands:

DEFINE/GROUF UETF$CTRLNAME M3
RUN UETDISKO0O
x

example).

letter
The

that

group

explicitly when you

test phases.

<RET:

UETFREVO1

Section

2.3.1).

The Device Tests

test disks, line printers, magnetic
once, issue the following command.

Section

PHASES

Note

(see

test

line

UDEFINE/GROUF

RUN

test

run

printers

UETFRINOO

magnetic

UEFINE/GROUF

RUN

name

individual

only,

issue

specific

device
the

controller

UETP$SCTRLNAME

tests.

following

commands:

only,

issue

UETF$CTRLNAME

the

following

commands:

UETTAFEQO

test

terminals

DEFINE/GROUF

RUN

only,

UETTTYS00

must

UETF$CTRLNAME LF3x

tapes

identifies
1logical

issue

the

UETF$CTRLNAME

following

commands:

(DMB,
be

for

defined

SUMMARY OF OPERATING INSTRUCTIONS
The Native Mode Tests

A.4.2

The native mode test phase includes four separate tests:
®

The system services test

The native mode utility tests

The VAX-11l RMS record management services test

The VAX-11 FORTRAN IV-PLUS compiler test

To run the system services test, issue the following command:
$ RUN UETNATVO1

To run the native mode utility test, issue the following command:
$ RUETNATVO2 L/0UTFUT=filesrecllutilitul

where utility is one of the following values:
(the default)

ALL
DEBUG
PATCH

To run the VAX-11 RMS test, issue the following commands:
?l
AF
! ==device-name
e MAGT
%

RUETNRMS00

Note that the RMS test cannot include magnetic tape tests
explicitly define the symbol MAGTAP as shown above.

To run the VAX-11 FORTRAN IV-PLUS compiler test, issue

the

unless

you

following

command:
$

QUETFORTOO

The System Load Test

A.4.3

To run the system load test, issue the following commands:
$ LEFINE/GROUF UETF$USERS n
$

RUN

UETLOADOL

Note that you must define the group logical name UETPSUSERS when you
run the 1load test separately. See Section 2.2.2 and Table 2-2 for
further

information.

SUMMARY OF OPERATING

A.4.4

INSTRUCTIONS

The Compatibility Mode Test

run the compatibility mode

test

issue the

following commands:

Cd MAGTAF==device~-rnamet!]
$ RUETCOMFOO

where

utility
ALL
DMP

(the

CL/0UTFUT=filesrec]

is one of
default)

the

LCutilitwl

following values:
PIP
SLP

FLX

SOS

LBR

SRT

PAT

VFY

Note that you must define the global symbol MAGTAP to include the
test in the compatibility mode test phase;
see Section 2.4.4.

FLX

INDEX

A
Aborting UETP execution, 2-8
AME (Application Migration
Executive), 1-6
Application Migration Executive
(AME), 1-6
AUTHORIZE utility, 2-1

Booting

system,

Image File Patch utility

Interrupting UETP

1-4
execution,

I/0 device tests,

1-4

output, 2-11
running, 2-10,

2-8

A-3

2-1

Line printers,
preparing to test, 2-4, A-2
testing, 1-5, 2-10, A-3

LOAD.LOG,

Compatibility mode utility test,
1-6, 2-16, A-5
log file, 2-~9
Console log, 2-5
Continuous UETP runs, 2-7

CTRL/C,
CTRL/Y,

(PATCH),

testing, 2-12, A-4
Initialization phase,

2-8
2-8

2-9,

console,

2-5

Logging into system, 2-1, 2-2,
Logical names, group,
deassigning, 2-15
UETPSCTRLNAME, 2-10, A-3
UETPSUSERS,
LOGP.LOG,

D
DEBUG (VAX~-1l Symbolic Debugger),
testing, 2-12, A-4
Diagnostics, 1-2
Disk drives,
preparing to test, 2-2, A-1l
testing, 1-5, 2-10, A-3

2-16

deleting versions of, 2-16
Log file(s), 1-6, 2-5, 2-8, 2-9

2-14,

2-9,

2-15,

A-4

2-11

Magnetic

tape drives,
preparing to test, 2-3,

2-4,

A-2
MAGTAP,

global

symbol,

2-13,

2-16,

A-5.

Master

Error logging, 1-2
Error messages, 1-6,

command

Messages,
3-1

procedure

1-6,

3-1

3-6

FORTRAN,
1-5

VAX-11l

testing,

IV-PLUS

compiler,

Native mode tests, 1-5
running, 2-11, A-4
Native mode utility test,
DEBUG,

2-13,

A-4

2-13,

2-9
2-12,

A-4

2-16,

A-5

Group logical names,
deassigning, 2-15
UETP$SCTRLNAME, 2-10, A-3
UETPSUSERS, 2-14, 2-15, A-4

1-5

2-12

running,

G
symbol MAGTAP,

2-12

log file,
PATCH,

Global

A~-l

Output,

compatibility mode test,
device test, 2-11
interpreting UETP, 1-6
Index-1

2=17

INDEX

Output (Cont.),
log files, 2-8,

2-9

native mode utility test, 2-12
system load test, 2=15, 2-16
system services test, 2-12
VAX-11 FORTRAN IV-PLUS compiler
test, 2-14
VAX-11 RMS test,

preparing to test, 2-4, A-2

2-12, A-4

Phases,

compatibility mode test, 1-6,
2-16,

A-5

1-4

I/0 device test, 1-4, 2-10, A-3

native mode test, 1-5, 2-11, A-4

system load test, 1-5, 2-14, A-4

termination,

[SYSTEST] directory, 2-1, 2-5, 2-8

Terminals,

2-2, A-1l

initialization,

quotas, 2-2, 3-6
username, 2-1, A-1l

PATCH (Image File Patch utility),
testing,

SYSTEST account, 2-1, A-1l
privileges, 2-2, 3-6

2-13

Password,

(Cont.)

1-6

running individual, 2-9 to 2-17,

A-3 to A-5
Preparing to test,

testing, 1-5, 2-10, A-3
Termination phase, 1-6
Testing,

compatibility mode utilities, 1-6,
2-16,

A-5

2-12,

A-4

controllers, 1-4, 2-10, A-3
devices, 1-4, 2-10, A-3
native mode utilities, 1-5,

system load, 1-5, 2-6, A-4
system services, 1-5, 2-11, A-4
VAX-11 FORTRAN IV-PLUS compiler,
1-5, 2-13, A-4
VAX~11] RMS services,

1-5,

2-13,

A-4

devices, 2-2, 2-3, 2-4, A-l
disk drives, 2-2, A-1
line printers, 2-4, A-2

magnetic tape drives, 2-3, A-2

UCOMP.LOG, 2-9, 2-17
UETCOMPO00.COM, 1-6, 2-16, A-5

terminals, 2-4, A-2
VAX/VMS system, 2-1, A-l
Privileges, account, 2-2, 3-6

UETDISKO00.EXE,
UETFORT00.COM,
A-4

(VAX-11 RMS),

1-5

1-4 ’
1-4
1-4
1-5 I 4
UETNATVOl.EXE, 1-5 ,

2—10

UETNATV02.COM,
A-4
UETNRMS00.COM,
A-4

Record management services

messages,
role of,

running,

2-6

1-5 ’
1 -5,

2-11,

2-13,

1-6,

1-1

3-1 to 3-6

1-3,

2-7,

1-3,

1-4,

users of, 1-1
variables, 2-5

System services test, 1-5
2-11, A-4

A-4

2=11, A-4
2"11’ 2-12'

output, 1-6, 2-8
password, 2-2

selecting number of users for,
2-12

2-14,

aborting, 2-8
account, 2-1
continuous runs, 2=7
interrupting, 2-8
log files, 2-8

SSLOG.LOG, 2-9, 2-12
System load test, 1-5
running, 2-14, A-4

running,

2-13,

UETP,

2-7

output,

A-3

2-11,

UETINIDEV.DAT,
UETINITOO.EXE,
UETINITOl.EXE,
UETLOADOl.EXE,

Quotas, account, 2-2, 3-6

magnetic tape test,
running, 2-13, A-4

2-10,

1-5,

UETP.COM,

Index~-2

2-9

INDEX

UETPSCTRLNAME,
deassigning,
UETPDEVOl.EXE,
UETPLOG.LOG,

2-10, A-3
2-11
1-4, 2-10,

2-6,

'
A-3

Variables,
defining UETP, 2-5
VAX-11l FORTRAN IV-PLUS

2-9

UETPRINOO.EXE, 2-10, A-3
UETPSUSERS, 2-14, A-4
deassigning, 2-15
UETTAPEOO.EXE, 2-10, A-3
UETTERMOl1.EXE,
UETTTYSO00.EXE,

UNATIVE.LOG,

1-6
2-10,

2-9,

running test of, 2-13, A-4
VAX-11l RMS, 1-5
magnetic tape test, 2-7

running test of, 2-13, A-4
VAX=-11 Symbolic Debugger (DEBUG) ’
testing, 2-12, A-4

A-3

1-6,

2-16,

A-5

native mode,

1-5,

2-12,

compiler,

1-5

2-12

Utilities,
compatibility mode,

(Cont.)

A-4

Index=3

VAX/VMS
UETP User's
AA-D643A-TE

READER'S

NOTE:

This
use

form

comments

Guide

COMMENTS

for document

comments

submitted

this

form

only.

DIGITAL will

company's

the

discretion.
If you require a written reply and are
eligible to receive one under Software Performance
Report (SPR) service, submit your comments on an SPR
form.

Did you find this manual understandable,
suggestions for improvement.

usable,

Did you find errors
page

in this manual?

number.

Please

indicate

Oooood

riease cur aiong this line,

Please make

the

Assembly

type of

language

Higher-level
Occasional

reader

so,

and well-organized?

specify

the error and the

that you most nearly represent.

programmer

language programmer

programmer

(experienced)

fiser with little programming experience
Student programmer

Other

(please

specify)

Name

Date

Organization
Street

City

State

Zip Code
or

Country

—

Do Not Tear- Fold Hereand
Tap¢ —

—

No Postage

dlilgliltiall

Necessary

if Mailed in the

United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

RT/C SOFTWARE PUBLICATIONS

TW/A14

DIGITAL EQUIPMENT CORPORATION
1925 ANDOVER STREET
TEWKSBURY, MASSACHUSETTS

—_—

—

Do Not Tear - Fold Here

01876