Digital PDFs

AA-PEYAA-TE

July 1991

62 pages

Original

3.0MB

Document:	KAV30 Software Installation and System Testing Information
Order Number:	AA-PEYAA-TE
Revision:	0
Pages:	62
Original Filename:	AA-PEYAA-TE_KAV30_Software_Installation_and_System_Testing_Information_Jul91.pdf

OCR Text

KAV30

Software Installation and System Testing
Information

Part Number: AA-PEYAA—-TE

KAV30
software Installation and System
Testing Information
Order Number:

AA—PEYAA—TE

July 1991
This guide describes how to install the KAV30 software.
the KAV30 system exerciser.

It also describes
|

Revision Information:

This is a new guide.

Operating System and Version:

VMS Version 5.0 or higher,
VAXELN Version 4.2 or higher.

Software Version:

VAXELN KAV
Version 1.0

Digital Equipment Corporation
Maynard, Massachusetts

Toolkit Extensions for VM

July 1991
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 be used or copied
only 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 Equipment Corporation or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013.
© Digital Equipment Corporation

1991.

forms at the end of this document

to assist in preparing future

documentation.

request your critical

The following are trademarks of Digital Equipment Corporation: CVAX, DEC, DECnet, Digital,
VAX Ada, VAX C, VAX FORTRAN, VAX-11/780, VAXcluster, VAXELN, VAXELN Pascal, VMS,
and the DIGITAL logo.
68000 is a registered trademarks of Motorola, Inc.

Intel is a trademark of Intel Corporation.

This document was prepared using VAX DOCUMENT,

Version 2.0.

Contents
Preface

eee ence nn ennnas

Checking Installation Requirements ..................20058.
Software Requirements ............
0.0 eee eee eee eee

1-1
1-1

1.1.3
1.1.4

Privilege and Disk Space Requirements.................
System Parameter Requirements................0000008

1-2
1-2

1.1.6
1.2
1.3

VMSINSTAL Requirements ...............
0000 cee eeee
Backing Up The System Disk ..................0.
00000 us
Registering the License ..........
0... 0 cc eee eee eee eee

1-2
1-3
1-3

Hardware Requirements

...........
0.000 e eee eee eee

Process Account Quota Requirements

..................

1-1

1-2

Installing the KAV30 Software
2.1

2.2

Installation Procedure

...........
00. ccc eee ee eee eae

Error Recovery ........

0.0. cee ee

2-1

ee eee eee ee ee ees

2-10

Running the Installation Verification Procedure .............
Reporting Problems ..........
0... 0.0. cece eee eee ee eens

3-1
3-2

After Installing the KAV30 Software
3.1
3.2

cence

1.1
1.1.1

1.1.5

cece

Preparing for a KAV30 Software Installation
1.1.2

..... 0.0... 0...

KAV30 System Exerciser
4.1
4.2

Overview of the System Exerciser ........... 0.0000 cee ueee
Starting the System Exerciser ..........
0.0000 cee eee wees

4.2.3
4.3

Loading and Running the VAXELN System..............
System Exerciser Screen ....... 0.0... 0c ee eee eee eee eee ae

4.2.1
4.2.2

Building the System Exerciser Into a VAXELN System.....
Building a Secondary System Exerciser Into a VAXELN
System...

ee eee eee ee ees

4—1
4-2

4-3

4—4

4-5
4-6

4.4
4.5
4.6

...........
0.000 e ee ueeees

4-7
4-9
4-15

Initial KAV30 System Exerciser Screen ..............0005
Sample KAV30 System Exerciser Screen ...............4.

4-5
4—6

System Exerciser Commands
System Exerciser Tests ....

Creating System Exerciser Tests

Sample Installation

Files Modified and Installed

Glossary
Index

Figures

4—1
4-2
Tables

1-1

Disk Space Requirements

Preface
This guide describes how to install the VAXELN™ KAV Toolkit Extensions for
VMS™ (KAV30 software). It also describes the KAV30 system exerciser.
This guide applies to Version 1.0 of the KAV30 software and all the subsequent
maintenance releases up to the next major product release.

Who Should Read This Guide
This guide is for the following people:
e

System managers who want to install the KAV30 software

KAV30

system exerciser users

To install the KAV30 software, you must be familiar with the VMS operating
system. To use the KAV30 system exerciser, you must be familiar with

VAXELN,

the VMEbus

environment,

and the KAV30 hardware.

Structure of This Guide
This guide is divided into four chapters, two appendixes, a glossary, and an
index:
e

Chapter 1 describes how to prepare to install the KAV30 software.

Chapter 2 describes how to install the KAV30 software.

Chapter 3 describes what you can do after you install the KAV30 software.

Chapter 4 describes the KAV30 system exerciser.

Appendix A contains a sample KAV30 software installation.

Appendix B lists the files that the KAV30 software installation modifies
and installs on the system.

The glossary defines some important terms used in this guide.

Associated Documents
For more information, see the following documents:

KAV30 Software Product Description (AE-PFB5A-TE)

KAV30 System Support Addendum (AE-PFB6A-TE)

KAV30 Software Cover Letter (AV-PEYFA-TE)

KAV30 Programmer’s Reference Information (AA-PEYCA-TE)

KAV30 Hardware Cover Letter (AV-PFSSA-TE)

KAV30 Hardware Installation and User’s Information (AA-PFM6A-TE)

Conventions
The following conventions are used in this guide:
Convention

Description

Note

A note contains information that is of special
importance to the reader.

Ctrl/x

Ctrl/x indicates that you hold down the Ctrl key
while you press another key (indicated here by x).

Brackets enclose optional command arguments in
command descriptions.
Brackets are also used in the syntax of a directory
name in a VMS file specification.

italic type

Italic type emphasizes important information and
complete titles of manuals.

UPPERCASE

Words in uppercase indicate a command, the name
of a file, or an abbreviation for a system privilege.

Monospace type

Monospace type indicates both system displays and

user input.

Preparing for a KAV30 Software

Installation

This chapter describes how to prepare for a KAV30 software installation.
gives information on the following:
e

Checking installation requirements

Backing up the system disk

Registering the license

The bill of materials (BOM) and Indented Bills Report (BIL) specify the
number and contents of the media. Verify the contents of the kit with this

information.

If the kit is damaged,

or if you find that parts of it are missing,

contact your Digital™ Equipment Corporation representative.

1.1

Checking Installation Requirements
This section gives the KAV30 software installation requirements.

1.1.1

Software Requirements
You must have the following software on the system:

1.1.2

VMS Version 5.0 or higher

VAXELN

Version 4.2 or higher

Hardware Requirements
You must have either a hardcopy or a video terminal. Use the terminal
to communicate with the operating system and to respond to installation
prompts.

Preparing for a KAV30 Software Installation

1-1

Preparing for a KAV30 Software Installation

1.1.3

Privilege and Disk Space Requirements
To install the KAV30 software, you must login to an account that has the
SETPRV or SYSPRV privilege. Note that VMSINSTAL turns off the BYPASS
privilege at the start of the installation.
You must have read (R) and write (W) access to the ELN$

directory.

You must have a certain amount of free disk space while installing the KAV30

software. After you install the KAV30 software, you need less space. Table 1—1
summarizes the KAV30 software disk space requirements.

Table 1-1

Disk Space Requirements
Blocks During

Kit
KAV30

software Version 1.0

Blocks After

Installation

2,500

800

To determine the number of free disk blocks on the current disk, enter the
following command at the DCL prompt:
S SHOW DEVICE

1.1.4

SYSSSYSDEVICE

System Parameter Requirements
The installation account does not require nonstandard

system parameter

settings. Standard system parameter settings are those that Digital ships with
the system account.

1.1.5

Process Account Quota Requirements
The installation account does not require nonstandard process account quotas.
Standard process account quotas are those that Digital ships with the system
account.

1.1.6

