Digital PDFs

AA-2874F-TC

July 1985

126 pages

Original

4.8MB

Document:	RSX-11S System Generation and Installation Guide
Order Number:	AA-2874F-TC
Revision:	0
Pages:	126
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11S_V4.2_Jul85/AA-2874F-TC_RSX-11S_4.2_Sysgen_198507.pdf

OCR Text

RSX-118
System Generation
and Installation Guide
Order No. AA-2874F-TC

RSX-11 S Version 4.2

digital equipment corporation · maynard, massachusetts

First Printing, September 1975
Revised, February 1977
Revised, December 1977
Revised, June 1979
Revised, November 1981
Revised, July 1985
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.
Copyright @ 1975, 1977, 1979, 1981, 1985
by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future
documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-IO
DECSYSTEM-20
DEC US
DECwriter

DIBOL
EduSystem
IAS
MASSBUS
MicroPDP-11
Micro/RSTS
Micro/RSX
PDP

PDT
RSTS
RSX
UNIBUS
VAX
VMS
VT

mnmaama

HOW TO ORDER ADDITIONAL DOCUMENTATION
In Continental USA and Puerto Rico call 800-258-1710

DIRECT MAIL ORDERS (CANADA)

In New Hampshire, Alaska, and Hawaii call 603-884-6660

Digital Equipment of Canada Ltd.
100 Herzberg Road
Kanata, Ontario K2K 2A6
Attn: Direct Order Desk

In Canada call 613-234-7726 (Ottawa-Hull)
800-267-6215 (all other Canadian)
DIRECT MAIL ORDERS (USA A PUERTO RICO)*
Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (INTERNATIONAL)
Digital Equipment Corporation
PSG Business Manager
c/o Dlgital's local subsidiary or
approved distributor

*Any prepaid order from Puerto Rico must be placed
with the local Digital subsidiary (809-754-7575)
Internal orders should be placed through the Software Distribution Center (SOC), Digital Equipment
Corporation, Northboro, Massachusetts 01532

Zl<2866

CONTENTS

Page

vii

PREFACE
CHAPTER 1
1.1
1. 2
1. 3
1. 4
1. 5

CHAPTER 2

INTRODUCTION TO RSX-llS
THE MEMORY-RESIDENT SYSTEM
• • 1-1
THE RSX-llS UPDATE KIT • • •
• 1-2
HOST/TARGET SYSTEMS
• • • •
• • • • • • • • • 1-3
HARDWARE/SOFTWARE CONFIGURATIONS •
1-4
VIRTUAL MONITOR CONSOLE ROUTINE
• • • •
• • • 1-5
RSX-llS SUPPLIED SOFTWARE

2.1
BASIC MCR • • • • • •
Initiating Basic MCR • • •
• • • •
•
2.1.1
2.1. 2
Basic MCR Commands • • • •
• • • •
2.1. 3
Basic MCR Error Messages
2.2
ON-LINE TASK LOADER
•
2.2.1
Invoking OTL • • • • • •
2.2.2
OTL Operation
• • • • •
Programming Hints
2.2.3
2.2.3.1
Using OTL to Load Tasks and Common Blocks
Into Memory
• • • • • • • • •
2.2.4
OTL Error Messages • • • • • • •
SYSTEM IMAGE PRESERVATION PROGRAM
2.3
2.3.1
Invoking SIP • • • •
2.3.2
SIP Operation
• • • • • • • • •
2.3.3
Hints on Using SIP • • • • • • •
SIP Error Messages • • • • • • •
2.3.4
2.4
TASK TERMINATION NOTIFICATION PROGRAM
Invoking TKTN
• • . • • • • • • • • •
2.4.1
2.4.2
TKTN Error Messages
• • • • • •
2.5
THE SETTIM CALLABLE SUBROUTINE • • • • •
2.6
SYSTEM ACTIVITY DISPLAY PROGRAMS •
FILE CONTROL SERVICES
• • • •
2.7
2.7.1
File-Processing Macro Calls
•••••
2.7.1.1
OPEN$x • • • •
• • • •
2.7.1.2
OPNS$x • • • • • • • •
2.7.1.3
OPNT$W/OPNT$D
2.7.1.4
OFID$/OFNB$
2.7.1.5
OPEN$
• • • •
2.7.1.6
CLOSE$ • • • • • • • •
2.7.1.7
GET$x
• • • •
2.7.1.8
PUT$x • • • . • . • • •
2.7.1.9
READ$, WRITE$, WAIT$ •
2. 7 .1. 10
DELET$ • • • • • • • •
2.7.2
File Control Routines
2.7.2.1
Default Directory String Routines
2.7.2.2
Default File Protection Word Routines
2.7.2.3
File Owner Word Routines • • • • • •
2.7.2.4
ASCII/Binary UIC Conversion Routines
2.7.2.5
Filename Block Routines
2.7.2.6
Directory Entry Routines • • •
2.7.2.7
Directory Information Routines •
2.7.2.8
File-Positioning Routines
2.7.2.9
Queue I/O Function Routine •
2.7.2.10
Rename-File Routine • • • • • • • •
iii

• • 2-1
• • 2-1
• • 2-2
2-4
• • 2-7
• • 2-8
• • 2-9
2-10
2-10
2-11
2-16
2-17
2-18
2-18
2-19
2-20
2-21
2-21
2-23
2-24
2-25
2-25
2-25
2-26
2-26
2-26
2-26
2-26
2-26
2-26
2-27
2-27
2-27
2-27
2-27
2-27
2-27
2-27
2-28
2-28
2-28
2-28
2-28

CONTENTS
2.7.2.11
2.7.2.12
2.7.2.13
2.7.3
CHAPTER 3

File-Extension Routine
File-Deletion Routines
Device Control Routine
Using the FCS Subset • •

•
•
•
•

2-28
2-28
2-29
2-29

RSX-llS VERSION 4.2 DISTRIBUTION KIT

3.1
3.2

RSX-llS VERSION 4.2 DISTRIBUTION MEDIA • • • • • • 3-1
CONTENTS OF THE RSX-llS VERSION 4.2 DISTRIBUTION

3.3

ADDITIONAL FILES REQUIRED FOR RSX-llM-PLUS AND
VAX/VMS HOST SYSTEMS • • • • • • • • • • •
• • 3-3

KIT

CHAPTER 4
4.1
4.2
4.2.1
4.2.1.1
4.2.1.2
4.2.1.3
4.2.1.4
4.2.1.5
4.2.2
4.2.2.1
4.2.2.2
4.3
4.4
4.4.1
4.4.1.1
4.4.1.2
4.4.1.3
4.4.2
4.4.3
4.4.4
CHAPTER 5
5.1
5.1.1
5.1. 2
5.1. 3
5.2
5.3

CHAPTER 6
6.1
6.1.1
6.1. 2
6.1. 3
6.2
CHAPTER 7

•

3-1

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
BUILDING THE EXECUTIVE • • •
BUILDING THE RSX-llS TASKS
. . .
System Tasks •
TKTN • • • •
Basic MCR
OTL
• • • •
SIP
• • • • •
RSDV05, RSDV52, and RSDVlH (RSD)
Other Tasks
• • • • •
.
K-series Lab Support Routines
User-Written Tasks • • • • • •
FINAL CONFIGURATION OF THE EXECUTIVE
OPERATING CONSIDERATIONS • •
• •
Libraries
. • • • • • • •
System Object Library
System Macro Library • •
FCS Subset Resident Library
Device Commons • • • . • • • •
Other Methods for Task Loading
System Loading • • • • • • • • . .

• • • • • • 4-1
. . . . . . 4-1
. . . . . • 4-2
• 4-2
• • • 4-2
• 4-3
4-4
••••
• 4-5
• • 4-6
. . . . . . • 4-6
• • • 4-6
•
• 4-7
• •
4-8
• 4-8
4-8
4-9
• • • 4-9
• 4-9
4-10
. . . . . .
4-10
.

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM
PERFORMING AN RSX-llS SYSTEM GENERATION ON AN
RSX-llM HOST SYSTEM • • • •
• • • • • • • • •
Copying Procedures • • • • • • • • • • •
• •
Invoking the System Generation Programs
••
Notes for RSX-llS Version 4.2 System Generation
on an RSX-llM Host • • • • • • • • • • • • •
SYSGEN DIALOG ON AN RSX-llM HOST SYSTEM
EXAMPLE OF AN RSX-llS SYSTEM GENERATION DIALOG ON
AN RSX-llM HOST SYSTEM • • • • • • • • • • • •

5-1
5-2
5-2
5-2
5-3
5-4

RSX-llS SYSTEM GENERATION ON AN RSX-llM-PLUS HOST
SYSTEM
PERFORMING AN RSX-llS SYSTEM GENERATION ON AN
•
RSX-llM-PLUS HOST SYSTEM • •
• • • • • •
Copying Procedures • • • • • • • • • • •
•
•
Invoking the System Generation Programs
Notes for RSX-llS Version 4.2 System Generation
on an RSX-llM-PLUS Host
• • • • • • • • •
SYSGEN DIALOG ON AN RSX-llM-PLUS HOST SYSTEM • • •
RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

6-1
6-2
6-3
6-3
6-4

CONTENTS
7.1
7 .1.1
7.1.2
7. 1. 3
7.2
7.3

APPENDIX A

PERFORMING AN RSX-llS SYSTEM GENERATION ON A
VAX/VMS HOST SYSTEM
Establishing VAX/VMS Privileges
Copying and Invoking the RSX-llS System
Generation Programs
Notes for the RSX-llS System Generation on a
VAX/VMS Host
SYSGEN DIALOG ON A VAX/VMS HOST SYSTEM
EXAMPLE OF AN RSX-llS SYSTEM GENERATION DIALOG ON
A VAX/VMS HOST SYSTEM

. 7-1
............
....
. . 7-3
....
. . 7-4
....
. . . . . . . . . . . . . . . . . . 7-5
. . . . . . 7-6
7-8
............

RSX-llS ERROR MESSAGES

EXAMPLES
4-1

Final Configuration of the Executive for a Mapped
System with Executive Commons, System-Controlled
Partitions, and Loadable Device Drivers • • • • • 4-7

2-1

Relationship of Access Rights to Main Partition
and Its Subpartitions
• • • • • • • • • • • • •

FIGURES
2-11

TABLES
1-1
2-1
2-2
3-1
4-1
4-2

RSX-llS System Generation Phases • . . . • • . • . 1-3
OTL Load Devices and Media Format
. • • 2-7
SIP Load Devices and Media Format
2-16
Contents of the RSX-llS Distribution Kits
• • 3-1
OTL Assembly Control Symbols and Load Devices
4-4
SIP Load Devices • • • . • . • • • . • • • • • • • 4-5

PREFACE

MANUAL OBJECTIVES AND INTENDED AUDIENCE
The RSX-llS System Generation and Installation Guide describes the
system generation and installation process for RSX-llS Version 4.2.
This manual is intended for system managers as well as those users who
are responsible for maintaining system software.

STRUCTURE OF THIS MANUAL
This manual is organized as follows:
•

Chapter 1
system.

describes

the

•

Chapter 2 describes the RSX-llS supplied software.

•

Chapter 3 describes the RSX-llS Version 4.2 distribution kits.

•

Chapter 4 contains information on task-building the RSX-llS
Executive as well as information on building system tasks.

•

Chapter 5 explains the RSX-llS system generation process on an
RSX-llM host system and gives an example of a typical system
generation dialog.

•

Chapter 6 explains the RSX-llS system generation process on an
RSX-llM-PLUS host system.

•

Chapter 7 explains the RSX-llS system generation process on a
VAX/VMS host system and gives an example of a typical system
generation dialog.

•

Appendix A
messages.

contains

RSX-llS

memory-resident

description

the

operating

RSX-llS

error

ASSOCIATED MANUALS
Please read the
generation:

following

manuals

before

you

perform

the

•

The RSX-llS Version 4.2 Update Notes

•

The RSX-llM System Generation and Installation Guide

The RSX-llM/RSX-llS Release Notes

vii

system

PREFACE
CONVENTIONS USED IN THIS MANUAL
The following conventions are observed in this manual:
Convention

Meaning
A symbol that indicates the CTRL key; it must
be held down while another key is pressed. For
example,
~
means hold down CTRL while
pressing z.
In examples within this manual,
this control key sequence is shown as AA. For
example,
AZ indicates the result of ~
because that is how the system echoes most
control key combinations.
A 1- to 3-character key symbol. For example,
~
indicates the RETURN key, ~
indicates
the LINE FEED key, and ~
indicates the ESC
key.
The circumflex character; when appearing with
another character, it represents the system
response to receiving a control character. For
example, when you type gRLg)
while running
some system tasks, the system echoes AZ.
(On
some terminals, the up-arrow <A> is used in
place of the circumflex.)

"print" and "type"

As these words are used in the text, the
system prints and the user types.

[

Square brackets; used to indicate optional
syntax. Brackets that are part of directory
names, however, do not indicate
optional
syntax.
In addition,
certain
Basic
MCR
directives use brackets as part of their
required syntax.

]

The prompting character that appears whenever
control is returned to the user's terminal and
the system is ready to accept input.

red ink

Color of ink used to
commands in examples.

viii

show

all

user-entered

SUMMARY OF TECHNICAL CHANGES

The RSX-llS System Generation and Installation Guide has been
to reflect the following changes to Version 4.2:
Support for the RXSO (DU:) load device for
• Loader
(OTL)

the

revised

On-Line

Task

• Support for the TKSO (MU:) cartridge tape subsystem

• Support for DIGITAL Storage Architecture (DSA) software
• Support for Network Command Terminal (NCT) software
•

New installation dialogs for RSX-llS system
performed on RSX-llM and VAX/VMS host systems

generations

CHAPTER 1
INTRODUCTION TO RSX-llS

RSX-llS Version 4.2 is the memory-resident version of the RSX-llM
operating system. RSX-llS and the tasks that run on it are created on
a host RSX-llM, RSX-llM-PLUS, or VAX/VMS operating system, before
being transported to the target system.
The following topics are described in this chapter:

1.1

•

The RSX-llS update kit

•

RSX-llS as a memory-resident operating system

•

The relationship between the host and target systems

•

The hardware and
Version 4.2 system

•

The Virtual Monitor Console Routine (VMR)

software

configurations

for

RSX-llS

THE MEMORY-RESIDENT SYSTEM

The RSX-llS memory-resident operating system is compatible internally
with RSX-llM.
It supports an I/O driver interface identical to that
supported by RSX-llM, and is a compatible subset of RSX-llM at the
user
level.
It is designed primarily to provide a run-time
environment for executing tasks.
Because RSX-llS is a memory-resident operating
support:
•

A file system

•

Nonresident tasks

•

Checkpointing

•

Disk-resident
overlaid
tasks
overlaid tasks are supported)·

•

Program development

system,

(although

does

not

memory-resident

The user interface to the RSX-llS operating system is supplied by a
compatible subset of the RSX-llM Monitor Console Routine (MCR) called
Basic MCR. Strict subset compatibility is provided by the RSX-llS
system.

1-1

INTRODUCTION TO RSX-llS
The following privileged tasks may also
system generation:
•

included

during

RSX-llS

The On-Line Task Loader (OTL), which is used to install, load,
and fix tasks in an RSX-llS system

System Image Preservation (SIP) program, which saves an
• The
image
of
an operational RSX-llS system for subsequent
bootstrapping
Task Termination Notification
(TKTN)
program,
which
• The
returns
messages about device status and abnormal task
termination
e

1.2

The set of display tasks (RSDV05, RSDV52, and RSDVlH), which
provide video terminal displays of information concerning
activity in the RSX-llS system

THE RSX-llS UPDATE KIT

If you have an RSX-llS Version 4.2 operating system, you will receive
an update distribution kit, which replaces your existing RSX-llS
distribution kit. This kit contains a fully corrected version of
RSX-llS.
Note that you must tailor this kit to your software
operating system. Your updated RSX-llS kit will be contained on one
of the following media:
•

Magnetic tape (800 or 1600 bpi)

RK06/RK07 disk

RL01/RL02 disk

•

TK50 tape cartridge

The RSX-llS Version 4.2 update distribution kit also
includes
corrections
and enhancements made to RSX-llS layered products.
However, you must perform a system generation before you can apply
corrections to the layered products.
Instructions for applying these
corrections are contained in files (.DOC file type)
located on the
distribution kit.
There are two methods for accessing the correction files,
magnetic tape and one for disks.
For magnetic tape,
following command:
>FLX ddnn:/RS=mmnn: [ggg,200]product.DOC/DO/RW/DNS:n
For disks, enter the following:
>PIP TI:=ddnn: [ggg,200]product.DOC
Both of the methods share the following elements:
ddnn:

is the device and unit of the distribution kit

ggg is the directory group number for "product"
product is the name of the layered product
n is the density of the magnetic tape

1-2

one for
type the

INTRODUCTION TO RSX-llS
To use your update distribution kit, you must run the system
generation procedure.
Please read the following manuals before you
attempt to generate your system or apply the corrections contained on
the update kit:

1.3

•

RSX-llS System Generation and Installation Guide

•

RSX-llS Version 4.2 Update Notes Revision A

RSX-llM/RSX-llS Release Notes

HOST/TARGET SYSTEMS

Program development for and system generation of an RSX-llS Version
4.2 system require a host RSX-llM (Version 4.1 or later), RSX-llM-PLUS
(Version 2.1 or later), or VAX/VMS operating system.
NOTE
To generate an RSX-llS system on a host VAX/VMS
Version 4.0
(or later)
system, VAX-11 RSX must be
installed. See the Chapter 7 of this manual for more
information.
The host system must be mapped and have at least 64K words of memory.
You may write tasks in MACR0-11 assembly language or other supported
high-level languages. Once you have assembled
(or compiled)
and
linked these tasks to the host system, you will transport the tasks to
an RSX-llS target system for program execution.
An RSX-118 operating system is generated on a host system in two
phases.
Table 1-1 describes both phases of the RSX-llS system
gene~ation program.
Table 1-1
RSX-llS System Generation Phases
Phase

Operation

Phase I

Define
the
RSX-llS
system
hardware
configuration and assemble the Executive,
device drivers, and
laboratory
device
drivers.

Phase I I

Task-build the Executive, device drivers,
and all privileged tasks; configure the
RSX-llS target system.

The complete RSX-llS operating system is constructed on the host
system under the control of command files and an RSX-llM utility
called the Virtual Monitor Console Routine (VMR).
See Section 1.5 for
more information about VMR.

1-3

INTRODUCTION TO RSX-llS
The following three methods can be used to transport tasks from a host
system to an RSX-llS operating system. You may

1.4

•

Use the VMR command FIX on the host system to fix your tasks
in the RSX-llS system image before writing the image to the
transporting medium. You may use VMR to specify partitions
and load device drivers, as well as to install and fix tasks.

•

Use the File Transfer Utility Program (FLX, described in the
RSX-llM/M-PLUS Utilties Manual) on the host system to write a
task to the transport medium. Once the transfer is complete,
you may use the On-Line Task Loader {OTL) to read the task
from the medium and load it into memory.

•

If you have DECnet support in both the host and the target
RSX-llS systems (DECnet-VAX Version 2.0 for VAX/VMS), you may
down-line task-load from the host system.

HARDWARE/SOFTWARE CONFIGURATIONS

RSX-llS is a hardware/software system capable of expanding from an 8K
word configuration to a 1920K word system with a large number of
peripherals.
It supports all PDP-11 processors, from the LSI-11 to
the PDP-11/84.
RSX-llS Version 4.2 includes support for the following
new systems and devices:
•

Systems
PDP-11/84
MicroPDP..:11/73
MicroPDP-11/83

•

Devices
FPJll processor
KDASO-Q controller
LA210 Letterprinter
LN03 laser printer
LQP03 letter-quality printer
RC25 fixed/removable disk subsystem
RXSO diskette
TK25 magnetic tape cartridge
TKSO magnetic tape cartridge

Because RSX-llS is based on and is internally compatible with RSX-llM,
RSX-llS enjoys most of the features inherent to that system. For
example, RSX-llS automatically supports all the peripheral devices
(except the console logger device)
that RSX-llM supports. This
capability also extends to other hardware features such as floating
point, parity memory, and memory management. You select the options
you want during the system generation process.
Note that the more
options you select, the more memory your system will require.

1-4

INTRODUCTION TO RSX-llS
The basic software building blocks for an RSX-llS operating system and
their approximate sizes (in decimal} are as follows:
•

A subset of the features available in
(2.5 to 4.5K words)

the

RSX-llM

Executive

•

All RSX-llM Version 4.2 I/O device drivers, except the console
logger device driver
(most drivers use an average of I.SK
words; the line printer driver needs less, the terminal driver
needs more}

•

Basic MCR (3K words)

•

On-Line Task Loader (OTL}

•

System Image Preservation (SIP) program (2K words}

•

Task Termination Notification (TKTN} program (lK words)

•

System activity display programs RSDVOS,
(6K words)

(3.5K words}

RSDV52,

and

RSDVlH

The minimum software system is a 2.SK Executive.
However, you must
enlarge this minimal Executive with other software for it to be
useful. For example, two to four I/O drivers could be added at the
expense of an additional l.SK words of memory each.
If operator
communication is required, you can include Basic MCR in a system.
Including Basic MCR, however, requires a 3K-word increase in memory.
On-line task loading in a system that is designed with 4K words for
user tasks requires a minimum 14.SK-word system. This is because
approximately 10.SK words are required for system software
(that is,
2.5K-word Executive, 3K-word MCR, l.SK-word I/O drivers, and 3.SK-word
OTL).

1.5

VIRTUAL MONITOR CONSOLE ROUTINE

The Virtual Monitor Console Routine (VMR} is an RSX-llM system program
that allows you to configure an RSX-llS system image. Using VMR, you
can define partitions, load and unload device drivers, install and fix
tasks, and establish other system parameters. You can then transfer
the entire system to an appropriate (load) medium to be bootstrapped
on the target system. VMR is documented in the RSX-llM/M-PLUS System
Management Guide.
The RSX-llM-PLUS host system uses the RSX-llM VMR system program
generate an RSX-llS system.
It is installed and executed under the
name VMM, but it issues the VMR prompt (VMR>).
(The RSX-llM-PLUS host
must also use the RSX-llM Task Builder.}
VAX/VMS also uses the RSX-llM VMR system program for generating an
RSX-llS system.
It is installed and executed under the name VMR.
It
too issues the VMR prompt (VMR>) •
(The VAX/VMS host must also use the
RSX-llM Task Builder.)

1-5

CHAPTER 2
RSX-llS SUPPLIED SOFTWARE

The RSX-llS
software:

Version

4.2

distribution

kit

contains

the

following

•

Basic MCR, which supplies the user interface

•

On-Line Task Loader (OTL), which installs,
tasks

•

System Image Preservation (SIP) program,
images for subsequent bootstrapping

•

Task Termination Notification (TKTN) program, which returns
messages about device status abnormal and task termination

•

SETTIM subroutine, which sets the system time

System display tasks
(RSDV05, RSDV52, and RSDVlH),
display system activity information on video terminals

•

RSX-llS File Control Services (FCS), a subset of
FCS that performs basic record I/O

loads,
which

and

fixes

saves

system

the

which
RSX-llM

The following sections describe these tasks. Refer to Chapter 4 for
information on how to build the tasks during the RSX-llS system
generation procedure.

2.1

BASIC MCR

Basic MCR, which supplies user interface to RSX-llS, is a subset of
the RSX-llM Monitor Console Routine
(MCR).
Basic MCR provides
commands to control and modify the execution of tasks installed in an
RSX-llS system.
If Basic MCR is to be included in the RSX-llS system,
you must configure a terminal driver and at least one terminal
interface
(DLll, DHll, DJll, or DZll) into the target system.
See
Section 4.2.1.2 for information on building the Basic MCR task.

2.1.1

Initiating Basic MCR

To use Basic MCR in an RSX-llS system, you must install and fix
MCR in the system image by running VMR on the host system.

2-1

Basic

RSX-llS SUPPLIED SOFTWARE
2.1.2

Basic MCR Commands

MCR commands are documented in the RSX-llM/M-PLUS MCR Operations
Manual.
This section contains a brief summary o"'fthe Basic MCR
commands.
Initialization Command
TIM [E]

[hrs :mi ns [:secs] ] [month/day /year]

Use this command to set the system clock.
Task Control Commands
ABO[RT] taskname
Use this command to abort the specified task.
CAN[CEL] taskname
Use this command to cancel all time-based schedule
for the specified task.

requests

RED[IRECT] new:=old:
Use this command to redirect all I/O for the old
the new device.

device

task

from

the

specified

REM[OVE] taskname
Use this command to remove the specified
system and release its partition.
RES[UME] taskname
Use this command to resume the execution
task that issued a SUSPEND directive.

RUN taskname [/keyword-I] [/keyword-2]
Use this command to cause the specified task to be executed.
RUN taskname dtime [/keyword-I] [/keyword-2]
Use this command to execute the specified task at
specified number of time units from command issuance.

the

RUN taskname sync [dtime] [/keyword-1] [/keyword-2]
Use this command to execute the specified task at the
specified number of time units following the next specified
whole time unit.
RUN taskname atime [/keyword-I] [/keyword-2]
Use this command to
specified time of day.

execute the specified task
Keywords are as follows:

/RSI - nnnnu
/UIC - [group-number,member-number]

2-2

RSX-llS SUPPLIED SOFTWARE

For the /RSI (rescheduling interval) keyword, nnnn is the
number of units to be clocked and u is the units field.
The
units field can be T (ticks), S (seconds), M (minutes), or H
(hours.) The number of units cannot exceed 24 hours in the·
specified unit.
System Maintenance Commands
ATL 1
Use this command to display the status of all active tasks.

Use this command to pass control to the Executive
Tool (XDT).

Debugging

OPE[N) memory-address [+or -n) [/keywordJ 1
Use this command to display the contents of the effective
address. On mapped systems, the effective address is formed
by decoding the specified memory address; applying the
optional additive term (+ or -); and, if the optional
keyword /PAR is specified, using the result as an offset
from the start of the partition. On unmapped systems, only
the memory address argument is permitted. After the slash,
you
may
enter
an
optional
value
to
replace
contents-of-address, followed by one of the line terminator
options.
The format of the displayed contents is as
follows:
(memory-address)

(contents-of-address)/[value)line-terminator

The following keyword may be used with mapped systems only:
/PAR

= partition name

The following line terminators may be used:
Escape or ALTMODE:
Pressing the ESC or
ALTMODE key does not open any additional
location and terminatess the OPEN command.
Pressing the ESC
(or ALTMODE) key is the
only way to exit from the MCR command OPEN.
~

Carriage return: Pressing the RETURN
opens the next sequential location.
Pressing the circumflex
some
terminals)
and
previous location.

key

key
(up-arrow on
RETURN opens the

Pressing the asterisk carriage key and
RETURN or the at-sign key and RETURN opens
the location pointed to by the final
contents of the current location.

1. An option during RSX-llS system generation.
2. Included if Executive Debugging
system generation.
2-3

Tool

(XDT)

was

selected

during

RSX-llS SUPPLIED SOFTWARE

Use this command to display
installed in the system.

2.1.3

the

status

all

tasks

Basic MCR Error Messages

You may assemble Basic MCR with long or short error messages.
Long
error messages identify which component of Basic MCR is the source of
the message, and give both a numeric error code and an ASCII
description of the error condition. Short error messages exclude the
ASCII description, thus conserving memory space.
Your distribution kit contains Basic MCR that assembles with short
err9r messages.
You can assemble Basic MCR with long error messages
by editing the file BMPRE.MAC during Phase II of the system generation
(see Section 4.2.1.2).
Basic MCR generates the following error messages. The error messages
are shown in their long form.
The XXX in the messages indicates the
three-character component name of MCR that detected the error.
Each
message is followed by a brief explanation of its possible causes.
XXX

1 - ILLEGAL FUNCTION
Explanation:

XXX

MCR could not recognize the entered command.

2 - SYNTAX ERROR
Explanation: This message generally indicates that the required
information
was
entered
incorrectly.
Retype the command
specification using the correct syntax.

XXX

3 - NO POOL SPACE
Explanation: The Executive could
request for dynamic memory.

XXX

not

currently

satisfy

MCR's

4 - INVALID KEYWORD
Explanation: The specific command processor did not recognize
keyword specified in the command line.

XXX

5 - DEVICE NOT IN SYSTEM
Explanation:
The device specified in the command was not
generated into the system.
Devices to be used in the system must
be specified during system generation.

1. An option during RSX-llS system generation.
2-4

RSX-llS SUPPLIED SOFTWARE
XXX

6 - PRIVILEGED COMMAND
Explanation: A command available only to
was issued from a nonprivileged terminal.

XXX

privileged

7 - PARTITION NOT IN SYSTEM
Explanation:
The partition name specified as an
command could not be found in the system.

XXX

terminals

8 -

argument

IO ERROR

Explanation:
In attempting to read the next command, either OPEN
detected an error or an MCR terminal-write operation failed.
XXX

9 - BYTE ADDRESS
Explanation: An odd address was specified as the argument to the
OPEN command.

XXX -- 10 - INVALID TIME PARAMETER
Explanation:

A specified time field was entered incorrectly.

XXX -- 11 - TASK NOT IN SYSTEM
Explanation:
XXX -- 12 -

The specified task was not installed in the system.

INVALID ADDRESS

Explanation:
The address specified as an argument by the OPEN
command referenced a nonexistent memory location or an address
outside the boundaries of the specified partition.
XXX -- 13 - TASK NOT ACTIVE
Explanation:

The specified task is not currently active.

XXX -- 14 - TASK BEING ABORTED
Explanation: A request for the execution of a task was made, but
the task was being aborted because of an error or an MCR command
ABORT.
XXX -- 15 - TASK NOT SUSPENDED
Explanation:
The task specified in the RESUME command
never suspended.

line

was

command

was

XXX -- 16 - TASK ACTIVE
Explanation:
active.

The task used as the argument of

2-5

the

RSX-llS SUPPLIED SOFTWARE
XXX -- 17 - CIRCULAR REDIRECT ERROR
Explanation: The attempt to redirect a device would result in
circular list of redirection.

XXX -- 18 - OLD DEVICE NOT KNOWN TO SYSTEM
in the
Explanation:
The system did not know the old device
REDIRECT command
(the device does not exist in the device
tables).
XXX -- 19 - NEW DEVICE NOT KNOWN TO SYSTEM
Explanation:
The system did not know the new device in the
REDIRECT command line
(the device does not exist in the device
tables).
XXX -- 20 - PSEUDO DEVICE REDIRECT ERROR
Explanation: An attempt was made to redirect one
to another pseudo device.

pseudo

device

XXX -- 21 - OLD DEVICE ATTACHED
Explanation:

An attempt was made to redirect an attached device.

XXX -- 22 - TI REDIRECT ERROR
Explanation: An attempt was made to redirect the
TI:.
This device cannot be redirected.
XXX -- 23 -

pseudo

INVALID UIC

Explanation: A value of O was detected for either
number or the member number.
This is invalid.
XXX -- 24 -

device

the

group

the

·limits

ILLEGAL KEYWORD VALUE

Explanation: A value entered for a keyword exceeded
for that argument.
Enter a valid value.
XXX -- 26 - LISTING DEVICE NOT AVAILABLE

Explanation: MCR attempted to display information to a device
unit that was attached and therefore unavailable for printed
output.
XXX -- 27 - DEVICE NOT REDIRECTABLE
Explanation:

The specified device cannot be redirected.

2-6

RSX-llS SUPPLIED SOFTWARE
2.2

ON-LINE TASK LOADER

The RSX-llS On-Line Task Loader (OTL) performs the same functions as
those of the MCR commands INSTALL and FIX in RSX-llM.
The task images
(including common blocks) read by OTL are produced by the RSX-llM Task
Builder and are transferred to a load-device medium by means of the
File Transfer Utility Program (FLX). OTL then performs the following
operations:
1.

Reads a task image from the load-device medium

Verifies the task image format

Checks for error conditions

Creates a Task Control Block (TCB) for the task

Places the TCB in the System Task Directory (STD)

Fixes the task in memory (thus making the task known
system)

For system-controlled partitions, OTL allocates
(Partition Control Block) for the task.

the

subpartition

PCB

OTL expects the load-device medium to be written in either DOS or
RT-11 format,
depending on the load device.
The load devices
supported by OTL, and their required formats, are listed in Table 2-1.
Table 2-1
OTL Load Devices and Media Format
OTL Load Device

Media Format

PRll paper tape reader (PR:)

DOS

RXOl flexible disk

(DX:)

RT-11

RX02 flexible disk (DY:)

RT-11

RXSO flexible diskette (DU:)

RT-11

TU60 cassette tape (CT:)

DOS

TU56 DECtape

RT-11

(OT:)

TE10,TU10,TS03 magnetic tape (MT:)

DOS

TS11,TU80,TSV05,TK25 magnetic tape (MS:)

DOS

TE16,TU16,TU45,TU77 magnetic tape (MM:)

DOS

TU58 DECtape II

RT-11

(DD:)

When transferring a task image to a
load-device medium other than
paper tape, you must first initialize the volume with FLX (if this has
not already been done}. The /RT switch must be specified
if
the
medium is to be written in RT-11 format.
You can then transfer the
task image file to the load device with a FLX transfer command.
Additionally,
include the appropriate format switch (/RT or /DO} on
the output side of the command specification and the /RS switch
(for
Files-11 format) on the input side of the command specification.
2-7

RSX-llS SUPPLIED SOFTWARE
For example, to transfer the task image file SIP.TSK from directory
[1,50] on SY:
to a cassette tape, type the following FLX commands:
FLX>CT:/ZE/DO
FLX>/DO=[l,SO]SIP.TSK/RS
If you wish to transfer the same file to an RXOl flexible
the following:

disk,

type

FLX>DX:/ZE/RT
FLX>DX:/RT=[l,SO]SIP.TSK/RS
For a full description of the
Utilities Manual.

FLX

Utility,

see

the

RSX-llM/M-PLUS

NOTE
Because FLX is sensitive to the contents of the file
type field in input file specifications, DIGITAL
strongly recommends that the standard file extension
type, .TSK, always be used. This will ensure that all
task image files are written on load-device media in
the proper format.
See Section 4.2.1.3 for information on building the OTL task.

2.2.1

Invoking OTL

Before you can use OTL in an RSX-llS system, both OTL and Basic MCR
must be installed and fixed in the system image by the Virtual Monitor
Console Routine (VMR). This is done during the system generation
process while running on a host system (see the RSX-llM/M-PLUS System
Management Guide and Chapter 1 of this manual).
You can then invoke
OTL in the RSX-llS system by entering the following Basic MCR command:
>RUN OTL
OTL then begins execution and indicates its readiness
command line by displaying the following prompt:

OTL>
To exit from OTL, press CTRL/Z.
The OTL command line has the following format:
OTL>dev: [ufd]filename.type[/INC=n.]
where:
dev:

specifies the load device, which contains the task image
file.
You must specify dev:
in the command line since
there is no default device.

[ufd]

specifies the User File Directory (UFD), which consists of
a group number and a member number in the form [g,m]. This
UFO is associated with the task image file.
The UFO need
not be specified, and is ignored for all devices except
magnetic tape (MM:, MS:, and MT:).
The default UFD is the
same as the User Identification Code (UIC) under which OTL
runs.

2-8

RSX-llS SUPPLIED SOFTWARE
filename

specifies the six-character alphanumeric file name of the
task
image file.
There is no default for filename.
It
must be specified with all devices except paper tape
readers (PR:), for which it is optional.

type

specifies the three-character alphanumeric file-type field
(preceded by a period).
The file
type need not be
specified; its default is .TSK. OTL interprets. a file name
followed only by a period as the specification for a null
file type.

/INC=n.

specifies the switch to increase the size of the task by
the specified number of octal bytes
(or decimal,
if
followed by a period).
This allows buffering space at the
end of the task.

Blank and tab characters are not allowed in an OTL command line.
Following are examples and brief explanations of OTL command lines:
OTL>DX: S.IP
Explanation: This command creates the Task Control Block
(TCB) for the SIP task, and reads the task image from the RXOl
disk and loads it into memory.
OTL>MM: [l,54]TKN
Explanation: This command creates the TCB for the TKN task,
and reads the task image from the magnetic tape and loads it
into memory.
TKN is then renamed to TKTN.
OTL>PR:
Explanation: This command creates the TCB for the task on the
paper tape and loads it into memory.
OTL>CT:TEST.TSK
Explanation:
This command
creates
the
TCB
for
the
user-written task TEST.TSK, and reads it from the cassette
tape and loads it into memory.

2.2.2

OTL Operation

When OTL accepts a command line, it first parses the line for proper
syntax.
If the syntax is correct, OTL determines whether the
designated device was generated into the system as a load device.
If
it was, then the device is attached (except PR:
devices) and a search
operation is performed to locate the designated file.
When OTL finds the file, it reads the first block of the file to
determine whether the file
is a valid task image.
If it is, OTL
proceeds to install and fix the task or common block in the following
manner:
1.

Allocates and initializes a Task Control Block (TCB)
image is a task

Verifies that the designated partition is in the
is available

2-9

the

system

and

RSX-llS SUPPLIED SOFTWARE
3.

Finds space in a system-controlled partition
(mapped system
only)
and allocates a subpartition Partition Control Block
(PCB)

Reads and initializes the task's header

Loads the overlay
overlaid tasks)

Allocates and initializes a copy of the header
Executive's pool space (if the system is mapped)

Loads the task or common block into memory

Inserts the TCB into the System Task Directory (STD)
image is a task

segments

into

memory

(memory-resident
in

the

OTL simultanenously performs additional validity checks.

2.2.3

Programming Hints

Except for the /INC keyword, OTL does not accept keyword input;
consequently, you must specify all other attributes and options for a
task when it is built.
(The task must be built before OTL can load
it.) Be certain to specify the partition and task name during the
option input.
If a task name is not specified in the task image, OTL
defaults the task name to the file name that was specified in the
command line. This default also occurs with,paper tape, for which no
file name is required.
Tasks installed by OTL cannot have disk overlays and cannot be
checkpointed.
An attempt to install a disk-overlaid task results in
an error message and a failure to install the task.
OTL ignores the
checkpoint
attribute
and installs all checkpointable tasks as
noncheckpointable. Tasks with memory-resident overlays, however, can
be installed with OTL.
(See the RSX-llM/M-PLUS and Micro/RSX Task
Builder Manual for more information on the different kinds of tasks:-yOTL also supports tasks with memory-resident overlays that link to
commons.
You link the task with the common when the task is built.
Additionally, OTL uses various methods to load tasks and common blocks
into memory.
These methods are described in the following section.

2.2.3.1 Using OTL to Load Tasks and Common Blocks Into Memory - When
using task-controlled partitions, OTL fixes each task or common block
that it installs in memory and marks the partition as occupied.
OTL
returns an error message in the event of one of the following errors:
•

An attempt is made to install
partition or subpartition.

task

•

An attempt is made to install a task in a
main partition is occupied.

•

occupied

main

subpartition

whose

An attempt is made to install a task in a main partition
has an occupied subpartition.

that

(When a task is removed by means of Basic MCR, the task's partition is
no longer occupied.)

2-10

RSX-llS SUPPLIED SOFTWARE
With system-controlled partitions, OTL searches
for
sufficient
contiguous memory into which it can load the task. OTL dynamically
creates a subpartition for the memory it has allocated for the task.
It then marks the subpartition as occupied and the subpartition PCB is
linked into the PCB list.
When loading common blocks, OTL ignores the partition state.
This
permits you to overwrite previously loaded common blocks when desired.
Furthermore, common main partitions and subpartitions can be occupied
simultaneously.
This feature allows you to install tasks with
different access privileges to different parts of a common main
par ti ti on.
For example, in Figure 2-1, the main partition (COMM) is consists of
three subpartitions (Cl, C2, C3). The main partition and each of its
subpartitions have associated access rights. You may install a task
with access to either the main partition, or to one or more
subpartitions. A task installed with access to COMM has read-write
access rights
(indicated in the command line by /RW) to the entire
main partition. A task installed with access to Cl has read only
access rights
(indicated in the command line by /RO)
to that
subpartition only.
main
partition
COMM,
with RW
access
rights

} subparti ti on Cl with RO access rights
} subparti ti on C2 with RW access rights
} subparti ti on C3 with RO access rights
ZK-4181-85

