Digital PDFs

DEC-XV-IRSMA-A

September 1976

34 pages

Original

1.1MB

Document:	Master Index
Order Number:	DEC-XV-IRSMA-A
Revision:
Pages:	34
Original Filename:	http://bitsavers.org/pdf/dec/pdp15/XVM/DEC-XV-IRSMA-A_XVM-RSXsysMan/DEC-XV-IRSMA-A_pt12_System_Installation_Guide.pdf

OCR Text

XVM/RSX PART XII
VIB SYSTEM INSTALLATION GUIDE

XVM/RSX V1B

September 1976

CHAPTER 1
INTRODUCTION

This part of the manual describes how to build an XVM/RSX system in
general terms.
Familiarity with XVM/DOS is assumed. Users who are
unfamiliar with XVM/DOS are advised to read the following manuals
before attempting to build a system:
1.

XVM/DOS System Installation Guide

XVM/DOS Users Manual

Building an XVM/RSX system is a seven-stage process. The first stage
is building an XVM/DOS system tailored to the user's hardware system.
(The disk on which this system is built will hereafter be called the
system disk.) Next, a program supplied with XVM/RSX must be run under
DOS to generate a batch job file.
This program asks various questions
regarding
the
user's
hardware
system
and
desired software
configuration. From the information supplied, a batch job file
is
generated capable of building an RSX system in its initial form.
The
third stage in the process is to run the batch job, mounting those
XVM/RSX distribution tapes requested. This completes the XVM/RSX VIA
build procedures.
A similar sequence of operations has to be
performed to update the system to XVM/RSX VIB. This must be done
before going on to the next stage.
At this point in the build proc~dure, the user has a "preconfigured"
XVM/RSX system on disk (i.e.,"a system that has RSX built into DOS),
but one in which RSX has not yet been activated. This system should
then be saved on tape via the DOSSAV program supplied with XVM/DOS.
Next, the user must tailor XVM/RSX to the specific needs of the
installation.
Finally, any additional tasks such as user programs,
I/O handlers or system programs should be installed into the XVM/RSX
system.
Under certain circumstances, it is desirable to configure a system in
which a complete DOS system is used for bootstrapping an RSX system
If this
from a different disk (referred to as a cross-disk system).
software
configuration
is required, read Appendix B for more
information.
The user is strongly urged to read this entire part of the manual
before attempting to build an XVM/RSX system. Chapters 2 through 5
describe the steps necessary to build a system and explain the reasons
for doing each one. These chapters are not system build instruction,
but contain essential information for followinq the actual build
procedures found in Chapter 6.
.

XVM/RSX V1B

XII-1-1

September 1976

CHAPTER 2
BUILDING AN XVM/DOS SYSTEM

XVM/RSX uses XVM/DOS as a base.
RSX must be built into a DOS system
before it can be used.
The DOS system should be built following the
directions given in the XVM/DOS System Installation Guide.
This
system must contain:
1.

The A version of the system disk handler and the A version of
the cross-disk handler, if any.

The A version of either the magtape or DECtape handler,
(whichever one can read the RSX system distribution tapes).

The SGEN, PIP,
PATCH,
MACRO, DOSTKB, UPDATE and EXECUTE
system programs.
(The file EXECUT BIN must exist in both the
BNK and PAG UFOs of the system disk.)

If the user's installation has UNICHANNEL hardware, PIREX must contain
drivers for all DOS and RSX UNICHANNEL peripheral device handlers to
be used by either system. The spooling facilities can be installed in
the system, if desired.
If RSX is to reside on the RF fixed-head disk, the DOS system built on
that disk should be as small as possible. Only those DOS system
programs and binary files specifically required to build RSX should be
installed in DOS. This is recommended, because the RF disk may be too
small to store a large DOS system, a complete RSX system and user
files.
It is mandatory that the XVM/DOS RF disk system have the
maximum number of free disk blocks if the RSX Executive must be
assembled.
In this text, it is assumed throughout the RSX build procedures that
the DOS MICLOG password is SYS.
The program called BUILD, which
generates a batch job file for building XVM/RSX into XVM/DOS, must be
run on the system disk.
Under no circumstances should the DOSSAV
system distributed with XVM/DOS be used as a base for
building
XVM/RSX.
The required XVM/DOS system must be generated usinq the
XVM/DOS build procedures.

XVM/RSX V1B

XII-2-1

September 1976

I
I

CHAPTER 3
GENERATING A DOS BATCH JOB FILE

After the XVM/DOS system has been built, the program called BUILD
be run to generate a DOS batch job.

3.1

can

PREPARING TO RUN BUILD

On the RSX distribution tape DEC-XV-IXRAA-A-UC3 for DECtape media,
DEC-XV-IXR2A-A-MC7 for 7-track Magtape media, or DEC-XV-IXR2A-A-MC9
for 9-track Magtape media are the files CODE SRC, RSXPAT XCU, RSXPAT
XCT, BUILD XCU, and BUILD XCT.
Prior to running BUILD, all five of
these files should be transferred to the system disk.
This step
reduces the time required to load and execute BUILD.
After making the appropriate
• OAT slot assignments, PIP may be
requested. Then each of these five files can be transferred from tape
to disk.

3.2

RUNNING BUILD

Once RSXPAT XCU, RSXPAT XCT, BUILD XCT, BUILD XCU, and CODE SRC are on
disk, BUILD can be run using the EXECUTE XVM/DOS system program.
In order for BUILD to create a batch file capable of building XVM/RSX
into DOS, the user must supply that program with various information.
The following subsections explain what questions are asked and how to
answer them.
The titles of these subsections specify most of the
questions.
1.

Is your distribution media DECtape?
This question determines the device to be used when PIPing
files from tape to disk during the batch job run.
If the
user received the XVM/RSX system on DECtape, the answer
should be 'YES ' . Otherwise, the answer should be 'NO ' .

xrr-3-1

Do you want TKB to be a DOS system program?
There is a version of the RSX Task Builder, TKB, which can be
made to run under DOS.
Its inclusion into DOS is optional.
If it is desirable to build RSX tasks under DOS, answer
'YES'. Otherwise answer 'NO'.

Do you have floating point hardware?
The user should respond according to the installation's
hardware
configuration.
The
answer to this question
determines if the floating point version of the RSX system
library,
.LIBFX BIN, should be transferred to disk.
In all
cases the non-floating point library,
.LIBRX BIN, will be
transferred.
This question also relates to the transfer of
the floating point version of the FORTRAN IV compiler.
More
information
on
this
latter
point
will be supplied
subsequently.

Is this disk the RSX system disk?
Unless the user plans to use a complete DOS system on one
disk and an RSX system on another
(i.e.,
a cross disk
system), the a.nswer should be 'YES'. Only if a cross disk
system is being built and the user is building a system on
his DOS system disk should the answer be
'NO'.
If this
question is answered 'NO', then BUILD will ask:
SPECIFY RSX SYSTEM DISK(1=RK,2=RP,3=RF):
The user should respond by typing the numeric code identified
with the type of disk to be the RSX system disk.
This
question ends the dialogue between BUILD and the user in this
case.

What is your memory size in K words?
In the case where an RSX system disk is being built, BUILD
will ask for the installation's memory size.
The user should
respond with the decimal number of K word increments of
memory on his system,
i.e.,
increments of 1024 memory
locations.
The number specified should be an integral
multiple of 4. This number must also be between 32 and 128.

Do you want the standard RSX executive?
BUILD must determine if the user desires a special version of
the XVM/RSX executive.
If the user has XVM hardware,
requires no more than 64 LUNs (comparable to
.DAT slots in
DOS), and has no more than six terminals, the answer should
be 'YES'.
If the standard version of the executive is not
desired, the following questions will be asked:
Do you have XVM hardware?

XII-3-2

How many LUNs do you want?
How many terminals do you have?
The first of these questions should only be answered 'YES' if
the user has an XVM computer or an XM-lS option on a PDP-IS
computer. If the answer is 'NO', the NOXM assembly parameter
will
be
defined when assembling the executive.
This
parameter's definition will cause the removal of the Share
directive and the Task Timing routine associated with XVM
hardware.
The other two questions are self explanatory and require only
a decimal integer to be supplied. The number of LUNs must be
between 21 and S12. The number of terminals must be between
1 and 17.
NOTE
The last few questions asked by BUILD determine which
TSK files will be transferred from tape to disk. TSK
files are linked binary files from which a core image
of the task is written on disk when the task is
installed by RSX.

Do you want all the standard MCR functions?
Regardless of the user's response, all
mandatory
MCR
functions will be installed in the system. If the RSX system
disk is the RF, only those MCR functions which the user
specifically requires should be installed. Hence, for RF
users the answer should usually be 'NO'. If not all of the
standard MCR functions are needed, each optional MCR function
will be listed so the user can indicate which ones are
desired.
Optional MeR functions can also be installed
on-line once the disk storage requirements of the system are
more clearly defined~

Do you want all the standard TDV functions?
This section of the dialogue is analogous to that relating to
MeR functions. If this question is answered 'NO', BUILD will
interrogate the user to determine what TDV functions are
needed.

Indicate which of these I/O handlers you want.
BUILD must determine if the user wants a DECtape handler,
standard line printer handler (LPIS), or a UNICHANNEL line
printer handler (LPll). The answer to this set of questions
is obvious from the user's hardware.

XII-3-3

10. Do you want the RSX checkout package?
The checkout package
is optional.
It is
recommended,
however,
that
it be run at installations that have not used
RSX before.
11. Do you want the RSX batch subsystem?
The XVM/RSX batch subsystem is optional.
It can be installed
on-line.
Unless the user is certain that RSX Batch will be
used, the response should be "NO".
12. Do you have UNICHANNEL hardware?
This question is asked only if the system disk is not an RK
disk or
if the UNICHANNEL line printer handler was not
selected.
If the question is answered "YES", the RSX POLLER
task
is transferred to disk.
This task is responsible for
interrogating PIREX to determine the status of UNICHANNEL I/O
devices.
It should not be transferred to disk for systems
without UNICHANNEL hardware .

• When BUILD has completed its dialogue, a batch job file is written on

the device assigned to .DAT slot 2.
This batch job can then be run to
build an XVM/RSX VIA preconfigured system.
If BUILD detects an erroneous answer,
the user's response
is
rerequested.
If ,the user wishes to stop BUILD prematurely, he can do
so by typing CTRL/C.

3.3

RUNNING THE BATCH JOB

The batch job file written by BUILD can be invoked via the DOS Monitor
batching mechanism.
Whenever
the batch
job asks for a tape to be
mounted and pauses, the user should mount the tape on the indicated
drive and type CTRL/R to resume the batch job.
Following these
procedures results in the creation of a preconfigured XVM/RSX VIA
system on the system disk.

3.4

BUILDING XVM/RSX VIB

An XVM/RSX VIB system can be preconfigured after
system build procedures have been completed.

the

foregoing

VIA

NOTE
If you do not
intend
to
include
MULTIACCESS
in RSX, but you do wish to
have batch processing,
use
the batch
system available with version VIA.
The
new MULTIACCESS Batch
Processor
is
incompatible with the VIA TDV facility.
There are three files on the distribution medium that must be
These
transferred
to the system disk in order to build XVM/RSX VIB.

XVM/RSX V1B

XII-3-4

September 1976

files are BUILD XCT, BUILD XCU and CODE SRC.
(These should not be
confused with files of the same name from the XVM/RSX VIA build
procedures.) The necessary PIP commands to transfer the files are
shown below.
Both DECtape 1 and magtape versions are shown. The
portion of each command that varies is enclosed in brackets.
$PIP
>T SY <SCR>,+{MT } BUILD XCT,BUILD XCU (B)
DTO
>T SY <SCR>+{MT }
DTO

CODE SRC

Proceed with the RSX build procedures by bootstrapping the DOS system
at memory location 77637
(octal).
Enter the following set of DOS
commands:
$A SY 1,2/TT 12,13
$XVM OFF
$BANK ON
$E BUILD
BUILD then asks a series of questions concerning
constructing the system. The para~eters are:
Parameter

for

Meaning

NLU

Number of LUNs in the RSX system.

MA.NLU

Number of virtual LUNs per MULTIACCESS user.

TTYS

Number of terminals on the system.

MCRTMO

Number of seconds before MCR timeout occurs.

NOMAC

The system is non-MULTIACCESS if this parameter is
defined (given a value).

PARITY

Parity processing is included on terminal
this parameter is defined.

I/O

NOXM

This parameter is defined if the
management option does not exist.

memory

LIGHTS

This parameter is defined if a rotating light
pattern is desired in the AC, XR, LR and MQ.

The questions
paragraphs.
1.

parameters

asked

BUILD

are

explained

XM-15

the

following

Is the DOS and RSX system disk the same disk?
If the DOS and RSX systems reside on the same disk, answer
"YES" to this question and the next question will be skipped.

Enter the RSX system disk type (l=FK, 2=DP, 3=DK).
Enter a decimal number corresponding to the disk type that
will contain the RSX Executive and tasks. This disk must be
patchable and have a DOS file structure.

For DECtape, be sure to use drive

XVM/RSX VIB

XII-3-5

September 1976

Do you have a DECtape update kit?
If the answer is "NO", a magtape kit is assumed.

Do you have TKB as a DOS system program?
DOSTKB is a required component for the XVM/RSX VIB build
procedures.
If space has already been allocated on the DOS
system disk for TKB, answer "YES" to this question.

Do you have magtape?
If your system configuration includes a magtape, answer "YES"
to this question.

Do you have UNICHANNEL hardware?
If your system configuration includes
end, answer "YES" to this question.

UNICHANNEL

front

Do you have an LP-11?
If a line printer is connected
"YES" to this question.

the

UNICHANNEL,

answer

If you have the XM-IS memory management option, answer
to this question.

"YES"

Do you have XVM hardware?

Do you have floating-point hardware?
If you have the FP-IS floating-point option, answer "YES" to
this question.
If you answer "NO", the next question is
skipped.

10.

Do you want the non-floating-point compiler and libraries?
To include FOR as a TDV function task, answer "YES"
question.

11.

this

Do you want to run MULTIACCESS?
If you want to run the new multiuser version of
"YES" to this question.

12.

TDV,

answer

Do you want the RSX batch subsystem?
If you answer "YES" to this question, the components of the
batch-processing subsystem are assembled and the resulting
binary files are stored under the RSX UIC.
At this point,
however, certain pieces of the batch-processing software will
not be constructed. These pieces are FORTRAN code and must
be compiled with the RSX FORTRAN Compiler.
It is the user's responsibility to insert
into RSX.

13.

th~

batch subsystem

Do you want ODT?
If you answer "YES" to this question, the binary
placed under the RSX UIC.

ODT

It is the user's responsibility to insert ODT into RSX.

XVM/RSX V1B

XII-3-6

September 1976

14.

Do you want to run the default system?
If you answer "YES" to this question, no further questions
will be asked and the following default values will be
assumed for the parameters listed:
Default Value (Decimal)

Parameter

NLU
MA.NLU
TTYS
MCRTMO
NOMAC
PARITY
NOXM
LIGHTS
15.

16.

MULTIACCESS

Non-MULTIACCESS

200
25
5

64
3
60

How many LUNs do you want?

[64 or 200]

The numbers in
non-MULTIACCESS
respectively.

are the default values for a
a
MULTIACCESS
system,
and

brackets
system

How many LUNs/user do you want?

[25]

If you have not specified a MULTIACCESS system, this question
is not asked.
To plan the number of LUNs/user, use the formula:
(total number of LUNs-64)/number
(must be at least 24)
17.

How many terminals do you have?

users=

LUNs/user

[3 or 5]

The numbers in brackets are the default values for
non-MULTIACCESS and a MULTIACCESS system, respectively.
18.

Enter the number of seconds for
[O=no MCR timeout]

the

MCR

timeout

interval.

The number entered can be 0, or 15 or more.
Any number
between 1 and 14 causes the RSX Executive not to assemble.
19.

Do you want parity processing on terminal I/O?
If some of the terminals attached to your system require
correct parity to operate properly, answer "YES" to this
question. Odd parity is generated.

3.5

RUNNING THE BATCH JOB

The batch job file written by BUILD can be invoked via the DOS Monitor
be
batching mechanism. Whenever the batch job asks for a tape to
mounted and pauses, the user should mount the tape on the indicated
Followingthese
drive and type CTRL/R to resume the batch job.
procedures results in the creation of a preconfigured XVM/RSX VIB
system on the system disk.

XVM/RSX VIB

XII-3-7

September 1976

3.6

SAVING THE PRECONFIGURED SYSTEM

Once a preconfigured RSX system has been generated, it must be saved
on tape with the DOSSAV program.
The use of DOSSAV is described in
the XVM/DOS Users Manual.
Saving the system at this point is very
important, because it is needed whenever the RSX Executive is modified
and whenever updates of XVM/RSX are distributed.

XVM/RSX V1B

VII-3-8

September 1976

CHAPTER 4
RSX CONFIGURATION PROCEDURES

This section describes basic RSX configuration procedures which are
used to define devices, partitions, and other system characteristics
to RSX.

4.1

RSX: BOOTSTRAPPING THE RSX SYSTEM

The RSX system can be automatically bootstrapped from the
disk by requesting a program installed in the DOS system.
the following:

DOS system
Simply type

If this is the first time RSX has been invoked in this way, the system
will respond by requesting configuration.

4.2

RSX SYSTEM CONFIGURATION

The system configurator asks a short set of questions to determine
various
characteristics
of the XVM/RSX system.
The following
subsections explain how the user should respond.
The titles of these
subsections specify the questions.
All numeric responses are in
decimal notation except where otherwise noted.
Typing a carriage
return in response to a question gives the bracketed value specified
in the question.
1.

Specify number of clock ticks per second [60]:
The user should respond with
the
frequency
of
the
installation's KW-15 real time clock.
In the United States
this number wiil usually be 60;
50 in Europe.

Specify core size [32K]>
Here the user should supply his installation's core memory
size in K words, e.g., 64K, 96K, etc. The number must be an
integral multiple of 4 and must be between 32 and 128.

XII-4-1

CAUTION:
This number may be smaller than or equal to the
answer specified to BUILD's question asking for memory size.
It cannot be larger.
If a larger number is specified, file
structure degradation may occur!
3.

MCR partition size octal

(3000] >

Under normal circumstances the user should accept the default
value.
If a smaller value is chosen several mandatory MCR
functions ( ... INS, ... RCF, etc.) may not be installed in that
partition.
The system configurator will reject a value
greater than 3000 octal.
4.

System disk;

[RF], RP, RK>

The user must supply the name of the RSX system disk type.
The response governs the disk type from which the system
configurator's version of INSTALL will obtain TSK files and
where the SAVE MCR function will write core images of the
system.
5.

How many RF platters?

(0]>

The number of RS09 disks on the system should be the answer.

How many RP disks?

[0] >

The number of RP02 disks on the system should be the answer.

How many RK disks?

[0] >

The number of RK05 disks on the system should be the answer.

How many large nodes?

[10] >

This answer governs the number of partitions which can be
specified in the system. Additional large nodes can be added
using the RCF MCR function.
Usually the default value should
be accepted.
9.

How many small nodes?

[150]>

This parameter may be highly variable.
The user is advised
to consult the System Management section (Part III) for an
explanation of small node usage.
Usually, the default value
should be accepted.
More small nodes can be added to the
system later with RCF.

XII-4-2

4.3

SYSTEM CONFIGURATION ERROR MESSAGES

There are several error messages which may be encountered during
system configuration.
The following list shows all error messages
which may be output during the user's dialogue with the system
configurator.
***IF YOU HAVE KTl5 (MEMORY RELOCATE) THE
***PROTECTjRELOCATE SWITCH IS SET WRONG
ILLEGAL NUMBER OF TTY'S PATCHED IN
AAASYNTAX ERR AT "X" -- RETYPE
AAAINVALID SIZE -- RETYPE
AAANAME ALREADY USED -- RETYPE
***RE-ENTRANT ECO PACKAGE NEEDED
INSUFFICIENT CORE OR NODES, TRY AGAIN
'RSX' UFD NOT ON SYSTEM DISK
NODES WOULD OVERFLOW DISK PARTITION
In addition to thes~ error messages, the System Configurator's version
of INSTALL may issue various others while attempting to install the
initial set of tasks. Refer to the documentation on the INSTALL MCR
function for more details.

4.4

SETTING UP AN RSX ENVIRONMENT

After the SystemConfigurator has run to completion, the XVMjRSX
system is established. Before a true multiprogramming environment can
be established, however, a series of procedures must be followed to
describe and enable terminals, and back up the newly configured
system. Specifically, the user must define the characteristics of
every terminal in his system using the DTC MCR function.
Then, the
system disk files handler should be assigned to various LUNs.
Finally, an image of core should be written to the RSX system disk via
the SAVE MCR function.
Then, if the user wishes to run the RSX
checkout package, the following steps should be done.

XII-4-3

Invoke On-Line System
Configurator

MCR>RCF
TYPE UNITS "NAME(BASE,SIZE)"
PARTITION
>COPI(70000,2000)
>COP2(72000,3000)
>COP3(75000,2000)

Assign partitions for
Tasks in the checkout
package

End of partition
specifications

SYS COM

No COMMON block
specifications

No additional small node
specification at this
time

SMALL NODE

>
LARGE NODE

No additional large node
specifications at this
time

>
TYPE N TO EXIT

Indicate satisfactory
input

RCF OK!

Successful reconfiguration

MCR>INS
MCR>INS
MCR>INS
l\1CR>INS

SATCHK
RX
COPHM
DTRUN

Install certain tasks
necessary to run the
checkout package

MCR>SAVE

Back up the current RSX
system

MCR>COP

Invoke the RSX checkout
package

MCR>KCH

Stop (kill) checkout
package output

COP-CANCELLED BUT ACTIVE TASKS RUN THROUGH COMPLETION
CAUTION -- DON'T ABORT EXEC MODE COP TASKS!

XII-4-4

CHAPTER 5
ADDING TASKS TO THE SYSTEM

After establishing an initial RSX environment it may be desirable to
add other I/O handlers, system programs, and user tasks to the system.
For each new task to be added, use the following steps.
1.

Determine the memory requirements of the task.
For system
programs and standard I/O handlers the core requirements are
given in Appendix A of the System Management Part.
Then
define the task's partition if the partition is not already
in the system.

Assemble or compile the task's sources.
For system programs
and standard I/O handlers, the assembly parameters required
are noted in Appendix B of the System Management Part.

Task build the task.
Instructions for
building
tasks
supplied with the system are located in Appendix B of the
System Management Part.

If the task is an I/O handler, use the ADV
add PDVL nodes for this handler.

Use the RCF MCR function to enter the task's partition
the system if the partition is not already specified.

Install the task by using the INSTALL MCR function.

Use the SAVE MCR function to record
task.

XII-S-l

the

MCR

function

existence

to
into

this

CHAPTER 6
XVM/RSX SYSTEM BUILD PROCEDURES

The following figure (6-1) indicates the
building XVM/RSX into an XVM/DOS system.

XII-6-1

actual

steps

involved

CAUTION
DO NOT ATTEMPT TO USE THESE PROCEDURES UNLESS
YOU HAVE READ THE PRECEDING CHAPTERS.

NOTES

1.
2.
3.

User responses and commands are underlined;
system outputs are not.
All command lines end with a carriaqe return (.)
unless otherwise noted.
.
\-lhere several items are bracketed,
the user
must include only one item in the command line.

I},