VMSINSTAL Requirements
When you invoke VMSINSTAL, it checks the following:

1-2

Ifyou have set the default device and directory to SYS$UPDATE

If you are logged in to a privileged account

Ifthe installation account has adequate process account quotas

If DECnet™ is running

If other users are logged into the system

Preparing for a KAV30 Software Installation

VMSINSTAL requires the installation account to have the following minimum
quotas:

ASTLM = 24
BIOLM = 18
BYTLM = 18,000
DIOLM = 18
ENQLM = 30
FILLM = 20

1.2 Backing Up The System Disk
This section gives guidelines on backing up the system disk. Digital
recommends that you back up the system disk before installing software.
Use the backup procedures that are established at your site. For details on
performing a system disk backup, see the Backup Utility manual in the VMS
System Management

Subkit.

1.3 Registering the License
This section gives guidelines on registering the license. Register and load the
KAV30 software license before installing the KAV30 software. Use the VMS
license management facility (LMF) to register and load the license. This kit
includes a product authorization key (PAK). The PAK contains the information
that you must have to register the license.

When you plan to use the KAV30 software from more than one node in a
VAXcluster™, follow these steps:
1.

Before you install the KAV30 software, register the license on the node
from which you are installing

After you install the KAV30 software, register the license on the nodes
from which you plan to use the KAV30 software

See the License Management Utility manual in the VMS documentation set for
complete information on using LMF.

Preparing for a KAV30 Software Installation

1-3

Installing the KAV30 Software
This chapter describes how to install the KAV30 software.
on the following:

Installation procedure

Error recovery

Before you install the KAV30

prepare for the installation.

software, read Chapter

It gives information

1, which describes how to

The installation takes between five and 20 minutes, depending on the type
of media and the system configuration.

Installing the KAV30

software

and running the Installation Verification Procedure (IVP) on a standalone
VAX-—11/780™ system takes seven minutes.

2.1

Installation Procedure
This section describes the KAV30 software installation procedure. The KAV30
software installation consists of a series of questions and informational
messages. See Appendix A for a sample installation.
Note

When you press Ctrl/Y, the installation deletes all the files that it has
created up to that point, and exits.
To install the KAV30 software, follow these steps:
1.

Invoke VMSINSTAL

S @SYSSUPDATE: VMSINSTAL

saveset-name

device-name

options

To start the installation, invoke VMSINSTAL from a
such as the SYSTEM
directory.

account.

VMSINSTAL

privileged account,

is in the SYS$UPDATE

Installing the KAV30 Software

2-1

Installing the KAV30 Software
The following list defines the VMSINSTAL parameters:
saveset-name

The name of the saveset that you want to install.
KAV30 software, use the following saveset name:

For Version

1.0 of the

KAV010

device-name
The name of the device on which you want to mount the media containing
the KAV30 software. For example, MKB500: is the device name for a tape
drive. It is not necessary to use the console drive for this installation.
However, if you do use the console drive, replace removed media after the
installation.

options

An optional parameter specifying the VMSINSTAL

the following VMSINSTAL options:

options.

You can specify

Release_note option (N): Displays the release notes menu.

Auto_answer option (A): Creates an answer file. The answer file
contains your answers to VMSINSTAL questions. You can use this
option (and an answer file) to save time during a reinstallation.

Get saveset option (G): Temporarily stores product savesets on a

magnetic tape or in a disk directory.

File log option (L): Logs installation actions on the screen.

Alternate root option (R): Installs the product to a system root other

than that of the running system.

To specify an option, type OPTIONS and the letter representing the option
you want to specify. For example, to specify the release notes option, type:
OPTIONS

To specify more than one option, type OPTIONS

and the letters

representing options that you want to specify. Separate the options
with commas and enclose the options in parentheses. For example, to
specify the release notes and the log file options, type:

OPTIONS

(N,L)

See the VMS System Management Subkit for more information on the

options parameter.

2-2

Installing the KAV30 Software

Installing the KAV30 Software
The following example invokes VMSINSTAL to install the KAV30 software
from tape drive MKB500: and shows the system response.
uses the OPTIONS N parameter.
S @SYSSUPDATE:VMSINSTAL
VAX/VMS

Software

KAV0O10

Product

6-MAY-1991

10:41.

Enter

a question

mark

(?)

MKB500:

Installation

Procedure

for

any

time

V5.4-2

help.

Confirm DECnet

status

SVMSINSTAL-W-DECNET,

Your

DECnet

network

continue

anyway

[NO]?

* Do

you

want

This example

and

running.

When you install with VMS Version 5.1 or lower, VMSINSTAL notifies you
if DECnet is running and displays a list of the active processes. It then
asks if you want to continue the installation. Digital recommends that
you install the KAV30 software on a standalone system or cluster when
DECnet is shut down. NO is the default response to the question. Press
Return to choose this default response.
When you install with VMS Version 5.2 or higher, VMSINSTAL does
not check the DECnet status. You can install the KAV30 software while
DECnet is up and running.

3.
* Are

you

Confirm system disk backup
satisfied

with

VMSINSTAL

e
e

4.
The

backup

your

system

disk

[YES]?

asks if you are satisfied with the system disk backup:

Press Return when you are satisfied and want to continue the

installation.

Type NO and press Return when you are not satisfied and want to
stop the installation. After you back up the system disk, restart the
installation.

Read informational messages

following

KAV

the

products

will

processed:

V1.0

Beginning

installation

sVMSINSTAL-I-RESTORE,

of KAV V1.0
Restoring

VMSINSTAL

10:41

product

save

set

A...

displays informational messages.
Installing the KAV30 Software

2-3

Installing the KAV30 Software

Choose a release notes option
If you specified OPTIONS N at the start of the installation, VMSINSTAL
now offers you the release notes options.
When you install with VMS Versions 5.0 or 5.1, VMSINSTAL
following options:

Release

Notes

Options:

Display release notes
Print release notes
Both 1 and 2
Copy release notes to
Do not display, print

* Select

displays the

option

SYSSHELP
or copy release

notes

[2]:

When you install with VMS Version 5.2 or higher, VMSINSTAL
the following options:
Release

notes

Additional
1.
2.
3.
4.

included

Release

with

Notes

this

kit

are

always

copied

displays

SYSSHELP.

Options:

Display release notes
Print release notes
Both 1 and 2
None of the above

* Select

option

[2]:

Choose option 1 to display the release notes on the terminal.
to clear release notes from the screen.

Press Ctrl/C

Choose option 2 to print the release notes. VMSINSTAL prompts you for a
print queue name, as follows:
* Queue

name

[SYSSPRINT]:

Take one of the following actions:
e

Enter a print queue name.

Press Return. When you press Return you send the file to the default
output print device

Choose option 3 to both display the release notes on the terminal and print

the release notes.

VMSINSTAL

displays the release notes on the terminal,

and when you finish reading the release notes, VMSINSTAL prompts you
for a print queue name.

2-4

Installing the KAV30 Software

When you install with VMS

Version 5.0 or 5.1, choose option 4 to copy the

release notes to the system help directory. When you install with VMS
Version 5.2 or higher, choose option 4 if you have reviewed the release
notes and are restarting the installation.

When you install with VMS Version 5.0 or 5.1, choose option 5 if you have
reviewed the release notes and are restarting the installation.
* Do

you

want

continue

the

installation

[N]?:

VMSINSTAL then asks you if you want to continue the installation:
¢

Type YES and press Return to continue the installation

Press Return to stop the installation

SVMSINSTAL-I-RELMOVED,

Product’s

release

notes

have

been

moved

SYSSHELP.

In either case, VMSINSTAL copies the release notes to the
SYS$HELP:KAV010.RELEASE_NOTES file.
Note

The name of the release notes file installed by VMSINSTAL is denoted
by the current product name and version number. Do not delete release
notes for previous versions of the KAV30 software.
6.

