AMT

Active Memory Technology

DAP Series

System Management under

VAX/VMS

(manO2O.O1)
4$ .
 V

Table of Contents

Chapter 1 Hardware Installation 1

1.1 Introduction 1
1.2 Hardware overview 1
1.2.1 VAX hardware 1
1.2.2 DAP Hardware 3
1.2.3 Cables 3
1.3 Installing a DRB32 link 3
1.3.1 VAX-end considerations 3
1.3.2 DAP-end considerations 5
1.3.3 Cable connection 5
1.4 Installing a DR1J-W/DRV11-WA link
1.4.1 VAX-end considerations 7
1.4.2 DAP-end considerations 10
1.4.3 Cable connection 10

Chapter 2 Software Installation 13

2.1 Introduction 13
2.2 Installing on VAXclusters 14
2.3 Pre-installation checks for all products 14
2.4 Installing DAPBASE 15
2.4.1 Pre-Installation checks 16
2.4.2 Post-Installation procedures 16
2.5 Installing optional products 25
Chapter 3 PowerIng up the DAP 27
3.1 Introduction 27
3.2 Indicator lights 27
3.3 Control buttons . . .
28
3.4 Key switch 28

System Management under VAXNMS manO2O. 07 v

22 Chapter 2: Software Installation

2.4.2.6 Customizing the user The environment that is established by including the execution
environment of DPSTRTVF COM as part of system startup, may be
.

altered depending on the requirements of the DAP site. Such

changes could include the establishment of:
• Default target machine type
• Default directory specification for text files to be included
in FORTRAN-PLUS compilation
• Default text library to be included in FORTRAN-PLUS
compilation
• Default object libraries to be searched for symbol
resolution during program linkage
You can use the AMT manual DAP Series: Program
Development under VAX/VMS as a guide to the facilities
described in the following sections.

Default target machine type Many of the DAP utilities such as the FORTRAN-PLUS compiler,
the DAP linker and DAP librarian default to assuming that the
target machine is a DAP 500. To direct the software to assume
that a DAP 600 is the target machine, the D.APSIZE qualifier
is used. Thus:

[_s Di,ic S1LDP

links the DAP object file SMALL DP DOB to produce the

.

DAP executable file LARGE DAP.DEX for a DAP 500.

Howeve the command:

[s DL K/DAPSIZE=64 LARGE flAP

links the DAP object file LARGE DAP.DOB to produce the

DAP executable file LARGE flAP DEX for a DAP 600.
.

The logical name DAP_SIZE can be used to establish the

target DAP (for information on this see the manual DAP Series:
Program Development under VAX/VMS). If the target machine
is a DAP 600, it is sensible to establish a system-wide logical
name. A system-wide logical name is defined for any process
on the system and therefore removes the necessity for the
individual user to establish a private (process-wide) logical
name or explicitly specify the DAPSIZE qualifier.

To establish DAP_SIZE as a system wide logical name, such

that the target DAP is assumed to be a DAP 600, include the
following command in the startup command file:

DEFINE/SYSTEM DAP_SIZE 64

22 manO2Q.O1 AMT
2.4: Installing DAPBASE 23

The command:

$ DIJNK I1AR_DAP

will now link the DAP object file tARGE flAP DOE to produce
D
.

the DAP executable file LARGE D)P .DEX for a DAP 600.
Default text files to be included in To establish a default search path for FORTRAN-PLUS source
FORTRAN-PLUS compilation files that have been included in a FORTRAN-PLUS program,
the logical name DAPF INCLUDE can be defined (see
chapter 2 in the manual DAP Series: Program Development
under VAXNMS). If you wish to establish such a search path
on a system-wide basis, then this definition can be established
in the system startup file, using the DCL command:

[ $ DEFINE/SYSTEM DAPF INCLUDE USERDISK1: [D.P. INCLUDE]

where USERDISK1: [DAP. INCLUDE] is a directory set up

to hold the relevant FORTRAN-PLUS source files.

Default text library to be included In FORTRAN-PLUS source files may be put into a text library, and
FORTRAN-PLUS compilation included in a FORTRAN-PLUS program. The situation is similar
to that given above, except that the default is a text library
rather than a directory specification. You can use the logical
name DAP? LIBRARY to establish the default library.

For example, suppose there are a number of FORTRAN-PLUS

PARATER definitions that will be included in programs
written by many users. If these files are put into a text library in
SYS$LIBRARY called PARATERS TLB; instead of using
the DFORTRAN command:

$ DFORTRaN H ROG+SYS$IThRAPY: P1.TERS/LIBRARY

the logical name DAPF LIBRARY can be established on a

system-wide basis:

$ DEFINE/SYSTEM DPF_MBRARY SYS$MBR1RY : PI4RM4ETERS

thus simplifying the DFORTRAN command to:

[ $ DFORTR1N

System Management under VAXNMS manO2Q. 07 23

 26

o
26 manQ2Q.Q1 AMT
 Chapter 3
Powering up the DAP

3.1 Introduction The control panel of a DAP (see figure 3.1 below) includes:
• A 20 character by 2 row vacuum fluorescent display panel
• Two indicator lights:
POWER FAULT
• Three control buttons:
SELECT ANSWER EXIT
• A four-position keyswitch, with positions:
PWR OFF RESET RUN MENU

3.2 Indicator lights The green indicator POWER is a power-on’ light.

Figure 3.7
DAP control panel RUN

RESET
FAULT

System Management under VAX/VMS manO2Q.O 1 27

 30 Chapter 3: Powering up the DAP

STOP or RUN Accepting one of these options changes the displayed menu
once again, and you are now offered the menu:
STOP
RUN
These options control whether or not the item already selected
at the menu level above for example DAPTITLE is displayed
—
—

(RUN) or is not displayed (STOP). Note that the option

highlighted when the STOP/RUN menu first comes up is the
one that iscurrently active.
As a result of your selection one or more of the options listed
below will be displayed on the control panel when the key is
returned to the RUN position.
• The time
• A moving logo, along with the average temperature of the
boards inside the DAP.
Only this option is being RUN on the DAP 600 in figure
3.1 on page 27
• The temperatures of the individual boards inside the DAP
DAP TESTS Accepting the DAP TESTS option from the top level menu
allows you to run manually the self-tests which are normally run
by the DAP at power-up. You are first reminded that DPBOOT
STOP must be executed before you begin these tests by the
message:

CONFIRM DAPBOOT REMOVED

on the DAP display panel. When you confirm that

DAPMONITOR has been removed (by pressing ANSWER), .a
sub-menu is disayed.

DAP 500 tests On a DAP 500 the following tests are available:
• DAP SELF TESTS
• MCUTESTSPART1
• ARRAY STORE
• CODE STORE
• PETESTS
• MCUTESTSPART2
• MCU TESTS PART 3
• PEM/STESTS

DAP 600 tests On a DAP 600 the following tests are available:
• DAP SELF TESTS
• MCU TESTS PART 1

30 manO2O.01 AMT
3.4: Key switch 3.I

ARRAY STORE
• CODE STORE
• PE TESTS PART 1
• PE TESTS PART2
• MCU TESTS PART2
• MCU TESTS PART3
• PEM/STESTS

The first test in the menu, DAP SELF TESTS, is effectively an

amalgam of the other options, and runs each of them in turn.
When you turn the key back to RUN from MENU, the message:

RE.ADY FOR DAPBOOT

will appear on the DAP display panel for a short time. !f the
reason for selecting MENU was to change the display on the
panel, and DPBOOT STOP has not been executed, the
message READY FOR DAP300T may be ignored.

System Management under VAX//MS manO2O.O7 31

32

.
32 manQ2O.Q1 AMT
 33

Chapter 4
U sing DAPBOOT Once the DAP has been turned on and has completed its self
tests (see chapter 3), various control programs and possibly
device drivers must be downloaded to the DAP before it can
run user programs. This bootstrap procedure is carried out by
the D.APBOOT and DPMONITOR programs as described
below:

4i DAP BOOT and The process of booting the DAP is divided into two parts,
DAPMONITOR programs performed by two programs, DAPBOOT and DABMONITOR.
The DAPBOOT program is run either interactively or from the
system startup file and performs the following tasks:
• It runs the DAPMONITOR program as a detached process
• It sends boot information to DAPMONITOR
• It reports the progress of the boot process on
sS $OUTPUT
Note that operator (OPER) privilege is required to run
DAPBOOT.
When the DAP bootstrap process has been completed, the
DABBOOT program will terminate.

The DAPMONITOR program which runs as a detached

—

process .AMTDAP 1 carries out three tasks:

—

• It boots the DAP according to the information it receives

from DAPBOOT
• It records the accounting information requested (see
Chapter 6) in the accounting files:
SYS$MNAGER:DAPSYS1 LOG .

SYS $MNAGER : ACCOUNTNG .DAT

• It records DAP hardware errors in the engineer’s log file:

sYs$MNAGER:AM’rDAP_1. LOG

The DAPMONITOR program must be running before user

programs can be executed on the DAP.

If DAPYONITOR terminates due to a DAP error it sends the

following message to the operator’s console via the OPCOM
process:

DAPMONITOR has terminated

System Management under VAX/VMS manO2O.O1 33

34 Chapter 4: Using DAPB DOT

The process of booting the DAP consists of loading the

following programs:
• DAP message server
• DAP MCU control program
• DAP HCU control program
• User written HCU-based device drivers
The names of the files containing the above programs are held
in the DAP configuration file which is created by the
DPCONFIG.COM command procedure, (see Chapter 2,
pages 16-17, for further details on running DPCON’IG). The
configuration file is read by DAPBOOT and the necessary
information is then passed to DAPMONITOR which performs
the load. DPMONITOR reports any errors in the engineer’s
log file SYS$MANAGER: AMTDAP_1 LOG and sends an error
.

status report toDAPBOOT which displays an error message on

SYS$OUTPUT. If the boot process is successful, DAPBOOT
terminates with the status message:

[ DAP booted successfully

42 DAPBOOT command The DPBOOT command has the form:

DPBOOT [I qualifiers] [action]

where:

I qualifiers specify various options to the boot process

action specifies whether the DAPMONITOR program
is to be started, restarted or stopped
The DAPBOOT parameter action takes one of the following
values:

• START
This parameter signals a request to boot the DAP,
provided the D.APMONITOR program is not already
running. If D.APMONITOR is running D.APBOOT reports an
error and terminates
• RZSTART
This parameter signals a request to boot the DAP, after
stopping the DAPMONITOR program if it is already
running
• STOP
This parameter signals a request to stop the
DAPMONITOR program

34 manO2Q.O7 AMT
 4.2: DAPBOOT command
35

The default value for action is START. The parameter can be

abbreviated provided it remains long enough to be identified
uniquely.

Note that the RESTART and STOP options both terminate

DAPMONITOR (if it is running) and this will result in any DAP
jobs currently executing being abandoned.
The DAPBOOT command can take several qualifiers which can
be used to control the way the boot process is carried out and
the subsequent operation of the DAPMONITOR program.

4.2.1 /ACCOUNTING qualifier The/ACCOUNTING qualifier controls the accounting

information written out by DAPMONITOR whenever a DAP
process terminates. There are two types of accounting output
(see chapter 6) and both are optional. The two types are:
• ASCII accounting in the DAP system log file:
SYS$MMiAGER:DAPSYS_1 LOG .

• Binary accounting in the VMS accounting file:

SYS$MNAGER : ACCOONTNG .DAT
If you specify /ACCOUNTING, both accounting files are
written this is te default. You can turn off the output to one
—

or both files by specifying /ACCOUNTING=type where type

is one (or more) of the following:
NONE specifies no accounting information is to be output
FULL specifies both accounting files are to be written (the default)
ASCII specifies that the DAPSYS_1 LOG file is to be written
BINARY specifies that the ACCOUNTNG DA file is to be written
If you give more than one type, then you should separate the
values by commas and enclose them in parentheses.
If you do use the accounting files, you should inspect or
analyse them regularly, and delete them when necessary as
they may become very large.

Note that you must stop DAPYONITOR before you can delete
DAPSYS1 LOG. You can use the DCL command:
.

$ SET ACCOUNTING/NEWFILE

to close the existing version of ACCOONTNG .DAT and open

a new one, without stopping DAPMONITOR.

System Management under VAXNMS manO2O.Q 1 35

36 Chapter 4: Using DAPSOOT

4.2.2 /CONFIGURATION_FILE You can use the /CONFIGURATION_FILE qualifier to

qualifier specify the DAP configuration file which is created by
DPCONFIG.COM (see section 2.4.2.1 pages 16-17). The
default configuration file assumed by DAPBOOT is
SYS$M3NAGER:D.APl .CFG and this is the default file
created by D.APCONFIG. CON. An alternative file can be
specified by using the /CONFIGURATION FILE qualifier in
the form:

[ $ DPBOOT/CONFIJRATION FUaE= file-spec

The file type of file-spec defaults to cFG, thus the command:

.

[ $ DAP3OOT/CONFIcJRATION_FflLE=TEST

would use the file TEST. DFG as the configuration file.

4.2.3 /FORCELOAD qualifier The /FORCEIOAD qualifier forces the D.APMONITOR

program to ignore any errors encountered during the DAP self
tests which are performed before any control programs are
loaded. Failure of these self tests indicates a fault on the DAP
and should be reported to AMI However, under certain
circumstances, it may be possible to continue using the DAP
successfully despite the failure of the confidence tests, until
the fault has been corrected. The /FORcELOD qualifier
should only be used on the advice of AMT.

4.2.4 DAPBOOT messages When DAPBOOT is invoked it sends a message via OPCOM
to the operator’s console. The foçm of the message is:

DAPBOOT started from process Id Id by user name

As the DAP boots up, each successfully loaded program is

reported via DAPBOOT to SYS$OUTPUT and to the engineer’s
log file SYS$MANAGER:AMTDP_1 LOG. If the DAP boots
.

successfully, the information message:

L%DAPBO0T_T_BooTsucc, DAP booted successfully

is displayed by DPBOOT and the message:

[ DAP booted successfully

is also sent to the operator’s console via the opcom process.

DAPBOOT then terminates. At this point, user programs can

36 manO2O.O1 AMT
4.2: DAPBOOT command 37

be executed on the DAP as described in DAP Series:

Program Development under VAX/VMS (chapter 4).
If the DAP bootstrap fails, DAPBOOT will display a failure
messge on SYS$OUTPUT. Depending on the cause of the
failure extra information may be sent to the engineers log file
SYS$MAGER :AMTDAP1 LOG. . The information
message:

%DAPBOOT-F-BOOTFAIL, OAPBOOT failed to perform the required operation

is displayed by DAPBOOT it the DAP bootstrap fails. In this

case D.APBOOT sends the message:

DAP300T failed

to the operator’s console via the OPCOM process. Other

messages will give more detailed information about the cause
of the error and these are listed in Appendix M of DAP Series:
Program Development Under VAX/VMS (editions 04 and
upwards of manOO4).

4.2.5 Files used by DAPMONITOR The DAPMONITOR program creates (if necessary) and writes
information to the following files:

• SYS$MNAGER:ACCOUNTNG .DAT
(if binary accounting is selected)
• SYS$SYSTEM:DPPARAMS .DAT
• SYS$MANAGER:]ThPSYS1 .LOG
(if ASCII accounting is selected)
• SYS$MNAGER: AMTDAP1 LOG .

Note that the accounting and log files are created if they do not
exist, but otherwise information is appended to them. Also, if
D?PMONITOR cannot create or write to D.APP.ARAMS .DAT it
will terminate and DAPBOOT will fail.

The engineer’s log file (AMTDAP1 LOG) will record error

.

information in the case of a DAP fault. If the DAP fails at any

time, please report the information in MTDA21 LOG to .

AMI

More information on AMTDP1 LOG is given in section 5.1

.

on pages 3941.

System Management under VAX/VMS manO2Q.O7 37

38

.
38 manQ2Q.Q1 AMT
 39

Chapter 5
Maintaining DAP system files
There are a variety of files used by the DAP system software to
record DAP specific information (for example DAP resource
limits, error logging and accounting). This chapter describes
the purpose of these files and how they are used.

51 Engineer’s log file The DAP engineer’s log file NTDAP_1 LOG is stored in the
.

AMTDAP YLOG directory sYs$MAGER and records the following

— information:

• The progress of the DAP bootstrap. For each attempt to

bootstrap the DAP the DAPYONITOR program outputs
the following information to ANTDAP1 LOG: .

o The date, time and host-DAP interface used

o The name of the configuration file
o Whether one or both PE banks are selected
o The times at which the DAP was last powered up and
down
a The files being down loaded to the DAP
The DAP clock speed.

Figure 5.1 on the next page shows an example of a

successful bootstrap of the DAP 500 recorded in
AMTDAP1 LOG
In addition, if the D.APMONITOR program is stopped using
either the ESThRT or STOP parameter to DAPBOOT
(see section 4.2 pages 34-35), a message of the form:

[ date tine - DAPBOOT action used to stop DAPMONITOR

is recorded in .AMTDAP . LOG, where action is either

RESThRT or STOP.
It the DAP bootstrap fails then, depending on the cause of
the error the following diagnostic information may be
recorded in the engineer’s log file.

System Management under VAXNMS manO2O.O 1 39

40 Chapter 5: Maintaining DAP system files

*******************************************************************************

Dapboot invoked on 24-FEB-l989 14:28:09.54 via DR11 parallel line

- Configuration filename: SYS$MNCER:DAPl.CFG

Both PE banks selected

Dap last powered up: Thu Feb 23 11:45:04 1989

Dap last powered down: Thu Feb 23 08:01:05 1989

DAP confidence tests successfully completed

Message Server successfully loaded from file ‘SYS$SYSTEM:MSGS.HCU’
MCUCP successfully loaded from file ‘SYS$SYSTEM:MCUCPDPIO5.DEX’
HCUCP successfully loaded from file ‘SYS$SYSTEM:HCUCPDPIOS.HCU’

Clock speed: 100 ns

Fig 5.7: An example of a successful bootstrap of The DAP 500

• A summary of any non-fatal errors and exceptions

recorded when the DAP was running, and stored in the
NVRAM of the DAP. These summaries are preceded by
the messages rror dump and Exceptions dump
respectively
• DAP failures. If a DAP hardware fault or fatal software error
occurs when the DAP is running, a summary of the
machine registers and other locations is dumped to the
engineer’s log file.
Such a dump is preceded by the message:

HCUCP dump following error on date tine

A similar dump is generated if the DAP fails one of its

confidence tests during the bootstrap procedure and is
preceded by the message:

TESTMAN dump following error on date time

If either type of dump occurs it should be reported to AMT.

An example of a dump produced during the bootstrap
procedure is given in Figure 5.2 on the page opposite.
The engineer’s log file is created (if it does not already
exist) by the DA2MONITOR program; if the file does exist,
DAPMONITOR appends to it.

40 manO2O.07 AMT
5.2: Engineers log file AMTDAP_ 7.LOG 41

flAP failed confidence test number 0 dump follows

-

TESTMAN dump following error on 22-FE3-1989 13:42:35.69

MCU Registers:
MO: 0x80808080 M7: 0x00000080
Mi: 0x20080000 MB: Ox00000lOO
M2: Ox00000000 M9: 0x00000200
M3: Ox00000000 M1O: 0x00000400
M4: 0x20020000 Mu: Ox00000BOO
M5: 0x00000020. M12: Ox0000l000
ME: Ox200c0000 M13: 0x00002000
ME: Ox0000lill MP: 0x00008000
Code Store Array Store
Datum: Ox000l0000 OxOOl00000
Limit: 0x00020000 0x00200000
DO Loop: start times count length
0xc0000067 Oxffffffff 0x0098c393 Ox00000000
offset
Ox00000000
State PC: 0xe0000067
Jump Log:
Oxe00000E7 0xe0000067 0xe0000067 0xe0000067
0xe0000067 0xe0000067 0xe0000067 0xe0000067
0xe0000067 0xe0000067 0xe0000067 0xe0000067
0xe0000067 0xe0000067 0xe0000067 0xe0000067
0xe0000067 0xe0000067 0xe0000067 0xe0000067
0xe0000067 0xe0000067 0xe0000067 0xe0000067
0xe0000067 0xe0000067 0xe0000067 0xe0000067
0xe0000067 0xe0000067 0xe0000067 0xe0000067
Link Link-i Link-2 Link-3
Instruction: 0x340f23a7 Ox9eaebebe Oxbeaebebe Ox8ebeaebe
Interrupt MCU ECU
Status: Ox00000000 Ox00000000
Enable (Sw van): Oxefffffff Oxfcffefff
Reflect Registers Address Data Statu
Array bus 0: Ox3fffffff Oxffffffff Ox6fedOfff
1: Ox3fffffff Oxffffffff Ox6fedOfff
2: Ox3fffffff Oxffffffff Ox6fedOfff
DAP bus 0: Oxffffffff Oxffffffff OxOOff9fff
1: Oxffffffff Oxffffffff OxOOff9dff
2: 0x20000022 0x20000022 OxOOff9d49

Parity A Status A Parity 3 Status B

Rows 0- 7
word 0: Ox00000000 0x80808080 Ox00000000 0x80808080
Rows 8- 15
word 0: Ox00000000 0x80808080 Ox00000000 0x80808080
Rows 16 — 23
word 0: Ox00000000 0x80808080 Ox00000000 0x80808080
Rows 24 — 31
word 0: Ox00000000 0x80808080 Ox00000000 0x80808080
End of TESTMAN dump
Dapboot halted on 22-FEB-i989 13:42:36.17

fig 5.2 An exarrple of a dump produced during The bootstrap procedure for a DAP 5(X)

System Management under VAX/VMS manO2Q.O7 47

44 Chapter 5: Maintaining DAP system files

5.5 AMT Text Libraries The DAP basic software contains several VMS text libraries
which are stored in the directory SYS$LIBRARY and are
available for general use.

5.5.1 DAPFDEF.TLB The text library DAPFDEF.TLB contains one module,

PATTERNS, which can be included in a FORTRAN-PLUS
source file and makes several useful bit patterns available to
the program (see DAP Series: FORTRAN PLUS Language,
Appendix A, for more details). The PATTERNS module does
not have to be extracted from the library since the
FORTRAN-PLUS compiler automatically searches
D.PFDEY.TLB for a text module included using the
#include directive in the form:

[ #include module-name

5.5.2 APALDEF.TLB The text library PM1DEF.TLB contains one module,

USRMACS, which can be included in an PAL source file.
USENACS makes several useful bit patterns available to the
program and also provides a set of macros designed to
simplify the taskof interfacing between different code sections
(see DAP Series: APAL Language, chapters 9 and 10). The
APAL assembler automatically searches PALDEF TLB for a
.

text module included using the #include directive as shown

above.

5.5.3 AMTFORDEFS.TLB and The text libraries MTFORDEFS TLB and ANTCDEFS TLB
.

AMTCDEFS.TLB each contain a module, MTDEF, which can be included in

VX FORTR.N and ThX C source files respectively to provide
symbolic names for the DAP accounting packet structure given
in table 6.3 on page 48.

44 manO2Q.O1 AMT
 45

Chapter 6
Accounting
6.1 DAP system AMT software generates accounting information about DAP
ACCOUNTING facilities processes in two forms:
• An ASCII text file which contains a summary of each DAP
process
• User data entries in the standard VMS accounting file
You can use the data recorded in these files to learn how the
system performs under different circumstances and how
different groups of users use the DAP; you can also use the
data for billing purposes if necessary.

6.2 The DAP system log When a DAP piocess terminates that is, DAPREL is executed or
—

the host process terminates —the DAPMONITOR program adds an

ASCII text record to the file SYS$MANAGER:DAPSYS1 LOG .

giving the following information in tabular form:

username The VAX username of the process owner
time loaded The absolute time at which the process completed loading
time unloaded The absolute time at which the process completed unloading
array size The amount of array store requested by the program f in planes)
code size The amount of code store requested by the program (in bytes)
CPU time The amount of DAP CPU time used (in milliseconds)
timeslice The final timeslice used by the process
program name The name of the DAP executable program which was run
(truncated to at most 32 characters by the VMS library routine
LIB$TRXM_FILESPEC)
If the program fails to finish loading (for example, where the
load is interrupted) then the message:

J***Load Abandoned***

is written across the columns normally used for time

loaded, array size, code size, CPU time and
times lice.

The DPSYS1 110G file also contains records indicating

.

every time DAP800T is invoked and every time a change is

made to the system parameter Quantum.

System Management under VAXNMS manO2Q.Q1 45

46
Chapter 6: Accounting

These DAPSYS1 LOG records have the form:

.

( DAPBOOT invoked on date tine

L date time Quantum set to n

You can suppress the logging of accounting information to the

DPSYS_1.LOG file by invoking DAPBOOT with the
qualifier:

/ACCOONTING=NOASCI I
Note that AMT reserves the right to change the format and
content of the data sent to DAPSYS1 LOG in future releases.
.

6.3 VMS ACCOUNTING When a process terminates that is, D?PREL is executed or
—

the host process terminates the DAPYONITOR program

—

appends a record to the VMS system accounting file

SYS $MANAGER : ACCONTNG.DAT. Each record consists of
a record header and an identifier packet, followed by a binary
accounting packet of type User data (refer to VAX/VMS

Accounting Utility Reference (VMS V4 users) or

Manual VMS

Accounting Utility Manual (VMS V5 users) for details of

accounting packets).
Figure 6.1 below shows a block diagram of the layout of fields
in a user data packet. The layout conforms to the VMS
convention in which data is represented as a series of 4-byte
strips, with the lowest address byte being at the top right of the
representation. The Count field holds the number of bytes in
User data, and occupies the first byte of the user data.

1
Length Type

Count

User data

Data (length of User data is lbyte (for Count) plus at most

255 bytes)
fields

4bytes
Endof
packet

Figure 6. 1 Block diagram of a user data packet

46 manO2O.O1 AMT
6.3: VMS ACCOUNTING 47

Table 6.1 below describes the fields contained in the packet;

their symbolic offsets from start-of-packet. and their contents.

field Symbolic offset Contents (length)

from start of packet
Type AcR$W_TYPE See table 6.2(1 word)
Length AcR$W LENGTH Total length of the packet (1 word)
User data (including Count) AcR$T_USER_DATA AMT data (counted string)

Table 6. 1 field descriptions of a user data packet

The layout of the Type field in the user data packet is set out
in table 6.2 below:

field Symbolic offset Contents (length)

from start-of-packet
Header AcR$ V_PACKET Identifies the item as a packet
it the field is set to 1 (1 bit)
Type AR$V _TYPE The user packet type code (7 bits)
ACR$K USER DATA

Table 6.2 Sub-field descr,otions for field Type

The organisation of the sub-fields in the User data field is

shown in figure 6.2 below.

MT identifier
VMS PID
Quantum Speed DP type reserved
PT]) Timeslice Status

Start time (8 bytes)

End time (8 bytes)

CPU time
Array
Code

Program name (32 bytes)

(Reserved -52 bytes)

figure 6.2 Block diagram of The subfields in the User data field in a user data packet

System Management under VAXNMS manO2Q.O 1 47

50

50 manQ2O.Q1 AMT
 51

Chapter 7
Trouble Shooting This chapter attempts to covet some of the more common
problems that you may experience in installing a DAP and
attempting to use D?PBOOT to start up the DAR
• The software installation ptocedure fails:
Action:
o Check that you have sufficient disk space to perform
the installation (see section 2.3 pages 14-15)
o Ensure that you ate logged on as SYSTE)& Software
installation may require cettain privileges that you do
not have if you are not using the SYSTEM account
• Execution of DJPSThRTUP COM either manually or
.

during system startup produces errors. This will occut if:

The adapter name is wrong — DR1 1-W/DRV11-WA only
The CSR is invalid or already in use DR1 1 -W/DRV1 1-WA only
—

(see section 1.4.1.2 pages 8-10)

The interrupt vector is invalid or already in use —

DR1 1-W/DRV1 1-WA only (see section 1.4.1.2 pages 8-10)

The VAXBI node number is invalid or already in use —

DRB32 only (see section 1.3.1.2 pages 4-5)

Action:
o Confirm the hardware settings with the DEC engineer.
For DR11-W/DRV11-WA you need to know the
Unibus/Qbus to which the device is attached, the CSR
address and intetrupt vector address of the device.
For DRB32 devices, confirm the VAXBI node number
with the Digital engineer
° Ensure that SYS$MANAGER:DPSTARTUP.COM
has been modified to reflect these values (see
chapter 1, page 18)
• Running DPBOOT returns the message:

Cannot open configuration file file-name

This occurs if D.APCONFIG has not been run

Action:
a To execute DPCON?IG use the command:

$ @SYS$MANAGFR: DIPCONFIG

Systems Management under VAX/VMS manO2Q.O1 51

 54
Chapter 7: Trouble Shooting

generally means that the device (physical) settings

and the VMS (DAP STARTUP) settings match. It the
address does not respond with anything similar to
FFEO there may well be a mismatch.
u Check the cables between the VAX and the DAP
Ensure that they are crossed Ji <--> J2
(DR1 1-W/DRV1 1-WA only)
• DAPEOOT terminates immediately with the message:

You need operator (OPER) privilege to run DAPBOOT

Action:
a Your VAX system manager must authorize the granting
of OPER privilege to you.

54 manO2O.07 AMT
Index 55

Index

A D
Accounting Facilities 45 DAP control panel 27
ACCOUNTING qualifier 35, 46 DAP System Accounting Facilities
AMT Text Libraries 44 See SYSTEM ACCOUNTING FACILITIES
AMTCDEFS.ThB 44 DAP system characteristics file
AMTFORDEFS.TLB 44 See DAPPARAMS.DAT
APALDEFTLB 44 DAP TESTS 29
DAPFDEEThB 44 DAP TYPE field 49
AMTCDEFS.TLB DAP_SIZE logical name 22
See AMT TEXT LIBRARIES DAPBASE 13-17, 19, 21, 23
AMTDAP_1 process 35 Contents of DAPBASE, 15
AMTDAP1.LOG 33, 34, 36, 37, 39, 41 DAPBOOT 15-17, 21, 28,33, 35-37, 43, 49, 51,
AMTDEF 44,49 52, 54
AMTFORDEFS.TLB Privileges Required 33
See AMT TEXT LIBRARIES DAPBOOT command 34, 35, 37
ANSWER button 27, 28, 30 Parameters 34
APALDEF.ThB Qualifiers to 34-36
See AMT TEXT LIBRARIES DAPBOOT STO 31
ASCII accounting file DAPCONFIG command procedure 16, 17, 52
See DAPSYS_1 .LOG DAPDRIVER, 4, 21
AUTOGEN 20 DAPET 24, 25
DAPF_INCLUDE logical name 23
DAPFDEFTLB
B See AMI TEXT LIBRARIES
DAPMAN 42
BOOT DAPOS 29 DAPMONITOR 15, 30, 33, 39, 40, 42, 43, 46
Booting a DAP 35-39 Files used by 37
Buses available for the VAX 2 DAPPARAMS.DAT 42
DAPRUN 24, 25
DAPSIZE qualifier 22
DAPSTARTURCOM, 7, 17-19, 21,51, 52
C
DAPSYS_1 LOG 43
Cable assembly (DR1 1-W/DRV1 1-WA) 10 DAPSYSQUE.DAT 42
Cable assembly (DRB32) 5 DAPTEMP menu option 29
Cables 3 DAPTITLE menu option 29
CES HVR-821 7 5 DASSEMBLE13
CLOCK menu option 29 DCL commands, 14,15
Configuration file (creation of) Device drivers, 4
See DAPCONFIG DFORThAN, 23
CONFIGURATIONfILE qualifier 17, 36 DLINK, 23, 24
Control and Status Register DR11-W, 1,2,3
See CSR DR1J-W/DRV11-WA 7,9,11,18,51,53
COUNT field 46 Control and Status Register (CSR) 7-9
CSR 7, 8, 53 IKON Model 10089 10-12
Interrupt Vector 7-9
Unibus/Qbus Adapter 7
DRB32 1-2, 3-5, 18, 51

System Management under VAXNMS manOO2.O7 55

 58

58 manO2O.Q1 AMT
Reader comment form
AN4T
Read9. UK
Any comments you care to make, whether reporting bugs in the manual or making more general comment,
about this or any AMT publications will help us improve their quality and usefulness. To report bugs, if you have
the time, the ideal way from our point of view is to send us a photo-copy of the relevant page, with the bug
marked on it. If you are in the UK, please use our FREEPOST address to send us the copy.
If you also can spare the time to fill in the mini-questionnaire below that would be doubly useful to us. To send
us this form, please fold it as indicated, and post it postage is pre-paid for the UK.
—

Comments

Title of publication: System Management under VAX/VMS (manO2O.O1) I other — please specify:

My name and job title:

My department: .

My company:
My company address: .

My telephone number — country: number: . . .

I found the contents:

I used the publication:
i True Partly true Not true
As an introduction to the subject Helpful D D D
j To teach myself Accurate D D D
Q To teach others Written clearly D D
As a reference manual Well illustrated D
j Other — please specify
I Well indexed D D D
Other — please specify D D D

Thank you for your help. May 89

System Management under VAX/VMS manO2O.O1 59

 Second fold
— First fold

-1

r
No postage needed for posting in the UK.
If posting outside UK, please stick stamps to normal value.
r
Publications Manager
Active Memory Technology Ltd
FREEPOST (RG 1436)
Reading
Berkshire RG6 1 BR
United Kingdom

PlOPJlflOUP13flI

Second fold
1. 1— First told
. .