BUILD XVM/DOS
contain:
System disk handler
!1TA or DTA
SGEN
PIP
PATCH
!1ACRO
UPDATE
EXECUTE

~1ust

NOTE:
XVr-I/DOS
build
procedures

It may be advantageous
to save a copy of the
system on tape via
DOSSAV.

XVM/DOS
UNICHANNEL
build
procedures

VIB

TRANSFER BUILD AND ITS DATA FILE TO DISK

Bootstrap DOS at 77637

Mount on drive 1 tape

3.
4.

$K ON...)

$PIP.)

>T SY

....

{~ii~

BUILD XCU, RSXPAT XCU (B)...)

>T SY

.... ~MTl}

BUILD XCT, RSXPAT XCT (B)...)

....

CODE SRC.)

$C 7.)(required only if distribution medium is magtape)
{MTA}
DTA

11...)

DTI

>T SY

10.

>tC

II.

$BANK ON.)

12.

$XVM OFF-./

{MTl}
DTI

(type CTRL/C)

START BUILD

1.
2.
3.

$A TT 12,13.)
$A SY <SCR> 1,2,-4...)

Figure 6-1. Guide to Building XVM/RSX.
XVM/RSX VIB

XII-6-2

September 1976

NOTE
TO answer BUILD questions. type y..} for YES
and N---' for NO. In response to questions
asking for a numerical answer. type the
appropriate integer.