Read Informational Messages

DEC

VAXELN

KAV

TOOLKIT

EXTENSIONS

oKAV-I-VMS, Checking VMS version
SKAV-I-VERSION, VMS Version 054,

FOR

VMS

RELEASED

VMSINSTAL displays informational messages.
7.

Respond

Product:
Producer:
Version:

Release

* Does

this

Date:

product

to license registration query
KAV-TOOLKIT-V
DEC
1.0

1-NOV-1990

have

authorization

key

registered

and

loaded?

Installing the KAV30 Software

2-5

Installing the KAV30 Software
The installation procedure displays license information about the product

and asks if you have registered and loaded the Product Authorization Key

(PAK):
¢

Type NO and press Return when you have not registered and loaded
the PAK. Register and load the PAK before continuing with the
installation.

Type YES and press Return when you have registered and loaded the
PAK.

Choose the IVP option

This kit contains an Installation Verification Procedure
IVP verifies that the installed software is available on
You can run the IVP to verify the DEC VAXELN KAV Toolkit
for VMS installation.
You can
the IVP
Digital

* Do

you

(IVP).

The

your system.
Extensions

run the IVP either during or after the installation. To run
after the installation, execute the following command at the
Command Language (DCL) prompt:

@SYSSCOMMON:

[SYSTEST.KAV] KAVSIVP .COM

run

during

the

IVP

following

question:

want

run

the

IVP

the

installation

after

the

procedure,

installation

answer

YES

the

[YES]?

The installation procedure now asks if you want to run the IVP. The KAV30
IVP verifies that the KAV30 software and hardware are available on the
system.

Digital recommends that you run the IVP.

Purge files

This

installation

modifies

the

following

files

your

system:

the

following

files

your

system:

ELNS >RTL.OLB
. OLB
ELNS : RTLOBJECT
ELNS :SHARED STATUS TEXT. EXE
This

installation

installs

ELNS : 300KER. EXE
ELNS: 300KER.MAP
ELNS: 300KER.STB

ELNS > EBUILD. EXE
ELNS :EBUILD.HLB
ELNS :KAVSRTL_ OBJLIB.OLB
ELNS :KRDRIVER. EXE

2-6

Installing the KAV30 Software

Installing the KAV30 Software
ELNS: SCST53C700.OBJ

ELNS: SCSI53C700.OPT
ELNS: SCSI53C700 SCRIPT.OBJ
ELNS :KAVDEF.H, .PAS, .FOR, .ADA
DAT
ELNS : KAVSEXERCISER.
ELNS : KAVSEXERCISER.
EXE
ELNS : KAVSEXERCISER.
OPT
ELNS :KAVSEXR ETHERNET SECONDARY » EXE
INTS SECONDARY .EXE
ELNS :KAVSEXR
ELNS :KAVSEXR OBJLIB.OLB
ELNS: KAVSEXR_ SECONDARY . DAT
ELNS : KAVSEXR_UART SECONDARY. EXE
USER 1 PROCESS .PAS
ELNS :KAVSEXR
ELNS :KAVSEXR
USER 2 PROCESS .PAS
USER 3 PROCESS .PAS
ELNS :KAVSEXR
USER 4 PROCESS .PAS
ELNS :KAVSEXR
USER 5 PROCESS .PAS
ELNS :KAVSEXR
ELNS :KAVSEXR
USER 6 PROCESS. PAS
ELNS: KAVSEXR
USER _7 PROCESS .PAS
ELNS: KAVSEXR USER 8 PROCESS .PAS

ELNS$:KAVSEXR
VME DATA SECONDARY .EXE
ELNS : KAVEXRDEF
. PAS
This installation
system:
[SYSHLP
SYSHLP
SYSHLP
SYSHLP

installs

the

following

example

programs

your

. EXAMPLES .KAV]
KAV_ MVME.FOR
. EXAMPLES .KAV]KAV_TIMER.C
. EXAMPLES . KAV] MVMEDEF .H
. EXAMPLES . KAV] MVMEDRIVER.C
» EXAMPLES .KAV]MVMEDRIVER AST.C
EXAMPLES. KAV]MVMEDRIVER ISR.C
. EXAMPLES .KAV]MVMEDRIVER
ISR AST.C

[SYSHLP . EXAMPLES

. KAV] VDADDRIVER.C

[SYSHLP EXAMPLES. KAV]FIFO AST ROUTINES.ADA
. EXAMPLES .KAV]FIFO CONSUMER.ADA
» EXAMPLES .KAV] FIFO CONSUMER.
DAT
. EXAMPLES .KAV]FIFO PRODUCER.ADA
. EXAMPLES .KAV]FIFO PRODUCER.DAT
. EXAMPLES .KAV]FIFO SIGNALLER_ TASK.ADA
* Do

you

want

purge

files

replaced

this

installation

[YES]?

The KAV380 software installation installs and modifies a number of files on
the system. See Appendix B for a description of these files. You have the
option to purge any previous versions of these files that are on the system.
Digital recommends

that you purge these files.

Installing the KAV30 Software

2-7

Installing the KAV30 Software

10. Read informational messages
The installation
remainder of the
depending on the
SVMSINSTAL-I-RESTORE,
The

procedure will not ask any
installation takes between
processor configuration.

Restoring

installation

product

procedure

installation
of

procedure

these

files

...

all

updates

ELNS$:RTL.OLB

files.

If either
aborts.

set B

renames

ELN$S:300KER.OLD
*, and deletes
The

save

more questions. The
5 and 20 minutes,

not

ELNS:300KER.*

versions

present,

the

files

of ELN$:300KER.OLD*

and ELNS:RTLOBJECT.OLB.

installation

procedure

SKAV-I-UPDLIB, updating ELNS$:RTL.OLB...
sKAV-I-UPDOBJ, updating VAXELN Kernel global data...
SKAV-I-UPDOBJ, updating VAXELN global parameter...
sKAV-I-INSOBJ, inserting KAV Kernel global data...
oKAV-I-UPDOBJ, updating VAXELN Kernel vector table...
SKAV-I-UPDOBJ, updating VAXELN Kernel messages/text...
SKAV-I-UPDLIB, updating ELNS:RTLOBJECT.OLB...
sKAV-I-UPDOBJ, updating VAXELN Kernel messages for EPASCAL...
SVMSINSTAL-I-SYSDIR, This product creates system disk directory
SYSSCOMMON:
[SYSHLP .EXAMPLES.KAV] .
SVMSINSTAL-I-SYSDIR, This product creates system disk directory
oVMSINSTAL-I-MOVEFILES,

Files

VMSINSTAL

will

now

SYSSCOMMON: [SYSTEST.KAV] .

moved

their

target

directories...

displays informational messages.

11. Observe the IVP
The

installation

procedure

invokes

the

IVP.

If you chose to run the IVP, VMSINSTAL runs it now.
System

image

size

495

This

IVP provides

pages

(248

Kbytes);

file

loadable

system

a downline

size

496

blocks

KAVSIVP.SYS in SYSSCOMMON: [SYSTEST.KAV] .
This system can be used to verify the correct
installation of the KAV software and the KAV30
hardware, it however requires the KAV30 to be
installed and ready.
Before you downline load the IVP system
use the following commands to setup the
S MC

NCP

Set

Node

S MC

NCP

Set

Node

S MC NCP

2-8

Set Node

Installing the KAV30

<Name>

Address

<Name>

Load

<Name>

Software

Hardware

<Addr>

File

Address

NCP

database:

08-00-2B-nn-nn-nn

SYSSCOMMON:

[SYSTEST.KAV] KAVSIVP .SYS

Installing the KAV30 Software

Upon successful installation and
KAV30 module will start counting
with 00 in the status display.

bootup, the
up starting

The IVP displays informational messages as it runs. When the IVP runs
successfully, it displays the following message:
DEC

VAXELN

KAV