Figure 2-1 Relationship of Access Rights fo Main Partition and
Its Subpartitions
When writing task image files to cassette tape by means of the File
Transfer Utility Program (FLX), you must use a block size (specified
with the /BS switch) that evenly divides into 512(10) bytes.
The
default
block
size of 128(10) bytes is compatible with this
requirement. Attempting to install a task image from cassette tape
with a block size that does not evenly divide into 512(10) bytes
results in an error message and terminates the operation.
For more information on building and loading tasks, refer to
RSX-llM/M-PLUS
and
Micro/RSX
Task
Builder
Manual
and
RSX-llM/M-PLUS and Micro/RSX Execut~Reference Manual.

2.2.4

the
the

OTL Error Messages

When OTL detects an error condition, it takes the following steps:
1.

Aborts its current operation

Displays an error message at the terminal from which
activated

Prompts for another command line

was

If the detected error condition is NO POOL SPACE, OTL may immediately
exit from the program because printing the error message also requires
pool space.

2-11

RSX-llS SUPPLIED SOFTWARE
You may assemble OTL using long or short error messages.
Long error
messages identify OTL as the source of the message and give both a
numeric error code and an ASCII description of the error condition.
Short error messages exclude the ASCII description, thus conserving
memory space.
Your distribution kit contains the version of OTL that
assembles with short error messages. For information on assembling
OTL with long error messages, see Section 4.2.1.3.
OTL generates the following error messages, shown here in their long
form. Each message is followed by a brief explanation of its possible
causes.
OTL -- 2 - SYNTAX ERROR
Explanation: A command was entered incorrectly.
command line using the correct syntax.

Retype

the

OTL -- 3 - NO POOL SPACE
Explanation: When it issued an I/O request or attempted to
allocate pool space, OTL detected insufficient pool space in the
Executive. When this error condition occurs, OTL may exit
without printing this error message.
OTL -- 5 - DEVICE NOT IN SYSTEM
Explanation: The device specified in the command line was not
generated into the system. Devices to be used in the system must
be specified during system generation.
OTL -- 7 - PARTITION NOT IN SYSTEM
Explanation: The partition specified in the task image was not
defined in the system. Alternatively, the specified partition
was defined, but some or all of its memory was not present in the
current configuration.
OTL -- 8 - IO ERROR
Explanation: This message is returned in the event of one of the
following errors:
In attempting to read the next command, the MCR command OPEN
• operation
detected an error.

• An MCR terminal-write operation failed.
hardware error was encountered as the result
• Arequest
issued to the load device or terminal.
•

The specified device was generated into the system, but it was
not present in the hardware configuration.

OTL -- 40 - BASE ADDRESS MUST BE ON A 4K BOUNDARY
Explanation: A task image (not a common block)
in
system specified a base address not on a 4K boundary.

2-12

mapped

RSX-llS SUPPLIED SOFTWARE
OTL -- 41 - ILLEGAL lST APR
Explanation: This message is returned in the event of one of the
following errors:
•

The image of a nonprivileged task in a mapped system specified
a nonzero first Active Page Register (APR).

•

The image of a privileged task in a mapped system specified
first APR that was not in the range APR4 through APR6.

OTL -- 42 - NOT ENOUGH APRS FOR TASK IMAGE
Explanation: There were not enough APRs to map the task as well
as the resident library references that the task image may have
had in a mapped system.
OTL -- 43 - FORMATTED BINARY CHECKSUM ERROR
Explanation: A checksum error was encountered
task image from paper tape.

while

reading

OTL -- 44 - FORMATTED BINARY FORMAT ERROR
Explanation: An invalid binary format was encountered in a
image being read from paper tape.

task

OTL -- 45 - UNEXPECTED END OF FILE ENCOUNTERED
Explanation: An end-of-file was encountered
task image was read.

before

the

entire

OTL -- 46 - SPECIFIED PARTITION TOO SMALL
Explanation: The partition specified in the task image
smaller than the load size of the task or common block.

was

OTL -- 47 - SPECIFIED PARTITION FOR COMMON BLOCK
Explanation:
block.

An attempt was made to install a task into a common

OTL -- 48 - TASK IS OVERLAID
Explanation: This message is returned in the event of one of the
following errors:
•

An attempt was made to install an overlaid task in a system
without memory management directives.

•

An attempt was made to install a
overlays.

task

with

disk-resident

OTL -- 49 - TASK NAME ALREADY IN USE
Explanation: An attempt was made to install a task with the same
name as that of a task already installed.

2-13

RSX-llS SUPPLIED SOFTWARE
OTL -- 50 - TASK NAME NOT DEFINED

Explanation: An attempt was made to install a
task from paper
tape without an optional file name specified. Additionally, the
task image did not contain a task name. Retype the command line,
specifying a file name that will become the task name by default.
OTL -- 51 - TASK AND PARTITION BASES MISMATCH

Explanation:
An attempt was
unmapped system whose base
specified partition.

made to install a task
in an
address did not match that of its

OTL -- 52 - INVALID COMMON BLOCK

Explanation: A task contained a library reference
block that was not in the system.

common

OTL -- 53 - PARTITION TOO LARGE FOR PRIVILEGED TASK

Explanation:
An attempt was made to install a privileged task in
a partition whose size was greater than 12K words.
(This message
occurs only on unmapped systems.)
OTL -- 54 - FILE NOT FOUND

Explanation:

The specified file was not found.

OTL -- 55 - COMMON BLOCK IS TASK PARTITION

Explanation: A task image contained a library reference that had
the same name as a task partition.
OTL -- 56 - COMMON BLOCK NOT LOADED

Explanation: A task image contained a
common partition that was not loaded.

library

reference

OTL -- 57 - LENGTH MISMATCH COMMON BLOCK

Explanation: A task image contained a
library reference to a
common block that was smaller than the size specified when the
task was built.
OTL -- 58 - BASE MISMATCH COMMON BLOCK

Explanation: A task image contained a
library reference to a
common block whose base address was different from the one
specified when the task was built.
OTL -- 59 - COMMON BLOCK PARAMETER MISMATCH

Explanation: This message is returned in the event of one of the
following errors:
o

A task image contained a library reference to a common block
that did not contain position-independent code.
It was,
however, expected to contain this code.
2-14

RSX-llS SUPPLIED SOFTWARE
common block
It was not,

•

A task image contained a library reference to a
that did contain position-independent code.
however, expected to contain this code.

•

An attempt was made to load a common block whose task name did
not match the partition name.

OTL -- 60 - PARTITION NOT COMMON
Explanation: An attempt was made to install a common block in
task partition.

OTL -- 61 - ILLEGAL DEVICE
Explanation: A task image contained a logical unit number
assignment to a device not in the system.

(LUN)

OTL -- 62 - FILE NOT TASK IMAGE
Explanation:
Preliminary checks indicated that either
the
specified file was not a task image or the file was corrupted.
OTL -- 63 - PARTITION IS BUSY
Explanation: This message is returned in the event of one of the
following errors:

OTL

•

An attempt was made to fix a
occupied subpartition.

task

main

partition

•

An attempt was made to fix a task in a main partition that had
an occupied subpartition.

•

An attempt was made to fix a task in a subpartition
an occupied main partition.

•

An attempt was made to load a task into a system-controlled
partition, but the partition did not have enough contiguous
memory.

that

had

65 - INVALID BLOCK SIZE ON LOAD DEVICE
Explanation: The block size of a task image file
tape) could not be evenly divided into 512(10).

(on

cassette

OTL -- 66 - FILE NAME REQUIRED
Explanation: No file name was specified with a device.
name is required.

file

(or

was

Active

Page

OTL -- 67 - INVALID LOAD DEVICE
Explanation: The version of OTL in use did not support
not assembled to support) the specified device.
OTL -- 68 - TOO MANY WINDOW BLOCKS
Explanation: The task
Registers (APRs).

required

2-15

than

eight

RSX-llS SUPPLIED SOFTWARE
OTL -- 69 - TASK BUILT FOR WRONG SYSTEM
Explanation: OTL determined that the task required one
following features that the system does not support:

the

•

The task was built for an RSX-llM-PLUS system.

•

The wrong version of the Task Builder was used to build the
task.
(For memory-resident overlaid tasks, the version must
be RSX-llM Version 3.2 or later.)

OTL -- 70 - ILLEGAL USE OF INCREMENT
Explanation: This message is returned in the event of one of the
following errors:

2.3

•

The specified increment caused the task to exceed 32K.

•

An attempt was made to use an increment to install and fix an
overlaid task.
Overlaid tasks cannot be loaded with an
increment.

SYSTEM IMAGE PRESERVATION PROGRAM

The RSX-llS System Image Preservation
(SIP)
program saves RSX-llS
system images on a load device medium and writes to the bootstrap
block. The format of these system images on all media, except paper
tape, is as follows:
•

The bootstrap block

•

The label block

•

The system image

For paper tape, the format is a system image in absolute loader
format; there is no bootstrap or label block. See Section 4.2.1.4 for
information on building the SIP task.
Table 2-2 lists the load device media that SIP
their required format.

supports

Table 2-2
SIP Load Devices and Media Format
SIP Load Devices

Media Format

PPll paper tape reader (PP:)

DOS

RXOl flexible disk (DX:)

RT-11

RX02 flexible disk (DY:)

RT-11

TU60 cassette tape (CT:)

DOS

TU56 DECtape (DT:)

RT-11

TE10,TU10,TS03 magnetic tape (MT:)

DOS

TE16,TU16,TU45,TU77 magnetic tape (MM:)

DOS

2-16

well

RSX-llS SUPPLIED SOFTWARE
2.3.1

Invoking SIP

Before you can use SIP in an RSX-llS system, both SIP and Basic MCR
must be installed and fixed in the system image. SIP may be installed
and fixed in the system by any of the following:
•

Virtual Monitor Console Routine (VMR)

•

OTL running on the RSX-llS system

•

Down-line loading with DECnet

Basic MCR is installed by using VMR on the host system.
typing the following Basic MCR command:

Invoke SIP by

>RUN SIP
SIP then begins execution and indicates its readiness
command line by displaying the following prompt:

SIP>
To exit from SIP, press

mRL/z) •

The SIP command line has the following format:
SIP>dev:label
where:
dev:

specifies the load device designated to receive the system
image.
You must specify dev:
in the command line since there
is no default device.

label

specifies the label, which consists of 1 to 12 alphanumeric
characters, to be associated with the system image.
The label
must be specified for all devices except paper tape, for which
it is ignored.

Blank and tab characters are not allowed in a SIP command line.
Following are examples and brief explanations of SIP command lines:
SIP>MM:RSXllS
Explanation: This command saves the RSX-llS system image on a
magnetic tape.
SIP>PP:
Explanation: This commmand saves the RSX-llS system image
a paper tape.

SIP>DTl:llSMAPPEDSYS
Explanation: This command saves the RSX-llS system image on a
DECtape.
Another file name is used to distinguish between
different versions of the system image on the DECtape.

2-17

RSX-llS SUPPLIED SOFTWARE
2.3.2

SIP Operation

When SIP accepts a command line and no
encountered, it performs the following steps:
syntax

error

conditions

and

creates

It parses the line for proper
block.

It determines whether the designated device
into the current system as a load device.

It verifies that the system contains no outstanding I/O.

It attaches the device,
rewinds it
(if cassette tape or
magnetic tape), and outputs the bootstrap and label blocks
(if not paper tape).

It outputs the system image at processor priority level PR7.
If the output device is the paper tape punch, the system
image is output in absolute loader format.

It returns the processor priority level to
for another command line.

PRO

was

and

are
label

generated

prompts

The subsequently produced system image, with the exception of paper
tape, may be bootstrapped directly with an appropriate hardware
bootstrap. To bootstrap a paper tape image, the absolute loader must
first be bootstrapped by means of the paper tape bootstrap.
You can
then bootstrap the paper tape produced by SIP with the absolute
loader.

2.3.3

Hints on Using SIP

In general, any system saved by SIP on a device other than paper tape
be bootstrapped on another system with a different amount of
memory. When you are transporting the saved system to a smaller
system, however, the top of memory must not be lower than the physical
top of SIP's task image in the saved system.
ca~

To enhance system transportability further,
a system saved on a
TMll/TMAll/TMBll 9-track magnetic tape drive in 800 bpi mode can be
bootstrapped from a TU16 magnetic tape drive, or conversely.
The maximum memory size that can be saved is 124K words. SIP imposes
maximum sizes on saved images in mapped systems for certain devices.
If a mapped system is saved with a memory size greater than the
maximum size imposed by SIP for the specified device, only the amount
of memory equal to the maximum size and starting at physical location
0 is saved. A diagnostic error message· is not issued. SIP imposes a
maximum size on saved images for the following devices:
Device

Maximum Size

PCll/PRll paper tape punch (PP:)

28K words

RXll/RXOl flexible disk

(DX:)

122K words

RX211/RX02 flexible disk

(DY:)

122K words for single-density
disk

TA11/TU60 cassette tape (CT:)

2-18

28K words

RSX-llS SUPPLIED SOFTWARE
SIP also determines the amount of memory to be saved by examining the
location, $SYSIZ, in the Executive module SYSCM.
This location is set
to the size of physical memory (in 32K-word blocks) when the system is
bootstrapped.
You can reduce the size of the saved system by placing
the desired value in this location when the system is not being used.
However, you must restore the 6riginal value after the system is
saved.
Certain restrictions must be enforced when you are not saving all
the
physical memory.
SIP must be fixed entirely in the saved area or the
system will not rebootstrap properly.
Tasks that are fixed in memory
outside
of the saved area cannot be run when the system is
rebootstrapped.
DIGITAL recommends that you remove all such tasks
before saving the system.
When a system is saved on paper tape, the last 300(8) bytes of
the
system image are not output; this is done to accommodate the absolute
loader. Unmapped systems and mapped systems smaller than 28K words of
memory that are saved on paper tape must be bootstrapped on a
configuration having at least the same amount of memory.
Mapped
systems larger
than 28K words that are saved on paper tape (of which
only the first 28K words of the system image is saved)
must be
bootstrapped on a configuration having at least 28K words of memory.
These restrictions are necessary to prevent the absolute loader from
overwriting itself.
When you are bootstrapping from paper tape, the absolute loader halts
if it encounters a checksum error.
If the paper tape is backed up to
a previous interblock gap and the CONTINUE switch on the processor
console panel
is pressed, the absolute loader will rettempt the read
operation.
Interblock gaps appear on the tape as a group of at least
4 nulls,
followed by a 1, followed by another null.
The tape should
be positioned
in the group of nulls.
If the absolute loader
encounters a hardware error on the paper tape reader, you must restart
the loader.

2.3.4

SIP Error Messages

When the System Image Preservation
(SIP)
condition, it takes the following steps:
•

Aborts the current operation

•

Displays an error message

•

Prompts for another command line

program

detects

error

The only exception to this procedure arises when the Executive has
insufficient pool space.
When this happpens, SIP immediately exits
from the task because it has no additional pool space with which to
display
an
error
message.
When an I/O error occurs while
bootstrapping a system saved by SIP from a device other than paper
tape, a
"BR
"
(branch to the same location) instruction, or its
equivalent, is issued.
This instruction causes the central processing
unit
(CPU)
to enter a closed loop and, subsequently, all I/O is
stopped.
You may assemble SIP with long or short error messages.
Long error
messages identify SIP as the source of the message and give both a
numeric error code and a brief ASCII description of the error
condition. Short error messages exclude the ASCII description, thus

2-19

RSX-llS SUPPLIED SOFTWARE
conserving memory space. Your distribution kit contains the version
of SIP that assembles with short error messages. Section 4.2.1.4
describes the steps necessary to assemble SIP with long error
messages.
SIP generates the following error messages, shown here in their long
form. ~ach message is followed by a brief explanation of its possible
causes.
SIP -- 2 - SYNTAX ERROR
Explanation: A command was entered incorrectly.
command line using the correct syntax.

Retype

the

SIP -- 5 - DEVICE NOT IN SYSTEM
Explanation: The device specified in the command line was not
generated into the system.
Devices to be used in the system must
be specified during system generation.
SIP -- 8 - IO ERROR
Explanation: This message is returned in the event of one of the
following errors:
•

In attempting to read the next command, the MCR
detected an error

command

OPEN

•

An MCR terminal-write operation failed

•

A hardware error was encountered as the result
request issued to the load device or terminal

I/O

•

The specified device was generated into the system, but it was
not present in the hardware configuration

SIP -- 66 - LABEL REQUIRED
Explanation:
required.

No label was specified with a device.

label

SIP -- 67 - INVALID LOAD DEVICE
Explanation: The version of SIP in use did not support
(or was
not assembled to support} the specified device as a load device.
SIP -- 68 - IO OUTSTANDING
Explanation: An attempt was made to save the system
when one or more tasks had outstanding I/O •

2.4

time

TASK TERMINATION NOTIFICATION PROGRAM

The Task Termination Notification (TKTN} program outputs abnormal task
termination and device status information.

2-20

RSX-llS SUPPLIED SOFTWARE
If a task aborts, TKTN prints the notification and appropriate error
message on the task's initiating terminal. TKTN also displays the
contents of the task's registers when the task aborted.
If a task
aborts with I/O requests outstanding, the error message will include
the phrase "and with pending I/O requests."
All task abort messages are printed or displayed at the initiating
terminal.
All other TKTN messages are printed on the console
terminal. The messages printed on the console terminal generally
identify error and status conditions relating to the system.
See Section 4.2.1.1 for information on building the TKTN program.

2.4.1

Invoking TKTN

TKTN is activated by the Executive when a task terminates abnormally
or when a device driver wants to report unusual status information.
You must use VMR to install and fix TKTN into the system during the
RSX-llS system generation.

2.4.2

TKTN Error Messages

TKTN generates the following error messages in an RSX-llS system.
In
this section, each error message is followed by a brief description of
the probable cause.
Error messages that are related to task termination will include a
display of the contents of the task's registers at the time of
termination.
These are represented here by
the
"(registers)"
notation.
Error messages that are related to devices are preceded by the
mnemonic, represented here by "ddnn:".

device

Task-related error messages:
TASK

"taskname"
(registers)

TERMINATED -- ODD

ADDRESS

OTHER

TRAP

FOUR

Explanation: This message is returned in the event of one of the
following errors:
•

The task executed a word instruction with an odd address
no SST routine was specified to process the trap.

task
• The
unmapped

but

referenced a nonexistent memory location in an
system but no SST routine was specified to process

the trap.
TASK "taskname" TERMINATED -- MEMORY PROTECT VIOLATION (registers)
Explanation: The task encountered a memory protect violation but
no SST routine was specified to process the trap.

2-21

RSX-llS SUPPLIED SOFTWARE
TASK "taskname" TERMINATED -- T-BIT TRAP OR BPT EXECUTION (registers)
Explanation: The task has either set the trace-bit
(T-bit)
in
the Processor Status Word
(PSW) or executed a Breakpoint Trap
instruction, but no SST routine was specified to process the
trap.
TASK "taskname" TERMINATED -- IOT EXECUTION (registers)
Explanation:
The task executed an I/O Trap (IOT) instruction but
no SST routine was specified to process the trap.
TASK "taskname" TERMINATED -- RESERVED INST EXECUTION (registers)
Explanation: The task executed an illegal instruction but no SST
routine was specified to process the trap.
TASK "taskname" TERMINATED -- NON-RSX EMT EXECUTION (registers)
(EMT)
Explanation:
The task executed
an
Emulator
Trap
instruction that had an argument other than 377(8)
but no
synchronous system trap (SST) routine was specified to process
the trap.
TASK "taskname" TERMINATED -- 11/40 F.P. EXCEPTION (registers)
Explanation:
The task encountered a floating point exception
while executing on a PDP-11/40 but no SST routine was specified
to process the trap.
TASK "taskname" TERMINATED -- TRAP EXECUTION (registers)
Explanation:
The task executed a TRAP instruction
routine was specified to process the trap.