Specify RSX
system disk
(l=RK. 2=RP. 3=RFl:

RUN
RSXGEN terminates

BATCH
JOB

Figure 6-1 (Cant.) Guide to Building XVM/RSX.

XII-6-3

N....!

Indicate
which of these
MeR functions

you want.

Figure 6-1 (Cant.) Guide to Building XVM/R8X.

XII-6-4

Indicate
which of these
TDV functions
you want.

*Only asked i~ floating point
hardware is available.

Figure 6-1 (Cant.) Guide to Building XVM/RSX.

XII-6-5

Indicate
which of these
I/O handlers
you want.

RUN
BATCH
JOB

*Asked only if the system disk is
not RK and the LPll line printer
handler was not selected.

Figure 6-1 (Cant.) Guide to Building XVM/RSX.

XII-6-6

NOTE
\..:Then the BATCH job asks that
a particular tape be Mounted,
it-- will pause. After mounting
the tape on the specified
drive, the user should type tR
to resume the BATCH job.

Define terminal
characteristics.

"ICR>DTC TTO

VT50
KSR33 )
KSR35
LA30
baud_/
{ VT05
LA36

HCF.>DTC TTn

VT50
KSR33 )
KSR35
LA30
baud.J
{ VT05
LA36

RUN BATCH JOB
Mount tapes as
requested:
$BATCH SYA RSX.)