Toolkit

Extensions

for

VMS

IVP

completed

successfully.

When the IVP fails, it displays one or more of the following messages:
300KER.EXE

not

found

- IVP

failed.

300KER.STB
300KER.MAP

not
not

found
found

IVP
IVP

failed.
failed.

KAVDEF.ADA

not

found

IVP

failed.

KAV Object Library not found - IVP
KAVDEF.H not found - IVP failed.
KAVDEF.PAS not found - IVP failed.
KAVDEF.FOR not found - IVP failed.
RTL. OBJ not found - IVP failed.
New module 1 in RTL.OBJ not found
New module 2 in RTL.OBJ not found
New module 3 in RTL.OBJ not found
New module 4 in RTL.OBJ not found
New module 5 in RTL.OBJ not found

failed.

IVP
IVP
IVP
IVP
IVP

failed.
failed.
failed.
failed.
failed.

See Section 3.2 for information on what to do when the IVP fails.

12. End the installation procedure
Installation
VMSINSTAL

KAV

V1.0

completed

procedure

done

10:47

VMSINSTAL indicates that the installation is complete.
out of the privileged account:
S$ LOGOUT
SYSTEM

logged

out

6-MAY-1991

You can now log

10:48:01.39
Note

VMSINSTAL deletes or changes entries in the process symbol tables
during the installation. If you are going to continue using the system
manager’s account and you want to restore these symbols, log out of
the account and log in again.

Installing the KAV30 Software

2-9

Installing the KAV30 Software

2.2

Error Recovery
This section describes how to recover from errors that occur while you install

the KAV30 software.
When

the installation fails, VMSINSTAL

SVMSINSTAL-E-INSFAIL,

The

installation

displays the following message:
of

KAV

V1.0

has

failed.

Errors occur during the installation if any of the following conditions exist:
e

The operating system version is incorrect

Prerequisite software is absent

You did not register and load the product license

For descriptions of the error messages generated by these conditions, see
the VMS documentation on system messages, recovery procedures, and VMS

software installation. When the system indicates that any of these conditions

exist, take the appropriate action, as described in the error message.

2-10

Installing the KAV30 Software

After Installing the KAV30 Software
This chapter describes what you can do after installing the KAV30

gives information on the following:

3.1

Running the IVP

Reporting problems

software.

Running the Installation Verification Procedure
This section describes how to run the KAV30 IVP. The IVP verifies that the
KAV30 software and hardware function correctly. You usually run the IVP

during the installation procedure. However, you might want to run the IVP
after the installation procedure. For example, after a system failure, you must
run the KAV30 IVP to make sure that users can access the KAV30 software
and hardware.
To run the IVP after the installation procedure, follow these steps:

> MC NCP
> MC NCP

$ MC

NCP

Set-up the network control program (NCP) database so that you can
downline load the IVP system to the KAV30. To include details of the
KAV30 in the NCP database, enter the following commands:

SET NODE
SET NODE
SET

NODE

<node-name>

ADDRESS <node address>
HARDWARE ADDRESS <ethernet address>
LOAD

FILE

SYSSCOMMON:

[SYSTEST.KAV]KAVSIVP.SYS

Replace <node name> with the node name. Replace <node address> with
the node address. Replace <ethernet_ address> with the Ethernet address.
2.

Downline load the IVP system to the KAV30.

SYS$COMMON:ISYSTEST.KAVIKAVS$IVE.SYS
system.

The

file contains the IVP

After Installing the KAV30 Software

3-1

After Installing the KAV30 Software
3.

Boot the KAV30. When you boot the KAV30, it runs the IVP. When the IVP
is successful, it displays the following message:
KAV

Installation

verification

procedure

completed

successfully.

When the IVP fails, it displays one or more of the following messages:
300KER.EXE not found - IVP failed.
300KER.STB not found - IVP failed.
300KER.MAP not found - IVP failed.
KAV Object Library not found - IVP
KAVDEF.H not found - IVP failed.
KAVDEF.PAS not found - IVP failed.
KAVDEF.ADA not found - IVP failed.
KAVDEF.FOR

not

found

RTL.OBJ not found - IVP
New module 1 in RTL.OBJ
New module 2 in RTL.OBJ
New module 3 in RTL.OBJ
New module 4 in RTL.OBJ
New module 5 in RTL.OBJ

IVP

failed.

failed.
not found
not found
not found
not found
not found

IVP
IVP
IVP
IVP
IVP

failed.
failed.
failed.
failed.
failed.

See Section 3.2 for information on what to do when the IVP fails.

3.2

Reporting Problems
This section describes how to report problems to Digital. When you encounter
a problem while using the KAV30 software, report it to Digital. Depending on
the nature of the problem and the type of support that is available to you, take
one of the following actions:

Call Digital when the software contract or warranty agreement entitles you
to telephone support.

Submit a Software Performance Report (SPR).

Fill out and submit a Reader’s Comments form when the problem has to
do with this documentation. There are two Reader’s Comments forms at
the back of each KAV30 guide. Use the form from the guide in which you
found the error. Include the section and page number.

Review the Software Product Description (SPD) and Warranty addendum
for an explanation of warranty. When you encounter a problem during the
warranty period, report the problem as indicated above, or follow alternate
instructions provided by Digital for reporting SPD nonconformance problems.

3-2

After Installing the KAV30 Software

4
KAV30 System

Exerciser

The KAV30 system exerciser is a VAXELN application program that allows
you to verify that the KAV30 hardware and software function correctly. This
chapter describes the KAV30 system exerciser. It gives information on the

following:

4.1

Overview of the system exerciser

Starting the system exerciser

System exerciser screen

System exerciser commands

System exerciser tests

Creating system exerciser tests

Overview of the System Exerciser
This section gives an overview of the KAV30 system exerciser.
system exerciser is a VAXELN

The KAV30

application program that allows you to

verify that the KAV30 hardware and software function correctly. It does
this by allowing you to test elements of the KAV30 hardware and software
functionality, and then allowing you to review the test results.
The system exerciser offers you an interface from which you can perform

actions including the following:
e

Specify tests to add to a test run

Set the test run duration

Perform a test run

Review test run performance data

You execute system exerciser tests in test runs. A test run is a collection of
system exerciser tests. When you perform a test run, the system exerciser

executes the specified tests for the duration of the test run.

KAV30 System Exerciser

4—1

KAV30 System Exerciser
You can specify tests to monitor the following KAV30 hardware and software
functionality:

Asynchronous system trap (AST) functionality
The CVAX™

microprocessor

The VMEbus data interface
The VSB data interface
The VMEbus

interrupt functionality

The auxiliary port
The AUI port
The small computer system interface (SCSI) port

The battery backed-up random-access memory (RAM)
The first-in/first-out (FIFO) buffers
The calendar/clock
The 32-bit cascaded timers

4.2 Starting the System Exerciser
This section describes how to start the system exerciser.
exerciser, follow these steps:

To start the system

Build the KAV30 system exerciser into the VAXELN system of the KAV30
that you want to monitor. See Section 4.2.1 for more information.
Some system exerciser test require a second KAV30. When you want to
run tests that require a second KAV380, build the KAV30 secondary system
exerciser into the VAXELN system of the second KAV30. See Section 4.2.2

for more information.

When the console terminal is not connected to the KAV30 that you want to
monitor, you must connect it. See the KAV30 Hardware Installation and
User’s Information manual for more information.

Load and run the VAXELN

exerciser on the KAV30
more information.

system that includes the KAV30 system

that you want to monitor.

See Section 4.2.3 for

When you want to run tests that require a second KAV30, load and run the
VAXELN system that includes the KAV30 secondary system exerciser on
the second KAV30. See Section 4.2.3 for more information.

4-2

KAV30 System Exerciser

4.2.1