but

SST

cannot

TASK "taskname" TERMINATED -- SST ABORT. BAD STACK (registers)
Explanation: This message is returned when an SST
effected because of one of the following conditions:

task's~stack.

•

The SST parameters could not be pushed onto the

•

A stack overflow was detected in an unmapped system,
indicated by a nonzero value in the header guard word.

TASK "taskname" TERMINATED -- AST ABORT. BAD STACK (registers)
Explanation: An AST could not be effected because
parameters could not be pushed onto the task's stack.

the

AST

TASK "taskname" TERMINATED -- ABORTED VIA DIRECTIVE OR CLI
Explanation:
Either an Executive directive or a CLI
issued by another taek caused the task to be aborted.

2-22

command

RSX-llS SUPPLIED SOFTWARE
TASK EXIT WITH OUTSTANDING I/O (registers)
Explanation:
(This is only a warning message.)
terminated before all its I/O was completed.

The

task

PARITY ERROR (registers)
Explanation: A parity error occurred during task execution. The
task is fixed in memory so that the memory cannot be reused for
another task.
Device-related messages:

***

ddnn:

NOT READY

Explanation:

***

ddnn:

The specified device was not ready.

SELECT ERROR

Explanation: The selected device was not ready or more than
drive had the same unit number.

***

ddnn:

one

DISMOUNT COMPLETE

Explanation: This is an informational message.
It indicates
that
the
device requested for dismount is now logically
disconnected from the system (that is, all files are deaccessed
and the Volume Control Block (VCB) is deallocated).
MICRO CODE LOADER NOT INSTALLED
Explanation: This message is associated with KMC-controlled line
printers.
A system that includes the KMCll driver (LKDRV) has
been generated but the LPINIT task has not been installed.

2.5

THE SETTIM CALLABLE SUBROUTINE

SETTIM is a subroutine which can be called with FORTRAN to set the
system's internal time.
It is supplied to allow a running program to
set the time in a configuration that does not include a console
terminal and/or Basic MCR.
The module is included in a user task by
linking with the file SETTIM.OBJ, which resides
in UFO
[1,20]
for
unmapped systems or UFO [1,24] for mapped systems.
The format of the FORTRAN call is as follows:
CALL SETTIM (itime)
The variable itime is an eight-word integer array containing the time.
The contents of the array are used in the following order:
Year
Month
Day
Hour
Minute
Second
Tick of second
Ticks per second

(since 1900)
(1-12)
(1-31)
(0-23)
(0-59)
(0-59)
(depends on clock frequency)
(depends on clock frequency)
2-23

RSX-llS SUPPLIED SOFTWARE
Complete error checking occurs to ensure that the specified date and
time are legal, but no errors are returned to the calling program.
If
an error is detected, the date or time is not changed.
Calls made
without an array specified simply return.
SETTIM may also be called with a six-word array
entries for tick of second and ticks per second.
default to the values previously set for them.

by omitting the
These two entries

To generate SETTIM, you need the SET SYSTEM TIME
($STIM) directive.
This directive is one of the Executive options you can select during
Phase I of the RSX-llS system generation procedure.

2.6

SYSTEM ACTIVITY DISPLAY PROGRAMS

RSDVOS, RSDV52, and RSDVlH (referred to in this section as RSD)
are
privileged tasks that display information concerning task activity in
an RSX-llS system. You can invoke and continually run these tasks on
a VTOS-B video terminal, a VT52 video terminal, and a VTlOO video
terminal, respectively. The display format is similar to that of the
RMDEMO display, which is described in the RSX-llM/M-PLUS System
Management Guide. RSD running on RSX-llS requires approximately 6K
words.
RSD includes the following display features:
•

The current date and time.

•

The currently active task.

•

All tasks, loaded drivers, and common blocks currently in
memory,
displayed
in a graphic fashion to show their
individual memory requirements and locations relative to other
tasks.

•

The number of active tasks currently in memory and
amount of memory occupied by each task.

•

The current amount of available system dynamic memory
{pool).
This includes the largest available block and the number of
fragments, and the worst case of pool space since bringing up
RSD (not displayed on a VTOS-B).

•

A graphic display of partition information.

the

total

RSD scales the display to the memory size of the computer on which it
is executed. Graphically, total memory is represented in multiples of
32 words. For this reason, the display may not always represent the
exact total memory for the associated computer.
RSD is a useful task designed to allow either a computer operator or a
user to view the current state of the operating system.
The
information is presented in a graphic, easily understandable form.
Task locations and sizes displayed by RSD should be considered
approximations. RSD is primarily designed to provide a visual display
and system debugging tool.
It does not accurately measure task size
and location.

2-24

RSX-llS SUPPLIED SOFTWARE
A specific instance in which RSD can help you is in locating certain
system lockout problems or bugs in application and/or system-level
software. You can detect and more easily reproduce bugs and other
situations that cause pool exhaustion (resulting in unexplained
suspended activity on a system). See Section 4.2.1.5 for information
on building the RSD tasks.

2.7

FILE CONTROL SERVICES

RSX-llS does not have its own file system, but it does support a
subset of the RSX-llM File Control Services (FCS) that performs basic
record I/O. The RSX-llS FCS subset does not support the following:
•

File-structured devices (Files-11 disk and ANSI magnetic tape)

•

Block I/O operations

•

Random access record I/O

•

Sequential records

All the RSX-llM FCS calls are present in the RSX-llS FCS subset, even
though they are not supported in RSX-llS.
If a call is made to an
unsupported FCS routine, the result is an immediate return to the
caller or an error return.
The level of support in each call in
RSX-llS is described in Section 2.7.1.
In general, the FCS subset handles I/O operations in the same way that
the RSX-llM FCS handles I/O for record I/O operations.
Minor
exceptions to this are noted in Section 2.7.1. Note that a MACR0-11
programmer must maintain the data structures (such as File Descriptor
Block and Filename block) as described in the RSX-llM/M-PLUS and
Micro/RSX I/O Operations Reference Manual.
Section 2.7.1 describes the macro calls used to process files,
and
Section 2.7.2 describes the file control routines. These calls and
routines are fully documented in the RSX-llM/M-PLUS and Micro/RSX I/0
Operations Reference Manual.

2.7.1

File-Processing Macro Calls

The file-processing macro calls are used to manipulate files.
These
calls, described in the following sections, allow you to open files
for read and write operations.

2.7.1.1 OPEN$x - Generalized OPEN Macro Call - Although RSX-llS does
not support a file system, the concept of file I/O is still
applicable. Before you can transfer any data, you must open a file.
This
procedure
has
been
simplified
by
the
exclusion
of
directory-structured devices.
In general, the OPEN$x macro calls
perform as they do for record devices under standard FCS.

2-25

RSX-llS SUPPLIED SOFTWARE
When FCS opens a file, it takes several steps to identify a file name.
The FCS subset has reduced this procedure to a single step.
Of the
three fields in the file descriptor
(device, directory,
and
file
name),
only the device string is significant, and it is parsed as
usual.
The directory-string field
is ignored;
the Master File
Directory
(MFD)
is always assumed.
The file name string is always
ignored. As a result, all error status returns regarding the latter
two fields are eliminated.
Because RSX-llS does not support a directory structure,
need
to search the MFD and User File Directory
identifications are always forced to be 1.

there is no
(UFD) •
File

2.7.1.2 OPNS$x - Open File for Shared Access - File access protection
is enforced by the file system primitives. Because RSX-llS does not
support a file system, all files are implicitly opened for shared
access.

2.7.1.3 OPNT$W/OPNT$D - Create and Open Temporary Files - Creating
temporary files
is similar to creating a file that does not have a
directory entry associated with it.
This applies for all file
operations in this subset FCS.

2.7.1.4 OFID$/OFNB$ - Open by File Identificaton/Open by Filename
Block - All file
identifications are forced to be 1. Therefore, no
specific test is performed in OFID$ for a file identification.

2.7.1.5 OPEN$ - Generalized Open for Specifying File Access - All
comments in Sections 2.7.1.1 through 2.7.1.4 apply to th1s general
OPEN$ call.

2.7.1.6 CLOSE$ - Close Specified File - Because RSX-llS does not
support record blocking,
there are no partially filled buffers and
consequently no need to empty them. Furthermore,
there is no file
deaccess because there is no file system. As a result, no FCS error
conditions are possible.

2.7.1.7 GET$x - Read Logical Record - The GET$ and GET$S macro calls
translate directly into requests to read from the device; there is no
record unblocking. However, the virtual block number field (F.VBN) is
maintained.
Therefore, you may treat a block device as a record
device having a direct translation of virtual block into logical
block.
The GET$R macro call is returned with an error code of IE.ISQ
(illegal sequential operation).

2.7.1.8 PUT$x - Write Logical Record - The PUT$ and PUT$S macro calls
translate directly into requests to write to the device; there is no
record blocking. As with the input operations,
the virtual block
number is maintained in the FDB, allowing record I/O to block devices.
The PUT$R macro call is returned with an error code of IE.ISQ (illegal
sequential operation) •

2-26

RSX-llS SUPPLIED SOFTWARE
2.7.1.9 READ$, WRITE$, WAIT$ - Virtual Block I/0 - These calls are
not applicable to record devices and therefore are not supported.
Attempts to use these calls and to open a file for read/write I/O
(record access parameter is FD.RWM) result in the return of an error
code IE.ILL (illegal operation).

2.7.1.10 DELET$ - Delete Specified File - Because RSX-llS does not
maintain a file structure, the delete-file function is minimal. A
parse of the device field is performed and the file is closed if it is
currently open.

2.7.2

File Control Routines

The file control routines allow you to make changes to files.
However, RSX-llS does not support all these routines. Sections
2.7.2.1 through 2.7.2.13 describe each routine and,
if applicable,
explain why it cannot be used on RSX-llS.

2.7.2.1 Default Directory String Routines - RSX-llS does not support
a directory structure. Calls to .RDFDR to read the default directory
string descriptor always return a zero in Rl, the size of the string
in bytes. Calls to .WDFDR to write the string descriptor result in an
immediate return.

2.7.2.2 Default File Protection Word Routines - File protection is a
function of the file system, which is not present in RSX-llS.
Therefore, calls to .RDFFP to read the default-file-protection word
always return a zero in Rl.
Calls to .WDFFP to write a new
default-file-protection word result in an immediate return.

2.7.2.3 File Owner Word Routines - File
owner
information
is
established at file creation and is relevant only to the file system.
Thus, calls to .RFOWN to read the file-owner word always return a zero
in Rl.
Calls to .WFOWN to write a new file-owner word result in an
immediate return.

2.7.2.4 ASCII/Binary UIC Conversion Routines - The requirement to
maintain and/or establish User Identification Codes (UICs) disappears
with the absence of a file system. Calls to .ASCPP to convert an
ASCII UIC string to binary always return a zero in the word location
whose address is contained in R3. Calls to .PPASC to convert a binary
UIC representation to ASCII always return a null value to the byte
referenced by R2. Furthermore, the contents of R2 are increased by a
value of 1.

2.7.2.S Filename Block Routines - Directory and file name strings are
ignored.
As a result, a call to .PARSE is reduced to an examination
of the device string, an assignment of a logical unit number (LUN)
to
that
device,
and
the
establishment
of a default directory
identification of [-1,-1) (the MFD). Calls to .PRSDV (parse a device
string) and to .ASLUN (assign a logical unit number), however, remain
unaffected.
2-27

RSX-llS SUPPLIED SOFTWARE
2.7.2.6 Directory Entry Routines - File directories are not supported
in the FCS subset.
Therefore, calls to .ENTER (insert directory
entry), .FIND (locate directory entry), and .REMOV
(delete directory
entry)
are reduced to a LUN assignment and returned with a file
identification of 1.

2.7.2.7 Directory Information Routines - Lack of directory structure
support also reduces the capability of these routines. Both .GTDID
(insert default directory information in filename block)
and
.GTDIR
(insert directory information in filename block) calls now perform
only a LUN assignment and fill
in the directory-identification of
[-1,-1].

2.7.2.8 File-Positioning Routines - The .POINT routine (position file
to specified byte)
unconditionally stores the virtual block number
(VBN) field for treating block devices as though they were record
devices.
The .POSIT and .POSRC routines are concerned with the positional
relationship of records within a file.
This relationship is of use
only in random access programming and is not supported in RSX-llS.
Calls to these routines return the error code IE.ISQ
(illegal
sequential operation) •

2.7.2.9 Queue 1/0 Function Routine - The queue I/O function routine
is called to execute a specified QUEUE I/O function and to wait for
its completion. The queue I/O routine accepts parameters that include
the address of the desired File Descriptor Block (FOB), the desired
QUEUE I/O function code, and any optional parameters that are to be
included in the QUEUE I/O directive.

2.7.2.10 Rename-File Routine - The rename-file function is concerned
with entries in a directory structure.
Because RSX-llS does not
support a directory structure, calls to .RENAM produce the following
results:
•

The file whose FOB address is contained .in RO is closed.

•

A parse (as defined in Section 2.7.2.5) is performed for
FDBs.

•

No additional checks are made.

both

2.7.2.11 File-Extension Routine - You cannot extend a file without
the support of a file system. Therefore, th~ file extend routine,
.EXTND, simply parses the file name (as defined in Section 2.7.2.5) if
the file is not already open.

2.7.2.12 File-Deletion Routines - The delete by
filename
block
routine, .DLFNB, performs exactly as DELET$ does (described in Section
2.7.1.10). If the file is open, the .DLFNB call marks the file for
deletion (.MRKDL).
If the file is closed, the logical unit assignment
occurs.

2-28

RSX-llS SUPPLIED SOFTWARE
2.7.2.13 Device
Control
Routine - The
routine
to
perform
device-specific control functions, .CTRL provides users with a control
interface to the ANSI magtape and Files-11 ACPs.
Because neither of
them is supported on RSX-llS,
this routine returns an error code
IE.ILL (illegal operation).

2.7.3

Using the FCS Subset

If you wish to acquire the features of FCS subset
(as a result of
either explicit use of macro calls or FORTRAN I/O), you should link
your task against the subset object
library,
[l,l]llSLIB.OLB.
Creating this library is an option in the RSX-llS system generation
process. Failure to use this library results in the resolution of FCS
code from the host system object library (SYSLIB.OLB). The FCS host
system object library is much larger than the subset object library.
It is also inappropriate to use the FCS host system object library
with RSX-llS because it requires interaction with a
file system to
service several types of devices.

2-29

CHAPTER 3
RSX-llS VERSION 4.2 DISTRIBUTION KIT

3.1

RSX-llS VERSION 4.2 DISTRIBUTION MEDIA

RSX-llS Version 4.2 software is distributed on
The following distribution kits are available:

variety

media.

• One RK06 cartridge disk
• One RK07 cartridge disk
• Two RLOl cartridge disks
• One RL02 cartridge disk
• One TK50 magnetic tape cartridge
• One magnetic tape, 9-track, 800 bpi, 2400-foot
• One magnetic tape, 9-track, 1600 bpi 2400-foot
I

For RLOl distribution kits, the first volume is labeled llSKIT and the
second volume is labeled UPDATEA.

3.2

CONTENTS OF THE RSX-llS VERSION 4.2 DISTRIBUTION KIT

Table 3-1 lists most of the files contained in the RSX-llS Version 4.2
release kit.
All files in this table are located in UFO [2,20].
Section 3.3 lists additional files needed for generating an RSX-llS
system on an RSX-llM-PLUS or VAX/VMS host system.
The disk media are written in Files-11 format by the Peripheral
Interchange Program (PIP). The magnetic tape media are created in DOS
format by the File Transfer Utility Program
(FLX).
See
the
RSX-llM/M-PLUS and Micro/RSX Utilities Manual for more information on
PIP and FLX.
Table 3-1
Contents of the RSX-llS Distribution Kits
File

Identification

BMPRE.MAC

Basic MCR assembly prefix file

ABOBAS.MAC

Basic MCR source file

ATLBAS.MAC

Basic MCR source file
(Continued on next page)

3-1

RSX-llS VERSION 4.2 DISTRIBUTION KIT
Table 3-1 (Cont.)
Contents of the RSX-llS Distribution Kits
Identification

File
BRKBAS.MAC

Basic MCR source file

ERRBAS.MAC

Basic MCR source file

ERRMSG.MAC

Basic MCR source file

FMTDV.MAC

Basic MCR source file

FNDUCB.MAC

Basic MCR source file

GNBLK.MAC

Basic MCR source file

GETNUM.MAC

Basic MCR source file

KEYWD.MAC

Basic MCR source file

LKLST.MAC

Basic MCR source file

MCRBAS.MAC

Basic MCR source file

OPEBAS.MAC

Basic MCR source file

PRSBAS.MAC

Basic MCR source file

REDBAS.MAC

Basic MCR source file

REMBAS.MAC

Basic MCR source file

RPSBAS.MAC

Basic MCR source file

RUNBAS.MAC

Basic MCR source file

TIMBAS.MAC

Basic MCR source file

OTLPRE.MAC

Task
Loader
On-Line
assembly pref ix file

OTL.MAC

OTL source file

OTLCD.MAC

OTL source file

OTLERR.MAC

OTL source file

OTLHD.MAC

OTL source file

OTLLB.MAC

OTL source file

OTLLD.MAC

OTL source file

OTLQIO.MAC

OTL source file

OTLRD.MAC

OTL source file

SIPPRE.MAC
SIP.MAC

System Image Preservation
assembly pref ix file
SIP source file

SIPBOO.MAC

SIP source file

(OTL)

(SIP)

(Continued on next page)

3-2

RSX-llS VERSION 4.2 DISTRIBUTION KIT
Table 3-1 (Cont.)
Contents of the RSX-llS Distribution Kits
File

Identification

SIPCO.MAC

SIP source file

SIPERR.MAC

SIP source file

SIPLD.MAC

SIP source file

SIPQIO.MAC

SIP source file

TKTN.MAC

Task
Termination
(TKTN) source file

FCSllS.OBJ

File
Control
Services
subset
concatenated
modules

SETT IM.MAC

Source file of FORTRAN callable
routine to set system time

RMDUNM.OLB

RMDEMO object library
unmapped systems

file

for

RMDMAP.OLB

RMDEMO object library
mapped systems

file

for

llSGEN.CMD

RSX-llS system generation command
file for Phase I

l lSGEN 2. CMD

RSX-llS system generation command
file for Phase II

BLXIOU .OBJ

Object file required to build OTL
for unmapped systems

BLXIOM.OBJ

Object file required to build OTL
for mapped systems

3.3

ADDITIONAL FILES
SYSTEMS

REQUIRED

FOR

RSX-llM-PLUS

Notification

AND

(FCS)
object

VAX/VMS

HOST

The RSX-llS Version 4.2 distribution kits also contain additional
files to generate RSX-llS on an RSX-llM-PLUS or VAX/VMS host system.
These additional files include the following:
•

Command files to perform the RSX-llS system generation

•

The RSX-llM Task Builder task image file and the
Virtual Monitor Console Routine (VMR) task image file

•

Necessary portions of system macro and object libraries

•

Command files to build process control device commons

•

Executive and device driver source files

•

Command files and object library to build
Analyzer (CDA) for use on the host system

the

RSX-llM

Crash

Dump

The command file, llSCOPY.CMD, copies all the needed files from the
distribution kit to your target disk during Phase I of the system
generation.
3-3

CHAPTER 4
TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS

This chapter briefly describes how to task build the Executive as well
as the how to task build the system tasks.
It also describes how to
build user-written tasks and provides additional information you will
need to generate your RSX-llS system.

4.1

BUILDING THE EXECUTIVE

The first step in building the Executive is to obtain the system
generation output and the Executive object library.
(The command
files controlling the RSX-llS system generation will ensure that all
required files are present.)
This output consists of at least the
following three files:

RSXllS.OLB

Executive object library

RSXBLD.CMD

Executive task-build command file

RSXMC.MAC

Executive assembly prefix file

Additional files are present provided that you
included support
the DSSll, UDCll, or ICS/ICRll subsystems in the Executive.

for

If you selected one or more user-written resident
drivers during
Phase I, you can insert the driver(s) and data base object module(s)
into RSXllS.OLB during Phase II.
However, you must edit the Executive
task-build command file to include the resident drivers.
After TKB builds the target Executive, the task image file RSXllS.TSK
and the symbol table files
are placed in the following User File
Directories (UFOs) designated for system tasks:
•

[1,60]

For unmapped systems

•

[1,64]

For mapped systems

To prevent the accidental loss of your system, you should maintain the
task
image file
(RSXllS.TSK) as a backup after 11SGEN2 creates your
system image file (RSXllS.SYS).

4.2

BUILDING THE RSX-llS TASKS

You can write RSX-llS tasks in MACR0-11 or FORTRAN.
To ensure that
FORTRAN tasks are linked properly to the Object Time System {OTS), you
must place the OTS modules in a library.
You must then specify that
library in the task-build command line.
The steps to include OTS are
documented in the appropriate FORTRAN installation guide.

4-1

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
Section 4.2.1 describes how to build system tasks
describes how to build other kinds of tasks.

4.2.1

and

Section

4.2.2

System Tasks

The following system tasks may be included in the RSX-llS system:
e

TKTN

Basic MCR

OTL

SIP

•

The system activity
RSDVlH)

display

programs