Reassign system disk file
handler.
DOSSAV the system
HCR>REA 5,10,11,15,17,18

{~R~P·}

""ONE.J

\')ri te an image of core to the
system disk.

Bootstrap XVM/DOS
from the DOS system
disk.

MCR>SAVE.J

Bootstrap XVM/RSX
by typing:

END
Answer the system
configuration
questions:
NOTE
At this point, the user can
run the checkout package
as described in section 4.4
or add any other tasks
as described in Chapter 5.

Enter time and date:
MCR>ETI hour:min:sec
month/day/year~

Figure 6-1 (Cont). Guide to Building XVM/RSX.

XVM/RSX V1B

XII-6-7

September 1976

TRANSFER BUILD AND ITS DATA FILE TO DISK

Bootstrap DOS at 77637

Mount on drive 0 tape

$K ON..)

$C 7..-J

(required only if distribution medium is magtape)

$A {MTA}..-J
DTA

(required only if distribution medium is magtape)

$PIP..-J

>T SY <SCR>, + {~;} BUILD XCT, BUILD XCU

>T SY <SCR>+{~;} CODE SRC..-J

>tc

DEC-XV-IXRUA-A-UAl}
DEC-XV-IXUIA-A-MC7
{ DEC-XV-IXUIA-A-MC9

(B)..)