Building the System Exerciser Into a VAXELN System
Use the VAXELN System Builder with the appropriate data file to build the
KAV30 system exerciser into a VAXELN system. The VAXELN System Builder
offers you a menu interface through which you can enter information about the
system that you are building. The data file contains answers to the System
Builder prompts. See the VAXELN Development Utilities Guide for a complete
description of the VAXELN System Builder.
To build the KAV30
steps:

system exerciser into a VAXELN

Create a work directory.

the system exerciser files.

system, follow these

Use this directory to preserve original versions of

Copy the following files to the work directory:
e

ELN$:KAV$EXERCISER.DAT

ELN$:KAV$EXERCISER.EXE

Change the data file answers that do not apply to the VAXELN system
that you are building. The data file has the following specification,
ELN$:KAV$EXERCISER.DAT.
Delete device description entries for devices that the KAV30 does not have.
For example, when the KAV30 does not have the SCSI option, delete the
DUA

description entry.

Change the System Builder parameters that do not apply to the VAXELN
system that you are building.

See the KAV30 Programmers Reference

Information manual for more information about the System Builder
parameters.

Invoke the System Builder with the following command:
S

EBUILD/NOEDIT

KAVSEXERCISER

The /NOEDIT qualifier specifies that you do not want to enter the menu
system interface. The System Builder uses the data file answers to build
the new VAXELN system.

KAV30 System Exerciser

4-3

KAV30 System Exerciser

4.2.2

Building a Secondary System Exerciser Into a VAXELN System
Use the VAXELN System Builder with the appropriate data file to build the
KAV30 secondary system exerciser into a VAXELN system.
To build the KAV30 secondary system exerciser into a VAXELN system, follow
these steps:
1.

Create a work directory. Use this directory to preserve original versions of

the system exerciser files.

Copy the following files to the work directory:
e

ELN$:KAV$EXR_SECONDARY.DAT

ELN$:KAV$EXR_VME_DATA SECONDARY.EXE

ELN$:KAV$EXR_ETHERNET_SECONDARY.EXE

ELN$:KAV$EXR_UART_SECONDARY.EXE

ELN$:KAV$EXR_INTS_SECONDARY.EXE

Change the data file answers that do not apply to the VAXELN system
that you are building. The data file has the following specification,
ELN$:KAV$EXR_SECONDARY.DAT.
Delete device description entries for devices that the KAV30 does not have.
For example, when the KAV30

DUA description entry.

does not have the SCSI option, delete the

Change the System Builder parameters that do not apply to the VAXELN
system that you are building. See the KAV30 Programmers Reference
Information manual for more information about the System Builder
parameters.

Invoke the System Builder with the following command:
S

EBUILD/NOEDIT

KAVSEXR_ SECONDARY

The /NOEDIT qualifier specifies that you do not want to enter the menu
system interface. The System Builder uses the data file answers to build
the new VAXELN system.

4-4

KAV30 System Exerciser

4.2.3

Loading and Running the VAXELN System
After you build either the KAV30

system exerciser or the KAV30

secondary

system exerciser into a VAXELN system, use one of the following methods to
load the VAXELN system onto the KAV30 and to run the system:
¢

Downline load the VAXELN system over the Ethernet from the host system
to the KAV30 and boot the system

Copy the VAXELN system to a DEC™
boot the system from the SCSI disk

SCSI floppy disk or hard disk and

For more information about loading and running VAXELN
VAXELN Development Utilities Guide.
When you boot a new VAXELN

systems, see the

system containing the KAV30

system exerciser,

the KAV30 runs the exerciser and displays the exerciser screen on its console
terminal.

Figure 4—1 shows the initial KAV30

Figure 4-1

Initial KAV30 System Exerciser Screen

KAV30
System
Exerciser
¥1.0
(C)
Digital
Equipment
Corporation,

State

KAYS0_EXR>

system exerciser screen.

1991.

STOPPED

When you boot a new VAXELN system containing the KAV30 secondary system
exerciser, the system containing the KAV30 system exerciser can perform
system exerciser tests with the new VAXELN system. The new VAXELN
system does not display an interface.

KAV30 System Exerciser

4-5

KAV30 System Exerciser

4.3 System Exerciser Screen
This section describes the system exerciser screen.
KAV30

system exerciser screen.

Figure 4-2

Figure 4—2 shows a sample

Sample KAV30 System Exerciser Screen

KAY30O System
Exerciser
‘V1.0
(Ci) Digital
Equipment
Corporation,

State
Runtime
Errors
detected

1991.

:
:
:

STOPPED
2
0

minute(s)

KAY3SO_LEXR:
INIT
KAYS0O_EXR>
SET RTC
KAY30_EXR>
SET RUN/OURATION="0
00:04:00"
KAVYSO_EXR>
GO
eke
Test run complete
— Performing
Post-run
cleanup
#**
KAY3SO_EXR>
REVIEW
RTC - no errors
detected
RTC ran
6B times,
used
600.0000
ms of cpu
time

KAV3O_EXR>

The system exerciser screen has the following characteristics:
e

4-6

The top half of the screen displays the following information:
-

The test run status

The number of minutes the exerciser is performing the present test run

The number of errors detected during the present test run

The bottom half of the screen is a scrolling region that displays the
following information:
-

Previously executed exerciser commands

Exerciser message text

The exerciser command prompt

KAV30 System Exerciser

4.4 System Exerciser Commands
This section describes the system exerciser commands.
e

They are as follows:

Arguments: <comment> specifies comment text.
Qualifiers: None.
Description: This command prefixes a comment.

The system exerciser

ignores text between an exclamation mark (!) and the next end-of-line
character.

6 EXIT
Arguments: None.
Qualifiers: None.

Description: This command exits you from the system exerciser.
The system exerciser actions depend on the system configuration. For

example, when you run the system exerciser from VAXELN Command
Language (ECL), the system exerciser returns you to the ECL prompt.

Arguments:

None.

Qualifiers: None.
Description: This command performs a test run. When the system
exerciser finishes the test run, it performs a cleanup operation for
approximately one minute.

INITIALIZE
Arguments: None.
Qualifiers: None.
Description: This command

initializes a test run.

§6REVIEW

Arguments:
Qualifiers:

Description:

None.

This command displays the performance data for the

previous test run.

KAV30 System Exerciser

4-7

KAV30 System Exerciser
e

SET <test name>

[/Pl=<parameter>

...

/P10=<parameter>]

Arguments:

<test name> specifies a system exerciser test name.

more information about system exerciser tests.
Qualifiers:

See Section 4.5 for

/P1 to /P10 specify parameters to the test specified in <test name>.

Starting with /P1, specify the parameters.
parameters in any order, for example:
SET

INTS/P2=1/P1=8

Description:
run.
e

You can specify the

This command adds the specified test to the current test

SET RUN/DURATION=<time>
Arguments:
Qualifiers:

None.