(RSDVOS,

RSDV52,

and

During the llSGEN process, you are asked whether the assembly listings
and/or the task-build maps for these system tasks should be printed.
If you choose to print either of these, your listing output is then
sent to the line printer if one is available.
If not, the listing is
printed on the console terminal.
The sizes of Basic MCR, OTL, and SIP depend on whether you include
optional features.
The respective build files for each of these tasks
allows for the maximum size of the task. However, even if you do not
include all the options for Basic MCR, OTL, or SIP, it is not
necessary to edit the build file to reduce the size of the partition
for that task.
When configuring the system with VMR, use the map
listings to determine the size of the partition for each of the tasks.
A task can be loaded into a partition smaller than the size specified
in the build file, as long as the partition is large enough to include
the task address limits.

4.2.1.1 TKTN - The Task Termination Notification
(TKTN) program is
the privileged task used by the Executive to print task termination
and device status messages.
If you select TKTN during Phase I, it is
assembled and built during the 11SGEN2 procedure.
The command file TKNllSBLD.CMD specifies that you use partition
SYSPAR, with a length of 3700(8) bytes and a base address of 20000 for
unmapped systems. Normally, the default base address of TKTN for an
unmapped system is not correct and must be changed to the proper
address. On a mapped system, SYSPAR is 3700(8) bytes long.

4.2.1.2 Basic MCR - Basic MCR provides the RSX-llS user with a subset
of the MCR commands available in RSX-llM. The commands are described
in Section 2.1 of this manual.
The size of Basic MCR varies from approximately 6300(8) to 12100(8)
bytes for unmapped systems and 6400(8) to 14000(8) bytes for mapped
systems. Unmapped systems include a base address of 20000.
The
difference in size between the smaller and larger versions is due to
the inclusion of optional features. These are the ATL/TAL commands,
the OPEN command, and full error message text.

4-2

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
The distribution kit includes the Basic MCR assembly prefix file,
BMPRE.MAC.
This file produces a Basic MCR that includes none of the
optional features.
If you want to include an option, edit the
assembly prefix file.
You can edit the file by locating the control
symbol corresponding to the desired option and removing the semicolon
(;)
from the beginning of the line (refer to the sample dialogs in
Chapters 5 and 7).
The control
symbols,
along
with
their
corresponding options, are as follows:
e

R$$ATL

ATL/TAL commands

R$$ERM

Full error message text

R$$0PE

OPEN command

DIGITAL recommends that you choose the full form of the error messages
so that you will not have to look them up every time an error occurs.
The Basic MCR task-build command file, BASMCRBLD.CMD, specifies that
the partition MCRPAR be used, with a maximum length of 12100 bytes for
unmapped systems (14000 for,. mapped systems).
The base address
is
20000 for unmapped systems.
When you begin task building, if the specification of a partition
length is larger than necessary, it will have no effect on the task
image. However, for an unmapped system, you must determine the
partition base address by carefully examining the memory requirements
of other system components.

4.2.1.3 OTL - The On-Line Task Loader (OTL) allows you to install and
fix a task in an RSX-llS system.
You must build the task on the host
system and copy it to a medium supported by OTL and the RSX-llS system
(that is, the device driver for that medium must be loaded in the
RSX-llS system with VMR). If OTL is to be included, you must assemble
and build it during the RSX-llS SYSGEN procedure.
The size of OTL varies from approximately 6200(8)
to 10600(8)
bytes
for unmapped systems and from 10000(8) to 15000(8) bytes for mapped
systems. The difference in size between the smaller and larger
versions is due to the inclusion of optional error message text and
device support.
The distribution kit contains a prefix file that does not include
support for full error message text.
If you wish, you may edit the
assembly pref ix file OTLPRE.MAC. This is done by locating the line in
which the control symbol R$$ERM is assigned the value 0 and removing
the semicolon (;) from the beginning of that line. DIGITAL recommends
that you choose the full form of the error messages so that you will
not have to look them up every time an error occurs.
Table 4-1 lists the load devices that OTL supports
control symbol associated with each medium.

4-3

and

the

assembly

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
Table 4-1
OTL Assembly Control Symbols and Load Devices
OTL Assembly Control symbol

Load Device

PRll, P$$Rll

PCll/PRll paper tape reader

RXll, R$$Xll

RXll/RXOl flexible disk

RX21, R$$X21

RX211/RX02 flexible disk

RXSO, R$$UDA

RUXSO/RXSO flexible diskette

TAll, T$$All

T~ll/TU60

TCll, T$$Cll

TC11/TU56 DECtape

TMll, T$$Mll

TM11/TE10,TS03,TU10 magnetic tape

TSll, T$$Sll

TS11/TK25,TS11,TSVOS,TU80
magnetic tape

TU16, T$$Jl6

TM02/TE16,TU16,TU45,TU77 magnetic
tape

TU58, T$$U58

DL11/TU58 DECtape II

cassette tape

If you include any of these devices during the RSX-llS system
generation, OTL will support them. OTL requires that the driver for
any device you want to use be in the system
(either resident or
loadable).
If you want to make OTL smaller, you may limit the types of devices
supported by OTL.
You can do this by editing the assembly prefix file
OTLPRE.MAC. Locate the line that contains "INCLUDE" that is followed
by the symbol for the device type you wish to exclude.
(Refer to the
OTL assembly control symbols listed in Table 4-1.) Insert a semicolon
(;)
from the beginning of the line. The line will be treated as a
comment and the code required to support the device type will not be
included in OTL when it is assembled.
The OTL task-build command file OTLBLD.CMD specifies that
the
partition OTLPAR be used. The partition may have a maximum length of
10600(8) for unmapped systems and 15000 for mapped systems.
This
would include a base address of 20000 for unmapped systems.
You can
edit this file according to the guidelines specified for Basic MCR.

4.2.l.4 SIP - The System Image Preservation (SIP) task allows you to
save (up to 124K words) a copy of a running RSX-llS system on a medium
that can be bootstrapped.
If you wish to include SIP, it can be
tailored in exactly the same manner as OTL.
The size of SIP varies from approximately 3500(8) to 6700(8) bytes for
unmapped systems and from 3700(8) to 7400(8) bytes for mapped sytems.
Again, the size difference between the smaller and larger versions is
due to the inclusion of optional error message text and device
support. You can adapt SIP to meet specific system needs by editing
its assembly prefix file, SIPPRE.MAC, using the same guidelines as
those presented for OTL.

4-4

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
The distribution kit file, SIPPRE.MAC, does not include full error
message text.
If you wish to include it, edit the assembly prefix
file by locating the line in which the control symbol R$$ERM is
assigned the value 0. Remove the semicolon (;) from the beginning of
the line. DIGITAL recommends that you choose the full form of the
error messages so that you will not have to look them up every time an
error occurs.
There are some minor differences in device support between SIP and
OTL. One difference concerns paper tape. OTL reads a task image into
memory and therefore uses the paper tape reader. However, SIP writes
a system image and must use the paper tape punch.
The control symbol
employed by SIP for the PCll paper tape punch is PPll.
Additionally,
SIP does not support the following devices:
•

RX50 flexible diskette

•

TK25 magnetic cartridge

TU58 DECtape II

•

TSll magnetic tapes

Table 4-2 lists the load devices that SIP supports
control symbol associated with each medium.

and

the

assembly

Table 4-2
SIP Load Devices
SIP Assembly Control Symbol

Load Device

PPll, P$$Pll

PCll/PPll paper tape punch

RXll, R$$Xll

RXll/RXOl flexible disk

RX21, R$$X21

RX211/RX02 flexible disk

TAll, T$$All

TA11/TU60 cassette tape

TCll, T$$Cll

TC11/TU56 DECtape

TMll, T$$Mll

TM11/TE10,TS03,TU10 magnetic
tape

TU16, T$$Jl6

TM02/TU16,TU45,TU77 magnetic
tape

The SIP task-build command file, SIPBLD.CMD,
specifies that the
partition SIPPAR be used. The maximum length is 6700(8) for unmapped
systems and 7400(8) for mapped systems. This includes a base address
of 20000 for unmapped systems. You should edit this file according to
the guidelines given for Basic MCR.

4.2.1.5 RSDVOS, RSDVS2, and RSDVlH (RSD) - RSDV05, RSDV52, and RSDVlH
are the system activity display programs. They are privileged tasks
that run on VTOS, VT52, and VTlOO video terminals, respectively.
The
RSD tasks require approximately 6K words of memory to run on RSX-llS.
(These display programs are similar to the RMDEMO display program on
RSX-llM and RSX-llM-PLUS; see the RSX-llM/M-PLUS System Management
Guide for more information.)

4-5

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
If you include any of the RSD tasks in your system, you should select
the following two options during the system generation process:
•

Executive AST support.

•

Unsolicited input character AST
(terminal driver option).
This option is available in all terminal drivers except the
baseline terminal driver.

Selecting these options will allow you to do the following:
•

•

4.2.2

Exit cleanly from an RSD display by
PRL/zl
(Otherwise, you must press
RSD.)

pressing

pRuq

(CTRUCl
or
and then abort

Generate an updated display (replay) at any time by pressing
the keyboard space bar or any other keyboard character.

Other Tasks

This section provides information on generating
system tasks, but are tasks that you may need.

tasks

that

are

not

4.2.2.1 K-series Lab Support Routines - The K-series lab support
routines are built by SGNKLAB, which is run separately after Phase II.
During Phase I of the system generation, you will be asked if you want
K-series support.
If you answer Yes, the following will occur:
•

You will be prompted for the required vector information.
If
the K-series devices,
or any other devices,
require an
interrupt vector address greater than 400, you must specify
the highest address needed.

•

The CINT$ directive will be included in your system.

•

Asynchronous system trap (AST) support will be included in the
system.

To build these routines, use one of the following command lines
completing Phase II:

after

>@[200,200]SGNKLAB (on an RSX-llM host system)
>@[2,200]SGNKLAB (on an RSX-llM-PLUS or a VAX/VMS host system)
For more information on the K-series routines,
RSX-llM/M-PLUS I/O Drivers Reference Manual.

refer

the

4.2.2.2 User-Written Tasks - To properly assemble and link
any
user-written tasks that are to be included in the target system,
special library conventions must be observed. You must use EXEMC.MLB
as the macro library and llSLIB.OLB as the system library.
(System
libraries are discussed in Section 4.4.1.)

4-6

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
4.3

FINAL CONFIGURATION OF THE EXECUTIVE

Once the RSX-llS Executive and all of the privileged tasks are built,
the following steps must be completed before you can bootstrap and run
the system.
(You can run VMR on the system's task image file to
complete these steps.)
1.

Create the memory partitions in the system

Load the required device drivers

Install the needed tasks

Fix the tasks in memory

The minimum steps required to configure the Executive include creating
all the partitions, loading the required device drivers and, if tasks
are to be loaded on line, installing and fixing into memory Basic MCR
and OTL.
Once these are in memory, tasks and commons can be loaded
into a running RSX-llS system by using OTL.
If the RSX-llS system is a DECnet node and it supports down-line task
loading, OTL is not required for on-line loading of nonresident tasks
(because the tasks can be down-line loaded by DECnet).
The following procedure details how to set up partitions
required tasks on the target system:

and

install

Install and run VMR

Extend pool space to the base of the first partition

Set up partitions by consulting the maps for
tasks

Load the loadable device drivers

Install the privileged tasks (Basic MCR, OTL, SIP, TKTN)

Fix the tasks into (virtual) memory

Set the time (optional) and save a copy of the
bootable medium

Exit from VMR

the

privileged

system

Example 4-1 shows the application of this procedure.
Example 4-1 Final Configuration of the Executive for a Mapped System
with Executive Commons, System-Controlled Partitions,
and Loadable Device Drivers
MCR>SET /UIC=[l,64]
MCR>INS $11MVMR/TASK= ••• VMM
MCR>VMM
ENTER FILENAME: RSXllS.SYS
VMR>SET /POOL=*
VMR>SET /MAIN=TTPAR:*:l64:TASK
VMR>LOA TT:
VMR>SET /MAIN=DRVPAR:*:*:SYS
VMR>LOA MM:
VMR>LOA OM:
VMR>LOA DK:
VMR>SET /TOP=DRVPAR:-*

4-7

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
VMR -- *DIAG* Installed tasks may no longer fit in partition
VMR>SET /MAIN=SYSPAR:*:37:TASK
VMR>SET /MAIN=MCRPAR:*:l40:TASK
VMR>SET /MAIN=OTLPAR:*:l50:TASK
VMR>SET /MAIN=SIPPAR:*:74:TASK
VMR>SET /MAIN=EXCOM1:*:200:COM
VMR>INS EXCOMl
VMR -- *DIAG* Partition reduced to executive common size
VMR>SET /MAIN=EXCOM2:*:200:COM
VMR>INS EXCOM2
VMR -- *DIAG* Partition reduced to executive common size
VMR>SET /MAIN=GEN:*:*:TASK
VMR>INS TKN/FIX=YES
VMR>INS BASMCR/FIX=YES
VMR>INS OTL/FIX=YES
VMR>INS SIP/FIX=YES
VMR>Az
NOTE
If you answered No to the Phase II question,
"Do you
want to configure the Executive at this time using
VMR," you would follow the procedure described in
Section 4.3.
If you answered Yes,
the Phase II
program automatically creates the system image file
and installs and runs VMR.
When the VMR prompt
appears follow the procedure outlined in Section 4.3

4.4

OPERATING CONSIDERATIONS

The remainder of this chapter gives information
helpful in generating your RSX-llS system.

4.4.1

that

you

may

find

three

types

each

Libraries

The RSX-118 operating system contains the
libraries:
•

System object library

•

System macro library

•

Resident library

The following sections
libraries.

give

brief

following

descriptions

these

4.4.1.1 System Object Library - Although the host system has a
complete system object library
(SYSLIB.OLB) of its own, you should
create an additional object library for tasks.
This will allow you to

4-8

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
use several hardware/software features on the target RSX-llS system.
Your RSX-llS system object library must contain the following modules
to support these features:
FCS Subset

(Required with FORTRAN OTS)

FORTRAN OTS
LPS/ARll
ICS/ICRll
UDCll
DRS/DSSll
Purdue ISA

FORTRAN process I/6 routines
FORTRAN process I/O routines
FORTRAN process I/O routines
FORTRAN process I/O routines
FORTRAN process I/O routines (required with
LPS/ARll, ICS/ICRll, UDCll, DRS/DSSll,
LPAll, and LP routines)
I/O support routines

LPAll

During the RSX-llS system generation, this library
(llSLIB.OLB)
is
created under the system directory of the target system device (SY:}.
(On RSX-llM, the system directory is
[1,1].
On RSX-llM-PLUS and
VAX/VMS, the directory is [g,l], where g is the group number specified
for system files during the SYSGEN procedure.)
When you build tasks for the target RSX-llS system that require any of
the
previously
listed
features, you should include the file
specification for your system object library in the task-build command
input.
This specification prevents the llSGEN command file from
referencing the host system's system library.
Also, note that if you have selected a UFO other than [1,1]
for your
system object library (RSX-llM-PLUS and VAX/VMS hosts only), you must
specify the directory with the /DL switch when building a task.
Otherwise, the Task Builder will expect to find SYSLIB.OLB in [1,1].

4.4.1.2 System Macro Library - You must use the standard system macro
library
RSXMAC.SML
for
program
development
on
an RSX-llM,
RSX-llM-PLUS, or VAX/VMS host. As with SYSLIB.OLB, if RSXMAC.SML is
not in UFO
[1,1], you must specify the directory in the MACR0-11
command line when assembling a module.

4.4.1.3 FCS Subset Resident Library - You create the standard FCS
resident
library
by assembling the file
[2,200]11SRES.MAC and
task-building it according to the directions given in the file itself.
For more information on building, defining, and loading resident
libraries into a system, see the RSX-llM System Generation and
Installation Guide and the RSX-llM/M-PLUS and Micro/RSX Task Builder
Manual.

4.4.2

Device Commons

Several DIGITAL-supplied support routines require direct access to the
I/O page to service some process-I/O options.
On mapped systems, the
construction of a device common is required to obtain direct access.
However, construction of a device common is optional on an unmapped
system. Direct access is required to support the following options:
UDCll

Analog outputs
Single-shot digital outputs
Digital inputs
Counter inputs
4-9

TASK-BUILDING THE RSX-llS EXECUTIVE AND SYSTEM TASKS
ICS/ICRll

Digital inputs
Counter inputs

DSSll

All

The llSGEN command procedure automatically constructs device commons
when you request direct access for the previously mentioned devices or
the device common itself (by answering Yes to the questions).
To load device commons into the system, create a partition that has
the DEV attribute. This will map the desired portion of the I/O page.
Then use the INSTALL command to mark the device common resident.
You
can perform these steps using VMR commands.
For more information on processing I/O device commons,
RSX-llM/M-PLUS and Micro/RSX I/O Drivers Reference Manual.

4.4.3

see

the

Other Methods for Task Loading

By virtue of its memory-resident design, RSX-llS relies on
a
host/target system relationship for program development. Tasks for
RSX-llS systems must be developed on the host system and may be
transported to the target system.
As previously discussed, the
On-Line Task Loader (OTL) is provided to load tasks into a running
RSX-llS system.
There are, however, two alternative methods to
accomplish task loading.
The first method relies on VMR to install and fix the task image into
the RSX-llS system image.
When this image is bootstrapped into
memory, the task is available to be run.
The second method requires the facilities of DECnet-11 Version 3.0,
the RSX-11 network software.
A special network task loader is
provided to down-line task load images over a communications line.
Furthermore,
the capability of RSX-llS is enhanced by DECnet to
support task checkpointing to the host by means of the network loader.
Both the host and target system must be configured with DECnet to use
these features.
Refer to the DECnet System Manager's Guide for more
information.

4.4.4

System Loading

When you complete the RSX-llS system generation, you must bootstrap
the system image file, RSXllS.SYS,
into memory for it to become
operational. On RSX-llM hosts, RSXllS.SYS resides in UFO [1,60] ~or
unmapped systems and UFD [1,64] for mapped systems. On RSX-llM-PLUS
and VAX/VMS hosts, the file resides in UFD
[g,64], where g is the
group number specified for system files during the system generation
procedure.
VMR on the host system has the capability of saving the contents of
the system task image file to a variety of device media in bootable
format. You can load these system images directly on the target
configuration by using the appropriate bootstrap mechanism.
A host system configured with DECnet allows the down-line loading of
an RSX-llS system image.
This feature eliminates the necessity of
using VMR to SAVE an RSX-llS system image on media in bootable format.
As discussed in Section 4.2.1.4 you can save a running RSX-llS system
using SIP, which produces a bootable image in exactly the format
generated by the VMR command SAVE.
4-10

CHAPTER 5
RSX-115 SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

This chapter explains how to generate an R8X-ll8 system on an RSX-llM
host system.
It also contains an example of a typical terminal dialog
from an RSX-llS system generation on an RSX-llM host system.

5.1

PERFORMING AN RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

A complete RSX-118 system generation is performed in two phases on an
RSX-llM host system.
In the first phase, the procedures are primarily
the same as those followed for generating an RSX-llM system.
(Consult
the RSX-llM System Generation and Installation Guide for a detailed
description of this phase of the SYSGEN command procedure.) This phase
is controlled by the command file llSGEN.CMD, which is found in User
File Directory
(UFD)
[2,20]
of the RSX-llS distribution medium
labeled, "llSKIT".
NOTE
To perform your RSX-llS system generation on line, you
must
first make a copy of your latest RSX-llM
distribution kit. This will serve as your target
disk.
You may then begin the system generation
procedure.
The command file that controls the second phase of the RSX-llS system
generation is 118GEN2.CMD. This file is also located in UFO [2,20].
The RSX-llS system generation procedures, llSGEN and 118GEN2, expect
to find llSGEN.CMD and llSGEN2.CMD in UFO [200,200] on your baseline
disk. Therefore, you must copy them as described in Section 5.1.1.
The following
llSGEN.CMD:

operations

are

performed

•

Prompting for the Executive options

•

Assembling the Executive

•

Assembling the drivers

5-1

during

the

processing

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM
The following
11SGEN2.CMD:

operations

are

performed

during

the

•

Building the target Executive and the drivers

•

Assembling (building) the RSX-llS system tasks

•

Final configuration of
image)

the

Executive

processing

(creating

the

system

The Phase II operations are discussed in Chapter 4.

5.1.1

Copying Procedures

Before you perform the RSX-llS system generation on an RSX-llM host,
you must copy [2,20]11SGEN.CMD and [2,20]11SGEN2.CMD from the llSKIT
distribution media. These indirect command files must be copied to
[200,200]
on the disk on which the system generation is to be
performed.
If your distribution kit is on disk(s), use the PIP
Utility to copy the files.
For example,
>PIP ddnn:[200,200]=ddnn: [2,20]11SGEN.CMD
If your kit is on magnetic tape(s), you can use the FLX Utility.
example,

For

>FLX ddnn:[200,200]=mmnn:[2,20]11SGEN.CMD
NOTE
If you have an RLOl distribution kit,
the
files are on the volume labeled "llSKIT".

5.1.2

command

Invoking the System Generation Programs

Type the following command to invoke the
programs:

Phase

system

generation

Type the following command to invoke the Phase
programs:

system

generation

>@llSGEN.CMD

>@11SGEN2.CMD

5.1.3

Notes for RSX-llS Version 4.2 System Generation on
Host

RSX-llM

This section contains information you should consider before you begin
the system generation process.
1.

If you are running on an RLOl kit, be sure to make a copy of
the RSX-llM kit because 11SGEN2 deletes selected files to
make room for later stages of the RSX-llS system generation.

If you are performing an RLOl RSX-llS system generation,
listing
files
(.LST)
for privileged tasks are deleted
automatically to provide room for the SYSGEN.

5-2

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM
3.

If you are generating the system from the baseline disk, you
may
have
to load the device driver for the RSX-llS
distribution kit medium. After the files have been copied,
you must unload the driver.
Whether you are generating the system on line or from the
baseline disk, you must dismount (and deallocate if you are
on a multiuser system) the RSX-llS distribution kit device
before you invoke the SYSGEN command procedure.

If you are generating the system on line, assign the baseline
disk to be your system disk as follows:
ASN ddnn:=SY:

Always perform the RSX-llS system generation with the command
files in UFO [200,200).

You may want to do a preliminary system generation before you
do your actual SYSGEN. To do a preliminary SYSGEN (PREPGEN),
invoke the command file for Phase I of the SYSGEN
(@llSGEN)
and answer YES to the question,
"Do you want to inhibit
execution of MCR commands (PREPGEN)?"
Phase I continues, but the answers you give to the questions
are placed in a saved answer file instead of being used
immediately. When Phase I finishes, reinvoke llSGEN.CMD to
run the phase again.
This time, you do not inhibit MCR
command line execution and the SYSGEN procedure uses the
answers in the saved answer file.
Performing a PREPGEN saves time and prevents mistakes.
The
sample dialog in Section 5.2 shows a PREPGEN being done
before the actual SYSGEN.

During Phase I of the system generation procedure, llSGEN.CMD
asks for your system's device configuration and requests the
system directives you would like in the Executive.
In both
cases, you may print out a table of the available options
before you answer the question.

For further information on generating the
Chapter 4.

5.2

RSX-llS

system,

refer

SYSGEN DIALOG ON AN RSX-llM HOST SYSTEM

This section contains an example of the text of a typical
dialog from an RSX-llS system generation on an RSX-llM host.

terminal

The dialog and procedures in Phase I are the same for RSX-llM and
RSX-llS; for detailed explanations of the Phase I system generation
questions, see the RSX-llM System Generation and Installation Guide.
The system generated in the example in this chapter supports
following hardware configuration for a PDP-11/23 processor:
128K memory
60
cycle line clock
1
RL02 cartridge disk controller with two drives
TU58 DECtape controller with two diives
1
1
LPll line printer controller
null device driver
1
1
DZVll terminal interface
1
DLVll terminal interface
5-3

the

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM
The following software support is included:
•

Large {20K) RSX-llS Executive

•

Support for:
Executive common
Memory management
Send/receive directives
Get mapping context directive
Address checking
I/O rundown
Loadable device drivers
AS Ts
Powerfail recovery
Logical devic~ assignment
Crash notification
Group-global event flags
Memory parity

TKTN

XDT

•

System-controlled partitions

MCR with support
• Basic
error-message text

for

OPEN,

ATL/TAL,

and

full

with support for full error-message text and for
• OTL
devices generated into the RSX-llS system

all

OTL

SIP with support for full error-message text and for
• devices
generated into the RSX-llS system

all

SIP

RSDVlH

•

RSX-llS File Control Services {FCS) subset

The system generation is being performed on an RSX-llM Version 4.2
RL02 baseline system disk. The RSX-llS release kit consists of one
RL02 labeled, "llSKIT".
Questions calling for a YES/NO answer can be answered by pressing
RETURN key for a "NO" answer.
{This is the default answer.)

the

By pressing the RETURN key, you may specify the default answer to a
question that asks for a value.
This default value is displayed on
the terminal screen.

5.3

EXAMPLE OF AN RSX-llS SYSTEM GENERATION DIALOG ON AN RSX-llM HOST
SYSTEM

Fo~lowing

is the actual dialog for an RSX-118 system generation on
RSX-llM host system.

RSX-llM V4.2 BL38
>RED DL:=SY
>RED DL:=LB:
>MOU DL:RSXM38
>@DL: [l,2]STARTUP

124.k Mapped

(BASELINE)

5-4

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM
>* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY) (SJ: 13:40 29-MAY-85
>TIM 13:40 29-MAY-85
>*ENTER WIDTH OF THIS TERMINAL [D 0:132.J:
>SET /BUF=TI:l32.
>ACS SY:/BLKS=512.
>@ <EOF>
>MOU DLl:llSKIT
>INS $PIP
>PIP DLO: (200,200)/NV=DLl: [2,20JllSGEN.CMD,llSGEN2.CMD
>DMO DLl:
OMO -- TTO:
dismounted from DLl:
*** Final Dismount Initiated ***
13:40:50 *** DLl: -- Dismount complete
>@llSGEN

>;
>; RSX-llS Version 4.2 BL38 System Generation done on RSX-llM

>;
>; Copyright (C) 1979,1981,1983,1985
>; Digital Equipment Corporation, Maynard, Mass.
>; All Rights Reserved.

>;
>;

>; RL01/RL02 distribution kit

>* 3. Do you want to inhibit execution of MCR commands? [Y/NJ: Y
>* 3A. Do you want to create the assembly and build files on the SY: device? [Y/N D:YJ N
>* 5. Are you generating a mapped system? [Y/NJ: Y
>* 6. Use an input saved answer file? [Y/NJ:
>* 9. Name of output saved answer file [D: SYSSAVED.CMDJ [SJ:

>;
>; Phase I output saved answers created in file DLO: [200,200JSYSSAVED.CMD;l

>;
>* 16. enter device for EXCPRV disk when it is ready (ddu:)
>MOU DLl:EXCPRV

[D: DLl:J

[SJ: DLl:

>;
>; Target configuration

>;
>* 1. Processor Type [D: ll/34J
(SJ: 11/23
>* 2. Does processor have a switch register? [Y/N D:N]:
>* 3. Memory Size (in K-word blocks) [D R:l6.-1920. 0:16.]: 128.
>* 4. Include support for K-series devices? [Y/N D:NJ:
>* 6. Floating point processor (FP-11) present? [Y/N D:NJ: Y
>* 8. Extended instruction set (EIS) present? [Y/N D:NJ:
>* 10. Line frequency: A- 60 HZ B- 50 HZ [D: AJ [SJ:
>* 11. KWll-Y Watchdog timer support? [Y/N D:NJ:
>* 12. Memory parity support? [Y/N D:NJ: Y

>;
>;
>;
>;
>;
>;
>;
>;

The response to the following question specifies the highest interrupt
vector.
If you respond with a value less than or equal to 400, SYSGEN
will assign the value associated with the highest interrupt vector
specified during the Peripheral Section. Therefore, if your system
will include devices that are not specified during the Peripheral
Section and which have vectors above 400 (devices such as K-series and
certain communication devices), specify that value in the next question.

>* 14. Highest interrupt vector [O R:0-774 D:OJ:
For device configuration: "*" Prints device table, "." Terminates inquiry
"?" Prints current configuration
Enter devices and number of controllers for devices which require drivers
>* 15. Devices (SJ: *

>;
>;
>;
>
>

Device codes for A/D and industrial/laboratory devices:

5-5

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

AD- ADOl-D A/D Converter
AF- AFCll A/D Converter
AR- ARll Laboratory Subsystem
IC- ICRll/ICSll Industrial Contr~l Subsystem
IS- DRSll/DSSll Industrial Control Subsystem
LA- LPAll Laboratory Subsystem
LS- LPSll Laboratory Subsystem
UD- UDCll Universal Digital Controller
Device codes for Interprocessor communication devices:
XB- DAll-B Interprocessor Link
XE- DEUNA Unibus Ethernet Controller
XL- DLll-E Interprocessor Link
XM- DMCll-E/DMRll Interprocessor Link
XP- DPll Synchronous Interface
XQ- DQll Synchronous Interface
XU- DUll Synchronous Interface
:XW- DUPll Synchronous Interface
Device codes for unit record devices:
CR- CRll/CMll-E Card Reader
GR- VT11/VS60 Graphics Subsystem
LP- LAll/LPll/LSll/LVll/LNOl Line Printer
PP- PCll Paper Tape Punch
PR- PCll/PRll Paper Tape Punch and Reader
Device codes for disks devices:
DB- RP04/RP05/RP06 Disk Drive
DD- TU58 Cartridge DECtape II
DF- RFll Fixed Head Disk Drive
DK- RK03/RK05 Disk Drive
DL- RL01/RL02 Disk Drive
DM- RK06/RK07 Disk Drive
DP- RP02/RP03 Disk Drive
DR- RM02/RM03/RM05/RM80 Disk Drive
DS- RS03/RS04 Fixed Head Disk Drive
DT- TU56 DECtape
DU- RA60/RA80/RA81/RC25/RD51/RD52/RD53/RX50 Disk Drive
DX- RXOl Floppy Disk Drive
DY- RX02 Floppy Disk
EM- MLll Non-Rotating Electronic Memory
Device codes for Magnetic tape devices:
CT- TU60 Cassette Tape Drive
MM- TU16/TU45/TU77/TE16 Magtape Drive
MS- TS11/TU80/TSV05 Magtape Drive
MT- TU10/TE10/TS03 Magtape Drive
MU- TU81/TK50 Magtape Drive
Device codes for terminal interface devices:
YH- DHll Asynchronous Terminal Interface
YV- DHUll/DHVll Asynchronous Terminal Interface
YJ- DJll Asynchronous Terminal Interface
YL- DLll-A/-B/-C/-D/-E/-J/-W Asynchronous Terminal Interface
YZ- DZll/DZVll Asynchronous Terminal Interface

5-6

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

Device codes for pseudo devices:

>;
>;
>;

CO- console device
NL- null device

>;
>;
>;
>;

Enter responses as: devl=number controllers,dev2=number controllers, •••
If a device is specified without the nmnber of controllers, the number
of controllers defaults to 1.

>;
>;

Example: DK,DM=2,YL,NL.

>;
>* 15. Devices [SJ: DD,DL,LP,NL,YL,YZ.

>;
>; Processor:ll/23

Memory Size:l28K,Mapped

>;
>; Host configuration
>;
>*
>*
>*
>*

System:RSX-llS

1. Is a line printer available? [Y/N]: Y
3. Does the listing/map device have at least 120 colwnns? [Y/N]: Y
4. Assembly listings device (ddu:) [D: •NL:•] [SJ:
5. Map device for Executive and device drivers (ddu:) [D: DLl:J [S]:

>* EOS

* Do you want to: <CR>-continue R-repeat section E-exit P-pause (SJ:

>; Executive Options

>;
>;
>;
>*
>*
>*
>*

>;
>;

Answer Y(ES) if the following support is desired

6.
7.
8.
9.

>* 15.
>* 16.

>*
>*
>*
>*
>*
>*
>*
>*
>*
>*

>;
>;
>;
>;
>;
>;
>;

18.
19.
20.
22.
23.
25.
30.
32.
33.
36.

Executive common? [Y/N]: Y
Memory management (PLAS) directives? [Y/N]: Y
Send/Receive by reference directives? [Y/N]: Y
Get mapping context directive? [Y/N]: Y
Address checking support will be included
I/O rundown support will be included
Loadable device drivers? [Y/N]: Y
Should the default for all applicable drivers be loadable? [Y/N]: Y
AST support will be included
Include support for Cancel Selective Marktime? [Y/N]: Y
Task termination and device not ready messages (TKTN)? [Y/N]: Y
Power fail recovery? [Y/N]: Y
Large (20K) Executive? [Y/N]: Y
Logical device assignment? [Y/N]: Y
Do you intend to include a user-written driver? [Y/N]:
Executive Debugging Tool (XDT)? [Y/N]:
Include support for communications products (such as DECnet)? [Y/N]:
System controlled partitions? [Y/N]: Y
Group global event flags? [Y/N]: Y
For directives:

* - Prints the table
%

- Terminates inquiry
Gets all valid directives and terminates inquiry

>* 37. Enter code for system directives [SJ:

>;
>;
>;
>;
>;
>;

>;
>;

A- Get partition parameters
C- Send/Receive
E- Extend task
G- Get sense switch
I- Stop bit
K- Parent offspring tasking

B- Get task parameters
D- Alter priority
F- Connect to interrupt vector
H- Set system time
J- Specify requested exit AST
L- Parent offspring tasking with chaining

Enter responses as codelcode2code3 •••

5-7

(no commas)

(e.g.: ABCDF.)

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*

37.
38.
39.
40.
41.
42.
46.
48.
51.
52.
53.
54.

Enter code for system directives [SJ: %
Number of pre-allocated QIO packets [D R:0.-15. D:5.J:
Size of data transfer vector in words [D R:0.-33. D:33.J:
Round-robin scheduling interval in ticks [D R:0.-1000. D:5.J:
Highest priority class for consideration [D R:l.-249. D:l50.J:
Lowest priority class for consideration [D R:l.-150. D:l.]:
Seconds between printer not ready messages [D R:0.-255. D:30.]:
System crash register and stack dump device CSR [O R:0-177700 0:177564]:
Crash dump analysis: A- PANIC B- Crash Dump Analysis (CDA) C-None
[D:
CDA output notification device CSR [O R:l60000-177700 D:l77564]:
Enter CDA memory dump device mnemonic (ddu:) [S R:3-4]: DLl:
Enter CDA memory dump device CSR [O R:l60000-177700 0:177404]:

>* EOS *

Do you want to: <CR>-continue R-repeat section E-exit P-pause [S]:

>;
>;
>; Terminal driver options

>;
>*

1. Terminal driver desired (A/B/C/D, *prints table)

[S]: *

>;
>;
>;
>;
>;

Terminal drivers:

A- Tailorable half duplex
B- Tailored half duplex (user-oriented)
C- Full duplex
D- Baseline half duplex

>;
>*
>*

1. Terminal driver desired (A/B/C/D, *prints table) [S]: C
2. Unsolicited input timeout value in seconds [D R:0.-255. 0:120.J:

>;
>;

>*
>*
>;
>*
>*
>*
>*
>*
>*
>*
>*

Answer Y(ES) if the following support is desired
6. Unsolicited input character AST? [Y/N]: Y
8. Breakthrough write? [Y/N]: Y
CTRL/R support will be included
10. Escape sequence handling? [Y/NJ: Y
11. Get multiple characteristics? [Y/N]: Y
12. Set multiple characteristics? [Y/N]: Y
13. Get terminal driver options? [Y/N]: Y
17. Read after prompt? [Y/N]: Y
20. CRT rubout support? [Y/N]: Y
25. Hardware unrecoverable input error notification? [Y/N]: Y
26. Device independent cursor positioning? [Y/N]: Y

>;
>* EOS *Do you want to: <CR>-continue R-repeat section E-exit P-pause [S]:

>;
>;
>; System Options

>;
>;
>;

Answer Y(ES) if the following support is desired

>* 2A. Include support for the IPll Industrial I/O Subsystem? [Y/N]:
>* 11. What name would you like to give your system [D: RSXllS] [S R:0-6]:

>* EOS *Do you want to: <CR>-continue R-repeat section E-exit P-pause [S]:

>;
>;
Thinking •••
>; End of Executive option generation at 13:51:09 on 29-MAY-85

>;
>; Peripheral Configuration
>;
>;
Parameters appearing in square brackets"[ ••• ]" can only be
specified for the first controller of a particular device.
>;
>;
Parameters appearing in parentheses "( ••• )" only need be specified
>;
if the indicated option is present on the target system.
>;

5-8

[SJ:

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>;
>;
>;
>;

The default for loadable drivers has been set to *TRUE*.
To override this setting enter R (resident) as the first parameter
for the first controller of the specified device.

>; A/D and Laboratory devices: None specified

>;
>; Interprocessor communication devices: None specified
>;
>; Unit record devices: LP
>;
>; Enter [L/R,J vector, CSR, printer option
>;
(,[KMC timeout count <O=no KMC>, KMC vector, KMC CSR]) for:

>;
>* 16. LP controller 0 [D: 200,177514,LAlB0,0,300,160130]

(SJ:

,,LPll-B

>;
>; Disks: DD, DL
>;
>; Enter [L/R,] vector, CSR, number of drives for:
>;
>*

3. DD controller 0 [D: 300,176500)

[S]: ', 2

>;
>* 3. DL controller 0 [D: 160,174400)
>* 53. Con tr 0 unit o. is an RL01/RL02 [D: RLOl]
>* 53. con tr 0 unit 1. is an RL01/RL02 [D: RLOl]

[S]:

, '2
[S] : RL02
[S] : RL02

>; Tapes: None specified

>; Non-physical (pseudo) devices: CO, NL, TI, CL, LB, SY

>;
>; Terminal interface devices: YL, YZ

>;
>; Enter vector, CSR, E=DLll-E modem support/NO=no for:

>* 21. YL controller 0 [D: 60,177560,NO]

[SJ:

>;
>; Enter vector, CSR, highest line number <O to 7> [, answer speed] for:

>;
>* 24. YZ controller 0 [D: ,160100,,300)

[SJ: 310,160100,3,300

>;
>* EOS *

Do you want to: <CR>-continue E-exit P-pause [SJ:

>;
>;
>; End of interrupt vector area has been set to 400

>;
>;
>; Create Executive build files

>;
>;
>*

1. Do you wish to edit any of the Executive files? [Y/N]: N

>;
>;

>* EOS *Do you want to: <CR>-continue R-repeat section E-exit P-pause (SJ:

>;
>;
>;
>; Prepare for task building

>;
>;
>; Clean-up extraneous object files

>;
>;
>* EOS *Do you want to: <CR>-continue R-repeat section P-pause [SJ:
>OMO DLl:EXCPRV
OMO -- TTO:
dismounted from DLl:
*** Final dismount initiated ***
13:59:48 *** DLl: -- Dismount complete

5-9

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>;
>; End of llSGEN phase I at 13:59:50 on 29-MAY-85
>;
To continue type: @[200,200]11SGEN2

>;
>@ <EOF>

>
>@~lSGEN

>;
>; RSX-llS Version 4.2 BL38 System Generation done on RSX-llM

>;
>; Copyright {C) 1979,1981,1983,1985
>; Digital Equipment Corporation, Maynard, Mass.
>; All Rights Reserved.

>;
>;
>; RL01/RL02 distribution kit

>;
>* 3. Do you want to inhibit execution of MCR commands {PREPGEN)? [Y/N]: N
>INS- $UFO
>INS $EDI
>INS $LBR
>INS $INI
>INS $MAC
>* 4. Have you made a copy of the distribution kit? [Y/N]: Y
>*
5. Are you generating an unmapped system? [Y/N]: N
>* 6. Use an input saved answer file? [Y/N]: Y
>* 7. Name of input saved answer file [D: SYSSAVED.CMD] [SJ:

>;
>;
>;
>;

Phase I input saved answers
created on 29-MAY-85 at 14:01:05
by llSGEN version 2.10
are from file DLO: [200,200]SYSSAVED.CMD;l
9. Name of output saved answer file [D: DLO: [200,200]SYSSAVED.CMD]

[SJ:

>;
>; Phase I output saved answers created in file DLO: [200,200]SYSSAVED.CMD;2

>;
>*
>*
>*
>*
>*
>*

10.Use saved host configuration? [Y/N]: Y
11.Use saved peripheral configuration? [Y/N]: Y
12:Skip end of section {EOS) breakpoints? [Y/N]: Y
13.Skip end of execution {EOX) breakpoints? [Y/N]: Y
14.Clean up files from previous GENs? [Y/N]: Y
16.Enter device for EXCPRV disk when it is ready {ddu:)

[D: DLl:]

>;
>MOU DLl:EXCPRV
>SET /UIC=[l,l]
>PIP [l,20]RSXBLD.CMD;*/DE/NM
>PIP [ll,20]*.0BJ;*/DE/NM,*.UDC;*,*.ICR;*,*.IDS;*,*•PCS;*
>PIP [ll,24]*.0BJ;*/DE/NM,*.UDC;*,*·ICR;*,*·IDS;*,*·TTY;*,*•PCS;*
>PIP [ll,lO]RSXMC.MAC;*/DE/NM,ICTAB;*,[200,200]SGNPARM.CMD;*
>PIP [200,200]RSXBLD.CMD;*/DE/NM,TTDRVBLD;*
>PIP SY:[ll,20]RSXASM.CMF;*.DE.NM,RSXDRVASM;*.[12,20]MCRSETASM;*
>PIP SY: [ll,24]RSXASM.CMF;*.DE.NM,RSXDRVASM;*.[12,20]MCRSETASM;*
>PIP DLl: [ll,24]RSXASM.CMF;*.DE.NM,RSXDRVASM;*. [12,20]MCRSETASM;*
>PIP /FR
DLO: has 13825. blocks free, 6655. blocks used out of 20480.
Largest contiguous space = 9578. blocks
1383. file headers are free, 153. headers used out of 1536.

5-10

[SJ:

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>SET /UIC=[ll,10]

>;
>; Target configuration

>;
>: Processor:ll/23

>;
>;
>;
>;

Memory Size:l28k, Mapped

Systern:RSX-llS

Floating Point Processor
Parity Memory

>; Host Configuration

>;
>; Executive Options

>;
>; Terminal driver options

>;
>; System Options
>;
>;
>;

Thinking •••

>; End of Executive option generation at 14:10:40 on 29-MAY-85
>;
>; Peripheral configuration

>;
>;
>;

>;
>;
>;
>;
>;

>;
>;

Parameters appearing in square brackets "[ ••• ]"can only be
specified for the first controller of a particular device.
Parameters appearing in parentheses "( ••• )" only need be specified
if the indicated option is present on the target system.
The default for loadable drivers has been set to *TRUE*.
To override this setting enter R (resident) as the first parameter
for the first controller of the specified device.

>; A/D and Laboratory devices: None specified

>;
>; Interprocessor communication devices: None specified

>;
>; Unit record devices: LP

>;
>; Disks: DD, DL
>;
>; Tapes: None specified

>;
>; Non-physical

(pseudo) devices:

co, NL, TI, CL, LB, SY

>;
>; Terminal interface devices: YL, YZ
>;
>SET /UIC=[l,24] ! Creating TTDRVBLD.CMD
>SET /UIC=[ll,10]
>; End of interrupt vector area has been set to 400

>;
>;
>; Create Executive build files
>;
>; PIP RSXMC.MAC=DLl:RSXMCO.MAC/AP
>ASN SY:LB:

>;
>; Start of Executive assembly at 14:15:38 on 29-MAY-85
>SET /UIC=[ll,24]
>MAC @SY:RSXASM

>; End of Executive assembly at 14:33:22 on 29-MAY-85

>;
>:

5-11

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>; Start of device drivers assembly at 14:33:23 on 29-MAY-85
>MAC @SY:RSXDRVASM

>;
>; End of device drivers assembly at 14:46:34 on 29-MAY-85
>ASN =LB:

>;
>; Prepare for task building

>;
>SET /UIC=l,24]
>PIP RSXllS.OBS=[ll,24]*.0BJ
>PIP TTDRV.PBJ=[ll,24]*.TTY
>LBR RSXllS/CR:l00.:1010.:128.=RSXllS.OBS
>LBR TTDRV/CR:30.:380.:64.=TTDRV
>PIP /NV=[ll,lO]RSXBLD.CMD
>PIP [11,lO]RSXBLD.CMD;*/DE/NM
>REM LBR

>;
>; Clean-up extraneous object files

>;
>PIP RSXllS.OBS;*/DE/NM,TTDRV.OBJ;*[ll,24]*.0BJ;*,*/TTY;*
>DMO DLl:EXCPRV
DMO -- TTO:
dismounted from DLl:
*** Final dismount initiated ***
10:25:16 *** DLl: -- Dismount complete
>REM MAC
>REM UFD
>REM !NI
>REM EDI

>;
>; End of llSGEN phase I at 14:52:18 on 29-MAY-85
>;
To continue type: @[200,200]11SGEN2

>;
>SET /UIC=[200,200]
>@ <EOF>

>@[200,200]11SGEN2

>;
>; RSX-llS Version 4.2 BL38 System Generation Phase II

>;
>; Copyright (C) 1975,1981,1983,1985
>; Digital Equipment Corp., Maynard, MA.
>; All Rights Reserved.

01754

>;
>;

>;
>;
>;
>;
>;
>;
>;
>;
>;

Build The Executive And All Required Tasks
This command file will produce the target system on your SY: disk.
If it is an RLOl or an RL02, this command file will delete a number
of files from this disk to make room for those required to complete
this llSGEN. You must be running on an expandable copy of
your disk.
Note however, that the disk will be left in a
state such that RSX-llS sysgens may be performed at a later
date.
In addition, the sysgen itself may be terminated and
may be restarted at just about any point to rebuild particular
pieces of the system.

>;
>*In what UIC is SGNPARM.CMD if not [2,200] [S]:
>; RL01/RL02 distribution kit llSGEN version 2.lQ for RSX-llM BL38

5-12

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>; Continuation from llSGEN PHASE I done on 29-MAY-85 at 14:48:11
>TIM
17:51:36 29-MAY-85

>;
>;The map device specified must already be mounted with UIC [1,34].
>; If it is not, respond to the next question with AZ and do so.

>;
>* In which device is the PRVBLD disk [DDU:]
>MOU DLl:PRVBLD
>ASN SY:=LB:

[S]: DLl:

>;
>; Expanded comments provide a complete description of every step in
>; this llSGEN command file.
On the other hand, short comments
>; provide virtually no explanatory text.

>*Do you want expanded comments? [Y/N]: y

>;
>; Make room on the basline disk to complete the llSGEN

>;
>SET /UIC=[l,l]
>PIP [1,34]*.*/PU/NM
>PIP [l,54]CTDRV.TSK;*/DE/NM,DBDRV.TSK;*,DPDRV.TSK;*,DRDRV.TSK;*
>PIP [l,54]CTDRV.STB;*/DE/NM,DBDRV.STB;*,DPDRV.STB;*,DRDRV.STB;*
>PIP [200,200]SYSGEN2.CMD;*/DE/NM
>PIP /FR
DLO: has 12902. blocks free, 7578. blocks used out of 20480.
Largest contiguous space = 9578. blocks
1343. file headers are free, 193. headers used out of 1536.

>;
>; Create RSX-llS subset system library
>; if you have not already done so.

>*Have you already created llSLIB.OLB? [Y/N]: N
>LBR LB:llSLIB/CR:30.:896.:320.
>REM LBR
>*Have you already built the Exec? [Y/N]: N
>SET /UIC=[l,24]

>;
>; Purge Exec build command files and assembly prefix files

>PIP RSXBLD.CMD/PU/NM
>PIP [11,lO]RSXMC.MAC/PU/NM

>;
>;
>;
>;
>;

Now we build the Executive
If you must make changes to the Executive build files
answer yes to the following question. Edit RSXBLD.CMD
by issuing the command EDI LB:RSXBLD.EMD. 11SGEN2 will
build the Executive after you resume from the pause.

>*Do you wish to edit the Executive build file? [Y/N]: N
>INS SY:$TKB
>TKB @LB:RSXBLD
>* Did the Executive build successfully? [Y/N]: Y

>;
>; You now need the Executive maps to layout
>; the partitions in you new system.

>;
>; Do you have the maps already? [Y/N]: Y

5-13

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>;
>;
>;
>;
>;
>;

Look in the map of the Exec for the symbol "$SYTOP" which
indicates the last address allocated to the Exec. User
partitions may start at any location beyond this address
as long as they fall on a 64 byte boundary. See the RSX-llM
Sysgen manual for a description of how to set up partitions.
You may wish to stop at this time to layout your partitions.

>;
>SET /UIC=[l,64]
>*Do you want to build any loadable drivers now? [Y/NJ:
>SET /UIC=[l,24J
>PIP RSXllS.OBJ;*/DE/NM
>*Have you already built the full duplex terminal driver? [Y/NJ: Y
>*Do you want to continue and build the privileged tasks? [Y/NJ: Y
>OMO DLl:
OMO -- TTO:
dismounted from DLl:
*** Final dismount initiated ***
17:53:06 *** DLl: -- Dismount complete

>;
>; Prepare to assemble and build the RSX-llS privileged
>; software components.

>;
>; The tasks TKTN, BASMCR, OTL, and SIP must be assembled, and the
>;
>;
>;
>;
>;
>;

task build command files possibly edited before they can be built.
The tasks RSDVOS, RSDV52, and RSDVlH need only to be built, but
their command files may also be edited before they are built.
It is not necessary to save/print the assembly listings;
However, we recommand that you save/print the task build
maps. This is especially important when generating
>; an unmapped system -- without maps it will be difficult
>; to determine partition limits.

>*Assembly list device for privileged tasks (DONN:) [D: NL: J [SJ:
>* Map device for privileged tasks (DONN:) [D: SY: J [SJ:
>*Have you already built task TKTN? [Y/NJ: N

>;
>; Task TKTN will be included in your llS system as a result
>; of your selection in llSGEN Phase I.

>;
>;

>;
>;
>;
>;

The privileged tasks BASMCR, OTL, and SIP were specially designed
for use in the RSX-llS environment. Their inclusion in the system
is optional.
If desired, they will be assembled and built under
control of this command file.

>*Do you wish to include BASMCR, OTL, or SIP in your system? [Y/NJ: Y

>;
>;
>;
>;
>;
>;

The tasks RSDV05, RSDV52, and RSDVlH dynamically display
the status of memory on a graphics terminal and can be built
for the VT05B terminal, VT52 terminal, and VTlOO terminal
respectively.
These tasks display which tasks are in memory
and where in memory they reside, which task is currently
running, and the status of pool.

>*Do you want to include RSDVOS, RSDV52, or RSDVlH? [Y/NJ: Y

>;
>;
>;
>;
>;
>;

The RSX-llS subset file control services (FCS) are distributed as a single file containing the concatenated object
modules. They cannot be placed in the RSX-llM system object
library (SYSLIB.OLB).
However, users who require this FCS
should link with the RSX-llS subset of SYSLIB (llSLIB.OLB)
created during this Sysgen.

5-14

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM
>*Do you wish to include the RSX-llS subset FCS? [Y/N]: Y

>; If you have previously done an RSX-llS Sysgen on this disk, all
>;of the files were transferred to the UFO (2,20]. These were
>; optionally deleted by the Sysgen process.
Therefore, unless
>; it was specified to delete the files or they were later
>; deleted independently, there is no need to copy all of the
>; files from the release kit again.

>*Do you have to copy the files from the release kit? [Y/N]: Y
>* Enter device and unit of RSX-1 lS distribution kit (DONN:} [S] : DLl:

>; Place the RSX-llS release kit cartridge disk in drive DLl:

>;
>*Is the disk ready in drive OLl:? [Y/N]: y
>SET /UIC=[2,20]
>INS SY:$UFD
>UFO SY: (2,20]
UFO -- Directory already exists
>REM UFO
>PIP *.*;*/DE/NM
>MOU DLl:llSKIT
>PIP SY:=OLl:
>OMO DLl:
OMO -- TTO:
dismounted from DLl:
*** Final dismount initiated ***
17:57:04 *** DLl: -- Dismount complete
>SET /UIC=[ll,10]
>*Do you wish to make corrections to RSX-llS source modules? [Y/N]:
>INS SY: $MAC
>SET /UIC=[l,24]
>MAC @TKNASM
>PIP TKNASM.CMO;*/DE
>REM MAC

>;
>;
>;
>;
>;

The task build command file for TKTN specifies that it run in
partition SYSPAR, having a length of 3700 octal.
If you must change the partition name or length,
you will have to edit its task build command file.

>;
>*Do you have to edit the task build command file for TKTN? [Y/N]:
>INS SY: $TKB
>TKB @TKNllSBLD.CMD
>REM TKB

>;
>;
>;
>;
>;

BASMCR is a privileged task which supplies a subset (or basic
set} of the RSX-llM MCR commands.
It cannot be included if
during SYSGEN Phase I you indicated that you did not want any
terminal devices.
Its size, depending upon options, ranges
from 6400 to 14000 octal on mapped systems.

>;
>*Do you want to include task BASMCR? [Y/N]: Y
>INS SY: $UFO
>UFD SY: (16, 10]
>UFD SY: (16,24]
>REM UFO
>SET /UIC=[l6,10]
>PIP BMPRE.MAC;*/OE/NM
>PIP *.MAC;*/RM/NM
>PIP (16,*]*.*;*/DE/NM
>PIP [16,10]=[2,20]BMPRE.MAC

5-15

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>PIP [16,10]/EN=[2,20]ABOBAS.MAC,ATLBAS,BRKBAS,ERRBAS,ERRMSG
>PIP [16,10]/EN=[2,20]FMTDV.MAC,FNDUCB,GNBLK,GETNUM,KEYWD
>PIP [16,10]/EN=[2,20]LKLST.MAC,MCRBAS,OPEBAS,PRSBAS,REDBAS
>PIP [16,10]/EN=[2,20]REMBAS.MAC,RPSBAS,RUNBAS,TIMBAS
>SET /UIC=[l6,24]

>;
>;
>;
>;
>;
>;

The size of BASIC MCR is dependent upon the inclusion of
conditional assembly code.
The inclusion of the code is
controlled by symbol definitions appearing in an assembly
prefix file.
The default for these conditionals is
exclusion. The following options, along with the corresponding control symbols, are available:

>;
>;
R$$ATL - ATL/TAL COMMANDS
R$$ERM - ERROR MESSAGE TEXT
>;
>;
R$$0PE - OPEN COMMAND
>;
>; To include an option locate the desired conditional symbol
>; and remove the semicolon at the beginning of the line. For
>; example:
>;
>;
*PL ;R$$ATL
>;
;R$$ATL = 0
;INCLUDE ATL
>;
*C /;//
>;
R$$ATL = 0
;INCLUDE ATL
>;
*
>;
>; Repeat this for all desired options. Note that the symbols
>; appear on consecutive lines in alphabetical order in the file.

>*Do you wish to edit the assembly prefix file for BASMCR? [Y/N]: Y
>EDI [16,lO]BMPRE.MAC
[00029 lines read in]
[Page
l]
*PL ;R$$ATL
;R$$ATL = 0
; INCLUDE ATL
*C /;//
R$$ATL = 0
INCLUDE ATL
*PL ;R$$ERM
;R$$ERM = 0
INCLUDE ERROR MESSAGES
*C /;//
R$$ERM = 0
INCLUDE ERROR MESSAGES
*PL ;R$$0PE
;R$$0PE
0
INCLUDE OPEN
*C /;//
R$$0PE = 0
INCLUDE OPEN
*EX
[Exit]
>INS SY:$MAC
>MAC @BASMCRASM.CMD
>REM MAC
>SET /UIC=[l,24]
>PIP [16,lO]BMPRE.MAC;*/DE/NM
>PIP [16,10]*.MAC;*/RM/NM
>PIP BASMCR.OBJ=[l6,24]*.0BJ
>PIP [16,24]*.*;*/DE/NM
>LBR BASMCR/CR:21.:64.:64.=BASMCR
>PIP BASMCR.OBJ;*/DE/NM

5-16

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>;
>;
>;
>;

The task build command file for BASMCR specifies that it
run in partition MCRPAR, length 16000 octal (mapped).
If you must change the partition name or length,
you will have to edit its task build command file.

>;
>*Do you wish to edit the task build command file for BASMCR? [Y/N]:
>INS SY: $TKB
>TKB @BASMCRBLD.CMD
>REM TKB

>;
>;
>;
>;
>;
>;

OTL is a privileged task which is the RSX-llS on-line task loader.
It performs the install, load, and fix functions for tasks which
were created on a host development system and copied via FLX to a
load medium. Depending on the number of load devices, etc, OTL
ranges from 8000 to 15000 octal on mapped systems.

>* Do you want to include task OTL? [Y/N: Y
>INS SY: $UFO
>UFO SY: [20, 10]
>UFO SY: [20, 24]
>REM UFO
>SET /UIC=[20,10]
>PIP SY:OTLPRE.MAC;*/DE/NM
>PIP SY:*.MAC;*/RM/NM
>PIP [20,*]*.*;*/DE/NM
>PIP [20,10)=[2,20]0TLPRE.MAC
>PIP [20,10]/EN=[2,20]0TL.MAC,OTLCD,OTLCM,OTLERR
>PIP [20,10]/EN=[2,20]0TLHD.MAC,OTLLB,OTLLD,OTLQIO,OTLRD
>SET /UIC=[20,24]

>;
>;
>;
>;
>;
>;
>;
>;
>;

>;
>;
>;
>;
>;
>;

The size of OTL is dependent upon the inclusion of conditional
assembly code.
The inclusion of the code is done in two ways,
by a single symbol definition and by macro calls appearing
in an assembly prefix file.
The first controls the inclusion
of error message text. To include this option, locate the
symbol R$$ERM, and remove the semicolon from the beginning
of the line. The default for error message text is exclusion.
For example:
*PL ;R$$ERM
;R$$ERM=O
*C /;//
R$$ERM=O

>;
>;
>;
>;

The other type of option concerns the exclusion of unwanted
device support. For each of the OTL load devices which
were included in Sysgen Phase I, corresponding support will be
generated in OTL.
Naturally, support will not be generated for
>; those OTL load devices which were not included in SYSGEN Phase I.
>; The following devices along with corresponding control symbols
>; may be supported by OTL:

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

PR:
DX:
DY:
DU:
CT:
DT:
MT:
MS:
MM:
DD:

- PRll, paper tape reader
flexible disk
- RXll,
- RX21, flexible disk
- RXSO, flexible diskette
cassette tape
- TAll,
- TCll, DECtape
- TMll, mag tape
- TSll, mag tape
- TU16, mag tape
- TUSB, cartridge

5-17

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>; To exclude OTL support for a device which has been generated into
>: your RSX-llS Executive, locate the corresponding device symbol
>; and place a semicolon at the beginning of the line. For example:

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

*PL PRll
INCLUD PR11,P$$Rll

;PCll/PRll paper tape reader

INCLUD PR11,P$$Rll

;PCll/PRll paper tape reader

*C //;/
;

*
Perform this for all of the above devices which will be part of
your RSX-llS Executive, but for which you do not want OTL
support. Note that the symbols appear on consecutive lines in
alphabetical order in the file.

>*Do you wish to edit the assembly prefix file for OTL? [Y/N]: Y
>EDI [20,lO]OTLPRE.MAC
(00036 lines read in]
[Page
OJ
*PL ;R$$ERM
[00036 lines read in]
;R$$ERM=O
*C /;//
R$$ERM=O
*EX
[Exit]
>INS SY:$MAC
>MAC @OTLASM.CMD
>REM MAC
>SET /UIC=[l,24)
>PIP [20,lO]OTLPRE.MAC;*/DE/NM
>PIP [20,10)*.MAC;*/RM/NM
>PIP OTL.OBJ=[20,24]*.0BJ
>PIP [20,24)*.*;*/DE/NM
>LBR OTL/CR:21.:128.:64.=0TL
>LBR OTL=[2,20]BLXIOM
>PIP OTL.OBJ;*/DE/NH

>; The task build command file for OTL specifies that it
>; run in partition OTLPAR, length 15000 octal (mapped).
>; If you must change the partition name or length,
>; you will have to edit its task build command file.

>*Do you wish to edit the task build command file for OTL? [Y/N]:
>INS SY:$TKB
>TKB @OTLBLD.CMD
>REM TKB

>; SIP is a privileged task which performs the RSX-llS system
>; image preservation duties.
It replaces the RSX-llM SAV MCR
>; command. Depending on the number of load devices, etc, SIP
>; ranges from 3700 to 7400 octal on mapped systems.

>*Do you want to include task SIP? [Y/N]: Y
>INS SY:$UFD
>UFD SY:[21,10]
>UFO SY: [21,24)
>REM UFO
>SET /UIC=[21,10]
>PIP SY:SIPPRE.MAC;*/DE/NM
>PIP SY:*.MAC;*/RM/NM
>PIP [21,*]*.*;*/DE/NM

5-18

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>PIP [21,10]=[2,20]SIPPRE.MAC
>PIP [21,10]/EN=[2,20]SIP.MAC,SIPBOO,SIPCD,SIPERR
>PIP [21,10]/EN=[2,20]SIPLD.MAC,SIPQIO
>SET /UIC=[21,24]

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

>;
>;
>;
>;
>;
>;
>;

The size of SIP is dependent upon conditional assembly code
in exactly the same manner as OTL. There are only a few minor
differences.
OTL supports the paper tape reader using the
control symbol PRll; SIP on the other hand supports the paper
tape punch using the control symbol PPll.
In addition, OTL
supports DECtape II cartridges using control symbol TU58,
TSll magnetic tape drives using the control symbol TSll
and RXSO flexible diskettes using the control symbol RXSO.
Edit SIPPRE.MAC in the same way described for OTL. For example:
*PL PPll
INCLUD PP11,P$$Pll

;PCll/PPll paper tape punch

INCLUD PP11,P$$Pll

;PCll/PPll paper tape punch

*C //;/
;

>* Do you wish to edit the assembly prefix file for SIP? [Y/N]: Y
>EDI (21,lO]SIPPRE.MAC
(00036 lines read in]
[Page
OJ
*PL ;R$$ERM
(00036 lines read in]
;R$$ERM=O
*C /;//
R$$ERM=O
*EX
[Exit]
>INS SY:$MAC
>MAC @SIPASM.CMD
>REM MAC
>SET /UIC=[l,24)
>PIP (21,lO]SIPPRE.MAC;*/DE/NM
>PIP [21,10)*.MAC;/RM/NM
>PIP SIP.OBJ=[21,24]*.0BJ
>PIP [21,24)*.*;*/DE/NM
>LBR SIP/CR:20.:64.:64.=SIP
>PIP SIP.OBJ;*/DE/NM

>;
>; The task build command file for SIP specifies that it
>;run in partition SIPPAR, length 7400 octal (mapped).
>; If you must change the partition name or length,
>; you will have to edit its task build command file.

>*Do you wish to edit the task build command file for SIP? [Y/N):
>INS SY:$TKB
>TKB @SIPBLD.CMD
>REM TKB
>SET /UIC=[l,24)
>PIP RMD.OLB/NV=[2,20]RMDMAP.OLB
>*Do you want to include task RSDVOS? [Y/N]:
>*Do you want to include task RSDV52? [Y/N]:
>*Do you want to include task RSDVlH? [Y/N]: Y

>;
>;
>;
>;
>;

The task build command file for RSDVlH specifies that it
run in partition RSDVlH, length 40000 (octal).
If you must change the partition name or length, you
will have to edit the task build command file.

5-19

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

>; Do you wish to edit the task build command file for RSDVlH? [Y/N]:
>INS SY:$TKB
>TKB @RSDVlHBLD.CMD
>REM TKB

>;
>; Add subset FCS to the RSX-llS system object library.

>;
>SET /UIC=[l,l]
>LBR LB:llSLIB/RP=[2,20]FCSllS
>PIP LB:llSLIB.OLB/PU/NM
>SET /UIC=[l,64)
>PIP *.*/PU/NM
>PIP [l,24)*.*/PU/NM

>;
>; The operation left to be performed is that of the final
>; configuration of the virgin executive using Virtual MCR.

>;
>*Do you want to configure the Exec at this time using VMR? [Y/N]: Y

>;
>;
>;
>;
>;
>;

The contents of your RSX-llS release kit currently resides
under the UFO [2,20).
If your SY: disk is not an RK06/07 or an
RP04/05/06 you may want to delete these files.
Leaving
them on the disk will save the time of re-copying them the next
time you perform an RSX-llS Sysgen.

>;
>*Do you want to delete the RSX-llS kit from this disk? [Y/N]:

>; We will now make a copy of your target system

>;
>PIP RSX11S.SYS/NV/CO/BL:498.=RSX11S.TSK

>; If you wish to make a copy of your task or system image file
>; on another device we will pause to allow you to do so.

>*Do you wish to copy your system to another device? [Y/N]:

>;
>; RSXllS.TSK is a backup copy of the llS system you have just built.
>; If you do not wish to retain it, we will delete it now.

>*Do you wish to delete the system backup file RSXllS.TSK? [Y/N]:

>;
>; Your target system is now ready to set up partitions and install
>; the required tasks.
The procedure to follow is:
>;
1) Run Virtual MCR
>;
2) Extend POOl space to base of first partition
3) Set up your partitions
>;
>;
3B) Load needed drivers
>;
3C) Set up a partition for the Directive Common
>;
4) Install tasks (BASMCR, OTL, SIP, TKTN)
>;
5) Fix tasks into (virtual) memory
>;
6) Optionally set the time and save a copy of THE
>;
system on a bootable medium
>;
7) Exit from virtual MCR and boot in your target system

>; VMR example:

>;
>;
>;
>;
>;
>;
>;
>;
>;

>VMR
RUN VIRTUAL MCR
ENTER FILENAME:RSXllS.SYS
! VMR PROMPTS FOR FILE NAME
VMR>SET /POOL=XXX
EXTEND POOL TO FIRST PARTITION BASE
VMR>SET /MAIN=TTPAR:XXX:XXX:TASK !SET UP FULL DUPLEX TT PARTITION
VMR>SET /MAIN=DRVPAR:XXX:XXX:TASK ! SET UP DRIVER PARTITION
VMR>SET /MAIN=EXC0Ml:XXX:200:COM ! SET lST EXEC. COMMON
VMR>INS EXCOMl
!INSTALL lST EXECUTIVE COMMON
VMR>SET /MAIN=EXCOM2:XXX:200:COM ! SET 2ND EXEC. COMMON

5-20

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

>;
>;
>;
>;
>;

VMR>INS EXCOM2
!INSTALL 2ND EXECUTIVE COMMON
SET UP TKTN PARTITION
VMR>SET /MAIN=SYSPAR:XXX:XXX:TASK
VMR>SET /MAIN=MCRPAR:XXX:XXX:TASK
SET UP MCR PARTITION
SET UP OTL PARTITION
VMR>SET /MAIN=OTLPAR:XXX:XXX:TASK
VMR>SET /MAIN=SIPPAR:XXX:XXX:TASK
SET UP SIP PARTITION
VMR>SET /MAIN=GEN:XXX:XXX:SYS ! IF SYSTEM CONTROLLED PAR.
VMR>SET /MAIN=GEN:XXX:XXX:TASK ! IF USER CONTROLLED PARTITION
LOAD XXDRV
VMR>LOA XX:
VMR>INS TKN/FIX=YES
INSTALL TASK TERMINATION TASK
INSTALL BASIC MCR
VMR>INS BASMCR/FIX=YES
VMR>INS OTL/FIX=YES
INSTALL ONLINE TASK LOADER
INSTALL SYSTEM PRESERVATION TASK
VMR>INS SIP/FIX=YES
VMR>TIM 10:45 05/30/85
SET TIME AND DATE
SAVE SYSTEM ON RXOl FLOPPY
VMR>SAV DX:RSXllS
VMR>""Z
EXIT FROM VIRTUAL MCR

>; End of VMR example

>;
>;
>;
>; Now we will run Virtual MCR so that you may initialize
>;
>;
>;
>;
>;
>;
>;

>;
>;
>;
>;
>;
>;
>;
>;
>;

your system. Be sure to define all required partitions
at this time, because the SET function is not supported
in RSX-llS BASIC MCR. Furthermore, if you plan to
include BASIC MCR and OTL in your system, they must
be installed and fixed into memory. Other tasks,
such as SIP and TKTN may be loaded into a running
RSX-llS system using OTL.
NOTE: Since LOAD and UNLOAD are not supported on
a running RSX-llS system, all required loadable
drivers must be loaded using VMR.

NOTE: You have requested to include the
directive common. You must install the
common prior to exiting Virtual MCR
or your RSX-llS system will not boot.
>INS SY:$VMR
>VMR
Enter filename: RSXllS
VMR>SET /POOL=*
VMR>SET /MAIN=TTPAR:*:400:TASK
VMR>LOA TT:
VMR -- *DIAG*-Loadable driver larger than 4K
VMR>SET /MAIN=DRVPAR:*:*:SYS
VMR>LOA DD:
VMR>LOA DL:
VMR>LOA LP:
VMR>SET /TOP=DRVPAR:-*
VMR -- *DIAG*-Installed tasks may no longer fit in partition
VMR>SET /MAIN=EXCOM1:*:200:COM
VMR>INS EXCOMl
VMR -- *DIAG*-Partition reduced to executive common size
VMR>SET /MAIN=EXCOM2:*:200:COM
VMR>INS EXCOM2
VMR -- *DIAG*-Partition reduced to executive common size
VMR>SET /MAIN=SYSPAR:*:lOl:TASK
VMR>SET /MAIN=MCRPAR:*:l37:TASK
VMR>SET /MAIN=OTLPAR:*:l50:TASK
VMR>SET /MAIN=SIPPAR:*:74:TASK
VMR>SET /MAIN=RSDV1H:*:400:TASK
VMR>SET /MAIN=GEN:*:*:SYS
VMR>INS TKN/FIX=YES
VMR>INS BASMCR/FIX=YES
VMR>INS OTL/FIX=YES
VMR>INS SIP/FIX=YES

5-21

RSX-llS SYSTEM GENERATION ON AN RSX-llM HOST SYSTEM

VMR>INS RSDVlH/FIX=YES
VMR>REA RSDVlH 1 TTl:
VMR>REA RSDVlH 2 TTl:
VMR>SAV DDl: llS
VMR -- *DIAG*-saved system truncated to 492. blocks
VMR>"'Z
;

>;
>; When this command file completes, your RSX-llS system is
>; ready to run.

>;
>REM VMR
>SET /UIC=[200,200]
>TIM
11:17:10 30-MAY-85

>;
>@ <EOF>

5-22

CHAPTER 6
RSX-llS SYSTEM GENERATION ON AN RSX-llM-PLUS HOST SYSTEM

This chapter explains how
RSX-llM-PLUS host system.

6.1

generate

RSX-llS

PERFORMING AN RSX-llS SYSTEM GENERATION ON AN
SYSTEM

system

RSX-llM-PLUS

HOST

Performing the RSX-llS system generation on an RSX-llM-PLUS host
requires an that RSX-llS distribution kit be contained on one of the
following medium:

RK06

RK07

•

RLOl (two disks)

RL02

TK50

•

Magnetic tape

In addition, you will need
RSX-llS system generation.

another

disk

which

perform

the

During the system generation process, a number of files will be
transferred to this disk. The disk must have approximately 8000 free
blocks to accommodate these files and the system generation of the
target system.
You can perform an RSX-llS system generation on the host system disk
or on another disk. If you use the host system disk, you can select
group numbers during the system generation procedure for the RSX-llS
system and Executive files.
This will ensure that the group numbers
will not conflict with the files already on the disk. The valid group
numbers you may select are 3 through 10. The default group number is
3.

You may also select the group numbers if you use a disk other than the
host system disk.
However, the valid group numbers are 1 through 10
for the system files (1 is the default) and 1 through 11 for Executive
files (11 is the default).

6-1

RSX-llS SYSTEM GENERATION ON AN RSX-llM-PLUS HOST SYSTEM
If you select alternate group numbers for the system and Executive
files, note that you must specify the User File Directory {UFO) in the
command line. This must be done whenever you want to use such files
as the system object library {SYSLIB.OLB) or the system macro library
(RSXMAC.SML). Normally, the Task Builder
(TKB)
and the MACR0-11
assembler expect to find these libraries in UFO [1,1]. Refer to
Section 4.1 for more information.
If you generate more than one RSX-llS system on the same target disk
by specifying additional system and Executive group numbers, be sure
that the disk has enough free blocks on it to contain each additional
RSX-llS
SYSGEN.
Each additional RSX-llS system generation is
segregated from the previous SYSGEN(s).
A complete RSX-llS system generation is performed in two phases on an
RSX-llM-PLUS host.
The procedure is controlled by the indirect
command files,
llSGEN.CMD and 11SGEN2.CMD, which reside on the
distribution media.
In the first phase, the procedures are controlled
by the command file llSGEN.CMD and are primarily the same as those
followed for generating an RSX-llM system.
(Consult the RSX-llM
S*stem Generation and Installation Guide for a detailed description of
P ase I of the --SVSGEN command procedure.) The second phase of the
RSX-llS system generation is controlled by
the
command
file
11SGEN2.CMD.
Because the RSX-llS system generation programs,
llSGEN and 11SGEN2,
expect to find the files llSGEN.CMD and 11SGEN2.CMD in UFO [2,200] on
your target disk, you must copy them as described in Sections 6.1.1
and 6.1.3.
The following
llSGEN.CMD:

operations

are

performed

•

Prompting for the Executive options

•

Assembling the Executive

•

Assembling the drivers

The following
11SGEN2.CMD:

operations

are

performed

during

the

processing

during

the

processing

•

Building the target Executive and the drivers

•

Assembling (building) the RSX-llS system tasks

•

Final configuration of
image)

the

Executive

(creating

the

system

The Phase II operations are discussed in Chapter 4.

6.1.1

Copying Procedures

Your distribution kit (labeled, "llSKIT") contains a file that must be
copied before you can perform the system generation. You should copy
the file, [2,20]11SGEN.CMD, to UFO [2,200] on the disk upon which the
system generation is to be performed.
If your distribution kit is on
disk(s), use the PIP Utility to copy the files.
For example,
>PIP TI:=ddnn: [2,200]11SGEN.CMD

6-2

RSX-llS SYSTEM GENERATION ON AN RSX-llM-PLUS HOST SYSTEM
If your kit is on magnetic tape(s), you can use the FLX Utility.
example,

For

>FLX ddnn:[2,200]=mmnn: [2,20]11SGEN.CMD
NOTE
If you have an RLOl (a two-volume) distribution kit,
the command files are on the volume labeled, "llSKIT".
All other files that are required for the system generation will be
copied to your target disk by the procedure llSCOPY.CMD. This
procedure is invoked by llSGEN.
The file-copying process takes
approximately 60 to 90 minutes.

6.1.2

Invoking the System Generation Programs

Type the following command to invoke the
programs:

Phase

system

generation

system

generation

Generation

>@llSGEN.CMD
Type the following command to invoke the Phase
programs:
>@11SGEN2.CMD

6.1.3

Notes for RSX-llS
RSX-llM-PLUS Host

Version

4.2

System

This section contains information you should consider before you begin
the system generation process.
1.

Copy llSGEN.CMO from UFD [2,20] on the distribution media
UFO (2,200] on the target disk.

Assign SY:

Always perform the RSX-llS system generation with the command
files in UFO (2,200].

Install the following tasks:
PIP
UFO
EDI

to the target device (ASN ddnn:=SY:).

LBR
MOU
OMO

FLX

LOA
UNL
TKB

INI

MAC

privileged

tasks

are

not

Listing
(. LST)
files
automatically deleted.

The RSX-llM VMR is used for generating the RSX-llS system on
an RSX-llM-PLUS host system. It is installed and run under
the name VMM, but it still prompts with VMR>.

The RSX-llM Task Builder is used to build the RSX-llS tasks
on an RSX-llM-PLUS host system.
It is installed and run
under the name TKM, and it prompts with TKM>.

6-3

RSX-llS SYSTEM GENERATION ON AN RSX-llM-PLUS HOST SYSTEM
8.

If you are planning to save the target system (using VMR
SAVE)
to some device, MOUNT the device with the FOREIGN
keyword (/FOR) before beginning the system generation.

You may want to do a preliminary system generation before you
do your actual SYSGEN. To do a preliminary SYSGEN {PREPGEN),
invoke the command file for Phase I of the SYSGEN {@llSGEN)
and answer YES to the question,
"Do you want to inhibit
execution of MCR commands (PREPGEN)?"
Phase I continues, but the answers you give to the questions
are placed in a saved answer file instead of being used
immediately. When Phase I finishes, reinvoke llSGEN.CMD to
run the phase again. This time, do not inhibit MCR command
line execution; the SYSGEN procedure uses the answers in the
saved answer file.
Doing a PREPGEN will save time and
prevents mistakes.

10.

During Phase I of the system generation procedure, llSGEN.CMD
asks for your systems's device configuration and requests the
system directives you would like in the Executive.
In both
cases, you may print out a table of the available options
before you answer the question.

For further information on generating the
Chapter 4.

6.2

RSX-llS

system,

refer

SYSGEN DIALOG ON AN RSX-llM-PLUS HOST SYSTEM

The dialog for an RSX-llS system generation on an RSX-llM-PLUS host
system is very similar to that of an RSX-llS system generation on an
RSX-llM host.
The primary differences are as follows:
You must use the MCR command line interpreter.
• command
to set your terminal to MCR.)
SET /MCR=TI:

(Use

•

(Use the

You must set your default to nonamed directory mode.
command SET /NONAMED to set your default.)

Examine the example of the RSX-llS system
host system in Chapter 5.

generation

the

RSX-llM

Additionally, the dialog and procedures in Phase I are the same as
those for an RSX-llM system generation. For detailed explanations of
the Phase I system generation questions, see the RSX-llM System
Generation and Installation Guide.

6-4

CHAPTER 7
RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

This chapter explains how to generate an RSX-llS system on a VAX/VMS
host system.
It also contains an example of a typical terminal dialog
from an RSX-llS system generation on a VAX/VMS host system.

7.1

PERFORMING AN RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

RSX-llS Version 4.2 is available on the following distribution
for VAX/VMS host systems:
•

Magnetic tape

•

RK07 disk cartridge

•

RL02 disk cartridge

VAX/VMS uses RSX-llM indirect command files
target system.

generate

medium

RSX-llS

NOTE
In order for you to perform an RSX-llS
system
generation on a host VAX/VMS Version 4.0 (or later)
system, VAX-11 RSX must be installed. See the VAX-11
RSX Installation Guide and Release Notes for more
information.
This section explains how to perform
the
system
Subsequent sections detail the following information:

generation.

•

Section 7.1.1 describes the privileges you must have to set up
and run the system generation.

•

Section 7.1.2 describes the procedure for beginning the system
generation.

•

Section 7.1.3 contains additional information about performing
the RSX-llS system generation.

•

Section 7.2 contains the text of a typical dialog
RSX-llS system generation on a VAX/VMS host system.

7-1

from

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

You can perform an RSX-llS system generation on the host system disk
or on another disk.
If you use the host system disk, you can select
group numbers during the system generation procedure for the RSX-llS
system and Executive files so that they will not conflict with files
already on the disk. The valid group numbers you may select are 3
through 10. The default group number is 3.
You may also select the group numbers, provided that you use a disk
other than the host system disk.
In this case, the valid group
numbers are 1 through 10 for the system files (1 is the default) and 1
through 11 for the Executive files (11 is the default).
If you select alternate group numbers for the system and Executive
files, note that you must specify the User File Directory (UFO) in the
command line whenever you want to use such files as the system object
library
(SYSLIB.OLB) or the system macro library
(RSXMAC.SML).
Normally, the Task Builder and the MACR0-11 Assembler expect to find
these libraries in UFO [1,1]. See Section 4.4 for more information.
If you generate more than one RSX-llS system on the same target disk
by specifying additional system and Executive group numbers, the disk
must have enough free blocks on it to contain each additional RSX-llS
SYSGEN.
Each additional RSX-llS system generation is segregated from
the previous SYSGEN(s).
You must have a command line interpreter
(CL!)
symbol table of at
least 40 pages to perform an RSX-llS system generation on a VAX/VMS
system.
Because the table is established when the system
is
bootstrapped, you must rebootstrap the system to set a new symbol
table space if it is not already adequate.
Determine your current
symbol table size by running the VAX/VMS SYSGEN Utility. To increase
the symbol table space, run VAX/VMS SYSGEN to set a new value for the
CLISYMTBL parameter and then rebootstrap the system (see the VAX-11
Software Installation Guide). For example:
Username:
Password:

SYSTEM/CLI=MCR

> RUN SYS$SYSTEM:SYSGEN
SYSGEN> SHOW CLISYMTBL
Parameter Name
CLISYMTBL
SYSGEN> SET CLISYMTBL 40
SYSGEN> SHOW CLISYMBTL
Parameter Name
CLISYMTBL
SYSGEN> WRITE CURRENT
SYSGEN> EXIT

Current

Default

Minimum

Maximum Unit

Dynamic

128 Pages

-------

Current

Default

Minimum

-------

Maximum Unit

------128

Pages~

-------

Dynamic

-------

The numbers shown in the CL! symbol table are the current number of
pages, the default number, the minimum number, and the maximum number.
After you have made the desired changes to the symbol table,
rebootstrap the system, and log in on the system again.
NOTE
If you are generating an RSX-llS operating system on a
VAX/VMS
(Version 3.0 or later) operating system, you
do not have to increase the CLISYMTBL space.

7-2

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
Note that the VAX/VMS version of the RSX-llM Task
image files whose file extension type is .EXE.

Builder

produces

If you wish to build a task on a VAX/VMS system with the On-Line
Debugging Tool
(ODT), you must include ODT/DA on the input file side
of the task-build command line. You must include the debugging switch
with the ODT file name and you must have the terminal included in your
RSX-llS system. The following command line shows how to include ODT
for an RSX-llS task built under a VAX/VMS system:
MCR>TKB TEST=[g,l]ODT/DA,TEST
NOTE
Normally, the ODT object file
(ODT.OBJ)
is on the
target system disk in UFO [1,1].
If during the system
generation, however, you selected an alternate group
number for the system files, you must specify this
group number (g) in the TKB command line.

7.1.1

Establishing VAX/VMS Privileges

You must be logged in to a VAX/VMS system and have certain privileges
in order to set up and run the RSX-llS system generation. If you
perform the system generation from the system manager's account that
is distributed with the VAX/VMS system (as long as its privileges have
not been altered), you will have access to the following required
privileges:
•

System Protection Privilege
(SYSPRV), which allows you to
create files in directories not owned by the current UIC.
(You must set this privilege before you can set the ·remaining
privileges.)

•

Change Mode to Kernel Privilege (CMKRNL), which allows you
change default UICs and directories.

Logical I/O Privilege (LOG IO), which permits RSX-llM
do logical I/O on task image files.

VMR

Protection Override Privilege (VOLPRO), which is
• Volume
only with an RSX-llS magnetic tape distribution kit.
privilege allows you to
/FOREIGN qualifier.

mount

the

magnetic

If you have the SETPRV privilege, you can
privileges with the following MCR command:

establish

tape

used
This
with the

the

required

>SET PROCESS/PRIVILEGE=(privilege[, ••• ])
Specify the following MCR command lines to find
you have:

out

what

privileges

> SHOW PROCESS/PRIVILEGE
You should have CMKRNL, LOG IO, VOLPRO, and SYSPRV (the privileges
described in the previous bulleted list).
These privileges are
described in the VAX/VMS System Manager's Guide.

7-3

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
7.1.2

Copying and Invoking the RSX-llS System Generation Programs

The following steps enable you to begin an RSX-llS system generation
on a VAX/VMS host system. After you log in on the system and mount
the RSX-llS distribution kit, you can proceed with the RSX-llS system
generation.
If your distribution kit is on disk, use the following steps:
1.

Log in on the VAX/VMS system with the /CLI=MCR qualifier so
that you can use MCR, which is the required command line
interpreter (CL!) for the RSX-llS system generation.
Username:
Password:

SYSTEM/CLI=MCR

Set up the required privileges as described in Section 7.1.1

Mount the RSX-llS distribution kit.
> MOUNT ddnn:

llSKIT

Set your default disk and User Identification Code
[2,200] on the target disk.

(UIC)

Copy [2,20]11SGEN.CMD from the llSKIT distribution medium
UFO [2,200] on your target disk.

> SET DEFAULT ddnn:
>SET /UIC=[2,200]
5.

Create the UFO on your target disk.
> UFO ddnn: [2,200]

> PIP ddnn:/NV=ddnn: [2,20]11SGEN.CMD
7.

Dismount the distribution kit.

> OMO ddnn:/NOUNLOAD
8.

Make sure your UIC is set to [2,200] and execute the
system generation procedure.

RSX-llS

> SHOW DEFAULT

> @llSGEN
If your distribution kit is on magnetic tape, use the following steps:
1.

Log in on the VAX/VMS system with the /CLI=MCR qualifier so
that you can use MCR, which is the required command line
interpreter (CLI) for the RSX-llS system generation.
Username:
Password:

SYSTEM/CLI=MCR

Set up the required privileges as described in Section 7.1.

Mount the RSX-llS distribution kit as foreign.

> MOUNT mmnn:/FOR

7-4

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
4.

Mount the target disk.
> MOUNT ddnn: volume-name

Set your default UFO on the target disk to be [2,200].
> SET DEFAULT ddnn:
> SET /UIC=[2,200]

Create the UFO on your target disk.
> UFO ddnn: [2,200]

Copy [2,20]11SGEN.CMD from the
[2,200] on your target disk.

distribution

medium

UFO

> FLX ddnn:/RS=mmnn: [2,20]11SGEN.CMD/DNS:l600/DO/RW

Dismount the distribution kit.
OMO mmnn:/NOUNLOAD
(Specifying the /NOUNLOAD keyword allows you to dismount
remount the tape without having to reload it.)

Make sure your UIC is set to [2,200] and execute the
system generation procedure.

and

RSX-llS

> SHOW DEFAULT

> @llSGEN
All the files needed for the system generation are copied to
target
disk by llSCOPY.CMD, which lS invoked by llSGEN.
file-copying process takes approximately 20 minutes.

the
The

Note that to save a bootable RSX-llS system image onto the system
console device, you must use the device name CS:. To put the console
device on line (if it currently is not), specify the following:
$ SET PROCESS/PRIVILEGE=CMKRNL
$ MCR SYSGEN
SYSGEN>CON CON
Following is an example showing how to save the RSX-llS
on the console device:

system

image

VMR> tBm
ENTER FILENAME:
<filename>
VMR>SAVE CS:label
VMR is documented in the RSX-llM/M-PLUS System Management Guide.

7.1.3

Notes for the RSX-llS System Generation on a VAX/VMS Host

This section contains information you should consider before you begin
the system generation process.
1.

If you have disk quota checking on your SYS$LOGIN device
(your work disk), it must be disabled before you begin your
RSX-llS system generation. This is because the compatibility

7-5

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
mode task, MAC, needs to create temporary work files in UICs
that probably do not have an established disk quota on
SYS$LOGIN. Otherwise, MAC cannot assemble any files during
the system generation.
To disable disk quota checking, invoke the Disk Quota Utility
(DISKQOUTA) by issuing the following command line:
$ RUN SYS$SYSTEM:DISKQUOTA

When the DISKQUOTA prompt appears on your terminal, issue the
following command lines:
DISKQ>USE diskname:
DISKQ>DISABLE ~
DISKQ> (CTRL/Z)
$
Diskname:

is the name of the SYS$LOGIN device.

Now disk quota checking is disabled and
begin your RSX-llS system generation.
2.

you

are

ready

You may want to do a preliminary system generation before you
do your actual SYSGEN. To do a preliminary SYSGEN (PREPGEN),
invoke the command file for Phase I of the SYSGEN
(@llSGEN)
and answer YES to the question,
"Do you want to inhibit
execution of MCR commands (PREPGEN)?"
Phase I continues, but the answers you give to the questions
are placed in a saved answer file instead of being used
immediately. When Phase I finishes, reinvoke llSGEN.CMD to
run the phase again.
This time, do not inhibit MCR command
line execution; the SYSGEN procedure uses the answers in the
saved answer file.
Doing a PREPGEN saves time and prevents mistakes.
The sample
dialog shows a PREPGEN being done before the actual SYSGEN.

7.2

During Phase I of the system generation procedure, llSGEN.CMD
asks for your system's device configuration,
the system
directives you would like in the Executive, and the type of
terminal driver you want to use.
For these questions, you
can print out a table of the available options before you
answer the question.

During Phase I, you can also select different group numbers
for the system and Executive files.
In the sample SYSGEN,
group number 3 is selected for the system files and group
number 10 for the Executive files.
(The default group
numbers are 1 and 11, respectively.)

SYSGEN DIALOG ON A VAX/VMS HOST SYSTEM

This section contains an example of the text of a typical terminal
dialog from an RSX-llS system generation on a VAX/VMS host system.
The dialog and procedures in Phase I are the same as those for an
RSX-llM host.
For detailed explanations of the Phase I system
Generation
and
System
generation questions, see the
RSX-llM
Installation Guide.

7-6

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
The system generated in the example supports
configuration for a PDP-11/84 processor:

the

following

hardware

128K memory
cycle line clock
60
RP06 disk controller with 1 drive
1
1
RL02 cartridge disk controller with 2 drives
RC25 cartridge disk controller with 2 drives
1
1
TE16 magnetic tape controller with 1 drive
null device driver
1
1
DLll terminal interface
The following software support is included:
•

Large (20K) RSX-llS Executive

•

Support for:
Memory parity support
Cache memory
Executive common
Memory management directives
Send/receive-by-reference directives
Get mapping context directive
Address checking
I/O rundown
Loadable device drivers
AS Ts
Cancel selective marktime
Powerfail recovery
Logical device assignment
System-controlled partitions
Group-global event flags

TKTN

•

Full-duplex terminal driver

•

Basic MCR with support for the OPEN and ATL/TAL
full error-message text

•

OTL with support for full error-message text and for
devices generated into the RSX-llS system

all

OTL

•

SIP with support for full error-message text and for
devices generated into the RSX-llS system

all

SIP

•

CDA for crash dump analysis on the host system

•

RSX-llS File Control Services (FCS) subset

SETTIM

commands

and

The system generation is being performed on a VAX/VMS host system with
an RK07 as the target disk. The RSX-llS release kit is a 2400-foot
magnetic tape.
Questions calling for a YES/NO answer can be answered by pressing
RETURN key for a "NO" answer.
(This is the default answer.)

the

By pressing the RETURN key, you may specify the default answer to a
question that asks for a value. This default value is displayed on
the terminal screen.

7-7

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

7.3

EXAMPLE OF AN RSX-llS SYSTEM GENERATION DIALOG ON A VAX/VMS
SYSTEM

HOST

Following is the actual dialog from an RSX-llS system generation on
VAX/VMS Version 4.0 host system.
Username: SWABODA/CLI=MCR
Password:
Welcome to VAX/VMS Version V4.0
> SET PROC/PRIV={SYSPRV,CMKRNL,LOG IO,VOLPRO)
> MOU MTO:/FOR
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, mounted on MTAO:
> ALL DMO:
%MCR-I-ALLOC, DMAO: allocated
> INI DMO: llSDSK/STRUCTURE=l
> MOU DMO: llSDSK
%MOUNT-I-MOUNTED, llSDSK
mounted on DMAO:
> SET DEFAULT DMO:
> SET /UIC=[2,200]
> UFD DMO: [2,200]
> FLX DMO:/RS=MTO: [2,20]11SGEN.CMD/DNS:l600/DO/RW
> DMO MTO:/NOUNLOAD
> SH DEF
DMO: [2, 200J
> @llSGEN

>;
>; RSX-llS Version 4.2 BL38 System Generation done on VAX/VMS

>;
>;
>; RSX-llS system generation set-up section

>;
>; The system device is the disk on which all of the host's, VAX/VMS,
>; system files are stored. If your llS target disk is the system device
>; then there may possibly be a conflict in some file names (e.g., SYSLIB).

>;
>*Is the target disk, $$0:, the system device? [Y/NJ: N
>*What is the group number for the system files [O R:l-10 D:l]:
>*What is the group number for the executive files [O R:l-11 D:llJ:
>*Target device name [SJ: DMO:
>SET DEFAULT DMO:
>ASN DMO:=SY:
>ASN OMO:=SYO:
>ASN OMO:=LB:
>ASN OMO: =LBO:
>ASN MP:=MPO:
>ASN TK:=TKO:
>ASN OMO: [l,54]11MTKB.TSK=TKB
>ASN OMO: [l,54JllMVMR.TSK=VMR
>ASN OMO: =WK:
>ASN OMO:=WKO:
,
>*Copy the Rsx~11s distribution files to the target disk? [Y/NJ: Y
>*Enter device for the RSX-llS distribution kit [SJ: MTO:

>
>

Place the TAPE labeled llSKIT on MTO:
Is the TAPE ready on MTO:? [Y/NJ: Y

7-8

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

>MOU MT 0 : /FOR
%MOUNT-I-WRITELOCK, volwne is write locked
%MOUNT-I-MOUNTED, mounted on MTAO:
>FLX DMO:/RS=MT0:[200,200]11SCOPY.CMD/DO/RW/DNS:l600
>UFO SY: [1,1)
>UFO SY: [1,2]
>UFO SY: [1,4]
>UFO SY: [2,20)
>UFO SY: [l,54]
>UFO SY: [1,60]
>UFO SY: [1,64]
>UFO SY: [ 1, 20]
>UFO SY: [ 1, 24)
>UFO SY: [11, 20]
>UFO SY: [11,24]
>UFO SY: [l,30)
>UFO SY: [1,34)
>UFO SY: [11, 30]
>UFO SY: [11,34)
>UFO SY: [12,20)
>UFO SY:[l2,24]
>UFO SY: [45, 10)
>UFO SY: [45,20]
>UFO SY: [45, 24)
>UFO SY: [45,30)
>UFO SY: [45, 34)
>UFO SY: [11,10)
>PIP [l,l]EXEMC.*;*/DE/NM,EXELIB.OLB;*,EXEUTL.OBJ;*,UCTDF.OBJ;*
>PIP [l,l]DIRSYH.OBJ;*/DE/NH,GCML.OBJ;*,ARITH.OBJ;*,ODT.OBJ;*
>PIP [l,l]LPA.OBJ;*/DE/NM,RSXMAC.SML;*,FCSRES.MAC;*
>PIP [l,l]PURUDC.OBJ;*/DE/NM,PURISA.OBJ;*,PURICR.OBJ;*,PURPCS.OBJ;*,LPS.OBJ;*
>PIP /FR
LBO: has 52702. blocks free, 1088. blocks used out of 53790.
Largest contiguous space = 26837. blocks
13417. file headers are free, 30. headers used out of 13447.
>FLX [2,200]=HTO: [200,200]*.*,[2,20]11SGEN2.CMD/DNS:l600
>FLX [2,20]=HT0:[2,20]*.*/DNS:l600
>PIP [2,20]11SGEN.CHD;*/DE/NH,llSGEN2.CMD;*
>FLX [l,l]=MTO: [l,l]*.*/DNS:l600
>FLX [l,20]=MTO: [l,20]*.*/DNS:l600
>FLX [l,24]=MTO: [l,24]*.*/DNS:l600
>FLX [l,54]/CO/BL:l80.=MTO: [l,54]11HVMR.TSK/DNS:l600
>FLX [l,54]/CO/BL:l80.=MTO:[l,54]11MTKB.TSK/DNS:l600
>PIP [l,54]11HVMR.TSK/PU/NM,11MTKB
>FLX [11,lO]=MTO: [ll,10]*.*/DNS:l600
>FLX [45,lO]=HTO: [45,10]*.*/DNS:l600
>FLX [45,20]=MTO: [45,20]*.*/DNS:l600
>FLX [45,24]=HTO: [45,24]*.*/DNS:1600
>PIP [1,20)*.*/PU/NM,[1,24]*.*
>PIP [2~20]*.*/PU/NM,[45,10)*.*,[45,20]*.*,{45,24]*.*
>PIP /FR
LBO: has 43411. blocks free, 10379. blocks used out of 53790.
Largest contiguous space = 26837. blocks
13123. file headers are free, 324. headers used out of 13447.

>;
>; Distribution kit copy is now complete

>;
>OMO MTO:

>;
>; You may now remove your

di~tribution

kit from drive MTO:.

7-9

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
>SET /UIC=[2,200]

>;
>; Big disk distribution kit
>;
>* 3. Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/N]: Y
>* 5. Are you generating an unmapped system? [Y/N]: N
>* 6. Use an input saved answer file? [Y/N]: N
>* 9. Name of output saved answer file [D: SYSSAVED.CMD] [S]:
>;
>; Phase I output saved answers created in file $$0: [2,200]SYSSAVED.CMD;l
>;
>;
>; Target configuration
>;
>* 1. Processor Type [D: 11/34] [SJ: 11/84
>* 3. Memory size (in K-word blocks) [D R:32.-1920. 0:32.): 256.
>* 4. Include support for K-series devices? [Y/N D:N]:
>* 6. Floating point processor (FP-11) present? [Y/N D:N]: Y
>* 8. Extended instruction set (EIS) present? [Y/N D:N]: Y
>* 9. If using KWll-P as system clock: number of intrps./sec. [D R:0.-1000. D:O.]:
>* 10. Line frequency:
A- 60 Hz
B- 50 Hz
[D: A] [S]:
>* 11. KWll-Y Watchdog timer support? [Y/N D:N]:
>* 12. Memory parity support? [Y/N D:N]: Y
>* 13. Cache memory? [Y/N D:N]: Y
>;
>; The response to the following question specifies the highest interrupt
>; vector. If you respond with a value less than or equal to 400, SYSGEN
>; will assign the value associated with the highest interrupt vector
>; specified during the Peripheral Section. Therefore, if your system
>; will include devices that are not specified during the Peripheral
>; Section and which have vectors above 400 (devices such as K-series and
>; certain communication devices), specify that value in the next question.
>;
>* 14. Highest interrupt vector [O R:0-774 D:O]:
>;
For device configuration: "*" Prints device table, "·" Terminates inquiry
>;
"?" Prints current configuration
Enter devices and number of controllers for devices which require drivers
>;
>* 15. Devices [S]: *
>;
>;
Device codes for A/D and industrial/laboratory devices:
>;
>;
AD- ADOl-0 A/D Converter
>;
AF- AFCll A/D Converter
>;
AR- ARll Laboratory Subsystem
>;
IC- ICRll/ICSll Industrial Control Subsystem
>;
IS- DRSll/DSSll Industrial Control Subsystem
>;
LA- LPAll Laboratory Subsystem
>;
LS- LPSll Laboratory Subsystem
>;
UD- UDCll Universal Digital Controller
>;
>;
Device codes for Interprocessor communication devices:
>;
>;
XB- DAll-B Interprocessor Link
>;
XE- DEUNA Unibus Ethernet Controller
>;
XL- DLll-E Interprocessor Link
>;
XM- DMCll-E/DMRll Interprocessor Link
>;
XP- DPll Synchronous Interface
>;
XQ- DQll Synchronous Interface
>;
XU- DUll Synchronous Interface
>;
xw- DUPll Synchronous Interface
>;

7-10

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
>;
Device codes for unit record devices:
>;
>;
CR- CRll/CMll-E Card Reader
>;
GR- VT11/VS60 Graphics Subsystem
>;
LP- LAll/LPll/LSll/LVll/LNOl Line Printer
>;
PP- PCll Paper Tape Punch
>;
PR- PCll/PRll Paper Tape Punch and Reader
>;
>;
Device codes for disk devices:
>;
>;
DB- RP04/RP05/RP06 Disk Drive
>;
DD- TU58 Cartridge DECtape II
>;
DF- RFll Fixed Head Disk Drive
>;
DK- RK03/RK05 Disk Drive
>;
DL- RL01/RL02 Disk Drive
>;
DM- RK06/RK07 Disk Drive
>;
DP- RP02/RP03 Disk Drive
>;
DR- RM02/RM03/RM05/RM80 Disk Drive
>;
DS- RS03/RS04 Fixed Head Disk Drive
>;
DT- TU56 DECtape
>;
DU- RA60/RA80/RA81/RC25/RD51/RD52/RD53/RX50 Disk Drive
>;
DX- RXOl Floppy Disk Drive
>;
DY- RX02 Floppy Disk
>;
EM- MLll Non-Rotating Electronic Memory
>;
>;
Device codes for Magnetic tape devices:
>;
>;
CT- TU60 Cassette Tape Drive
>;
MM- TU16/TU45/TU77/TE16 Magtape Drive
>;
MS- TS11/TU80/TSV05 Magtape Drive
>;
MT- TU10/TE10/TS03 Magtape Drive
>;
MU- TU81/TK50 Magtape Drive
>;
>;
Device codes for terminal interface devices:
>;
>;
YH- DHll Asynchronous Terminal Interface
YV- DHUll/DHVll Asynchronous Terminal Interface
>;
>;
YJ- DJll Asynchronous Terminal Interface
YL- DLll-A/-B/-C/-D/-E/-J/-W Asynchronous Terminal Interface
>;
YZ- DZll/DZVll Asynchronous Terminal Interface
>;
>;
Device codes for pseudo devices:
>;
>;
CO- console device
>;
NL- null device
>;
>;
>;
Enter responses as: devl=number controllers,dev2=number controllers, •••
If a devices is specified without the number of controllers, the number
>;
of controllers defaults to 1.
>;
>;
Example: DK,DM=2,YL,NL.
>;
>;
>* 15. Devices [S]: DU=2,DL,DB,MU,YL,YV,NL.
>;
>; Processor:ll/84
Memory Size:256K,Mapped
System:RSX-llS
>;
>; Host configuration
>;
>* 1. Is a line printer available? [Y/N]: Y
>* 3. Does the listing/map device have at least 120 columns? [Y/N]: Y
>* 4. Assembly listings device (ddu:) [D: "NL:"] [SJ: SY:
>* 5. Map device for Executive and device drivers (ddu:) [D: SYO:] [S]:
>;

7-11

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

>* EOS *Do you want to: <CR>-continue R-repeat section E-exit P-pause (S]:

>;
>; Executive Options

>;
>;
>;
>*
>*
>*
>*

Answer Y(ES) if the following support is desired
6.
7.
8.
9.

>;
>;

>* 15.
>* 16.

Executive Common? [Y/N]: Y
Memory management (PLAS) directives? [Y/N]: Y
Send/Receive by reference directives? [Y/N]: Y
Get mapping context directive? [Y/N]: Y
Address checking support will be included
I/O rundown support will be included
Loadable device drivers? [Y/N]: Y
Should the default for all applicable drivers be loadable? [Y/N]: Y
AST support will be included
Include support for Cancel Selective Marktime? [Y/N]: Y
Task termination and device not ready messages (TKTN)? [Y/N]: Y
Power fail recovery? [Y/N]: Y
Large (20K) Executive? [Y/N]: Y
Logical device assignment? [Y/N]: Y
Do you intend to include a user-written driver? [Y/N]:
Executive Debugging Tool (XDT)? [Y/N]:
Include support for communications products (such as DECnet)? [Y/N]: Y

>*
>*
>*
>*
>*
>*
>*
>*

18.
19.
20.
22.
23.
25.
30.
32.

>;
>;
>;
>;
>;
>;
>;
>;

If you will be generating DECnet into this system, be sure you have
read the section on SYSGEN requirements in the "RSX DECnet Network
Generation and Installation Guide."
Several DECnet features
(eg. remote terminal support,
llS task
loading/upline dumping, etc.) require special consideration during
SYSGEN.

>;
ACP support will be included
>* 32A. Include Network Command Terminal support? [Y/N]: Y
>* 33. System controlled partitions? [Y/N]: Y
>* 36. Group global event flags? [Y/N]: Y

>;
>;

For directives:

>;
>;
>;
>;
>;

* - Prints the table
- Terminates inquiry
%
Gets all valid directives and terminates inquiry

>* 37. Enter code for system directives [S]:

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*

A- Get partition parameters
C- Send/Receive
E- Extend task
G- Get sense switch
I- Stop bit
K- Parent offspring taskiQg

B- Get task parameters
D- Alter priority
F- Connect to interrupt vector
H- Set system time
J- Specify requested exit AST
L- Parent offspring tasking with chaining

Enter responses as codelcode2code3 •••
37.
38.
39.
40.
41.
42.
48.
51.
52.
53.
54.

(no commas)

(e.g.: ABCDF.)

Enter code for system directives [SJ: ABCDEFHIJK.
Number of pre-allocated QIO packets [D R:0.-15. D:5.]:
Size of data transfer vector in words [D R:0.-33. 0:33.]:
Round-robin scheduling interval in ticks [D R:0.-1000. 0:5.]:
Highest priority class for consideration [D R:l.-249. D:l50.]:
Lowest priority class for consideration [D R:l.-150. D:l.]:
System crash register and stack dump device CSR [O R:0-177700 D:l77564]:
Crash dump analysis: A- PANIC B- Crash Dump Analysis (CDA) C- None
[D:
CDA output notification device CSR [O R:l60000-177700 0:177564]:
Enter CDA memory dump device mnemonic (ddu:) [S R:3-4]: MUO:
Enter CDA memory dump device CSR [O R:l60000-177700 0:174500]:

7-12

[S]:

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

>* EOS *

Do you want to: <CR>-continue R-repeat section E-exit P-pause [S]:

>;
>;
>; Terminal driver options
>;
The Full Duplex Terminal Driver will be included.
>* 2. Unsolicited input timeout value in seconds [D R:0.-255. D:l20.]: 0

>;
>;

Answer Y(ES) if the following support is desired

>;
>*
>*
>;
>*
>*
>*
>*
>*
>*
>*
>*

6. Unsolicited input character AST? [Y/N]: Y
8. Breakthrough write? [Y/N]: Y
CTRL/R support will be included
10. Escape sequence handling? [Y/N]: Y
11. Get multiple characteristics? [Y/N]: Y
12. Set multiple characteristics? [Y/N]: Y
13. Get terminal driver options? [Y/N]: Y
17. Read after prompt? [Y/N]: Y
20. CRT rubout support? [Y/N]: Y
25. Hardware unrecoverable input error notification? [Y/N]: Y
26. Device independent cursor positioning? [Y/N]: Y

>* EOS *Do you want to: <CR>-continue R-repeat section E-exit P-pause [S]:

>;
>;
>; System Options

>;
>;

Answer Y(ES) if the following support is desired

>;
>* 2A. Include support for the IPll Industrial I/O Subsystem? [Y/N]: N
>* 11. What name would you like to give your system [D: RSXllS] [S R: 0-6]:

>;
>* EOS *Do you want to: <CR>-continue R-repeat section E-exit P-pause [S]:

>;
Thinking
>; End of Executive option generation at 10:06:51 on 29-MAY-85

>; Peripheral configuration

>;
Parameters appearing in square brackets "[ ••• ]" can only be
>;
specified for the first controller of a particular device.
>;
>;
Parameters appearing in parentheses "( ••• )" only need be specified
if
the indicated option is present on the target system.
>;
>;
>;
The
default for loadable drivers has been set to *TRUE*.
To override this setting enter R (resident) as the first parameter
>;
>;
for
the
first
controller
of
the
specified
device.
>;
>; A/D and Laboratory devices: None specified
>;
>; Interprocessor communication devices: None specified
>;
>; Unit record devices: None specified
>;
>; Disks: DB, DL, DU
>;
>; Enter [L/R,] vector, CSR, number of drives, unit number of first drive,
[O=offset recovery support/NO=no support] for:
>;
>;
>*

2. DB controller 0 [D: 254,176700,,0,0]

[S]:

>* 52. Contr 0 unit o. is an RP04,05/RP06 [D: RP06] [S]:
>;

7-13

, ,l

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

>; Enter

[L/R,] vector, CSR, number of drives for:

>;
>* 3. DL controller 0 [D: 160,174400)
>* 53. Contr 0 unit O. is an RL01/RL02 [D: RLOl]

>*
>*

3. DU controller 0 [D: 154,172150)
3. DU controller 1

[S]:

,,1

[S): RL02
[S]:

,,2

[S]: 360,172154,2

>;
>; Tapes: MU

>;
>; Enter [L/R,] vector, CSR for:

>;
>*

1. MU controller 0 [D: 260,174500)

[S]:

>;
>; Non-physical

(pseudo) devices: CO, NL, TI, CL, LB, SY

>;
>; Terminal interface devices: YL, YV

>;
>; Enter vector, CSR, E=DLll-E modem support/NO=no for:

>;
>* 21. YL controller 0 [D: 60,177560,NO]

[S]:

>;
>; Enter vector, CSR, highest line number <O to 15> [, answer speed] for:

>;
>* 26. YV controller 0 [D: ,160440,,300]

[S]: 300,160440,4

>;
>* EOS *

>;
>;

Do you want to: <CR>-continue E-exit P-pause [S]:

>; End of interrupt vector area has been set to 400

>;
>;
>; Create Executive build files

>;
>;
>*

1. Do you wish to edit any of the Executive files?

[Y/N]:

>;
>;
>* EOS *Do you want to: <CR>-continue R-repeat section E-exit P-pause [S]:

>;
>;
>;
>; Prepare for task building

>;
>;
>; Clean-up extraneous object files

>;
>;
>* EOS *Do you want to: <CR>-continue R-repeat section P-pause [S]:

>;
>; End of llSGEN phase I at 10:40:17 on 29-MAY-85
>;
To continue type: @[2,200]11SGEN2

>;
>@ <EOF>
> @llSGEN

>;
>; RSX-llS Version 4.2 BL38 System Generation done on VAX/VMS

>;
>;

7-14

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

>; RSX-llS system generation set-up section

>;
>*Is the target disk, LBO:, the system device? [Y/N]: N
>*What is the group number for the system files (0 R:l-10 D:l]:
>*What is the group number for the executive files [O R:l-11 D:ll]:
>*Target device name [SJ: OMO:
>SET DEFAULT OMO:
>ASN DMO:=SY:
%MCR-I-SUPERSEOE, previous value of SY has been superseded
>ASN DMO:=SYO:
%MCR-I-SUPERSEOE, previous value of SYO has been superseded
>ASN OMO:=LB:
%MCR-I-SUPERSEDE, previous value of LB has been superseded
>ASN DMO:=LBO:
%MCR-I-SUPERSEDE, previous value of LBO has been superseded
>ASN MP:=MPO:
%MCR-I-SUPERSEDE, previous value of MPO has been superseded
>ASN TK:=TKO:
%MCR-I-SUPERSEDE, previous value of TKO has been superseded
>ASN OMO: [l,54]11MTKB.TSK=TKB
%MCR-I-SUPERSEDE, previous value of TKB has been superseded
>ASN DMO: [l,54]11MVMR.TSK=VMR
%MCR-I-SUPERSEDE, previous value of VMR has been superseded
>ASN DMO:=WK:
%MCR-I-SUPERSEDE, previous value of WK has been superseded
>ASN DMO:=WKO:
%MCR-I-SUPERSEDE, previous value of WKO has been superseded
>*Copy the RSX-llS distribution files to the target disk? [Y/N]:

>; Big disk distribution kit

>;
>*
>*
>*
>*

3.
5.
6.
7.

Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/N]:
Are you generating an unmapped system? [Y/N]: N
Use an input saved answer file? [Y/N]: Y
Name of input saved answer file [D: SYSSAVED.CMD] (SJ:

>;
>; Phase I input saved answers
>; created on 29-MAY-85 at 09:41:56
>; by llSGEN version 2.10
>;are from file LB0:[2,200]SYSSAVED.CMD;l

>;
>*

9. Name of output saved answer file [D: LBO: [2,200]SYSSAVED.CMD]

[SJ:

>;
>;Phase I output saved answers created in file LB0:[2,200]SYSSAVED.CMD;2

>;
>* 10. Use saved host configuration? [Y/N]: Y
>* 11. Use saved peripheral configuration? [Y/N]: Y
>* 12. Skip end of section (EOS) breakpoints? [Y/N]: Y
>* 13. Skip end of execution (EOX) breakpoints? [Y/N]: Y
>* 14. Clean up files from previous GENs? [Y/N]: Y
>SET /UIC=[l,l]
>PIP [l,20]RSXBLD.CMD;*/DE/NM
>PIP [l,24]RSXBLD.CMD;*/DE/NM,TTDRVBLD;*
>PIP (11,20]*.0BJ;*/DE/NM,*.UDC;*,*.ICR;*,*.IDS;*,*.PCS;*
>PIP [11,24]*.0BJ;*/DE/NM,*.UDC;*,*.ICR;*,*.IDS;*,*.TTY;*,*.PCS;*
>PIP [ll,30]*.LST;*/DE/NM,(11,34)*.LST;*
>PIP [11,lO]RSXMC.MAC;*/DE/NM,ICTAB;*,[2,200]SGNPARM.CMD;*
>PIP [2,200JRSXBLD.CMD;*/DE/NM,TTDRVBLD;*
>PIP SY: [11,20]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,20]MCRSETASM;*
>PIP SY: [ll,24]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,20]MCRSETASM;*
>PIP SYO: [ll,24]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,24]MCRSETASM;*
>PIP /FR

7-15

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
LBO: has 43372. blocks free, 10418. blocks used out of 53790.
Largest contiguous space = 26837. blocks
13119. file headers are free, 328. headers used out of 13447.
>SET /UIC=[ll,10]

>;
>; Target configuration

>;
>; Processor:ll/84

Memory Size:256K,Mapped

System:RSX-llS

>;
Switch Register
>;
Floating Point Processor
>;
Extended Instruction Set
>;
Parity Memory
>;
Cache Memory
>;
>;
>; Host configuration
>;
>; Executive Options
>;
ACP support will be included
>;
>;
>;
>; Terminal driver options
The Full Duplex Terminal Driver will be included.
>;
>;
>; System Options
>;
>;
Thinking •••
>;
>; End of Executive option generation at 11:05:37 on 29-MAY-85
>;
>; Peripheral configuration
>;
Parameters appearing in square brackets "[ ••• ]" can only be
>;
specified for the first controller of a particular device.
>;
>;
Parameters appearing in parentheses "( ••• )" only need be specified
if
the indicated option is present on the target system.
>;
>;
The
default for loadable drivers has been set to *TRUE*.
>;
To override this setting enter R (resident) as the first parameter
>;
for
the
first
controller
of
the
specified
device.
>;
>;
>; A/D and Laboratory devices: None specified

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

Interprocessor communication devices: None specified
Unit record devices: None specified
Disks: DB, DL, DU
Tapes: MU
Non-physical

(pseudo) devices: CO, NL, TI, CL, LB, SY

>; Terminal interface devices: YL, YV

>SET /UIC=[l,24] ! Creating TTDRVBLD.CMD
>SET /UIC=[ll,10]
>; End of interrupt vector area has been set to 400

>;
>;
>; Create Executive build files
>;

7-16

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
>PIP RSXMC.MAC=SYO:RSXMCO.MAC/AP
>ASN SY:=LB:
%MCR-I-SUPERSEDE, previous value of LB has been superseded

>; Start of Executive assembly at 11:25:50 on 29-MAY-85
>SET /UIC=[ll,24]
>MAC @SY:RSXASM

>;
>; End of Executive assembly at 14:30:32 on 29-MAY-85

>;
>;
>; Start of device drivers assembly at 14:30:33 on 29-MAY-85
>MAC @SY:RSXDRVASM

>;
>; End of device drivers assembly at 18:53:30 on 29-MAY-85
>ASN =LB:

>;
>; Prepare for task building

>;
>SET /UIC=[l,24]
>PIP RSXllS.OBS=[ll,24]*.0BJ
>PIP TTDRV.OBJ=[ll,24]*.TTY
>LBR RSXllS/CR:l00.:1010.:128.=RSXllS.OBS
>LBR TTDRV/CR:30.:380.:64.=TTDRV
>PIP /NV=[ll,lO]RSXBLD.CMD
>PIP [11,lO]RSXBLD.CMD;*/DE/NM

>; Clean-up extraneous object files

>;
>PIP RSXllS.OBS;*/DE/NM,TTDRV.OBJ;*,[11,24]*.0BJ;*,*·TTY;*

>; End of llSGEN phase I at 18:57:06 on 29-MAY-85
>;
-- To continue type: @[2,200]11SGEN2

>SET /UIC=[2,200]
>@ <EOF>

> @11SGEN2
>;
>; RSX-115 Version 4.2 BL38 System Generation Phase II

01754

>;
>;

Build The Executive And All Required Tasks

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

This command file will produce the target system on your SY: disk.
If it is an RLOl or RL02, this command file will delete a number
of files from this disk to make room for those required to complete
this llSGEN.
You must be running on an expendable copy of
your disk.
Note however, that the disk will be left in a
state such that RSX-llS sysgens may be performed at a later
date.
In addition, the sysgen itself may be terminated and
may be restarted at just about any point to rebuild particular
pieces of the system.

>;
>* In what UIC is SGNPARM.CMD if not [2,200] [S]:
>; Big disk distribution kit llSGEN version 2.10 for RSX-llM BL38

>;
>; Continuation from llSGEN PHASE I done on 29-MAY-85 at 18:56:57
>TIM
30-MAY-1985 09:22:43

7-17

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
>* Target device name [S]: OMO:
>SET DEFAULT OMO:
>ASN OMO: =SY:
%MCR-I-SUPERSEDE, previous value of SY has been superseded
>ASN OMO: =SYO:
%MCR-I-SUPERSEDE, previous value of SYO has been superseded
>ASN DMO:=LB:
%MCR-I-SUPERSEDE, previous value of LB has been superseded
>ASN OMO: =LBO:
%MCR-I-SUPERSEDE, previous value of LBO has been superseded
>ASN TK:=TKO:
%MCR-I-SUPERSEDE, previous value of TKO has been superseded
>ASN MP: =MPO:
%MCR-I-SUPERSEDE, previous value of MPO has been superseded
>ASN OMO: [l,54]11MTKB.TSK=TKB
%MCR-I-SUPERSEDE, previous value of TKB has been superseded
>ASN OMO: [1,54]11MVMR.TSK=VMR
%MCR-I-SUPERSEDE, previous value of VMR has been superseded
>ASN OMO: =WK:
%MCR-I-SUPERSEDE, previous value of WK has been superseded
>ASN OMO: =WKO:
%MCR-I-SUPERSEDE, previous value of WKO has been superseded
>SET NOON

>; The map device specified must already be mounted with ore [1,34].
>; If it is not, respond to the next question with AZ and do so.

>ASN SY:=LB:

>;
>; Expanded comments provide a complete description of every step in
>; this llSGEN command file.
On the other hand, short comments
>; provide virtually no explanatory text.

>;
>*Do you want expanded comments? [Y/N]: y

>;
>; Create RSX-llS subset system library
>; if you have not already done so.

>SET /UIC=[l,1]
>* Have you already created llSLIB.OLB? [Y/N]:
>LBR LB:llSLIB/CR:30.:896.:320.
>* Have you already built the Exec? [Y/N]:
>SET /UIC=[l,24]

>;
>; Purge Exec build command files and assembly prefix files

>;
>PIP RSXBLD.CMD/PU/NM
>PIP [11,lO]RSXMC.MAC/PU/NM

>;
>; Now we build the Executive
>; If you must make changes to the Executive build files
>; answer yes to the following question. Edit RSXBLD.CMD
>; by issuing the command EDI LB:RSXBLD.CMD. 11SGEN2 will
>; build the Executive after you resume from the pause.

>;
>* Do you wish to edit the Executive build file? [Y/N]:
>TKB @LB: RSXBLD
>* Did the Executive build successfully? [Y/N]: Y

>
> You now need the Executive maps to layout
> the partitions in your new system.
>

7-18

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
>*Do you have the maps already? [Y/N]:
>PIP LP:=SYO: [l,34]RSX11S.MAP,EXCOM1.MAP,EXCOM2.MAP

>;
>;
>;
>;
>;
>;

>;
>SET /UIC=[l,64)
>*Do you want to build any loadable drivers now? [Y/N]: Y

>;
>; Build Loadable drivers

>* 3. Device for driver's maps [D: NL:]
>SET /UIC=[l,24]

[S]: DMO:

>; The following are mnemonics of the loadable device drivers selected.

>;
>;

>;
>; When all drivers are built, strike carriage return.

>* 5. Driver 2-character device mnemonic [S]: DB
>* 6. Ori ve par ti ti on name [D: DRVPAR] [S]:
>TKB @SY:DBDRVBLD
>* 5. Driver 2-character device mnemonic [S]: DL
>* 6. Drive partition name [D: DRVPAR] [S]:
>TKB @SY:DLDRVBLD
>* 5. Driver 2-character device mnemonic [SJ: DU
>* 6. Drive partition name [D: DRVPARJ [S]:
>TKB @SY:DODRVBLD
>* 5. Driver 2-character device mnemonic [SJ: MU
>* 6. Drive partition name [D: DRVPARJ [S]:
>TKB @SY:MODRVBLD
>* 5. Driver 2-character device mnemonic [SJ:
>SET /OIC=[l,64)
>SET /UIC=[l,24]
>*Have you already built the full duplex terminal driver? [Y/N]:

>;
>; Now we build the full duplex terminal driver

>;
>;
>; The task build command file for the full duplex terminal drive
>; specifies that it run in partition TTPAR, having a length of
>; 40000 octal.

>*Do you wish to edit the build command file for the terminal driver? [Y/N]:
>TKB @LB:TTDRVBLD.CMD
>*Did the terminal driver build successfully? [Y/N]: Y
>*List full duplex terminal driver map? [Y/N]: Y
>PIP LP:=SYO: [l,34]TTDRV.MAP
>*Do you want to continue and build the privileged tasks? [Y/N]: Y

>;
>; Prepare to assemble and build the RSX-llS privileged

>; software components.
>;
>; The tasks TKTN, BASMCR, OTL, and SIP must be assembled, and the
>; task build command files possibly edited before they can be built.
>; The tasks RSDVOS, RSDV52, and RSDVlH need only to be built, but
>; their command files may also be edited before they are built.

7-19

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
>;
>;
>;
>;
>;

It is not necessary to save/print the assembly listings;
However, we recommend that you save/print the task build
maps. This is especially important when generating
an unmapped system -- without maps it will be difficult
to determine partition limits.

>;
>* Assembly list device for privileged tasks (DDNN:) [D: NL:] [S]: DMO:
>*Is DMO: mounted as a FILES-11 volume with UFO [1,34]? [Y/N]: Y
>* Map device for privileged tasks (DONN:) [D: SY:] [SJ:
>*Have you already built task TKTN? [Y/N]:

>;
>; Task TKTN will be included in your llS system as a result
>; of your selection in llSGEN Phase I.

>;
>;
>; The privileged tasks BASMCR, OTL, and SIP were specially designed
>; for use in the RSX-llS environment. Their inclusion in the system
~; i~ optional.
If desired, they will be assembled and built under
>; control of this command file.

>;
>*Do you wish to include BASMCR, OTL, or SIP in your system? [Y/N]: y

>;
>;
>;
>;
>;
>;
>;

The tasks RSDVOS, RSDV52, and RSDVlH dynamically display the
the status of memory on a graphics terminal and can be built
for the VTOSB terminal, VT52 terminal, and VTlOO terminal
respectively.
These tasks display which tasks are in memory
and where in memory they reside, which task is currently
running, and the status of pool.

>;
>*Do you want to include RSDVOS, RSDV52, or RSDVlH? [Y/N]: y

>;
>;
>;
>;
>;
>;
>;

>;
>*Do you wish to include the RSX-llS subset FCS? [Y/N]: y

>;
>;
>;
>;
>;

The RSX-llM crash dump analyzer (CDA)
may also be built to run on a non-M
host system for analysis of RSX-llS
crash dumps.

>*Do you wish to build CDA for your host system? [Y/N]: y
>SET /UIC=[ll,10]
>*Do you wish to make corrections to RSX-llS source modules? [Y/N]:
>SET /UIC=[l,24]
>MAC @TKNASM
>PIP TKNASM.CMD;*/DE

>;
>;
>;
>;
>;

>*Do you have to edit the task build command file for TKTN? [Y/N]:
>TKB @TKNllSBLD.CMD

>;
>;
>;
>;
>;

BASMCR is a privileged task which supplies a subset (or basic
set) of the RSX-llM MCR commands. It can not be included if
during Sysgen Phase I you indicated that you did not want any
terminal devices.
Its size, depending upon options, ranges
from 6400 to 16000 octal on mapped systems.

7-20

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
Do you want to include task BASMCR? [Y/N]: Y
>UFO SY: [16, 10]
>UFO SY:[l6,24]
>UFO OMO: [16, 34]
>SET /UIC=[l6,10]
>PIP BMPRE.MAC;*/DE/NM
>PIP *.MAC;*/RM/NM
>PIP [16,*]*.*;*/DE/NM
>PIP [16,10]=[2,20]BMPRE.MAC
>PIP [16,10]/EN=[2,20]ABOBAS.MAC,ATLBAS,BRKBAS,ERRBAS,ERRMSG
>PIP [16,10]/EN=[2,20]FMTDV.MAC,FNDUCB,GNBLK,GETNUM,KEYWD
>PIP [16,10]/EN=[2,20]LKLST.MAC,MCRBAS,OPEBAS,PRSBAS,REDBAS
>PIP [16,10)/EN=[2,20]REMBAS.MAC,RPSBAS,RUNBAS,TIMBAS
>SET /UIC=[l6,24]

>;
>;
>;
>;
>;
>;

>;
>;
>;
>;
>;

The size of BASIC MCR is dependent upon the inclusion of
conditional assembly code.
The inclusion of the code is
controlled by symbol definitions appearing in an assembly
prefix file.
The default for these conditionals is
exclusion.
The following options, along with the corresponding control symbols, are available:
R$$ATL - ATL/TAL COMMANDS
R$$ERM - ERROR MESSAGE TEXT
R$$0PE - OPEN COMMAND

>; To include an option locate the desired conditional symbol
>; and remove the semicolon at the beginning of the line. For
>; example:

>;
>;
>;
>;
>;
>;
>;

*PL ;R$$ATL
;R$$ATL = 0 ;INCLUDE ATL
*C / ; / /
R$$ATL = 0 ; INCLUDE ATL

>; Repeat this for all desired options.
Note that the symbols
>; appear on consecutive lines in alphabetical order in the file.

>*Do you wish to edit the assembly prefix file for BASMCR? [Y/N]: Y
>EDI [16,lO]BMPRE.MAC
[00029 lines read in]
[Page
l]
*PL ;R$$ATL
;R$$ATL
INCLUDE ATL
0
*C /;//
R$$ATL
0
INCLUDE ATL
*PL ;R$$ERM
;R$$ERM
INCLUDE ERROR MESSAGES
0
*C /;//
INCLUDE ERROR MESSAGES
R$$ERM
0
*PL R$$0PE
INCLUDE OPEN
;R$$0PE
0
*C /;//
R$$0PE
INCLUDE OPEN
0
*EXIT
[Exit]
>MAC @BASMCRASM.CMD
>SET /UIC=[l,24)
>PIP [16,lO]BMPRE.MAC;*/DE/NM
>PIP [16,10]*.MAC;*/RM/NM
>PIP BASMCR.OBJ=[l6,24]*.0BJ
>PIP [16,24)*.*;*/DE/NM
>LBR BASMCR/CR:21.:64.:64.=BASMCR
>PIP BASMCR.OBJ;*/DE/NM

7-21

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

>;
>;
>;
>;

The task build command file for BASMCR specifies that it
run in partition MCRPAR, length 16000 octal {mapped).
If you must change the partition name or length,
you will have to edit its task build command file.

>;
>*Do you wish to edit the task build command file for BASMCR? [Y/N]:
>TKB @BASMCRBLD.CMD

>;
>;
>;
>;
>;
>;

OTL is a privileged task which is the RSX-llS on-line task loader.
It performs the install, load, and fix functions for tasks which
were created on a host development system and copied via FLX to a
load medium.
Depending on the number of load devices, etc, OTL
ranges from 8000 to 15000 octal on mapped systems.

>;
>*Do you want to include task OTL? [Y/N]: Y
>UFD SY: [20, 10]
>UFD SY: [20,24]
>UFO DM0:[20,34]
>SET /UIC=[20,10]
>PIP SY:OTLPRE.MAC;*/DE/NM
>PIP SY:*.MAC;*/RM/NM
>PIP [20,*]*.*;*/DE/NM
>PIP [20,10]=[2,20]0TLPRE.MAC
>PIP [20,10]/EN=[2,20]0TL.MAC,OTLCD,OTLCM,OTLERR
>PIP [20,10]/EN=[2,20]0TLHD.MAC,OTLLB,OTLLD,OTLQIO,OTLRD
>SET /UIC=[20,24]

>; The size of OTL is dependent upon the inclusion of conditional
>; assembly code. The inclusion of the code is done in two ways,
>; .by a single symbol definition and by macro calls appearing
>; in an assembly prefix file.
The first controls the inclusion
>; of error message text. To include this option, locate the
>; symbol R$$ERM, and remove the semicolon from the beginning
>; of the line.
The default for error message text is exclusion.
>; For example:

>;
>;
>;
>;
>;
>;

*PL ;R$$ERM
;R$$ERM=O
*C /;//
R$$ERM=O

>;
>;
>;
>;

The other type of option concerns the exclusion of unwanted
device support. For each of the OTL load devices which
were included in Sysgen Phase I, corresponding support will be
generated in OTL.
Naturally, support will not be generated for
>; those OTL load devices which were not included in Sysgen Phase I.
>; The following devices along with corresponding control symbols
>; may be supported by OTL:

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

PR:
DX:
DY:
DU:
CT:
OT:
MT:
MS:
MM:
DD:

- PRll, paper tape reader
- RXll, flexible disk
- RX21, flexible disk
- RXSO, flexible diskette
- TAll, cassette tape
- TCll, DECtape
- TMll, mag tape
- TSll, mag tape
- TU16, magtape
- TU58, cartridge

7-22

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

>; To exclude OTL support for a device which has been generated into
>; your RSX-llS Executive, locate the corresponding device symbol
>; and place a semicolon at the beginning of the line. For example:

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

*PL PRll
INCLUD PR11,P$$Rll

;PCll/PRll paper tape reader

INCLUD PR11,P$$Rll

;PCll/PRll paper tape reader

*C //;/
;

>*Do you wish to edit the assembly prefix file for OTL? [Y/N]: Y
>EDI [20,lO]OTLPRE.MAC
[00142 lines read in]
[Page
l]
*PL ;R$$ERM
;R$$ERM=O
*C /;//
R$$ERM=O
*EXIT
[Exit]
>MAC @OTLASM.CMD
>SET /UIC=[l,24]
>PIP [20,lO]OTLPRE.MAC;*/DE/NM
>PIP [20,10]*.MAC;*/RM/NM
>PIP OTL.OBJ=[20,24]*.0BJ
>PI P [ 2 0, 2 4 ] * • * ; */DE /NM
>LBR OTL/CR:21.:128.:64.=0TL
>LBR OTL=[2,20]BLXIOM
>PIP OTL.OBJ;*/DE/NM

>;
>; The task build command file for OTL specifies that it
>;run in partition OTLPAR, length 15000 octal (mapped).
>; If you must change the partition name or length,
>; you will have to edit its task build command file.

>*Do you wish to edit the task build command file for OTL? [Y/N]:
>TKB @OTLBLD.CMD

>;
>;
>;
>;
>;

SIP is a privileged task which performs the RSX-llS system
image preservation duties.
It replaces the RSX-llM SAV MCR
command. Depending on the number of load devices, etc, SIP
ranges from 3700 to 7400 octal on mapped systems.

>;
>*Do you want to include task SIP? [Y/N]: Y
>UFD SY:[21,10]
>UFO SY: [21,24]
>UFO DM0:[21,34]
>SET /UIC=[21,10]
>PIP SY:SIPPRE.MAC;*/DE/NM
>PIP SY:*.MAC;*/RM/NM
>PIP [21,*]*.*;*/DE/NM
>PIP [21,10]=[2,20]SIPPRE.MAC
>PIP [21,10]/EN=[2,20]SIP.MAC,SIPBOO,SIPCD,SIPERR
>PIP [21,10]/EN=[2,20]SIPLD.MAC,SIPQIO
>SET /UIC=[21,24]

7-23

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

>;
>;
>;
>;
>;
>;
>;
>;
>;

>;
>;
>;
>;
>;
>;
>;

The size of SIP is dependent upon conditional assembly code
in exactly the same manner as OTL. There are only a few minor
differences. OTL supports the paper tape reader using the
control symbol PRll; SIP on the other hand supports the paper
tape punch using the control symbol PPll. In addition, OTL
supports DECtape II cartridges using control symbol TU58,
TSll magnetic tape drives using the control symbol TSll
and RX50 flexible diskettes using the control symbol RX50.
Edit SIPPRE.MAC in the same way described for OTL. For example:
*PL PPll
INCLUD PP11,P$$Pll
*C //;/
INCLUD PP11,P$$Pll
;

;PCll/PPll paper tape punch
;PCll/PPll paper tape punch

>*Do you wish to edit the assembly prefix file for SIP? [Y/N]: Y
>EDI (21,lO]SIPPRE.MAC
[00085 lines read in]
[Page
1)
*PL ;R$$ERM
;R$$ERM=O
*C /;//
R$$ERM=O
*EXIT
[Exit]
>MAC @SIPASM.CMD
>SET /UIC=[l,24)
>PIP (21,lO]SIPPRE.MAC;*/DE/NM
>PIP (21,10)*.MAC;*/RM/NM
>PIP SIP.OBJ=[21,24]*.0BJ
>PIP (21,24)*.*;*/DE/NM
>LBR SIP/CR:20.:64.:64.=SIP
>PIP SIP.OBJ;*/DE/NM

>;
>*Do you wish to edit the task build command file for SIP? [Y/N]:
>TKB @SIPBLD.CMD
>SET /UIC=[l,24)
>PIP RMD.OLB/NV=[2,20]RMDMAP.OLB
>*Do you want to include task RSDVOS? [Y/N]: N
>*Do you want to include task RSDV52? [Y/N]: N
>*Do you want to include task RSDVlH? [Y/N]: Y

>; The task build command file for RSDVlH specifies that it
>;run in partition RSDVlH, length 40000 (octal).
>; If you must change the partition name or length, you
>; will have to edit the task build command file.

>;
>* Do you wish to edit the task build command file for RSDVlH? [Y/N]:
>TKB @RSDVlHBLD.CMD
>SET /UIC=[l,24)

>;
>; It may be necessary to edit the task build command file and ODL file
>; to build CDA for the non-M host. Change the partition name and
>; base address to match that of the partition (on the host system) into
>; which CDA will be installed. You will also need to change the ODL
>; file to reference the correct device on the host where SYSLIB and
>; EXELIB reside.
The files are named CDABLD.CMD and CDABLD.ODL.
>; We will now pause to allow you to edit the command files.
>; 11SGEN2 -- Pausing. To continue type "CONTINUE".
IND
Pausing. To continue type "RES"
>RES

7-24

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

IND
-- Continuing
>; 11SGEN2 -- continuing
>SET /UIC=[l,64]
>TKB @[l,24]CDABLD
>; The CDA.TSK file resides in [1,64] on your RSX-llS sysgen disk
>; and can be run on the host system.
>; CDA must be run in compatibility mode on VAX/VMS hosts.
>SET /UIC=[l,24]

>;
>; Add subset FCS to the RSX-llS system object library

>;
>SET /UIC=[l,l]
>LBR LB:llSLIB/RP=[2,20]FCSllS
>PIP LB:llSLIB.OLB/PU/NM
>SET /UIC=[l,64]
>PIP *.*/PU/NM
>PIP [1,24]*.*/PU/NM

>;
>; The operation left to be performed is that of the final
>; configuration of the virgin executive using Virtual MCR.

>;
>*Do you want to configure the Exec at this time using VMR? [Y/N]: Y

>;
>;
>;
>;
>;
>;
>;

The contents of your RSX-llS release kit currently resides
under the UFD [2,20].
If your SY: disk is not an RK06/07 or an
RP04/05/06 you may want to delete these files.
Leaving
them on the disk will save the time of re-copying them the next
time you perform an RSX-llS Sysgen. If your SY: disk is an RK05,
they will be automatically deleted.

>*Do you want to delete the RSX-llS kit from this disk? [Y/N]:

>;
>; We will now make a copy of your target system

>;
>PIP RSX11S.SYS/NV/CO/BL:498.=RSX11S.TSK

>;
>; If you wish to make a copy of your task or system image file
>; on another device we will pause now to allow you to do so.

>;
>*Do you wish to copy your system to another device? [Y/N]:

>;
>; RSXllS.TSK is a backup copy of the llS system you have just built.
>; If you do not wish to retain it, we will delete it now.

>;
>*Do you wish to delete the system backup file RSXllS.TSK? [Y/N]:

>;
>; Your target system is now ready to set up partitions and install
>; the required tasks. The procedure to follow is:
>;
1) Run Virtual MCR
>;
2) Extend POOL space to base of first partition
>;
3) Set up your partitions
>;
3B) Load needed drivers
>;
3C) Set up a partition for the Directive Common
>;
4) Install tasks (BASMCR, OTL, SIP, TKTN)
>;
5) Fix tasks into (virtual) memory
>;
6) Optionally set the time and save a copy of THE
>;
system on a bootable medium
>;
7) Exit from virtual MCR and boot in your target system

7-25

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM
>; VMR example:

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

>VMR
! RUN VIRTUAL MCR
ENTER FILENAME:RSXllS.SYS ! VMR PROMPTS FOR FILE NAME
VMR>SET /POOL=XXX ! EXTEND POOL TO FIRST PARTITION BASE
VMR>SET /MAIN=TTPAR:XXX:XXX:TASK !SET UP FULL DUPLEX TT PARTITION
VMR>SET /MAIN=DRVPAR:XXX:XXX:TASK ! SET UP DRIVER PARTITION
VMR>SET /MAIN=PUCOM:XXX:XXX:COM
! SET UP COMMON FOR DU OR MU DRIVER
VMR>INS PUCOM
! INSTALL DU OR MU DRIVER COMMON
VMR>SET /MAIN=EXCOMl:XXX:200:COM ! SET lST EXEC. COMMON
VMR>INS EXCOMl !INSTALL lST EXECUTIVE COMMON
VMR>SET /MAIN=EXCOM2:XXX:200:COM ! SET 2ND EXEC. COMMON
VMR>INS EXCOM2 !INSTALL 2ND EXECUTIVE COMMON
VMR>SET /MAIN=SYSPAR:XXX:XXX:TASK
SET UP TKTN PARTITION
VMR>SET /MAIN=MCRPAR:XXX:XXX:TASK
SET UP MCR PARTITION
VMR>SET /MAIN=OTLPAR:XXX:XXX:TASK ! SET UP OTL PARTITION
VMR>SET /MAIN=SIPPAR:XXX:XXX:TASK ! SET UP SIP PARTITION
VMR>SET /MAIN=RSDVlH:XXX:XXX:TASK !SET UP RSDVlH PAR
VMR>SET /MAIN=GEN:XXX:XXX:SYS ! IF SYSTEM CONTROLLED PAR.
VMR>SET /MAIN=GEN:XXX:XXX:TASK ! IF USER CONTROLLED PARTITION
VMR>LOA XX:
! LOAD XXDRV
VMR>INS TKN/FIX=YES ! INSTALL & FIX TKTN
VMR>INS BASMCR/FIX=YES ! INSTALL & FIX BASIC MCR
VMR>INS RCT/FIX=YES
! INSTALL & FIX RCT
VMR>INS OTL/FIX=YES ! INSTALL & FIX OTL
VMR>INS SIP/FIX=YES ! INSTALL & FIX SIP
VMR>INS RSDVlH/FIX=YES ! INSTALL & FIX RSDVlH
VMR>TIM 10:45 11/10/77 ! SET TIME AND DATE
VMR>SAV DX:RSXllS ! SAVE SYSTEM ON RXOl FLOPPY
VMR>~Z
! EXIT FROM VIRTUAL MCR

>; End of VMR example

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

>;
>;
>;
>;
>;
>;
>;
>;
>;

Now we will run Virtual MCR so that you may initialize
your system. Be sure to define all required partitions
at this time, because the SET function is not supported
in RSX-llS BASIC MCR.
Furthermore, if you plan to
include BASIC MCR and OTL in your system, they must
be installed and fixed into memory.
Other tasks,
such as SIP and TKTN may be loaded into a running
RSX-llS system using OTL.
NOTE: Since LOAD and UNLOAD are not supported on
a running RSX-llS system, all required loadable
drivers must be loaded using VMR.
NOTE: You have requested to include the
directive common.
You must install the
common prior to exitting Virtual MCR
or your RSX-llS system will not boot.

>VMR
Enter filename: RSXllS.SYS
VMR>SET /POOL=*
VMR>SET /MAIN=TTPAR:*:314:TASK
VMR>LOA TT:
VMR -- *DIAG*-Loadable driver larger than 4K
VMR>SET /MAIN=DRVPAR:*:*:SYS
VMR>LOA DB:
VMR>LOA DL:
VMR>LOA DU:
VMR>LOA MU:

7-26

RSX-llS SYSTEM GENERATION ON A VAX/VMS HOST SYSTEM

VMR>SET /TOP=DRVPAR:-*
VMR -- *DIAG*-Installed tasks may no longer fit in partition
VMR>SET /MAIN=PUCOM:*:62:COM
VMR>INS PUCOM
VMR>SET /MAIN=EXCOM1:*:200:COM
VMR>INS EXCOMl
VMR -- *DIAG*-Partition reduced to executive common size
VMR>SET /MAIN=EXCOM2:*:200:COM
VMR>INS EXCOM2
VMR -- *DIAG*-Partition reduced to executive common size
VMR>SET /MAIN=SYSPAR:*:36:TASK
VMR>SET /MAIN=MCRPAR:*:l36:TASK
VMR>SET /MAIN=OTLPAR:*:l42:TASK
VMR>SET /MAIN=SIPPAR:*:40:TASK
VMR>SET /MAIN=RSDV1H:*:314:TASK
VMR>SET /MAIN=GEN:*:*:SYS
VMR>INS TKN/FIX=YES
VMR>INS BASMCR/FIX=YES
VMR>INS RCT/FIX=YES
VMR>INS OTL/FIX=YES
VMR>INS SIP/FIX=YES
VMR>INS RSDVlH/FIX=YES
VMR>AZ

>;
>; When this command file completes, your RSX-llS system is
>; ready to run.

>SET /UIC=[2,200]
>TIM
30-MAY-1985 11:14:20

>;
>@ <EOF>
> MOU MTO:/FOR
%MOUNT-I-MOUNTED, mounted on
> SET /UIC=[l,64)
>SET DEF [1,64)
> VMR
Enter filename: RSXllS
VMR>TIM 30-MAY-85 11:40
VMR>SAV MTO:RSXllS
VMR>AZ

MTAO:

7-27

APPENDIX A
RSX-llS ERROR MESSAGES

The following list of error messages is a subset of the RSX-llM
messages. The error message format is as follows:

error

XXX -- ## - ERROR MESSAGE
where:

xxx

indicates the three-character mnemonic of the On-Line
Task Loader
(OTL), System Image Preservation (SIP)
program, or Monitor Console Routine (MCR).

indicates the numerical error
particular error message.

ERROR MESSAGE

indicates the possible cause of the
appropriate, suggests remedial action.

code

assigned

the

error

and,

NOTE
The following list omits the 3-character mnemonic to
make a numerical search easier for you. Refer to
Section 2.1.3 (for BASIC MCR), Section 2.2.4
(for
OTL), and Section 2.3.4 (for SIP) for the particular
error message.
1 -

ILLEGAL FUNCTION
Explanation: A command was entered that MCR could not
or an inappropriate keyword was specified.

2 -

recognize

SYNTAX ERROR
Explanation: This message generally indicates that the required
information was entered incorrectly.
Retype the command line
using the correct syntax.

3 -

NO POOL SPACE
Explanation: This message is returned in the event of one of the
following errors:
•

The Executive could not currently satisfy
dynamic memory.

A-1

MCR's

request

for

RSX-llS ERROR MESSAGES

•

4 -

OTL detected insufficient pool space in the Executive when it
issued an I/O request nr attempted to all-ocate pool space.
Note that when this error condition occurs, OTL may exit
without printing this error message.

INVALID KEYWORD

Explanation: A keyword was specified in the command
the specific command processor did not recognize.
5 -

line

that

DEVICE NOT IN SYSTEM

Explanation: The device specified in the command line was not
generated into the system.
Devices to be used in the system must
be specified during system generation.
6 -

PRIVILEGED COMMAND

Explanation: A command available only to
was issued from a nonprivileged terminal.
7 -

privileged

terminals

PARTITION NOT IN SYSTEM

Explanation: This message is returned in the event of one of the
following errors:

8 -

•

The partition name specified as an argument in a command
could not be found in the system.

•

The partition specified in the task image was not
the system.

•

The specified partition was defined, but some or all
memory was not present in the current configuration.

defined
of

line
in
its

IO ERROR

Explanation: This message is returned in the event of one of the
following errors:

9 -

•

In attempting to read the next command, the MCR
detected an error.

command

OPEN

•

An MCR terminal-write operation failed.

•

A hardware error was encountered as the result
request issued to the load device or terminal.

I/O

•

The specified device was generated into the system, but it was
not present in the hardware configuration.

BYTE ADDRESS

Explanation: An odd address was specified as the argument to the
MCR command OPEN.

A-2

RSX-llS ERROR MESSAGES

10 -

INVALID TIME PARAMETER
Explanation:

A specified time field was incorrect.

11 - TASK NOT IN SYSTEM
Explanation:

The specified task was not installed in the system.

12 - INVALID ADDRESS
The address specified as an argument
command referenced one of the following:

Explanation:

the

OPEN

•

A nonexistent memory location

•

An address outside the boundaries of the specified partition

13 - TASK NOT ACTIVE
Explanation:

The specified task was not active.

14 - TASK BEING ABORTED
The task is being aborted because either
command ABORT was issued or an error was detected.

the

MCR

line

was

command

was

Explanation:

15 - TASK NOT SUSPENDED
Explanation:
The task specified in the RESUME command
never suspended.

16 - TASK ACTIVE
Explanation:

The task used as the argument of

the

active.
17 - CIRCULAR REDIRECT ERROR
Explanation:
The attempt to redirect a device would result in
circular list of redirections.

18 - OLD DEVICE NOT KNOWN TO SYSTEM
The system did not know the old device in the
command
(the device does not exist in the device

Explanation:

REDIRECT
tables) •

19 - NEW DEVICE NOT KNOWN TO SYSTEM
The system did not know the new device in the
command
(the device does not exist in the device

Explanation:

REDIRECT
tables).

A-3

RSX-llS ERROR MESSAGES
20 - PSEUDO DEVICE REDIRECT ERROR
Explanation: An attempt was made to redirect one
to another pseudo device.

pseudo

device

21 - OLD DEVICE ATTACHED
Explanation:

An attempt was made to redirect an attached device.

22 - TI REDIRECT ERROR
Explanation: An attempt was made to redirect the
TI:. This device cannot be redirected.

pseudo

device

23 - INVALID UIC
Explanation: A value of 0 was detected for either
number or the member number.
This is invalid.

the

group

the

limits

24 - ILLEGAL KEYWORD VALUE
Explanation: A value entered for a keyword exceeded
for that argument. Enter a valid value.
26 - LISTING DEVICE NOT AVAILABLE
Explanation: MCR attempted to display information to a device
unit that was attached, and therefore unavailable for printed
output.
27 - DEVICE NOT REDIRECTABLE
Explanation:

The specified device cannot be redirected.

40 - BASE ADDRESS MUST BE ON A 4K BOUNDARY
I

Explanation: A task image (not a common block)
in
system specified a base address not on a 4K boundary.

mapped

41 - ILLEGAL lST APR
Explanation: This message is returned in the event of one of the
following errors:
•

The image of a nonprivileged task in a mapped system specified
a nonzero first Active Page Register (APR).

•

The image of a privileged task in a mapped system specified
first APR that was not in the range APR4 through APR6.

42 - NOT ENOUGH APRS FOR TASK IMAGE
Explanation: There are not enough APRs to map the task as well
as the resident library references that the task image may have
in a mapped system.

A-4

RSX-llS ERROR MESSAGES
43 - FORMATTED BINARY CHECKSUM ERROR
Explanation: A checksum error was encountered
task image from paper tape.

while

reading

44 - FORMATTED BINARY FORMAT ERROR
Explanation: An invalid binary format was encountered in a
image being read from paper tape.

task

45 - UNEXPECTED END OF FILE ENCOUNTERED
Explanation: An end-of-file was encountered
task image was read.

before

the

entire

46 - SPECIFIED PARTITION TOO SMALL
Explanation: The partition specified in the task image
smaller than the load size of the task or common block.

was

47 - SPECIFIED PARTITION FOR COMMON BLOCK
Explanation:
block.

An attempt was made to install a task into a common

48 - TASK IS OVERLAID
Explanation: This message is returned in the event of one of the
following errors:
•

An attempt was made to install an overlaid task
without memory management directives.

•

An attempt was made to install a task that
overlays.

disk-resident

has

system

49 - TASK NAME ALREADY IN USE
Explanation: An attempt was made to install a task with the same
name as that of a task already installed.
50 - TASK NAME NOT DEFINED
Explanation: An attempt was made to install a
task from paper
tape without an optional file name specified. Additionally, the
task image did not contain a task name. Retype the command line,
specifying a file name that will become the task name by default.
51 - TASK AND PARTITION BASES MISMATCH
Explanation: An attempt was
unmapped system whose base
specified partition.

A-5

made to install a task in an
address did not match that of its

RSX-llS ERROR MESSAGES
52 - INVALID COMMON BLOCK
Explanation: A task contained a library reference
block that was not in the system.

common

53 - PARTITION TOO LARGE FOR PRIVILEGED TASK
Explanation: An attempt was made to install a privileged task in
a partition whose size was greater than 12K words.
(This message
occurs only on unmapped systems.)
54 - FILE NOT FOUND
Explanation:

The specified file was not found.

55 - COMMON BLOCK IS TASK PARTITION
Explanation: A task image contained a library reference that had
the same name as a task block.
56 - COMMON BLOCK NOT LOADED
Explanation: A task image contained a
common block that was not loaded.

library

reference

57 - LENGTH MISMATCH COMMON BLOCK
Explanation: A task image contained a
library reference to a
common block that was smaller than the size specified when the
task was built.
58 - BASE MISMATCH COMMON BLOCK
Explanation: A task image contained a library reference to a
common block whose base address was different from the one
specified when the task was built.
59 - COMMON BLOCK PARAMETER MISMATCH
Explanation: This message is returned in the event of one of the
following errors:
•

A task image contained a library reference to a common block
that did not contain position-independent code.
It was,
however, expected to contain this code.

•

A task image contained a library reference to a
that
contained
position-independent code.
however, expected to contain this code.

•

An attempt was made to load a common block whose task name did
not match the partition name.

common block
It was not,

60 - PARTITION NOT COMMON
Explanation: An attempt was made to ins·tall a common block in
task partition.

A-6

RSX-llS ERROR MESSAGES
61 - ILLEGAL DEVICE
Explanation: A task image contained a logical unit number
assignment to a device not in the system.

(LUN}

62 - FILE NOT TASK IMAGE
Explanation:
Preliminary checks indicated that either
the
specified file was not a task image, or the file was corrupted.
63 - PARTITION IS BUSY
Explanation: This message is returned in the event of one of the
following errors:
•

An attempt was made to fix a
occupied subpartition.

task

main

partition

attempt was made to fix a task in a main partition that had
• An
an occupied subpartition.
attempt was made to fix a task in a subpartition
• An
an occupied main partition.
•

that

had

An attempt was made to load a task into a system-controlled
partition, but the partition did not have enough contiguous
memory.

65 - INVALID BLOCK SIZE ON LOAD DEVICE
Explanation: The block size of a task image file
(on
tape} was not able to be evenly divided into 512(10).

cassette

66 - FILE NAME REQUIRED
Explanation: No file name was specified with a device.
name is required {OTL message} •

file

label

66 - LABEL REQUIRED
Explanation: No label was specified with a device.
required (SIP message}.

67 - INVALID LOAD DEVICE
Explanation: The version of OTL or SIP in use did not
(or was not assembled to support} the specified device.

support

68 - TOO MANY WINDOW BLOCKS
Explanation: The task would require more than eight Active
Registers {APRs; OTL message}.

Page

68 - IO OUTSTANDING
Explanation: An attempt was made to save the system at a
when one or more tasks had outstanding 1/0 (SIP message}.

A-7

time

RSX-llS ERROR MESSAGES
69 - TASK BUILT FOR WRONG SYSTEM
Explanation: OTL determined that the task required one
following features that the system does not support:

the

•

The task was built for an RSX-llM-PLUS system

•

The wrong version of the Task Builder was used to build the
task.
(For memory-resident overlaid tasks, the version must
be RSX-llM Version 3.2 or later.)

70 - ILLEGAL USE OF INCREMENT
Explanation: This message is returned in the event of one of the
following errors:
•

The specified increment causes the task to exceed 32K.

•

An attempt was made to install and fix an overlaid task with
an increment.
Overlaid tasks cannot be loaded with an
increment.

A-8

INDEX

On-Line Task Loader (OTL) (Cont.)
error messages, 2-11
exiting, 2-8
functions, 2-7
invoking, 2-8
load devices supported, 2-7,
4-3
size, 4-3

Absolute Loader, 2-19
Basic MCR, 2-1, 4-2
error messages, 2-4
initialization commands, 2-2
size, 4-2
system maintenance commands,
2-3
task control commands, 2-2
Bootstrapping
from paper tape, 2-19

RSX-llS
characteristics, 1-1
device support, 1-4
distribution media, 3-1
error messages, A-1
hardware/software
configurations, 1-4
kits, 3-1
privileged tasks, 1-2
software components, 1-5
system tasks, 4-2
update kit, 1-2
RSX-llS System generation
on a VAX/VMS host system, 7-1
dialog, 7-6
on an RSX-llM host system, 5-1
dialog, 5-4
on an RSX-llM-PLUS host
dialog, 5-4, 6-4
on an RSX-llM-PLUS host system,
6-1

Command Line
common blocks, 2-11
OTL, 2-8
Command line interpreter (CLI)
VAX/VMS, 7-2, 7-4
Commands
Basic MCR, 2-2
initialization, 2-2
system maintenance, 2-3
task control, 2-2
FIX, 2-7
MCR INSTALL, 2-7
SIP, 2-17
Copying procedures
RSX-llM host, 5-2
RSX-llM-PLUS host, 6-3
VAX/VMS host, 7-4
Distribution kit, 3-1
Down-line loading, 1-4
Error messages
Basic MCR, 2-4
OTL, 2-11
RSX-llS, A-1
SIP, 2-19
TKTN, 2-21
Executive
building, 4-1
configuration, 4-7
File Control Services (FCS)
RSX-llS support, 2-25
File Control Services (FCS)
subset, 2-25
macro calls, 2-25
File Transfer Utility (FLX), 1-4,
2-7
Hardware/software configurations,
1-4
Host/Target systems, 1-3
K-series lab support routine, 4-6
On-Line Task Loader (OTL), 1-2,
2-7, 2-9
building, 4-3

SETTIM routine, 2-23
System Activity Display Programs
(RSD), 2-24
characteristics, 2-24
display fields, 2-24
supporting options, 2-25
System Image Preservation Program
(SIP), 1-2, 2-16, 2-18
building, 4-4
error messages, 2-19
invoking, 2-17
operation, 2-18
size, 4-4
System libraries
macro, 4-9
object, 4-9
subset FCS resident, 4-9
System Task Directory (STD), 2-7
Task Termination Notification
program (TKTN) , 1-2, 2-20
building, 4-2
error messages, 2-21
invoking, 2-21
size, 4-2

Virtual Monitor Console Routine
(VMR), 1-5
Index-1

RSX-US
System Generation
and Installation Guide
AA-2874F-TC
READER'S COMMENTS
NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company's discretion. If you require a written reply and are eligible to receive one under Software
Performance Report (SPR) service, submit your comments on an SPR form.

Did you find this manual understandable, usable, and well organized? Please make suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent.

D
D
D
D
D
D

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify)

Organization
Street
State _ _ _ _ _ _ Zip Code - - - - - or Country

DoNotTear-FoldHereandTape -

~nmnomn

No Postage
Necessary
if Mailed in the
United States

111111

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

- -

Do Not Tear - Fold Here