(type CTRL/C)

START BUILD
1.

$A SY 1,2/TT 12,13.)

$XVM OFF..)

$BANK ON~

$E BUILD..)

Enter the RSX
system disk type
(l=RK, 2=DP, 3=DK).

Set the crossdisk indicator.

Figure 6-1 (Cont). Guide to Building XVM/RSX.

XVM/RSX VIB

XII-6-8

September 1976

Reset system
defaults.

Figure 6-1 (Cont). Guide to Building XVM/RSX.

XVM/RSX V1B

XII-6-9

September 1976

Enter the number of
seconds for the MCR
timeout interval.
[O=no MCR interval]

Generate the
batch file

Figure 6-1 (Cont). Guide to Building XVM/RSX.

XVM/RSX VIB

XII-6-10

September 1976

APPENDIX A
REPLACING THE RSX EXECUTIVE

From time to time it may be necessary to replace the RSX executive.
This will be the case if the user wishes to reassemble the executive
with a different set of assembly parameters, correct an error, modify
the functions of the executive, or include an updated version.
To do this, restore the preconfigured RSX system to the RSX system
disk with DOSSAV. Transfer the correct source files of the executive
into the SCR UFD on that disk. Then assemble the executive under DOS
with the desired assembly parameters as indicated in Appendix B of
System Management Part. Next MICLOG under DOS so the RSX executive
can be PATCHed into the system. Assign .DAT slot -10 to the A version
of the DOS system disk handler and associate it with the SCR UFD e.g.,
$ASSIGN RKA <SCR> -10. Then invoke the DOS system program PATCH and
enter the new version of the RSX executive as follows:
$PATCH
PATCH XVM Vnxnnn
>RSXIMG
>READ RSX.P2
>EXIT
$
The sources and binary files of the RSX executive can now be deleted
from disk.
The updated preconfigured RSX system should be saved on
tape.
It will then be necessary to invoke
the
RSX
system
configurator, define terminal characteristics, REASSIGN devices, etc.