/DURATION=<time> specifies the duration of the current test run.
Specify <time> in standard VMS delta time, and enclose it in quotes
("). The default duration is one minute.
Description: This command sets the duration of the current test run.
Example: To set the test run duration to three days, enter the
following command:
SET
e

WAIT

RUN/DURATION="3

00:00:00.00"

<time>

Arguments:

<time> specifies the amount of time to pause the exercise execution.

Specify <time> in standard VMS delta time, and enclose it in quotes (").
Qualifiers: None.
Description: This command pauses the exerciser execution for the

specified amount of time.

For example, the following commands monitor all the 32-bit cascaded timers
and the calendar/clock for one hour:
!

Initialize

the

test

INIT

4-8

KAV30 System Exerciser

run

KAV30 System Exerciser

Add

SET
SET
SET
SET
SET
SET
!

tests

the

test

run

duration

RTC
TIMER/P1=0
TIMER/P1=1
TIMER/P1=2
TIMER/P1=3
TIMER/P1=4

Set

the

test

SET
|

RUN/DURATION="0

01:00:00"

Perform

the

test

run

! Review

the

test

run’s

GO
|
performance

data

REVIEW

4.5 System Exerciser Tests
This section describes the system exerciser tests. They are as follows:
e

§6AST

Description:

This test monitors the AST functionality.

Requirements:

None.

Restrictions: None.
Parameters: None.
e

CVAX

Description: This test monitors the CVAX microprocessor. The test
executes as a low-priority compute-bound process within the system

exerciser.
Requirements:

None.

Restrictions: None.
Parameters: None.

KAV30 System Exerciser

4-9

KAV30 System Exerciser
e

DATA Pl P2 P3 P4 P5 Po P?
Description:

This test monitors VMEbus

data transfers between two

KAV30s. It performs master accesses, slave accesses, and location
monitoring. The system exerciser displays VME DATA when referring to

this test.
Requirements:
1.

The KAV30 rotary switch is set to the value F

A second KAV30 running a VAXELN system that includes the KAV30
secondary system exerciser

Restrictions:
Parameters:

You can only specify one DATA test in a test run.

The number of transfers.

The VMEbus A24 base address of the KAV30 that runs the secondary
system exerciser. Specify either the decimal or hexadecimal value.
Prefix hexadecimal values with OX.

The swapping operation that the KAV30, running the system
containing the KAV30 system exerciser, performs. Specify 0 for
byte swapping on outgoing accesses. Specify 1 for byte swapping on

The default is one.

incoming accesses.

The address modifier codes that the KAV30 operating in master mode
uses. Specify 0 for A24 user mode codes. Specify 1 for A24 supervisor
mode codes.

The byte swapping mode that the KAV30, running the system
containing the KAV30 system exerciser, uses. Specify 0 for mode
0 swapping (default). Specify 2 for mode 2 swapping. Specify 3 for
mode 3 swapping. The KAV30 running the system containing the
KAV30 secondary system exerciser uses mode 0 swapping.

Whether the KAV30, running the system containing the KAV30
system exerciser, performs unaligned accesses. Specify 0 for aligned
accesses only (default). Specify 1 for both aligned and unaligned
accesses. The KAV30 running the system containing the KAV30
secondary system exerciser only performs aligned accesses.

accesses.

When

you specify 7, the system

exerciser

performs the amount of transfers specified in P1 for bytes, words,
and longwords.

4-10

KAV30 System Exerciser

KAV30 System Exerciser
e

ETHERNET Pl

Description: This test monitors Ethernet communication between two
KAV30s.
Requirements:
1.

A second KAV30 running a VAXELN system that includes the KAV30
secondary system exerciser

Restrictions:

Parameters:
Pl

None.

The number of bytes to transfer. The default is one.

FIFOS Pl
Description: This test monitors the FIFO buffers.
Requirements: None
Restrictions: You can only specify four FIFOS tests in a test run—one
for each FIFO buffer.
Parameters:
Pl

The FIFO buffer to monitor. Specify 0 for FIFO buffer 0 (default).
Specify 1 for FIFO buffer 1. Specify 2 for FIFO buffer 2. Specify 3 for
FIFO buffer 3.

MEM Pl P2 P3 P4 P5 Po P7

Description: This test monitors memory accesses to another VMEbus
or VSB device. The test writes a specified amount of data to the
device’s memory, reads back the data, and verifies the transfer.
Requirements:
1.

A VMEbus

Restrictions:

or VSB

device

In a test run, you can specify one MEM test for each

device on the VMEbus and VSB

Parameters:
Pl

The number of transfers.

The base address of the other device for the type of access that you
want to perform. Specify either the decimal or hexadecimal value.
Prefix hexadecimal values with OX.

The default is one.

The bus to use. Specify 0 for the VMEbus (default).
VSB.

Specify 1 for the

KAV30 System Exerciser

4-11

KAV30 System Exerciser

The address modifier codes that the KAV30, operating in master
mode, uses. Specify 0 for A24 user mode. Specify 1 for A24 supervisor
mode. Specify 2 for A32 user mode. Specify 3 for A382 supervisor
mode. Specify 4 for A16 user mode. Specify 5 for A1l6 supervisor
mode.

The type of data access to perform. Specify 0 for longword accesses
(default). Specify 1 for byte accesses. Specify 2 for word accesses.
Specify 4 for longword accesses. Specify 7 for byte, word, and
longword accesses. When you specify 7, the system exerciser
performs the amount of transfers specified in P1 for bytes, words,
and longwords.

INTS Pl P2

Description:

VMEbus

This test monitors the generation and handling of

interrupts.

You can specify that the KAV30

generates and

handles interrupts itself (default), or you can specify that the KAV30
interacts with a second KAV30.

When you specify that the KAV30 interacts with a second KAV30,
the KAV30 generates interrupts which a second KAV30 handles. The
second KAV30 then generates an interrupt at the interrupt-request
(IRQ) level of the interrupt it handles. The KAV30 then handles this
interrupt.

The system exerciser displays VME INTS when referring to this test.
Requirements:
1.

4-12

When you want the KAV30 to interact with a second KAV30, you
must have a second KAV30 running a VAXELN system that includes
the KAV380 secondary system exerciser

KAV30 System Exerciser

Restrictions:
Parameters:

You can only specify one INTS test in a test run.

The IRQ level at which to generate the interrupt. Specify 0 for IRQ
1 (default). Specify 1 for IRQ 1. Specify 2 for IRQ 2. Specify 3 for
IRQ 3. Specify 4 for IRQ 4. Specify 5 for IRQ 5. Specify 6 for IRQ 6.
Specify 7 for IRQ 7. Specify 8 for all the levels (that is, IRQ 1 through
to IRQ 7)

The mode of operation. Specify 0 when the KAV30 both generates
and handles the interrupt itself (default). Specify 1 when the KAV30
interacts with a second KAV30.

RD BBRAM

Pl P2 P3

Description: This test checks that the specified character is at the
specified location in the user region of the battery backed-up RAM. The
test runs immediately after you issue the command to execute it. Use
this test with the WR_BBRAM test.
Requirements: None.
Restrictions:
Parameters:

None.

The number of bytes to read. The default is one byte.

The offset into the user region of battery backed-up RAM. The default
is zero.

The ASCII character whose value is at the offset. The default is *.

RTC

Description: This test monitors the calendar/clock. The test uses the
calendar/clock to generate an interrupt every second, and counts the
number of interrupts in a ten-second period.
Requirements: None.
Restrictions: You can only specify one RTC test in a test run.
Parameters: None.
SCSI Pl

Description:

This test monitors the KAV30 SCSI interface.

Requirements:
1.

A Digital SCSI disk that is initialized with a valid FILES-11 disk
structure

Restrictions:

None.

KAV30 System Exerciser

4-13

KAV30 System Exerciser

Parameters:
P1
2

TIMERS

The disk drive’s SCSI ID. The default is zero.
Pl

Description:

This test monitors a 32-bit cascaded timer.

generates an interrupt every second,

interrupts in a ten-second period.
Requirements: None.

Restrictions:

The test

and counts the number

In a test run, you can specify one TIMER test for each

32-bit cascaded timer.

Parameters:
Pl

The timer to monitor.

Specify 0 for cascaded timer 0 (default).

1 for cascaded timer 1. Specify 2 for cascaded timer 2.

cascaded timer 3. Specify 4 for cascaded timer 4.
e

Specify

Specify 3 for

Ulto U8

Description: The KAV30 system exerciser allows you to create up
to eight system exerciser tests (U1 to U8). See Section 4.6 for more
information.
°

UART Pl

Description:

This test monitors the KAV30 auxiliary port.

Requirements:
1.

The KAV30 auxiliary port must be connected either to a loopback
connector, or to the auxiliary port of a second KAV30

When you want to connect the KAV30 auxiliary port to a second
KAV30, you must have a second KAV30 running a VAXELN system
that includes the KAV30 secondary system exerciser

Restrictions:
Parameters:

Pl
e

WR BBRAM

None.

The number of bytes to transfer. The default is one.
Pl P2 P3

Description:

This test writes the specified character to the specified

offset into the user region of the battery backed-up RAM.

The test runs

immediately after you issue the command to execute it. Use this test
with the RD_BBRAM test.

Requirements:

4-14

KAV30 System Exerciser

None.

KAV30 System Exerciser

Restrictions:

None.

Parameters:
Pl

The number of bytes to write. The default is one.

The offset into the user region of battery backed-up RAM.
is Zero.

The ASCII character to write to the battery backed-up RAM. The

The default

default is ™.

4.6 Creating System Exerciser Tests
This section tells you how tu create system exerciser tests. The KAV30 system
exerciser includes a number of tests. However, you can supplement these tests
with your own tests. Use one of the eight test templates to write a system

exerciser test. The templates, which are in the ELN$ directory, have the
following specifications:
KAV$EXR_USER_1_PROCESS.PAS
KAV$EXR_USER_2_PROCESS.PAS
KAV$EXR_USER_3_PROCESS.PAS
KAV$EXR_USER_4_PROCESS.PAS
KAV$EXR_USER_5_PROCESS.PAS
KAV$EXR_USER_6_PROCESS.PAS
KAV$EXR_USER_7_PROCESS.PAS
KAV$EXR_USER_8 PROCESS.PAS

To help you write tests, the KAV30 system exerciser includes a VAXELN
Pascal™ user-callable interface. This interface consists of a number of
functions and procedures that allow you to access KAV30 system exerciser data

structures. The functions and procedures are as follows:

KAVSEXR
WAIT FOR START

When you issue the GO system exerciser command, the exerciser signals

an event. This function waits for the system exerciser to signal that event.
Call this routine after you perform test-specific initialization.

KAVSEXR UPDATE WORK DONE

This procedure updates the number of times the test runs.
use the REVIEW

command

When you

at the system exerciser interface, the system

exerciser displays the number of times the test ran. Supply a single
parameter, index, to this procedure. This procedure passes the index
parameter to the system exerciser test as a process argument.

KAV30 System Exerciser

4-15

KAV30 System Exerciser

KAVSEXR _ RECORD

START

CPU TIME

This procedure records the time that the system exerciser test starts to use
the CPU. The system exerciser uses this time to calculate the CPU usage
time that it displays when you use the REVIEW command at the system
exerciser interface. Supply a single parameter, index, to this procedure.
This procedure passes the index parameter to the system exerciser test as
a process argument.

KAVSEXR RECORD END CPU TIME

This procedure records the time that the system exerciser test finishes
using the CPU. The system exerciser uses this time to calculate the
CPU usage time that it displays when you use the REVIEW command
at the system exerciser interface.

this procedure.

Supply a single parameter, index, to

This procedure passes the index parameter to the system

exerciser test as a process argument.

KAVSEXR _ END

RUN

This boolean function returns true when the test run finishes. If system
exerciser tests contain explicit calls to WAIT_ANY, specify KAV$EXR_
END_OF_RUN as a condition that it waits for.
KAVSEXR _ LOCK DISPLAY
KAVSEXR UNLOCK DISPLAY

Surround all WRITEs and WRITELNs with these procedures.
procedures protect the writing of data on the screen.
e

These

KAVSEXR _ COPY QUALIFIER VALUES

This procedure obtains the values of the system exerciser test’s qualifiers.
Supply the following three parameters to this procedure:
-

Index

Count

Qualifier_values

This procedure passes the index parameter to the system exerciser test as
a process argument.

The count parameter is an integer value that specifies

the number of qualifiers. The Qualifier_values parameter is a packed array
of integer values that returns the qualifier values.

4-16

KAV30 System Exerciser

KAVSEXR HANDLE ERROR

This procedure records the number of errors that this system exerciser test
detects. Supply the following four parameters to this procedure:
-

Index
Verbose

Prefix
Status

This procedure passes the index parameter to the system exerciser test as
a process argument. The verbose parameter is a boolean value. Specify

TRUE

for the verbose parameter if you want the system exerciser test

to display an error message when an error occurs. Otherwise, specify
FALSE for the verbose parameter. When you specify FALSE, the system
exerciser only records that an error occurred.

The prefix parameter is a

varying _string(80) value that specifies a text string to display as part of
the error message.

The status parameter is an integer error status value.

To create a system exerciser test, follow these steps:
1.

Create a work directory. Use this directory to preserve original versions of
system exerciser files.
Copy the test template that you want to use to the work directory.
Enter the relevant information in the original test template.
Compile the test template. For example, enter the following command to
compile KAV$EXR_USER_1_PROCESS.PAS:

$ EPASCAL KAVSEXR
USER 1 PROCESS + ELNSEXR OBJLIB/LIB + KAVSRTL_OBJLIB/LIB - + RTLOBJECT/LIB
Replace the test template in KAV$EXR_OBJLIB.OLB. For example, to
replace KAV$EXR_USER_1_PROCESS.PAS, enter the following command:

$ LIB/REPLACE ELNS:KAVS$EXR OBJLIB KAVSEXR
USER 1 PROCESS
Link the system exerciser as follows:
LINK

ELNS : KAVSEXERCISER OPT/OPT

Start the system exerciser. See Section 4.2 for more information.

KAV30 System Exerciser

4-17

Sample Installation
This appendix contains a sample KAV30 software installation.
S @SYSSUPDATE: VMSINSTAL

VAX/VMS
It

Software

KAV010

Product

MKB500:

Procedure
for

6-MAY-1991

10:41.

Enter

a question

mark

(?)

any

* Are

you

with

the

backup

The

following

KAV

time
of

help.

your

products

will

processed:

installation

KAV

V1.0

V5.4-2

system

disk

[YES]?

YES

moved

V1.0

Beginning

SVMSINSTAL-I-RESTORE,
Additional
1.
2
3.
4.

Installation

satisfied

OPTIONS

Restoring

Release

Notes

10:41

product

save

setA...

Options:

Display release notes
Print release notes
Both 1 and 2
None of the above

* Select option [2]: 2
* Queue name [SYSSPRINT]:

SYSSPRINT

* Do you want to continue the installation [N]?: YES
SVMSINSTAL-I-RELMOVED, Product’s release notes have been
DEC

VAXELN

KAV

TOOLKIT

EXTENSIONS

¢KAV-I-VMS, Checking VMS version
*KAV-I-VERSION, VMS Version 054,
Product:
Producer:
Version:

Release

* Does

this

Date:

product

FOR

VMS

key

registered

SYSSHELP.

RELEASED

KAV-TOOLKIT-V
DEC
1.0

1-NOV-1990

have

authorization

and

loaded?

YES

Sample Installation

A-1

Sample Installation

This kit contains
IVP verifies that

You

for

can

VMS

You can
the IVP
Digital

run the

you

IVP to verify

installation.

the DEC VAXELN

KAV Toolkit

(IVP). The
your system.

Extensions

run the IVP either during or after the installation. To run
after the installation, execute the following command at the
Command Language (DCL) prompt:

S$ @SYSSCOMMON:

* Do

an Installation Verification Procedure
the installed software is available on

[SYSTEST.KAV] KAVSIVP .COM

To run the IVP during
following question:

the

installation

want

after

the

installation

This

installation

modifies

the

following

files

your

system:

the

following

files

your

system:

run

the

IVP

procedure,
[YES]?

answer

YES

ELNS :RTL.OLB
ELNS : RTLOBJECT.
OLB
ELN$: SHARED STATUS TEXT.EXE
This

installation

ELNS
: 300KER.EXE

installs

ELNS : 300KER.
MAP
ELNS : 300KER.
STB
ELNS : EBUILD
. EXE
ELNS : EBUILD.
HLB
ELNS :KAV$RTL_OBJLIB.OLB
ELNS : KRDRIVER.
EXE
ELNS : SCSI53C700.
OBJ
ELNS : SCSI53C700.OPT
ELNS :SCSI53C700 SCRIPT.OBJ
ELNS:KAVDEF.H, .PAS, .FOR, .ADA
ELNS : KAVSEXERCISER.DAT
ELNS : KAVSEXERCISER.
EXE
ELNS : KAVSEXERCISER.
OPT
ELNS :KAVSEXR ETHERNET SECONDARY
.EXE
ELNS : KAVSEXR_INTS SECONDARY .EXE
ELNS :KAVSEXR_OBJLIB.OLB
ELNS : KAVSEXR SECONDARY .DAT
ELNS : KAVSEXR UART SECONDARY
. EXE
ELNS :KAVSEXR
USER 1 PROCESS.PAS
ELNS :KAVSEXR
USER 2 PROCESS.PAS
ELNS : KAVSEXR USER 3 PROCESS.PAS
ELNS : KAVSEXR USER 4 PROCESS .PAS
ELNS : KAVSEXR_USER_5 PROCESS.PAS
ELNS :KAVSEXR
USER 6 PROCESS.PAS
ELNS : KAVSEXR USER 7 PROCESS.
PAS
ELNS :KAVSEXR
USER 8 PROCESS.PAS
ELNS : KAVSEXR VME DATA SECONDARY
.EXE
ELNS : KAVEXRDEF
. PAS

A-2

Sample Installation

the

Sample Installation

This installation
system:

installs

the

following

example

programs

[YES]?

YES

your

[SYSHLP EXAMPLES. KAV]KAV MVME.FOR
[SYSHLP . EXAMPLES .KAV]KAV_TIMER.C
[SYSHLP . EXAMPLES . KAV] MVMEDEF . H
[SYSHLP. EXAMPLES .KAV]MVMEDRIVER.C
[SYSHLP . EXAMPLES .KAV]MVMEDRIVER AST.C
[SYSHLP . EXAMPLES .KAV]MVMEDRIVER ISR.C
ISR AST.C
[SYSHLP . EXAMPLES. KAV]MVMEDRIVER
]
.K AV] ] VDADDRIVER.C
[SYSHLP. EXAMPLES

ADA
[SYSHLP . EXAMPLES -KAV] ] FIFO AST ROUTINES.
[SYSHLP . EXAMPLES .KAV] FIFO CONSUMER.ADA
[SYSHLP. EXAMPLES. KAV]FIFO ~CONSUMER.DAT
[SYSHLP . EXAMPLES .KAV]FIFO ] PRODUCER.ADA
[SYSHLP . EXAMPLES .KAV] FIFO PRODUCER.DAT
SIGNALLER TASK.ADA
[SYSHLP EXAMPLES .KAV]FIFO ]
* Do

