Digital PDFs

AA-H427D-TC

October 1985

150 pages

Original

49MB

view download

OCR Version

39MB

view download

Document:	RSX-11M-PLUS Release Notes Version 3.0
Order Number:	AA-H427D-TC
Revision:	0
Pages:	150
Original Filename:

OCR Text

RSX-11M-PLUS
Release Notes
Order No. AA-H427D-TC

RSX-11M-PLUS Version 3.0

digital equipment corporation - maynard, massachusetts

First

Printing,

October

Revised,
Revised,

April
April
Revised, July

The
and

information
should

Corporation.
for

any

The

software

and

this
be

used

appear

this

only

assumed

for

the

change
by

assumes

without
Digital

1983
1985

notice

Equipment

responsibility

document.

document

copied

commitment

Corporation
in

this

subject

Equipment

that may

described

document

construed

Digital

errors

may

not

1979

1982

furnished

accordance

with

under
the

terms

license
of

such

license.
No

responsibility

equipment

that

not

affiliated

companies.

(c)

use

supplied by Digital

1979, 1982, 1983,
~ All

reliability

software

Equipment Corporation

its

1985 by Digital Equipment Corporation

Rights

Reserved.

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

DIBOL
EduSystem

PDT
RSTS

DEC/MMS

IAS

DECnet

MASSBUS

RSX
UNIBUS

DECsystem-10
DECSYSTEM-20
DECUS

MicroPDP-11
Micro/RSTS
Micro/RSX

VAX
VMS
VT

HOW TO ORDER ADDITIONAL DOCUMENTATION
In Continental USA and Puerto Rico call

800-258-1710

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

613-234-7726 (Ottawa-Hull)
800-267-6146 (all other Canadian)

DIRECT MAIL ORDERS (USA & PUERTO RICO)*
Digital Equipment Corporation
P.0O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (CANADA)

Digital Equipment of Canada Ltd.

940 Belfast Road

Ottawa, Ontario K1G 4C2
Attn: A&SG Business Manager

DIRECT MAIL ORDERS (INTERNATIONAL)
Digital Equipment Corporation
A&SG Business Manager
c/o Digital’'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 (SDC), Digital Equipment
Corporation, Northboro, Massachusetts 01532

CONTENTS

Page

PREFACE

o
+«

o
«

=«
«

@
.

]

are

Support
»

B
N

.
[

Subsystem

¢«

o«

-»

&
[
L]
L]

NAME

Strings
. « « o o
Name Translations

o
.

«
.

o
.

INSTALLED COMMONS

FEATURES

1-10

1-11
1-11
1-11

Form ddnn:
e o o
Loglcal Names

1-12
1-13

1-14
1-14

New Executive Features . . . . .
New Directives . « ¢ o« o« o «
High-Level Language Interface
.
Supplementary Executive Information
Privileged TasksS . « « « ¢ o o o o
Changes Made to Executive Data Structures
»

iii

the
. .
for

[]

LOGICAL

IP1l

(SPM-11)

]
&*

Extended

w N+

Creating Directories . « « « .
o« o
Directory for Nonprivileged Tasks e

Using Loglcal Names in
New Directives . . . .
FCS and RMS-11 Support

*®

9
&

@
*
¢

WO
O

&
o

HH
wN

Logical
Logical

9
&

EXECUTIVE
NN

PRESERVING CHANGES

Optlonal New Features
Questions for LAT and Term1na1 Driver
I/O
» L4 » » - LJ - » Modified Software Performance Monitor
Crash Device . « . « .
New Device Support . .
New Terminal Support .
MSCP Command and Response Rings
.

NEW

VWO

Disks

Processor

System

Hosts

L J

]

New

VAX

10)]

s
N

[]

o
®

¢«
&

W N

New Target

GENERATION

[

SYSGENs

NOAONAANAAO
UV
WWWWW W WwWw

Product

Data Terminal Emulator
Discontinued Support
Note Regarding the DLVJ1l
Support for the LASO, LA100, LNO1, and LNO3
Printers . . . . . .
Modifying or Removing Support for the Printers
Device Support Restrictions
Use of the TK50 With Utilities
LK201 Keyboard . . .

SYSTEM

s
*
s
&
&
®

Ww wwwwhpbh
o

sl el el et el el o

a
.

N el

]

Ry
W

o
s

R
&
s

S
e

&
&

R
&

&
s

el e

e
8
&

Layered

Il el

IPV11l

cooo0Oo OWOWWOWWYW

and

T
T
e

IP1l

Support

-»

RQDX3 Controller . .
KDAS50-Q Controller .
RUX50 UNIBUS Interface

BB WWWWWWWNN

o
.+
o
=

H@dhaw+dhflwrdk4wrdTeruT§4T
I
I

«
.
o
o
o

«
.
o
o
s

«
.
o
o+
&

New Device Support FeatuUres
. «
Summary of New Device Support
RD52 Fixed Disk
=« ¢« & o « o o
RD53 Fixed Disk
. . . . .
c
TK25 Magnetlc Tape Subsystem c
TK50 Magnetic Tape Subsystem

~I~J~JANWU

hiwrdhurrdTraTaT

Processor

-»

New

3.0

VERSION
”»

Controller

[]
[]
L4

el el el

[]

.
¢

-»

RESTRICTIONS

RQDX2

Pt b e
O
Ul
WO

SUPPORT

AND

FEATURES

MAJOR NEW FEATURES FOR RSX-11M-PLUS
DEVICE

e
I I S
R
e el e
L4
&
]
.
L
L
L
L]
L]
&
.
]
L
L]
[]
NN
DD N
L
[]
]
[]
®
.
.
L
|]
* []
L]
] LJ
|]
-

SOFTWARE

RSX-11M-PLUS

CHAPTER

1-13

1-14
1-14
1-14

1-15
1-15
1-17

-»

FeatuUres

o«

1-18
1-18

Commands

1-18

New DCL Qualifiers . .
Modified INITIALIZE/BAD BLOCKS
DCL Restriction
e o s+ o o s o s

command
e o + o

.
e

.
o

.
e

TDX

Installlng

1.12.2

1.12.3
1.12.4

Modifying the TDX Source File
Installing Tasks Permanently .
INDIRECT

BRU

o
«

o
o

o
o«

BRU

Features

Over

Not

System

Image

Restrictions

1-29
1-30

1-30

1-29

1-29
1-29
1-29

1-30
1-31
1-31

. o« o o o o o o« o
.
/NEWVERSION and /VERIFY
» » » » » » B
. »
» L
Image

e
o
.

BRU and BAD

RT-11

New

1-35

»
.

1-35
1-35
1-35

1-35
1-36

Foreign

¢«

o«

.«

Features

Feature

L4
&

. . .
Error

MESSAgEe

CRASH

DUMP

ANALYZER

o«

Restriction
FEATURES

L ]

NEW

1-37

1-37
1-38
1-38

New RMD Features

New and Modified VMR Keywords
.
New Data Terminal Emulator (DTE)
Management

1-36

1-37
1-37

1-38

l1.17.1.5

System

Kits

1-36
1-36

[]

Pre-Generated

Encryption

1-36

[]

1.17.1.6
1.17.1.7

Exercising

SHUTUP

Terminal

1.17.1.3
l.17.1.4

Devices

for

Password

New Options
ACNT

1.17.1.1

During a Copy Operatlon
Default File Types . .

Management

1.17.1.2

1-34
1-34

MANAGEMENT
System

New

SYSTEM

RESTRICTION

Message

1-34

Error

1.15.3.3
FMT
l.16

1.15.3.2

Information

Handling an Error
Image Mode Switch

and

FLX

]

FOImat

Feature

Copying

ReStriCtions

1.15.3.1

FLX

DOS-11

Disk

FLX

Mount

New

Supplementary

for

1.15.2
1.15.2.1

DOS""ll

1-34

1-33

1.15.1

1.15.2.2

Block

1-32
1-32
1-32

Boot

BRU

1.14.3.7
Change
FLX
1.15
»
&
»

1-32
1-32

Simultaneously
. . .
. . . . . . .
Files . . . .
Support for Multivolume Backups for Disks
.
Modified BRU Qualifiers
. . v o ¢ ¢« o o o &
/MOUNTED Qualifier Error Message . . . « « .
Additional Device Support
.
. .
« o
.
Memory Requirements for Booting Stand Alone

1.14.3.5
1.14.3.6

1-31
1-31
1-31

Supplementary BRU Information
Changes in Placement of HELP

1.14.3.4

1.17.2
1.18

&
&

]

@
s
&

s
&

.
-

L J

o«

Bootable

System

Run

o«

1-27
1-28

RestrictionNs

&
&

Sklpplng

1.14.3.2
1.14.3.3

1.17

¢
«

Bootable

l1.17.1

.«
¢

New

1.14.2.2

1.15.3

.«
¢«

Message

Restriction

Do Not Specify
Together »
L
L

l1.14.3.1

1-25

.
«

Error

1.14.2.1

1.14.2.3
1.14.3

1-25

1-25
1-25

BRU

1.14.1.1
l1.14.1.2
1.14.2

1-23

1-23
1-23
1-23

New

Indirect

1.14.1

¢«

New and Modified Directives
New Special String Symbols .

1.13.1.5
1.14

New Indirect Features
.
e o o o o e s e »
Changes to <TITYPE> Symbol .
e o s
New Delimiter for Symbols and Expre531ons

1.13.1.3
1.13.1.4

1.13.2

PROCESSOR

1.13.1.1
1.13.1.2

COMMAND

1-20
1-23

1-24
1-24

[

1.13

CYe
o
x|

TDX

Commands .
. .
Keywords .
.
.
Modified MCR Keywords

]

New MCR
New MCR

]

1.11.3
1.11.4

Numbers

Terminal

)

Version
Command

.E‘

FEATURES

[

DCL

]

DCL

Decimal

1.13.1

1-17

Network

1.12.1

1-17

NEW MCR

1.12

L
[]

w N

.
*
»

PROTECTION

SUPPORT
»

New

1.11.5

DEFAULT

directory

into

directory

See Chapter 3 of the RSX-11M-PLUS
Guide for more information.

1.4

Directories

directories do not already exist on the output disk.
the RSX-11M-PLUS System Generation and
1Installation
information.

1.3.13

for

that

the

target

System Generation

system

and

instead

and

of [1,54].
1Installation

INSTALLED COMMONS

Changes made

in the memory image of a common
can only
be
preserved
when
the
common is removed by installing the common with the /WB=YES
option.
If the common has been installed with the /WB=YES option, the

REMOVE
command writes the
task image file, replacing

reinstalled,
the
new
when it was removed)
15

common,

the

version

placed

with

original

the

its

memory.

1-10

changes,

into

its

original

image.
When
the
common
is
common (as it existed in memory

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
NOTE

The default behavior

they are removed.
version,

and

NEW LOGICAL

NAME

may

not

to write back

commons when

This is different from the previous
require

the

modification

applications dependent upon the old behavior.

1.5

Logical

name

support

FEATURES

has been

extended

for

RSX-11M-PLUS

Version

3.0.

This section contains descriptions of the following new features:
®

Assigning

Logical name

Using

logical

New directives

FCS

and

strings

translations

RMS-11

names

the

form ddnn:

support

for

logical

names

Logical Strings

1.5.1
On

logical

RSX-11M-PLUS

make logical

systems with extended

string assignments.

its equivalence

string

were

logical

name

support,

vyou

can

Previously both the logical name and

limited

the

form ddnn:.

You

can

now

use
any
alphanumeric
characters
for
both the logical name and its
equivalence string.
No colon
1is
required.
For
example,
you
can
assign the logical string SYSSLOGIN to DB3:[1l,1].

The system maintains logical name and equivalence name
following

logical

name tables:

pairs

the

Task logical name table -- contains logical name entries that

Session logical name table -- contains
that are local to a logged-in user

Group logical name table -contains
1logical
name
entries
that can be used by users having the same group number

System logical name table -- contains
accessed by any task in the system

l1.5.2

are

local

Logical

to a particular

task

logical

entries

name

that

entries

can

Name Translations

On RSX-11M-PLUS systems with extended logical name support,
has
been
made
1in
the
way
that
the system creates and
logical
system
device.
used.
logical

a
change
translates
logical name, the

assignments.

Previously, when you created a
immediately
translated
the assignment to the actual physical
No further translation was necessary
when
the
1logical
was
Now,
when
you
create a logical name, the system assigns the
name to the given equivalence name, but no translation is done

1-11

RSX*llM*PLUS

until

you

other

logical

For

‘and

use

example,

the

logical

name.
assigned to

names
if

SOFTWARE

you

make

the

ASN

DB3:=SY:

ASN

SY:[1,1]=SYSSLOGIN

issue

the

SHOW

LOGICALS

FEATURES AND

RESTRICTIONS

When you reassign a logical name, all
that logical name are also reassigned.

following

command,

logical

you

see

assignments

the

following

assignments

displayed:
SY

DB3:

SYSSLOGIN
If

you

use

SY:[1,1]

SYSSLOGIN,

DB3:.
If
SYSSLOGIN,

(Local,

Final,

(Local,

TT26:)

fully

TT26:)

translated

the

you reassign SY:
to DB2:, and then
SYSSLOGIN translates to DB2:[1,1].

physical

use

the

translates

device

logical

string

NOTE

When

RSX-11M-PLUS

creates,

logical
name assignments,
the logical name when used

displays,

the colons
as part of

are dropped
a Files-11

from
file

specification.

disable

final (no
switch.

recursive
further

1.5.3

Using

use

you

Logical

the

translation,

translation
|

Names

ddnn:

format

equivalence
string,
the
command, in that when the
string is fully expanded.

you

occurs)

the

can make
by

using

logical

string

the

equivalence

system

for

both

the

1logical

name

1is
assigned
as final.
1If

device specification, but that device is
not
receive
the
error
message:
"Device not

translates

the

command

anything

using

other

the

new

than

its

to
the
in
in

device,

functionality

ASSIGN and assigns the ddnn:
value
to
the
equivalence
example, if you make the following assignments
ASN

and

system mimics the o0ld behavior of the ASSIGN
logical name is
assigned,
the
equivalence
If the expanded string is the specification

you

interprets

Form ddnn:

of an existing system device, then the logical
name
that
device
string
and
the translation is marked
expanded string is
the
system,
then
system".

assignment

the /FINAL qualifier

name.

For

DR3:=YY:

ASN

[1,1]SYSLIB.OLB=SS:

ASN

SS:=XX:

and then

use

assignments

the

SHOW

LOGICALS

command,

you
TT26:)

displayed:

DR3:

(Local,

Final,

[1,1]SYSLIB.OLB
SS:

(Local,
(Local,

TT26:)
TT26:)

1-12

see

the

following

ONS

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTI
New Directives

1.5.4

logical name support in your own tasks:
CLONS and CLOGS

Create logical names

DLONS and DLOGS$

Delete logical names

access

can

you

The following new directives have been added so that

Translate logical names
Provide recursive translation

TLONS and TLOGS
RLONS and RLOGS

match creation,
The xxxN$ form of each directive performs exact
form of each
xxxGS
The
names.
al
logic
of
ion
delet
translation, and
the P/OS
with
y
ibilit
directive has been provided to allow compat
operating

system.

on the end
On P/0S, if a logical name is used as a device, the colon
l name. On
logica
the
of
part
a
ered
consid
1is
string
of the device
d in
include
not
is
and
er,
delimit
a
RSX-11M-PLUS, the colon is only
both
on
ed
includ
are
ives
direct
xxxG$
the
Thus,
the 1logical name.
single
a
allow
to
s
systems but have slightly different functionalitie
task to run on both systems.

If compatibility with P/0OS is desired,

the

use

form

xxxG$

the

trailing colons and leading zeroes in device
directives and
logicals. For example, specify DR0O05: as opposed to DR5:. On P/OS,
the xxxG$ directives will work the same way as the xxxN§ directives in
include

that the exact string that is provided will be used.

On RSX-11M-PLUS,

logical name, and will eliminate any leading zeros in

the

will

directives

xxxGS

remove one or two trailing colons from a
-

string.

the ddnn:

number

The following directives are used for file system access:
ACHNS

PFCSS
PRMSS

The ACHNS directive performs the same function as the current ALUNS
However, the ALUNS directive accepts input only in the
directive.
The
form ddnn:. The ACHNS directive accepts any string as 1input.
and
n
expansio
logical
e
extensiv
perform
es
directiv
PRMS$
PFCSS and
RMS.
and
FCS
to
merging, and were included to minimize the code added
See the RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual for
more information about these directives.

FCS and RMS-11 Support for Logical Names

1.5.5

File Control Services (FCS) and Record

have

been

following

to support logical names.

DB3:[1,1]

SYS:

command:

ASSIGN

you can access files in DB3:[1l,1]

See the

Management

modified

RSX-11M/M-PLUS

1I1/0

(RMS-11)

Services

For example, with the

using the logical name SYS:.

Operations

Reference

information on using logical names for file access.

Manual

for

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.6

EXECUTIVE

This section describes new features and supplementary information
the

Executive

l1.6.1

The

New

RSX-11M-PLUS

Executive

supports

the

New directives

High-level

following

language

New Directives

Executive

Version

3.0.

for

Features

®@

l1.6.1.1
The

supports

new

features:

interface

the

following

new directives:

Assign Channel (ACHNS)
Create Logical Name (CLONS$, CLOGS)
Delete Logical Name (DLONS$, DLOGS)
Test for Specified System Feature (FEATS)

File Specification Scan (FSSS)
Get Default Directory (GDIRS)
Parse FCS (PFCSS$S)
Parse RMS (PRMSS)
Recursive Translation of Logical

Name

(RLONS,

RLOGS)

Receive By Reference or Stop (RRSTS)
Set Default Directory (SDIRS)
Test for Specified Task Feature (TFEAS)
Translate Logical Name (TLONS$, TLOGS)

l1.6.1.2
All

High-Level
the

language

l1.6.2

Language

Interface -

Executive directives

can be

used

Supplementary

from

that

FORTRAN

Executive

and

can be
from

called
other

from

1is

still

Privileged tasks

Changes

made

high-level
languages.

Information

This section describes information
from
the
previous
applies
to
the
Executive.
Although this information

Version 3.0,
it
following topics:

high-level

wvalid.

Executive

This

data

information

structures

version that
is not new for

includes

the

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

1‘6'2‘1

Privileged Tasks -

This section describes privileged tasks and the Executive.

queued

The module DREIF makes special checks on send packets

a task to determine whether the UCB address in the packet

The purpose is to allow data
is that of a virtual terminal.
1is a virtual terminal.
to be sent to a slave task whose TI:

If a user's task receives specially formatted send packets,
should be built with the /-SE switch.
slave task
the
then
from
This sets the T3.NSD bit that prevents the new check
interpreting

the UCB address

field

the packet.

For directives that take a TCB address in RO as input, if
is greater

Because

than

140000,

the

definitions

the TCB

is mapped

implementation

through APR 6.

1/D-space,

user

mapping register symbols

wuser

the

RO
the

(such as

oOr
(UINARx)
instruction
UISARO) may point to either of the
A similar situation exists with
the data (UDSARx) registers.
code must
Privileged
the kernel mapping register symbols.

not
locally
define
these symbols or assume they refer to a
particular mapping register.

that

Some Executive routines

not

were

previously

the

Directive Partition may have been moved to this partition for

Executive
that calls
code
privileged
Thus,
Version 3.0.
ensure that the entry
to
checked
be
should
points
entry
points are still

accessible.

Drivers that address check their own

change

SACHKW/SACHKB/SACHRO

These new

partition

l.6.2.2

address

I/O count.

check

have

buffers

will

correctly

maintain

to $CKBFW/S$CKBFB/$CKBFR/$CKBFI.

routines

the

Changes Made to Executive Data Structures -

This section describes changes made to Executive data structures.
which previously
T2.TI0O,
To enhance buffered I/0, the bit
for only one buffered I/O per task, has been changed
allowed
to the byte T.TIO, which allows a task to queue many buffered
This is one of the many changes
I/0 requests simultaneously.

made to the buffered

I/0 algorithm.

Tasks that examine task headers must be altered, because

the

privileged tasks assign LUNs by loading the UCB address

into

headers
the

LUN

may

longer

the

header,

primary

pool.

Since many

table

header

enables them to work until the tasks can be

upgrading to Version 3.0.
external

this may be a problem when

Installing these tasks without

1-15

RSX-11M~-PLUS SOFTWARE FEATURES AND

modified to support
support

.IF

external

by entering

RESTRICTIONS

headers.

the

following

You

can

add

this

commands:

X$ SHDR

MOV

SSAHDB, KISAR6

;

MAP

MOV

SSAHPT,R2

;

GET ADDRESS

HEADER

. IFF

; X$SHDR

MOV

SHEADR, R2

;

GET ADDRESS

HEADER

.ENDC

; XS$SHDR

<{Header manipulations

using

TASK

HEADER

R2>
NOTE

These instructions must be executed at
system
state
and
must
not
be
mapped
through
APR6.
Also
the
references to @SHEADR require no
modification.
This
code is necessary only to address header offsets other
than the saved stack pointer.
If

the

task

Prototype

has

TCBs

external

(for

tasks

header,

whose

P.HDR

name

the

PCB

the

form

1is

now

...XXX)

can
now
reside in secondary pool.
Therefore, any task that
scans the PCB list should be modified to check for P2.SEC
in
P.ST2.
If
set,
the
TCB
corresponding
to that PCB is in
secondary pool.
A task that scans the
installed
task
1list
should also be modified to scan $PTCBL, which is the listhead
of

the

secondary

pool

prototype

TCBs.

The word at offset 0.STAT+2 of the offspring control block
used

to contain

which

only

the

the exit

The

filled

secondary

in whenever

word

status region of

used.

CLI

Note

support

individual

the word

the

the OCB may be

addition of alternate

1 -

status,

U.MUP of

Previously,

that more words

used

has

the

changed

in
future.

how

users.
the

TKTN abort code,

the offspring exits.

O.STAT was

are associated with
Bits

exit

CLIs

terminal's UCB

are

used

to
identify the CLI associated with that terminal.
The bits
form an
offset
into
a
table
located
at
SCPTBL
in
the
Executive
module
SYSCM.
This module contains a pointer to
the CPB (CLI Parser Block) for the CLI.
Since
only
4
bits
are
used
to
form
this offset, the system is limited to 16
CLIs.

Tasks

check

that

use A.TCB

a new bit,

A.TCB

contains

rather

than

This means
access the

the

(not

AS.PRO

to be confused

in A.STAT.

32-word

the virtual

physical

bias

with

this bit
of

address of the TCB

that tasks will have
TCB where needed.

the

A.TCBL)

is set,

prototype

must

then

TCB

in primary pool.

remap an APR

order

The following Accounting data structures have ‘changed:

the

User Account Block (UAB), the System Account Block (SAB), and
the
Mount
Transaction.
Tasks
can
differentiate
between
Version 1.0 and Version 2.0 by the length of the block.
°

1-16

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.7

DISK DATA CACHING

Disk data caching

I/0

performance

directed

that

is a feature on RSX-11M-PLUS systems

the

reducing

to a disk.

enhances

physical I/0 requests

number

on pregenerated

The disk data caching option is selected by

default

generation option for RSX-11M-PLUS systems;
the full-functionality Executive.

it is included as part

data

Disk

systems.

RSX-11M-PLUS

caching can be chosen as a system

disk.

Disk data caching must be activated explicitly for a

activate,

override,

disable,

using the commands discussed

System Management Guide.

1.8

USER-DEFINED

DEFAULT

monitor,

Chapter

You

can

modify disk data caching
of

the

RSX-11M/M-PLUS

PROTECTION

program
Previously, if protection was not explicitly provided through
control,
protection
was
derived
from a
volume default defined by

for
Now, because of support
either the INITIALIZE or MOUNT commands.
user-defined default protection, you can use the MCR command SET /DPRO

or DCL

command

define

vyour

protection

value

SET

default

PROTECTION/DEFAULT

protection

file

define

default

file

the

Account

File

assigned to files you create.

Maintenence
Program
(ACNT).
RSX-11M-PLUS
the
or
Manual

wusing

You can also

See
the RSX-11M/M-PLUS MCR Operations
more
for
Manual
Command Language

information.

1.9

NAMED DIRECTORY SUPPORT

Named directory
named directories.
for
support
RSX-11M-PLUS has
support means that you can have alphanumeric directory names such as
named directories,
get
To
[DIRECTORY] or [NUMBER2].
command SET /NAMED or DCL command SET DEFAULT/NAMED.

use

the

MCR

still nonamed directory behavior.
is
default named directory behavior by using the

The default for RSX-11M-PLUS

However,

account

you

det

can

file maintenance program.

Also, a differentiation has been made between the protection UIC and
In named directory mode, the MCR command SET
the default directory.
MCR
The
/UIC and DCL command SET UIC modify only the protection UIC.
command SET /DEF and DCL command SET DEFAULT change only your default
directory.

Because of this change, some oldstyle command files that

/UIC or SET DEFAULT commands will not work properly.

contain

SET

Before executing

such command files, enter the MCR command SET /NONAMED or DCL
command
commands inform the system to translate
These
DEFAULT/NONAMED.
SET
the commands in the command file according to their original meanings.
SET /NONAMED or SET DEFAULT/NONAMED commands are necessary when
The
installing layered products.
See the
RSX-11M/M-PLUS
MCR
Operations
Reference Manual or the RSX-11M-PLUS Command Language Manual for more
information.

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

1.10

This

DCL

section

describes

new

Command

Language

(DCL)

1.10.1

New DCL

Features

DCL

supports

the

following

features
and
a
restriction
RSX-11M-PLUS Version 3.0.

new

New

DCL

commands

New

DCL

qualifiers

Modified

1.10.1.1

Digital

features:

INITIALIZE/BAD BLOCKS

New DCL Commands

for

command

The following are new commands for DCL:
ANALYZE/MEDIA[/qualifier([s]]

/ALLOCATE=1label
/BADBLOCKS
/BADBLOCKS/NOEXERCISE
/ [NO]JEXERCISE[=(n,m)]
/OVERRIDE
/RETRY
/SHOW
The

ANALYZE/MEDIA

the

number

of bad

if bad blocks
locations for

command
blocks

exist
use by

on
the

allows you
on a disk.

to identify and determine
ANALYZE/MEDIA determines

a
disk
volume
and
records
BACKUP and INITIALIZE commands.

their

DEFINE [/qualifier[s]]
/FINAL
/GLOBAL

[ :g]
/GROUP
/LOCAL
/LOGIN
/SYSTEM
/TERMINAL:ttnn:
/TRANSLATION ATTRIBUTES:TERMINAL
The

DEFINE command

name,

logical

all

name.

equates

logical

part

file

name

physical

specification,
or

device
another

DELETE/DIRECTORY

The

DELETE/DIRECTORY command deletes a directory on a Files-11
and
removes
its
name
from the volume's Master File
Directory (MFD).
volume

RSX-11M-PLUS SOFTWARE}FEATURES AND RESTRICTIONS
SET

FILE[/qualifier([s]]

|
/END OF FILE: (BLOCK:n,BYTE:n

/ENTER:synonym filespec
/REMOVE
/REWIND
/TRUNCATE
/ [NO]J]WARNINGS

The
SET

SET

FILE

command

establishes

certain

file

characteristics.

HOST

The
SET

SET

HOST command

connects your

terminal

another system.

PASSWORD

The
SET

SET

PASSWORD

command

allows

you

change

your

password.

UIC

The SET UIC command
(UIC).

changes

your

User

Identification

Code

SHOW CACHE[/qualifier]
/DEVICE=ddnn:
/RATE:n
/REGION=name
The
SHOW
CACHE
command
allows
information on data caching.
SHOW

display

system

HOST

The

SHOW

which
SHOW

vyou

HOST

your

command

terminal

displays

the

name

the

processor

name

assignments.

currently connected.

LOGICALS[/qualifier([s]]

/ALL

/GLOBAL
/GROUP [:qg]
/LOCAL
/LOGIN
/SYSTEM
/TERMINAL: ttnn
The
SHOW

SHOW

command

displays

logical

PROTECTION

The

SHOW

file
SHOW

LOGICALS

PROTECTION

protection

command

displays

your

code.

personal

default

UIC

The

SHOW UIC

(UIC).

command

displays

your

User

Identification

Code

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

1.10.1.2
The

New DCL Qualifiers -

following

are

new qualifiers

for

DCL:

APPEND[/qualifier(s]]
/NOWARNINGS
/REWIND
/SHARED

ASSIGN[/qualifier[s]]
/FINAL
[g]
/GROUP:
/TRANSLATION

ATTRIBUTES:TERMINAL

COPY[/qualifier(s]]
/ALLOCATION:n[.]
/NONEW VERSION

/NOWARNINGS

/OVERLAY
/PRESERVE_DATE
/REWIND
/SHARED

CREATE/DIRECTORY [/qualifier]
/NOWARNINGS
/OWNER _UIC: [uic]

DEASSIGN|[/qualifier[s]]
/GROUP[:qg]

DELETE [/qualifier([s]]

/NOWARNINGS

DIRECTORY [/qualifier[s]]
/NOWARNINGS
/REWIND

DISMOUNT [/qualifier[s]]
/TERMINAL:ttnn:

INITIALIZE[/qualifier([s]]
/BAD BLOCKS:arg

NOAUTOMATIC

(AUTOMATIC,MANUAL)
(OVERRIDE,MANUAL)

/DENSITY:arg
HIGH

LOW

/LABEL:VOLUMEMACCESSIBILITY:"C"
/PROFESSIONAL

INITIALIZE/UPDATE[/qualifier([s]]
|

/LABEL:newvolumelabel
/PROFESSIONAL

INSTALL[/qualifier(s]]
/FAST MAP
/ [NO]INTERPRETER
/[NOJRESIDENT HEADER

/TRANSLATION ROUTINE:n
/ [NOJWRITE BACK

1-20

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
LINK[/qualifier([s]]
/CODE: (arg[s])
CLI
FAST

MAP

/ [NO]PRINT

MOUNT [/qualifier[s]]

/[NO]JCACHE [:arg([s]]

/OVERRIDE:arg
IDENTIFICATION
/PROCESSOR:arg
UNIQUE

PRINT[/qualifier[s]]
: TOMORROW
/AFTER
[NO]WARNINGS

PURGE [/qualifier([s]]
/NOWARNINGS

REMOVE [/qualifier]
/TRANSLATION_ROUTINE:H

RENAME [/qualifier([s]]
/NOWARNINGS

RUN[/qualifier|[s]
/[NO]I0O PAGE
/READPARTITION:parname

/ [NO]SLAVE

SET DEFAULT[/qualifier]
/ [NO]NAMED DIRECTORY

SET DEVICE[/qualifier([s]]
/ [NOJCACHE [:arg[s]]
[:n]
name]
[ :parname]
:CREATE [:reg
:REGION [:regname]
: [NO]JDIRECTORY[:n]
[ : n]
: [NOJOVERLAY
: [NO]JVIRTUAL[:n]
[ :n]
: [NOJREADAHEAD
: [NOJLOGICAL[:n]

SET PROTECTION[/qualifier]

/ [NO]DEFAULT

SET SYSTEM[/qualifier([s]]

/NETWORK UIC
/POOL/LIMITS:arg
HIGH=n
LOW=n
MINIMUM SIZE=n
TASK_PRIORITY=n

SET TERMINAL[/qualifier([s]]

/ [NOJADVANCED VIDEO
I_
CRT
/ [NO]JANS
/[NO]BLOCK MODE

/ [NO]CONTROL=C

/[NO]DEC_CRT
/ [NO]DTCO1
/[NOJEDIT MODE
/ [NOJHOSTSYNC

(continued

on next

page)

RSX-11M-PLUS

SET

SOFTWARE

TERMINAL[/qualifier[s]]

FEATURES

AND

(Cont.)

/ [NO]INQUIRE
/LAS50

/[NO]JLA210
/ [NOJLNO3
/[NO]JLQPO2
/ [NOJLQPO3
/[NO]PARITY:arg
ODD
EVEN

/ [NO] PASTHRU
/[NO]JPRINTER

PORT

/ [NO]PRO SERIES
/[NO]REGIS

/ [NO]SOFT CHARACTERS
/ [NO] TRANSLATION ROUTINE:n

/ [NO] TTSYNC
/VT200 SERIES
SHOW

ASSIGNMENTS|[/qualifier(s]]

/GROUP
[ :qg]
/TERMINAL:ttnn:
SHOW DEVICE[/qualifier[s]]

/ [NO]CACHE
SHOW SYSTEM[/qualifier[s]]
/NETWOR
UIC
K
/POOL/LIMITS
SHOW

TASKS[/qualifier([s]]

/DEVICE:ddnn:
SHOW

TERMINAL|[/qualifier[s]]

/ [NO]JADVANCED VIDEO
/[NO]JANSI CRT

/ [NO]BLOCK MODE

/ [NO]JCONTROL=C
/ [NO]DEC_CRT
/[NO]DTCO1
/ [NOJEDIT MODE
/ [NOJHOSTSYNC
/LAS50
/[NOJLA210
/ [NO]LNO3

/ [NOJLQPO02

/ [NOJLQPO3
/ [NO]PARITY

/ [NO] PASTHRU

/[NO]PRINTER

PORT

/ [NO]JPRO SERIES

/ [NO]REGIS
/ [NO]SOFT CHARACTERS

/ [NO]TTSYNC

/VT200_ SERIES

RESTRICTIONS

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.10.1.3

Modified INITIALIZE/BAD_ BLOCKS command -

it is
The DCL command INITIALIZE/BAD BLOCKS has been modified so thatfollows:

consistent with the MCR command INI /BAD.

the

MCR

The INIT/BAD:NOAUTOMATIC command has been added to DCL.
is equivalent to the MCR command INI /BAD=[NOAUTO].

The

The changes are as

INIT/BAD:OVERRIDE

command INI /BAD=[OVR].

command

1is

equivalent

Previously, it translated to the MCR

command INI /BAD=[NOAUTO].

DCL Restriction

1.10.2

This section describes a restriction for using DCL on RSX-11M-PLUS.

format

Console

Routine

The following DCL commands do not accept a logical name in

other than ddnn:

for a device name:

ALLOCATE
DEALLOCATE
MOUNT

SET DEVICE
SHOW DEVICE
SHOW TERMINAL

DISMOUNT

1.11

'NEW MCR FEATURES

This section describes new features for the
(MCR)

on RSX-11M-PLUS Version 3.0.

Monitor

MCR supports the following new featureé:
e

Decimal version numbers

Network command terminals

New MCR commands

New MCR keywords

Modified MCR keywords

~1.11.1

Decimal Version Numbers

If you select support for decimal
generation, you can use them in

version numbers during system
file specifications. The system

increments decimal version numbers in the same way as octal ones.

1.11.2

Network Command Terminal

(NCT)

NCT provides a means for establishing a remote

connection

from

your

terminal to other systems in a network. Use either the MCR command
SET /HOST, or DCL command SET HOST, to establish a network connection
to a remote node. These commands allow for transparent connections

between RSX systems, or between RSX and VAX/VMS systems.

RSX-11M-PLUS

l1.11.3

SOFTWARE

FEATURES

AND

RESTRICTIONS

New MCR Commands

‘The following are new MCR commands for Version 3.0:
ANCILLARY CONTROL

DRIVER

(ACD)

The

ACD
command
loads
and
unloads
routines so that terminals that conform
use the DIGITAL Multinational Character

DEFINE

LOGICALS

The

DFL

l.11.4

The

defines,

during

New MCR

Keywords

ASSIGN

are

new

deletes,

systems

support

following

to
Set

other

translation

standards

can

(MCS)
.

(DFL)

command

assignments

character

system

that

and

select

displays

extended

generation.

MCR keywords

for

Version

logical

1logical

name

3.0:

/FINAL

/GROUP
CLI/ CTRLC

HOME /POS

INITIALIZE
INSTALL

/POS

/FMAP

/WB
LOAD

/VEC

MOUNT /[NO]JCACHE

SET /[NO]ANSI
/ [NO]AVO

/ [NO]BLKMOD
/ [NO]CACHE
/ [NO]DEC
/DEF
/ [NO]DPRO
/ [NO]JEDIT
/HOST
/ [NO]HSYNC

/INQUIRE
/[NO]NAMED
/ [NO] PARITY
/PASSWORD
/ [NO] PASTHRU
/[NO]PRINTER
PORT
/ [NO]REGIS
/[NO]SOFT
/ [NO] TTSYNC
UNLOAD

/VEC

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
Modified MCR Keywords

1.11.5

The following MCR keywords have been modified for Version

3.0:

MOUNT /FPRO
/PRO

SET /BUF
/TERM

1.12

TDX

TDX (a catch all task)
This section includes information about using
section includes the following

on RSX-11M-PLUS Version 3.0.

This

topics:

~—

Installing

TDX commands

Modifying the TDX source file

Installing tasks permanently

1.12.1

TDX

Installing TDX

and abbreviate
The TDX facility allows you to run uninstalled tasks
name ...CA. 1is
task
the
with
Any task installed
command names.
nized command,
unrecog
an
receives
MCR
If
task.
all
catch
a
treated as
d line to
comman
the
passes
and
it searches for a task with that name
TDX.

To use TDX as the catch all task for your system, install it by

wusing

the following command:

INS S$TDX/TASK=...CA.

of
Once installed, TDX checks the typed command against its d1list
a
into
comman
the
ates
transl
TDX
match,
ds
comman
If the
commands.
TDX commands

The following section describes the

valid MCR command.

and their corresponding MCR commands.

1.12.2

TDX Commands

TDX commands
qualifiers.

a shorter way of specifying MCR commands and
following table 1lists the TDX commands, their MCR

are
The

translations, and the definition for each command.

TDX Command

MCR Translation

Command Meaning

ATS

ACT /ALL

Displays the names of all
active

tasks

the

system.

ATS ttnn:

ACT /TERM=ttnn:

Displays the names of all
the
on
tasks
active
specified terminal.
(continued

on next page)

RSX-11M-PLUS

TDX

Command

CHD

SOFTWARE

FEATURES

MCR TranSlation
SET /DEF

SET /DEF=[g,m]

AND

RESTRICTIONS

Command Meaning
Displays
default
terminal

the current
directory
TI:.

directory mode,

named

changes

the

for

current

default
directory to the
directory specified.
In
nonamed
directory
mode,
changes

the

default

directory

current
and,

privileged,
protection UIC.
CHU

SET

/UIC

Displays
UIC

the

for

protection

terminal

and,

if
directory
default
CHU

SET/UIC=[g,m]

TI:

nonamed

mode,

UFD.

named

if
the

the

directory mode,

changes
protection
specified

the
UIC

current
the UIC

(privileged

command) .

nonamed

directory

mode,
changes
default
directory
if
privileged,
the

the
and,
protection
CLR

UIC.

—

Clears

the

issuing
terminal's
sets

the

Returns

EXSSUC
a

CRT

not

CRE

file

PIP

file=TI:

0,0.

status

the

terminal

EXSWAR

1is
is

CRT.

Creates

new

without
editor.

CVT val

and

exit

if
and

screen
cursor

file

invoking

Evaluates

arithmetic

expression, converts that
expression into different
formats,
the

and

formats

terminal.

input

nn,nn)
or

displays all
on
your

CVT
octal

accepts
(nnn or

decimal
(nnn.
words oOr

nn.,nn.)

bytes,
hexadecimal
numbers ($nnnn), radix-50
(3ccc) or
ASCII
('c
or.
"co)
characters,
or
arithmetic
expressions

(continued

page)

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

Command Meaning

MCR Translation

TDX Command
DEL

file(s)

PIP

DIR

[file[s]]

PIP

the specified

Deletes

file(s) /DE

file(s).

Displays a directory
listing at the terminal.

[file[s]]/LI

Displays information
about all
the
1logged-in
terminals on the system.

DLG

DEV /LOG

DLN

NCP SHOW

FRE

PIP /FR

Displays the amount
available space
on

FRE ddu:

PIP ddu:/FR

Displays the same
‘information as FRE

KNOWN

NODES

Displays

all

DECnet

known

nodes.

of
SY:,
contiguous
largest
the
space on SY:, the
number
file
available
of
headers, and
the
number
of file headers used.

for

specified device.
Deletes all but the
latest version of a

file(s) /PU

PUR file(s)

PIP

SHQ

QUE/LI

SYS

SET /SYSUIC

Displays

system

1.12.3

all

the current

UIC.

Displays the current
version of TDX.

TDX

TYP

information

about all entries
print queues.
Displays

file.

Prints files on
terminal.

PIP TI:=file(s)

file(s)

your

Modifying the TDX Source File

You may want

add

other commands

TDX

modifying

the

source

Routines for the commands are at the end of the
[24,10]TDX.MAC.
file,
after
making
additions,
To reassemble the source file
source file.
To rebuild TDX, follow
file located in [24,24].
the
TDXASM.CMD
use
tasks,
described
in
the
nonprivileged
building
the procedure for
RSX-11M-PLUS System Generation and

Installation Guide.

1-27

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
If the command you enter does not match a TDX command,

use

one

examples,

the

letters xxx

represent the

first

TDX attempts to

(In the following

of the following two MCR command options:

three characters of your

.)
command

MCR> RUN

$xxx/TASK=xxxTnn/CMD="paramsS..."

task.
a
removes
then
and
runs,
installs,
option
This
Your
"Params..." represents the command line that you enter.
command line cannot exceed 39 characters,
because
TDX
adds
other
characters
to
this
1line.
If you want this option,
place the following command in your LOGIN.CMD file:
SY:=7Z7Z1:

ASN

@SY:[loginuic]xxx.CMD or

MCR>

MCR> @QLB:[libuic] xxx.CMD or
MCR> @SY:[loginuic]CATCHALL.CMD
MCR> QLB:[libuic]CATCHALL.CMD

For

this

option,

TDX searches

for

one

the

@[...]xxx.CMD

Once TDX
the order indicated.
1in
files,
command
indirect
locates one of these files, the search stops.
You can design

indirect command file to perform a variety of functions,

the

such as

installing

tasks,

providing HELP,

1issuing

error

messages.

To use this option,

ASN

place

the

following

command

1in

your

file:

SY:=7272:

Note that RSX-11M-PLUS Version 3.0 contains a sample indirect

command

[3,54]CATCHALL.CMD.

file,

The option TDX uses depends on whether

your system.

exist

272:

your LOGIN.CMD file.

the logical

Note that the presence of the

masks the presence of the ZZ2:

assignment.

TDX will not exercise either option.

You can select an option by

system

startup

devices

ZZ1:

You can assign one of these devices in

the

placing

ZZl:

assignment

If no assignment is made,

following

command

the

file:

ASN SY:=ZZn:/GBL

where n equals

1 or 2, depending upon which ZZn option you prefer.

TDX issues the following message if the command

match a TDX command or
MCR --

l1.12.4

Task

not

1Installing

if TDX cannot

you

enter

does

not

locate the necessary task.

in system

Tasks Permanently

You may want to install some tasks permanently, rather than invoke TDX
to install them on an as-needed basis.
install the following types of tasks:
@

Tasks

requiring

larger

increment

is advisable to permanently

than

the default

RSX-11M-PLUS

SOFTWARE

FEATURES AND

RESTRICTIONS

frequently

Tasks

used

Tasks

requiring

commands

longer

than

characters

See the description of the INSTALL command in the

Operations Manual

for more

RSX-11M/M-PLUS

INDIRECT COMMAND PROCESSOR

1.13

This section contains new features and
RSX-11M-PLUS Version 3.0.

1.13.1

a restriction

for

Indirect supports

the

following

New delimiter

New and modified directives

New special

New

expressions

symbols

to <TITYPE>

Symbol

The <TITYPE> symbol supports two new terminal types.
corresponding

PC3xx
VT2xx

series
series

octal

The

1.13.1.3

string

as well as quotation marks (") can

symbols and

expressions.

New and Modified Directives -

following

directive

type

1is

for Symbols and Expressions -

Pound sign characters (#)
for

and

New Delimiter

as delimiters

types

codes are:

Also, the <TITYPE> symbol is evaluated whenever the terminal
requested, not just when Indirect is initialized.

1.13.1.2

Processor

message

error

Changes

symbols and

string

Indirect Command

features:

Changes

for

the

symbol

new

1.13.1.1

their

Indirect

New Indirect Features

This section describes new features for
(Indirect) on RSX-11M-PLUS Version 3.0.

The

MCR

information.

is new

for

Version

.TRANSLATE

Translates logical names.

.FORM

Acts as

3.0:

infterface to FMS-11

forms driver.

used

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
The following
a

file

directives

device

.CHAIN

logical

name assignments as a

part

specifications:
.OPEN

. TESTDEVICE

. OPENA

. TESTFILE

.OPENR

1.13.1.4

The

New

Special

String

Symbols

following

special

string

symbols

are

systems

with

contains

<SYTYP>

<VERSN>

1.13.1.5
The

the

contains

the

Contains

example,

RSX-11M-PLUS).

Contains

the

example,

3.0).

string

following

error

message

AT.

Logical

This

error

message

translation

1.13.2

name

Indirect

of
a

appears

section

contains

The

@/LB:module

command

line

name

referenced

truncates
the
name
Indirect returns the

Indirect

assumes

system

version

type

(for

number

(for

3.0:

error
an

the

error

occurs

during

the

.TRANSLATE directive.

restriction

does

not

or
from
within a command
from within a library.

the module

the

Version

when

name

string.

directories,

Restriction

This

prompt
issued

for

directories,

named

system's

translation

logical

named

UIC.

describing

new

3.0:

directory

for

default

current

Message

for

support

user's

Version

default

without

Error

for

support

user's

systems

New

new

for

work

file.

when

greater

File

Not

that

the module

problem

than

to 6 characters.
When a
following error message:

AT.

using

Indirect

issued

occurs

name

1is

when

characters,

file

CLI

Indirect

truncated,

Found
name

you

wish

reference

characters
1long, since the module names are truncated to
by the librarian utility when the files are included
1in

only

6 characters
the
command

library.

This

Indirect

- Version
To

avoid

behavior

will

problem,

always

remain

restriction

for

RSX-11M-PLUS

3.0.
this

specify

module

name

characters

less, when issuing the @/LB:module command line.
Also, do not use the
@/LB:module command line unless you plan to include command files in a
command library.

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.14

BRU

This section describes new features, restrictions,

information

for

Version

3.0.

1.14.1

New BRU

and

supplementary

the Backup and Restore Utility (BRU) on RSX-11M-PLUS

Features

BRU supports the following new features:
e

Skipping over a bootable system

New device support

image

Skipping Over a Bootable System Image -

'1.14.1.1

BRU can detect and automatically skip over

bootable

system

image

BRUSYS) when appending to or restoring from a magnetic
example,
(for
allows you to place a BRU backup set onto a
feature
This
tape.
that contains a bootable system image at its beginning
tape
magnetic

and also eliminates the need for a separate magnetic
the bootable

system

When BRU is used to append to or restore from a magnetic

will

the

over

this

1.14.1.2

tape,

feature.

New Device Support

BRU supports the following new devices:

Device

Mnemonic

TK50 cartridge tape drive
RD53 fixed disk

MU:
DU:

BRU Restrictions

1.14.2

there

delay for rewinding the magnetic tape and skipping

is
feature
this
Otherwise,
image.
system
See the Section 1.14.2.2 for a restriction regarding the

bootable

transparent.

use of

small

containing

tape

image.

The following restrictions apply to BRU:

Do not specify /NEW VERSION and /VERIFY together.

Bootable system image restrictions

Do not use BRU and BAD simultaneously.

RSX-11M-PLUS

1.14.2.1

Specifying

Not

"conflicting

verify
a
since the

/NEW VERSION

you

Also,

the

leave
image

version

Bootable

1is

and

these

and

RESTRICTIONS

/VERIFY

Together

qualifiers

together,

error message.
The reason
operation when the /NEW VERSION

the

files

numbers

System

Image

first backup
image,
you

the

LABEL

bootable

switch

the

Restrictions

set on
must

together

receive

is that BRU cannot
qualifier is used,

device

the

input

may

device.

not

a magnetic tape that
specify
/REW/APPEND.

ignored

system

vyou

output

files

the magnetic tape positioned
and then specify /APPEND.

the /TAPE

there

wuse

AND

qualifiers"

When placing the
bootable
system
simply
system

FEATURES

/NEW VERSION

restore
version numbers

correspond

1.14.2.2

Specify

the

illegal.

SOFTWARE

the

during

end

contains
a
You cannot

the

bootable

restore operation

1if

image at the beginning of the magnetic

tape.

1.14.2.3

not

Not

Run

RSX-11M-PLUS
run

BRU

space and
results.

1.14.3

and

Version

and

running

BRU

BAD

both

BAD

3.0

Simultaneously

BRUSYS

stand-alone

simultaneously.

tasks

Supplementary BRU

the

BRU

same

and

time

system,
BAD

use

yields

you

should

common

buffer

unpredictable

Information

This

that

applies

3.0,

section contains
information
from
the
previous
version
to BRU.
Although this information is not new for Version
is still valid.
This section includes the following topics:
®

Changes

Support

for multivolume backups

Modified

/MOUNTED qualifier error message

Additional

Memory

requirements

Change

1.14.3.1
For

Changes

Version

2.0

placement

BRU

HELP

files

for

disks

qualifiers

device

support

for booting

boot block

for

disk

stand-alone BRU

copying

in Placement of HELP Files -

and

Version

3.0

distribution

placed
on
the
second,
rather
than
the
magnetic tape kits or disk volume for
RKO07
these
HELP
files
to
your
system
disk
required on your part.
|

kits,

the

HELP

files

are

first, BRU backup set for
kits.
The
transfer
of
occurs without any action

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
The BASTART.CMD file for the RKO7 distribution kit has been

modified.

This command file invokes PIP in order to copy the HELP files from the
second

RK07 disk

1.14.3.2

to your

system disk.

Support for Multivolume Backups for Disks -

BRU performs multivolume backup operations

for disks.

You can copy

disk onto several smaller disks or several smaller disks onto a

large

mounted large disk.

format,

not

However,

Files-11.

the disks to which you copy are

BRU

This means that, before you can read what is

saved on the disks, you must restore them with BRU.
This
similar to magnetic tape backup and restore operations.

process

The

following

new

qualifier

multivolume disk backups:

has

been

added

BRU

1is

perform

/IMAGE: SAVE
: RESTORE

This qualifier

specifies that you want to do a

backup or restore operation.

multiple

disk-to-disk

If you are doing a backup operation, you

must specify the SAVE option on the command line.
If you are doing
a
restore
operation, you must specify the RESTORE option on the command
line.

1.14.3.3

Modified BRU Qualifiers -

Because of the

addition

multivolume

disk

backup

meanings of the following BRU qualifiers have changed:

support,

/APPEND

Directs BRU to append a backup set

/BACKUP SET:name
o

Specifies the name of the backup
set
to
be
placed
on
magnetic
tape
or
disk.
For a
mounted input or output disk during an
1image
or restore operation, you can specify
backup
the
full
backup
set
file
name
with
the
/BACKUP_SET qualifier.

/DIRECTORY

Lists, at your
or
files
on

the

volume to the last backup set on
disk
input
the output tape, or on the output disk if you
are using the /IMAGE qualifier.

disk

/JINITIALIZE

from

the

terminal, the backup set names
the specified magnetic tape or

volume.

Specifies that you
want
to
initialize
the
output
disk
during
a
tape-to-disk
or

disk-to-disk

operation.

/INVOLUME

Specifies the volume label of the input disk.

/MOUNTED

Allows you
is mounted

/NEW _VERSION

Resolves

to back up files from a disk
as a Files-11 volume.

file specification conflicts,

occur
during
either
backup
operations to a mounted disk.

that

which
restore

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

/SUPERSEDE

Specifies that when
file
specifications
on
the
mounted
output
volume are identical to

those on the input volume, the
output
volume
1is
deleted and
the file from the input volume.

1.14.3.4
If

you

/MOUNTED Qualifier

use

the

user

Additional

1.14.3.5
BRU

issued

supports

the

when

the

input

for

a magnetic

tape

input

following

additional

devices:

Memory Requirements
added

EM
DU

disk

for Booting Stand-Alone BRU -

to booting

stand-alone

requires

1.14.3.7

Disk Copying

Change

On RSX-11M-PLUS,
any

other

system, because
following

in Boot Block

for

you can copy a DB:,
of

magnetic

device.

TSV05/TU80 magnetic tape
ML11l electronic memory
RA60/RA80/RA81/RC25/RD51/RD52/RX50

have been

Device Support -

The stand-alone BRU system BRUSYS,

the

Mnemonic

Changes

device

syntax error message.
The purpose of this error
to
the
user
that
magnetic
tapes
cannot
be
volumes.
Previously, BRU ignored this qualifier

Type

1.14.3.6

the
with

Error Message -

/MOUNTED qualifier

tape,
BRU
issues
a
message is to clarify
mounted
as
Files-11

file
on
replaced

these

controller

the boot block

command

for

to write

DM:,
types

BRU

RSX-11M-PLUS.

EM:,

DR:,

or DU:

without having

these devices

the

for

124K-words of memory.

is common.

correct boot block

type

disk

resave

the

Use

only

the

output

disk:
MCR>SAVE/WB

1.15

FLX

This section describes a new feature, restrictions,
information
for
the
File
Transfer
Utility
RSX-11M-PLUS Version 3.0.

1-34

and
supplementary
program
(FLX)
on

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
l1.15.1

The

New

FLX

following

Feature

devices are

valid

RT-11 devices:

Device
RX50

Mnemonic

floppy disk

DU:

RD51 disk
RD52 disk
RD53 disk
RC25 fixed/removable disk
RCF25 fixed disk

DU:
DU:
DU:
DU:
DU:

Note that these are the only DU:-type devices
FLX as valid devices.

1.15.2

The

are

supported

FLX Restrictions

following

restrictions apply

DOS-11

Mount

following

to FLX:

format

DOS-11

1.15.2.1
The

that

and

RT-11

devices

foreign

Format -

devices do

RAG0

RD52

RAS1

RD53

RC25

RX50

not

support

DOS-11

format:

RD51

1.15.2.2

Mount DOS-11

and

RT-1l1 Devices as Foreign -

DOS-11 and RT-11 devices must be mounted as
can

use

1.15.3

Supplementary FLX

This section describes
applies

foreign devices before you

FLX.

still

FLX.

information

Although

valid.

Information

This

this

from

the

information

previous
not

new

includes

the

following

Handling an error during a copy operation

Image mode

Error

switch default

message

file

types

for

version

Version

that
3.0,

topics:

RSX~-11M-PLUS

1.15.3.1

Handling

SOFTWARE

Error

The behavior
operation to

FLX has

RT-11

Previously,

FLX

device when

insufficient

FEATURES AND

During

changed

Copy

RESTRICTIONS

Operation

handling

error

during

copy

device.

allowed

partial

space

file

existed

this

created

device

for

the

output

the complete

file.

Then, if a file existed on the output disk with the
same
the
newly created partial file, FLX deleted the pre-existing
substituted the partial file.
This replacing of an existing

as
and

with a
Now,

partial

resulted

loss

file

information.

if an error occurs during the copy operation, the partial file is
substituted for an existing file on the output disk.
The partial
no longer is closed as a permanent entry, and the definition
and

not
file

contents

1.15.3.2

The

file

for

the

existing

1Image

type

Mode

file

Switch

remain

Default

.CDA

should

image mode

switch

(/IM).

1.15.3.3

The

file

name
file

Error

following

Message

File

Types

list

the

added

default

file

types

error message

FLX -- Device

added

intact.

should

size exceeds

FLX:

65K blocks
ot

Explanation:
an

RC25,

blocks

The

RCF25,

cannot

l.16
The

FMT

This

devices

RSX-11M-PLUS

RAG0

1.17

RD52,

supported

Reenter

selected

the

RX50.

with

FLX.

command

RT-11

Devices

1line

device

greater

specifying

not

than

65K

valid

RESTRICTION

following

(FMT)

RD51,

User Action:

DU device

are

not

Version

supported

for

the

Disk

Volume

Formatter

3.0:

RD52

RASB1

RD53

RC25

RPO7

RD51

RX50

SYSTEM MANAGEMENT

section

management

describes

new

RSX-11M-PLUS

features

Version

and

3.0.

restriction

for

system

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS‘
l1.17.1

New System Management

Features

The following new system management features are supported:
e

New options for pre-generated kits

ACNT password encryption

Terminal

New SHUTUP

New

New VMR keywords

New Data

1.17.1.1

exercising
feature

features

RMD

Terminal

Emulator

(DTE)

error message

New Options for Pre-Generated Kits -

Several enhancements have been made to SYSPARAM.DAT

file

parameter

system

The

information on the structure of

1.17.1.2

and

LB:[1,2]SYSPARAM.DAT

STARTUP.CMD.

contains

ACNT Password Encryption -

Version 3.0 of RSX-11M-PLUS supports password encryption.

1is

account

these new options.

«created,

password

the

for

changed, the password for that account is encrypted
the Account File Maintenence

Program

(ACNT).

When a

new

existing account is
automatically

When a user runs ACNT and chooses either the DELETE or EXAMINE, or the

LIST

or MODIFY option,

(ENCRYPTED)

is displayed in the password field

Password encryption

of the ACNT record.

support

has

added

users

set

for

increased system security.

used

ACNT can no longer be

non-privileged

their

Non-privileged users can use the DCL command SET PASSWORD,
passwords.
passwords.
their
to modify
SET /PASSWORD,
the MCR command
and

Passwords

can

a maximum of 39 characters, although accounts used

for access by DECnet must restrict password length to 8 characters.

You can still build HELLO and ACNT

routine,

but

that

New accounts will be

routine

created

with

wuser-supplied

encryption

will only be used for existing accounts.

using

the

system-supplied

encryption

routine.

1.17.1.3

Terminal Exercising -

The RSX-11M-PLUS Version 3.0 I/0
Exerciser
(IOX)
supports
terminal
are exercised by using the LOOPBACK parameter
Terminals
exercising.
to

the

SELECT

command.

RSX-11M-PLUS

1.17.1.4

New

Shut

down

messages

You

are

prompted

shutdown

SHUTUP

SOFTWARE

Feature

include
for

"reason

for

shutdown"

reason,

and

New

RMD

Features

There

two

new

displays

about

are

Monitor

displays

RESTRICTIONS

the

message.

Resource

AND

1.17.1.5

the

FEATURES

Display

cache regions

(RMD).

These

field

displayed

that

been

are

have

the

RMD

SHUTUP.

the

system

added

page,

which

general statistics about a cache region, and the RMD D
page,
which
displays
detailed statistics about a cached device.
Note that
the bottommost line of the RMDemo D page will always be zero.

1.17.1.6

New

and

Modified

VMR

Keywords

The following keywords are new for
(VMR)

RSX-11M-PLUS

ASSIGN

Version

Virtual

Monitor

3.0:

Console

Routine

/SYSTEM

INSTALL

/WB
/FMAP

LOAD

/VEC

SET /[NO]AVO

/ [NOJANSI
/ [NO]BLKMOD
/ [NO]DEC
/[NO]JEDIT
/ [NO]HSYNC
/[NO]PARITY
/ [NO] PASTHRU
/[NO]JPRINTER

/[NO]JREGIS

PORT

/[NO]SOFT
/ [NO]TTSYNC
UNLOAD

1.17.1.7
The

/VEC

New Data

following

(DTE) :

Emulator

new error

message

(DTE)
for

Error Message -

the

Data

Terminal

?DTE-F-MODERR,

When
from

Terminal

Unable

to determine modem

you receive this message,
the modem or is unable to

DTE

has

type

either

interpret

the

Emulator

not

received

response

response,

Check to see that the modem is properly connected, and that the

switches

and

port

characteristics

are

1-38

properly

set.

modem

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

System Management Restriction

1.17.2

If you want to spool to the null device

DCL

command

initialize

1.18

the

INITIALIZE/SHAREABLE

(NL:), you

MCR

must

the

specify

command QUE /SHR when you

print processor.

NEW CRASH DUMP ANALYZER FEATURES

The following are new CDA features for RSX-11M-PLUS Version 3.0:
table

Assign

Data

New device

1.18.1

structures

support

Assign Table

1logical
1lists
table
The
The System Assign Table has been changed.
system logical assignments, group
three categories:
in
assignments
Also,

logical assignments, and user logical assignments.

size

the

includes

blocks

the

and

table

the

status (privileged

nonprivileged, and whether the translation of the assignment is final)
assignment.

for each logical

1.18.2

Data

Structures

Some system data structures have

RSX-11M/M-PLUS
a

list

1.18.3

changed.

See

of changed

data

the

crash

dump

structures.

Device Support

You can specify any of the following new devices
device

Appendix

and Micro/RSX Crash Dump Analyzer Reference Manual for

for

your

system:

Device Type

Mnemonic

" RA60 disk packs

DU:

RC25

removable disk cartridges

DU:

RX50

floppy diskette

DU:

TK50 magnetic

tapes

MU:

the

RSX-11M-PLUS

1.19

BATCH

AND

The

following

RSX-11M-PLUS

Restriction

not

use

Restriction

cannot

1.19.2

FEATURES

AND

apply

batch

and

for

using

/DELETE

for

the

/HOLD

Not

Use

/DELETE

/RESTART

together

and

with

/RESTART

active

it starts, making
it
following command:

impossible

batch

job.

Together

the /RESTART
switch.
The

submitted

/HOLD

switch

SUB/RESTART/DELETE

operations

/HOLD

and

Using

use

gets

queue

3.0:

When you SUBMIT a job with both
system
disregards the /RESTART

actually

RESTRICTIONS

RESTRICITONS

restrictions
Version

1.19.1
You

QUEUE

SOFTWARE

restart

and

/DELETE switches, the
deletes a job once

system

that

job.

For

example,

the

BATJOB.JOB

SUB/NORESTART/DELETE

BATJOB.JOB

Also, when you SUBMIT a job on a
privately
mounted
disk
using
the
/RESTART switch, you must use the /NOTRANSFER switch if you expect the
job to restart.
This is because the system
deletes
all
transferred
jobs
once
they
start,
making them impossible to restart.
Be aware
that using the /NOTRANSFER switch necessitates
1leaving
your
private
disk
attached
to
the
system, so that the system can access the job
without transferring it.

1.20

This

SYSTEM

Date

FCS

1.20.1

Date

Version

program.

format
not
(dd-mmm-vyy)
.

new

3.0.

features
SYSLIB

for

system

supports

the

library
following

routines

new

features:

routine

directory parsing

code

enhancement

Routine

RSX-11M-PLUS

contains
user

ROUTINES

section describes

RSX-11M-PLUS

For

LIBRARY

systems

new
The

with

extended

alternate date
new

date

dependent

routine

upon

logical

routine

that

allows

the

1-40

name

can

users

DIGITAL

be
to

support,

referenced
print

standard

dates

date

SYSLIB

any
a

format

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
To use the new routine,

you must build

INTDAT

These modules have been inserted into SYSLIB with

program or library.

See RSX-11M/M-PLUS and Micro/RSX Task Builder

deleted.

points

entry

Manual for a description of the /LB:
The INTDAT and

the

description”

modified;
module.

switch which is

wused

build

routines

$DAT

and

S$STIM.

INTDAS.

INTDAT and

(See

the SYSLIB modules,

(the normal version or the supervisor-mode version), into your

INTDAS

INTDAS modules contain

Library

System

IAS/RSX

routines.)

these

the

Reference

Routines

routine

STIM

The

Manual for a

been

not

has

is included simply because it is a part of the standard

The $DAT routine's calling sequence remains the same, but the

logical name SYSSDATE FORMAT can contain the following attributes:
DD

2-digit day of month with leading

zeros

2-digit month number with leading

zero

YY
ZzY
MMM

print 2-digit year with leading zero
print 2-digit year with leading zero suppressed
print alphabetic month (not necessarily 3 characters

print 2-digit day of month with leading zeros suppressed

print 2-digit month number with leading zero suppressed

long)

You can use additional characters (other than the uppercase letters D,
Z,
M, and Y) in SYSSDATE FORMAT as delimiters.
If SYSSDATE FORMAT is
SYSSDATE FORMAT can have a maximum

nn
The logical SYS$MONTH

alphabetic

month

(where nn

length of

(mmm)

characters.

16 characters.

traditional

default.

SYSSMONTH
nn

is used.

3-letter

can

the

provides

12)

printed when the mmm attribute

SYSSMONTH nn is not defined, you get the
abbreviations

length of

through

(dd-mmm-yy)

not defined, you get the DIGITAL standard date format

default.

month

have a max imum

Examples:

SYSSDATE FORMAT = "MMM
06 = "June"
SYS$SMONTH
Output:

June

ZD,

19YYy"

1985

specifying

.Xxp Dates,

SYS$DATE“FORMAT = "DD.MMM.YY"
06 = "VI"
SYSSMONTH
Output:

04.VI.85

SYSSDATE FORMAT = "ZD/MM/YY"
Output:

Logical

terminal

4/06/85

translation

is done in standard

order.

Therefore,

1local

assignment can override a system-wide assignment, permitting

the same program to

language or

preferred

produce

output

the

individual

wuser's

own

format.

There are two limitations to the alternate date routine.
First, using
it
necessitates
more output buffer space than the traditional format

because

standard

the output produced

characters.

all

SDAT

existing

routine

Second,

is one

can be as

however,

1long

always

the new module can be

programs.

produces

characters.

either

linked with many,

but

The

not

An example of a program that cannot use this

that performs operations on the

resulting

output

string

expecting it to be in the format produced by the standard routine.

RSX~11M-PLUS

1.20.2
A

new

feature

has

following

added

(FCS).

extension

Extension

.Byte

Reserved

has

AND

RESTRICTIONS

been

.Byte

Length

buffer

Length

directory

Word

Address

block

space.

and

Enter

the
¢

the

Enter

®¢

the

value,

address

length

block.

the

length

extension

block.

Insert

the

FDB.

the

uses

parsing

the

buffer.

value

for

the

directory

string

FDB,

which

File

used

has

1in

the

string

buffer

.PRSDI)

buffer

directory

the

string

(filled

are

string

into

the

buffer

the

extension

address

directory
it

created

string

allocated

used

the

also

the

code
as

the

into

extension

detects

puts

into

word

the

proper

address

the

block

that
and

proper

the

F.EXT

moves

byte

proper

byte

offset

has

the

F.EXT

nonzero

directory

the

your

parse,

block.

the

code

directory

for

directory

extension
Enter

parsing

the

directory

obtain

extension

directory

obtain

length

following:

into

the

can

.Byte

extension

When

You

format:

.Byte

address

the

been

Services

parse.

The

FEATURES

FCS Directofy Parsing Code Enhancement

Control

the

SOFTWARE

string

length
of
the
actual
directory
string
into the byte in the extension.
This directory will always be
filled in, except when the directory is obtained from the default
name
block
because
the
default name block does not contain the directory
string.
1In this case, the directory length will be set to zero.

1.21
The

TKS50
TK50

OVERVIEW

tape

subsystems,

subsystem
if

I/0

tape

unit

enough

the

mode.

While

streaming

commands

are

(about

one

second

for

expects

the

I/0

command

direction.

is,

maintain

subsystem.

issued

the

finishes,

this

constant

the

keeps

processing

forward

TK50).

Because

ready

the

tape

that

allows

motion.

for

the
one

has

tape.

second

This

is
to

with

unit

repositioned

this

(backed

moving

the

reposition

complete

before

operation
the

I/0

all

quickly

enough.

1-42

1I/0

the

result,

correct

the

position

approximately
be

processed.

performance
of
to the controller
|

that

position

can

the

forward

stream,

the

takes

unit

when

the

command

reposition time can
severely
impact
the
utilities
if they are unable to issue commands

tape
the

1if

the

that

tape

However,

up),

the

processing

command
1is
not
ready,
the tape unit moves past
tape where the I/0 operation was to be performed.
tape

tape

drops out of streaming mode and
into
start/stop
start/stop mode, each I/0 command issued incurs a time

penalty
current

tape

not

tape
fast

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
In order to alleviate the performance impact of the reposition time, a

padding

feature

output

controller to

the TK50 firmware.

enabled

issue up to a preset number

padding

This allows the
blocks

during

Before each

the tape in order to keep the tape streaming.

pad block is written, the controller checks to see if

the

host

written and the host's I/0 request

the

host

1is

ready

for

the controller will reposition back over

the

If it is, then no more pad blocks are

for processing.

ready

I1/0

is performed.

command is not ready, the controller writes out another pad block.
continues to do this until either a host

I/0

command

the number of consecutive pad blocks written reaches a
or
processing
controller specified maximum.
In the latter case, the tape unit
will
When the next
streaming mode and into start/stop mode.
drop out of
write command

pad

blocks

the

wunit

As a result,

that

issued,

it wrote before actually doing the write operation.

tape capacity is not lost

if the application cannot

keep

1If the application does keep the unit

mode.

streaming

partially in streaming mode, then some tape capacity will be lost
due
On input from TK50, the controller does not return
to the pad blocks.
any of these pad blocks to the application program.
Because of
this,
padding is transparent to the user's application.
The following section describes performance
using RSX utilities with the TK50.

1.21.1

and capacity impacts

when

TK50 Performance Using RSX Utilities

This section describes anticipated timings for various RSX
These

are

guidelines

system load, disk usage,
@

only;

the actual

tape ECC errors encountered, and so forth.

MOU - When mounting a TK50 tape, either

tape,

foreign or as an ANSI

taken is dependent upon the position of the

time

the

wutilities.

times will vary depending on

or
If the tape is at
tape when the mount command is issued.
track, the expected time for the
a
of
beginning
the
near
Dur ing
seconds.
twenty
mount operation is on the order of
the controller performs calibration functions on
time
this
the tape.
If the tape is near the end of a track,
the
time
tape <can increase to as much as two minutes.
the
to mount
This time

is taken up

1.6

(approximately

the

minutes)

functions by -the controller.

rewind

When a cartridge

1is

the

tape

calibration
inserted,

will be at the beginning of tape so the expected time, on

the average,

seconds.

for

the mount operation

the

track by an abnormal

during

minutes.

actual

followed

tape

event,

operation,

However,

will

about

this

is a

for example

then

this

very rare

the

time

system

the

tape

unit as part of

Depending on where the tape

1is

crashes

can approach 2

instance.

DMO - When dismounting a tape, a REWIND command
issued

twenty

tape is left positioned near the end of a

the dismount

positioned,

this

generally
function.

may

between
one second (the tape is at the beginning of a
and 1.6 minutes (the tape is at the end of a track).

take

track)

RSX-11M-PLUS

This

mode.

BRU

The

During

SOFTWARE

utility

will

exceptions
the

FEATURES

generally

initial

this

set

operation
contained

1is
dependent
on
on the input disk.

minutes,

BRU generally will

commands
to
streaming.
3.

Any

use

restoring

the

BRU will

BRU

stream

drive

from

The

writing

stream

out

extra

during

its

this
this

of directories

load

the

This load will slow BRU
not be
able
to
issue

fast

enough

BRU

disk

to
a

number

there

which

the

able
As

of directories
can take
from

keep

backing

run

the

TK50

head movements

time to BRU's processing time that
issue I/0O's to the TK50 controller
in streaming mode.

not

streaming

number
process

the

generally cause BRU

start/stop mode.

sufficient
be able to
to keep it

TK50

start/stop mode during
The
time
taken
for

BRU is run.
that it will

TK50

the disk

will

that

the
This

based

not

system
at
the time
down sufficiently so

the

tape, BRU will not be
TK50
quickly
enough.

the TK50 will run in
BRU's
operation.

ten

keep

up phase,

result,
phase of

one
to
written.

RESTRICTIONS

are:

directory
information
to
issue I/0 commands to the

AND

/VERIFY

will

add

it will not
fast enough

pass.

will

not
stream
while
it
1is
sorting
retrieval
The
number
of
such
sort
operations
is
dependent on the degree of disk fragmentation that exists
pointers.
on

Once

the

input

BRU begins

disk.
copying

data

blocks

out

the

TK50,

will

keep
the
TK50
wunit in streaming mode provided that none of
the conditions described above occur.
A test
case
using
a
slow
disk
and 40MB of data was
this took thirteen minutes, with

three

minutes

this

run.
The save operation for
the directory writes
taking

time.

sufficient

data

were

available for backing up to the tape, BRU would have utilized
approximately
83%
of
the total capacity (94MB) of the tape
for storing data.
Such a capacity
rating
would
allow
the

backing
up
of
a 75MB disk (0.83
TK50 tape cartridge.
1In this test

was performed.
take

However,

approximately one

BRUSYS

This

x 94MB =
case, no

78MB) to a single
verify
operation

the verify operation

hour

for

this

is estimated

example.

utility exhibits the capacity
and
above for online BRU.

performance

characteristics mentioned

FLX - This utility will not keep the TK50
streaming.
FLX's
internal
design
does not permit the issuing of I/0 commands
to the TKS50 at the rate required in order to
keep
the
tape
streaming.
Because
1t
does not stream, the padding blocks
added by the
controller
will
be
over-written
during
the
reposition

operation.

A test case using
FLX

copied

the

180

files

Tape

capacity

blocks contained

1.8 minutes.

1-44

will

not

be diminished.

in nine

files was run.

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
@

PIP - This utility will

not keep

required

design

internal
the

TKS50

at the

the

TK50

streaming.

Its

does not permit the issuing of I/0 commands
rate

order

keep

the

tape

does not stream, the padding blocks
it
Because
streaming.
added by the
controller
will
be
over-written
during
the
Tape capacity will not be diminished.
reposition operation.
A test case using
in

FLLX

10.5 minutes.

test

processing.
test

the

There

180

blocks contained

case

files was run.

This

due

time differs

significantly

The default block

from

the

involved in ANSI tape

overhead

the

size on ANSI

tape was

used

for

case.

is an

optimization

throughput

that can be

ANSI

tape

optimization does not result

fewer

in nine

the TK50 as an ANSI tape, copied the information

using

PIP,

performed

the

streaming;

TK50

increase

drive.

it does result

This

1in

I/0s to the tape unit and therefore fewer repositions.

The size of the block written to ANSI tape can
be
1increased
by
using
the /BS switch in PIP.
A value up to 8192.
bytes
can be specified (the default is 512.
bytes).
PIP should be

installed

not,

with an increment if this value is used.

PIP may

issue

"not

enough buffer

during certain copy operations

1.21.2

TK50

Because

the

error

1If it is

messages

tape.

Indicator Lights
actual

TK50

tape

recording

surface

is hidden

from view,

often difficult to determine what the tape unit is actually doing.

There are

some

space"

two

lights

information

the

front of

what

the

TK50

is happening.

tape

unit

that

purpose,

provide

A description of these

follow:

Green

indicator

The green

light

indicator

light

serves a dual

follows:

blink,

When the green indicator light is on and does not

When the green indicator light is blinking or not on,
it
is
not safe to remove the cartridge.
A blinking pattern
indicates that the tape is in motion, either in a forward
or reverse direction.

Red
The

it
1indicates
that
the
removed from the unit.

<cartridge

can

safely be

light

indicator
red

tape

indicator

1light

serves

multiple

purpose,

follows:

When the red indicator light is on and does not blink,
tape cartridge is loaded in the drive.

When

the

red

indicator

light blinks

slowly,

(on

for

second and then off for one second) it indicates
tape is in use and is currently rewinding.

When the red
that

cleared by

succession.

context.

indicator light blinks rapidly,

drive error

pressing
Note

has

the

that

occurred.

will

one

that the

it indicates

This condition can be

LOAD/UNLOAD

this

switch

cause

twice

1loss

tape

RSX-11M-PLUS

1.22

FEATURES

AND

RESTRICTIONS

restriction

1/0 DRIVERS

This

section

drivers

1.22.1

New

The

SOFTWARE

describes

new

RSX-11M-PLUS

I/O

following

Driver

features

Version

features

Stall

QIO

Extended

I/0

Modified

TF.TMO subfunction

Tape

®@

New disk driver

device

for

the

are

supported:

RC25

DEUNA driver

driver

1.22.1.1

Stall

support

I/0

for

Features

new device driver
I/0

and

3.0.

1/0

function

functional

for

error

the

change

code

RC25

has

been

modified

for

this

release.

I/0
1is
stalled
only
to
the fixed disk of the RC25 subsystem.
removable disk will lose context if the drive is spun down.
Also,
VER task is no longer used in stalled I/0 processing.
Because

context

may

lost

the removable

spun
down,
all
spin-down requests are
the RC25.
For the removable disk unit,

order

spin-down

When you queue an
processed
the

because

the

I/O request to
of

the

drive

I/0

stall

subsystem

of
in

is dismounted.

the DU:

I/0,

the

driver

and

following message

it
is

cannot

printed

has

stalled

been

following message

DDbnn:

The

when

console:

DDnn:

When

the device

disk

ignored for the fixed unit
you
must
be
privileged

The
the

RSX QIO

I/0

DEUNA

printed

again
on

and

the

I/0 processing

can

continue,

the

Ethernet

console:

resumed

driver

by
systems
without
QIO$ macro to the XE:

DECnet's

spun

allows

DECnet.
device.

messages

sent

over

To use the DEUNA driver, you issue the
The DEUNA driver
1is
compatible
with

Direct
Line
Access
Interface
(DLX),
which
permits easy
to a DECnet system.
New I/0 functions have
been
added
to
support
the
QIO
DEUNA driver.
See Chapter 13 of the RSX-11M/M-PLUS
I1/0 Drivers Reference Manual for more information.

migration

RSX-11M-PLUS

FEATURES

AND

RESTRICTIONS

Extended I/0 Function -

1.22.1.3
There

is a new

bits.

See

Manual

SOFTWARE

for

function,

I0.EIO,

the

a description of

See Section

1.22.1.4

I/0

Chapter

which allows

for

new

subfunction

RSX-11M/M-PLUS I/0 Drivers Reference

IO.EIO.

1.22.2 for a restriction regarding

IO.EIO.

Modified TF.TMO Subfunction -

The TMO parameter of the TF.TMO subfunction has been modified so

you

can specify the amount of

time

the driver

maximum

time-out

characters before the read is aborted.
is

called

255 (decimal)

time-out.

The

intervals.

1is

waits between

The amount of time

value you can

specified,

the

read

two

TMO

that

input

waits

specify

times

out

immediately
after
reading
any
data
that
may
be in the typeahead
buffer.
1If you enter a 0,
no
time
1is
allowed
for
you
to
enter
characters,
and
all
characters
are read from the typeahead buffer.

See

the

RSX-11M/M-PLUS

1I/0

information.

1.22.1.5

New and Modified Magnetic

The meanings of the
¢

following

Completion of

Tape Driver

Manual

for

Information -

MUDRV

devices means

IO.DSE
takes

(Data Security Erase) is valid only for the
approximately
35
minutes
to
complete.

rewind

initiated;

(MU:)

has

the

BOT

has

operation is initiated,
the

TK50

runs

controller.

for MSDRV

been

(MS:)

completed.

it is under the complete

The

I0.DSE command

I0.SEC

(Get Tape Characteristics)

®@

the

has

the

it means
TK50
Once

control

and
the

cannot be aborted by

completion.

TK25 and

that

devices

the host software; the controller ensures that the
@

functions have changed:

IO.RWD for

been

Reference

rewind
that

Drivers

specific

operation

changes

for

TK50.

Select errors are not issued for MUDRV
devices
(TK50).
1f
the
drive is taken off-line, the drive positions the tape at
BOT so the off-line condition is treated
as
tape
"position
lost"
or
"powerfail".
The
cartridge must be unloaded and
loaded

in order

result

in the tape unit rewinding to BOT.

application

mounted

access

is possible

ANSI

the

tape

again.

such an event.

tape,

the

This

action

will

No recovery by the
If

the

tape

was

tape context maintained by

MTAACP

is invalid.
The tape must be dismounted and remounted
in
order to reinitialize the data structures used by MTAACP.
If the tape was being accessed in write mode, then
the
file
being
written is incomplete and the tape may no longer be in
valid ANSI format.

Read recovery for MSDRV devices is
done
as
follows:
Read
errors
are
retried
by
rereading
the
block
in
error
a
predetermined number of times.
For MS:
devices (except
for

TK25), on every eighth reread the block is passed by the tape
cleaner blade.
If the error persists after
a
predetermined
number of retries the error code IE.VER, is returned.

RSX-11M-PLUS SOFTWARE FEATURES AND

Under

certain

mounted
than the

1.22.1.6
The

New Disk

following

IE.IFC

1.22.2

The

IO.EIO

Driver

new error

Invalid

1I/0 Driver

remote

command

the
the

terminal
RT:.

SET

The

code

has

been

function

for

disk

will

describes

I/0 Operation

support

and

tape

one more

QIO

SET

issuing

terminal
That is,
/HOST,

has been set
as
a
after you enter the

and

log

extended

and

into

I/0

RT:,

for

1/0

has

been

request

restrictions

from

Features

the

following

Logical

CSIS4

Changes

®¢

New

New bit definition

New

volume

New

file

Modified

Buffer

specification

format

new

features:

expanded

name parsing

command

semantic

parameters

offsets

for

command

new
features
Version 3.0.

File

format

written

added:

MCR

rejects

RSX-11M-PLUS

File

will be even
MOUNT command.

not

1.23.1.1

Code

the

section

I/0 operations

HOST,

This

New

size

work if your
another system.

I/0 OPERATIONS

1.23.1

file

driver

(RT:)

1.23

operations

Error

block

Restriction

function

terminal

DCL

conditions,

/NOLABEL,
its
value specified

RESTRICTIONS

the

label

header

for macros

File

for

Descriptor

wildcard

Block

(FDB)

processing

format

label

keywords

flush

parser

(HDR3)

for

format

the magnetic

tape

control

task

routine

Specification

specifying

expanded

for

1logical

Micro/RSX

I/0

Operations

Format

files

name

Expanded

on disk

and

support.

Reference

Manual

1-48

See

magnetic
the

for more

tape

RSX-11M/M-PLUS

information.

and

RSX-11M-PLUS

SOFTWARE

FEATURES

AND

RESTRICTIONS

Logical Name Parsing -

1.23.1.2

File Control

Services

(FCS)

FCS .PARSE directive.

supports

When the

per forms any necessary logical

logical

name

translation

.PARSE directive receives a string,

expansion and

then parses the

the

resulting

string.

Adding

logical

increase

own

1in

address

remove

name support

size.

space will

logical

name

[1,1]FCSNOLOG.OBS

you

select

this

for

See

the

FCS

An existing

support

increase

You

caused

certain

size by about

from

only need

for extended

routines

FCS,
to

700 (octal)

replace

logical names,

the

bytes.

the

its
To

module

1if

otherwise SYSGEN does

you.

RSX-11M/M-PLUS

and

Micro/RSX

for more

information on logical

1.23.1.3

CSI$4 Command

The CSI$4 Command
support.

except that

This

RSX-11M/M-PLUS
information.

1.23.1.4

The

support

SYSLIB.

has

task that includes FCS modules

I/0 Operations

Semantic

Parser

Semantic Parser has
routine

1is

the

Changes

Micro/RSX

been

added

for

1logical

the existing CSI$2

to handle logical names.

I/0 Operations

Parameters

Manual

same as

includes extra code
and

Reference

name parsing.

for

Macros

Reference Manual

name

routine,

See

the

for more

following macros have been modified:
e

The

FD.PRN parameter

for

the

FDATSA

macro

has

been

added.

This
parameter indicates whether the record is preceded by a
word containing carriage control information.
This value
is
the print file format attribute.
@

The

FDOPSA

lock

all

macro

has

been

modified

that

the

that

the

FA.SHR

parameter
indicates
whether
the
file should be opened for
shared access.
Shared access is
a
precondition
for
Dblock
locking.
The logical OR of FA.LKL!FA.EXL can be specified to
blocks

The OPENSx

that

macro

parameter

requests

file.

FD.RAN

PUTS operations.
If

are

has

been

modified

random access

not

FCS

A PUTS
is

accessed.

operation

specified

the

does

file during

uses

not

FD.RAN

GETS or

truncate

the

sequential

access

Reference

Manual

by default.

See the RSX-11M/M-PLUS
for more information.

1.23.1.5

The

New Offsets

following

and Micro/RSX

I/0 Operations

In the File Descriptor Block

are new FDB offset values:

F.EXT

Address

F.FLG

Flag byte

the

FDB

extension.

1-49

(FDB)

RSX-11M-PLUS

1.23.1.6

SOFTWARE

FEATURES AND

RESTRICTIONS

New Bit Definition for Wildcard Processing Y

A bit definition has been
N.STAT.
The
Dbit symbol

added to the
Filename
Block
Status
Word,
is NB.WCH.
It is set if wildcard processing

required.

1.23.1.7

There

New

Volume

new

Label

volume

1l1) can be any
restriction.

ANSI
You

Format

label

"a"
can

format.

character.
specify

The

accessibility byte

(position

A space indicates no accessibility
the
"a"
character
with
the

/VOLUME ACCESSIBILITY:"c"
Any ANSI "a" character is
The

Label

Standard

1.23.1.8
There

qualifier
in
the
DCL INITIALIZE command.
allowed.
The default character is a
space.
Version byte in position 80 contains a 3.

New File Header Label

new

file

system-dependent

file attributes
RSX-11M/M-PLUS

header

field

(HDR3) Format -

label

format.

character

in the format
and Micro/RSX

The

positions

new

format

(64

contains
bytes).

are specified at creation time.
I/0 Operations Reference Manual

a
The

See the
for more

information.

1.23.1.9
The

Modified

following

Control

task

are

Keywords
new

for

the Magnetic Tape

keyword

definitions

Control

for

the

Task

Magnetic

Tape

(MAG):

Keyword

Definition

/BS

The

/CC

number

mounted

tape.

The

type

bytes

a mounted

characters

of carriage

(bytes)

control.

tape

per

block

the
on

The default

tape

will

new

ACP

for

/CC=NONE.

/INITIALIZE

The volume

label

to which

the

initialized.
This

keyword

volume
a

new

output

1.23.1.10

Buffer Flush Routine -

The

flush

buffer

routine

allows

satisfy

(.FLUSH)

volume

writes

the

vyou

request
for

block

create

from

the

ANSI

tape.

buffer

the

file

being
written
1in
record mode.
Also, the .FLUSH routine writes
attributes
(including
F.EFBK
and
F.HIBK,
the
end-of-file
high-allocation block numbers) each time the routine is called.

file
and

Closing

that

the

file

guarantees

attributes

are

that

the

block

written back

buffer

the

flushed

file header.

and

However,

closing and opening a file
results
1in
high
system
system resources.
See the

frequently, to write to the
block
buffer,
overhead
and many disk accesses that hoard
RSX-11M/M-PLUS and Micro/RSX I/0 Operations

Reference Manual

information.

for more

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.23.2

I/0 Operations Restrictions

The following restrictions apply to I/O operations:

A user task record buffer is required for multiple buffering.

A user task record buffer is required for big buffering.

1.23.2.1

A User Task Record Buffer Is Required for Multiple Buffering

Multiple buffering can improve performance for I/O-bound

certain circumstances.
is not very efficient.

under

When multibuffering in random mode is used,

record buffer is always required.

task

user

tasks

However, multibuffer processing in random mode
a

1If one is not supplied,

the task's low memory may be overwritten and the task may then abort.

1.23.2.2

A User Task Record Buffer

is Required for Big Buffering -

When using "big" buffering in random mode, a user task
is always

required.

1If

one

is not

supplied,
the

task's

record

buffer

low memory may

be overwritten and the task may then abort.
See
the
RSX-11M/M-PLUS
and Micro/RSX I/0 Operations Reference Manual for more information.

NEW FEATURES FOR USER-WRITTEN DEVICE DRIVERS

1.24

This section describes the following
new
features
device drivers on RSX-11M-PLUS Version 3.0:

Using asynchronous buffered
I/0

Vectoring for privileged tasks and the Executive

Converting

Converting to vectored access in drivers

Overlapped

1.24.1

to vectored access

user-written

in privileged tasks

I/0 completion

Using Asynchronous Buffered I/0

Typically, data

for

from

and

for

input and output requests are transferred directly

To allow the successful transfer of data,

task memory.

the task cannot be checkpointed until the transfer is
complete.
For
most
high-speed
devices,
the
transfer occurs quickly enough that a
task does not occupy memory for
too
1long
a
time.
For
slow-speed

devices,

however,

memory to a

task

for

some
too

Using the routines $TSTBF,
I0OSUB,

driver

mechanism must be available to avoid binding

long

time while

I/0 request

To perform the I/0 request, the driver
to

request

in progress.

the

driver

task

is performing

SINIBF, and $QUEBF in the Executive

can execute

allocated

the

while the

for

buffers

task

I/O.

module

a slow-speed device.

the

data

is checkpointed and

memory

the

I/0

RSX-11M-PLUS

test

whether

task

SOFTWARE

FEATURES AND

proper

RESTRICTIONS

state
to

initiate

the
driver
I/0 packet.

I/0 buffering,

calls the $TSTBF routine and passes it the address of the
By extracting the address of the Task Control Block (TCB)
from the I/0 packet, STSTBF can examine various task attributes.
(For
example,
1f
the
task
1is
checkpointable,
buffered
I1/0
can
be
performed.)
Once S$TSTBF has examined the task's attributes it returns
to the driver and indicates whether buffered I/0 can be performed.

If buffered I/0 can be performed, the driver performs two

First,

request,

space.,

establishes

copies

For

the

1in

input

receive

incoming

Second,

the

task

driver

calls

the

count

and

task

transformed

unblocked,

buffered

the

described

1in

$INIBF

the

I/0

normal

the

I/0

and

the

space

initiate

count,

releases

task

operations.

For
an
output
allocated
pool

sufficient pool

routine

task

T.TIO,

shuffling.

state

subject

it allocates

decrements

checkpointing

conditions.
to
dynamically

buffers

request,

data.

buffering.
SINIBF
task's buffered
I/0

buffering

the

requirements

and

1/0

increments

the

for

task

currently blocked,

into
a
stop
state
until
the
completes, or both.
Checkpointing

RSX-11M/M-PLUS

active

Micro/RSX

stopped

Executive

the

task
is
the task

state

Reference

Manual.

After

the

queue

driver

the

transfers

buffered

1I/0

the

data, it calls
completion.

for

the
SQUEBF
SQUEBF
sets

routine
to
up
a Kernel

Asynchronous

System Trap (KERNEL AST) for
the
buffered
1I1/0
request
necessary, unstops the task.
When the task is active again, a
in the Executive module SYSXT notices the outstanding AST
and
processes
1it.
(If
the request is for input, the routine copies the
buffered data to task memory.)

and, if
routine

This mechanism
AST.
pool.

occurs

transparently

The routine then
SIOFIN completes

1.24.2

Vectoring

RSX-11M-PLUS

for

calls
the

the

task,

thus

deallocate

the

name

allow

Tasks and

vectored

the

offset

vectored
@

the

access

For

directive

virtual
to

some

common.

address

Executive

systems,

access

using

code

space

most

cases,

Executive

their

most

multiple

the

saved

tasks

time,

the

directive

provides

can

privileged

run

the

distributing
common
privileged
different system images.
¢

code

tasks

allows

versions of

RSX

reference
When the

resolved
resolves

task

common.

following

advantages:

distribution

with

kits

multiple

and

need

not

rebuilt

software

sold

separately

systems

without

relinking

1-52

Executive

when

the

span

is updated.

cases,

from

Executive

privileged
task.
Accessing
entry
points
in
a vectored
requires that the privileged task be
slightly
altered
to
these
entry
points
through
1local
vectors
in
the task.
privileged task is built, the addresses in these vectors are
to
the

KERNEL

the buffer

processing.

Privileged

Executives

driver

the

tasks.

RSX-11M-PLUS

A vectored Executive
system.

SOFTWARE

requires

This common

FEATURES

AND

special

RESTRICTIONS

directive

and resolves the Executive routine addresses.
that

is vectored

has a

unique

fixed

offset

have all

Executive

references

the

it builds a

Each Executive

task

routine

the directive common.

Privileged tasks that are built against the dummy

RSXVEC.STB,

common

is used by the Task Builder when

symbol

resolved

table

as offsets

file

into

the

special directive common, rather than as virtual Executive addresses.
These offsets are

translated

into virtual

addresses at

task run

time.

For a system that does not support vectoring,

the modified task can be

rebuilt by using

symbol

will resolve all

symbols at task

system-specific

RSX11M.STB

build

time.

table

Both

file.

This

RSXVEC.STB

and

RSX11M.STB are distributed.

Any privileged

modified

beginning

Executive

task

that directly

reference

Executive

you want to take advantage of vectoring.

such

tasks

entry

should

points

that

set

aside

store

code

must

An area at the

vectors

the

allow the task to address the required

Executive locations.
Therefore, privileged tasks that take
advantage
of
vectoring will increase in size by approximately one word for each
unique Executive reference.
The task's vectors in this
area
contain
offsets into the special directive common previously described.
When

the

task

translate

the

invoked,

offsets

the directive common.
the
offsets
1located
addresses to reference

The GINS directive
therefore

the

vectored,

GINS

1in

special

the

file

and

GINS

directive

to virtual

located

within

directive
run

the

fails

task

that

vector

Drivers,

which

rebuilt

system with

are

different scheme because the
driver

must

pointer

SYSCM

1issued

modified

GIN$

fixed low-core memory location
where

mapped

the

address

that

has

wusing

internal

through

directive

information

code

also

common;
not

been

specific
changes.

must

uses

use

APRS.

through a

The

known

This location contains

needed

for drivers to be

APR5,

the entry points

(112 octal).

overwrite
uses these

directive

system

Additional changes are necessary to make it possible
vectored.

1is

addresses available

The addresses obtained in the common
in
the
task
1in
memory.
The task
Executive routines.

allowing a vectored

RSX11M.STB

task

the driver

located.

1.24.3

For a

Converting

task

created

dollar
from

1in

sign

offset

to Vectored

Access

use vectored entry,
the

task.

from global

in Privileged

table of entry addresses

convenient

way

to do

labels where possible and

definitions.

For

Tasks

example,

this

to omit
a

the

must

omit

the

period

task
contains a reference to the Executive global data cell
S$SACTHD,
calls
routine
S$MPLND, and uses offset definition S.PKT, which is one of the
floating data structure offsets.
|

1-53

suppose

privileged

RSX-11M-PLUS

The

first

the

step

task

converting

similar

;

SOFTWARE

FEATURES AND

privileged

the example

Executive

Entry

RESTRICTIONS

task

construct

table

following:

Point

Vector

Table

EXEVEC:
.WORD

;

ACTHD:

.WORD

SACTHD

;

MPLND:

.WORD

SMPLND

SPKT:

.WORD

S.PKT

;
;

Flag

for

vector

not

yet

filled

EXEVCL=<<.-EXEVEC>/2>

The
has

first
not

merely

task

word
been

of the table
1initialized

.WORD

reference

1linked,

RSX11M.STB,

The

second

which

step

is made zero to indicate
that
the
table
yet.
Each subsequent word of the table is
the desired address.
When the
privileged

must

provides

linked

internal

in converting

with

offset

RSXVEC.STB

values

privileged

for

task

change
all
the references to Executive symbols in
those symbols through the
vector.
Some
examples
follow:
;o

Converting

MOV

SACTHD,R5

Executive

references

;;

Get

address

@ACTHD, R5

CALL

SMPLND

privileged

first

TCB

fl
first

TCB

Get

Follow redirection

list

:+;

Follow redirection

list

;;

Get

becomes

CALL

@MPLND

MOV

S.PKT(R3) ,R0

ADD

SPKT,R3

;;

MOV

(R3) ,RO

Get

step

translation of

first

I/0 queue

address

GINS$ directive must

listhead

first packet

included

example section of

packet

code

perform

is as

the

follows:

.MCALL

GINS

TRNVEC:

GINS

GI.VEC,EXEVEC,EXEVCL

;

Translate

Executive

vector

START:

DIRS

TRNVEC

;

Translate

Executive

vector

« END

START

internal
directive
the

the

first

nonzero

when

foregoing

number of

the

GIN$

directive,

the

offset
definitions,
and
the
replaces each
of
the
offset

address of

The

that

the vector.

Before executing

address

'
Point

last

task

;;

becomes

The

address

symbols.

requires
that
you
the task to access
of
this
process
“

becomes
MOV

instead

the

symbol

word

in
the

the GINS

procedure

the

Executive.

vector

function
allows

with

the

times without corrupting

vector

The

filled

1is 0.
with

the

first

function

GINS directive

the vectors.

the
to

with

The
the

GINS directive also

issued,

1-54

1is

first
word
definitions

GINS
real

fills

word

is made a
executed

NOP.

any

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.24.4

Converting to Vectored Access in Drivers

Drivers cannot issue

provided

that

GINS

callable

Because this routine is at a

system

variable

Therefore,

directive,

state to fill

some

address,

fixed

address

Location 112 points to a table of information.

is needed.
entry

table contains one datum, which is the address of the APR bias of

That

the

entry point to the

The

routine.

vectoring

the

containing

common

1is

routine

in the vector.

An example calling sequence is as

routine is offset 4 in that common.
follows:

Callable routine for converting Executive references in a driver

: Get address of table of entries

@ 112,R0

MOV

(RO) ,RO

; Get address of APR bias, which

MOV
MOV
MOV
CALL

(RO) ,KINARG
$#EXEVEC,R3
#EXEVCL,R2
@$140004

;
;
;
;

1.24.5

Overlapped

in table

first word

Map common through I-space APR6
Point to vector
Specify length of vector
Translate the vector

1I/0 Completion

In general, overlapped I/0 completion support causes the execution

completion

1/0

the

Executive's

are

the

driver's

request.

postponed until

code

for

each

the next request has been initiated.

queue,

this

complete the I/O processing while the

action

requests

the Executive to

device

services

the

other

than

minor side effect of this feature is that multiple

I1/0 requests to the same device may complete in an

the issued order.

If I/0

causes

.physical

request to be

1I/0

order

This feature is described in the following text.

When a driver requests the Executive to complete the I/0 request,

the

If the queue is

Executive checks the queue of requests to the driver.

not empty, the Executive defers I/O completion by placing the

current

Control returns to the
fork 1list.
completion at the end of the
driver, which assumes that the Executive has completed I/0 processing.
After the driver
The driver can then initiate the next I/0 operation.
has initiated an I/0 operation on the device,

the

Executive

fork processing begins.

and

the

driver

returns

Thus, the I/0 completion

When a hardware I/0
for the previous I/O0 can be processed to the end.
operation completes, the driver receives an interrupt and then forks,
previously
the
which always causes the I/0 completion to occur after
queued completion.

The exception to sequential completion occurs when
an
I/0O operation
In this case, the driver
hardware operation.
does not require a
processes

the

the queue,

this completion also goes at the end

completion

I/0

routine,

request

and

then

calls

the

Executive's

I/0

1If there is an additional I/O request waiting on
of the

fork list,

and

sequential
processing is maintained.
Nonsequential completion occurs
when the very last request in the queue is a nonhardware-oriented I/O.

this

case, that I/0 request completes prior to any others waiting

for completion.
There are many
cases
of
nonhardware-oriented
1I/0,
such as inquiries into device state, or attach and detach requests.
This feature speeds up 1/0 operation

operations

may occur

operation.

in the case

'of

actual

hardware

because the new hardware I/0 is initiated and the transfer

in parallel

The 1I1I/0

with

the

processing

necessary to process the remaining
finish routine.

final

speeds

completion

instructions

the

amount of time
Executive

1I/0

RSX-11M-PLUS

There

one

case

to
finish in an
This occurs when
not

require

1.25

This

ERROR

The

FEATURES AND RESTRICTIONS

where overlapped I/0 completion causes I/0
requests
order other than the order in which they were issued.
the last I/0 request queued to
the
controller
does

device

interrupt

complete.

LOGGING

section describes

information

1.25.1

SOFTWARE

for

error

New Error

following

new features, restrictions,
and
supplementary
logging on RSX-11M-PLUS Version 3.0.

Logging

new

error

Features

logging

features

Internal

Non-DIGITAL device

Error

DCL

error

logging

commands

DCL

SHOW

ERROR LOG

command

MCR ELI command switches

I/0

supported:

operations

logging

control

files

1.25.1.1

1Internal

The error

logging system
supports
such as data caching.

operations

are

I/0 Operations

qualifiers

error

1logging

for

internal
|

1I/0

You

no longer need to add a record to the DEVICE INFO
table
in
the
DEVSM1 module for the error logging system to recognize a user-written
device level module.
After you write the device level
module(s)
for
your
devices,
compile the module(s) with the DSP2P1.SYM file.
Next,

insert your module(s)

module must

following

the

ERRLOG.ULB.

The

name

form:

user-written

ExxUSR

The

letters

cannot

the

stand
same

Specify your module
MODULE

your

the device
the

any

the device mnemonic.
DIGITAL-supplied

name

must

set

specify

the

MODULE

Your

device

statement

device

mnemonic

mnemonic.

as:

ExxUSR

for

module,

you

device

you

INDICATE.TAPE
FLAG

specify
TRUE.

the

variable

disk.
1is

not

INDICATE.TAP
FLAG
E

disk,

set

the

FALSE

variable

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
Remember to set your

INTERMOD DEVERR variables accordingly.

If there is a NOTES module, its name must be in the following form:
NxxUSR

1.25.1.3

Error Logging Control Files -

The error logging control files have device-specific
the

following

for

information

devices:

RX50
RD51

RD52
RD53
TK50

1.25.1.4

DCL Error

The following

Logging Commands

is a list of the DCL commands that are

for

wused

error

logging:
ANALYZE/ERROR LOG

SET

APPEND/ERROR LOG
CREATE/CFL
MESSAGE/ERROR_LOG

1.25.1.5

ERROR LOG

SHOW ERROR LOG
START/ERROR LOG
STOP/ERROR_LOG

DCL SHOW ERROR LOG Command Qualifiers -

The DCL command SHOW ERROR_LOG displays error logging information
the

specified

device

or,

The SHOW ERROR_LOG command

error logging information for all devices.
has the

following

for

vyou do not specify a device, displays

qualifiers:

/CU [RRENT]

Displays errors that have occurred on all devices since
the
1logging system was started using the
error
the
time
last
/JUPDATE
qualifier.
This
qualifier
provides
the
same
functionality as the MCR command ELI/SHOW/CURRENT.
/HI [STORY]

Displays

devices

since

started

summary of

using

the

errors

1last

that

have

occurred

all

time the error logging system was

the /ZERO qualifier.

This

qualfier

provides

the same functionality as the MCR command ELI/SHOW/HISTORY.
/RE [CENT]
Displays

order)

brief description

errors

(in

chronological

that have been recorded by the error logging system.

This qualifier provides
command ELI/SHOW/NEW.

the

same

functionality

the

MCR

RSX-11M-PLUS

1.25.1.6

The

MCR

ELI

command

SOFTWARE

Command

ELI

has

FEATURES AND

Switches

the

RESTRICTIONS

following

switches:

/SH[OW]
Displays

error

or,

you

information

logging

information

not

for

specify

all

devices.

for

the

device,

specified

displays

device

error

logging

/SH[OW]
/CU [RRENT]
Displays

last

errors

time

/UP[DATE]

that

the

have

error

occurred

1logging

switch.

all

system

devices

was

since

started

using

the
the

/SH[OW]
/HI [STORY]
Displays

devices

since

started

summary

using

the
the

errors
1last

/ZE[RO]

that

have

time the

error

occurred
logging

system

all
was

qualifier.

/SH[OW]
/NE [W]
Displays
order)

1.25.2

Error

brief description

that

Logging

have

been

recorded

errors
the

(in

error

chronological

logging

system.

Restriction

By moving

the error logging routines
to
the
Executive
common,
the
following
restriction is introduced:
if a driver of an error logging
device calls the SCRPKT routine to create an error logging packet, the
data
address for the data subpacket must not be an address within the
driver.
Specifically, the address must not be mapped
by
APR
5,
as
this
APR
is
used
to
map the common.
Any user-written driver that
performs

such a function must allocate a piece of pool,
appropriate
information,
and
pass
the
pool
address
Packet Routine.

1.25.3

Supplementary Error

Logging

fill

the

in
the
Create

Information

This

section describes information
from
the
previous
version
that
to
error
1logging.
Although this information is not new for
Version
3.0,
it
still
applies.
This
section
describes
the
relationship between hard and soft limits.
applies

Error

logging

allows

independently.

hard

and

Previously,

soft

error

reaching

one of

1limits

the

limits

reached

would

disable

logging of either kind of error on that
device.
Now,
reaching
the
soft limit does not affect the logging of hard errors and vice versa.

Device
soft

l1.26

time-outs

errors

are

logged

hard

errors

wunrecoverable

and

recoverable.

TASK BUILDER

This section describes new features, restrictions,
and
supplementary
information for the Task Builder (TKB) on RSX-11M-PLUS Version 3.0.

ONS

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTI
New Task Builder Features

1.26.1

er:

The following new features are supported for the Task Build
e

New TKB /SB switch and DCL /SLOW qualifier

New TKB /FM switch and DCL /CODE:FAST_MAP qualifier

FCSRES and FCSFSL change

TKB /CP replaces /AL

Creating a task builder with /SB as its default

STKBLD.BLD procedure

e New TKB /CL switch and DCL /CODE:CLI qualifier

1.26.1.1

New TKB /SB Switch and DCL LINK/SLOW Qualifier -

the system
The Slow Task Builder (STK) is not included separately in Builder
are
Task
the
and
Builder
Task
Slow
The
kit.
distribution
included together in one task image. Use the TKB switch /SB to select
the mode of the Task Builder that you want to use.

The following TKB command line for MCR shows the correct placement

the /SB switch:

TKB>file.tsk/SB,,=file.ob]

The following TKB

command

line

placement of the /SLOW qualifier.

for

DCL

demonstrates

the

correct

SLINK/TAS/SLOW/MAP/SYM INPUTFILE

The default is /-SB or that /SLOW is not enabled.

1.26.1.2

New TKB /CL Switch and DCL /CODE:CLI Qualifier -

The TKB switch /CL or DCL qualifier LLINK/CODE:CLI informs theYou Task
can
Builder that the task is a Command Line Interpreter (CLI).
when
switch
this
Use
CLI=YES.
ing
specify
then install a CLI without

you task build the DCL task or any other CLI task. You can still
install a CLI built without the /CLI switch by specifying CLI=YES when
(Note that the Fast Task Builder (FTB) does not
installing 1it.
support the /CL switch or /CODE:CLI qualifier.)
The following TKB

command

placement of the /CL switch:

line

for

MCR

demonstrates

the

correct

TKB>file.tsk/CL, ,=file.obj

The following TKB command line for DCL
placement of the /CODE:CLI qualifier:
SLINK/TAS/CODE:CLI/MAP/SYM

demonstrates

INPUTFILE

The default is /-CL or that /CODE:CLI is not enabled.

the

recommended

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

MAP Qualifier New MCR /FM Switch and DCL /CODE:FAST

1.26.1.3
The

TKB

switch

/FM

DCL

qualifier

/FAST

MAP

allow

space

for

fast

mapping.
This switch or qualifier informs the Task Builder that space
must be allocated in memory between the task and the
external
header
for use by the fast-mapping feature of the Executive.
The

/FM

switch

/CODE:FAST
MAP qualifier

command

qualifier

does

support

not

The

following

the

/FM

/FMAP=YES.

the

TKB

/FM

Note

that

corresponds

the

Fast

Task

the

switch

/FAST MAP

qualifier.

line

for

MCR shows

the

correct

DCL

the

recommended

command

INSTALL

Builder

(FTB)

placement

switch:

TKB>file.tsk/FM, ,=file.ob]j
The following TKB command line for
of the /CODE:FAST
MAP qualifier:
SLINK/TAS/CODE:FAST

The default

1.26.1.4

/-FM or

FCSRES

and

FCSRES and

FCSFSL

that

can

MAP/MAP/SYM

FCSFSL Change

into

either

not

enabled.

user-

placement

INPUTFILE

that /CODE:FAST
MAP

are merged

used

shows

single vectored-entry memory
or

supervisor-mode

image

libraries.

This

reduces both disk and memory space requirements.
The
[1,1]FCSRES.TSK
image
file
1installs
under
the
1library
name FCSRES and is used to
satisfy both user and supervisor library requests.
Existing tasks that reference FCSRES are unaffected by this change
need
not be rebuilt except to use new functionality (for example,
new

logical

name

parser,

rebuild
existing
FCSFSL directly or
been built
The

FCS

use

the

new

1library,

you

tasks that reference FCSFSL, whether they
by referencing a library (such as F77RES)

reference

resident

CSIS$4).

and

the
must

reference
that
has

FCSFSL.

1library

1image

([1,1]FCSRES.TSK)

has

been

built

containing
the
supervisor-mode library completion routine.
However,
because the user-mode FCSRES library
1is
a
memory-resident
overlaid
library,
it
must
be
distinguished from the supervisor-mode library
usage

(because

the

completion

routine

cannot

overlaid).

Thus,

the

files
for
FCSFSL
must
be used to build tasks using supervisor-mode
(the .TSK file is needed for information contained in the label block;
the .STB file is needed for symbol values and overlay structure).
To

supply

the

two

different

image, the Task Builder has
to become FCSRES references

This

1is

the

build

also

(LIBR=FCSRES
both
remain

considerably

Note

true

commands

or
in

for

the

both

descriptions

Fast

Task

codes

wuse

Builder

remain

SUPLIB=FCSFSL),
[1,1]
(although

the

same

1library

and
the

the

(FTB).

same

files (both
FCSFSL.TSK

In other
they

FCSFSL
image.

words,

have

.TSK and
file

been

.STB)
size

for
is

use

the

reduced).

that existing

tasks

referencing

previous version of FCSFSL until
the

but

been changed to force references to
in the resulting
executable
task

FCSFSL can

continue

they are rebuilt,

but they cannot use

new image file supplied under
the
name
[1,1]FCSFSL.TSK
Dbecause
this image does not contain executable library code.
Also, when tasks
specifying FCSFSL are built with the modified Task Builder,
they
are
forced to use the new, merged FCSRES image.

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

There

is one additional

consequence

this merge:

the new

image

can

generate a non-overlaid user-mode reference to FCSRES for tasks having
sufficient

virtual

address

space

available.

This

new mode

results

smaller task root code (from reduced or eliminated overlay RTS support
requirements) and faster task execution (from eliminating overlay
RTS

calls).
to

specify

To use the image in this new way, build the referencing task
the

FCSFSL

library

files

but

(LIBR=FCSFSL) .
The

possible

TKB Option

references

and

the

results

through
|

are

FCSRES

LIBR=

FCSFSL

SUPLIB=

FCSFSL

Result
Same as existing user-mode
FCSRES (PIC, memory-resident
overlaid, uses one APR)

New,

user-mode nonoverlaid

FCSRES

requires

(syntax

FCSRES

APRs

and

functionality

not

two APRs; was
- now PIC)

Invalid - completion routine

cannot be overlaid

TKB /CP Replaces /AL -

1.26.1.5

Task Builder

the /AL

two

Supervisor-mode FCSRES usage
changed;
absolute

SUPLIB=

reference

follows:

Library Specification

LIBR=

The

user mode

/CP

(/CHECK:TASK)

(/CHECK:SYSTEM)

switch

switch has been

in the SYSGEN.BLD files

tasks:

substituted

for the

for

following

HRC

HEL

MCD

SYL

BYE

TKN

SAV
INS

SHF
PMT

FCPLRG

SHU

The reason for this substitution is that external task header
support
is
automatically included in the full-functionality Executive option,
which
most
users
select.
Tasks
with
external
headers
can
be
checkpointed
only
to
a
system
checkpoint
file.
The /AL switch,
however,

never
task

allocates

used

eligible

checkpoint
image.

system

that

the

same task

the

checkpointing,

/AL switch had

Creating a Task Builder

with /SB as

the RL02 pregenerated distribution

that

image;

with external headers.

this

space

The /CP switch makes a

thus

eliminating

allocated within the

the

task

1.26.1.6

for

space

space within

tasks

1is

named

LB:[l,2]MAKESTK.CMD.

version of Slow
Task
Builder
(STK)
procedure
accepts
a
parameter
that
library or the FCSFSL library is used.
parameter.

kit,
The

Its

Default -

command

file

procedure

provided
creates

1in
LB:<LIBUIC>.
The
command
determines
whether the FCSRES
You can supply RES, FSL, or no

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

you

supply

version
Task

Builder

RES,

the

uses

the FCS routines
I1f

you

supply

version

MAKESTK.CMD copies

Task

the FCS

FSL,

the

library

resolve

resident

library to

MAKESTK.CMD copies

Task

uses

RL02

TKBRES.TSK file

(the

resolve

the

symbols

kit

the
for

the

TKBFSL.TSK

Builder on your system)

supervisor-mode

the
I-

symbols

and

version

file

(the

Builder

This

Task

the

FCS

This

resident

in the FCS routines that TKB uses.

D-space contains

Builder

1latest

into STKFSL.TSK.

FCSFSL.

If you supply no parameter, MAKESTK.CMD copies the TKB.TSK

STK.TSK.

latest

into STKRES.TSK.

that the Task Builder uses.

Task Builder

Only the

the

Builder on your system)

contains

the FCS

routines

file

that

into

the

Task

uses.

MAKESTK.CMD places the

LB:<LIBUIC>.

Then,

requested

version

the

Task

Builder

using a ZAP command, MAKESTK.CMD changes the TKB

default from /-SB or not enabling /SLOW,

to /SB or /SLOW.

STKBLD.BLD Procedure -

1.26.1.7

You can invoke a command procedure

generation.

called

STKBLD.BLD

STKBLD.BLD creates the Task Builder

during

system

.CMD and .ODL files.

The distributed Task Builder on the system uses these files
one of the following files with /SB as the default:

build

STK.TSK

STKRES.TSK
STKFSL.TSK

Task Builder Restrictions

1.26.2
The

following

restrictions apply to

the Task Builder:

Map supervisor-mode libraries at address

Do not use LINK /SLOW with

Only referenced symbols result in autoload vectors.

The

Base address displayed

Do not cluster

You should use the /SS switch with RSX11M.STB.

1.26.2.1

indirect command

first library specified must be

first

read-only and

read/write

libraries.,

A Supervisor-mode library must be mapped at virtual
library

used.

library entered.

incorrect.

Map Supervisor-Mode Libraries At Address

supervisor-mode

files.

address

e TM

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.26.2.2

Do Not Use LINK /SLOW With Indirect Command Files -

indirect

The LINK /SLOW qualifier does not function when used with an

If you invoke the Task Builder with an indirect command

command file.

file, you will have to accept the use of the standard Task Builder

add the /SB switch in the

1.26.2.3

indirect command file.

Only Referenced Symbols Result in Autoload Vectors -

Autoload vectors supplied by the symbol

table

(.STB)

files

the

1libraries are selectively included in the user's task image.

resident

Only referenced symbols result in autoload vectors that are present in
the

task

1.26.2.4

image.

The First Library Specified Must Be First Library Entered -

The first library specified in the CLSTR option should

first

the

library entered
by
the task.
If a memory-resident overlaid library
has been built with a null root, the install process merely checks for
the presence of the required libraries but does not map to them.
When
the default
1library entered becomes
first
the task executes, the
library,
regardless of the order in which the libraries are specified
in the CLSTR option statement.

If the first cluster element specified

the

llbrary

first

parameter passing,

the

that

entered

and

overlay

runtime

in the CLSTR statement

library

the

uses

the information passed between the cluster

elements

and

1.26.2.5

Base Address Displayed

system

1is

not

stack for

1library

becomes corrupted, which

results in unpredictable behavior of the executing task.

Incorrect -

the map as
in
A non-PIC shared region's base address is displayed
not zero, but has a true base address.
1is
The base address
zZero.
This problem is a map-generation problem of the Task Builder.

1.26.2.6

Do Not Cluster Read-Only and Read/Write Libraries -

Read-only and read/wrlte libraries cannot be clustered together.
form of clustering

1.26.2.7

is not supported.

You Should Use the /SS Switch with RSX11M.STB file

When you use the RSX11M.STB
file)

as an

input

that,

potentially,

file to TKB,

to the file specification.

The

(the

Executive

specifying

.STB file

TKB could exhaust

RSX11M.STB.

symbol

definition

you should always append the /SS switch

contains

many

symbols

library

modules

its virtual memory tables.

Explicitly include on the command line the

before

This

required

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS

1.26.3

Supplementary

Task

Builder

Information

This

section describes information
from
the
previous
to the Task Builder.
Although this information
Version 3.0, it is still valid.
This section describes
topics:
applies

Two

I-

and

D-space

task

Autoload

I-

and

D-space

task

disk

block

size

forms

symbol

Segment descriptor

1.26.3.1

Two

Forms

definition

of Symbol

the

.STB

version
that
is not new for

the

following

file

vectors
allocation

Definition

the

.STB File

The symbol table file (.STB) contains two forms of symbol
To
maintain
backward
compatibility,
all
autoloadable

definition.

symbols are
in the global symbol
directory,
and
the
vector
itself
is
in
associated
text
records.
Additionally,
the .STB file
contains a new internal symbol directory of autoloadable
symbols for
conventional
tasks,
as
well
as
the information needed to generate
Autoload vectors for I- and D-space tasks.

entries
defined

1.26.3.2

1I-

and

D-Space

Task

For I- and D-space tasks
two

parts:

I-space

program
A

Disk

D-space

part

the Autoload vectors consist

consisting

words

1I- and

D-Space

allocation

words

contained

Task

for

accommodate

I-

Disk

and

Block

contained

Allocation

D-space

overlay

into memory,

the

However,

the

memory

increased

segments

because

l1.26.3.4
The

size

speed

I-space
part
and
the
blocks.
The I-space part

these

Segment
of

depends
on
conventional
230(octal)
bytes.

program

1is

large

D-space part
comes
first

in
on

comes second.
When an overlay segment is
and
D-space
parts
are
read
separately.

with

over

the

segments

the

1I-

the

separate but adjacent disk
disk,
and
the D-space part

read

S$S$ALVI
consisting

S$SALVD

space

enough

(user mode),

part

section

section,

1.26.3.3

Vectors

Autoload

which

what

parts

Descriptor

are

1I-

and

D-space

would

normal

adjacent

Block

Size

the

parts

for

are

two

read

into

separate

disk.

the

segment descriptor
block
that
is
internal
to
TKB
whether
an
Iand
D-space task is being built.
For a
task, the size of
the
internal
segment
descriptor
is

bytes.

For

I-

and

D-space

task,

the

size

262 (octal)

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.27

LAYERED

PRODUCTS RESTRICTIONS

The following
Version 3.0:

restrictions apply to layered products

RSX-11M-PLUS

DCL

command

SET

the

FED

This section describes new features and supplementary information
MACRO-11 on RSX-11M-PLUS Version 3.0.

for

Command files containing SET /UIC commands

FMS-11

1.27.1

Command Files Containing

Because

support

DEFAULT/NONAMED

for

MCR

SET /UIC Commands

named

directories,

command

running any command files that use

1.27.2

SET

the

/NONAMED should be used before

the SET /UIC command.

FMs-11

FMS-11 Version 1.0 does not have named directory suppart
and

FUT

utilities.

support and

1.28

this will

FMS-11 Version 2.0 will

longer

include named directory

restriction.

MACRO-11

1.28.1

New MACRO-11 Features

The following new MACRO-11 features are supported:
®

Support

Corrections to the MACRO-11 Version 5.3 assembler

1.28.1.1

for

logical

names

Support for Logical Names -

MACRO-11 fully supports RSX logical names by calling the .CSI4
parsing

1.28.1.2

Corrections to the MACRO-1l1l Version 5.3 Assembler -

The following corrections have been made to the MACRO-11

assembler:

SYSLIB

routine.

Previous versions of MACRO-1l1l would hang
if
they
encountered
a
record with an
That

problem has been

fixed.

1-65

Version

in an infinite
invalid record

5.3
1loop
size.

RSX-11M-PLUS

MACRO-11 did
they

SOFTWARE

FEATURES AND

RESTRICTIONS

not mark symbolic expressions

contained

symbol

from a

complex

relocatable program

when

section

and a symbol from an absolute program section.
That resulted
in
incorrect
1linker
output
if
the
base
of the absolute
program section was not zero.
Those symbolic expressions are
correctly marked

MACRO-11

did

complex.

not mark

symbolic

expressions

complex

they
contained
symbols
from
different
absolute
sections.
That resulted in incorrect linker
output
base
of either program section was not zero.
Those
expressions are correctly marked as complex.

When MACRO-11 directly assigned
symbol

"."

global

symbol

the current

when

program
if
the
symbolic

location

counter

program

section,

absolute

MACRO-11 incorrectly bound the
global
symbol
to
the
.ABS
program
section.
MACRO-11l correctly binds the global symbol
to the absolute
program
section
in
which
the
assignment
occurred.
e

MACRO-11

characters,

encountered

MACRO-11 would hang

label

in an

containing

invalid

infinite loop if

existed a macro with the same name as the valid part
label name.
MACRO-1l1l correctly returns an error.

1.28.2

Supplementary MACRO-11

3.0,

MACRO-11.

Although

it is still valid.
5.2

there

the

Information

This section describes information

applies

this

from

the

information

previous
is

not

veréion

new

for

that

Version

This section includes the following topics:

Version

RSX changes

Use of colon

MCS

Version

Corrections

to the Version

Version

RSX-specific

Corrections

.ASCII\and

.ASCIZ strings

support

5.1

5.0

RSX-specific

changes

the Version

1.28.2.1
Version 5.2 RSX Changes
to MACRO-11 V5. 2.

5.1 assembler

5.0 assembler

There were no

RSX-specific

changes

made

1.28.2.2

Use of Colon in .ASCII and .ASCIZ Strings -

MACRO-11 does not allow the colon
.ASCII

.ASCIZ

strings.

(:)

This

character

1is documented

PDP-11 MACRO-11 Language Reference Manual.

delimiter

in Chapter

for

the

TM
r 0Y»es,%%

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
l1.28.2.3

MCS Support

MACRO-11 Version 5.2'provided support for the 8-bit DEC
(MCS).

Set

Character

Reference Manual

Multinational

See Appendix A of the PDP-11 MACRO-1l1l Language

for a table on MCS.

“

The following table lists the directives that support

The

MCS.

the

corresponding
section
numbers
are
locations in the PDP-11 MACRO-11
each
Language Reference Manual where you can access information about
‘

directive.

Macro

Section

6.3.4

.ASCII directive

.ASCIZ directive
.ERROR directive
.IF
directive
.IF

6.3.5
7.5
6.9.1

DIF

~ .IF IDN
. IFF
directive
.IFF
. IFF

6.9.2

DIF
IDN

. IRP

directive

7.6.1

.NCHR
.PRINT
. REM
.SBTTL
.TITLE

directive
directive
directive
directive
directive

7.4.2
7.5
6.1.6
6.1.3
6.1.2

.IRPC

7.6.2

directive

See the following section numbers
Reference
Manual
for
further
Multinational character set:

the
PDP-11
MACRO-1l1]
Language
information
on
the
8-bit
DEC

Section

2.2.4

Comment field

7.3.6

Keyword arguments

1.28.2.4

Version 5.1 RSX-Specific Changes -

Previous versions of MACRO-11 would exit

status
been

ASCII conversion characters
Arguments in macro definitions and macro calls

6.3.3
7.3

even

though

with

errors were reported.

fixed.

If MACRO-11 detected an I/0 error
while
reading
a
command
file,
MACRO-1]1
would
produce
an
odd-address
trap.
Now,
MACRO-11
reports
the
error
message
"MAC -- Command
1/0
error"”.
v

1.28.2.5

Corrections to the Version 5.1 Assembler -

The following corrections have been made to the MACRO-11

assembler:

exit

SUCCESS

That problem has

MACRO-11 Version 5.1 processed

floating-point

processes all

numbers

some

Version

index-deferred

default.

Now,

5.1

arguments

MACRO-11

index-deferred arguments as octal by default.

RSX-11M-PLUS

MACRO-11

did

statements

SOFTWARE

not

mark

internal
with

listing.

MACRO-11

set

object

bit

They
3,

files

are

MACRO-11
from

MACRO-11.

object
a

will

1.28.2.6

the

Version
The

displaced
an

with

files

the

result,

new

they

options

SEC

«PSECT

have

comparison of
resulting task

the

object

That change makes
of

MACRO-11

versions

different

of
PAT

the files will show
or .SAV image files

same.

cross-reference

all

version

with

will

5.0 RSX-Specific Changes

(')

correctly.

sets bit

created

relocatable

apostrophe

bit,

longer

checksums,
and
a
binary
differences.
However, the

RESTRICTIONS

now marked

unused

<created

different

AND

relocatable

assembly

records.

FEATURES

and

ERR have been

added.

NOTE

The
has

RSX-11
Cross-Reference
been updated to include

two

new macro

the

new

cross-reference

RSX-11

distributed

CRF

with

RSX-11M-PLUS

this

2.1

(CRF)

for

these

options.

version

RSX-11M

Version

version

Processor
support

Only

(Version

Version
should

4.1

and

used

with

MACRO-11.

The default for the
command
1line
option
/[-]SP
has
been
modified
from
/SP to /-SP.
The new default may be modified
by the system manager using the TKB GBLPAT
option
described
in the MACRO-11/RSX task build command file.

1.28.2.7

Corrections
The

code

permanent

the

JMP

the

Version

CALLR

addr

symbol

table

code.

complement

the

CALL

JSR

PC,addr

code.

The

for

version

automatic

range

Most

addr

local

30000$

(Call-Return)
(PST).

The
addr

This

65535$

change

Lines

.NLIST
are

code

table

that

statement

encountered.

the TOC argument
printed.

code,

generating

code

text

that

the
of

effect

You

may

now

include

was

assembly

the

time
the

table

the

symbols.

the

.SBTTL directive

the

added

upper/lower

readability of
.SBTTL

the

uppercase.

specify

the

of 64$ to
1278
MACRO-11 uses a

local

increase

equivalent

Now,

converted

1-68

code

range

listing

prevent

added
is

when

include

been
code

which

used

generation.

was made

contents

addr

MACRO-11

MACRO-11 code.
Lines of
.TITLE directive are not

the

has

This

CALLR

symbol

assembler-generated

case.,

5.0 Assembler

are

listing,

the

.NLIST

listed
even

.SBTTL

directive

contents

from

in
an

lines
with

being

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
The symbol table is printed at the end of an

the

even

assembly,

You may specify the

directive is in effect.

.NLIST

.NLIST directive with the SYM argument to prevent the

symbol

. table from being printed.

All page headers include the day of the week.

Total number of virtual work file reads

Total number of virtual work file writes

Maximum amount of virtual memory used

Size of physical memory free space (in words and pages)

Operating system and environment
running

end

The assembler statistics information that appears at the

of the assembly listing file has been updated to include the
following additional information:

that

the

assembler

the

1listing

under

elapsed assembly time

Total

MACRO-11 command line

The .PSECT synopsis that is

the

after

(in words and pages)

symbol

table,

number

printed

includes

the

program

file,

section

attributes.

The

maximum

expression

has

been

relocatable

changed.

terms

complex

The maximum size of an .OBJ

was
produce
can
that MACRO-1l1
record
42 (decimal) bytes to 128 (decimal) bytes.

increased

from

Do not compare .OBJ files that have been created by different
of MACRO-11 when verifying whether your code
versions
this
Changes that have been made for
generation is correct.

version

MACRO-11

direct comparison of

(mentioned

assembler

above)

.OBJ

will

output.

invalidate a

Verify

code

generation by linking or taskbuilding the .OBJ files involved
and then comparing the

.SAV or the .TSK image files.
NOTE

Because
version

files produced by this
.0OBJ
the
MACRO-11 are different, users of
of

are
Utility)
Patch
Module
the PAT (Object
checksums must be recomputed on
that
warned
this
with
assembled
patches
object
any
version of MACRO-11.

The default for the LC argument has been changed from
LC to .ENABL LC.

The following

.ENABL/.DSABL options have been added:

.ENABL LCM/.DSABL LCM
.ENABL MCL/.DSABL MCL

.DSABL
'

RSX-11M-PLUS

The

following

SOFTWARE

FEATURES AND

directives

are

Reference

Manual.

have

documented

been

RESTRICTIONS

added

the

MACRO-11.

PDP-11

MACRO-11

These

Language

.CROSS
. INCLUDE

. LIBRARY

.MDELETE

. NOCROSS
-REM

+WEAK

1.29

DECMAIL-11

This
on

section describes a new feature and

RSX-11M-PLUS

1.29.1

Version

New DECmail-11

DECmail-11

supports

restrictions

for

Feature

the

use

named

directories

addition

for
folder
names,
distribution lists, batch control
files specifications.
UICs will still be required in

file

(NAMES.DAT),

registration

1.29.2
The

used

of mail

DECmail-11

3.0.

users

input

NAMES.TSK,

your

system.

files

and

UICs

other

the
user
name
which controls the

DECmail-11 Restrictions

following

restrictions

®¢

Extended

®¢

New

1.29.2.1

logical

DECmail-1ll

Extended

DECmail-11

apply

names

DECmail-1l1:

not

supported

installation

Logical

Names

procedure

Not

Supported

Version

names

1in

some

cases,

2.0 does not support the
specifications.
While using

file

their

logical
the use

name
of the

1is

rather

than

logical

name

will

use

should

1longer

underscore

1logical
be

used

than

avoided,

the

instead

use
of
logical

especially

corresponding

character

device

(

)

the

1-70

the

cases

physical

indicate

same name,
physical

extended
names will

logical
work in

where

name.

device

will not work.

device

name.

the

Also,

The

RSX-11M-PLUS SOFTWARE FEATURES AND RESTRICTIONS
1.29.2.2
Several

New DECmail-1ll Installation Procedure changes

have

required

that

new

installation

command

file

included
with
Update
A.
You must use this new installation command
file in place of the version provided in the
distribution
kit.
For
information
regarding
use
of
the
new
procedure,
please refer to

DECMAIL.DOC

included

the

Update

A kit.

CHAPTER

CORRECTIONS TO DOCUMENTATION

chapter

This

documentation.

corrects

The

and

errors

omissions

the

1in

RSX-11M-PLUS

section titles in this chapter are the titles of

manuals that require correction.

2.1

RSX-11M-PLUS SYSTEM GENERATION AND INSTALLATION GUIDE

This section contains a note regarding

moved and a correction to an error.

documentation

that

has

been

They

are

SYSGEN Questions Removed

2.1.1

longer
are no
SYSGEN gquestions
following
The
documented as being asked in Section 3.2.2.

asked.

CEl122

Do you want host support for LAT terminal servers?

CE254

Do you want terminal driver extended I/O support?

These features are supported.
for LAT support to function.

2.1.2

Update

However, you must have
“

DECnet

support

Procedure

The Update procedure which was in the RSX-11M-PLUS Update Installation

Guide

and Update Notes, is described in Chapter 2 of the RSX-11M-PLUS

System Generation and Installation Guide.

2.2

RSX-11M-PLUS COMMAND LANGUAGE MANUAL

This section corrects errors and omissions in the RSX-11M-PLUS Command

Language Manual.

These corrections are as follows:
format

SHOW DEVICES command

Description of RUN/COMMAND

Additions to qualifiers

Corrections to qualifier descriptions

Miscellaneous

errors

CORRECTIONS TO DOCUMENTATION

Additional

task

Additional

error message

2.2.1

SHOW DEVICES

Section

follows:

5.13.3,

status

Command

the

Format

correct

SHOW DEVICES[/attribute]
The parameter dd[nn:]
that

you

want

flags

the

syntax

for

the

SHOW

DEVICES

command

1is

([dd[nn:]]
specific device or

examine.

The

/dd[nn:]

the

type

qualifier

device

not

valid

qualifier.

2.2.2
In

Description of

Section

7.2.1,

incorrect.

The

the

RUN/COMMAND
description

description

should

for

the

read

DCL

command

RUN/COMMAND

follows:

RUN/COMMAND:
" taskcommand"
Passes

the

specified

The
command
must
valid for the task

command

begin
or
a

line

the

task

you

command
must be inside the quotation marks (")
40 characters long.
For example, the following

S RUN/COMMAND:"PIP
/LI"TM

SPIP

When

2.2.3

The
of

the

running.

it must be
Also
the

and not more
command:

than

(E]

runs PIP and then passes the /LI switch to it.
directory

are

with the task's acronym and
syntax
error
will
occur.

The result

listing.
task

has

finished

executing

the

command

the

Quick

line,

the

task

removed.

Additions

following
Chapter

Qualifiers

qualifiers are missing

from

DEFINE/FINAL

DEFINE/TRANSLATION ATTRIBUTE=TERMINAL

HELP/LOCAL

SET

SHOW

TERMINAL/MCR

Reference

Section

CORRECTIONS TO DOCUMENTATION

Corrections to Qualifier Descriptions

2.2.4

qualifiers

The following

are

Reference Section of Chapter 9:
e

e
~
e

incorrectly described

DELETE/[NO]CONFIRM

is a synonym for /[NO]QUERY.
/[NO]JCONFIRM
INITIALIZE/UPDATE/DENSITY:arg
The argument is either HIGH or LOW.
INSTALL/EXTENSION:n

The argument n is decimal.

LINK/CODE: [NO]FPP
FPP is the default argument.

MOUNT/WINDOW:arg

e
e

Quick

the

The three arguments are:

n, (USER:n, INDEX:n), and FULL

PRINT/[NO]JWIDE

/[NOJWIDE is not a valid qualifier.
RUN/EXTENSION:n

The argument n is decimal.

Miscellaneous Errors

2.2.5

Correct the following miscellaneous errors in the RSX-11M-PLUS Command
|

Language Manual:

e
e

Section 4.8.2 - DELETE,

missing.

/[NO]JCONFIRM

qualifier

not

In Section 4.10.1 - PRINT, the /[NOJWIDE qualifier

valid qualifier.

Section

/DENSITY
using

the

It is a synonym for /[NO]QUERY.

5.9 - MOUNT,

qualifier

density

the

specified

with

the

cannot be altered; it can only be checked

INITIALIZE/UPDATE/DENSITY.

In Section 5.10 - DISMOUNT, the /[NO]UNLOAD qualifier

applies

only to magnetic tape devices.

In Section 5.11.1 - INITIALIZE/UPDATE, the

for

the

/DENSITY

correct

qualifier are HIGH and LOW.

arguments

/DENSITY does

not alter the density value in the Volume Home Block, but
checks the density value established when the volume was
initialized.

In Section 5.13.3 - SHOW DEVICES, the correct syntax

SHOW DEVICES command is as follows:
SHOW DEVICES[/attribute]

that

you

want to examine.

not a valid qualifier.

the

type

[dd[nn:]]

The parameter dd[nn:] is the specific device or

device

for

the

The /dd([nn:] qualifier is

CORRECTIONS

Section

6.5.1

/CODE: [NO]FPP.

LINK,

The

the

In Section 8.1.3 - SET SYSTEM,

are

2.2.6

stored.

Additional

Section

The

Task

7.14.3.1,

brackets

Status

add

the

TS.NRP

Mapped

TS .RUN

Running

status

flag

TS.CHK,

should

2.2.7

Additional

Error

Message

following

error

message

Add

the

yyy

You did
command line.

the

Action:

proper

the /NETWOR
UIC
K qualifier
required

task

status

non-resident

another

flags

T2.CHK;

and

Chapter

10:

not

specify

the

prevent

run

for

the

bad

blocks

Reenter

the

command

1line

after

an error

the

RSX-11M/M-PLUS

description

bad

blocks

the

Bad

number

are

the

incorrect.

parameter

checking

for

MCR

Operations

from

Block

/BAD=[option]
The

being

Locator

and

location

not

allocated

correct

allocated

Utility
bad

keyword for the MCR
description follows:
to

files

(BAD).

blocks.

any other

non-last-track

the

last

addresses

Bad

good

Detected

Sector

File

SDBSF.

INI

the

Sector

the
File

(SDBSF).
then

and

the

creates

SDBSF.

BAD

records

the

device.

Bad

Descriptor

devices,

Bad

MDBSF

block

called

Block

last-track

devices,

Block

File

the

volume,

tests

volumes

way,

known

this

upon

the

input

data

generated

testing.

addresses

bad

blocks

This
Descriptor

create

last

track can
(MDBSF), and
a

BAD

file.

The way in which INI creates BADBLK.SYS depends
receives
from
the
BAD utility.
In turn, the
BAD differs according to the type of device it

the

flag,

syntax.

INI [TVOLUME]

first

the

7-2:

Manual.

Chapter

status

destination

section corrects

Table

partition

This

processor

RSX-11M/M-PLUS MCR OPERATIONS REFERENCE MANUAL

command

has

syntax.

2.3

Reference

expected

Explanation:

User

should

TS.RDN.

Destination

are

should

T3.RDN

argument

the default.

:[directory].
You need this argument
in which all the DECnet-related tasks

following

NRP

the

Flags

RUN

Also,

/CODE:FPP

FPP argument

the following argument:
to specify the directory

DOCUMENTATION

writes

BADBLK.SYS

a
by

1list
of
bad
block
File.
INI then uses
BADBLK.SYS.
However,
on
contain

a
Software

record

combining

Manufacturer's

bad
the

Detected

blocks
input

Bad

the
from
o,

TO DOCUMENTATION

CORRECTIONS

non-last-track

If you want BAD to treat a last-track device as a

device, specify the /OVERRIDE switch in the BAD command line.

response

Descriptor

the

File

switch,

JOVERRIDE

Then, when you initialize the volume, you must also

/BAD

[OVR]

KkKeyword with the

Block

specify

the

1last good block before the last track.

the

1In

Bad

writes

BAD

option

(INI /BAD=[OVR]), so that INI

can locate the Bad Block Descriptor File and

wuse

create

1it

BADBLK.SYS.

you do not specify the /BAD keyword with the INI command,

default

action

command

the

/BAD=[AUTO].
The

automatically performs bad block processing.

the

That is, INI

other

options

of the /BAD keyword allow you to modify the default action of the
command.

2.4

RSX-11M/M-PLUS INDIRECT COMMAND PROCESSOR MANUAL

This section corrects

omissions

Indirect Command Processor Manual.
®

Invalid

and

errors

the

RSX-11M/M-PLUS

These corrections are as follows:

symbol value
condition

for

.ONERR

<SYSTEM> Symbol Value

2.4.1

In Section 2.4.1.2, page 2-19, add the following statement:

The special symbol <SYSTEM> will have a value of 5 if Indirect is

running on a VMS host under VAX-11l RSX.

2.4.2

1Invalid Condition for

In Section 2.6.22,

.ONERR

page 78, add the following statement:

For the .ONERR directive, the first item in

conditions

1is

not

valid

condition.

the

1list

error

This item should be as

follows:

Task not

2.4.3

installed

in system

(.XQT,

.WAIT)

J.ASK Time-out Values

Sections 2.5.2,
specification.

2.6.3, and 2.6.4 include ticks
This is incorrect.

valid

time-out

CORRECTIONS

2.5

TO DOCUMENTATION

RSX-11M/M-PLUS AND MICRO/RSX EXECUTIVE REFERENCE MANUAL

This section corrects omissions
Micro/RSX
Exectuive . Reference

and

follows:

The

Parameter

list

for

CALL

RCTLON

Parameter

list

for

RLONS

and

Macro

the

RLONS

Parameter

list

for

CALL

TRALON

Parameter

list

for

TLONS

and

Macro

the

TLONS

following

2.5.1
The

errors

Manual.

expansion

for

expansion

for

corrections

Parameter

parameter

List

list

for

apply

for

CALL

and

the

RSX-11M/M-PLUS

corrections

CALL

and

are

RCTLOG

RLOGS
directive

and

CALL

TRALOG

TLOGS

directive

both

RCTLON

These

the

and
and

FORTRAN

CALL

and

Macro

calls.

should

RCTLOG

CALL

RCTLOG

follows:

(mod,itbmsk,[status],lns,lnssz,iens,ienssz,[rsize],[rtbmod],[idsW])

2.5.2
The

Parameter List for RLON$ and RLOGS

parameter

list

for

RLONS

and

RLOGS

should

follows:

mod, [tbmsk],[status],lns,lnssz,ens,enssz,[rsize],
[rtbmod]

2.5.3

Macro

The

first

read

RLONS$

The

line

for

the

the macro

RLONS Directive

expansion

for

the

RLONS

directive

should

follows:

MOD, TBMSK, STATUS,LNS,LNSSZ,ENS,ENSSZ,RSIZE,
RTBMOD

rest

2.5.4

Expansion

the

Parameter

parameter

expansion

List

list

for

correct.

CALL

follows:

TRALON

and

CALL

TRALOG

CALL

TRALOG

should

(mod,tbmSk,[status],lns,lnssz,ens,ienssz,[rsize],[rtbmod][,idsw])

2.5.5
The

Parameter

parameter

List

list

for

TLONS

and

TLOGS

should

follows:

mod, tbmsk, [status],lns,lnssz,ens,enssz,[rsize],
[rtbmod]

CORRECTIONS TO DOCUMENTATION
2.5.6

Macro Expansion for the TLONS Directive

directive

The first line of the macro expansion for the TLONS$
read

should

follows:

TLONS MOD, TBMSK,STATUS,LNS,LNSSZ,ENS,
ENSSZ,RSIZE, RTBMOD

The rest of the expansion is correct.

2.6

RSX-11M/M-PLUS SYSTEM MANAGEMENT GUIDE

1last

In the de§cription of the RMDemo D page, the value for the

1ncorrect.

always

2.7

The

statistic

for write % deferred

(last line)

1line

will

zero.

RSX-11M/M-PLUS AND MICRO/RSX DEBUGGING REFERENCE MANUAL

manual' combines

This

information about XDT.

IAS/RSX-11

the

ODT

and

Manual

Reference

Information specific to IAS has been deleted.

The RSX-11M, RSX-11M-PLUS, and Micro/RSX Executives all

contain

code

that detects
certain types of internal system corruption.
If XDT is
included in the system, the Executive attempts to enter XDT as soon as
the
system
corruption
1is detected.
XDT on RSX-11M-PLUS systems and

loadable XDT use bug checks to report this type of error.
includes

2.8

information on

This manual

interpreting bug checks.

RSX-11M/M-PLUS BATCH AND QUEUE OPERATIONS MANUAL

This section corrects omissions and errors in the RSX-11M/M-PLUS Batch

and

Queue

follows:

2.8.1

Operations

command

Manual.

These

errors

SUBMIT

/[NO]TRANSFER qualifier description

Batch

log

and

omlsslons are as

format

information

SUBMIT Command Format

In Section 3.7, page 3-15, the MCR format for the

SUBMIT

command

1is

slash

(/)

unclear in that a place for specifying the MCR batch log file switches
is omitted.

The

format should be as

follows:

MCR> SUBMIT [queuename:][jobname][/jobswitch[s]]][1ogfileswitch[es]]=filespec([s]

Note that all the logfile

except the SUB jobname=

[/fileswitch(es)]

switches

switch.

require

preceding

CORRECTIONS

2.8.2
In

/[NO]TRANSFER

Qualifier

DOCUMENTATION

Description

Section

2.2, page 2-6,
the
description
of
the
PRINT
command's
/ [NO]TRANSFER,
does not mention that when a copy of a file
transferred from a private device and then printed, the copy of the

qualifier
is

file 1is
device.

2.8.3
On

deleted.

Batch

page

Log

3-19,

The

original

file

not

deleted

from

the

private

Information

replace

the

second

and

following:

third

paragraphs

with

the

|
The

log

time

file

they

comments

includes

were

and

the

commands

executed,

optionally

the

10g1n

the

batch

error messages

messages,

and

chain,

the

received,

any

the

for
the
job.
The log also includes all system
would normally appear on your terminal during an

data

blocks

output

that

interactive

session.

The

log

file

spooled

file

job

qualifiers
If

you

output

used

specify

2.9

own

the

appended

log

the

with
the
default
batch log file.

/NOLOG

job.
spooled as

UTILITIES

file,

the

printed

PRINT command

RSX-11M/M-PLUS

contains

maps

for

be
no log file
or maps will be

its

job

/NOPRINT

separate

well

job.

any

The

log

command

qualifier,

Therefore,

qualifiers.

any

there
will
output, listings,

3jobs,

each

with

MANUAL

This section corrects
errors
and
omissions
in
the
RSX-11M/M-PLUS
Utilities Manual.
Utilites requiring correction are presented here in
alphabetical order.

2.9.1

BRU

This

section

Utility

corrects

(BRU)

corrections

errors

chapter

are

and

the

omissions

follows:

Indirect

Wildcards

/NOSUPERSEDE qualifier

/VERIFY qualifier

®¢

Changes

®¢

Tape

MANUAL option

command

write

files

input

specifications

error

description

Stand-alone

RSX-11M/M-PLUS

BRU

message

the

Backup

Utilities

and

Manual

Restore

These

CORRECTIONS

DOCUMENTATION

Indirect Command Files -

2.9.1.1
Add

the

following

Section

7.0,

page

7-1:

You can execute an indirect command file containing BRU
from

BRU.

specification

2.9.1.2

for

Wildcards

so,

the

type

This is

BRU does not

types

file

1like

utilities.
@

wildcards.

the

page

number

UFD

treated
to

7-19,

add

the

qualifier causes
the output file.

the

file

omitted,

they were wildcards.

file

1is consistent

names

with

other

file

RSX

in that:
will

treated

1like

NAME.EXT is equivalent to NAME.EXT;*.

specified,

omitted

utilities

[UFD]*.*;*,

the entire

wildcard.

file

For

specification

example,

[UFD]

1is

following:

file
and
an
input
file
have
identical
file
but
different
version numbers, the /NOSUPERSEDE
the

input

file

to be copied but does not

delete

/VERIFY Qualifier Description -

The description of the BRU /VERIFY
7-22,

commands

/NOSUPERSEDE Qualifier Description -

When an output
specifications

2.9.1.4

behavior

For example,

equivalent

2.9.1.3

This

version

only the

will

followed by

file.

elements as

treat

BRU differs from other

wildcard.

(@)

the documentation states that BRU treats

specification

incorrect.

sign

Input Specifications -

page 7-8,

omitted

indirect command

In Section 7.2.2.1,

all

inaccurate.

qualifier

The description

should

1in

Section

read

7.4,

page

follows:

/VERIFY

Verifies

that

the

output

volume

was

written

correctly

comparing the input volume to the output volume and reporting any

differences.

During

a backup operation,

the

beginning

the verify operation.

operation,

however,

volume

each

starting

tape or disk

verified

Dbefore

backup

1is

restored

before

in the backup set.

the entire

set

During a restore

CORRECTIONS

2.9.1.5
In

Changes

Section

7.5,

Stand-Alone

page

7-23,

BRU

the

DOCUMENTATION

device

table

should

follows:

Device

CSR

Vector

CSR Status

172150

154

not

172440

330

present

172522

224

not

present

160000

320

not

present

174500

260

present

FOR=0

2.9.1.6

Tape Write

Section

message

action

7.4,

"BRU

BRU

User

7-54,

the

Action:

BRU

point

the

will

part

used

later

verify or

the

error

2.9.1.7

Section

the

recurs

"bad"

backup

Option

7.6.3,

incorrect

for

occurred

ERROR."

The

the

correct

user

page

that

the

error

with

this

replacement

tape

from

tape

was

This

"bad"

tape

should

not

problem might

set

restore

tape
drive;
BRU and start

MANUAL

WRITE

ERROR

tape

rewrite

NOT

present

Action"

TAPE

TAPE WRITE

Replace

another.

and,

begun.

consequently,

the

same

operations.

replacement

tape,

the

clean
over on

the
heads
on
another drive.

replace

the

tape

drive

get

press

list
the

When

you

BRU

will

7-25,

DMP

This

section

(DMP)

last

two

typed

paragraphs with

the

corrections

and

continue

New /LIM

/HF

you

have

far,

type

slash

(/)

entering bad blocks, type 2 slashes
(//).
allocate the bad blocks which you have entered to

corrects
are

LBNs
key.

finished

then

chapter

the

RETURN

have

BADBLK.SYS

2.9.2

following:
To

"User
--

changed

follows:

*WARNING*

that

Message

*WARNING*

read

with
the
terminate

page
--

should

Error

errors
the

processing.

and

follows:

switch

omissions

RSX-11M/M-PLUS

description

the

File

Utilities

Dump

Manual.

Utility
These

CORRECTIONS TO DOCUMENTATION

New /LIM Switch -

2.9.2.1
Add

the

following

new

switch

Table

Switch
Specifies

record

default

page

11-3:

Description

/LIM:n:m

2.9.2.2

1l1-1,

the

range

block

bytes

format

switches

are

Section

11.4,

page

the

each

the

specified.

11-6,

replace

the

1last

sentence

before

the

selected

following:

Other blocks are output as a data dump in the
/AS, /BY, and so on, in default octal-words.

format

FLX

2.9.3

section corrects

the

File

Transfer

RSX-11M/M-PLUS Utilities Manual.
@

Transfer

Default file types

/ZE

/DE/RT

switch example

/NU/RT

switch example

Additional

2.9.3.1

/OCT is still

/HF Switch Description -

example with

This

through m

to be dumped.

mode

(FLX)

chapter

the

switches

for

the

Image mode switch

switch description

error message

Transfer Mode Switches

page 4-5,

Program

These corrections are as follows:

Table

4-1,

the

following

switches accept octal

numbers by

default:

/FA:n /FB:n /IM:n /BL:n /BS:n /NUin /ZE:n
If you want to assign decimal numbers

these

(.).

For

the

value

decimal value 18

of n with

period

to the /IM:n switch you type:

switches,
example,

you

must

assign

the

/IM:18.
The /DNS:n

switch accepts decimal

numbers by default.

Therefore,

do not need to follow the value of the /DNS:n switch with a period
if

the

2.9.3.2

value

Default

decimal.

File

Types

for

the

Image Mode

On page 4-6, the file type .CDA should be added
file types for the Image mode switch.

Switch

you

(.)

to the list of default

CORRECTIONS

2.9.3.3

/ZE

Switch

4-2,

FLX

Table

the

2.9.3.4

Section

2.9.3.5

4.4.2,

/NU/RT

This

2.9.3.6

FLX

results

4-21,

the

Device

Error

size

Action:

This

section

chapter
In

The

User

FMT

and

corrects

error

This

section

program

corrects

(LBR)

corrections

line

message

65K

file

the

example

specification

the

paragraph

directory

should

RD51,

selected

RD52,

RD53,

RX50.

FLX.

supported

with

Reenter

the

command

1line

error

errors

User

Create

/IN

file

following

entries,

RT-11

device

Devices

specifying

in
the
Disk
Volume
Utilities Manual.

and

the

follows:

attributes

switch

at
the

each

added:

cannot

chapter

are

blocks

DU device

RSX-11M/M-PLUS

5.4, page 5-9, add DL:
/VE switches can be used.

LBR

sentence

(/CR)

switch description

the

omissions

list

RSX-11M/M-PLUS

the

not

greater

wvalid

Formatter

(FMT)

device.

the

2.9.5

the

324 (decimal)

Section

/WLT

last

specification.

specification

last

Message

RCF25,

65K blocks

2.9.4

exceeds

than

RT-11

the

words.

following

RC25,

4-8,

the

total

file

well
SYS1.MAC.

Example

Explanation:
an

the

4-13,
read:

uses

page

Additional

page

4-12,

Switch

should

which

allow a

Example

page

4.4.3,

example

Switch

read:

not

of
the
page,
line, should be

Section

the

does

DOCUMENTATION

Switches,

should

switch

/DE/RT

the
top
following

Control

first paragraph
The /ZE

Description

devices

Librarian

Utilities

which

the

Utilitiy

Manual.

These

CORRECTIONS TO DOCUMENTATION

User File Attributes -

2.9.5.1

On page 10-7,

are

header

in Figure 10-7,

the bytes 40(octal)

to the

end

the

The documentation

referred to as "user file attributes".

does not state what these attributes are or what their relationship is
with the FDB of the original file from which the module was created.
Insert

the

following

paragraph:

The FDB of the original

sections

file from which the

information,

has

five

Record

type

Record

attribute

Record

size

Highest

End-of-file block number

Optional

These attributes are as

attributes."

virtual

module

was

created

wuniversal

library,

the first being "user file

follows:

block

information

When you create a file and insert it into

You
LBR copies the input file attributes to the module header.
the modify header
can modify some of these attributes by using
switch

2.9.5.2

(/MH).

Create Switch

(/CR)

the
specifying
In Section 10.5.2, page 10-12, the format for
follows:
as
is
format
correct
The
incorrect.
is
(/CR)
switch

Create

outfile/CR:size:ept:mnt:libtype:infiletype

2.9.5.3

/IN Switch Description -

In Section 10.5.8, page 10-19, delete the following sentence:

LBR recognizes only uppercase characters 1in macro directives.
This

2.9.6

longer

true.

PAT

This section corrects an omission in the Object Module
(PAT) chapter of the RSX-11M/M-PLUS Utilities Manual.
On page 14-13,

add

Patch

Utility

space

1in

the

with

the following new error message:

UNABLE TO OPEN FILE filename
Explanation:

There

User Action:

Install

1is

insufficient

work

internal File Storage Region (FSR) of the PAT utility.
increment.

Run

the

PAT

wutility

CORRECTIONS

2.9.7

PIP

This

section

corrects

errors

TO DOCUMENTATION

and

omissions

Interchangey,
Program
(PIP)
chapter
of
the
Manual.
These corrections are as follows:

/DD switch

format

/TD

format

Section

The

switch

3.2.2.4,

correct

page

examples

3-17,

are

the /DD
follows:

switch

in
the
the
Peripheral
RSX-11M/M-PLUS Utilities

examples

are

incorrect.

format

1is

incorrect.

Examples

PIP>/DD:01-JUN-80:01-JUL-80&/LI

2.
3.

PIP>/DD:*:1-JUN-80&/LI
PIP>/DD:1-JUN-80:*&
/LI

2.9.7.2
In

/TD

Section

The

Switch

Format

3.2.2.25,

page

format

correct

3-40, the
follows:

/TD

switch

PIP>/TD&/LI

2.9.8

SLP

This

section

Input

These

corrects

Program

corrections

are

Inaccurate

®@

Maximum

®@

SLP

2.9.8.1

error

Inaccurate

Section

13.5.2,

error

messages

and

chapter

omissions

the

RSX-11M/M-PLUS

Source

Language

Utilities

Manual.

follows:

example

number

SLP

errors

(SLP)

characters

file

names

message

Example

page
1s

13-20,

the

incorrect.

FATAL-ILLEGAL

SHIRLEY.MAC;
2/CF

SWITCH

example
The

illustrating

correct

FILESPEC

example

the
as

format

for

follows:

CORRECTIONS TO DOCUMENTATION

2.9.8.2

Maximum Number of Characters

in File Names -

On‘page 13-21, the "Illegal File Name" error
file

names

is incorrect.

characters

2.9.8.3

The
read

can be a maximum of

SLP

length.

Error

SLP

can

names

file

message

indicates

that

characters

in length.
This
19(decimal)
of
maximum

Message

error message:
as follows:

30(octal)

FATAL-ILLEGAL SWITCH

page

one

13-22

should

SLP -- FATAL-ILLEGAL SWITCH OR FILESPEC
command

line

segment

Explanation:

This

error

has

occurred

switch was

not a

legal

for

the

following

reasons:

The

A legal

file

switch was used

switch or

section corrects errors and

omissions

Library Routines Reference Manual.

2.10.1
In

1line,

specifying

the

legal

specification.

IAS/RSX-11 SYSTEM LIBRARY ROUTINES REFERENCE MANUAL

2.10
This

file

not be parsed

command

Reenter the

correct

illegal manner

in an

specification could

User Action:

SLP switch

Virtual

address

Additional SYSLIB routines

®@

Miscellaneous

the

IAS/RSX-11

System

first

These corrections are as follows:

units

errors

Virtual Address Units

Section

8.5.2,

add

the

following

information

the

paragraph:

Virtual
bytes.

address units are words,

and dynamic memory addresses are

CORRECTIONS

2.10.2
The

Additional

following

added

program

Table

SYSLIB

DOCUMENTATION

Routines

section

names

and

SYSLIB

routines

should

1-1:

Routines

Program

Section

Module

Routine

Name

Name (S)

PURSD

CATS5B

SCATSB

(data)
EDTMG

SEDTMG

(data)

PURSI

CATS5B

SCATSB

(instruction)
o

SEDTMG

EDTMG

(instruction)

2.10.3

Miscellaneous

Errors

Correct

the

miscellaneous

following

Library Routines
e

Section

should

2.1,

enclose

Section

under

Reference

For

HH,

all

values

Section

page

the

page

$TIM

routine

the

8.2,

Section

should
item.

page

the

IAS/RSX-11

box

the

top

Address

add

the

6-4,

S$SAVAL"

of
line.

following

always returns

8.4.1,

replace

8-6,

second

The

RSX-11M/M-PLUS

add

address

System

the

page

—

information

characters

for

Miscellaneous

Errors

page
"“"disk

8-16,

the

FDB must

the

address,"

words
in

the

errors

These

errors

overlay capability

Supervisor-mode

following

global

symbol

list:
be

stored

the

—

SINIVM.
"virtual
fourth

address"

bulleted

list

RSX-11M/M-PLUS

and

AND MICRO/RSX TASK BUILDER MANUAL

Additions

two

SWRKPT before calling

follows:

the

bulleted

This section corrects omissions and
Micro/RSX
Task
Builder
Manual.

the

specified.

word

2,11

2-3,

"Return

6.2.2,

SWRKPT

NOTE:

definition

errors

Manual:

libraries

building

SUPER

the

and

omissions

are

CORRECTIONS TO DOCUMENTATION
switches together

the /-PI and /LI

Using

/SHAREABLE:LIBRARY qualifier description

Changes

Changes to the resident common/library name block date

Additional

the task

Miscellaneous Errors

Correct

the

following miscellaneous errors:

2.11.2

in Chapters

and 8.

error.

The reference on page 1-9 to the "/" character in Chapter 4
Refer to the discussion of the /MP switch in
1incorrect.
is
10

instead.

In Section 5.2.3.5, a semicolon (;) is placed after LB in the
Replace the semicolon with a
line of the example.
second

colon

typographical

The occurrence of double brackets is a

They occur

Chapter

block

error message

2.11.1

label

(:)

(LB:).

On pages 8-8 and 8-17,
not

[1l,2]

[1l,1]

and

through

14.

SYSLIB.OLB is in directory

indicated.

Errors in Overlay Capability

In Section 3.6.1, there is a factual error in

These steps should

read as

follows:

steps

10.

,B0-(Bl
Step 3A: Write .ROOT CNTRL- (AO-(Al1,A2-(A21,A22))

11.

Step 3B: Write

12.

Step 3C: Write .ROOT CNTRL- (AO-(Al1,A2-(A21,A22)),B0-(B1,B2)

13.

Step 3B: Write

14.

Step 3C: Write .ROOT CNTRL- (AO- (A1,A2-(A21,A22)),B0-(B1,B2),C)

.ROOT CNTRL-(AO-(Al,A2-(A21,A22)),B0-(Bl,B2

.ROOT CNTRL-(AO-(Al,A2-(A21,A22)),B0-(B1l,B2),C

.ROOT statement.

In Section 3.6.2, a factual error occurs in the

The

statement should read as follows:

.ROOT CNTRL- (AO-(Al,A2-(A21,A22)) ,B0-(B1,B2),C)

The root statement with AFCTR included (the last

Section 3.6.2)

should read as

follows:

.ROOT

statement

.ROOT CNTRL- (AFCTR,BO-(B1,B2),C)

In Section 3.6.3, the first

should read as

.ROOT

statement

(without

the

follows:

.ROOT CNTRL- (AFCTR,BO0-(B1,B2),C)

The second .ROOT statement should read as follows:
. ROOT CNTRL-(AFCTR,BO-(Bl,BZ),C),CNTRLZ—(CNTRLX,CNTRLY)

co-tree)

CORRECTIONS

2.11.3

Supervisor-Mode

The map

for

SUPER

SUPER.TSK; 3

Partition

Memory

name

GEN

03.01

Task

UIC

:
attributes:

Total

address

Task

1image

Task

address

R-W disk
Root

page

8-11

windows:

map

changed

Page

000343

limits:

000002

000001

000O1.

CMPAL

limits:

000000

000341

000342

limits:

00226.

000002

000001

00001.

allocation

synopsis:

Section
.

words

000000

Disk

Memory

follows:

TKB M41.00

R/W mem

blk

128.

limits:

segment:

has

[7,61]
-HD,PI

size

blk

Libraries

allocation

Identification

TO DOCUMENTATION

BLK.:(RW,I,LCL,REL,CON)
|

Title

1Ident

File

000000

000342

00226.

000000

000140

00096.

CMPAL

03.01

SYSLIB.OLB;l

000140
000300

000140
000042

00096.
00034.

SUPER
SAVAL

01
00

SUPER.OBJ;
3
SYSLIB.OLB;1

SCMPCS

000110-R

Global stbols:
SEARCH

000220-R

SORT

000140-R

$SAVAL

000300-R

SSRTI

000002-R

Task

builder

Total

work

Work

file

references:

reads:

300.

0.
6466.
1024.

words
words

Additions

to Building

8-18,

the

add

The

page

using

and

address

352

space

SUPER

Using
10-30,

the

/-PI

the

/-PI/LI

SORT
and

and

item

5112

and

documented.

5122

1list

were
in
to

located
the

describing

virtual

the

virtual
address

mode-switching

respectively,

TSUP.

Together

incorrectly

together.

building a library, the region program
the
same as that of the library root.
.ABS

that

relocated

Switches

documentation

bulleted

respectively,

been

/LI

switches

the

8-2:

subroutines
274,

Example

have

residing

the

SUPER

following

allocation map

vectors

2.11.5

(25. pages)
(4. pages)

time:00:00:08

2.11.4
page

file writes:
of core pool:
Size of work file:

the memory

000022-R

statistics:

Work
Size

Elapsed

S$CMPAL

describes

you

use

section name
The name of

the

these

effect

switches

for

the

library

when

library
is

is
not

CORRECTIONS TO DOCUMENTATION

/SHAREABLE:LIBRARY Qualifier Description

2.11.6

Section

5.1.1

the

incorrectly documents

effect

using

the

g
/SHAREABLE:LIBRARY qualifier. If you use this qualifier when buildin
same
the
is
y
librar
the
for
name
n
a library, the region program sectio
as

of the library root.

that

The name of the library is not .ABS as

documented.

Changes to the Task Label Block

2.11.7

Add the following changes to Task Label Block
ue

Label block revision

Table B-1 of Appendix B:

number

772

LSBLRL::

774

; Second task flags word
LSBFL2::
s+ Task uses fast map
000002
T2 SFMP

T2SCLI

000001

Task is a CLI

’

and

(l=yes)

directive

B-5

Figure

(l=yes)

The following is a new bit definition for LS$BFLG:

LSBFLG::

; Task flags word

TSSNEW

000001

; Label block uses
new

format means

:
LSAME:

wSs

776

s+ LSBLRL describes format)

2.11.8

Always null for AME
Compatability (the last
word in Label Block 0)

Changes to the Resident Common/Library Name Block Date

Add the following changes to the Resident

Date in Table B-2 of Appendix B:

The following is a new bit

Common/Library

definition

for

Name

RSLFLG

Block

(library

flags word):

LDSRES

2.11.9

000040

: Library has memory-resident
s

overlays

Additional Error Message

Add the following error message to the
Task Builder Manual:

RSX-11M/M-PLUS

and

Micro/RSX

Cluster library element, element-name, is not resident overlaid.

built without memory-resident
The listed cluster element has been
be used as a cluster library
not
can
element
of
kind
This
overlays.
element.

Cluster libraries 2 through 6 must be memory-resident and overlaid.

CORRECTIONS

2.12

RSX-11M-PLUS

This

section

corrects

Writing an
®

GUIDE

I/O

Data

errors

Driver.

macro

and

These
and

call

Description

US.PUB

Description

U.BUF

Status

control

block

Additional

information

Inputs

SASUMR

Incorrect

Unclear

2.12.1

Data

I/0

omissions

errors

and

DRIVER

the

RSX-11M-PLUS

omissions

are

Guide

follows:

blocks

arguments

Unit

for

control

status

DOCUMENTATION

TO WRITING

structures

GTPKTS$

byte

for

the

K.OWN

function

reference

SCBDFS

definition

Structures

and

Control

Blocks

The data structures and control blocks in the
RSX-11M-PLUS
Guide
Writing an I/0 Driver are outdated.
The corrected data structures
control blocks can be
Dump Analyzer Manual.

2.12.2
On

GTPKT$

page

4-7,

description
For

Macro

Call

Table

the

multiple

parallel

found

SCB

suc

2.12.3

Unit

4-31,

page

US.FOR

the

controllers

not

4-7,

Mounted

Description

4-33,

the

following

require

that

set,

the

Micro/RSX

information

support

unit

synchronization,

the

description

foreign

case,

US.FOR

volume

(l=yes)

Crash

operation

K.OWN must

you must

US.PUB

should

description

device

public

device.

should

not

read

follows:

the

set

specify

read:

US.PUB

US.PUB=4

and

Byte

Figure

2.12.4
page

add

by the driver code.
For this
argument in the GTPKTS macro.

Status

RSX-11M/M-PLUS

argument:

dynamically

the

Arguments

4-3,

suc

but

and

CORRECTIONS TO DOCUMENTATION

Description of U.BUF

2.12.5

page

paragraph)

the

4-36,

address

For a UNIBUS NPR device, bits 4

and

1in

(in

U.BUF

description

should read as follows:

word

the

fifth

are

memory

for a MASSBUS or 22-bit Q BUS NPR device (the
extension bits;
KS.MBC bit is set), bits 8 through 13 are the memory extension

bits.

Status Control Block

2.12.6

On page 4-38, Figure 4-9, the S.RCNT field in the Status Control Block
follows:

should read as
Number

Words

Copy

Additional Information for the K.OWN Function

2.12.7

On page 4-52, add the

following

the

description

K.OWN

the

function:

For multiple SCB controllers that support unit operation in
parallel but do not require synchronization, K.OWN must be set
dynamically by the driver code. For this case, you must specify
the suc argument in the GTPKT$ macro.

2.12.8

Inputs for SASUMR

On page 7-9, add the following

information

the

inputs

for

the

SASUMR routine:

M.BFVL (R0)=LOW ADDRESS OF TRANSFER

(FOR ODD/EVEN BYTE

DETERMINATION)

2.12.9

Incorrect Reference

On page 8-1, change the reference in the first paragraph from
to

[200,1]

[USER].

2.12.10

Unclear SCBDFS$ Definition

On page 8-13, remove the SYSDEF reference
following

line

and

add

the

comment:

:Users of this or any control block macro should never specify the
:SYSDEF argument but should allow the definition to be resolved
:from the Executive .STB file.

CORRECTIONS

2.13

This

RSX-11M/M-PLUS

section

Error
an

Logging

error

log

SEPKDF.MAC.

ESHTYC

contains

Manual.
packet

and

change

Appendix

includes

Replace

LOGGING MANUAL

the

memory,

ESHTYS"

described

information
with

under

"Type

the

following

fields

ESHTYC

the

example

RSX-11M/M-PLUS
of

the

and

the

format

system

macro

Subtype codes

information:

for

Type

and

Subtype

codes

for

and

ESHTYS

Symbols

with

names

E$Cxxx

are

type

TMS

‘myg

fields

ERROR

TO DOCUMENTATION

Symbols

with

names

ES$Sxxx

are

subtype

codes

for

codes

field

ESHTYC.

field

ESHTYS.

for

ESCCMD

='B’

ESSSTA

='B'

ESSSWI
ESSAPP
ESSBAC

Error

='B'
='B"
='B'

2
3
4

Switch
Append

Logging
File

Files

ESSSHO

Declare

='B!

Backup

File

ESSCHL

Show

='B"

Change

;

ESCERR

='R"!

;

ESSDVH

='B!
='B!
='B!
='B!
='B!

1
2

;

ESSDVS
ESSTMO
ESSUNS
ESSTMS

Error

Log

Device

Control

Device
Device
Device

ESCDVI

='B!

;

ESSDVI

='B'

;

Device

Status

Change

Limits

Errors

Device
Device

3
4
5

Log

Hard
Soft

Error
Error
Interrupt Timeout (HARD)
Unsolicited Interrupt
Interrupt Timeout (SOFT)

Information

Device

Information

ESCDCI

="'B'

;

ESSMOU

='B'!

;

Device

Device Count Reset
Block Replacement

ES$SSDMO
ESSRES

="B!

Device

Control

Device

ESSRCT

='B"’
='B'

3
4

;
;

ESCMEM

='B'

;

E SSMEM

='B'

;

ESCSYS

='B"

;

ESSPWR

='B!

;

ESCCTL

='B"'

ESSTIM
ESSCRS

;

ESSLOA

='B!
='B"
='B"

System

ESSUNL
ESSHRC
ESSMES

Device

='B!
='B"
='B'

4
5
6

ESCCPU
ESSINT

='B"'
='RB'

10
1

;
;

CPU

ESCSDE
ESSABO

='R!
='B'!

11
1l

;
;

Software

Memory

System

Information

Mount

Dismount

Detected

Memory

Control

Errors

Error

Control

Power

Message

Information

Recovery

Information

Time

Change
Crash

Driver Load
Device Driver Unload
Reconfiguration Status
Message

Detected Errors
Unexpected Interrupt
Detected
Task Abort

Events

Change

CHAPTER

RMS-11 VERSION

This chapter

describes

RSX-11M-PLUS Version 3.0.
to

new

2.0

RMS-11

RELEASE NOTES

features

and

restrictions

for

Also included are corrections and additions

RMS-11 documentation.

RMS-11 Version 2.0 has not changed version numbers for this release of
RSX-11M-PLUS.

Information

into

the

manuals.

3.1

NEW FEATURES

RMS-11

1in this chapter has not been incorporated

RMS-11 Version 2.0 includes the following new features:
@

New resident library configuration

New interface to RSX

Improved

logical

remote access

names

to RSTS/E systems

New features have also been added

to several RMS-11 utilities.

New Resident Library Configuration

3.1.1

A new high

developed

performance/low

for

the

system-overhead

RMS-1l1

resident

partitioned into three separate segments,
physically resident in memory.
This partitioning allows

Only
The

those

remainder

tasks

that

are ever

of the

can

been

of which have to

the

library segments are eligible

use the physical memory.

required

1library

segments.

1its associated

and

link

user

SDISPLAY,

the
tasks

SERASE,

"root"

against

SPARSE,

the

replacement

task.

the new configuration

file

for

Not more than two segments

simultaneously by a given user

RMSRES.TSK
to

not all

"demand-paging"”

has

The library has been

segments containing code that is in use must be resident.

The functional breakdown for
@

configuration

library.

segmented

is as

follows:

library.

The

.TSK

.STB file are the only files needed
RMS-11.

S$SEARCH,

internal

EXTEND

function,

SOPEN and

SCLOSE operations.

all

This

SRENAME,

operations

segment

S$FREE,
for

supports

the common

sequential

files, all block I/0 record operations, all magtape functions
and some common code for relative and indexed
file
SCREATE,

RMS-11

VERSION

2.0

RELEASE

NOTES

RMSLBL.TSK is the library segment
that
supports
operations
for
Relative
files,
SEXTEND,
Indexed
file SOPEN, SCLOSE,
SCONNECT, SDISCONNECT, SFIND and SGET operations.
RMSLBM.TSK is the library segment that supports all remaining
Indexed
file operations; SDELETE, SPUT, SUPDATE, data record
insertion and index update for SPUT and
SUPDATE
operations,

bucket

allocation routine and

indexed

S$CREATE operation.

NOTE

All

library segments do

resident;

only

the

not
root

need

needs

physically

installed.
satellite that has
return ERSENV.
To
installing
all

However, if an operation requires a
not
been
installed,
RMS-11
will
avoid
complications
we
recommend
segments.

Comparisons
library:

with

old

configuration

the

RMS-11

segmented

resident

The minimum amount of physical memory
required
to
use the
RMS-11
resident
1library
1is
approximately
22Kb instead of
16Kb.
However, 1if relative or indexed
file
operations
are
required,
then
the
minimum
size
has
increased
to
approximately 36Kb instead of 16Kb.
The
o0ld
configuration
was
optimized
for
impact
on
memory.
It
has since been
determined that impact on system pool usage was a significant
problem.
Consequently
the
new
configuration
attempts to
compromise both of these needs.

The old

library

consisted

the

root

(RMSRES)

and

six

satellites (RMSLBA...RMSLBF), each of approximately 8Kb.
The
new library consists
of
a
root
(RMSRES
of
approximately
22Kb),
and two satellites:
RMSLBL of approximately 8Kb, and

RMSLBM of approximately 14Kb.
the

o01ld

RMSRES,

RMSLBA,

and

contains the old RMSLBC and
contains

the

old

RMSLBE

The new library root
RMSLBB.

RMSLBD.

and

The

RMSLBF.

RMSLBL

RMSLBM

combines

satellite

If most of your RMS-11 applications use only sequential
operations

there

will

need

for

the

system

file

load

any

satellites.
Consequently, the overhead
caused
by
swapping
between
satellites
1is eliminated.
1If your applications use
relative or indexed files, a similar effect occurs.
Once the
appropriate satellite has been loaded, all of the support for
that

operation

in memory.

The impact on system
following changes:

pool

usage

reduced

instead

result

Two

satellites

are

The

satellites

are only attached

Three partitions are installed instead of seven.

The new library
allow
existing

attached

the

six.

they are required.

root is still LB:[3,54]RMSRES.TSK.
This will
TKB
command
files
to work as before.
All
tasks
built
against
the
old
resident
library
will
transparently
use
the
new library.
Incompatible roots and
satellites will still result in the error ERSLIB.

RMS-11 VERSION 2.0 RELEASE NOTES
%

3.1.2

New Interface To RSX Logical Names

On systems with the new logical name support,

RMS-11

appropriate

operations,
the
user-provided file specification is sent to a system
parse routine that translates any
1logical
names
that
are
present.
This
support
1is available in the RMS-11 utilities and in any layered

applications for the current release of RMS-11.

mode,

the logical

name

is not parsed until

When in remote access

it reaches the remote node.

See the following RSX-11M-PLUS Version 3.0 manuals for information

names:

new RSX logical

RSX-11M/M-PLUS MCR Operations Manual

RSX-11M-PLUS Command Language Manual

RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual

Remote Access to RSTS/E Systems

3.1.3

RMSDAP supports remote access to indexed files on RSTS/E systems.
B

Appendix

information

the

remote

RSX-11M/M-PLUS

User's

RMS-11

Guide

for

See

access.

New Utilities Features

3.1.4

This section describes the new enhancements to

the

following

The

purpose

RMS-11

utilities:
®

RMSCNV

RMSBCK

RMSDSP

RMSRST

The RMSCNV utility supports a new /ER switch.

switch

RMSCNV

allow

encountering an exception record.

continue

processing

The new switch uses

this

file after

the

following

format:

/ER:filename

If no /ER switch is used,

first exception record.

type of exception

record.

RMSCNV will terminate after encountering the

It will issue an error message indicating the

If the /ER:filename switch is used, RMSCNV will
continue processing
If exception records are encountered, the exception records
the file.

will be placed

the

specified

file.

RMS-11

3.1.4.2
The

RMSBCK,

RMSDSP,

VERSION

and

2.0

RMSRST

RELEASE

NOTES

utilities

increase
performance
and
decrease
task
process file
specifications
that
include

1include

size.
the

enhancements

These utilities now
wildcard
characters

asterisk
(*)
and percent sign (%).
These wildcard characters can be
used in any position within the directory, file name, file
type,
and

file

version

number

added

utilities:

these

fields.

The

RMSBCK New Switches

new

switches

Disables

/NV

Creates

been

query mode
a

new version

Interprets

the

creation date

output

file

after (:A) the specified date,
creation/revision date format

/CD:date:B

have

Function

/NOQU

/CD:date:A

following

normal

Interprets the creation date as
before (:B) the specified date,
creation/revision date format

/RD:date:A

normal

Interprets
after (:A)

the revision date as
the specified date, in normal
creation/revision date format

/RD:date:B

Interprets

the

revision date

before (:B)
the specified date
creation/revision date format

normal

RMSDSP New Switches
/BR

Briefly displays attributes

/SU

Supersedes

RMSRST New

output

file

Switches

/NOCV

Disables

/NV

Creates

3.2

SOFTWARE

This

section describes

version

radix

conversion

new version of output

file

restrictions

RESTRICTIONS

software

problems
that
apply
to
RMS-11
preventing or correcting problems

3.2.1

existing

well

other

known

Version 2.0.
Suggested measures
are also included.

for

RMS-11 Access Methods

RMS-11

record
is

not

allows
usable.

unusable

the

creation

size that exceeds
file.

You

indexed

file

its bucket size.

should,

therefore,

with

However,

avoid

maximum

the

creating

file
an

RMS-11 VERSION 2.0 RELEASE NOTES

This

the target record ends on the block boundary.

file

fixed

sequential

Locate mode does not work when accessing a

To avoid it, do not use a fixed

problem impairs performance.

record size that allows records to fit perfectly in a block.

Default Extension Quantity

When

files.

sequential

Multiblock Count

size

does not work correctly

instead

the

for

it uses the

pack

default.

DEQ value instead of 0.
Consult
your
programming
documentation for implementation details.

language

problem

this

‘Until

(MBC)

(DEQ)

RMS-11 extends a file,

1is fixed you should specify an explicit

Current RMS-11 tasks will return the error message "Directory

(ERSDNF)

Not

Found"

DEF

.
/NONAMED)

certain

operations that are

file

executed from an account set to nonamed directory

(SET

mode

This will occur if the following conditions

are

true:

The tasks were.not

resident

RMS-11

the

against

built

library.

file

the
either
in
provided
not
1is
A directory
specification or the default file specification.

the
1in
directory
To work around this, you should provide a
or set your terminal to named directory
specification,
file
mode (SET DEF /NAMED).
If that is not possible, you
should
‘rebuild those tasks using the new version of RMS-11l.
Assigning one device to another by using

1logical

names

may

application performs a
an
If
results.
undesirable
cause
SPARSE operation on a string, which
results
in
a
terminal
device (for example DMO:), and there is another entry in the
user,

group,

reassigned

system

DM1l:,

then

logical

table

for

DMO:

Dbe

a subsequent SOPEN operation

RMS-11 will try to access DM1l:,
not
DMO:.
To
avoid
this
not use actual device names as logical names on
do
problem,
your

system.
NOTE

In the next major release of RMS-11,

may

be
possible
to receive an underscore in the
above
the
correct
will
This
device name.
problem.
Consequently, it will be necessary
for applications to consider this if they use
the

file

specification returned

form names for work files

by RMS-11 to

(since files cannot

have names with an underscore

them).

The following restrictions apply to RMS-11 utilities for Version

2.0.

RMSDES

RMSDEF is

still

available

try using

RMSDEF.

RMSDEF,

you

for

RSX-11M-PLUS

Version

3.0,

command

DEF,

however, the following information should be noted before you

which

defines

Version

3.0

1logical names.

need

LB:[1,2]STARTUP.CMD

LB:[3,54
] RMSDEF/TASK=...DFN
3-5

has a

type
to

new

DCL

Consequently, when you invoke
MCR

DEF,

read

modify

INSTALL

(or a filename of your choice).

RMS-11 VERSION 2.0 RELEASE NOTES
®

Using default areas - when the record size
is
greater
than
1024
Dbytes,
RMSDES
selects
area bucket sizes that are not
large
enough.
In
this
case,
the
file
1is
successfully
created,
but
1is
unusable.
To
work
around this problem,

override
creating
@

Using

the
the

bucket
file.

size

default

areas than
can

duplicates

can

Guide,

calculation),

area

RMSDES

SET

Selecting

for

the

returns

packed

reduced

decimal

length of
an

error

this

and

key

Key

RMSDES

uses

the

system

file
DAT
command.
login device is not
your

default

device

set

never

Create

the

segment

default

prompts

operation

for

File."

length,

device

This default may be inconvenient if
the system device, or
if
you
have

device

issuing the DCL SET
this,
you
should
specification.

other

than

the

of
allocate more

Specified

the

can

number

will

RMSDES

of
the

RMSDES

These

the

subsequent

Field

Therefore, you must explicitly
select a packed decimal key.
®

RMSDES

field

field.

"Invalid

for

allocations.

commands,

conservatively.

before

User's

than

value

necessary

RMS-11

overridden

correct

a
larger
number
(see Chapter 6 of

sets

larger

when
fit

the

there
is
in a bucket

RSX-11M/M-PLUS
up

with

you

GET

your
set

system device by

DEF or MCR ASN commands.
To work
around
supply
the
device
name
in
the
file

RMSIFL

than

aborts

one

/DE switch
problem is

RMSIFL

with

file

is
to

uses

key,

For

alternate

sort

does

can

RMSCNV and

1is
use

management

the

algorithm

not

violation

same

that,

preserve

keys,

problem
by using
duplicates in the

file

memory

RMSIFL

it
1is
RMSCNV.

the

when

FIFO

called

ordering

necessary
If the only

RMSIFL

/NOSO.

around

this

upon

and

the

sort

duplicates.

to
work
around
this
concern is ordering of

primary key, then as
1long
indexed file or a file sorted on

when

session

used.
A temporary means of working
invoke RMSIFL for each file.

processed

as
your
input
primary key, you

RMSIFL

RMSCNV

and

quantities
large

RMSIFL

when

enough

ignore

reduce

the

user

file.
number

provided

The
of

values
file

area

extension

that

they use are
extensions in
most

cases.

3.3

CORRECTIONS

PROBLEMS WITH

THE

This section describes corrections to software
the previous release of RMS-11 Version 2.0.

RELEASE

problems

relating

RMS-11 VERSION 2.0 RELEASE NOTES

RMS-11 Access Methods

3.3.1

The following corrections apply to RMS-11 access methods:

value
key
Records loaded into an indexed file by descending
found when either random access or sequential
all
not
were
access was used.

This problem has been corrected.

corrupted
sometimes
The first word of a block in a file was
with
a
-1
when
an
SUPDATE
operation
was performed on a
SUPDATE
or- an
This occurred when a S$FIND
sequential file.

a S$GET operation on the last record in a
followed
operation
one
block, if that record ended at the end-of-file or within
The -1 appeared in the first word of
end-of-file.
of
byte
the block.

In some cases there were problems with Update
operations
to
an
indexed
variable
file
containing
alternate
keys when
In
operations.
SUPDATE
record sizes were increased during
the new record no longer fit in the old bucket,
where
cases
RRV
the record was written to a new bucket with an incorrect
pointer.
Later
attempts
to
get
that record by using the
If you have
alternate key would return the ERSRRV condition.

experienced
RMSIFL

This problem has been corrected.

this

problem,

in order to fix

reload

your

indexed files with

the alternate key tree(s).

A problem with the single-precision multiply routine
in
the
access
methods
has
been corrected.
When calculations were
performed that would produce a value larger

incorrect value resulted.

than

131073,

This value transferred the bits in

the high word of the two-word value to
the
1low
word.
For
example,
1in.a relative file with 3 block buckets, an attempt

to insert relative record 43692 by issuing a $PUT
operation,
writing the record to block 3 rather than block
in
resulted
131076.
This
problem
affected
random
SPUT
and
SGET
For
operations in relative files and fixed sequential files.
relative files, the multiplication
of
the
relative
record
number
by
the
bucket size in blocks would be invalid.
For
sequential fixed files, the multiplication
of
the
relative
record
number
by the record size in bytes would be invalid.
This problem has been
corrected.
You
should
reload
your
files if your applications were affected by this problem.

The following corrections apply to RMS-11 utilities:
RMSCNV

A problem with the /EO switch in RMSCNV has been fixed.

This

switch
enables
the
conversion
of
the
ASCII
CTRL-Z
EOF
terminator to a null, and pads the
rest
of
the
file
with
nulls.
This problem has been corrected.

RMSIFL

Using the /DE switch allows the five RMSIFL sort files to
be
redirected
to
alternate devices rather than the device used
in the input
file
specification.
This
switch
failed
in
several
ways.
RMSIFL
reported’ either
"Failure to Create
IFLA.TMP (ERSCRE)" or "Extraneous Data in File
Specification
(ERSXTR)"
In
some cases, it sent data output to the console
device.

This problem has been corrected.

RMS-11 VERSION

Using

RMSIFL with

would

2.0

RELEASE

NOTES

indirect command

file

(IFL

@file.cmd)

return

the message "?0utput file must be empty" on any
commands following the first command.
This
would
abort
a
batch submission.
This problem has been corrected.

The

RMSIFL

utility

attempted

This

problem

was

process

has been

not
a

functioning

file

with

the

properly

when

/ER:filename

corrected.

switch.

RMSIFL

was failing to display the
correct
exception
record
type in the exception record file if the exception record was
detected
on
the
alternate
key.
This
problem
has
been
corrected.
RMSIFL

was

returning

incorrect

output

record

count

and

exception
record
exception detected
to be displayed as

count
after
processing
a
file.
Any
in the alternate key caused
these
counts
"?2??2?".
This problem has been corrected.

RMSIFL

displayed

exception
Exceptions
problem
problem

There
not

were

alternate

primary

detected

keys,

need

new

the
to

form

This

when

This
RMSIFL

corrects

the

was

and

form of
is

value

the

primary

worked

switch

IFLNON.CMD

PAR statement.

be modified

modules.

key

however,

only occurred when no /ER
has been corrected.

includes
new

incorrect

records

when

Kkey.

fine.
specified.

This

IFLNRN.CMD

that

command

rebuilt

The

file does

problem

incorporate
of needing

PACKED

DECIMAL

alternate

to
modify
command
files.
See
the
RSX-11M/M-PLUS
and
Micro/RSX
Task
Builder Manual
for
further information
on
tailoring the command file to reduce the size of RMSIFL.

RMSIFL did
keys.
It
alternate

not

correctly

handle

rejected
these
as
key
1loading
phase.

exception records during the
This
problem
has
been

corrected.

RMSIFL
a

did

not

corrupted

incorrectly.

return correct exit status when
index.
This
caused
batch

This problem

it encountered
jobs
to
run

has been corrected.

RMSIFL that is built
to
wuse
supervisor
mode
RMSRES
was
aborting with a memory protection violation in certain cases.
This problem has been corrected.
RMSRST

The

/SE

switch

container.
because of
has

been

is used to selectively restore
files
from
a
RMSRST
did
not always find the files specified
an incorrect order-based algorithm.
This
problem

corrected.

when an explicit file specification was given
switch,
through

The

use

would

This

RMSRST
found
the tape.
This

of a
not

wildcard

restore

the

problem has been

with

the

/SE

the
file
but
continued "searching"
problem has been corrected.

directory
file(s)

to
corrected.

the
the

output
original

specification
owner

account.

RMS-11 VERSION

2.0

RELEASE

NOTES

being

revised

DOCUMENTATION CORRECTIONS

3.4
The

RMS-11

This

Version

section

2.0 manuals

describes

appropriate

sections

information

are

not

documentation
the

added

manuals

the

for

this

release.

errors and directs you
to

make

manuals

1is

corrections.

also

included

the

New

this

the

section.

3.4.1

RSX-11M/M-PLUS

RMS-11 User's Guide

In Section 2.2.3.3,
please
discussion of deadlock:
An

application

add

should

the

use

following

information

multistream

rather

than

multi-channel
access
to
write
to
the same indexed file.
When RMS-11 updates an RRV in a
bucket
that
is
currently
locked,
it must wait for that lock to be released.
Control
will not be returned
to
the
program
until
this
release
occurs.
Deadlock
will
occur
when
the
1lock
1is held on
another

update
within

channel

an
the

within

RRV
same

the

same

in a bucket
program.

documentation

for

program;

however,

RMS-11

can

that is locked on another stream
See
your
programming
language

details

the

implementation

multistreaming.

Section

following
In

6.2.4,

the

discussion

writing
a record,

please

add

the

note:

the

event

key
but
alternate

that

1is
key

RMS-11 will

the

record

treat

the

present
in the record,
index structure.

alternate
making no

Section 6.3, the discussion
following information:
You

will
obtain
contiguous
on
a
there

includes

partial

alternate

not large enough to include space for
field, RMS-11 will act as follows:

means

key
entry

as
in

contiguity and

the

full

the

alternate

areas,

were

not
key

please

add

the

small
benefit
by
setting
areas
to
noncontiguous
multi-area
file, however,

for

RMS-11

determine

those

areas

remain
contiguous.
Consequently,
RMSDSP
and RMSDES will
display them as noncontiguous.
As long
as
the
areas
are
preallocated,
they
will
behave
1like contiguous areas; as
soon as

they

contiguous
In

Section

resident

option

8.1.2.1,

1library,

need

the

to be

extended,

they will

not behave

1like

areas.

Task

the discussion

incorrect

Builder

task building

syntax

command

1is

file.

against

documented

The

correct

for

the

RMS-11

the cluster

syntax

1is

follows:
CLSTR

RMSRES,DAPRES:RO

In Appendix B,
DECnet,

the

remote record

the discussion of remote

documentation

access

states

indexed

that

files.

file and
the

record

access

RSTS/E FAL does

This

longer

not

true.

using
support

RMS-11

3.4.2

RSX-11lM/M-PLUS

Section

2.3,

Section

the

last

2.0

Macro

argument

correct

5.19,

FID field
"If this

RMS-11

the

incorrect.,
The
Section 2.3.4.

VERSION

RELEASE

NOTES

Programmer's

for

PSBUF

argument

paragraph

Guide

"bufcount".

"iopoolsize",

incorrectly describes

in the NAM block.
It
value is non-zero..."

should

read

This

1is

as discussed

the

as follows:

use

too

In Appendix A, page A-8, please add the following sentence:
ERSKEY may also
small

Also

be caused

contain

the

whole

Appendix

please

ERSBEQ

Bad

Logical

(Octal:

ERSFTB

File

attempt

add

following

the

equivalence

specification

176364,

became

logical

name

174550,

Decimal:

Utilities

discussion

3.3.2

record

codes

Record

read

contains

The following table describes
distribution kit.

big

due

logical

name

exception

records,

modify

the

follows:

duplicate

PLACEMENT ON THE

conditions:

-1688)

This change indicates a duplicate
fields when no-duplicates
was

FILES AND

error

translations

key

3.5

that

-=780)

(Octal:

Section

002:

too

Too many

record

-184)

Decimal:

RMS-11

field.

string

Decimal:

RSX-11M/M-PLUS

the

insert

key

3.4.3

exception

primary

177510,

(Octal:

ERSTRN

by an

key

where

either

the

not

allowed

primary

alternate

specified.

DISTRIBUTION KIT

the

contents of

the

RMS-11
“

Version

2.0

NOTE

Some

file

names

indicates

that

are marked
the

RC25

distribution

space

reasons

used

rebuild

files

kits.

the

Destination

RMSMAC.MLB

LB:[1,1]

They

are

excluded

because

kit,

and

because

RMS-11

RMSDAP.OLB

they

Version

RL02
are

and
of
only

2.0.

Comments
Can

This

included

deleted

MACRO-11

RMSLIB.OLB

asterisk.

not

components

File Name

with
are

Object

RMS-11

you

are

not

using

library

programs.
for RMS-11

local

library

for

remote

access.

LB:[1,1]

Object

RMS-11

access.

Can

be deleted

remote

RMSBCK. TSK

LB: [3,54]

you

not

need

access.

RMSBCK utility;

uses

(continued

RMSRES.
on next

page)

RMS-11 VERSION

File Name

Destination

RMSRST.TSK

LB:[3,54]

RMSDEF.TSK
RMSDSP. TSK

LB: [3,54]
LB:[3,54]

RMSCNV.TSK

LB: [3,54]
LB:[3,54]
LB: [3,54]
LB:[1,
2]
LB:[1,1]
LB:[1,1]

RMSDES.TSK

RMSIFL.TSK
RMSDES. IDX

RMS11.0DL

RORMS1.MAC

RMS12X.ODL

LB:[1,1]
LB:[1,1]
LB:[1,1]
LB:[1,1]

RMSRLX.ODL
DAP11X.ODL

LB:[1,1]
LB:[1,1]

DAPRLX.ODL

LB:[1,1]
LB:[1,1]

RMS11S.0DL
RMS12S.0ODL

RMS11X.0ODL

RMSRES.TSK

2.0

RELEASE NOTES

Comments

RMSRST
RMSDEF
RMSDSP
RMSCNV
RMSDES

utility;
utility;
utility;
utility;
utility;

LB:[1,1]

RMSLBM. TSK

RMSRES.STB

LB:[1,1]
LB:[1,1]

DAPRES.TSK

LB:[1,1]

DAPRES.STB

LB:[1,1]

RMSLBL.MAP*

LB:[1,34]
LB:[1,34)]

RMSLBM.MAP*
RMSRES.TSK

LB:[1,34]
LB:[3,54]

RMSRES.STB

LB: [3,54]

RMSRES.MAP*

LB: [3,54]

RMSFAK.CMD*
RMSROT.STB*

LB:[1,24]

RMSROT.CMD*
RMSZAP.CMD*

LB:[1,24]

RMSLBL.CMD*

LB:[1,24]

RMSLBL.ODL*
RMSLBM.CMD*

LB:[1,24]
LB:[1,24]
LB:[1,24]
LB:[1,24]
LB:[1,24]
LB:[1,24]

DAPRES.MAP*

RMSRES.
RMSRES.
RMSRES.
RMSRES.
RMSRES.

RMSIFL utility; uses RMSRES.
Indexed help file used by RMSDES.
Prototype ODL file.

For

use

with

ODL file
ODL file
Standard

the

prototype

non-supervisor mode library.
Task image for RMSRES segment.
Task image for RMSRES segment.
STB file for RMSRES.
Task image for RMSDAP resident
library.
STB file for DAPRES.
Maps

for

segmented

library.

Task image for linking in
supervisor mode. Also installed
as the root of the library
(supervisor mode and non-supervisor
mode) .

STB file
mode

RMSLBM.ODL*
DAPRES.CMD*

DAPRES.ODL*
BCKNON.CMD*

LB:[1,24)]

BCKNSN.ODL*
CNVNON.CMD*

LB:[1,24]

BCKNRN.ODL*
BCKNSN.CMD*'

linking supervisor

tasks.

LB:[1,24]

LB:[1,24]
LB:[1,24]
LB:[1,24]
LB:[1,24]
LB:[1,24]

BCKNRN.CMD*

for

Map file for supervisor mode
library.
For rebuilding RMSRES.

For

rebuilding

RMSLBL.

For

rebuilding

RMSLBM.

For

rebuilding

DAPRES.

rebuilding

the

For
of

BCKNON.ODL*

ODL.

for sequential.
for sequential.
indexed file ODL.

Indexed file ODL.
ODL for use with RMSRES.
ODL for use with overlaid RMSDAP.
ODL for use with DAPRES.
TSK image for linking against
RMSRES,

RMSLBL.TSK

uses
uses
uses
uses
uses

CNVNON.ODL¥*

LB:[1,24]

CNVNRN.CMD*

LB:[1,24]

CNVNRN.ODL¥*

LB:[1,24]

overlaid

version

RMSBCK.

For rebuilding the resident
library version of RMSBCK.
For rebuilding the supervisor
mode version of RMSBCK.
For rebuilding the overlaid
version of RMSCNV.
For rebuilding the resident
library version of RMSCNV.
(continued

3-11

on next

page)

RMS~-11

File

Name

VERSION

2.0

RELEASE

Destination

NOTES

Comments

CNVNOO.CMD*

B:[1,24]

CNVNOO.ODL*

LB:[1,24]

CNVNRR.CMD*

rebuilding the overlaid
version of RMSCNV with RMSDAP.

CNVNRR.ODL¥*

LB:[1,24]
LB:[1,24)]

For rebuilding the
library version of

CNVNSN.CMD*

LB:[1,24)]

For

rebuilding

CNVNSN. ODL*

B:[1,24]

mode

version

For

resident
RMSCNV with

RMSDAP.

DEFNON.CMD*

LB:[1,24)]

DEFNON. ODL*

LB:[1,24]

DEFNRN.CMD*

LB:[1,24]
B:[1,24]

the

supervisor

of RMSCNV.
rebuilding the overlaid

DESNRN.CMD*

LB:[1,24]

For
version of RMSDEF.
For rebuilding the resident
library version of RMSDEF.
For rebuilding the supervisor
mode version of RMSDEF.
For rebuilding the overlaid
version of RMSDES.
For rebuilding the resident

DESNRODL
N.
*

LB:[1,24]

library

RMSDES.ODL*

DESNSN.CMD*

LB:[1,24]
B:[1,24]

For

rebuilding

DESNSN.ODL*

LB:[1,24)]

mode

DSPNON.CMD*

version

LB:[1,24]

DSPNON.ODL*

For

LB:[1,24]

version of

DSPNRN.CMD*

LB:[1,24]

DSPNRN.ODL*

LB:[1,24]

DSPNSN.CMD*

LB:[1,24]

DSPNSN.ODL*

For rebuilding the
library version of
For rebuilding the

LB:[1,24]

IFLNON.CMD*

LB:[1,24]

DEFNRN. ODL*

DEFNSN.CMD*

LB:[1,24]

DEFNSN. ODL*

LB:[1,24]

DESNON.CMD*

LB:[1,24]
LB:[1,24]

DESNON. ODL*

IFLNON.ODL*

LB:[1,24]

IFLNRN.CMD*

LB:[1,24]

IFLNRN.ODL*

LB: [1,24]

IFLNSN.CMD*

B:[1,24]

IFLNSN.ODL*

LB:[1,24)]

RSTNON.CMD*

LB:[1,24]
LB:[1,24]

RSTNON.ODL*
RSTNRN.CMD*

version

the

supervisor

of RMSDES.
rebuilding the overlaid

RMSDSP.
resident
RMSDSP.

supervisor
mode version of RMSDSP.
For rebuilding the overlaid
version of RMSIFL.
For rebuilding the resident
library version of RMSIFL.
For rebuilding the supervisor

mode

version of RMSIFL.
For rebuilding the overlaid
version of RMSRST.

RSTNSN.CMD*

LB:[1,24]
LB:[1,24]
LB:[1,24]

RSTNSN.ODL*

rebuilding the
library version of
For rebuilding the

LB:[1,24]

mode

RSTNRN.ODL*

RMSDES.

For

version

resident
RMSRST.

supervisor

RMSRST.

For rebuilding several ut111t1es

RMSUTL. OLB*

LB:[1,24]

RMSODL. ODL*

LB:[1,24]

GSA.MAC

LB:[200,1]

Demonstration

included

how

RMS-11

pool

program
illustration of
task

the

PARSE.MAC

LB: [200,1]

Demonstration

programs

LB:[200,1]

new directory
facilities.

and

LB: [200,1]

ERASE.MAC

LB:[200,1]

PARSE.TSK

LB:[200,1]

SEARCH. TSK

LB:[200,1]

RENAME. TSK

LB: [200,1]

ERASE.TSK

LB:[200,1]

event

for

RMSDAP

RMS-11

files
access

can

files

deleted
on

remote

you

nodes.

are

the

wildcarding

NOTE

All

extend

exhaustion.

SEARCH.MAC
RENAME.MAC

not

wusing

~~~~~~~

RMS-11 VERSION

2.0 RELEASE

RMS-11 VERSION 2.0 INSTALLATION

3.6

On RSX-11M-PLUS systems, all RMS-11
system after system generation.

3.6.1

NOTES

Startup Command

install

RMS-11,

system

items:

the resident libraries and

RLO2 and

library

RC25 pregenerated

(RMSRES,

RMSLBL,

are already installed

the

only

RMS-1l1 utilities

installation

the

RMS-11

segmented

and all the RMS-11 utilities

system

that

the file

Please note the following

systems,

RMSLBM)

installation of the DAPRES

DECnet

your

sample comments that can

become system startup commands.

To aid you in the installation process,

LB:[1,2]STARTUP.CMD contains commands and

edited

automatically

Procedures

install

startup.

files are

1is

resident

image.

For

library

needed

1is

these

the

kits,

optional

system has

support and if RMS-11 remote access facilities are to

used.

On systems

other

than

RL02

and

RC25,

the

startup

file

contains commands that install the segmented resident library
in the system image.
Note that
these
are commands,
not
want to install the library, you
not
if you do
comments;
should edit the file to make
note the following items:

these commands comments.

All resident libraries
option /RON=YES.

The root of the library, RMSRES, must be the
task
image
contained in [3,54].
The [1,1]RMSRES.TSK should never be
installed

the

should

system;

installed

Please

is only used

using

when

tasks

the

are

linked to use the non-supervisor mode version of RMSRES.
-

PFailure to install the root segment RMSRES will cause the
error
"INS
-Common
block
not Loaded RMSRES" when a
referencing task
or
utility
1is
invoked.
Failure
to
install
any
of
the remaining resident library segments
will not give an error at invocation.
However,
it
may
cause
the
error
codes
ERSLIB or ERSENV, or a BPT trap

(with RO containing ERSLIB), when the missing segment

needed by

RMS-11.

1is

There are several circumstances
involving
"inconsistent
or
incomplete
resident
1libraries" that can cause a BPT
trap to be generated with RO containing

ERSLIB.

This

library are

can

the

error

code

of the
occur if not all the segments

installed

the version numbers of one or

more
segments
do not match the root segment,
the RMSDAP
code, or the task itself.
1In particular, this can happen
to
the
RMS-11
utilities
if
they are built to use the
segmented resident
incorrectly.

library and

the

segments are

installed

RMS-11 VERSION

The

resident

2.0

RELEASE

libraries

have

NOTES

been

built

with

the

PAR=parname option in the TKB command file, where parname
is the name of the resident library.
This
feature
was
included
for
compatibility
with
RSX-11M systems.
You
should
install
the
resident
1libraries
1in
the
GEN
partition.
Do not generate individual partitions for the
libraries on RSX-11M-PLUS; doing so would negate much
of
the benefit of having a "demand-paged" segmented library.

you

are

using

RMSRES

different

install

supervisor

task.

You

mode,

you

simply

need

not

need

link

your

task.

you

want

wuse

the

RMS-11

utilities

the

RMSDAP

resident
1library (RMSDAP), you must edit the startup command
file, which contains template commands
(comments)
that
you
can edit to install these facilities.

3.6.2
The

Utility Configurations

RMS-11
to

built

RMSLBL

and

utilities that are
wuse
the segmented
RMSLBM should

provided on
the
resident library.

installed

before

you

distribution
kit
are
Consequently, RMSRES,
use

any

the

RMS-11

utilities.

3.6.2.1

Utility Command

and ODL Files -

For each utility, a command and ODL file is provided
to
build
the
utility
wusing disk-overlaid RMS-11.
files are the following:
For

RMSBCK:

For

RMSRST:

RSTNON.CMD, RSTNON.ODL, RMSODL.ODL

For

RMSCNV:

CNVNON.CMD,CNVNON.ODL

that can be
used
The names of the

BCKNON.CMD,BCKNON.ODL,RMSODL.ODL

For

RMSDSP:

DSPNON.CMD,DSPNON.ODL,RMSODL.ODL

For

RMSDES:

DESNON.CMD,DESNON.ODL,RMSDES.ODL

For

RMSDEF:

DEFNON.CMD,DEFNON.ODL,RMSODL.ODL

For

RMSIFL:

IFLNON.CMD, IFLNON.ODL

NOTE

These

RLO2

command

and

RC25

and

ODL

files

are

not

supplied

with

the

kits.

For

each utility, a command and ODL file is provided that can be
to
build
the utility using the supervisor mode library, RMSRES.
names of the files are as follows:
For

RMSBCK:

BCKNSN.CMD,BCKNSN.ODL

For RMSRST:

RSTNSN.CMD,RSTNSN.ODL

For

RMSCNV:

CNVNSN.CMD,CNVNSN.ODL

For RMSDSP:

DSPNSN.CMD,DSPNSN.ODL

For

RMSDES:

DESNSN.CMD,DESNSN.ODL

For

RMSDEF:

DEFNSN.CMD,DEFNSN.ODL

For

RMSIFL:

IFLNSN.CMD,IFLNSN.ODL

3-14

used

The

RMS-11 VERSION 2.0 RELEASE NOTES

Rebuilding the Utilities -

3.6.2.2

To rebuild the utilities,

follow these steps:

Set your default account to [1,24] on the system disk.

Use TKB to build the utility or utilities.

The utilities and the corresponding map files will be built in the
You may then want to put the utility in the system
current account.
([3,54]).

account

Each command file for a particular utility creates a

utility

the

CNVNRN.CMD and CNVNON.CMD both produce
One 1is built to wuse the resident

For example,
correct name.
task images called RMSCNV.TSK.

library and one is built with disk-overlaid RMS-1l1.

3.7

REPORTING PROBLEMS

Software Performance Reports (SPRs) allow you to report

problems

any

software

Appendix B of this manual includes the

directly to DIGITAL.

general procedures for filling out Software Performance Reports.

The following additional information should be submitted with SPRs for
RMS-11

software:

1Include the version number and patch level of the RMS-11l that

you are

using.

language

Include a Postmortem Dump and a map of the task involved,

Indicate whether you are

process

the

file(s)

and patch level

RMS-11

aborts

of the

(or

programming

language.

appears to be the cause).

4.,

using

and, if so, include the version number

some

Include copy(s) of the file(s)

other

task crashes and RMS-11

involved, in RMSBCK format.

Include copies of the files that can cause the error, if

the

If the problem is not reproducible,
errors are reproducible.
include a copy of the corrupt file if possible.

or interactive
Include a description of the command line(s)
session that led to the error (for RMS-11 utilities).

1Include a listing of the actual error, if possible.

APPENDIX

THE DIGITAL EQUIPMENT COMPUTER USER'S SOCIETY (DECUS)

DECUS, the DIGITAL Equipment Computer User's Society, is
one
largest and most active user groups in the computer industry.
not-for-profit association,

actively

controlled

Marlborough,
activities.

supported

members.

or used a DIGITAL computer,

interest

The

DECUS

DECUS.

by DIGITAL,

headquarters,

1located

but

1in

Membership

anyone

who

has

genuine

is free and voluntary.

GOALS

primary goals

administered

Massachusetts, administers all international policies and
Members
include individuals who have purchased, leased,

ordered,

A.l1

and

DECUS

of
the
It is a

of DECUS

are

follow:

To advance the art of computation

and exchange of

ideas and

through

information

mutual

education

To establish standards and provide channels to facilitate the

exchange

provide

To
advance
peripherals,

software

computer

programs

feedback to

customer

needs

the
effective
and
software

DIGITAL

regarding

hardware

and

use
of
DIGITAL
computers,
by
promoting the interchange of

information

further

these

goals,

DECUS

serves

its members by holding

symposia;

maintaining
a
program library; publishing an association newsletter,
technical newsletters, and books; and supporting a number
of
Special
Interest

Groups

(SIGs).

A.2 DECUS ACTIVITIES
Local, regional, and national
opportunity
to
meet
other

DECUS
organizations
give members
the
DIGITAL
customers
and
employees in an

informal setting.
From the monthly local
meetings
to
the
national
symposia,
members
can
discuss
their
ideas,
learn what others are
doing,
and
give
DIGITAL
valuable
feedback
for
future
product
development.

THE DIGITAL

Often,

the

stage
for
interesting

national

EQUIPMENT COMPUTER USER'S

meetings

the

various

SOCIETY

(DECUS)

countries

also

major new product announcements as well as
developments in both hardware and software

provide

the

a showplace
technology.

for
At

any
meeting,
members
might
describe
ideas
and programs they have
implemented, or fine-tuning that has been achieved
for
a
particular
application.
Members
present
papers,
participate
in
panel
discussions,
lead
workshops,
and
conduct
demonstrations
for
the
benefit of other members.
Many

the

technical

papers

and

presentations

from

published
as
a
book,
the
DECUS
Proceedings.
Proceedings are supplied to symposia attendees and
DECUS
members.
DECUS also publishes newsletters
interests and a society newsletter.

each

symposium

are

Copies of the DECUS
can be purchased by
focusing on special

DECUS has

a
Program
Library,
which
contains
over
1,700
software
packages
that
are
written
and submitted by users.
A wide range of
software
1is
offered,
including
languages,
editors,
numerical
functions,
wutilities,
display
routines,
games,
and other types of
application software.
Library catalogs
are
available
that
contain
program
descriptions
and
ordering
information.
The
programs are
available for a
nominal
service
charge
that
covers
the
cost
of
reproduction and media.
Many DECUS members

derive additional benefits
from
joining
a
DECUS
Special
Interest Group (SIG).
SIGs often meet as subsets of regional
and national meetings.
They may also meet on their
own,
to
discuss
their special field, such as operating systems, languages, processors,
and applications.
There are at least 25 SIGs
in
the
United
States
alone.
Many
of
the SIGs print newsletters and disseminate valuable
technical information to members.

To obtain a membership
representative

the

form

nearest

for

DECUS,

contact

DECUS

chapter

office.

DIGITAL

‘sales

APPENDIX B

REPORTING

This appendix
Per formance

with or
An

SPR

describes
Report

the

(SPR).

questions about your
can

used

SPR

for

allows

submitting

you

system directly

report

Software

any problems

DIGITAL.

errors

Software

Documentation

errors

(when

the

documentation

comment

form

appropriate)

Follow-up on a

Questions

Suggestions

An SPR cannot be

procedure
An

for:

not

PROBLEMS

used

SPR

for:

Software license and price policies

o‘ Obvious hardware problems
®

Logistical or clerical
problems
with
kits,
such
media, or failure to receive the Software Dispatch

Problems

In general,
@

with

user-written

when you complete an SPR use the

Describe only one problem per

form.

following guidelines:
facilitate

it allows the person answering

This

will

to concentrate more fully on that
particular
problem.
problem per form also helps simplify record keeping.

One

Define

and

accurately as

circumstances
@

blank

software

more rapid response because

Illustrate

the

when

possible

the

problem

with

specific

If you report a documentation error,
manual,

error

and

include

occurred.

appropriate.

state

the

system

the problem occurred.

the

Include

section

table

examples.

specify the title of the
and

page

number

figure

where

number

the

REPORTING

SPRs

are

assigned

a
priority
described as
1.

priority

of
1
receives
follows:

PROBLEMS

through

the

highest

SPR

that

priority.

assigned

Priorities

are

Most production work cannot be rfin.
- Major system functions are unusable.
-

You

Necessary peripherals

Some

cannot

boot

production

the

work

cannot be used.

cannot

Certain

functions

System

performance

Installation does

All

production

work

system.

are

not

declined.

have
be

with

intervention

©System

has

Installation has

performance

user

impact.

required.

can

run

with

significant

impact

Problem

can

Suggestions,

the

patched

type

are

bypassed.

needed

errors

through

normal

documentation.

software problem.

answer

You

receive

Suggested

Enhancement

This

SPR contains

assigned
to

this

type

SPR

report.

priority of

return

categories of SPRs:

SPR contains

priority

easily

consultations,

following

Problem/Error

This

some

excess capacity.

production work

submit

capacity.

declined.

No system
modifications
production.

run

Significant manual

user.

can

excess

All

You

run.

unusable.

has

can

You do

not

suggestion.

receive an

answer

1is

assigned

this

report.

Other
This

type

assigned
answer
to
Please supply the
where applicable)
1.

CRASH
the

SPR

contains

a
priority
this type of

question

of
5.
report.

following
information
(in
when you report a problem:
A copy of

console

the

Executive

terminal,

the

file, and the crash
please
accurately

supply

copy or

hard

user

suggestion.

Or may

source

not

output

saved-answer

1is

receive

machine-readable

task-build map,

SYSGEN

Executive STB
reproducible,
a

You may

file,

form

from
the

dump.
If
the
crash
1is
describe
the
details and
code

when

necessary.

REPORTING PROBLEMS

software options,
information,
DRIVERS - Controller/device
error log output, copy of device registers, and a sample
program.

setup
showing
output,
terminal
UTILITIES - A copy of your
file
and' relevant
before and after effects,
commands,
information.

TASK BUILDER - A copy of your terminal output command
files,
task map, and a dump of the first few blocks of the task
the
image.

from verification
Output
volume:
FILE SYSTEM - Corrupted
Error
Improper results:
the volume.
and dump of
utility
code,

file header dump,

sample program.

ERROR LOG REPORT GENERATOR (RPT) - A copy of the report

generated

RPT,

either

machine-readable media.

hard

If a failure occurs when you are running privileged,

(for

example,

DECnet),

try

reproduce

the

add-on

sometimes

1lengthy.

Therefore,

critical problem, contact your local DIGITAL office.
read the Software Dispatch for news on

software

failure without the

Then, when you write the SPR, indicate
additional software.
system operated with and without the add-on software.
The SPR process is

file

1listing or on

copy

RSX-11M-PLUS,

you

how

have

the

1In the meantime,
which

changes and problems other people have found and solved.

includes

APPENDIX C

APPLYING CORRECTIONS TO SOURCE FILES

s are made Dby
Interim changes to the Executive, MCR, and device driver
Language
Source
the
by
sed
proces
creating correction files that are
s that
module
the
of
coOpy
new
a
tes
genera
SLP
Input Program (SLP).
file on
source
the
to
tions
contain the errors by applying the correc
for
Manual
es
Utiliti
/M-PLUS
RSX-11M
the distribution kit. (See the
complete information on SLP.)

of
After you have applied the corrections and obtained a new version
s
change
Interim
file.
source
al
origin
the
delete
NOT
DO
the file,
the
having
on
depend
and
ive
that may be distributed later are cumulat
original sources available.

C.1

UPDATING AN EXECUTIVE SOURCE MODULE

To update an Executive source file (ABCDEF.MAC, for example), mount
SLP
the disk on which you performed your SYSGEN and create a (All
.
[11,40]
UFD
the
1in
COR
ABCDEF.
named
file
correction
disk on which
instructions Dbelow assume that you are working on the
, submit
[11,10]
UIC
under
g
runnin
Then,
)
you performed your SYSGEN.
For example, you could follow this
the correction file to SLP.
sequence to update REQSB.MAC:
>SET /UIC=[11,40]
>EDI REQSB.COR
[CREATING NEW FILE]
INPUT

REQSB.MAC; 2/AU/-BF=REQSB.MAC;1

*EX

[EXIT]

>SET /UIC=[11,10]
>SLP @[11,40]REQSB.COR

If the updated Executive module in

driver,

your

system

1is

not

loadable

you must:

Assemble the new module, using the
target system.

For example:

24]
>SET /UIC=[11,

RSXMC.MAC

file

for

the

>MAC REQSB,[11,34]REQSB/-SP=[1,1]EXEMC/ML,[11,10]RSXMC/PA:1,REQSB

APPLYING CORRECTIONS TO SOURCE FILES

Use

LBR

RSX11M.OLB

replace

the

target

o0ld

version

system.

For

the

module

example:

>SET /UIC=[1,24]
>LBR RSX11M/RP=[11,24]REQSB
3.

Perform

following

Building

the

Building
Creating

the
the

the modified

(ZZDRV.MAC,

the

file

for

sections of

SYSGEN:

Executive and Drivers
Privileged Tasks
System Image File

your

example),

system

the

1is

updated

1loadable

module

can

device

driver

replaced

without

rebuilding the Executive.
Assemble the updated module and replace the
resulting
object
file
in the RSX11M.OLB of your target system.
For
example, assuming that [11,10] contains the RSXMC.MAC
file
resulting
from

your

system

generation,

the

following:

>SET /UIC=[11,24]
>MAC

ZZDRV=[1,1]EXEMC/ML,[11,10]RSXMC/PA:1,ZZDRV
>SET /UIC=[1,24]
>LBR RSX11M/RP=[11,24]ZZDRV
Use

[200,200]ZZDRVBLD.CMD

ZZDRV.TSK and

ZZDRV.STB

rebuild

into

the

>ASN

SY:=00:

>TKB

@[200,200]ZZDRVBLD

the

driver.

UFD corresponding

necessary,

the

copy

system

UIC.

>SET /SYSUIC
SYSUIC=[g,m]

>SET /UIC=[g,m]
>PIP /NV=[1,54]Z2ZDRV.TSK,ZZDRV.STB

Use
the

VMR to unload
new
driver

same

locations

reload

all

as
the

the

old

1is
the

larger than the o0ld one, it may not
old one.
It may
be
necessary
to

device

loadable

driver

drivers

and

that

load

the

partition

new

one.

fit into
unload
create

If
the
and

enough

room.

> VMR
ENTER

FILENAME:

VMR> UNL
VMR>LOA

7
VMR“>

RSX11M

ZZ:
ZZ:

>RUN SSHUTUP
Hardware boot

the modified

C.2

AN MCR

UPDATING
update

Create

the

MCR

SOURCE MODULE

source

SLP correction

[12,10]SETOV.MAC.

system.

file

Assemble

SETOV.MAC,

use

the

[12,40]SETOV.COR

SETOV

for

the

target

following

and

use

system.

procedure:

update

APPLYING CORRECTIONS TO SOURCE FILES
>SET /UIC=[12,40]
>EDI

SETOV.COR

[CREATING NEW FILE]

INPUT

SETOV.MAC;2/AU/-BF=SETOV.MAC;1

*EX
[EXIT]

>SET /UIC=[12,10]

>SLP @[12,40]SETOV.COR

Assuming [11,10] contains the RSXMC.MAC file
target system generation, do the following:

resulting

from

your

>SET /UIC=[12,24]

>MAC SETOV=[1l,1]EXEMC/ML,[11,10]RSXMC/PA:1,[12,10]SETOV

All of the Task Builder command files output a map to the 1logical
device MP:. MP: must be assigned to NL: or another device to avoid a
diagnostic error message from the Task Builder.

file
If it was necessary to modify the MCR Task Builder command
it may now be
during the 1last system generation,
(MCRBLD.CMD)
necessary to repeat those changes. To rebuild the secondary portion
and replace the module SETOV, use the following
of MCR (...MCR)
procedure:

>SET

>LBR
>PIP

/UIC=[1,24]

MCR/RP/NOEP=[12,24]SETOV
SETOV.OBJ;*/DE

>ASN

SY:=MP:

>ASN

SY:=IN:

>TKB

@MCRBLD

>VMR

ENTER FILENAME:

VMR>REM

...MCR

VMR>INS

MCR

"Z
VMR>

RSX11M

To rebuild the MCR dispatcher

(MCR...)

use the following procedure:
>SET

>LBR
>PIP

/UIC=[1,24]

MCR/RP/NOEP=[12,24]MCRDIS
MCRDIS.OBJ;*/DE

>ASN

SY:=MP:

>ASN

SY:=IN:

>TKB

@MCDBLD

>SET
/SYSUIC
SYSUIC=[g,m]
>SET /UIC=[g,m]
>PIP /NV=[1,54]MCD.TSK
>VMR

ENTER

FILENAME:

VMR>REM

RSX11M

MCR...

VMR>INS MCD/XHR=NO
VMR>"Z
>RUN SSHUTUP

and replace the module

MCRDIS,

APPLYING CORRECTIONS TO SOURCE FILES

There

is only one procedure

for

replacing

involves the following steps:
l.

Create

the

SLP file,

Incorporate

the

apply

updated

it,

external

and create

module

MCR

task.

the object

into

the

task's

the

system,

using

file,

object

library.

Rebuild

VMR.

the task and

Before

disk

containing

using
the

install

target

the

to the

system.

The following example replaces the module INSLB of
task

MCR

VMR, you must assign SY: and LB:

external

MCR

Install:

>SET /UIC=[1,24]

INS/RP=[12,24]INSLB

>LBR

it was necessary to modify the external

file

time

during

the

repeat

last system generation,

those

changes:

task's Task Builder command

it may be necessary at this

/UIC=[1,24]

>SET

SY:=MP:

>ASN

>TKB Q@INSBLD
>SET /SYSUIC
SYSUIC=[g,m]
>SET /UIC=[g,m]
>PIP /NV=[1,54]INS.TSK
>VMR
ENTER FILENAME:
VMR>REM ...INS
VMR>INS INS

RSX11lM

"Z
VMR>
>RUN

S$SHUTUP

Hardware boot

the

C.3

UPDATING

The procedure

libraries:

and

DCLO.OLB

COMMAND,

has

system.

DCL

SOURCE MODULE

is different

for modules

sure

not

library,

instance,

in UFD

whether

use LBR to scan the

the DCL task.

There are

two DCL object

DCL's

overlay

segments.

(One

[1,24]

of your distribution kit.

module,

versions in both the root and overlay libraries.)

libraries are located

are

for

DCLR.OLB for modules in the root segment of the DCL task,

view

module

1If

These

you

belongs in the root or the overlay
names

the

1libraries.

For

the module names in DCLO.OLB, enter the following

command
MCR:

LBR

[1,24]DCLO/LI

DCL:

LIBRARY/LIST

[1,24]DCLO

The modules you are most likely to need

tables

which

segments.)

are in DCLO.OLB.

See Chapter

to modify are the

DCL

syntax

(All DCL syntax tables are in overlay

the RSX-11M/M-PLUS

System

Management

Guide for more information on the structure of the DCL task and on the

DCLtask-building

process.

—

APPLYING CORRECTIONS TO SOURCE FILES

used

can be

kit,

File DCL.CMD, in UFD [23,24] of your distribution

or as
cither to assemble DCL overlay modules and to re-task build DCL,
own
its
s
contain
file
The
a template for your own commands.
copy
must
you
,
directly
command
this
use
to
that
Note
instructions.
various files into its UFD, and you must appropriately modify any UFDs
that they reference. DCL.CMD also shows how to assemble the special
module COMMAND.

The following process shows how to reassemble a DCL overlay module and

The process is similar for root modules; simply

DCL.

build

re-task

specify DCLR rather than DCLO.

See DCL.CMD for details on

rebuilding

COMMAND.

MCR:

SET /UIC=[23,24]

XXX
MAC XXX=[11,10]RSXMC/PA:1,[23,10]DCLMAC/PA:1,
SET /UIC=[1,24]
LBR DCLO/RP=[23,24]XXX
@DCLBLD

TKB
DCL:

[23,34]

SET DEFAULT

1, XXX
[11,10]RSXMC/PASS:1,[23,10]DCLMAC/PASS:

MACRO

_
[23,24]XX

SET DEFAULT [1,24]
LIBRARY/REPLACE DCLO
@DCLBLD

LINK

When you have built a new version of DCL.TSK, you must replace the old

DCL

copy

Then

the

terminals whose CLI

This is done as follows:

a system CLI.

following

is DCL must be logged off or set to

commands

must

First, any

another

CLI.

(Note that these

executed.

commands are MCR only.)
MCR:

CLI

/ELIM=DCL

REM

DCL

INS
CLI

S$DCL/CLI=YES
/INIT=DCL

The REMove and

used

command
it

C.4

INStall

modify

is MCR only,

not

there

APPLYING

commands are also valid VMR commands and can be

and must be put

already).

CORRECTIONS

TO THE

in your

FILE

All F11lACP updates begin by creating a
[13,40].

The

following

system's startup file

SYSTEMS

SLP

(if

(F11ACP)

correction

file

example patches a module called WTRNIl.

Boot your system and log
>HELLO

However, the CLI /INIT

your system's image on disk.

UFD

in on a privileged account:

SYSMANAGER

PASSWORD:

necessary,

restore

the

required

(This example assumes that the

the

files

[1,24]

have

not.)

files

from

the

[13,10]

distribution

tape.

have been deleted,

but

APPLYING CORRECTIONS TO SOURCE FILES

>UFD DBO:[13,10]
>UFD DBO:[13,40]
>BRU
|
BRU> /NOINITIALIZE/SUPERSEDE/NOPRESERVE/BACKUP_SET:MPLUSBL15SRC
FROM: MMO: [13,10]F11PRE.MAC,WTRN1l.MAC
TO: DBO:
.
BRU--COMPLETED
BRU>
~ 7

Create

the correction

file:

>SET /UIC=[13,40]
>EDT WTRN1l.COR

(Create

correction

file)

Apply the cofrection:
>SET /UIC=[13,10]
>SLP
Assemble

@[13,40]WTRN1.COR
the corrected module with

executive prefix

file RSXMC.MAC,

the

and

Executive

the prefix

macro

1library,

the

file F11PRE.MAC:

>SET /UIC=[13,24]
>MAC WTRN1l=[1,1]EXEMC/ML,[11,10]RSXMC,[13,10]F11PRE,WTRN1

Replace the defective module

in the FCP library:

>SET /UIC=[1,24]
>LBR FCP/RP=[13,24]WTRN1
MODULES

REPLACED

WTRN1

All

MP:

the

task

build

assigned

the patch,

command

files

require

that

the appropriate device.

it may be

necessary

specification contained

the

change

the

1logical

device

Depending on the

the

size of

value

task-build command

the

partition

file:

PAR=FCPPAR:0:nnn

the

following

designation

for

examples,

xxx must

your desired

FCP,

that

replaced

is,

MDL or

the

3-character

LRG.

Task build the new FCP using the updated library:
>ASN NL:=MP:
Edit

the
>TKB

task-build
@FCPxxxBLD

command

file,

necessary,

this

time.

APPLYING CORRECTIONS TO SOURCE FILES
Install the updated FCP in the system image:
>SET /SYSUIC

SYSUIC=[g,54]
>SET /UIC=[g,54]

>PIP /NV=[1,54]FCPxxx.TSK
>RUN SVMR
ENTER FILENAME:

RSX11M

VMR>REM F11ACP

VMR>INS FCPxxx/PAR=GEN/IOP=NO/CKP=NO
VMR>
7
>RUN

SSHUTUP

Reboot the system to place the new FCP in use.

C.5

APPLYING CORRECTIONS TO RECONFIGURATION TASKS CON AND HRC

CON

task.

CNCMR for the
The following example illustrates how to patch module command
sequence
Unless indicated otherwise, use a similar

for correcting module HRONL for the HRC task.

This example assumes that:

You have deleted the source files in [27,10].

You have not deleted the object libraries and command files in

The object library for both CON and HRC is

The disk to which

[1,24]

and

[1,20].

you

Files-11] on drive DBO:.

will

apply

the

[1,24]OLR.OLB.

patches

mounted

The distribution tape is mounted foreign on MMO:.

Per form the following steps to patch CNCMR:
1.

Boot your system, and log into a privileged account.

necessary,

distribution

restore

tape.

the

required

files

from

the

>UFD DBO: [27,10]

>UFD

DBO:[27,40]
>UFD DBO:[27,24]

>BRU

BRU>/NOINITIALIZE/SUPERSEDE/NOPRESERVE/BACKUPSET:MPLUSBLlSSRC
From:
To:

MMO:[27,10]CNPRE.MAC,CNCMR.MAC

DBO:

BRU -- Completed

If you were correcting module HRONL, you would substitute for
1line in the previous command sequence:
the From:
HRONL .MAC
MMO: [27,10]HRPRE.MAC,

Create the SLP correction file in UIC
>SET /UIC=[27,40]
>EDT CNCMR.COR

([27,40].

APPLYING CORRECTIONS TO SOURCE FILES

Apply

the

SLP

correction

file

CNCMR:

>SET /UIC=[27,10]
>SLP

@[27,40]CNCMR.COR

Assemble

the

library

and

use

these

addition,
a

corrected

the
when

assembling

wuse either

CON module

CNCMR module

Executive prefix
the

file

the

file

Executive macro

RSXMC.MAC:

corrected

prefix

HRPRE.MAC

using

HRC

CNPRE.MAC

assembling

you also

module.

assembling

HRC module.

>SET

/UIC=[27,24]

>MAC

CNCMR=[1,1]EXEMC/ML, [11,10]RSXMC/PA:1,[27,10]CNPRE, CNCMR

Replace

the

CNCMR

object module

the

OLR

library:

>SET /UIC=[1,24]

>LBR

OLR/RP/NOEP=[27,24]CNCMR.OBJ

Task build CON using the updated libraty:
>ASN

DBO:=IN:

>ASN

DBOQ:=0U:

DASN

NL:=MP:

>TKB @CONBLD
NOTE

you do

not

have

the

task-build

command

files
[1,24]CONBLD.CMD and [1,24]CONBLD.ODL,
you must
use
the
nonprivileged
task-build
section
of
SYSGEN
in order to rebuild CON.
For
you

HRC module, you must
rebuild
HRC
1if
do
not
have
[1,24]HRCBLD.CMD
and

[1,24
] HRCBLD.ODL.
8.

Install

the

updated

reconfiguration

wutility

image:
For

CON,

type:

For

>SET /SYSUIC

>SET /SYSUIC
SYSUIC=[g,54]

>SET /UIC=[g,54]

Enter

filename:

>SET /UIC=[g,54]

PIP
RUN

RSX11M

use

Shut

the

system

>RUN

Reboot

the

filename:

VMR>REM HRC...
VMR>INS HRC

VMR> " Z

order

/NV=[1,54]HRC.TSK
S$SVMR

Enter

VMR>REM ...CON
VMR>INS CON

VMR>
"Z

new

down

SSHUTUP

system.

reconfiguration

using

system

type:

SYSUIC=[g,54]

PIP /NV=[1,54]CON.TSK
RUN SVMR

HRC,

the

tasks,

shutup

utility:

RSX11M

APPLYING CORRECTIONS TO SOURCE FILES
C.6

APPLYING FCS CORRECTIONS

done

Correcting the FCS modules on an RSX-11M-PLUS system can

updating the source files, assembling them, and replacing modules in
1is
This process
wusually LB:[1,1]SYSLIB.OLB.
library,
the system
complicated by the fact that there are three kinds of FCS:
1.

ANSI - supports ANSI format magnetic tape and big buffers

Non-ANSI - does not support ANSI tape or big buffers

Multibuffered - supports ANSI tape, big buffers, and multiple
buffers.

An FCS

source

that

directives

file

1like

CLOSE.MAC

on the global symbols defined

different

three

Other FCS source files,

assembly

contains

conditional

assembly

can produce three different CLOSE objects, depending

directives.

when

CLOSE.MAC

1is

assembled.

These

objects correspond to the three kinds of FCS.

DELETE.MAC,

have

such

conditional

They are only assembled one way; that is, only

one DELETE object exists.

The SYSLIB.OLB provided on the kits contains the ANSI FCS.
Thus, this
SYSLIB contains modules
1like
CLOSE,
assembled
with the ANSI tape
conditionals and big buffer conditionals
enabled,
and modules
1like
DELETE, which have no such conditionals and are the same in any FCS.
An alternate system library called NOANSLIB.OLB is also provided.
It
contains
an
FCS
that does
not
support ANSI tape, big buffers, or
your
on
SYSLIB
Be sure that you know whether the
multiple buffers.

system

or if it has been replaced with the

FCS,

ANSI

the

contains

non-ANSI or multibuffered FCS.

Details of the

MCR

follow.

correcting procedure

1is

syntax

-used

throughout.

C.7

UPDATING THE FCS SOURCES

[50,10]

The FCS source files are found in

source

done

entering

the

Updating

kits.

entering "SLP @filename" to apply the correction.

C.8

ASSEMBLING FCS

Assembling the updated source(s)

One

correction file into [50,10], and

can be done in either

two

ways.

way is simple and time-consuming; the other is quick, but it must

be done with great care.

The simple way is to set your UIC to

[50,20]

and enter MAC Q@FCSASM.

This will assemble every FCS variant properly,

The other choice

assemble

producing over

100 object files.

is to

only

the

sources

that

have

been

To
it saves machine time.
but
simple,
not as
is
This
updated.
assemble only a particular file, look
at
the
five
*.CMD
files
in
Search the command files for all mentions of the
on the kit.
[50,20]
file you want to assemble.

and what you do with

A description follows of each command file

its contents.

APPLYING CORRECTIONS

SOURCE

FILES

FCSBOTH.CMD assembles

code

specifically

tape,

big

buffers,

you
have
assembled

updated

your

the

or multiple buffers.
If the
source
1is
mentioned
in FCSBOTH.CMD, then

same

SYSLIB.

assembles

files like DELETE.MAC, which contain no
written to support or deny support to ANSI

way

For

regardless

example,

which

this

1is

kind

the

FCS

command

file
it is

line

that

DELETE:

[50,20]DELETE, [50,30]DELETE/-SP=[50,10] FCSPRE,DELETE
(FCSPRE.MAC

assemble

enter
MAC

necessary macros

you

should

and

set

global

your

UIC

symbols.)

[50,20]

and

[50,20]DELETE, [50,30]DELETE/-SP=[50, 10]FCSPRE,DELETE

and

the

defines

DELETE.MAC,
following:

alternative,

enter

"MAC

you

could

@filename".

conditional

put
A

the

file

assembly directives,

command

will

line

DELETE.MAC,

file

which

has

be mentioned

only

FCSBOTH.CMD.
FCSANSI.CMD

big

assembles

buffer,

source

objects for the ANSI kind
the
ANSI
FCS,
and
the
mentioned in FCSANSI.CMD,

line

you

For

example,

files

or multiple-buffering

found

this

of FCS.
source
then

command

1line

contain

If
your
file
you

you

FCSANSI.CMD

that

ANSI

conditionals.

should

assemble

from

tape,

produces

SYSLIB
contains
have updated is
use

the

command

source

FCSANSI.CMD

file.

assembles

CLOSE.MAC:

[50,20)]CLOSE.MTA, [50,30]CLOSE.MTA/-SP=[50,10]FCSANSI/PA:1,FCSBIGBUF/PA:1,FCSPRE,CLOSE
FCSANSI.MAC

enables

the

ANSI

tape

conditional

assembly

directives,
and
FCSBIGBUF.MAC
enables
the
big
buffer
conditionals.
Note the sequence of input file names.
It
is
absolutely
1imperative
that the source file is the last file
name specified, and that FCSPRE is next to it, in
every
FCS

assembly.
Otherwise,
the
proper
enabled, with potentially confusing
Any

file

that

assembled

by FCSNOANSI.CMD and
types
above,
which
CLOSE

will

not be

results.
assembled

FCSMULBUF.CMD.
Note
the
"MTA"
file
distinguish
between the three kinds of

objects.

FCSNOANSI.CMD

also

assembles

tape,
big
buffer,
produces objects for

SYSLIB
have

conditionals

and
dangerous
FCSANSI.CMD is also

contains

updated

the

or
the

non-ANSI

is mentioned

use
the

source

files

kind

FCS,

and

contain

conditionals.

the

FCS.

source

file

ANSI

It
your

you

FCSNOANSI.CMD, then
you
should
found in FCSNOANSI.CMD to assemble

the
command line you
source
file.
This
command
assembles CLOSE.MAC:

1line

[50,20]CLOSE.NMT, [50,30]CLOSE.NMT/-SP=[50,10] FCSPRE,CLOSE

that

multiple-buffering

from

FCSNOANSI.CMD

APPLYING CORRECTIONS

TO SOURCE FILES

FCSMULBUF.CMD assembles source files that contain ANSI
tape,
big
buffer, or multiple-buffering conditionals.
It produces
objects that support all of
these
features.
This
command

line

from FCSMULBUF.CMD

assembles CLOSE.MAC:

[50,20]CLOSE.MBF, [50,30]CLOSE.MBF/-SP=-

[50,10]FCSANSI/PA:1,FCSMULBUF/PA:1,FCSBIGBUF/PA:1,FCSPRE,CLOSE
FCSMULBUF .MAC

More
that

enables

the

multiple-buffering

FCSASM.CMD simply
causes
the
other
executed, to assemble FCS in all ways.
single sources, ignore FCSASM.CMD.

conditionals.

command
files
to
be
If you are assembling

information is necessary to correctly assemble a few FCS
sources
require
additional
prefix
files.
These sources are GET.MAC,

PUT.MAC,
assembled

produce

will

OPEN.MAC,

the

GET.MTA,

FINIT.MAC,

normal

GET.NMT,

and

RDWRIT.MAC.

(ANSI, non-ANSI, or
GET.MBF.
An additional

enable

GETSQ, the
this is the

conditional
assembly
directives
sequential GET module, for each kind
command

line

GET.MAC

way

from FCSANSI.CMD,

can

multibuffered)
to
file,
GPSEQ.MAC,

in GET.MAC to produce
of FCS.
For
example,

which

produces

GETSQ.MTA:

[50,20]GETSQ.MTA, [50,30]GETSQ.MTA/~-SP=~

[50,10]GPSEQ/PA:1,FCSANSI/PA:1,FCSBIGBUF/PA:1,FCSPRE,GET
If you correct GET.MAC, be
sure
that
you
assemble
it
to
produce
objects GET and GETSQ, for whatever kind of FCS your SYSLIB contains.

Similarly,

GPSEQ.MAC will

for
each
kind
of FCS.
which produces PUTSQ.NMT:

produce

PUTSQ,

This

the

sequential

command

line

from

PUT

module,

FCSNOANSI.CMD,

[50,20]PUTSQ.NMT, [50,30]PUTSQ.NMT/-SP=[50,10]GPSEQ/PA:1,FCSPRE,
PUT
If

you

correct

objects

named

OPEN.MAC

can

PUT.MAC,

PUT
be

and

sure

that

you

assemble

produce

PUTSQ.

assembled

the

normal

multibuffered)
to
produce
OPEN.MTA,
additional prefix files exist.

way

(ANSI,

OPEN.NMT,

non-ANSI,

OPEN.MBF.

OPFID.MAC produces the open-by-file-id module,
OPFID.
command line from FCSANSI.CMD, which produces OPFID.MTA:

This

Three

1is

the

[50,20]O0PFID.MTA, [50,30]OPFID.MTA/-SP=[50,10]0PFID/PA:1,FCSANSI/PA:1,FCSBIGBUF/PA:1,FCSPRE,OPEN
OPFNB.MAC

the

produces

command

line

the

open-by-file-name

from FCSANSI.CMD,

which

block module,

produces

OPFNB.

This

OPFNB.NMT:

[50, 20]OPFNB.NMT, [50,30]OPFNB.NMT/-SP=[50,10]OPFNB/PA:1,FCSPRE,OPEN
OPENR.MAC

This

produces

the

command

the

open

line

module

from

for

resident

FCSMULBUF.CMD,

which

1libraries,

produces

OPENR.

OPENR.MBF:

[50,20]OPENR.MBF,
[50, 30]OPENR.MBF/-SP=-~
[50,10]OPENR/PA:1,FCSANSI/PA:1,FCSMULBUF/PA:1,FCSBIGBUF/PA:1,FCSPRE,OPEN
If

you

correct

OPEN.MAC,

objects
OPEN,
OPFID,
SYSLIB contains.

be sure
OPFNB, and

that
you
OPENR, for

C-11

assemble
whatever

it
kind

to
of

produce
FCS your

APPLYING CORRECTIONS TO SOURCE FILES

FINIT.OBJ and
be assembled to produce condi
FINIT.MAC and RDWRIT.MACx canfile
tionals to
es
enabl
P.MAC
FCSSU
The prefi
RDWRIT.OBJ.
used in
be
to
and RDWRSL.SUP
produce objects FINTSL.SUP These
objects are necessary for correct

libraries.
nes, which may be specified
execution of the user AST completion routi
This is the 1line from
ns.

supervisor-mode
for

and

READS

FCS

WRITES

functio

FCSANSI.CMD, which produces FINTSL.SUP:

[50,20]FINTSL.SUP,[50,30]FINTSL.SUP/—SP=[50,10]FCSSUP/PA:l,FCSPRE,FINIT

n the same entry point
Object files FINTSL.SUP and RDWRSL.SUP contai
ore they must be replaced in

names as FINIT.OBJ and RDWRIT.OBJ. Theref
SYSLIB with their entry points deleted, so that they are only used
when they are explicitly called when a supervisor-mode library is
See the example below.

task-built.

C.9

REPLACING THE FCS OBJECT MODULES

libraries, and use
Set your UIC to [1,1], make a backup copy of the have
assembled. For
you
that
s
object
FCS
ted
correc
LBR to replace the
PUT, and FINIT
,
DELETE
led
example, suppose you have updated and assemb
on a system with an ANSI FCS in SYSLIB:
SET /UIC=[1,1]

PIP /NV=SYSLIB.OLB

LBR SYSLIB/RP=[50,20]DELETE.OBJ,PUT.MTA,PUTSQ.MTA
LBR SYSLIB/RP=[50,20]FINIT.OBJ,FINTSL.SUP/-EP
Suppose you also use NOANSLIB.OLB:
PIP /NV=NOANSLIB.OLB

LBR NOANSLIB/RP=[50,20]DELETE.OBJ,PUT.NMT,PUTSQ.NMT

LBR NOANSLIB/RP=[50,20]FINIT.OBJ,FINTSL.SUP/—EP

If you want to

resident

incorporate

1library

FCSFSL

the

corrected

modules

into

library,

supervisor-mode

FCSRES

rebuild

the

1in

the

library, and then rebuild every task that links to it with SYSGEN. If
you rebuild and install a resident library and run a task that linked
to the old resident library, then the task will call routines

resident

library

the

wrong

The

addresses.

results

will

uncertain and potentially damaging, especially for privileged tasks.

C.10

PATCHING OBJECT MODULES

The Object Module Patch Utility (PAT)

into

existing

object

module.

incorporates

DIGITAL

publishes

written in MACRO-11 assembly language to correct an error

change.

object

patch

a patch file
Or

make

You then create and assemble the published file and input it

to PAT along with the object file being patched.

You must include the published checksum values in the specification
If the checksum value
for the input file and the correction files.
an error. If the
reports
PAT
result,
d
compute
the
does not agree with
correction

file

caused

the error, check the source file against the

ly.
original published source file to verify that it was copied correct
version of
If the input file caused the error, verify that the correct

the file is being patched.

APPLYING CORRECTIONS TO SOURCE FILES
Note

that

normally

object
module
containing the

necessary

from a library.
corrected object

use

LBR

PAT produces a
code.
When you

extract

the

original

new object module file
patch modules
from
a

library,
take the object module from the distributed library, correct
it, and then put it
into
a
copy
of
the
original
1library.
(All
corrections
are
put in the copy, which is used to rebuild the task.)
The
and

following guidelines
correction files.

Specify

Use

following

the

explicit

name,

apply

extension,

conventions

for

Correction

and

for

version

PAT

command

input

for

file.

number

source

for

all

input

name.PAT
name
. POB
name.OBJ
;n
name .0OBJ;n+1

and

correction

following example illustrates the command
file and the PAT output file:

files.
formats

for

correction
>MAC

each

Specification

file

Specify checksums

formats

names:

File

Correction file object
Input file object
Corrected object file

The

the

NAME.POB=NAME.PAT

>LBR

NAME.OBJ;1=LIBRARY.OLB;1l/EX:NAME

>PAT

NAME.OBJ;2=NAME.OBJ;1/CS:xxxx,NAME.POB/CS:yyyy

>PIP

LIBRARY.OLB;2=LIBRARY.OLB;1

>LBR

LIBRARY.OLB;2/RP=NAME.OBJ; 2

creating

the

INDEX

Account

File

Maintenence

Program

ACNT

See

encryption,

Batch job,
Batch log,
BRU, 1-31
and BAD,

1-37

1-40
2-8

block,

1-34

bootable system image, 1-32
device support, 1-34
devices, 2-10
devices, new, 1-31
documentation corrections, 2-8
error message, 2-10
indirect command file, 2-9
memory for stand-alone, 1-34
/MOUNTED, 1-34
multivolume backup, 1-33
/NEW VERSION qualifier, 1-32

/NOSUPERSEDE qualifier,

qualifiers, 1-33
restoring, 1-31, 1-33
restrictions, 1-31
"stand-alone, 2-10
/VERIFY, 2-9

/VERIFY qualifier,
wildcards, 2-9
Buffering
big,

2-9

1-32

1-51

DECUS,

discontinued, 1-5
KDAS50 controller,
LNO3 printer, 1-5
overview, 1-2
printers, 1-5
processors, 1-4
RD52 disk, 1-2
RD53 disk, 1-2
restrictions, 1-7
RQODX2
RQDX3

1-39

TK50

tape,

preserving
Controllers,

DLVJ1l,

changes,
new, 1-2

1-10

CPUs

LSI1-11/73,

1-4
1-4
MicroPDP-11/23, 1-4
MicroPDP-11/73, 1-4
MicroPDP-11/83, 1-4
PDP-11/84, 1-4
Crash Dump Analyzer

See

Data,
DCL,

1-2
1-8

1-5

vectored,

1-53

error message,

1-38

modem support,

1-5

Error logging, 1-56
control files, 1-57
commands,

documentation

Emulator

1-57

corrections,

2-22

error log packet format, 2-22
hard and soft limits, 1-58
MCR commands, 1-57

DTE

1-51

1-18

modified,

1-17

/HF switch, 2-11
/LIM switch, 2-10
Drivers, 1-47

DCL

command,

1-3

1-13

DTE

CDA

asynchronous,

1-3

DMP

MicroPDP-11,

Terminal

interface,

1-3

1-17

target,

1-53

1-3
1-3

protection UIC, 1-17
Disk data caching, 1-17
Disks
new,

1-61

directive,

Data

UNIBUS
tape,

1-40

1-3

controller,
controller,

TK25

Common

See

A-1

named,

device support, 1-39
system assign table,
Checkpointing

1-23

/DELETE switch restriction,
Device drivers, 1-46
Devices

default,

1-39

TKB,

2-3

logical names, 1-70
named directory, 1-70

Directives,
Directory

Catch all task
TDX, 1-25
cba,

Debugging, 2-7
Decimal version numbers,
DECmail-11], 1-70
installation, 1-71

RUX50

1-51

multi,

1-18

RUN/COMMAND command, 2-2
SHOW DEVICES command, 2-2
/DE switch, 2-12

1-32
appending, 1-31
boot

new,

documentation corrections,
logical names, 1-23
qualifiers, new, 1-20
restriction, 1-23

ACNT

password

DCL (Cont.)
commands,

restriction,

1-23

Index-1

1-58

INDEX

Error

logging

(Cont.)

user-written module,
Executive, 1-14
CLI,

1-16

data

structures,

entry

message,

FORTRAN,

1-15

.ONERR directive, 2-5
restriction, 1-30
symbols, 1-29, 1-30, 2-5
time-out values, 2-5

2-6

1-15

1-14

full-functionality,

Indirect
1-17

Command
Indirect

See

macro expansion, 2-6
mapping register symbols,
parameter lists, 2-6

1-15

1-14

INI

/BAD

INI

command

INS,

1-25

INSTALL

privileged

1-14
routines,

moved,

vectored,

terminal
IP11, 1-4

1-52

KDA50

FCS,

library,
Service

Block

(FDB)

/CR
1-23

/NU

support,

switch,

1-35

switch,

RT-11

2-12

/ZE
FMS-11
FMT

1-35
2-12

device,

transfer

mode

switch,

LK201

LNO3

1-36

Log

switches,

1-65

Full-functionality
TKB,

1-36

Executive

1-12

equivalence

1-70
1-13
names,

1-13,

1-40

MACRO-11,
parser,

asynchronous, 1-51
completion, overlapped,
processing, 1-55
1-51,

RMS,

1-55

Indirect
delimiters,

1-65

new,

parsing,

1-49

1-13

system table,
translations,

1-55

1-11
1-11

LSI-11/73

processor
configurations, 1-4

restrictions, 1-51
routines, 1-50, 1-51
sequential processing,
user-written, 2-20

1-11

1-49

filespec format, 1-48
/FINAL, 1-12
format, 1-11
functionality, old, 1-12

1/0

requests,

2-8

ddnn:

FCS,

1-61

HELP files, 1-33
/HF switch, 2-11
/HOLD switch restriction,

file,

form,
DECmail-11,
directives,

device restrictions,
devices, 2-12

keyboard restriction,
printer, 1-5

Logical names, 1-11
colons in, 1-12

2-11

2-12

restriction,

2-13

command,

2-13

/IN switch, 2-13
/LI switch, 2-18
/LIM switch, 2-11

2-12

restrictions,

/RT

1-65

2-13
documentation corrections,
file attributes, 2-13

2-12

message,

switch,

CREATE

FLX

error

1-3

LBR

specification
decimal version numbers,

device

1-37

/NONAMED qualifier, 1-17
/NONAMED switch, 1-17

1-49

switch,

1-37

exercising,

products, 1-65
directories, 1-17,

named

File

/DE

1-10

1-4

Layered

1-42

Descriptor

offsets,

1-60

command,

2-5

2-4

command,

controller,

1-42

FCS resident
File Control

File

IPV11l,

1-42

directory,

See

SELECT

(MCR),

/WB

I0X

1-15

Processor

command

tasks, 1-15
programming language interface,

FCS,

1-30

1-29
.FORM modification, 1-29
module name size, 1-30

1-15

points,

PASCAL,

(Cont.)

error

expressions,

directives, 1-14
documentation corrections,

drivers,

Indirect
1-56

1-55

MACRO-11,

logical
MCS

1-29

new, 1-29
documentation corrections,

support,

Magnetic

directive,

MCR,

2-5

Index-2

1-65

names,
tape,

1-65

1-67

new,

1-2

1-23

commands,

new,

1-24

1-7

INDEX

MCR

Resident

(Cont.)

RMSLBM.TSK,

RMSRES.TSK, 3-1
Resource Monitor Display
See

layered

products,

NCT,

RMD

/RESTART switch
RMD,

Named directory, 1-17
DECmail-11, 1-70
1-65

task

Terminal

P/0S
logical
Password

error

new

1-37

See
2-13

2-13

also

2-14

Pre-generated kit options, 1-37
PRINT /[NO]TRANSFER command (DCL),
2-8

RMSBCK,

3-4

RMSCNV,

3-3,

RMSDES,

3-5

RMSDSP,

3-4

3-6,

3-7

3-4,

3-8

3-4
switches,

RMSCNV,

3-3,

Printers

RMSDES,

3-5,

RMSDSP,

3-4,

1-7

switches,

LAS50,

1-5

LNOl1,

1-5

RMSIFL,

3-6,

LNO3,

1-5

RMSRST,

3-4,

modifying support, 1-6
page size, 1-6
removing support, 1-6
standard,

SYSGEN,

1-7

Protection

UIC,

1-17

3-4
3-7
3-8

3-4

controller,

1-3

RQDX3

controller,

1-3

switch,

2-12

2-19
DEVICES

format,
SHUTUP,

Services

RMS-11

2-2

/-SE switch, 1-15
/SHAREABLE:LIBRARY qualifier,
SHOW

1-46

RD52 disk, 1-2
RD53 disk, 1-2
Record Management
See

3-7

RQDX2

/RT

3-14

3-9

3-6,
3-9

device support, 1-35
RUN/COMMAND command (DCL),

1-17

1-17
1-17

switches,

3-4
3-6,

3-13

RT-11

1-5

Protection
default,
setting,

ODL files,
3-15

RMSIFL,
RMSBCK,

problems

procedure,

RMSRST,

PRINT command
log file, 2-8
Printer mode, 1-6
1""'5 Fd

3-1
3-7

3-15

Reporting

command and
rebuilding,

2-18

documentation corrections,

LA10O,

3-2,

access

startup command
utilities

PIP

switch,

summary,

3-1,

to RSTS/E, 3-3
reporting problems,

PAT

switch,

features,

remote

documentation corrections,

3-7,

files in the distribution kit,
3-10
installation, 3-13
logical name interface, 3-3

length, 1-37
setting, 1-37

switch,

3-5,

3-13

operations,

error message,

3-2,

messages,

3-10,

1-13

names,

encryption,

RC25,

2-7

2-4

3-10

2-9

2-7

ACNT,

correction,

flags,

methods, 3-4, 3-7
documentation changes, 3-9,

(NCT),

1-23

/TD

status

RMS-11

1-65

/NOSUPERSEDE qualifier,
/NU switch, 2-12

/DD

1-40

access

Network Command

/=PI

restriction,

1-38

documentation

1-23

oDT,

3-2
3-2

RMSLBL.TSK,

keywords, new, 1-24
Micro/PDP-11, 1-8
MicroPDP-11/23, 1-8

FMS-11,

library configuration,

3-1

documentation corrections, 2-4
INI command description, 2-4
keywords, modified, 1-25

command

2-2

(DCL)

1-38

Slow Task

Builder,

1-61

SLP

documentation

REMOVE command, 1-10
Reporting problems
RMS-11, 3-15

error

file

Index-3

message,

names,

corrections,
2-15

2-15

2-14

INDEX

SLP

(Cont.)

incorrect
Software

2-14

performance monitor,
Performance Report

Software
See

Task

examples,

1-9

1-52

TDX,

1-25

and

Source

files
correcting,

updating,

C-1

restriction,

1-9

installing permanently,
modifying, 1-28
Terminal Exercising

1-39

commands,

1-39

Terminals,

SPR

TK25

definition, B-1l
filling one out, B-1
priorities assigned, -B-2
types,

block,

2-21

driver,

(MCR)

crash

System

device,

creating

Generation

1-9

subsystem,

MSCP

command,

1-10

1-7

with

1-10

System
See

/CP

(MCS),

names,

1-40

2-16

2-16
1-8

SYSGEN

1-9

processor

support,

1-8

see

Tape,

disks,

1-60

FCSRES,

1-60

switch,

library,

1-60

1-60
Executive,

1-61,

1-64

1-63
command,

1-59

1-60

1-8

support,

LINK/SLOW

1-10

/=PI

1-8

library

1-59,

LINK/CODE:FAST
MAP command,
command,
switch, 2-18

qualifiers,

routines

new,

restrictions,

SYSLIB

root

1-59

1-63

statements,

2-17

/SB switch, 1-59, 1-61
/SHAREABLE:LIBRARY qualifier,
new,

1-2

2-19

Task

SKTBLD.BLD

checkpointing, 1-51
directive common, 1-53
entry points, 1-52
Executive, 1-15
Executive code, 1-53
I-

resident

LINK/CODE:CLI

1-9

(FTB),

I- and D- space tasks,
/LI switch, 2-18

support,

features,

VAX,

FCS

library,

terminal

Builder

2-16

1-61

optional

System

Task

full-functionality

1-9

target

2-19

switch,

FCSFSL,

/FM

Generation,

support,

1-63

1-60

1-61
documentation corrections,
error message, 2-19

correction
2-15
s,

device support, 1-9
I/0 terminal driver
LAT

code,

1-60

section

also

1-61

vectors,

checkpointing, 1-61
/CL switch, 1-59
common/library block,

Fast

routine

routines,

switch,

build

1-8

documentation
program

1-43

1-59

SYSLIB

new date

1-45

utilities,

autoload

nonprivileged tasks, 1-10
optional features, 1-9
questions, 1-9, 1-10, 2-1
response rings, 1-10
software performance monitor,
1-9
VAX,

restriction,

/AL

1-10

lights,

1-43

use

1-3

1-42

limitations,

TKB,

directories,

IP1l1

1-3

1-47

indicator

SYSGEN

1-28

1-2

tape,

description,

command
format, 2-7
also

new,

magnetic

TK50 tape
brief description,
BRU, 1-44

B-2

control

SUBMIT

See

1-25

1-25
definition, 1-25
installing, 1-25

C-1

Spooling

Status

MCR,

commands,

modification,

spooling

TKB

TCB,

SPR

SPM-11

builder

see

and

D-

1/0, 1-51
installing
vectoring,

space,

command

procedure,

1-62
Slow Task Builder (STK), 1-61
/SS switch, 1-63
supervisor-mode, 1-60, 2-18
restriction, 1-62

l1-64

switches,

new,

1-59

symbol table file, 1-64
task label block, 2-19

permanentl
1-28
y,
1-52

Index-4

INDEX

vuIic, 1-17

Update procedure, 2-1
VAX-11] RSX, 1-8
Vectored Executive, 1-52 to 1-55

Vectoring, 1-52 to 1-55

drivers, 1-53
/VERIFY qualifier, 2-9
Version number
decimal, 1-23
Virtual Monitor Console Routine
See VMR

VMR

new keywords,

1-38

Volume label format, 1-50

/WB qualifier, 1-10

Writing device drivers, 1-51
Writing

I/0 drivers

SASUMR, 2-21
data structures, 2-20

documentation corrections, 2-20
GTPKTS call, 2-20
K.OWN, 2-21
SCBDF$, 2-21
U.BUF, 2-21
US.FOR, 2-20
UsS.PUB, 2-20

“

/ZE switch, 2-12

Index-5

RSX-11M-PLUS
Release Notes

AA-H427D-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.
(]

Assembly language programmer

(]

]

Higher-level language programmer
Occasional programmer (experienced)

(]

User with little programming experience

]

Student programmer

(]

Other (please specify)

Name

Date

Organization

Street

City

State

Zip Code
or Country

—

DoNotTear- Fold Hereand Tape

—

No Postage

Necessary
if Mailed in the

United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.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

Cut Along Dotted Line

———

mm—

p——

Do Not Tear - Fold Here

—