XII-A-l

APPENDIX B
BUILDING A CROSS DISK SYSTEM

If the user's installation has two or more disk types, a cross disk
system may be desirable. This is especially true if the user plans to
use XVM/DOS extensively and one of his disks has limited storage
capacity
(e.g., RF-RP combinations). To create a cross disk software
system, the user will have to build a standard RSX system on the disk
on which he wants to store installed tasks. This disk will hereafter
be called the RSX system disk.
It must also contain a minimal DOS
system.
Furthermore, the user will have to build a typically larger
DOS system on the DOS system disk, i.e., on the disk from which RSX
will be bootstrapped.
The DOS system disk must contain an RSX
bootstrap as a DOS system program.
It is this disk which the user
should use when operating under DOS.
This process can be accomplished by following the RSX build procedures
through the final DOSSAV operation for both disks to be used. There
is only one exception. Once the batch run for the RSX system disk is
complete, perform the following extra steps:

Mount on drive 1 DEC-XV-IXRAA-A-UB2,
DEC-XV-IXRIA-A-MC9.

$MICLOG SYS

$A SY 10 /{DTA} 11
MTA

$C 7 (Required only if the distribution media is Magtape)

$PIP

)R SY <RSX) ••• DSY TSK

DT _{DOS. RK}
)T SY <RSX) ••• DOS TSK _ { MTI
RP TSK (B)
DOS.RF

)"C

DEC-XV-IXRIA-A-MC7

SY <RSX) .•. DOS TSK

(Type Control C)

The choice of the files DOS.RK TSK, DOS.RP TSK, or DOS.RF
correspond to the DOS system disk type,
i.e., RK,
respectively.

XII-B-l

TSK
RP,

should
or RF