you

want

purge

files

The installation
remainder of the
depending on the
-VMSINSTAL-I-RESTORE,
The

replaced

this

installation

procedure will not ask any
installation takes between
processor configuration.

Restoring

installation

product

procedure

renames

ELNS:300KER.OLD
*, and deletes
files.

save

set

all

more questions. The
5 and 20 minutes,
...

ELNS:300KER.*

versions

files

of ELN$:300KER.OLD*

The installation procedure updates ELNS:RTL.OLB and ELN$:RTLOBJECT.OLB.
If either of these files is not present, the installation procedure
aborts.
=KAV-I-UPDLIB, updating ELNS:RTL.OLB...
*“KAV-I-UPDOBJ, updating VAXELN Kernel global data...
-KAV-I-UPDOBJ, updating VAXELN global parameter...
“KAV-I-INSOBJ, inserting KAV Kernel global data...
~KAV-I-UPDOBJ, updating VAXELN Kernel vector table...
“-KAV-I-UPDOBJ, updating VAXELN Kernel messages/text...
*KAV-I-UPDLIB, updating ELN$:RTLOBJECT.OLB...
=KAV-I-UPDOBJ, updating VAXELN Kernel messages for EPASCAL...
-VMSINSTAL-I-SYSDIR, This product creates system disk directory
SYSSCOMMON: [SYSHLP.EXAMPLES.KAV] .
“VMSINSTAL-I-SYSDIR, This product creates system disk directory
SYSSCOMMON: [SYSTEST.KAV] .
-VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