When building the system on the RSX system disk,
avoid adding DOS
modules which are not specifically required to build RSX. When
building the system on the disk to be used when running DOS (i.e., the
DOS system disk) be sure to specify that this disk will not be the RSX
system disk.
Once built in its entirety, the RSX
follows:

system
sy~tem

can

bootstrapped

Bootstrap DOS off the DOS

In response to the DOS monitor's "$" type RSX.
be bootstrapped off the RSX system-disk.

disk.
RSX will then

When RSX is bootstrapped the first time, the user should establish the
proper environment by configuring RSX in the standard fashion.
It
will als~ be possibl~ to enter RSX fr6m the 'RSX system disk by:

Bootstrapping DOS'off the RSX system disk.

Typing RSX in response to the monitor's "$".

When running RSX and it is desired to bootstrap DOS off the DOS system
disk,
simply request the MeR function DOS via the standard MeR
interface.
It will also be possible to bootstrap the DOS system on the RSX system
disk from RSX by requesting the MeR function DSY via the standard MeR
interface.
The DSY MeR function
is simply the standard DOS MeR
function (bootstrap DOS off the RSX system disk) under a new name.

XII-B-2

CHAPTER 3
RSX CHECKOUT PACKAGE

A 'oheckoutpackage is supplied with the RSX PLUS III system 1:0 be used
in ensuring' '. that an installation fS hardware and 'lJysten.t software .'.

are

thorou9h1y'testea.

The package consists of the f.ollowing Tasks:
Task
RX

Function
LOw priori ty Task that sets JU, lU, R3 ,
F:4 ,; R5 ,
!l:6 ,
~:ll,
lU.2, X13, X14, XlS, Xl6,. Xl7, XR, LR, MQ,

no,

SC, L20, and optionally ,FP15 ,registeJ,"s, . continually
checks thatc:ontents of registers are notal.tered, and
logs in and (Jut on LUN-3,.
DTRlJN

W.rites file on DECtape unit 2, reads' it back to verify
contents (DI:Ctape with' a cleared~ directory should be
used) ,and logs in and out on LUN-3.

COPHM

. Logs in and out on LUN-3 to note pas$a~Je of

one

hour

of checkout package execution'.

TTY:[O

Prints message on LUN-3askinqfor numbe~r of. terminals
in system, requests that m.essage be typed.by opel:ator
on each of these terminals, and repeats this mes,sa.ge
on the appropriate terminaltentlmes.

SATCHK

Checks that disk driver and alloca.tor~re . fUllctionil'l,q
properly. for each disk in system, verifies 1:hat:bit
maps on each .disk are intact.. and does~,o~ cl11,:er any
data on the disks.
'

••• COPHCR

function

which

synchronizes

ex.~:uti<:itl

of ... F.'X,

DTRUN, COPHM, TTYIO, and: SATCHK •
•• • RCH

MCR function which cancels f'uture reques,ts
in checkout package.

for

'l'asks

There ares4lveralprocedures which must. be follow$d to instilll t'hese
checkout Tasks and x"eassign LUNs to be used for checkout purpc\ses.
During the :initial RSXconfiguration pro(~~ss< desc;-ibed in Chapter 1 clf
this manual, the user should be sure to do' the follow.in.q:

3--1

Install all Tasks listed above.

If the in,stallation has DECtape, install the DECtape Handler
and mount a DECtape on unit 2, write enabled. The DECtape
directory must be cleared. If the installation does not have
DECtape, remove both the DECtape Handler (namedM' •••• ) and
the DTRUN Task from the system with the REM MCRfunction.

Deassign LUNs 30 through 37 byreassigninq them to NONE with
the MCR REASSIGN Function. This is necessary because ••• COP
alters these LUN assignments.

Enter the time and date with the MeR ETIME function.

The checkout package synchronizes the Tasks described above to verify
that all devices are working properly and that multiproqramming has
been established in the RSX PLUS III syst~m.
To begin running
checkout, the user types the following at the MeR terminal:

MCR) COP
The command should be terminated with an ALTMODE (.n.ot a carriage
return) in order to free the MCR terminal for other output. This MeR
conmand invokes the Task named ••• COP, which synchronizes execution of
the other checkout Tasks, as follows,:
SYNC rue M OM SM
SYNC SATCHK M 1M SM.
SYNC DTRUNM 2M SM
SYNC TTYIO M 1305
SYNC COPHM M .3601S lH
The effect of this synchrordzation is that different Tasks will be
simultaneously accessing differen.t devices. RX and SATCHK will begin
examining registers and bit maps.
Then
DTRUN
will
initiate
verification of DECtape file and hardware integrity. Each terminal in
the system will then be accessed by TTYIO, which requests a messagE! of
the operator for each terminal and repeats it ten times, as Sh~l in
the printout below.
Tests will continue in this manner' until
terminated explicitly by the operator with the RCH MCR fWlction p as
follows:
MCR)KCH
If checkout continues for more than one hour, COPHM will. note the
passage of this and subsequent hours by logging onLUN-3. Any errc)r
. messages will be printed on the MCR terminal and followed by I~ string
of backarrows(+-) extending to the right margin.•
The following printout appears on the MCR terminal.

HCR) COP

~-2

* RSXCHECKOUT PACKAGE -- LUNS 30-37 *
• HAVE BEEN ALTERE.D ,PER PHYSICAL UNIT •

* EXISTENCE.

AWRltE-ENABLEDDECTAPE.
*
• WITH A NEW DIRECTORY IS NEEDED ON
• UNIT TWO (IF OECTAPES IN SYSTEM).
*

00:14:00 -- BEG~NREGISTER TEST
00:15:00 --,S2GINBIT MAP VERIFICATION
ALLoCATE ERROR ON RP1 I I . ' I • • I • I I I I • • • • •
GET ERROR ON RP 1 I . I • • • e" • 1 • I • I I I I • •
ALLOCATE ERROR ON RPI ••• ,,1,1, ••••••••

rue begins

SATCHK beqin.s .
RP errors

I
.

(Unit.

1 wasc,ff lint!)

GET ERROR ON RPl ••••••• • I I • I • • I I • I •

ALLOCATE ERROR ON RPI

Ie. II •• II • "

•• I • I

GET ERROR ON RP 1 •• I • • • « I I 1 I • • • • • t ••
ALLOCATE ERROR ON RP 1 • I • • 1 • • • • • '. , I , • • I

00:16:00 -- BEGIN DT I/O TEST
GET ERROR ON RPl • I f • • • I I • t I • • • I •• I .~
BOW MANY TTY'S DO YOU HAVE?3

DTRON begins

System requests
nwnber of
terminals

00:16 :13-- END BIT MAP VERIFICATION
·PLEASE TYPE A L,INE TERMINATED WITH A CAR RTN. ON EACH TTY

GGGKLLOYTRREGHBNM097654EDY80
'GGGI<LLOYTRREGHBNM097654EDY80
GGGKLLOYTRREGHBNM097654EDY80
GGt':.KLLOYTRREGHBNM097654EDY80
GGGKLLOYTREEGHBNM097654EDY80
GGGKLLOYTRREGHBNM097654EDY80
GGGKLLOYTRREGHBNM097654EDY80
GG(;KLLOYTRREGHBNM097654EDY80
00 ::17:16 _. END ImGISTER TEST
GGGKLLOYTRREGHBNf~09 7654EDY80
GGGKLLOYTRREGHBNM097654EDY80
GGGKLLOYTRREGHBNM097654EDY80
00:17:41 -- END 0'1' I/O TEST
MCR)KCH
COP CANCELLED BUT ACTIVE TASKS RUN THROUGH COMPLETION
CAUTION -- DON'T ABORT EXEC MODE COP TASKS 1
MCR)

SATCHIc ends

System types
User t~"Pes
System types
remainder

RX ends

DTRUN ends
Endc:heckout run
Return to MeR

. Additional termina'ls will be addressed as shown below:
PLEASE· TYPE A I,INE TEJU.1INATED· WITH A CAR RTN,

ON EACH. TTY

DFGHJKLOIY~GGG6890

DFGHJKLOIYREWWGGG6890
DFGHJKLOIYREWWGGG6890
DFGHJKLOIYREWWGGG6890
DFGHJKLOIYREWWGGG6890
DFGHJKLOIYREWWGGG6890
DFGHJKLOIYREWWGGG6890

System types
User types
System types
remainder

DFGH~LOIYREWWGGG6890

DFGHJRLOIYREWW'GGG6890

DFGHJKLOIYREWWGGG6890
DFGHJKLOIYREWWGGG6890
D.FGHJKLOIYREWWGGG6890

Multiprogramming is demonstrated in this package by the fact
times, all.of the following functions are being performed:

3-3

that

I
J

• ExUlination of core reqieters

(RX)

• Examination of drivers and bit map. for each disk (SATCHJ{)
• DBCtape copy (DTRUN)

• Texminal interaction (ftYIO)

3-4

INDEX

Adding tasks, 5-1

Batch job file,
running, 3-4, 3-7
Batch subsystem, 3-6
Bootstrapping RSX system, 4-1
BUILD, 3-1
preparing to run, 3-1
questions, 3-1
running, 3-1
Building process, 1-1
Building XVM/DOS system, 2-1
Building XVM/RSX VIB, 3-4

Carriage return, 4-1
Checkout package, 3-4
running, 4-3
Clock, 4-1
Configuration procedures, 4-1
Core size, 4-1
Cross disk system, 1-1, 3-2
building, B-1
CTRL/C, 3-4
CTRL/R, 3-4, 3-7

LPll, 3-6
LUNS,
number of, 3-3, 3-7

MCR,
partition size, 4-2
timeout interval, 3-7
Memory size, 3-2
MULTIACCESS, 3-6

DDT, 3-6

Partition size, 4-2
Password, 2-1
Preconfigured system,
saving, 3-7
Preparing to run BUILD, 3-1

Replacing RSX executive, A-I
RSX Task Builder (TKB) , 3-2
Running batch job file,
3-4, 3-7
Running BUILD, 3-1

Default values, 3-7, 4-1
DOS batch job file,
generating, 3-1

Error messages, 4-3
Executive,
replacing, A-I

Tasks, adding, 5-1
Terminals, 3-7
TK B, 3- 2, 3- 6
TSK files, 3-3

Unichannel hardware, 3-4, 3-6
Floating point, 3-2, 3-6
XVM hardware, 3-6
Generation DOS batch
job file, 3-1

Introduction, 1-1
I/O handlers, 3-3

XVM/RSX VIB

XII-Index-l

September 1976