System

The

installation

procedure

invokes

image

size

pages

Kbytes);

495

(248

the

IVP.

file

size

496

blocks

Sample Installation

A-—3

Sample Installation
This IVP provides a downline loadable system
KAVSIVP.SYS in SYSSCOMMON: [SYSTEST.KAV] .
This system can be used to verify the correct
installation of the KAV software and the KAV30
hardware, it however requires the KAV30 to be
installed and ready.
Before you downline load the IVP system
use the following commands to setup the
NCP

Set

Node

<Name>

Address

S
S

NCP
NCP

Set
Set

Node
Node

Hardware Address 08-00-2B-nn-nn-nn
Load File SYSSCOMMON: [SYSTEST.KAV]KAVSIVP.SYS

MC
MC

A-4

<Addr>

Upon successful installation and
KAV30 module will start counting
with 00 in the status display.

bootup, the
up starting

DEC

for

VMSINSTAL

$ LOGOUT

database:

S MC

VAXELN

Installation

SYSTEM

NCP

Toolkit

Extensions

KAV

V1.0

completed

procedure

done

logged

6-MAY-1991

Sample Installation

KAV

out

VMS

10:47

10:48:01.39

10:47

IVP

completed

successfully.

Files Modified and Installed
This appendix lists the files that the KAV30 software installation modifies and
installs on the system.

The installation modifies the following files in the ELN$ directory:
File

Modification

RTL.OLB

Add KAV data structures, KAV routine entry
points, and extended VAXELN kernel message
codes

RTLOBJECT.OLB

Add VAXELN

SHARED_STATUS_TEXT.
EXE

Add KAV kernel-specific message codes and

message codes

Pascal extended VAXELN

kernel

message texts

The installation installs the following files in the ELN$

directory:

File

Description

300KER.EXE

KAV30 kernel image

300KER.MAP

KAV30 link map

300KER.STB

KAV30 symbol table

EBUILD.EXE

VAXELN System Builder image

EBUILD.HLB

VAXELN System Builder help library

KAV$RTL_OBJLIB.OLB

KAV30

KRDRIVER.EXE

SCSI port driver image

SCSI53C700.0OBJ

SCSI NCR 53C700 port driver object code

SCSI53C700.0PT

SCSI NCR 53C700 port driver option file

SCSI53C700_SCRIPT.OBJ

SCSI NCR 53C700 port driver script

runtime library

Files Modified and Installed

B—1

Files Modified and Installed

B-—2

File

Description

KAVDEF.H

KAV30 VAX C™ language definitions

KAVDEF.PAS

KAV30 VAXELN Pascal language
definitions

ELN$:KAVDEF.FOR

KAV30 VAX FORTRAN™
definitions

KAVDEF.ADA

KAV30 VAX Ada™ language definitions

KAV$EXERCISER.DAT

KAV30 system exerciser VAXELN System
Builder data file

KAV$EXERCISER.EXE

KAV30 system exerciser image

KAV$EXERCISER.OPT

KAV30 system exerciser linker options

KAV$EXR_ETHERNET_SECONDARY.EXE

KAV30 secondary system exerciser image

KAV$EXR_INTS_
SECONDARY.EXE

KAV80 secondary system exerciser image

KAV$EXR_OBJLIB.OLB

KAV30 system exerciser object library

KAV$EXR_SECONDARY.DAT

KAV30 secondary system exerciser
VAXELN System Builder data file

KAV$EXR_UART_
SECONDARY.EXE

KAV30 secondary system exerciser image

KAV$EXR_USER_1_PROCESS.PAS