Digital PDFs

AA-2573H-TC

April 1983

124 pages

Original

5.7MB

Document:	RSX-11M/RMS-11/RSX-11S Release Notes
Order Number:	AA-2573H-TC
Revision:	0
Pages:	124
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V4.1_Apr83/1_Introduction/AA-2573H-TC_rsx4.1relNotes_198304.pdf

OCR Text

RSX-11 M/RMS-11/RSX-11 S
Reiease Notes
Order No. AA-2573H-TC

RSX-11 M Version 4.1
RMS-11 Version 2.0
RSX-11 S Version 4.1

digital equipment corporation · maynard, massachusetts

First Printing, November
Revised, September
Revised, January
Revised, April
Revised, December
Revised, June
Revised, January
Revised, April

1974
1975
1977
1977
1977
1979
1982
1983

The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a
license
and may be used or copied only in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by Digital Equipment Corporation or its
affiliated companies.

The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future
documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-lo
DECSYSTEM-20
DEC US
DECwriter

DIBOL

EduSystem
!AS
MAS SB US
PDP
PDT
RSTS

RSX
UNIBUS
VAX
VMS
VT

mamama
ZK2255

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

DIRECT MAIL ORDERS (CANADA)

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

Digital Equipment of Canada Ltd.
940 Belfast Road
Ottawa, Ontario K1 G 4C2
Attn: A&SG Business Manager

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

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 (SOC), Digital Equipment
Corporation, Northboro, Massachusetts 01532

CONTENTS

Page
PREFACE

vii

CHAPTER 1

RSX-llM V4.l RELEASE NOTES

NEW FEATURES FOR RSX-llM V4.l • • • • • • • • • • 1-1
RSX-llM Executive
• • • 1-1
SYSGEN Features • • • • • • • •
• • • • • 1-1
Backup and Restore (BRU)
• • • • •
• • 1-2
MCR and VMR
• • • •
• 1-2
Task Builder (TKB)
• • • •
• • • • • 1-2
New Device Support
• • • •
• 1-3
Support for the LASO, LAlOO, and LNOl Printers • 1-3
Files-11 ACP • • • • • • • •
• • • • • • • • 1-5
PDP-11 PASCAL/RSX • • • •
• • • • • • • • • 1-5
SUMMARY OF TECHNICAL CHANGES • • • • • • • • • • • 1-5
RSX-llM System Generation and Installation
Guide (R) • • • • • • • •
• • • • • • • • • 1-6
1.2. 2
RSX-llM/M-PLUS MCR Operations Manual (U) •
• 1-6
RSX-llM/M-PLUS Command Language Manual (R)
• 1-7
1.2 .3
1.2.3.1
COBOL-81 • • • • • • • • •
• • • • • 1-7
1.2.3.2
LINK/C81 Command • • • • • • • • • • • • • • • 1-9
1.2.3.3
CORAL 66 • •
1-10
1.2.3.4
BASIC-PLUS-2 • • • • • • • •
• • • • 1-12
1.2.3.5
FORTRAN 77 • • •
• • • •
1-12
1.2.3.6
BACKUP Command
• • • •
• • • • • • 1-12
1.2.3.7
SHOW Processortype Command •
• • • • • • 1-13
1.2.3.8
Miscellaneous Items
• • • • 1-13
1. 2. 4
RSX-llM/M-PLUS Utilities Manual (U)
1-13
Backup and Restore Utility (BRU) (R) • • • • 1-14
1.2.4.1
1.2.4.2
Task/File Patch Program (ZAP)
• • • • 1-15
RSX-llM/M-PLUS I/O Drivers Reference Manual (R) 1-16
1. 2. 5
1. 2. 6
RSX-llM/M-PLUS Task Builder Manual (R) • •
1-16
RSX-llM/M-PLUS System Management Guide (U)
1-18
1. 2. 7
Virtual Console Routine (VMR)
• • • •
1-18
1.2.7.1
RSX-llM/M-PLUS Error .Logging Manual (R)
1-18
1. 2. 8
1. 2. 9
RSX-llM Mini-Reference (R) • • • • •
1-20
1.3
NOTES ON SOFTWARE • • • • • • • • • • • • • • • 1-20
1. 3.1
Baseline Systems • • • • • • • • • • • • • • • 1-20
System Generation and Installation • •
1-21
1.3. 2
1.3.2.1
Performing an RSX-llM V4.l SYSGEN on a V3.2
System • • • • • • • • • • • • • • • •
1-21
1.3.2.2
Restriction to V4.l On-Line SYSGEN • •
1-22
V4.0 Saved Answer Files • • • • • • • • • • 1-22
1.3.2.3
1.3.2.4
Determining the Number of RKOS Units •
1-22
SYSGEN on RLOls or RL02s • • • • • • • • • • 1-22
1.3.2.5
1. 3. 3
user Account for the Warm-Up Session • • • • • 1-22
BRU64K Restriction • • • •
• • • •
1-23
1. 3. 4
DSC64K, DSCSYS, and BADSYS •
1-23
1. 3. 5
Power-Fail Recovery • • • •
1-23
1. 3. 6
Change to Executive~s Task Aoort Code • • • •
l . 3. 7
Restriction to Error Logging • • • • • • • • • 1-24
1. 3 .8
TDX (Catch-All Task) • • • • • •
1-24
1. 3 .9
1.1
1.1.1
1.1.2
1.1. 3
1.1.4
1.1.5
1.1.6
1.1. 7
1.1.8
1.1.9
1.2
1. 2.1

"' A

.i.-~~

iii

CONTENTS
Page
1.3.10
1.3.11
1.3.12
1. 3 .13
1.3.14
1.3.15
1. 3 .16
1.3.17
1.3.17.1
1.3.17.2
1.3.17.3
1. 3 .18
1.3.19
1. 3. 20
1. 3. 21
1. 3. 22

Restriction for DCL as the Catch-All Task
Indirect Command Procedure Library • • • •
Indirect Command Processor Support for V4.l
Task Builder Restrictions • • • • • • • • • •
Modifications to System Library Task Builder
Data Structures • • • • • • • • • • • • •
Transportability Among 22-bit Systems • • • •
Device Drivers and User Tasks • • • • • •
Changes to Code and Data Structures for
Privileged Tasks • • • • • • • • • • • • •
Changes Made to Executive Code • • • •
Changes Made to Executive Data Structures
Changes Made to I/O Data Structures • • • •
MACR0-11 • • • • • • • • • • • • • • , • • • •
Restriction for EDT Version 2.0 • • • • • • •
Changes to the Command String Interpreter (CSI}
Bootstrapping a DB-, DM-, or DR-Based System •
Correction to Multiuser MCR on an Unmapped

1-28
1-28
1-28
1-29

Sys tern •

1-35
1-35
1-35
1-35
1-36
1-37
1-37
1-38
1-40
1-40
1-42
1-46
1-47
1-48

•

File Transfer Program (FLX)
• • • • •
Incompatibilty Problem with BRU Tapes • • • •
1.3.24
Device Restrictions • • • • • • • • •
1. 3. 25
Queue Manager • • • • • • • • • • • • • • • •
1.3.26
Building the COBOL-81 Compiler • • • •
1. 3. 27
REPORTING PROBLEMS AND APPLYING CORRECTIONS
1.4
Software Performance Report • • • • •
1. 4 .1
Applying Corrections to Source Files •
1. 4. 2
Updating an Executive Source Module • • • •
1.4.2.1
Updating an MCR Source Module • • • • • • •
1.4.2.2
Updating a DCL Source Module • • • •
1.4.2.3
Patching Object Modules • • • • • • • • • • •
1. 4. 3
NOTES TO RSX-llM V4.l DOCUMENTATION
1.5
RSX-llM System Generation and Installation
1. 5.1
1. 3. 23

Guide

• • • • .

• • • .

• • • • • • •

RSX-llM/M-PLUS MCR Operations Manual •
RSX-llM/M-PLUS Utilities Manual ••
Correction for PIP Utility • • • •
1.5.3.1
Correction for FLX Utility • • • •
1.5.3.2
Format Change the LBR /CR switch •
1.5.3.3
1.5.3.4
New Switch for File Dump Utility (DMP)
New Error Message for PAT Utility • • •
1.5.3.5
1. 5. 4
RSX-llM/M-PLUS I/O Drivers Reference Manual
IAS/RSX-11 I/O Operations Reference Manual • •
1. 5 .5
1.5.S.l
MTAACP Enhancements • • • • • • • • • • • •
Compliance With ANSI and FIPS
••••
1.5.5.1.1
Support of Unlabeled Tapes • • • • • • • •
1.5.5.1.2
Mount, Dismount, and Volume Switch Control
1.5.5.1.3
RMS-11 Support • • • • • • • • • • • •
1.5.5.1.4
FDB Offset Definitions • • • • •
• •••
1.5.5.2
Shared Access and Block Locking
1.5.5.3
Opening a File by File ID Number •
i.5.5.4
Buffer Flush Routine (.FLUSH)
1.5.5.5
I/0 Error Codes • • • • • • • • •
1.5.5.6
1. 5.6
IAS/RSX-11 SYSTEM LIBRARY ROUTINES REFERENCE
MANUAL • • • • • • • • • • • • • •
1. 5. 7
RSX-llM/M-PLUS ODT Reference Manual • • • • •
1.5.8
RSX-llM/M-PLUS System Management Guide • • • •
1.5.8.1
Virtual Monitor Routine (VMR}
•••••••
1. 5.9
RSX-llM Guide to Writing an I/O Driver Manual
1.5.9.1
Changes to Data Structure Macros •
1.5.9.1.l
HWDDF$ •
1.5.9.1.2
PKTDF$ • • • • • • • • • •
1.5.9.1.3
TCBDF$ • • • • • • • • • • •
1. 5. 2
1. 5. 3

n,..n .... ,,,. ...
u~curq

1.5.9.2

•••

•

••

•

Asynchronous Buffered I/O
iv

•

.........

1-30
1-30
1-31
1-32
1-32
1-32
1-33
1-33
1-34
1-34
1-34

1-48
1-48
1-49
1-49
1-49
1-49
1-49
1-49
1-50
1-50
i-50
1-50
1-51
1-52
1-52
1-53
1-53
1-53
1-53
1-54
1-54
1-54
1-54
1-54
J.-55

1-55
1-55
1-55
1-56
1-56
1-56

CONTENTS
Page
1.5.10
1.5.10.1

RSX-llM/M-PLUS Task Builder Manual • • • • • •
Task-building an F4PRES, FORRES, or FMSRES

1.5.10.1.1
FCSRES • • • • • • • •
F4PRES • • • • • • • • • • • • • • • • • •
1.5.10.1.2
Options and Tradeoffs
• • • • • • • •
1.5.10.1.3
RSX-llM/M-PLUS Executive Reference Manual • •
1.5.11
Change to Executive Directives • • • • • • •
1.5.11.1
Corrections to Executive Reference Manual
1.5.11.2
CHAPTER 2

1-57

1-57
1-58
1-59
1-59
1-62
1-62
1-62

RMS-11 VERSION 2.0 RELEASE NOTES

2 .. 1
NEW FEATURES FOR RMS-11 VERSION 2.0 • • • • •
2-1
2 .1.1
Support for Clustering and Task Independence • • 2-1
Subset Library Support • • • • • • • • •
2-1
2.1. 2
Disk-Overlaid RMS-11 • • • • • • • • • •
2 .1. 3
• 2-1
Remote File and Record Access via DECnet e • e e 2-2
2.1.4
2.1.4.1
Remote Node Specification • • • • •
• 2-3
Linking Programs with RMSDAP Support
2.1.4.2
2-3
2.1.4.3
RMSDAP Environments • • • • • • •
. . • • • 2-4
New File and Directory Operations
2.1. 5
• 2-4
2.1.5.1
ENTER/REMOVE •
• • • • • • • • • • • 2-4
2.1.5.2
RENAME • • •
• • • • • • • • • •
• 2-4
2.1.5.3
PARSE
• • • • • • •
• 2-4
SEARCH • • • •
• • • 2-4
2.1.5.4
Wildcarding • • • • • • • • • • • • • •
2.1.6
• 2-4
Random Access to Fixed-Format Disk Sequential
2 .1. 7
Files • • • • • • • • • • • • • •
• • 2-5
2.1.8
Increased Device Independence • • • •
• • 2-5
2.1.9
More Usable Block I/O Facilities •
• 2-6
2.1.10
Sharing for Relative and Indexed Files •
• • 2-6
2.1.11
RMS-11 Utilities • • • • •
• • • • • • • 2-7
2.1.11.1 New File Design Utility_
• • • • •
• 2-7
2.1.11.2 New Features for RMSDSP
• • • • • 2-7
2.1.11.3 New Features for RMSCNV
2-8
2.1.11.4 Additional Utility Features
• • • • • 2-8
2.2
SUMMARIES OF TECHNICAL CHANGES
• • • • • • • • 2-9
2.2.1
RSX-llM/M-PLUS RMS-11 User's Guide (R} • • • • • 2-9
2.2.2
RSX-llM/M-PLUS RMS-11 Macro Programmer's Guide
2-11
(R)
• • • • • • • • • • • • • • • •
RSX-llM/M-PLUS RMS-11 Utilities (N}
2.2.3
2-12
2.3
COMPARISONS WITH RMS-11 VERSION 1.8
2-13
Memory-Resident Library (RMSRES)
2.3.1
2-13
2.3.2
Memory-Resident Library (RMSSEQ} •
2-13
Memory-Resident Library (DAPRES) •
2.3.3
2-14
Disk-Overlaid RMS-11 • • • • • • • • •
2.3.4
2-14
Non-Overlaid RMS-11
• • • • • • • • • • • 2-14
2.3.5
2.3.6
Other RMS-11 Version 1.8 Compatibility Notes • 2-15
2.4
MISCELLANEOUS INFORMATION • • • •
2-16
2.5
PROBLEMS FIXED WITH RMS-11 VERSION 2.0 • • • • • 2-16
2.6
KNOWN PROBLEMS WITH RMS-11 VERSION 2.0 • • • • • 2-17
2.7
RMS-11 FILES AND PLACEMENT ON THE DISTRIBUTION
2-17
KIT
• • • • • • • • • • • • • • • • • • • •
2.8
RMS-11 VERSION 2.0 INSTALLATION
• • • • • 2-19
2-19
RLOl/02 and RK06/07 Procedures
• • • •
2.8.1
2.8.2
Startup Command Procedures • •
2-19
Utility Configurations • • • •
2-20
2.8.3
2.8.3.1
Utility Command and ODL Files
••••
2-20
Rebuilding the Utilities •
• • • • • • • • 2-21
2.8.3.2
2-21
2.9
REPORTING PROBLEMS • • • • • • • • • • • •

CONTENTS
Page
CHAPTER 3

RSX-llS VERSION 4.1 RELEASE NOTES

3.1
3 .1.1
3.2
3.2.1

NEW FEATURES FOR RSX-llS V4.l
3-1
New Devices • • • • • • • • •
• • 3-1
NOTES ON SOFTWARE • • • • • • • • • • • • • • • • 3-1
Host Hardware Configuration Requirements for
RSX-llS SYSGEN • • • • • • • • • • • • •
• 3-1
Fixing Tasks on RSX-llS with PLAS Support
• 3-1
3.2.2
3.2.3
VMR Support for Systems Larger than 124.K Words 3-2
RSX-llS System Generation • • • • • • • • • • • 3-2
3.2.4
3.2.4.1
Performing an RSX-llS V4.l System Generation
on an RSX-llM-PLUS Vl. 0 Host • • •
• • 3-2
NOTES TO THE RSX-llS SYSTEM GENERATION AND
3.3
INSTALLATION GUIDE • • • • •
• • • 3-3
3.3.l
Distribution Kits • • • • • • • • •
• • 3-3
Q-Bus Terminal Interfaces • • • • •
• • 3-3
3.3.2
3.3.3
Transferring Task Image Files Using FLX
• • 3-3
• • 3-4
3.3.4
SETT IM • • • • • • • • • • • • • • • • •
Building a Resident Subset FCS Library •
• 3-4
3.3.5
SYSGEN DIALOGUE FROM AN RSX-llM HOST • • • • • • • 3-4
3.4
3.4.1
Introduction • • • • • • • • • • • • • •
• • 3-4
Actual Dialogue -- RSX-llS System Generation on
3.4.2
an RSX-llM Host
• • • • • • •
• 3-7
3.5
SYSGEN ON A RSX-llM-PLUS HOST SYSTEM • • • • • • 3-24
3.6
SYSGEN ON A VAX/VMS HOST SYSTEM
3-24

PREFACE

MANUAL OBJECTIVES
This manual summarizes the new software features for RSX-llM Version
4.1, RSX-llS Version 4.1, and RMS-11 Version 2.0. It also includes
information on problems and restrictions applicable to the new
software and incompatibilities with the previous version. Therefore,
it is important to read this document before generating and using your
system.

INTENDED AUDIENCE
The RSX-llM/RMS-11/RSX-llS Release Notes are intended for all users of
the RSX-llM or RSX-llS operating systems.

STRUCTURE OF THE DOCUMENT
CHAPTER 1

RSX-llM VERSION 4.1 RELEASE NOTES

Section 1.1

New Features RSX-llM V4.l
Describes briefly the major
V4.l

Section 1.2

new

features

RSX-llM

Summary of Technical Changes
Provides brief summaries of the new software features
and refers you to the appropriate manuals in the
documentation set for complete
information.
Any
changes made to the documentation since V4.0 including
new, revised, or updated manuals, are also indicated.

Section 1.3

Notes on Software
Describes the incompatibilities between the previous
and
the
new
versions of RSX-llM, and provides
additional miscellaneous information pertinent to the
successful performance of the software.

Section 1.4

Reporting Problems and Errors
Provides information on reporting any problems you
encountered
with the new software, and describes
procedures for applying corrections to files on the
source disk.

vii

PREFACE
Section 1.5

Notes to RSX-llM V4.l Documentation
Describes errors and omissions in the RSX-llM V4.l
documentation and refers you to the appropriate places
in the documentation to make corrections.

CHAPTER 2
Section 2.1

RMS-11 VERSION 2.0 RELEASE NOTES
New Features for RMS-11 Version 2.0
Briefly describes the
RMS-11 Version 2.0.

Section 2.2

major

new

functionality

for

Summaries of Technical Changes
Provides brief summaries of the new software features
and refers you to the appropriate manuals in the
documentation set for complete information.
Changes
made to the documentation since RMS-11 Version 1.8,
including new and revised manuals, are also included.

Section 2.3

Comparisons with RMS-11 Version 1.8
Describes differences between Version 1.8 and Version
2.0 of RMS-11, including new features and restrictions
in the use of RMS-11.

Section 2.4

Miscellaneous Information
Contains general
restrictions.

Section 2.5

notes

new

RMS-11

features

Problems Fixed with RMS-11 Version 2.0
Lists problems reported for Version 1.8 that are
for Version 2.0.

Section 2.6

and

fixed

Known Problems with RMS-11 Version 2.0
Notes problems that may occur with the use of RMS-11.

Section 2.7

RMS-11 Files and Placement on the Distribution Kit
Lists the files contained in
distribution kit.

Section 2.8

the

RMS-ii

Version

2.0

install

RMS-11

and

any

problems

you

features

RMS-11 Version 2.0 Installation
Provides information required to
configure the RMS-11 utilities.

Section 2.9

Reporting Problems and Errors
Provides information on reporting
encountered with the new software.

CHAPTER 3

RSX-llS VERSION 4.1 RELEASE NOTES

Section 3.1

New Features for RSX-115 V4.l
Describes briefly the major
V4.l.

viii

new

RSX-llS

PREFACE
Section 3.2

Notes on Software
Describes the incompatibilities between the previous
AoC!
i:i1.L
and
the
n~w
versions of RSX=llS, and """'""1::r.;
additional miscellaneous information pertinent to the
successful performance of the software.
V Y ........... .._._,

Section 3.3

Notes to the RSX-llS
Installation Guide

V4.l

System

and

Generation

Describes errors and omissions in the RSX-118 V4.l
System Generation and Installation Guide and refers you
to the appropriate places in the documentation to make
corrections.
Section 3.4

SYSGEN Dialogue from an RSX-llM Host
Contains an example of an RSX-llS
RSX-llM V4.l host system.

Section 3.5

V4.l

SYSGEN

SYSGEN on an RSX-llM-PLUS Host
Briefly describes how to perform an RSX-llS V4.l SYSGEN
on an RSX-llM-PLUS host system.

Section 3.6

SYSGEN on a VAX/VMS Host
Briefly describes how to perform an RSX-llS V4.l SYSGEN
on a VAX/VMS host system.

CHAPTER 1
RSX-11M VERSION 4.1 RELEASE NOTES

CHAPTER l

RSX-llM V4.l RELEASE NOTES

1.1

NEW FEATURES FOR RSX-llM V4.l

RSX-llM Version 4.1 software is an update of the disk-based RSX-llM
operating system.
The major new features for RSX-llM V4.l include the
following:
•

Software Performance Monitor support

•

Support for Micro/PDP-11

•

New device support

•

Multivolume backups for disks

•

RMS-11 Version 2.0

RSX-llM Executive

1.1.1

The following items are changes to the RSX-llM V4.l Executive:
•

Some Executive routines have been moved out of the ERROR
module and into an Executive Common. This change only affects
systems with both error logging support and Executive Common
support. See Section 1.3.8 for more information.

Software Performance
Monitor
hooks
are
(SPM-llM}
• The
integrated
into the RSX-llM V4 .1 Executive. As a result, you
do not need to perform another SYSGEN to install SPM-llM.
The RSX-UM V4.l Executive no longer
• device
with IQ.X functionality.

supports

attaching

SYSGEN Features

1.1.2

The following SYSGEN features are new for V4.l:
•

RSX-llM SYSGEN must be done on a mapped host system.

•

To do a SYSGEN, you must have a host system with at least
words of memory.

•

A mapped target system is now the default target system.

•

A new question asks whether you want RT-11 emulation support.

1-1

64K

RSX-llM V4.l RELEASE NOTES
•

Devices with the mnemonic DU are now valid crash devices.
with
all
devices,
crash
support
is
restricted
removable-media devices.

•

A new question asks whether you want Software Performance
Monitor
(SPM-llM)
support. SPM-llM, which must be purchased
separately, provides data on system usage. This question is
always asked {even if you choose the Standard Function
System). If you answer yes, the SPM-11 hook points are
included in the system.
You can then install the separate
SPM-llM layered product.

•

Micro/PDP-11
processors.

•

RSX-llM V4.l distribution kits are now in BRU format.

•

RSX-llM is no longer distributed on RK05s.

•

The stand-alone DSC system (DSC64K) and the stand-alone BAD
system (BADSYS) have been removed from the distribution kits.

•

RSX-llM V4.l SYSGEN now supports all the new devices listed in
Section 1.2.5.

1.1.3

has

been

added

the

list

As
to

supported

Backup and Restore (BRU)

BRU has three new features for RSX-llM V4.l: multivolume backups
disks, a new sort algorithm, and additional device support.
Section 1.2.4.1 for additional information.

1.1.4

for
See

MCR and VMR

RSX-llM now allows you to set the round-robin scheduling interval
priority using either MCR or VMR.

and

RSX-llM now allows you to set the interval length and priority range
for Executive swapping.
See Section 1.2.2 (MCR) and Section 1.2.7.1
(VMR) for more information.
MCR supports all the new devices listed in Section 1.2.5.

1.1.5

Task Builder (TKB)

The following is an abbreviated description of
the Task Builder for RSX-llM V4.l:

the

functionality

•

The Autoload entry point has been modified. This entry point
is now accessed by an indirect reference through the Overlay
Run-Time System's impure area rather th·an by direct references
in the Autoload vector.

•

The Symbol Table File (.STB) now contains two forms of symbol
definition.
To
maintain
backward
compatibility,
all
autoloadable symbols are entries in the
global
symbol
directory and the vector itself is defined in associated text
records.
Additionally, a new internal symbol
directory
record, which is TKB-generated, supports selective inclusion

1-2

RSX-llM V4.l RELEASE ROTES
of autoloadable symbols for conventional tasks as well as the
information needed to generate autoload vectors for I- and
D-space tasks in RSX-llM-PLUS systems.
•

Autoload vectors supplied by the symbol table (.STB) files of
resident libraries are now selectively included in the user's
task image. Previously, all autoload vectors resulting from
autoloadable symbols· were present in the task image. Now,
only referenced symbols result in autoload vectors that are
present in the task image.

•

Libraries created with older versions of TKB do not have the
!SD records in the .STB file that newer versions of TKB use to
create autoload vectors. Therefore, TKB must include vectors
from the ~STB file for every entry point in the library.

•

The rules concerning cluster libraries have changed so that
the first library of the cluster, the default library, can now
have a non-null root.

•

The following option is new in TKB:
DSPPAT

•

The following switch is new in TKB:
/EL

1.1.6

Allows object-level patching of a conventional task or
the D-space part of an I- and D-space task.

Specifies the maximum possible size for the library
according to the size specified in the PAR option.
The switch specifies a larger library virtual address
range than is actually present in the library to allow
RMS to map its vectored library segments.

New Device Support

RSX-llM V4.l supports a number of new devices.
a complete list.

1.1.7

See Section 1.2.S

for

Support for the LASO, LAlOO, and LNOl Printers

Support has been added to RSX-llM/M-PLUS for the LASO, LAlOO, and LNOl
printers.
These printers are capable of printing either 132 or 80
columns on 8 1/2 inch wide paper.
You can select support for these printers while performing SYSGEN.
During SYSGEN, this support is a task-build option for the queue
manager (QMG} and the line printer processor {LPP), and it is the
default.
In order to use an LASO, LAlOO, or LNOl printer, you set the printer
type when you initialize the print processor by using a form type in
the command line. The valid form types are as follows:
Form types
12S.
126.
127.

Printer type
LASO
LAlOO
LNOl

1-3

RSX-llM V4.l RELEASE ROTES
For example, if you have a LASO printer connected to terminal line
TT6:, you use the following command to initialize the print processor.
(MCR)

QUE TT6:/SP/FO:l2S./FL:l/LOWER

(DCL)

INITIALIZE/PROCESSOR TT6:/FORMS:l2S/FLAG:l/LOWER

When you wish to print a file, select your desired printer mode
including one of the following form types in the command line:
Form types

Printer mode
132-column, draft quality. Also
landscape mode for LNOl.
80-column, letter quality. Also portrait
mode for LNOl.
132-column, letter quality. Also
landscape mode for LNOl.
80-column, draft quality. Also portrait
mode for LNOl.

3.
4.

s.
6.

For example, to print the 132-column draft quality TEST.LST file (that
is, a normal listing file) and the 80-column letter quality TEST.TXT
file on an LASO, use the following commands. Note that these commands
assume that you have assigned the default print queue, PRINT, to the
processor handling the LASO.
(MCR)

PRI /F0:3.=TEST.LST
PRI /F0:4.=TEST.TXT

(DCL)

PRINT/FORM:3 TEST.LST
PRINT/FORM:4 TEST.TXT
Modifying or Removing Support for the Printers

The printer options are controlled by task-build parameters in the
build files for the queue manager and the line printer processor.
These
build
files
are,
respectively,
[l,20]QMGBLD.BLD
and
[l,20]LPPBLD.BLD on the distribution kits. You can modify these prior
to building the queue manager and the line printer processor during
SYSGEN. You can modify these files for the following reasons:
1.

You can change the form types that are used to represent
printer types.
To do so, moa1ry the GBLDEF options that
define the symbols Q$LSPS and Q$HSPS. The comments in the
build files explain the values of the symbols. The normal
defaults are 12S. through 127.

You can change the form types that are used to represent
document types.
To do so, modify the GBLDEF options that
define the symbols Q$LSPF and Q$HSPF. The comments in the
build files explain the value of the symbols. The normal
defaults are 3. through 6.
If you modify the range of form
types, you must change the GBLPAT options that define the
forms to include offsets appropriate for the new form types.
(See
the comments in the command file regarding form
definition.)

You can remove the support for these printers altogether.
This may be necessary if you do not have any of these
printers and if you use form types in the range 3.
through
or 12S.
through 127.
In order to remove the support,
6.
set the values of Q$LSPS and Q$LSPF to 1 and the values Of
................ ,.._ ....
,.... ""T,.,...
\lvni:>l"'r and \J.;;>Oi:>t'i:> to o.
You may Cl.J.:SO wish to remove the four
GBLPAT definitions for the form types 3.
through 6.
T"lrio'r.t

1-4

RSX-llM V4.l RELEASE NOTES
Note to LAlOO Users
If you have a LAlOO printer and you use
it for standard 132-column, 14 1/2 inch
paper, you probably
will
want
to
establish it as your standard printer
--with form type 0--and not use this
support.
This
support is intended
primarily for applications including all
three printers and involving 8 1/2 inch
wide forms.

Files-11 ACP

1.1.8

Two new features have been added to Files-11 (FllACP)
to support RMS-11 V2.0:
•

in RSX-llM

V4.l

FllACP supports new file attribute codes {creation, rev1s1on,
expiration, and backup dates), which read and write the data
in the file header using a 64-bit date format.
FllACP
performs a computation to convert the date between 64-bit
binary and ASCII form.

FllACP also supports the $SEARCH function of RMS-11 V2.0 by
• providing
character wildcarding assistance.
This support
substantially reduces processing
filename include wildcards.

Because of these features, you cannot use RMS-11 V2.0 on a version
RSX-llM prior to V4.l.

1.1.9

time

when

portions

PDP-11 PASCAL/RSX

RSX-llM V4.l includes DCL support for PDP-11 PASCAL.
Note however,
that PDP-11 PASCAL is scheduled to be released at a date later than
that of RSX-llM V4.l. Therefore, until PDP-11 PASCAL/RSX is available
on your system, the use of the PASCAL command will result in the
informational message nPASCAL -- Sorry task not installed."
RSX-llM V4.l lists PASCAL as one of the available HELP topics.
However, until PDP-11 PASCAL/RSX is released and becomes available on
your system, typing nHELP PASCAL" will result in
the
message
"PASCAL currently is unavailable on your system." PASCAL commands will
be documented in the PASCAL User's Guide, distributed at the time of
the PDP-11 PASCAL/RSX release.
Complete HELP files for PDP-11
PASCAL/RSX will be provided with the PASCAL distribution kit at the
time of its release.

1.2

SUMMARY OF TECHNICAL CHANGES

The following sections list the new features for RSX-llM as described
in your documentation. A summary of technical changes also appears in
the preface of each manual.
The title of each manual is followed by a letter indicating
the manual is a NEW (N), REVISED (R) , or UPDATED (U) version.

1-5

whether

RSX-llM V4.1 RELEASE ROTES
1.2.1

RSX-llM System Generation and Installation Guide (R)

The following new options and features have been added to the
system generation and installation procedure:

RSX-llM

•

SYSGEN must be performed on a mapped host system with at least
G4K words of memory.

•

SYSGEN no longer supports the RKOS distribution kit.

SYSGEN now supports SPM-llM.

•

SYSGEN now supports RAGO removable media and RA81 fixed
under the UDASO hardware controller.

•

SYSGEN now supports RC2sl fixed/removable media.

• ·sYSGEN now supports RDSl fixed media and RXSO
drives under the RQDXl hardware controller.

media

floppy

disk

•

SYSGEN now supports TSVOS and TUSO magnetic tape drives
the TSll hardware controller.

under

•

SYSGEN now supports the LNOl, LP07, LP2G,
printers under the LPll hardware controller.

line

•

SYSGEN now supports the DHVll hardware controller.

•

The distribution kits
system.

•

The default for the target system configuration is now mapped.

•

SYSGEN will always install the V4.l TKB from the
kit with the task name ••• TKL.

•

SYSGEN now allows DU devices (RAGO, RC25, and RXSO only) to be
chosen as the crash dump device.

•

In an RLOl/02 PREPGEN, the EXCPRV disk is mounted by SYSGEN.

•

The RSX-llM magnetic tape distribution kits are now in BRU
format.
Also, BRU is now used to copy all the RSX-llM V4.l
distribution kits.

•

RMS-11 V2.0 is now included in the RSX-llM
kit.

1.2.2

no-w

only

contain

and

LP27

mapped

V4.l

baseline

distribution

RSX-llM/M-PLUS MCR Operations Manual (U)

The following are new MCR features for RSX-llM V4.l:
•

MCR commands now support the following new
RA81, RC25, RXSO, RDSl, TSVOS, and TUSO.

•

The following MCR SET keywords have been modified:

1. There are a number of

devices:

RA60,

references in the RSX-llM/M-PLUS manuals,
including these Release Notes, to the RC25 device. This device is, as
of the first publication date of the manuals, not available for sale
or distribution; nor is its mention in the documents a commitment by
DIGITAL to sell or distribute this device.
1-G

RSX-llM V4.l RELEASE NOTES
/RNDC - Defines the length
scheduling interval.

the

Executive

round-robin

/RNDH - Defines the hiahest
priority
that
considered for Executive-round-robin scheduling.

will

/RNDL - Defines the lowest priority that will be considered
for Executive round-robin scheduling.
/SWPC - Defines the length of a single
interval.
/SWPR - Defines
swapping.

new

Executive

range

priority

for

swapping
Executive

The /REMOTE and /SPEED keywords now support new terminal
speeds and speed combinations for the DHVll multiplexer.
The new speeds are 75, 110, 134.5, 150, 300, 600, 1200,
1800, 2000, 2400, 4800, 9600, and 19200.
The /TERM keyword now supports the LASO.
information,
see
Section
1.5.1
RSX-llM/RMS-11/RSX-llS Release Notes.
•

The following
command:

error

message

new

the

This message means that an attempt
terminal (TTn:) to a null device.

was

made

For
of
MCR

more
the

REDIRECT

TT redirect error

1.2.3

redirect

RSX-llM/M-PLUS Command Language Manual (R)

This revision of the RSX-llM-PLUS Command Language Manual incorporates
changes and additions listed in the following sections.

1.2.3.1 COBOL-81 - The following lists
modifications to DCL COBOL-81 commands:

the

new

features

and

•

COBOL-81, rather than COBOL-11, is now the default compiler.

•

COBOL-Cl! invokes the current COBOL-11 compiler to perform the
compilation.

•

COBOL[/C81] invokes
compilation.

the

COBOL-81

compiler

perform

the

DCL command line for COBOL-81:
COBOL[/C81]

[/qualifier[s]

filespec [/qualifier[s]]

The DCL qualifiers and their MCR translation follow.
the default.
DCL Qualifier
/OBJECT [=file]
/NOOBJECT

A (D)

indicates

MCR Syntax
COBOL file,[list] ,[diag]=source
COBOL ,. [list] , [ diag] =source

(D)

Specifies whether an object file is created.

1-7

RSX-llM V4.l RELEASE NOTES
/LIST[=file]
/NOLIST (D)

COBOL [obj] ,file,[diag]=source
COBOL [obj] ,,[diag]=source

Specifies whether a compile listing is created.
/DIAGNOSTICS[=file]
/NODIAGNOSTICS (D)

COBOL [obj], [list] ,file=source
COBOL [obj] ,[list]=source

Specifies whether a diagnostics file is created.
/BLD
/-BLD

/OVERLAY DESCRIPTION
/NOOVERLAY_DESCRIPTION (D)

Specifies whether an indirect command file
(.CMD)
and an
Overlay Descriptor Language (.ODL) file are produced. If you
use the LINK/C81 command to task-build a program, do not use
this qualifier.
LINK/C81 also produces a .CMD and an .ODL
file.
/CODE:CIS
/CODE:NOCIS (D)

/CIS
/-CIS

Specifies whether the compiler should use CIS
the object code it produces.

instructions

Specifies whether cross-reference tables should be appended
the compile listing.

/CRF
/-CRF

/CROSS REFERENCE
/NOCROSS_REFERENCE (D)

/ANSI FORMAT
/NOANSI_FORMAT (D)

/CVF
/-CVF

Indicates whether the source program is
format or DIGITAL's terminal format.
/DEBUG
/NODEBUG (D)

conventional

ANSI

/DEB
/-DEB

Specifies whether the symbolic debugger is used.
If this
qualifier is used, the LINK/C81/DEBUG command must also be used
to link the file.
/SHOW
/SHOW:MAP
/SHOW:NOMAP (D)
/NOSH OW

/MAP
/MAP
/-MAP
/-MAP

Indicates whether the Data Division and Procedure
offset maps are to be included in the list file.
/TRUNCATE
/NOTRUNCATE (D)

Division

/TRU
/-TRU

Indicates whether the compiler is to perform decimal truncation
nn

...,..

~l-t.o

'-.&."'-"

.,,~1 n.o1!~~'1o1c_..

" ....... u~.;i

,...,&

V.&.

,...n.un
\,,V&-lr

...:1~1-'!!!JI.

UQ \.Q

.; +.A. ..... _
.L \..1;'1\1.::;,.

1-8

RSX-llM V4.l RELEASE NOTES
/PER/BOU
/-PER/- BOU
/PER/BOU
/-PER/-BOU
/BOU
/-BOU
/PER
/-PER

/CHECK
/NOCHECK (D)
/CHECK:ALL
/CHECK:NONE
/CHECK:BOUNDS
/CHECK:NOBOUNDS
/CHECK:PERFORM
/CHECK:NOPERFORM

Deals with run-time error checking. /CHECK enables subscript
(index)
range checking and nested PERFORM checking. /NOCHECK
suppresses both of these. /CHECK:NOPERFORM and /CHECK:NOBOUNDS
suppress each check individually.
/KER:aa

/NAMES:aa

Tells the compiler to use the two alphanumeric
specified as the PSECT kernel for this program.

characters

/INF
/-INF
/INF
/-INF

/WARNINGS (D)
/NOWARNINGS
/WARNINGS:INFORMATIONAL
/WARNINGS:NOINFORMATIONAL

Specifies whether the compiler should
diagnostics during the compilation.
/SKELETON (D)
/NOSKELETON

issue

informational

<no translation>
/-SKL

Specifies whether a skeleton
( .SKL) file is created.

Overlay

Description

Language

/SUB
<no translation>

/SUBPROGRAM
/NOSUBPROGRAM (D)

Indicates whether this program is a subprogram.
/TMP:device

/TEMPORARY:device

Tells the compiler to store its temporary
specified device.

work

files

the

1.2.3.2 LINK/CS! Command - The LINK/C81 command links COBOL-81 object
files to produce a task image.
The command will not work with
versions of COBOL-81 prior to V4.0.
DCL LINK/CS! command line:
LINK/C81[/qualifier{s)]

[filespec(,s)]

LINK/COBOL [/qualifier { s)]

[ f i lespec (, s)]

The new DCL qualifiers for this command follow.

1-9

RSX-llM V4.l RELEASE NOTES
/[NO]FMS
/FMS:NORESIDENT
The /FMS qualifier causes LINK/C81 to include Forms Management
Services (FMS) library support in your task image. You must use
this qualifier if you call FMS routines in your program.
/NOFMS
tells LI~K/81 not to include FMS support. This is the default.
The /FMS:NORESIDENT qualifier causes LINK/C81 to include support
for a non-memory-resident FMS library in your task image.
/OTS: [NO] RESIDENT
The /OTS:RESIDENT qualifier includes memory-resident OTS in
task image.

your

/RMS:[NO]RESIDENT
/NORMS:NORESIDENT
The /RMS:RESIDENT qualifier creates a reference to the shared
RMS-11 memory-resident library, RMSRES. This library includes
input and output support for sequential, indexed, and relative
file organizations.
/[NO]MAP
The /MAP qualifier causes LINK/C81 to produce a Task Builder
file with the file type .MAP. /NOMAP is the default.

map

/[NO]DEBUG
The /DEBUG qualifier tells LINK/C81 to include the COBOL-81
Symbolic Debugger in your task image. You must have assembled
the object module with the /DEBUG switch.
/NODEBUG is the
default.
You must have assembl~d the object module with the
/DEBUG switch.

1.2.3.3 CORAL 66 - RSX-llM systems support CORAL 66, a high-level
block-structured programming language.
Following is the format and
descriptions of the qualifiers available with CORAL 66.
Format:
CORAL[/qualifier] filespec[s]
Command qualifiers:
/[NO]CHECK
The /CHECK qualifier specifies that the code generated will
check
that
all subscripts used in array and switch
references are within bounds. The /NOCHECK qualifier is the
default.
/CODE:arg
EIS
FIS
FPP
PIC
The /CODE qualifier allows you to choose (at compile time)
the instruction set for which the code is to be generated
regardless of which machine is used to compiie the source
program.
1-10

RSX-llM V4.l RELEASE NOTES
/[NO]EXTEND_SOURCE
The /NOEXTEND SOURCE qualifier causes the compiler
to
process the first 72 characters of source input per line~
causes
all
The default is the /EXTEND SOURCE
which
characters in an input line to-be processed.
/[NO]LIST
The /LIST qualifier allows you to specify whether a compiler
listing should be generated.
The default is the /NOLIST
qualifier which causes no compiler listing to be generated.
/[NO]MACHINE_CODE
The /MACHINE CODE qualifier specifies that you want the
compiler listing to include a representation of the machine
code generated.
The default
is
the
/NOMACHINE_CODE
qualifier.
/NAMES:x
The /NAMES qualifier causes the
first
character
of
compiler-generated program-section names to be the character
'x', in order to make them unique for this compilation.
/[NO]OBJECT[:filespec]
The /OBJECT qualifier allows you to specify whether or not
the compiler must generate an object module. The default is
the /OBJECT qualifier, which generates an object file.
/[NO] OPTIMIZE [ [:LEVEL] : n]
/OPTIMIZE=n
The /OPTIMIZE qualifier allows you to optimize the
of CORAL 66 source programs.

function

/READ ONLY [:a rg]
ALL
NONE
PURE DATA
The /READ ONLY qualifier allows you to alter the
or READ-WRITE attributes of program sections.

READ-ONLY

/[NO]SHOW[:arg[,s]]
ALL
EXPANSION
NONE
OVERRIDE
SOURCE
STATISTICS
SYMBOLS
The /SHOW and /NOSHOW qualifiers specify elements
included in or excluded from the listing file.

you

want

/[NO]STANDARD
The /STANDARD qualifier highlights non-IECCA keywords in the
listing as warning messages. The default is the /NOSTANDARD
qualifier, which suppresses this function.

1-11

RSX-llM V4.l RELEASE NOTES
/TEST[:n]
The /TEST qualifier allows you
to
retain
or
omit
declarations and statements from a particular compilation
without editing the source text.
/[NO]TRACEBACK
The /TRACEBACK qualifier generates additional code to print
source-file and line-number information in run-time error
messages.
The /NOTRACEBACK qualifier
suppresses
this
function and is the default.
/WIDTH:n
The /WIDTH:n qualifier allows you to set the listing file to
a specific width in the decimal range 8 through 132. The
/WIDTH:l32 qualifier is the default.

1.2.3.4 BASIC-PLUS-2 - BASIC-PLUS-2 is
now
the
default
BASIC
compiler.
The compiler can create Task Builder Command and Overlay
Descriptor Language files and a listing file in addition to the object
module file for the program it compiles.
(Note that BASIC/Bll runs
BASIC-11.)

1.2.3.5 FORTRAN-77 - FORTRAN
IV-PLUS
has
been
superseded
by
FORTRAN-77, although both compilers are supported by DCL (as well as
FORTRAN-IV). Qualifiers added for FORTRAN-77 are as follows:
/[NO]STANDARD:arg
ALL
NONE
SOURCE
SYNTAX
Directs the compiler to look in your source code for
to ANSI standard FORTRAN at the full language level.

extensions

i.2.3.6 BACKUP Command - Two new qualifiers have been added to the
BACKUP command and several qualifiers have new functions because of
multivolume disk backup and restore operations. They are as follows:

/APPEND
Appends new data to a tape or disk that
more backup sets.

•

already

has

one

/DIRECTORY
Directs BACKUP to create UFDs (if they do not already exist)
on a mounted output volume, then copy into the UFDs the files
from the same UFD on the input volume.

•

/IMAGE:arg
SAVE
RESTORE
Specifies that you want to
backup or restore operation.

1-12

multivolume

disk-to-disk

RSX-llM V4.l RELEASE NOTES
•

/SAVE_SET
Specifies the name of the backup set to be placed on tape or
a1sK.
For tapes and unmounted disks, the default name is the
volume name for the disk being backed up. For mounted input
or output disks during an image backup or restore operation,
you can specify the full backup set name with SAVE SET.

1.2.3.7 SHOW
command line
follows:

Processortype Command - The DCL SHOW
processortype
has been modified so that you issue the command line as

SHOW processortype processornarne[/qualifier]
BATCH
CARDREADER
DEVICE
INPUT
PRINTER
PROCESSOR
The SHOW processortype command displays information about processors,
card readers, batch processors, and other devices under the control of
the Queue Manager.
CARDREADER and INPUT are synonyns.
DEVICE refers to all nonbatch
output processors and is a synonym for PRINTER. BATCH refers to all
batch processors.
(Batch
processing
is
available
only
on
RSX-llM-PLUS.)
A simple SHOW PROCESSOR command displays all processors in the system.

1.2.3.8 Miscellaneous
Items - The
modifications to DCL for RSX-llM V4.l:

lists

following

•

EDT is now the default editor.

•

The following qualifiers have been modified:

various

/CHECKPOINT_FILE and /WIDTH
These qualifiers when used
decimal numbers by default.

1.2.4

with

SET

DEVICE

now

The /HFILL and /VFILL qualifiers for the SET TERMINAL and SHOW
TERMINAL commands have been eliminated. However, the existing
/CRFILL and /LFFILL qualifiers perform the same functions,
respectively, as the two removed qualifiers.

•

The INITIALIZE/QUEUE command has a new qualifier, /NOWARNINGS.
This qualifier inhibits error messages.

RSX-llM/M-PLUS Utilities Manual (U)

Following are the additions and changes for the Backup
Utility (BRU) and the Task/Image Patch Program (ZAP).

1-13

and

Restore

RSX-llM V4.l RELEASE NOTES
1.2.4.1 Backup and Restore Utility (BRU)
has three new features:
•

(R) - BRU for

RSX-llM

V4.l

BRU now does multivolume backups. You can copy a single disk
onto multiple smaller disks. However, when you do this, the
smaller disks are in BRU format, not Files-11.
This means
that before you can read what is on the smaller disk, you must
restore it with BRU. This process is similar to magnetic tape
backup and restore operations.
To backup and restore a single disk to multiple disks,
use the following new BRU switch:

you

BRU /IMAGE:SAVE
:RESTORE
Specifies that you want to do a multiple disk-to-disk
backup or restore operation.
If you are doing a backup
operation, you must specify the SAVE option on the command
line8
If you are doing a restore operation, you must
specify the RESTORE option on the command line.
Because of the addition of multivolume disk backups,
meanings of the following BRU qualifiers have changed.

the

/APPEND
Directs BRU to append a backup set from the input disk
volume to the last backup set on the output tape, or on the
output disk if you are using the /IMAGE qualifier.
/BACKUP_SET:name
Specifies the name of the backup set to be placed on tape
or disk.
For a mounted input or output disk during an
image backup or restore operation, you can specify the full
backup set file name with the /BACKUP_SET qualifier.
/DIRECTORY
Lists at your terminal the backup set names or files on the
specified tape or disk volume.
/INITIALIZE
Specifies that you want to initialize the output
during a tape-to-disk or disk-to-disk operation.

disk

/INVOLUME
Specifies the volume label of the input disk.
/MOUNTED
Allows you to back up files from a disk that is mounted
a Files-11 volume.

/NEW_VERSION
Resolves file specification conflicts that occur during
either backup or restore operations to a mounted disk.

1-14

RSX-llM V4.l RELEASE NOTES
/SUPERSEDE
Specifies that when file specifications on the mounted
output volume ace identical to the file specifications on
the input vol~me, the file on the output volume is deleted
and replaced with the file from the input volume.
•

BRU has a new sort algorithm, which increases the speed of the
sorting procedure.

•

In Version 4.1, if you use the /MOUNTED qualifier when the
input device is a
tape, BRU issues a syntax error message.
The purpose of this error message is to clarify to the user
that tapes cannot be mounted as Files-11 volumes.
Previously,

BRU ignored this qualifier if the user issued it

for

tape

input device.
•

New examples have been added to BRU.

They are as follows:

Disk-to-disk multivolume backup operations.
Disk-to-disk multivolume restore operations.
Disk-to-disk multivolume backup and append operation.
Disk-to-disk multivolume restore operation for restoring an
appended backup set.
and

•

New error messages for multivolume backup
operations have been added to the BRU chapter.

•

BRU now supports the following additional devices:

•

Mnemonic

Type

TSV05/TU80 magnetic tape

MLll electronic memory

RA60/RA81/RC25/RD51/RX50 disk

Changes have been added to bootstrapping stand-alone
RSX-llM.

restore

BRU

for

On RSX-llM, you can now find BRU64K.SYS and BRU64K.STB in
[1,51] on the following disk volumes:

UFO

BIG DISK KIT

- RSXM35

RK06/RK07 KIT - CLISRC
RL01/RL02 KIT - RLUTIL

1.2.4.2 Task/File Patch Program (ZAP) - A new section has been added
to Chapter 15
(ZAP) describing the use of the /LI qualifier with land D-space tasks and a new description of the /LI switch and
Multiuser Task Image files has been added.

1-15

RSX-llM V4.l RELEASE NOTES
1.2.5

RSX-llM/M-PLUS I/O Drivers Reference Manual (R)

The following new devices are supported by RSX-llM V4.1.
Supported terminal devices:
Mnemonic

Type
LQP02 letter quality printer

LASO personal printer

DHVll multiplexer

Supported disks:
Mnemonic

Type
RA81 fixed media disk

RA60 removable media disk

RC25 fixed media/removable cartridge disk

RD51 fixed media disk

RXSO floppy disk

Supported magnetic tapes:
Type

Mnemonic

TU80 magnetic tape

TSVOS magnetic tape

Supported line printers:
Type

Mnemonic

LNOl line printer

LP07 line printer

LP26 line printer

LP27 line printer

1.2.6

RSX-llM/M-PLUS Task Builder Manual (R)

Following are the major changes documented in the Task Builder manual:
•

New Switch
/EL -- Extend Library
This switch specifies the maximum possible size for the
library according to the size specified in the PAR option.
The switch specifies a larger library virtual address range
than is actuaiiy present in the library to allow RMS to map
its vectored library segments.
1-16

RSX-llM V4.l RELEASE NOTES
•

New Options
DSPPAT -- Allows object-level patching of a conventional
task or the D-space part of an I- and D-space task.

•

Changed Options
ABSPAT -- Allows object-level patching of a conventional
task or the I-space part of an I- and D-space task.

•

New Error Messages
Module module-name contains incompatible autoload vectors

•

Changed Error Messages
Original: Lookup failure resident

libr~ry

file

Revised: Lookup failure resident library file filename.ext
•

Miscellaneous Technical Changes
Autoload vectors for conventional tasks have changed.
The
call to $AUTO is now made indirectly through .NAUTO in the
overlay impure area.
You now can write an .ODL specification by applying certain
rules to the virtual address space diagram.
The overlay run-time system routines have changed size from
the previous release.
For versions of TKB that support I- and D-space tasks and
that were used to build libraries, TKB allocates autoload
vectors in the root of the task only for those autoloadable
entry points in the library referenced by the task.
Internal Symbol Directory Records, along
with
their
formats, are described in Appendix A of the RSX-llM/M-PLUS
Task Builder Manual. They consist of:
•

Type 1 records, generated by TKB and output to the
file

•

Type 2 records, generated by language processors

•

Type 3 records, created from type 2 records
to the .STB file.

•

Type 4 records,
modification.

written

the

.STB

and

output

file

without

A new bit called LD$TYP distinguishes between a library or
common. It is at the offset R$LFLG in the resident library
name block data in Appendix B of the manual.
The first library in a cluster may be overlaid and
a non-null root.
New Task Builder .reserved
Appendix E.

1-17

symbols

have

been

contain
added

RSX-llM V4.l RELEASE NOTES
The Fast Task Builder supports the /EA switch and the TASK=
option.
Other, minor technical
made.

1.2.7

and

editorial

changes

have

been

RSX-llM/M-PLUS System Management Guide (U)

The following are changes or additions to the System Management Guide:

1.2.7.1 Virtual Console Routine
following VMR SET keywords:

(VMR) - RSX-llM

length

supports

the

round-robin

•

/RNDC - Defines the
scheduling interval.

•

/RNDH - Defines the highest priority that will
for Executive round-robin scheduling.

considered

•

/RNDL - Defines the lowest priority that
for Executive round-robin scheduling.

will

considered

•

/SWPC - Defines the length
interval.

Executive

•

/SWPR - Defines a new priority range for Executive swapping.

•

/LASO=ttnn: - Establishes ttnn: as an LASO
(Note
support is not documented in the VMR chapter.)

the

now

Executive

single

swapping

that

The SAVE command supports the following new devices for saving
images: RXSO, RA60, RC25, TSVOS, and TU80.

this
system

The REDIRECT command has a new error message:
TT redirect error
The message means that an attempt was made to redirect terminal (TTn:)
to the null device.

1.2.8

RSX-llM/M-PLUS Error Logging Manual (R)

The following are changes or additions to Error Logging:
•

Error Logging now allows hard and soft limits to be reached
independently.
Previously, reaching one of the limits would
disable logging of either kind of error on that device.
Now,
reaching the soft limit will not affect the logging of hard
errors and vice versa.

•

Device timeouts are now logged as hard errors if unrecoverable
and as soft errors if recoverable.

generating
a
report,
RPT
looks
first
for
• When
LX: [l,6]ERRLOG.ULB. LX: is a new pseudo-device used by Error
Logging. If it fails
LB:[l,6]ERRLOG.ULB.

1-18

find

that

file,

looks

for

RSX-llM V4.l RELEASE NOTES
have been a number of minor changes in the Control File
• There
Language (CFL)
component of the Error Logging System. The
following lists the differences between CFL
and the previous releases.

RSX-llM

V4.l

%CNV$xxx functions:
The field_width parameter is now optional and interacts
with the optional fill character parameter to determine
whether the resulting strTng is simply printed as is or is
left- or right-justified.
In the earlier version, the
digits in the string were always right-justified and blank
filled if no fill character was specified.

%LOK$LENGTH function:
This function always returns the length of the data in a
packet or subpacket.
The length wo.rd for the packet or
subpacket is not considered part of the data and is not
counted in determining the length value returned.
%LOK$BYTE, %LOK$WORD, %LOK$LONGWORD functions:
The offset parameter is the offset within the data of the
packet/subpacket at which the byte, word, or longword
begins. The offset unit is always in bytes, with the first
byte of data in the packet/subpacket being offset o.
%STR$UPCASE function:
%STR$UPCASE accepts an ASCII string as a parameter, and
returns the ASCII string with all the lowercase ASCII
characters converted to uppercase.
DYNAMIC TABLE statement:
This new statement is a synonym for the FILE statement
should be used instead of FILE in any new code.

and

FILE statement:
The FILE statement will be removed in a future release.
You should replace any FILE statement presently in your
code with the DYNAMIC TABLE statement.
WRITE and WRITE GROUP statements:
Because of overlay restrictions, the following operators
and functions cannot be used in expressions in WRITE or
WRITE GROUP statements:
single and double operand numeric operators
the MATCH operator
%COD$xxx functions
%CTL$xxx functions
%PKT$xxx functions
%RPT$xxx functions
%STR$xxx functions
%TIM$xxx functions
%USR$xxx functions

1-19

RSX-llM V4.l RELEASE NOTES
•

The RSX-llM/M-PLUS Error Logging Manual has two new chapters.
Chapter 4, Error Logging Control
File
Architecture,
explains the control file modules in detail, including flow
of program control, interface between modules, and module
dispatching. A knowledgeable system programmer can use the
information here to add user-written modules to the Error
Logging System. The chapter includes extensively annotated
examples of DIGITAL-supplied modules.
Chapter 5, Control File Language Guide, describes the
Control File Language, which is used to write control-file
modules.

1.2.9

RSX-llM Mini-Reference (R)

This revision to the RSX-llM Mini-Reference consists of a new section
on RMS-11, as well as technical improvements to several other sections
of the manual.
The RMS-11 section includes both procedures for invoking the following
RMS-11 utilities, and summaries of their commands and keywords.

• RMSDES (RMS-11 File Design Utility)
• RMS I FL (RMS-11 Indexed File Load Utility)
• RMSCNV (RMS-11 File Conversion Utility}
• RMSDSP (RMS-11 File Display Utility}
• RMSBCK (RMS-11 File Back-Up Utility)
• RMSRST (RMS-11 File Restoration Utility)
In addition, the RMS-11 section lists the RMS-11 completion codes
fatal error codes.

and

The sections Executive Directives and I/O Error
updated to include new or corrected information.

been

1.3

Codes

have

NOTES ON SOFTWARE

The following sections describe the incompatibilities between RSX-llM
V4.l and previous versions, and provide miscellaneous information
pertinent to the successful use of the software.

1.3.1

Baseline Systems

The V4.l baseline system in [l,54], on the disk labeled RSXM35,
requires a minimum of 64K words. This is an increase of 36K words
over the minimum memory requirement for V4.0.

1-20

RSX-llM V4.l RELEASE NOTES
System Generation and Installation

1.3.2

The host machine for a
minimum requirements:

system

generation

must

meet

•

Must have at least 64K words of memory

•

Must be mapped and have a null device (NL:)

the

following

1.3.2.1 Performing an RSX-llM V4.l SYSGEN on a V3.2 System - If you
intend to perform an RSX-llM V4.l system generation while running
under a V3.2 system, you must do the following:
1.

Update several modules in the V3.2
(IND.OLB).

indirect

object

library

Rebuild big indirect (BIGIND).

Use the TKB and VMR tasks from the V4.l distribution kit when
performing the SYSGEN.

There is a concatenated object file, INDFIX.OBJ, in UFDs
[12,20]
and
[12,24]
of the RSX-llM V4.l distribution kit that simplifies the
updating of IND.OLB. This object file consists of the individual
updates to four indirect modules:
INDPRC, INDPAR, INDOPN, and INDSET.
The procedure for updating is as follows:
1.

Set the UIC to [1,20]
mapped system.

for an unmapped system or [1,24]

Copy INDFIX.OBJ to the disk that has the most recent
of V4.0 IND.OLB.

Issue the following command:

Assign the logical names TK (task image device) and MP
(map
device)
to their proper devices:
for example, ASN LB:=TK:
and ASN NL:=MP.

Task-build the big indirect task as follows:

Remove the current indirect

Install the newly created big indirect (INS $BIGIND).

Mount the V4.l baseline distribution kit
(RSXM35), and
install the TKB and VMR tasks from it. The tasks are in
[ 1, 54] •

If your system does not have extend task support, and there
is ample memory available, install the V4.l TKB with an
increment:
for example, /INC=20000.

10.

Use the V3.2 BIGMAC {or the V4.l MAC)
for the system
generation. As with TKB, installing BIGMAC with an increment
will speed up processing if your V3.2 system does not have
extend task support.

1-21

for

version

LBR IND/RP=INDFIX.

TKB @BIGINDBLD.

REM ••• AT.).

RSX-llM V4.l RELEASE NOTES
Once you have completed this sequence of steps, you are ready to
Ref er to the RSX-llM System
perform
an RSX-llM V4.l SYSGEN.
Generation and Management Guide for instructions on performing an
on-line SYSGEN.

1.3.2.2 Restriction to V4.l On-Line SYSGEN - When performing a V4.l
on-line SYSGEN, SYSGEN will always install the Task Builder supplied
on the distribution kit ( ••• TKL).
This restriction is due to changes made in TKB to generate a new
autoload vector format for overlaid tasks.
These changes are closely
coupled with the overlay run-time system found in SYSLIB and result in
incompatibility problems between the old TKB and SYSLIB. Therefore,
in order for SYSGEN to execute successfully, the tasks that SYSGEN
needs must be built with the V4.l TKB.

1.3.2.3 V4.0 Saved Answer Files - A
V4.0
saved
answer
file
(SYSSAVED.CMD) can be used when generating a V4.l system. These files
are now upward compatible.
However, two new SYSGEN
questions
regarding checkpointing and SPM-llM support will be asked.

1.3.2.4 Determining the Number of RKOS Units - Fixed platter RKOS
drives (RKOSF) are handled as two units. The first of each RKOSF pair
must be an even unit number;
for example, O and 1, 2 and 3. Be sure
to take this into account when calculating the number of RKOS units.

1.3.2.5 SYSGEN on RLOls or RL02s - .Due to the space limitations of
the RLOl and the RL02, you should not perform more than one SYSGEN on
the disk without first clearing some space on it. This clearing can
be accomplished by copying files to another media and then deleting
the unnecessary files.

1.3.3

User Account for the Warm-Up Session

The Introduction to RSX-llM and RSX-llM-PLUS includes a warm-up
session for new users. A number-cif files that are associated with the
warm-up session are included on the RSX-llM kits, along with a few
other files intended for the convenience of all users.
During the post-SYSGEN clean-up procedure, while extracting the HELP
files, you are asked if you wish to extract the INTRODUCTORY files.
If you answer Yes to this question, the command procedure will extract
a module from HELP.ULB called INTRO.ULB.
All the introductory and convenience files are contained in INTRO.ULB.
Extract the module called INTROF, using the following procedure:
MCR>LBR INTROFIL.CMD=INTRO.ULB/EX:INTROF
or
DCL>LIBRARY/EXTRACT INTRO.ULB INTROF

1-22

RSX-llM V4.l RELEASE NOTES
This module is an indirect command file called INTROFIL.CMD, which you
can run to extract all the other files by typing:

The procedure extracts 20
files,
including WHATSHERE.TXT, which
explains what all the other files are.
You can use these files in two
ways, depending on the number of new users you have coming on to your
system.
In UFD [200,l] on your target system disk are introductory files
used
with the warm-up session for new users presented in the Introduction
to RSX-llM and RSX-llM-PLUS and RSX-llM-PLUS manual. When new users
come onto the system,
the--system manager should have them use the
account with the UIC [200:1] and the account name USER which has been
supplied with the distribution kit.
New users can log in to this
account and follow through the entire warm-up session.
See Section
6.2.9 of the RSX-llM System Generation and Installation Guide and
pages 1-5 to 1-7 in the Introduction to RSX-llM and RSX-llM-PLUS.
Alternatively, the system manager can copy the introductory files to
the new user's own account, then instruct the new user to delete these
introductory files when he or she has finished with the warm-up
session.
Use the convenience files as you wish.
the list below.
*A.A;l
*WARN ING • TSK; 1
*SEVERE.TSK;l
DELETE.CMD;l
SHOW.CMD;l
STARS.MAC;!
TEXT.TXT;l
CLEAN.CMD;l
*TMCLI.MAC;l
*TMCLI.FTN;l

They are marked with

*SUCCESS.TSK;l
*ERROR.TSK;l
LOGIN.CMD;l
*CLOCK.MAC;!
*CLKGEN.CMD;l
FLY.TXT;l
FLY.TXT;2
*WHATSHERE.TXT;l
SHAVE.CMD;l
HIYA.MAC;l

For more information on extracting HELP files from RSX-llM kits, see
Chapter 6 of the RSX-llM System Generation and Installation Guide.

1.3.4

BRU64K Restriction

On an BRU64K stand-alone system,
you should not run BRU and BAD
simultaneously.
Because BRU and BAD use common buffer space, running
both tasks at the same time yields unpredictable results.

1.3.5

DSC64K, DSCSYS, and BADSYS

The DSC64K, DSCSYS, and BADSYS stand-alone systems have been removed
from the distribution kits.
These stand-alone systems are no longer
needed, as BRU64K is now used as the stand-alone system.

1.3.6

Power-Fail Recovery

A disk driver is called at its power-fail recovery entry point when

power-fail occurs.

This recovery routine gives a disk sufficient time

to spin back up and be ready to accept I/O requests.

1-23

RSX-llM V4.l RELEASE NOTES
There are three possible recovery procedures:
1.

If a device is busy prior to the power-fail and the requested
I/O has not completed, the routine times out and checks the
device status until the device is ready for I/O operations to
resume.

If a device is not busy prior to the power-fail and receives
an I/O request after the power-fail, the routine times out
and checks the device status until the device is ready for
I/O operations to resume.

If a device is not busy prior to the power-fail and there are
no pending I/O requests, operations resume with no special
handling by the recovery routine.

Note in the first two cases that, if the maximum time-out count is
reached before the disk spins back up and is ready, an unsuccessful
I/0 completion code is returned.

1.3.7

Change to Executive's Task Abort Code

The Executive's task abort code has been modified. If you install an
Ancillary Control Processor {ACP) task with post-mortem dump (PMD)
enabled and this task aborts, then the system will crash.
A crash
dump is produced, which shows the state of the I/O data structures at
the time the ACP task aborted. By default, most DIGITAL-supplied ACPs
are installed with PMD enable.

1.3.8

Restriction to Error Logging

By moving the Error Logging routines into the Executive Common, the
following restriction is introduced: If a driver of an error logging
device calls the $CRPKT 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
that APR is used to map the common. Any user-written driver that
performs such a function must allocate a piece of pool, fill in the
appropriate information, and pass the pool address to the create
packet routine.

1.3.9

TDX (Catch-All Task}

Support for TDX, the catch-all task, is provided with RSX-llM systems.
The primary purpose of the catch-all facility is to give you the means
to run uninstalled tasks.
Any task installed with the task name ••• CA.
is treated as a
catch-all task.
If the Monitor Console Routine (MCR) receives an
unrecognized command, it searches for a task with that name and passes
the command line to this task. To use TDX as the catch-all task for
your system, install it as follows:
>INS $TDX/TASK= ••• CA.

1-24

RSX-llM V4.l RELEASE NOTES
TDX checks the typed command against its list of commands.
If the
commands match, TDX translates the command into a legal MCR command.
These commands and their MCR translations are:

Command

Translation

Meaning

ATS

ACT /ALL

Display the names of
all active tasks in
the system.

ATS ttnn:

ACT /TERM=ttnn:

Display the names of
all active tasks on the
specified terminal.

CHD

SET /UIC

Display the current
default UIC for

terminal TI:.
CHD g m

SET /UIC=[g,m]

Clear the issuing
terminal's screen and
set cursor to O,O.
Returns exit status of
EX$SUC if terminal is
a CRT, and EX$WAR if
it is not.

CLR

CRE file

Change the default UFD
to the UFD specifiede

PIP file=TI:

Create a new file
without invoking an
editor.

CVT val

Evaluate an arithmetic
expression, convert
that expression into
different formats, and
display all the formats
on your terminal. CVT
accepts input in octal
(nnn or nn,nn) or
decimal (nnn. or
nn.,nn.) words or
bytes, hexadecimal
numbers ($nnnn),
radix-so (%ccc) or
ASCII ('c or "cc)
characters, or
arithmetic expressions
using+,-,/,* and<>.

DEL file(s)

PIP file(s)/DE

Delete the
specified file(s).

DIR [file{s)]

PIP [file{s)]/LI

Display a directory
listing at the
terminal.

DLG

DEV /LOG

Display information
about all the
logged-in terminals
on the system.

1-25

RSX-llM V4.l RELEASE NOTES
Command

Translation

Meaning

DLN

NCP SHOW KNOWN NODES

Display all known
DECnet nodes.

FRE

PIP /FR

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

FRE ddu:

PIP ddu:/FR

Display the same
information as FRE
for a specified device.

PUR file{s)

PIP f i1 e {s) /PU

Delete all but the
latest version of
a file.

SHQ

SHOW QUEUE ALL

Display information
about all entries in
all print queues.

SYS

SET /SYSUIC

Display the current
system UIC.
Display the current
version of TDX.

TDX
TYP file ( s}

PIP TI:=file(s)

Print files on your
terminal.

You may want to add other commands to TDX.by modifying the source
file in [24,lO]TDX.MAC.
The routines for the commands are at the
end of the source file and serve as examples for user-tailored
routines. To reassemble the source file after making additions, use
the TDXASM.CMD file located in (24,20]. To rebuild TDX, follow the
procedure in the Phase III section of the RSX-llM System Generation
and Installation Guide. TDX comes preassembled ([l,24]TDX.OBJ)
if
you de net wish to make any changes.
Location of files on multivol~~e kits
Distribution

TDX.MAC

TDX.OBJ, TDXBLD.BLD

RLOl/02
RK06/07
(all other}

HLPDCL
CLISRC
RSXM35

EXCPRV
RSXM35
RSXM35

If the user's typed command does not match any of TDX's commands,
TDX attempts to issue one of the following two MCR command options.
In the examples, XXX represents the first three characters of your
command.
The option TDX uses depends on whether the logical devices ZZl:
or
ZZ2:
exist on your system. You can assign one of these devices in
your LOGIN.CMD file. Note that the presence of the ZZl: assignment
masks the presence of the ZZ2: assignment. If no assignment is
made, TDX will not exercise either option.

1-26

RSX-llM V4.l RELEASE NOTES
1.
MCR> RUN $XXX/TASK=XXXTTN/CMD="params ••• "
This option installs, runs, and then removes a
task.
"Params ••• "
represents the command line that you enter.
Your command line cannot exceed 39 characters, because TDX
adds other characters to this line.
If you want this
option, place the following in your LOGIN.CMD file:
ASN SY:=ZZl:
2.

MCR>
MCR>
MCR>
MCR>

@SY:[loginuic]XXX.CMD or
@LB:[libuic]XXX.CMD or
@SY:[loqinuic]CATCHALL.CMD or
@LB:[libuic]CATCHALL.CMD

For this option, TDX searches for one of the @[ ••• ]XXX.CMD
indirect command files, in the order indicated. As soon as
TDX locates one of these files, the search stops. You can
design the indirect command file to perform a variety of
functions, such as installing tasks, providing HELP, or
issuing error messages.
If you want this
LOGIN.CMD file:

option,

place

the

following

sample

indirect

your

command

file,

ASN SY:=ZZ2:
RSX-llM V4.l contains
[24,24]CATCHALL.CMD.

The ZZn option may be controlled for all users
following command in the system startup file:

placing

the

ASN SY:=ZZn:/GBL
where n equals 1 or 2, depending upon which ZZn option you prefer.
TDX issues the following message if the user's command does
match a TDX command or if TDX cannot locate the necessary task.

not

MCR -- Task not in system
You may wish to install some tasks permanently, rather than invoking
TDX to install them on an as-needed basis.
It is advisable to
permanently install:
•

Tasks requiring a larger increment than the default (see the
INSTALL command in the RSX-llM/M-PLUS MCR Operations Manual)

•

Frequently used tasks

There are two cases, when noninstalled tasks are invoked by indirect
command files,
where TDX may affect the execution of the command
file:
•

If the command line's length exceeds 39 characters

•

In systems without Parent Offspring tasking, TDX has no
means of returning the exit status of called tasks to
Indirect. In this case, Indirect proceeds immediately to
the next command line without waiting for the called task to
finish. Tn1s has the same effect as preceding the command
line with .XQT.

1-27

RSX-llM V4.l RELEASE NOTES
1~3~10

Restriction for DCL as the Catch-All Task

If your command line interpreter is set to MCR and DCL is installed
as the catch-all task ( ••• CA.) I do not use the DCL INITIALIZE/UPDATE
command to modify your disk parameters.
When you enter this
command, MCR interprets the IN! portion of the command to mean
INITIALIZE VOLUME, and consequently destroys all existing files on
your disk. As alternatives, either use the MCR HOME command or set
your command
line
interpreter
to
DCL
before
using
the
INITIALIZE/UPDATE command.

1.3.11

Indirect Command Procedure Library

Users wishing to use the Indirect command procedure
library
INDSYS.CLB
(as documented in the RSX-llM/M-PLUS MCR Operations
Manual) must copy it from the MCR source volume directory to their
system volume.
On single disk distribution kits (RP04/5/6 or
copy the file as follows:

RM03,

for

exam.ple),

PIP LB:[l,2]=LB:[l2,10]INDSYS.CLB
On multidisk distribution kits (RLOl/02, for example), mount the MCR
source volume and copy the file as follows:
PIP LB:[l,2]=dd:[l2,10]INDSYS.CLB
The characters dd represent the drive on which the MCR source volume
has been mounted.
For the RK06/07 kit, the file is on CLISRC;
kit, the file is on MCRSRC.

for

the

RLOl/02

Following are descriptions of the three versions of
Command Processor that are supported in RSX-llM V4.l.

the

Indirect

1.3.12

and

Indirect Command Processor Support for V4.l

•

The first version is called ICP and contains the same
functional parameters as the IND task released in V4.0.
This version requires a 12K partition size and must be used
when you are doing a V4~1 SYSGEN.
ICP is the standard
Indirect created during the Phase II privileged task build.
There is no FCSRES version of this task.

•

The second version is called ICQ and is more heavily
overlaid in order to fit in an SK partition. This version
supports .the minimum of functional parameters necessary to
execute a command file that does not exceed the following:
1 concurrently open data file
1 parallel XQT directive
2 Direct Access Labels

1 GOSUB nesting level
2-level depth of open command files
108(decimal)-byte command file input buffer

1-28

RSX-llM V4.l RELEASE NOTES
ICQ is designed for systems that lack sufficient memory space
to support a 12K task.
ICQ's execution time is slower than
ICP's, and its symbol table space and functional parameters
are insufficient to complete a SYSGEN.
ICQ is built during
SYSGEN only if the target system contains less than 24K of
memory.
•

The third type of task is the resident FCS {FCSRES} version of
ICQ.
This task is also highly overlaid and is slower than
ICP;
however, this version has the same functional parameters
as ICP with approximately the same symbol table space as ICQ.
The task resides in an 8K partition and has the following
parameters:

4 concurrently open data files
16 parallel XQT directives
16 Direct Access Labels
8 GOSUB nesting levels
4-level depth of open command files
132(decimal)-byte command file input buffer
This version is designed for systems that lack sufficient memory
space to support a 12K task but still want to retain the full
capabilities of the ICP task. However, it does not contain enough
symbol table space to complete a full SYSGEN procedure, and it must
be built as a privileged task with FCSRES support using the SYSGEN3
procedure.

1.3.13

Task Builder Restrictions

The following two restrictions apply to the V4.l Task Builder.
•

You may experience problems if you use the V4.l Task Builder
(task version M40.10)
with a SYSLIB other than the one
supplied with V4.l. Changes and additions have been made to
the
overlay
run-time
system modules that make them
incompatible with previous versions of SYSLIB.OLB.

•

The first library in a cluster of libraries may or may not
be overlaid and may or may not have a null root. The
remaining libraries in the cluster must be overlaid with a
null
root. The first library in a cluster is the one named
first in the Task Builder cluster (CLSTR) option.
Severe performance degradation can occur with
cluster
libraries if you have one of the following two conditions in
your task:
1.

The first library is overlaid and has a null root.

The first library called by the task is
library specified in the CLSTR option.

1-29

not

the

first

RSX-llM V4.l RELEASE NOTES
If the first library in the CLSTR option is overlaid and has
a null root, the overlay run-time system cannot distinguish
the first library from the remaining libraries in the
cluster.
The Task Builder therefore assumes that the first
library called by the task is the first library; this first
library is the one that Task Builder consistently maps by
default. Therefore, although the preceding two conditions
do not cause errors, they may cause performance degradation
because of excessive mapping and unmapping of libraries in
the cluster.
To avoid this problem, the library first called by the task
should be the first library specified in the CLSTR option.

1.3.14

Modifications to System Library Task Builder Data Structures

Beginning with the V4.0 release, the Task Builder and the associated
overlay run-time system incorporate new overlay functionality and
modified data structures.
New modules are included in the system library to support cluster
libraries (see the RSX-llM/M-PLUS Task Builder Manual for a complete
description of this feature}. In order to m1n1m1ze the virtual
memory impact of the new features, some changes were made in the
older modules. The customer product that used the run-time routines
may not build correctly or may malfunction unless minor changes are
made. In particular, the following points are relevant:
•

The run-time routines reference the register save routine,
.SAVRl instead of .SAVRG. In some overlaid applications,
this routine may have been explicitly loaded in an overlay
(for example, as part of a tightly overlaid FCS-11). This
reference results in a "Multiply defined global" message
from
TKB.
The change is to remove explicit .SAVRl
references from overlay specifications in th~ .ODL file and
to let TKB place this module in the root with the overlay
run-time routines.

•

The linkages between the various overlay run-time modules
have been modified slightly to support the new library
mapping; therefore, users who have developed debugging
tools that "hook" themselves into the overlay system should
refer to a copy of the source microfiche or the source kits.

1.3.15

Transportability among 22-bit Systems

RSX-llM supports transportability among all 22-bit systems.
These
systems can differ as to whether the Executive handles NPR transfers
by performing memory management functions, or the hardware has its
own 22-bit physical memory addressing capabilities.
To make these systems transportable, you must boot your target
system on the processor selected at SYSGEN and then SAVe it. The
saved system will then be hardware bootable and transportable among
the different 22-bit systems.

1-30

RSX-llM V4.l RELEASE NOTES
1.3.16

Device Drivers and User Tasks

The addition of new and enhanced device support to RSX-llM V4.l

causa

problems for some user tasks in V4.l.

the device drivers and the procedures recommended for handling
problems are described as follows:
•

may

The characteristics of

The UDASO (DUDRV} dynamically updates the system
to reflect the characteristics of the disk.

data

such
base

Recommended action: User tasks should issue a QIO Attach
function before requesting the device's characteristics with
the GET LUN directive.
•

The TMllA/B device driver (MTDRV)
dynamically updates the
system data base to reflect the density characteristics of
TElO/TUlO.
Recommended action: User tasks should issue a QIO function
using
the
function codes for the powerfail recovery
procedure, as described in the RSX-llM/M-PLUS I/O Drivers
Reference Manual, before requesting the device's density
characteristics with the GET LUN directive.

•

The RX02 device driver
{DYDRV)
dynamically updates the
system data base to reflect the characteristics of the media
in the RX02 drive.
Recommended action: User tasks should issue a QIO Sense
Characteristics function ~efore requesting the device's
media characteristics with the GET LUN directive.

•

Users issuing QIOs directly to MSDRV must be
following:

aware

the

The completion of the IO.RWD request occurs when the MS:
device reaches BOT.

When the MS: device changes status from either off-line
to on-line or from on-line to off-line, the MS: device
inhibits further physical I/O operations. After such a
change, the user must issue either an IO.RWD or an
IO.SMC request that succeeds before I/O operations
resume.

MS:

read/write data transfer features are as follows:
The data buffer starting address must be
boundary.

word

The data transfer size can be an
count.

even

byte

odd

The user can swap the odd and even data bytes by
using the tape characteristic bit 1 of IO.SMO or
IO.STC requests. When bit 1 is set to O, no byte
swap occurs.
When bit 1 is set to 1, the byte swap
does occur.
If you use byte swapping, it
is
recommended that the data buffer size be an even byte
count.

1-31

RSX-llM V4.l RELEASE NOTES
1.3.17

Changes to Code and Data Structures for Privileged Tasks

The changes documented in this section were new for RSX-llM V4.0
rather than for V4.l. This information is included here because it
has not yet been incorporated into the documentation set.
Many of the changes made to RSX-llM Version 4.0 may affect the
upgrading of privileged tasks and drivers that were written for a
previous release.
The following sections describe the most significant changes to code
and data structures since the previous release.
Note that nonprivileged tasks should not be affected by any of these
changes.

1.3.17.1

Changes Made to Executive Code -

•

The module IOSUB.MAC has been divided into four modules:
IOSUB, EXESB, MEMAP, and MDSUB. The last three are new.

•

The Get Partition Parameters directive now returns the real
virtual starting address of a privileged task's task region
instead of O as it did in Version 3.2.

•

Many Executive routines have been moved into the Executive
commons
(if
Executive
common support was selected).
Therefore, it may not be possible for privileged code to
reference these routines as they may have done in a previous
release. To determine if an Executive entry point is in an
Executive common, consult RSXllM.MAP. The entry point is in
a common if its address falls between 120000 and 140000.
If the entry points are inaccessible to the task because
they reside in the Executive commons, a procedure for
accessing that routine is available.
A transfer routine
must be written by the user that will permanently reside in
the mapped Executive address space. See module DRSUB for
examples of transfer routines. Note that transfer routines
are already provided for
.the
most
commonly
called
subroutines now moved into the commons and their existence
is transparent to any task referencing them8

•

1.3.17.2
•

The RSXMC.MAC symbol P$$D70 which indicated cache memory
a 22-bit processor has been changed to C$$CHE.

Changes Made to Executive Data Structures The Task Control Block (TCB)
has undergone many changes.
present format can be found in an appendix of the
RSX-llM/M-PLUS Crash Dump Analyzer Reference Manual.
The
following offsets are new:

The

T.TIO

Buffered I/0 count (byte)

T.TKSZ

Initial task size (root)

T.EFLM

Event flag waitfor mask and mask address

T.HDLN

Task header length in 32 word blocks (byte)

T.GGF

Task group global event flag use count (byte)

1-32

RSX-llM V4.l RELEASE NOTES
•

To enhance asynchronous buffered I/O, the bit T2.TIO that
allowed for only one buffered I/O per task, has been changed
to the byte T.TIO. This byte allows a task to queue many
buffered I/O requests simultaneously~

•

The word at offset O.STAT+2 of the offspring control block is
now used to contain a secondary exit status, the TKTN abort
code, which is filled in whenever the offspring exits.
Previously, only the word at a.STAT was used. Note that more
words in the exit status region of the OCB may be used in the
future and therefore shouid be considered as reserved for
future expansion.

•

The addition of alternate CL! support has changed how CLis are
associated with individual users.
On systems that include
alternate CL! support, the word previously at offset U.CLI in
terminal UCBs,
(DV.TTY is set) has been redefined. On these
systems it is referred to as U.MUP, since it now contains a
bit mask for various multiuser features. Bits 1 - 4 in this
word are now used to identify the CLI associated with that
terminal.
The bits form an offset into a table located at
$CPTBL in the Executive module SYSCM. This module contains a
pointer to the CPB (CL! Parser Block) for the CL!. Since only
four bits are used to form this offset, the system is limited
to 16 CLis. The bit that is used for the NOBROADCAST feature
is also in this word, which is why this feature is only
available on systems supporting alternate CLis.

•

There are now two additional feature mask words. These words
are documented in an appendix of the RSX-llM/M-PLUS Crash Dump
Analyzer Reference Manual.
These words are accessed as
positive offsets from the original feature mask word, $FMASK.

1.3.17.3
•

Changes Made to I/O Data Structures The bit DV.MXD in offset u.cwl of the UCB (previously for
mixed MASSBUS) has been changed to DV.MSD. This bit is set
for all mass storage devices, and must be turned on for all
user-written drivers that want to support error logging. In
addition, error logging devices must have four
words
preceding each UCB (negative offsets).

bit DV.SWL in offset U.CWl of the UCB (previously
• The
unused)
is now used to maintain the software write-lock
status of the device.
•

1. 3 .18

Prior to V4.0, two words were added to the end of each DHll
UCB to contain the vector and CSR of an associated DMllBB.
In V4.0, these two words were eliminated.
The information
is now contained in fork block offsets in the SCB.

MACR0-11

The maximum number of relocatable terms in a complex expression has
been changed from the old maximum of 6 to 20. This change was made
by increasing the maximum size of the .OBJ record that MACR0-11
produces from 42(decimal) bytes to 128(decimal) bytes.

1-33

RSX-llM V4.l RELEASE NOTES
You cannot verify that code generation is correct by comparing .OBJ
files created by different versions of MACR0-11. The correct way to
verify code generation is to task-build the .OBJ files, then compare
the .TSK image files.
Because the .OBJ files produced by the new version of MACR0-11
differ from those of previous versions, you must recompute checksums
using the PAT utility for any object patches assembled with this
version of MACR0-11.
See the Release Notes at the end of the PDP-11 MACR0-11 Language
Reference Manual for documentation of the changes to MACR0-11.

1.3.19

Restriction for EDT Version 2.0

These restrictions apply to V2.0 of EDT, which is a layered
bundled on your RSX-llM V4.l distribution kit.

product

Before EDT can be run in keypad mode, your terminal must be set to
lowercase (SET /LOWER). If the terminal is not set lowercase, the
terminal driver converts the escape sequences sent by the keypad
keys into uppercase and EDT does not recognize them.
Also, if you type CTRL/C while EDT is writing the output file (that
is, after you type the EXIT command but before the CLI prompt
appears), EDT stops writing the output file.
No message is
displayed to indicate that your output file has been only partially
written.

1.3.20

Changes to the Command String Interpreter (CSI)

The Command String Interpreter (CSI) was rewritten for Version 4.0
of RSX-llM to incorporate new functionality. The IAS/RSX-11 I/O
Operations Reference Manual documents a list of changes to CSI.
Two additional changes are:
1.

.CSil no longer references the module ODCVT.

.CSI2 no longer
references OD2CT.

references

the

module

ODCVT

and

These changes are normally not visible to the user, but could
problem for some overlaid tasks.

1.3.21

now
be

Bootstrapping a DB-, DM-, or DR-Based System

The MCR BOOT command can loop indefinitely when it boots a system
from an RP04/05/06 or an RK06/07 or an RM03/05/80 or an RPO? if it
encounters an ECC correctable error when reading the system image.
The bootstrap driver is not large enough to include ECC logic.
Therefore, it retries the read operation, and never succeeds.
To recover from this error, use PIP to copy the system image to
another
area
on
the
disk
and retry the boot operation.
Alternatively, you can copy the entire image to another disk and
boot from that one.

1-34

RSX-llM V4.l RELEASE NOTES
1.3.22

Correction to Multiuser MCR on an Unmapped System

The multiuser version of MCR will not task-build properly for an
unmapped
system.
Before
doing
a SYSGEN, locate the file
[l,20]MCMBLD.BLD. Edit the file and change the line
.DATA PAR=GEN: '$GPB':20000
to
.DATA PAR="$GEN'
For the RLOl distribution kit, the file can be found on
disk.

1.3.23

the

EXCPRV

File Transfer Program (FLX)

The behavior of FLX in handling an error during a copy operation to
an RT-11 device has changed. Previously, FLX allowed a partial file
to be created on the output device when insufficient space existed
on the output disk with the same name as the newly created partial
file. FLX deleted the preexisting file and substituted the partial
file.
This replacing of an existing file with a partial file
resulted in a loss of information.
Now, if an error occurs during the copy operation, the partial file
is not substituted for an existing file on the output disk. The
partial file no longer is closed as a permanent entry, and the
definition and contents of the existing file remain intact.

1.3.24

Incompati~ilty

Problem with BRU Tapes

Because of BRU's new sort algorithm, V4.l can read V4.0
tapes, but V4.0 BRU cannot read V4.1 BRU backup tapes.

1.3.25

BRU

backup

Device Restrictions

The following device restrictions apply to RSX-llM V4.l:
e

MCR/DCL
The MCR/DCL SET and SHOW commands do not recognize the LPQ02
letter-quality printer.
The DCL SET and SHOW
personal printer.

•

commands

not

support

the

LASO

File Transfer Program (FLX)
The following devices do not support DOS-11 or RT-11 format:
RC25
RA60
RA81
RDSl
RXSO

1-35

RSX-llM V4.l RELEASE NOTES
•

Disk Volume Formatter (FMT)
The following devices are not supported:
RD51
RXSO
RA60
RA81
RC25
RPO?

•

Bad Block Replacement Control Task (RCT}
The RX50 does not have an RCT area.

•

Virtual Monitor Routine (VMR}
The SAVE
devices:

command

does

not

recognize

the

following

RA81
RD51
The SET command does not recognize the following devices:
LNOl
LP26
LP27
LP07
LQP02
•

Error Logging
The Error Logging control files do not have
information for the following devices:

device-specific

RD51
RX50
•

Crash Dump Analyzer (CDA}
The following fixed disks cannot serve as CDA devices:
RASO
RA81
RD51
RC25 (nonremovable)

1.3.26

Queue Manager

The MCR /NM switch suppresses messages from the Queue Manager
such as "Queue already exists.•

(QMG)

In DCL, the equivalent switch is /NOWARNINGS.
Once a queue has been established, it will remain until eliminated,
in spite of system crashes.
But it is desirable to attempt to
reestablish the standard print queues each time the system is
bootstrapped, in case a queue has been inadvertently eliminated.
Issuing a QUE LPO:/CR command, though, yields the "Queue already
exists• message from the QMG if the LPO queue has not been
eliminated, as is generally the case.

1-36

RSX-llM V4.l RELEASE NOTES
The /NM switch, therefore, is used in the prototype STARTUP.CMD
supplied on the distribution kit to reduce the "clutter" that is
printed on the console terminal when STARTUP.CMD is invoked.

1.3.27

Building the COBOL-81 Compiler

If you are installing COBOL-81, you must answer the following
dialogue prompts as indicated in order to build the COBOL-81
compiler correctly:
Do you want to build the default compiler <YES>?
Do not take the default.

You shQuld type:

The next two questions in the dialogue concern CIS and RMS.
The first of these two questions is:
What should be the compiler task size in K words (legal range
from "26° to 0 31") <31>?
The legal range for the compiler task size actually is 25 to 30 K
words.
Do not use the default for this question;
type the
numerical value of the compiler size from the revised legal range.
Note that you should not respond with 25 to this question either.
The next question asks whether you want to change the default of any
of the compiler switches.
You can either take the defaults or
change them.
The entire COBOL-81
Installation Guide.

1.4

dialogue

documented

the

COBOL-81

REPORTING PROBLEMS AND APPLYING CORRECTIONS

RSX-llM/RSX-llS includes several features to use if you encounter
questions or problems with your system or if DIGITAL provides
temporary patches to improve its software performance.
Software Performance Reports (SPRs) allow you to report any problems
directly to DIGITAL.
The procedure for submitting an SPR is
described in Section 1.4.1.
Sections 1.4.2 and 1.4.3 describe how to apply temporary software
corrections to your system. You should use instructions to apply
manual patches that are given either in a DIGITAL response to an SPR
or in a Software Dispatch article.
Note that any patches in the Software Dispatch are temporary and
will be overriden by future DIGITAL Updates.
An Update is a
periodic software fix to your system, distributed in the form of
machine-readable code. DIGITAL customers who are under warranty or
who have purchased any level of software product service will
receive the Software Dispatch and Updates.

1-37

RSX-llM V4.l RELEASE NOTES
1.4.1

Software Performance Report

When you complete an SPR form, describe only one problem per form,
to simplify record keeping and facilitate a more rapid response.
An SPR can be used for the following:
•

Software errors

•

Documentation errors when the documentation comment form
not appropriate

•

Inquiries

•

Suggestions

•

Follow-up on a previous SPR

An SPR cannot be used for the following:
•

Software license and price policies

•

Obvious hardware problems

•

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

•

Problems with user-written software

There are three categories of reports that you can send:
•

Problem/error
This type of report should have a priority of one
(Answer is generated.)

•

to' five.

Suggested enhancement
This type of report contains suggestions or queries that are
brought to the development group's attention and has a
priority of five.
(No answer is generated.)

•

Other
This type of report contains queries and suggestions
are priority five.
(Answer may be generated.)

The priority numbers are as follows:
1.

Most production work cannot be run.
a.

Major system functions are unusable.

System does not boot.

Necessary peripherals cannot be used.

Some production work cannot be run~
a.

Certain functions are unusable.

System performance has declined.

Installation has insufficient excess capacity.

1-38

that

RSX-llM V4.l RELEASE NOTES
3.

All production work can be run with some user impact.
a.

Significant manual intervention is required.

System performance has declined
excess capacity.

All production work can be run with no
on user.
a.

but

has

significant

impact

return

normal

Problem can be patched.-

No system modifications are
production.
a.

installation

needed

This category includes suggestions, consultations, or
errors in documentation.

Because problems are often difficult to reproduce with a different
system configuration, please define as precisely as possible the
state of the system when the problem occurred. Illustrate a general
problem with spec1fic examples. When you refer to a manual, specify
the full title and section, table, or page numbere
Please supply the following information (in
where applicable) when you report a problem:

machine-readable

form

Crash - A copy of the Executive task-build map, output from
the console terminal, the SYSGEN saved answer file, the
Executive STB file, and the crash dump. If the crash is
reproducible,
please accurately describe the details,
supplying hard copy or user source code when necessary.

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

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

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

File system - Corrupted Volume: Output from Verify utility
and dump of the volume. - Improper results: .Error code,
file header dump, sample program.

Error Log Report generator (RPT) - A copy of the report
file generated by RPT, either on a hard copy listing file
or on machine-readable media.

If a failure occurs when you are running privileged, add-on software
(for example, DECnet) try to reproduce the failure without the
additional software. Indicate on the SPR the behavior o~ the system
with and without the add-on software.
The SPR process takes time;
therefore, if you have a critical
problem, contact the local DIGITAL office. In the meantime, read
the Software Dispatch for news on RSX-llM, which includes changes
and problems other people have found and solved.

1-39

RSX-llM V4.l RELEASE NOTES
1.4.2

Applying Corrections to Source Files

Interim changes to the Executive, MCR Error Log Control Files, and
device drivers are made by creating correction files, which are
processed by the Source Language Input Program (SLP). SLP generates
a new copy of the modules that contained errors by applying
corrections to the source file on the distribution kit.
(See the
RSX-llM/M-PLUS Utilities Manual for complete information on SLP.)

NOTE
A new update policy is in effect. All
software fixes will be distributed as
machine-readable updates instead of
patches to be manually entered. Also,
any patches published in the Software
Dispatch are temporary fixes that will
be superseded by the next update.
After you have applied the corrections and obtained a new version of
the file, do not delete the original source file. Interim changes
that may be dTstr1buted later are cumulative and depend on the
contents of the distributed sources.
Because RSX-llM is distributed on a wide variety of media, it is not
practical to provide comprehensive examples for applying source
corrections.
In the sample procedures that
follow,
several
assumptions are made: You must be a privileged user executing on a
multiuser, mapped, dual RLOl system with an RLOl distribution kit.
If your system disk is large, it already contains all the necessary
files and file transfers are not required.

1.4.2.l Updating an Executive Source
Module - To
update
an
Executive source file (ABCDEF.MAC for example), mount the disk
labelled EXCPRV and create a SLP correction file named ABCDEF.COR in
the UFO [11,40].
Then running under UIC [11,10] submit the
correction file to SLP. For example, you could follow this sequence
to update REQSB.MAC:
>SET /UIC=[ll,40]

>ALL DLl:
>MOU DLl:EXCPRV
>ASN DLl:=SY:
>EDI REQSB.COR
[CREATING NEW FILE]
INPUT

*EX
[EXIT]
>SET /UIC=[ll,10]
>SLP @[ll,40]REQSB.COR
If the updated Executive module in your system is not a loadable
driver, and the module is not resident in one of the Executive
commons, (EXCOMl and EXCOM2), rebuild the Executive and privileged
tasks to incorporate the modification.

1-40

RSX-llM V4.l RELEASE NOTES
To rebuild, do the following:
1.

Assemble the new module, using the RSXMC.MAC file
target system.

Use LBR to replace the old version
RSXllM.OLB on the target system.

Invoke SYSGEN Phase II.

the

for

the

module

If the updated Executive module in your system is resident in one of
the
Executive
commons,
EXCOMl
or
EXCOM2, the process of
incorporating the modification is as follows:

..I..

Execute the first two steps in the procedure listed above~
There is no need to rebuild the loadable drivers or
privileged tasks in this case.
Rebuild the Executive as follows:
>SET /UIC=[l,24]
>TKB @RSXBLD

Create a new system image file as follows:
SET /UIC=[l,54]
PIP RSXllM.SYS/NV/CO/BL:XXX.=RSXllM.TSK
Note that XXX should be equal to whatever value was used in
the original SYSGEN.
This value is usually equal to 4
times your system memory size in 1024 decimal-word blocks,
plus 2, up to a maximum of 498.

VMR @SYSVMR.CMD

If the modified file in your system is a loadable device driver
(ZZDRV.MAC for example}, the updated module can be replaced without
doing another system generation. Assemble the updated module and
replace the resulting object file in the RSXllM.OLB of your target
system.
Boot the target disk:
>ALL DLl:
>MOU DLl: EXCPRV
>SET /UIC=[l,24] ! [1,20] for unmapped systems
>MAC ZZDRV=[l,l]EXEMC/ML,[11,10] RSXMC/PA:l, DLl:ZZDRV
>DMO DLl:
>DEA DLl:
>LBR RSXllM/RP=ZZDRV
>PIP ZZDRV.OBJ;*/DE
Use the indirect command file [200,200]SGNBLDDRV.CMD to produce the
files ZZDRV.TSK and ZZDRV.STB.
If necessary, copy ZZDRV.TSK and
ZZDRV.STB into the UFO corresponding to the system UIC.
>@1200,200]SGNBLDDRV

>SET /SYSUIC
SYSUIC=[g,m]
>SET /UI C= [ g ,m]
>PIP /NV=[l,54]ZZDRV.* ! or [l,50] for unmapped systems
1-41

RSX-llM V4.l RELEASE NOTES
Use VMR to unload the old device driver and to load the new one.
If
the new driver is larger than the old one, it may not fit into the
same locations as did the old one.
It may be necessary to unload
and reload all of the loadable drivers in that partition to create
enough room.
If the system is unmapped, some other drivers may have
to be rebuilt.
>VMR
ENTER FILENAME:RSXllM
VMR>UNL ZZ:
VMR>LOA ZZ:
VMR> AZ
>RUN $SHUTUP
Hardware bootstrap the modified system.

1.4.2.2 Updating an MCR Source Module - Updating an MCR source file
is similar to updating an Executive source file.
NOTE
For
illustration
purposes,
the
following discussion applies to the
RL01/RL02 kit.
The illustration is
adaptable
to
other
types
of
distribution kits.
Please refer to
the table at the end of this section
for disk labels of other types of
distribution kits.
The MCR source files are on a disk labeled MCRSRC in UFO [12,10].
The source files for the following modules (referred to as terminal
driver-dependent modules) appear on two disks, MCRSRC and EXCPRV:
DV20V
SPSOV
SXlOV
SX20V
SX30V
SX40V
STSUB

The steps to update a source file for MCR
(single-user and
multiuser)
and external MCR tasks are the same. The procedures for
rebuilding the single-user and multiuser MCR differ slightly.
Furthermore, if the module is one of the terminal driver-dependent
modules, the corrections should be applied to source files on both
disks. An example is provided below for each procedure.
Convention: The notation [l,2x]
and [l,20] for unmapped system.

represents [1,24] for mapped system

The following example explains the procedure to update MCR for a
RL01/RL02 kit.
To update the MCR source file SPSOV.MAC, mount the
RL01/RL02 disk labeled MCRSRC~
Create the SLP correction file SPSOV.COR and use it to update
SPSOV.MAC.
Assemble SPSOV for the target system.
Since SPSOV is a
terminal driver-dependent module, the correction must be applied to
source files on MCRSRC and EXCPRV.

1-42

RSX-llM V4.l RELEASE NOTES

DLO: is mounted with RSXM35 baseline disk
>SET /UIC=[l2,40]
>ALL DLl:
>MOU DLl:MCRSRC ! mount disk with source file
>ASN DLl:=SY:
>EDI SPSOV.COR ! creating the SLP correction file
[CREATING NEW FILE]
*EX

[
>SET /UIC=[l2,10]
>SLP @[12,40]SPSOV.COR ! apply correction on MCRSRC
!
! assemble the updated module
!

>SET /UIC=[l,2x]
>ASN DLO:=SY:
ass~gn SY: to baseline disk
>ASN DLO:=LB:
assign LB:
>MAC SPSOV=[ll,10]RSXMC/PA:l,LB:[l,l]EXEMC/ML,DL1:[12,10]SPSOV

>
if module is terminal-driver-dependent,
repeat above procedure with the EXCPRV disk
>SET /UIC=[l2,40]
>MOU DLl:EXCPRV ! mount second disk with terminal-driver
dependent source file
>ASN DLl:=SY:
>EDI SPSOV.COR ! create same SLP correction file as above
[CREATING NEW FILE]
*EX
[EXIT]
>SET /UIC=[l2,10]
>SLP @[12,40]SPSOV.COR

apply correction on EXCSRC

>
Single-user and multiuser versions of MCR
require
different
procedures for
incorporating the modified module into the system.
The procedures involve the following steps:
1.

Incorporate the updated module into MCR's object library.
If the module is terminal driver-dependent, append it to
the file of concatenated MCR terminal driver-dependent
modules.

Invoke SYSGEN3 to rebuild MCR and install it into the
system with VMR, ensuring that SY: and LB: are first
assigned to the disk containing the target system.

To rebuild single-user MCR, use the following procedure:
DLO: is mounted with RSXM35 baseline disk
! -

>MOU DLl:EXCPRV
>SET /UIC=[l,2x]
>LBR DLl:MCR/RP=SPSOV ! replace object module into MCR.OLB
>PIP DLl:MCR~OBJ/AP=SPSOV.OBJ ! for terminal-driver dependent
1
modules only
>PIP SPSOV.OBJ;*/DE ! clean up

1-43

RSX-llM V4.l RELEASE NOTES

invoke SYSGEN3 to build privileged task MCR
>SET /UIC=[200,200]
>@SYSGEN3 ! refer to SYSGEN Manual for details

>ASN DLO:=SY: ! ensure proper assignments
>ASN DLO:=LB:
for VMR
)VMR
Enter filename: RSXl~M
VMR>REM MCR ••• ! remove old MCR
VMR>INS MCR ! install new MCR
VMR> "'z
! end of procedure

To rebuild the multiuser MCR, use the following procedure:
DLO: is mounted with RSXM35 baseline disk
>MOU DLl:EXCPRV
>SET /UIC= [ 1, 2 x]
>LBR DLl:MCR/RP=SPSOV ! replace object module into MCR.OLB
>PIP DLl:MCR.OBJ/AP=SPSOV.OBJ ! for terminal-driver dependent
!
modules only
>PIP SPSOV.OBJ;*/DE ! clean up
! invoke SYSGEN3 to build privileged task MCM

>SET /UIC=[200,200]
>@SYSGEN3 ! refer to SYSGEN Manual for details

>ASN DLO:=SY: ! ensure proper assignments
>ASN DLO:=LB:
for VMR
>VMR
Enter filename: RSXllM
VMR>REM MCR ••• ! remove old MCR primary
VMR>REM ••• MCR ! remove old MCR secondary
VMR>INS MCRMU ! install new MCR primary
VMR>INS SYS
install new MCR secondary
VMR>"'Z
end of procedure

There is only one procedure for replacing an external MCR task.
involves the following steps:

Create the SLP file, apply it, and create the object file.

Incorporate the
library.

Rebuild the task and install it in the system, using MCR or
VMR.
Before using VMR, you must assign SY: and LB: to
the disk containing the target system.

updated

module

1-44

into

the

task's

object

RSX-llM V4.l RELEASE NOTES
The following example replaces the module INSLB of the external
task Install:

MCR

>SET iUIC=[l,24]
>LBR INS/RP=[l2,24]INSLB
If it was necessary to modify the external task's Task Builder
command file during the last system generation, it may be necessary
at this time to repeat those changes:
>SET /UIC=[l,24]
>ASN SY:=MP:
>TKB @INSBLD
>SET /SYSUIC
SYSUIC=[g 1 m]
>PIP /NV=[l,54]INS.TSK
>VMR
ENTER FILENAME: RSXllM
VMR>REM ...... INS
VMR>INS INS
VMR>"'z
>RUN $SHUTUP
Hardware bootstrap the system.
The following tables summarize where the relevant MCR
on the multiple-media distribution kits:

files

appear

For RL01/RL02 distribution kit:
MCRSRC

[ 12 I 1 0 ] * • MAC

All MCR source files

EXCPRV

[12,10]*.MAC

MCR terminal-driver
source files

EXCPRV

[l,2x]MCR.OLB
[l, 2x] MCR. OBJ

MCR object library
Concatenated
terminal-driver
dependent object modules (used
by SYSGEN)

RSXM35

[l,l]EXEMC.MLB
[11,lO]RSXMC.MAC

Prefix files
modules

dependent

assemble

MCR

For RK06/RK07 distribution kits:
CLISRC

[ 1 2 , 10 ] * • MAC

All MCR source files

RSXM35

[12,10]*.MAC

MCR terminal-driver
source files

RSXM35

[l,2x]MCR.OLB
[l, 2x] MCR. OBJ

MCR object library
Concatenated
terminal-driver
dependent object modules (used
by SYSGEN)

RSXM35

[l,l]EXEMC.MLB
[11, 10] RSXMC .MAC

Pref ix files
modules

1-45

dependent

assemble

MCR

RSX-llM V4.l RELEASE NOTES
1.4.2.3 Updating a DCL Source Module - The procedure is different
for the DCL task.
There are two DCL object libraries: DCLR.OLB for
modules in the root segment of the DCL task, and DCLO.OLB for
modules in DCL's overlay segments..
(One module, COMMAND, has
versions in both the root and overlay libraries.)
These libraries
are located in UFO [1,24] of your distribution kit.
If you are not
sure whether a module belongs in the root or the overlay library,
use LBR to scan the module names in the libraries.
For instance, to
view the module names in DCLO.OLB, enter the following command:
MCR:
LBR [l,20]DCLO/LI
DCL:
LIBRARY/LIST [l,20]DCLO
The modules you are most likely to need to modify are the DCL syntax
tables, which are in DCLO.OLB.
(All DCL syntax tables are in
overlay segments.) See Chapter 12 of the RSX-llM/M-PLUS System
Management Guide for more information on the structure of the DCL
task and on the DCL task-building process.
File DCL.CMD, in UFO [23,24] of your distribution kit, can be used
either to assemble DCL overlay modules and to re-task-build DCL, or
as a template for your own commands.
The file contains its own
instructions. Note that to use this command directly, you must copy
various files into its UFO, and you must appropriately modify any
UFOs 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 re-task-build DCL.
The process is similar for root modules;
simply specify DCLR rather than DCLO. See DCL.CMD for details on
rebuilding COMMAND.
MCR:
SET /UIC=[23,24]
MAC XXX=[ll,lO]RSXMC/PA:l,[23,lO]DCLMAC/PA:l,XXX
SET /UIC=[l,20]
LBR DCLO/RP=[23,24]XXX
SET /UIC=[l,24]
TKB @DCLBLD
DCL:
SET DEFAULT [23,34]
MACRO [ll,lO]RSXMC/PASS:l,[23,lO]DCLMAC/PASS:l,XXX
SET DEFAULT [1,20]
LIBRARY/REPLACE DCLO [23,24]XXX
SET DEFAULT [1,24]
LINK @DCLBLD
When you have built a new version of DCL.TSK, you must replace the old
copy of DCL as a system CLI, as follows:
First, any terminals whose
CL! is DCL must be logged off or set to another CLI.
Then the
following commands must be executed.
(Note that these commands are
MCR only.)

1-46

RSX-llM V4.l RELEASE NOTES
MCR:
CLI /ELIM=DCL
REM DCL

INS $DCL/CLI=YES
CLI /INIT=DCL
The REMove and INStall commands are also valid VMR commands and can be
used to modify your system's image on disk.
However, the CLI /!NIT
command is MCR only, and must be put in your system's startup file {if
it is not there already).

1.4.3

Patching Object Modules

The Object Module Patch Utility {PAT)
incorporates an object patch
into an existing object module.
DIGITAL publishes a patch file
written in MACR0-11 assembly language to correct an error or make a
change.
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
for the input file and the correction files.
If the checksum value
does not agree with the computed result, PAT reports an error.
If the
correction file caused the error, check the source file against the
original published source file to verify that it was copied correctly.
If the input file caused the error, verify that the correct version of
the object file is being patched.
Note that it normally is necessary to use LBR to extract the original
object module from a library. PAT produces a new object module file
containing the corrected object code. When you patch modules from a
library, take the input object module from the distributed library and
put the patched object file into a copy of that library.
The following guidelines apply to the formats for
and correction files.

PAT

command

input

Specify an explicit name, extension, and version number for each file.
Use the following conventions for names:

File

Specification

Correction file source
Correction file object
Input file object
Patched object

name.PAT
name.PCB
name.OBJ;n
name.OBJ;n+l

Specify checksums for all input and correction files.
The following example illustrates the command formats for updating an
object module. First you must create the correction source file using
a text editor, and then do the following:
>MAC NAME.POB=NAME.PAT
>LBR NAME.OBJ=LIBRARY.OLB;l/EX:NAME
>PAT NAME.OBJ;2=NAME.OBJ;l/CS:3471,NAME.POB/CS:l532
>LBR LIBRARY.OLB;2/RP=NAME.OBJ;2
The correction source input file is used to accumulate all patches for
a given module.

1-47

RSX-llM V4.l RELEASE NOTES
1.5

NOTES TO RSX-llM V4.l DOCUMENTATION

The following sections contain notes that correct
V4.l documentation.

1.5.1

supplement

the

RSX-llM System Generation and Installation Guide

In Sections 2.3.1.2 and 2.3.2.1, Copying the Big Disk Magnetic Tape
Kit Stand-Alone and Copying the Big Disk Magnetic Tape Kit On-Line
respectively, the procedure BRU uses to copy the big disk 800 bpi
magnetic tape kit (steps 4 through 7 for Section 2.3.1.2 and step 5
for Section 2.3.2.1) is not documented in the correct sequence.
The
correct procedure (either stand-alone or on-line) to copy the big disk
800 bpi magnetic tape kit is as follows:
1.

Invoke the Backup and Restore Utility (BRU) and enter the
command line to copy the tape to disk. For example, to copy
the distribution tapes to the RM02 disk, enter the following
command to BRU:
>BRU
BRU>/BAC:RSXM35/INI/REW/DEN:800/VER
From:
MMO:
To:
DRO:
BRU - Starting Tape 1 on MMO:

BRU copies the first tape and then prompts you for the second
tape.
BRU - End of Tape 1 on MMO:
BRU - Mount Tape 2 on MMO:
BRU - Starting Tape 2 on MMO:

When the second tape finishes copying, BRU prompts you to
remount the first tape on the tape drive so that it can do
the verification of the first tape.
BRU BRU BRU BRU -

End of Tape 2 on MMO:
Mount Tape 1 on MMO:
Starting verify pass Tape 1 on MMO:
End of Tape 1 on MMO:

When BRU finishes verifying the first tape, it is ready to
verify the second tape.
BRU prompts you to remount the
second tape on the tape drive.
BRU - Mount Tape 2 on MMO:
BRU - Starting verify pass Tape 2 on MMO:
BRU - End of Tape 2 on MMO:
BRU - Completed
BRU><CTRL/Z>

At this point, you have completed the tape-to-disk copy of the big
disk 800 bpi tape kit and you are ready to generate your RSX-llM
system.

1.5.2

RSX-llM/M-PLUS MCR Operations Manual

The /TERM keyword for the MCR SET command now supports the LASO.
should add this new support to page 3-210 of Chapter 3.
1-48

You

RSX-llM V4.l RELEASE NOTES
1.5.3

RSX-llM/M-PLUS Utilities Manual

1.5.3.1 Correction for PIP Utility - In Chapter 3, page 3-21,
11. .... ,
maximum value of the byte location of EOF is 377(octal). c-u•.z
over this will result in an error message.

the
•7!:>1110
y

""" ......... ~

1.5.3.2 Correction for FLX Utility - In Chapter 4, Table 4-1, page 5,
the following correction should be made:
/IM:n

Image Mode

The transfer is to be in image mode.
Image mode forces fixed-length records.
You can use the value n to indicate the
desired record length (in octal bytes) for
Files-11 output (1000 (8) bytes maximum).
If you do not specify n, FLX assumes a
record length of 512 (10) bytes.

The documentation currently indicates the value of n in decimal rather
than in octal bytes.

1. 5. 3. 3

Format Change the LBR /CR switch - In- -Sec-tion 10. 5. 2 of the
Librarian Utility Program {LBR) chapter, the format for specifying the
Create switch {/CR) has changed to the following:
For macro and object libraries outfile/CR[:size:ept:mnt:infiletype=infile]
For universal libraries:
outfile/CR[:size:ept:mnt:infiletype:libtype=infile]

1.5.3.4 New Switch for File Dump Utility (DMP) - In Chapter 11, File
Dump Utility Program {DMP), the following new switch should be added
to Table 11-L
Switch

Description

/LIM:n:m

Specifies the range of bytes n through m of
each record or block to be dumped. /OCT is
still the default if no format switches are
specified.

1.5.3.5 New Error Message for PAT Utility - In Chapter 14, Object
Module Patch Utility (PAT), the following new error message should be
added to PAT MESSAGES:
UNABLE TO OPEN FILE filename
Explanation: There is insufficient work space in the internal
File Storage Region (FSR) of the PAT utility.
User Action:
increment.

Install

1-49

run

the

PAT

utility

with

RSX-llM V4.l RELEASE NOTES
1.5.4

RSX-llM/M-PLUS I/O Drivers Reference Manual

A complete RD51 Fixed Disk/RX50 Flexible Disk Subsystem consists of
the fixed and flexible disks and an RQDXl hardware controller
(RQDX1/RD51/RX50).
This information should be included on page 5-4.1.
Updated I/O error codes for this manual
Mini-Reference.

1.5.5

are

listed

the

RSX-llM

IAS/RSX-11 I/O Operations Reference Manual

1.5.5.1 MTAACP Enhancements - The following sections summarize the
enhancements made to the RSX-11 V4.0 and V4.l Magnetic Tape Ancillary
Control Processor (MTAACP)
in compliance with the ANSI standard.
Detailed descriptions of the enhancements are included in Appendix G
of the IAS/RSX I/O Operations Reference Manual.
The RSX-llM V4.0 MTAACP has been enhanced for the following:
•

compliance with ANSI and FIP standards

•

processing of unlabeled tapes

•

Mount, Dismount, and Volume Switch Control

The RSX-llM V4.l MTAACP has been enhanced to support RMS V2.0. MTAACP
supports new file attribute codes (creation, revision, expiration, and
backup dates), which read and write the data in the file header using
a 64-bit date format. MTAACP performs a computation to convert the
date between ASCII and 64-bit binary form.

1.5.5.1.1 Compliance With ANSI and FIPS. - DIGITAL now provides tape
labeling systems that conform to ANSI Standard X3.27
1978,
according to the Federal Information Processing Standard. The MTAACP
has been enhanced to comply fully at levels 1 and 2, and to comply at
level 3 with the exception of support for user-supplied labels.
User-supplied labels may appear on a tape; however, they are only
accessible to application programs through the
unlabeled
tape
facility.
The following new features are a result of the implementation of
compliance:
•

ANSI

Seventeen-character file name support
If file names appear in quotes ("), they may be up to 17
characters long and may contain any characters in the ANSI "a"
character set.
Note that as a result of this change, PIP directory listings
of magnetic tapes have a new format.
The most noticeable
difference is the presence of several spaces preceding the
version number.
The spaces are included to clearly delimit
the version number from the file identifier, which, in
accordance with the standard, may contain embedded semicolons.

•

Volume Set Identification support
Previously, the MTAACP only supported Volume Set Identifiers
that were the same as the Volume Identifier of the first
volume in the set. However, the ANSI standard requires that
Volume Identifiers be unique within an installation (thus
1-50

RSX-llM V4.l RELEASE NOTES
preventing a user from choosing names of his or her own).
Full support of the Volume Set Identifier allows the user to
choose a name for this field, which becomes the primary means
of access to a volume using the MOUNT command. This change
was implemented with full compatibility with the previous
releases and requires no changes in procedures for users who
do not wish to use the new feature.
•

Control of attributes
MOUNT and the MAG utility allow the specification of block and
record sizes for tapes written on systems that do not write
this information on the tape. They also allow control of the
carriage control attribute for tapes created on systems whose
system code is not recognized by the MTAACPe
Note that the default block size for files written to tapes
from an RSX system may also be modified with MOUNT or the MAG
utility.
This value is normally 512 bytes;
if it is
modified, additional buffer space must be allocated in the
programs writing to tape.

•

Magnetic tape file block size
The PIP block size switch is no longer necessary when reading
files from magtape;
FCS will adapt automatically to input
files of varying block size.
PIP directory listing of files on magtape show the number of
magtape blocks.
Thus, the file size on a magnetic tape
(represented in terms of variable size blocks)
may
be
different from the size of the file on disk.

•

Volume and file accessibility
In accordance with the ANSI standard, volumes that have a
nonspace character in the volume accessibility byte may be
mounted only by a user who has the privilege to override
accessibility.
The Initialize Volume Utility allows the specification of the
character to be placed in the volume accessibility byte in the
Volume Header Label.
Also in accordance with the standard, files that have a
nonspace character in the file accessibility byte may only be
accessed by a user who has mounted the volume with "override
accessibility 0
specified. A user who has mounted a volume in
this manner may also write a nonspace character in the file
accessibility byte of the file header label by specifying a
valid "a" character in the high byte of the file protection
word and a low byte of all ones. The file protection word may
be specified at MOUNT time {for example, a
file protection
specification of [,,WED,RWD] represents the character "A•) or
as an attribute to the CREATE QIO.

1.5.5.1.2 Support of Unlabeled Tapes - The MTAACP now permits tapes
to be mounted with the /NOLABEL switch. This allows utilities such as
PIP and higher-level language applications programs (in FORTRAN,
for
example) to read and write unlabeled tapes using the standard READ and
WRITE statements in the language.
Files on unlabeled tapes may contain fixed-length records that may
blocked or unblocked.
1-51

RSX-llM V4.1 RELEASE NOTES
In addition, when processing unlabeled tapes, you may
request
character set translation. An EBCDIC translate table is provided with
the ACP; you may add up to three additional installation-defined
translate tables.
Control of this feature is provided by the MOUNT
command and by the MAG utility, as well as by attributes specified by
applications programs when you create files.
The file name used when you access an unlabeled tape may specify
positioning information, if desired. If no positioning information is
desired, the file name has no meaning. However, some utilities, such
as PIP, may require a dummy file name to prevent the use of wildcard
mode.
Note that there are now three ~ays tapes may be mounted:
•

Mounted for ANSI

•

Mounted for Unlabeled Processing

Mounted foreign

The ability to mount a tape "foreign• is provided for compatibility
with other operating systems and has no effect in an RSX-llM system
other than reserving the drive for exclusive use. Access to a tape
mounted "foreign" is handled by logical QIO directives. Access to a
tape mounted "unlabeled" (/NOLABEL) or "ANSI" is through virtual QIOs,
primarily those issued by FCS, RMS, the READ and WRITE statements of
higher-level languages, and file-oriented utilities such as PIP.
In order to obtain support for unlabeled tapes, you must
Magtape support at system generation.

select

ANSI

1.5.5.1.3 Mount, Dismount, and Volume Switch Control - When the
operator dismounts an ANSI tape, the default action recommended in the
standard is to unload the tape. Depending on which model tape drive
is in use, this will either take the drive off line or actually unload
the tap~.
The DCL /[NO]UNLOAD switch and the MCR /LOCK=[NO]UNLOAD switch specify
a different action to be taken. This switch can be applied to either
the MOUNT or DISMOUNT command.
When a volume switch is requested, you may, by using the MAG utility,
cause error codes to be returned to the program that is reading or
writing.
(Previously, it was necessary either to mount a tape or to
abort the program.) The MAG utility also allows a tape to be
initialized if a new tape is needed for output and no previously
initialized tape is available.

1.5.5.1.4 RMS-11 Support - MTAACP supports new file attribute codes
(creation, revision, expiration, and backup dates), which read and
write the date in the file header using a 64-bit date format.
MTAACP
performs a computation to convert the date between ASCII and 64-bit
binary form.

1-52

RSX-llM V4.l RELEASE NOTES
1.5.5.2 FDB Offset Definitions - The following information should be
added to the FDB Offset definitions listed in Appendix A of the
IAS/RSX-11 I/O Operations Manual:
Offset

Size
(in Bytes)

Contents

F.RATT

Bit 2 = 1 to indicate the "print file
format"
(FD.PRN).
FCS allows this
attribute but does not interpret the
format word.

F.NRBD

Contains the
next
record
buffer
descriptor.
The format of the record
buffer descriptor is the size word
followed by the address of the buffer.

F.RCNM

Contains the number of the record for
random access operations. The format
of the record number is the high-order
word followed by the low-order word.

F.yBN

Contains the virtual block number.
The format of the virtual block number
is the high-order word followed by the
low-order word.

1.5.5.3 Shared Access and
information in Chapter 2,
Operations Reference Manual:

Block Locking - Include the following
Section 2.2.1.5 of the IAS/RSX-11 I/O

f acc
•

FA.SHR - Shared
locking.

access

also

precondition

for

block

•

FA.LKL!FA.EXL - FCS
permits
limited
block
locking
to
coordinate two or more tasks' access to the same file.
All
tasks accessing the file must open the file for shared access
by setting bit FA.SHR in FDB field F.FACC (the field access
byte) •

actl

1.5.5.4 Opening a File by File ID Number - Include the following
information in Chapter 3, Section 3.5 of the IAS/RSX-11 I/O Operations
Reference Manual. This information follows the bulleted list at the
end of the section:
The OFID$W macro call is equivalent to the OFID$U macro call;
invoking either OFID$W or OFID$U opens an existing file by file ID
number for update and extension.

1.5.5.5 Buffer Flush Routine
(.FLUSH) - Include
the
following
information in Chapter 4 of the IAS/RSX-11 I/O Operations Reference
Manual as Section 4.17:

1-53

RSX-llM V4.l RELEASE NOTES
When using PUT$S to a disk or ANSI tape file, FCS does not normally
write the contents of the block buffer to a file until the block
buffer is full or the file is closed. The .FLUSH routine forces the
block buffer to be written to the file. You may need this function to
protect data from a system crash or if the data needs to be written so
that another task can read it from the file.
The following register must be preset before calling this routine:
RO Must contain the address of the associated FDB.
During output, all registers are preserved, the carry bit is clear or
set to indicate success or failure, and the FDB F.ERR byte contains
the success or failure code.

1.5.5.6 I/O Error Codes - Updated I/O error codes for this manual are
listed in the RSX-llM Mini-Reference.

1.5.6

IAS/RSX-11 SYSTEM LIBRARY ROUTINES REFERENCE MANUAL

The following program section names and SYSLIB routines should be
added to Table 1-1 of the IAS/RSX-11 System Library Routines Reference
Manual:
Program
Section
Name
PUR$D

PUR$I

1.5.7

SYS LIB Routines
Module
Routine
Name
Name{s)
CAT5B
{data)

$CAT5B

EDTMG
(data}

$EDTMG

CAT5B
(instruction)

$CAT5B

EDTMG
(instruction}

$EDTMG

RSX-llM/M-PLUS ODT Reference Manual

The format for the relocation registers in some sections of this
manual is incorrect.
The correct format for the registers is $nx,
where n is a number and x is a letter.
The manual, however,
incorrectly reverses the letter and number, using an $xn format. For
example, where the text references relocation register $RO, the
reference should be $OR.

1.5.8

RSX-llM/M-PLUS System Management Guide

1.5.8.1 Virtual Monitor Routine (VMR) - VMR,
10, now has the following new error messages:

1-54

documented

Chapter

RSX-llM V4.l RELEASE NOTES
•

VMR -- saved system truncated to n. blocks
Explanation:
(RSX-llS systems only.) VMR tried to save a
system greater than n~ blocks;
This results in VMR
truncating the saved image file to n.
(112 decimal
blocks for 28.K word systems saved on paper tape, 492
decimal blocks for 123.K word systems saved on RXOl
floppy diskettes, and 496 decimal blocks for 124.K word
systems saved on all other bootable devices) •

•

VMR -- Reference to memory beyond end of system image file
Explanation: VMR attempted to fix a task, load a driver,
or install a common beyond the space limits of the system
image file. This results in the command aborting and not
executing.

The VMR SET /TERM keyword now supports the LASO.

1.5.9

RSX-llM Guide to Writing an I/O Driver Manual

1.5.9.1

Changes to Data Structure Macros - Appendix c

1.5.9.1.1 BWDDF$ - The symbol for the
program status word, PMODE, is no
management (M$$MGE) •

previous mode field of the
longer conditional on memory

The following symbol has been added to the third feature
definitions:
F3.SHF=40000

symbol

;MEMORY SHUFFLER SUPPORTED

1.5.9.1.2 PKTDF$ - In the kernel AST control block
following kernel AST types have been removed:
AK.TBT=203
AK.DI0=204

mask

definitions,

the

;TASK FORCED T-BIT TRAP AST
;DELAYED I/O (M-PLUS COMPATIBLE)

and the following kernel AST type has been added:
AK.GGF=303
In the Executive pool monitor
flag:
PC.ALF=4

;GROUP GLOBAL RUNDOWN AST
control

flags,

the

following

$POLST

;POOL ALLOCATION FAILURE (l=YES)

has been expanded into two flags:
PC.ALF=4
PC.XAF=lO

;FAILED TO ALLOCATE LARGE BLOCK (l=YES}
;FAILED TO ALLOCATE SMALL BLOCK (l=YES)

and the following flag has been added:
PC.XIT=200

;FORCE POOL MONITOR TASK TO EXIT

1-55

RSX-llM V4.1 RELEASE NOTES
1.5.9.1.3 TCBDF$ - In the Task Control Block offset definitions, the
conditionalization on the group global event flag use count field,
T.GGF, has been changed from group global event flag support or the
Send Data directive:
$$$=.
T.GGF:

.BLKB

;GROUP GLOBAL USE COUNT FOR TASK

.IF NDF G$$EFN

R$$SND

.ENDC

R$$SND

.=$$$
;G$$EFN

to group global event flag support and either the Send Data
or alternate CL! support:
$$$=.
T.GGF:

.BLKB

directive

;GROUP GLOBAL USE COUNT FOR TASK

•. IF NDF R$$SND & G$$EFN

A$$CLI & G$$EFN

.ENDC

A$$CLI & G$$EFN

.=$$$
;R$$SND & G$$EFN

1.5.9.1.4 UCBDF$ - In the Unit Control Block offset definitions,
following MSCP disk driver offsets have been added:

the

CHARACTERISTICS STORED FROM "GET COMMAND STATUS" END PACKETS
;

000124
000126

U.OTRF=U.VCB+70
U.CMST=U.VCB+72

;OUTSTANDING COMMAND STATUS REQUEST REG
;COMMAND STATUS PROGRESS REGISTER

The console driver offsets have moved from U.CNT to U.BUF+2:
000026
000030
000034

.=U.BUF+2
U.CTCB: .BLKW
U.COTQ: .BLKW
U.RED2: .BLKW

1
2
1

;ADDRESS OF CONSOLE LOGGER TCB
;I/O PACKET LIST QUEUE
;REDIRECT UCB ADDRESS

A new terminal-dependent characteristic word bit definition
added:

has

been

TERMINAL DEPENDENT CHARACTERISTICS WORD 4 {U.CW4) BIT DEFINITIONS
;

U4.CR=l00

; LOOK FOR CARRIAGE RETURN

1.5.9.2 Asynchronous Buffered 1/0 - The following information
buffered input and output should be included in Chapter 2.

Typically, data for input and output requests are transferred directly
to and from .task memory. To allow the successful transfer of data,
the task cannot be checkpointed until the transfer is complete.
For
most high-speed devices, the transfer occurs quickly enough so that a
task does not occupy memory for too long a time.
For slow-speed
devices, however, some mechanism must be available to avoid binding
memory to a task for too long a time while the task is performing I/O.
Using the routines $TSTBF, $INIBF, and $QUEBF in the Executive module
IOSUB, a driver can execute an I/O request for a slow-speed device and
allow the task to be checkpointed while the request is in progress.
1-56

RSX-llM V4.l RELEASE NOTES
To perform the I/O request, the driver buffers the data in memory
allocated to the driver while the task is checkpointed and the I/O
request is in progress.
To test whether a task is in a proper state to initiate I/O buffering,
the driver calls the $TSTBF routine and passes it the address of the
I/O packet. By extracting the address of the task control block (TCB)
from the I/O packet, $TSTBF can examine various task attributes.
For
example, if the task is checkpointable, buffered I/O can be performed.
$TSTBF returns to the driver and indicates whether buffered I/O can be
performed.
If buffered I/O can be performed, the driver performs two operations.
First, it establishes the buffering conditions.
For an output
request, it copies the task buffers to dynamically allocated pool
space.
For an input request, it allocates sufficient pool space to
receive the incoming data.
Second, the driver calls the $INIBF
routine to initiate the I/O buffering. $INIBF decrements the task I/O
count, increments the task's buffered I/O count in T.TIO, and releases
the task for checkpointing and shuffling.
If the task is currently
blocked, the task state is transformed into a "stopfor" state until
the task is unblocked, buffered I/O completes, or both. Checkpointing
the task is subject to the normal requirements of an active or
"stopfor" state as described in the RSX-llM-PLUS Executive Reference
Manual.
After the driver transfers the data, it calls the $QUEBF routine to
queue the buffered I/O for completion.
$QUEBF sets up a KERNEL
asynchronous system trap (KERNEL AST) for the buffered I/O request
and, if necessary, unstops the task. When the task is active again, a
routine in the Executive module SYSXT notices the outstanding AST and
processes it.
(If the request is for input, the routine copies the
buffered data to task memory.) This mechanism occurs transparently to
the task;
thus the name KERNEL AST. The routine then calls the
driver to deallocate the buffer from pool.
$IOFIN completes the
processing. These routines are not always present in RSX-llM.
If you
selected the full duplex terminal driver or networking support during
system generation, they are automatically included. To include them
in systems without these options, add the symbol A$$BIO= O to
RSXMC.MAC during Phase I of system generation.

1.5.10

RSX-llM/M-PLUS Task Builder Manual

1.5.10.l Task-building an F4PRES, FORRES, or FMSRES with/without
ECSRES - The following section describes how and why you might want to
link an application task to one or more languages, FMS, or a FCS
resident library. Trade-offs or memory, speed, flexibility, and ease
of use are discussed. For the sake of simplicity, the example of a
FORTRAN-IV-PLUS OTS resident library (F4PRES) is used in the rest of
this text to represent FORTRAN-IV-PLUS, FORTRAN-IV (FORRES), and FMS
(FMSRES) resident libraries.
On RSX-llM systems, resident libraries must reside in dedicated
partitions.
In general, the presence of a permanent resident library
is justified when it is used frequently enough that it saves physical
memory, compared to having the FCS or OTS code in the task images of
frequently used tasks.
For more information on resident libraries,
refer to the RSX-llM/M-PLUS Task Builder Manual Section 4.5, Use and
Size of Overlay Run-Time Routines, and Section 5.2, Cluster Libraries.
In all cases, the application task need only be linked to properly
built resident libraries using the L!BR, COMMON, RESL!B, RESCOM; or
CLSTR options.

1-57

RSX-llM V4.l RELEASE NOTES
1.5.10.1.1
follows:
1.

FCSRES - The

types

FCS

resident

libraries

are

Memory-resident overlaid FCSRES
SYSGEN can automatically generate a memory-resident overlaid
FCS resident library that uses one APR of task address space.
This FCSRES makes available all of FCS
{except little-used
routines .CTRL,
.PRSDI, and .PPR50), .CSI!, .CSI2, and many
other system library routines. See [l,20]FCSRS1BLD.BLD for a
list
of
routines.
When
FCSRES
is
built
from
LB:[l,l]SYSLIB.OLB, it uses 5128 decimal words of physical
memory;
and when it is built from LBP: [l,l]ANSLIB.OLB, it
uses 6624 decimal words.
FCSRES uses one APR in either case
because it is composed of two memory-resident overlays and a
null root segment.
SYSGEN Phase II and SYSGEN Phase III can link utility tasks
to this FCSRES, frequently improving task execution speed and
virtual address space, and lessening task image size.
This
feature,
plus the fact that no editing of a source file is
required, makes the memory-resident FCSRES easier to use than
the non-memory-resident FCSRES.
This
memory-resident
memory-resident support.

FCSRES

obviously

requires

In order to task-build an application task to both the
memory-resident FCSRES and F4PRES, it is necessary to take
special measures when building the F4PRES.
Such a resident
library is said to have revectored FCS.
Once the F4PRES is
built, application tasks may be linked to it with or without
linking to FCSRES as well.
The TKB cluster library facility,
using the CLSTR option, may be used to task-build the
application task to two or more resident libraries at a
savings in virtual address space.
2.

Non-Memory-resident FCSRES
You can manually assemble and build a non-memory-resident
FCSRES from
[200,200]FCSRES.MAC.
If you build the resident
library using LB:[l,l]SYSLIB.OLB, you can produce a 3744
decimal-word, 1-APR FCSRES without editing FCSRES.MAC.
If
you build the resident library using LB:[l,l]ANSLIB.OLB, then
you must edit FCSRES.MAC to remove enough FCS routines from
FCSRES to bring it below 4K words.
Unedited, FCSRES.MAC
builds
into
a
2-APR, 4448 decimal-word FCSRES using
ANSLIB.OLB.
Unedited, this FCSRES contains all of FCS. Note that .CSI!
and .CSI2, used by FORTRAN-IV and FORTRAN-IV-PLUS ASSIGN and
OPEN statements, are not present in the non-memory-resident
FCSRES.
Their 1426 decimal
total bytes will be present
either in your application task images if you use ASSIGN or
OPEN or they can be included in F4PRES.
If you want to link RSX utilities to a non-memory-resident
FCSRES, you must create and edit the TKB .CMD and .ODL files
and task-build the utilities manually.
No memory-resident support is required.

1-58

RSX-llM V4.l RELEASE NOTES
1.5.10.1.2 F4PRES - Building an optimal F4PRES depends
on
the
specific F4P OTS routines your application tasks use, their need for
virtual address space, and the available physical memory on your
system~

You must decide which F4P OTS routines are used frequently enough by
your applications to warrant their presence in F4PRES. Routines are
included or excluded by editing F4PRES.MAC.
The gating factor is often the number of APRs used to map to the
resident libraries. For example, if you construct an F4PRES that uses
two APRs, clustered with FCSRES, for a total of two APRs, you might
have an important privileged application task that only has 1 APR
available.
In this case, it may be best to edit more routines out of
F4PRES, to trim it to 1 APR.
The key to building an F4PRES so that it can be used with the
memory-resident FCSRES is.that no FCS code is present in the F4PRES,
but all subroutine calls to FCS in the F4PRES are resolved when the
F4PRES is built.
This scheme involves revectoring the FCS calls
through the application task image. The scheme is described in detail
(including TKB command files)
in the RSX-llM/M-PLUS Task Builder
Manual, Section 5e2e

1.5.10.1.3 Options and Tradeoffs - There are a number
building application tasks with resident libraries.

ways

The following examples assume a ,minimally sized F4PRES:
4096
decimal words
(1 APR)
if FCS is not contained in it, and 8192
decimal words (2 APRs) if FCS is contained in it. These numbers will
vary according to the F4P OTS routines that you include in F4PRES.
It
may not be possible for you to construct a useful F4PRES of one or
both of these sizes;
yours may have to be two APRs or three APRs,
respectively.
In the following cases, the "Virtual and Physical Memory" discussions
are always relative to a task with no overlays or resident libraries.
Your own disk or memory-resident overlays may add overlay run-time
routines, autoload vectors, and segment and region descriptors to your
task. Section 4.5 discusses this in more detail.
•

Case 1
F4PRES with revectored FCS calls and memory-resident FCSRES
used as a cluster library. Link the application task with
this TKB option:
CLSTR=F4PRES,FCSRES:RO
Uses a total of one APR, making available maximal virtual
address
space
in the application task.
This is most
appropriate for tasks that can take advantage of the increased
virtual address space. On a system with the memory-resident
FCSRES, F4P application tasks that do not profit from the
increased address space should be built according to case 2,
with two LIBR= TKB options.
Macro application tasks, of
course, can be built with one LIBR=FCSRES:RO TKB option (see
case 3 for memory characteristics in this case) •
If FCS routines are called from the task image, the calls are
resolved to entry points in FCSRES.
(FCS routines might be

called by either OTS cede in the task
.subroutines.)

1-59

image,

your

macro

RSX-llM V4.l RELEASE NOTES
Virtual and physical memory:
Uses one APR.
The application
task root incurs a load of 1250 decimal bytes, 32 decimal from
FCSJMP.OBJ, 650 decimal from FCSRES.STB (autoload vectors,
segment and region descriptors), and 568 decimal from the
overlay run-time routines.
Execution speed: Some execution time is consumed when the
overlay run-time code in the task image must change the APRs
from one resident library to another.
•

Case 2
F4PRES with revectored FCS calls and memory-resident FCSRES,
though not used as a cluster library.
Link the application
task with these TKB options:
LIBR=FCSRES:RO LIBR=F4PRES:RO
Uses a total of two APRs for the resident libraries, but there
is less overhead than with a cluster. This is best for tasks
that cannot profit by using the extra APR that a cluster could
make available.
If FCSRES is predominantly being used in this
way (little use of FCSRES linked to RSX utilities or macro
application tasks, and no clustered FCSRES and F4PRES), then
you should also consider case 4, where a 2- APR F4PRES
contains FCS with no cost in autoload vectors, FCSJMP, or
overlay run-time routines for FCSRES.
Other tasks
can
reference the resident libraries with one or more TKB LIBR
options, or with CLSTR.
If FCS routines are called from the task image, the calls are
resolved to entry points in FCSRES.
(FCS routines might be
called by either the OTS code in the task image or your macro
subroutines.)
Virtual and physical memory: Uses two APRs. The application
task root incurs a load of 1164 decimal bytes, 32 decimal from
FCSJMP.OBJ, 650 decimal from FCSRES.STB
(autoload vectors,
segment and region descriptors), and 482 decimal from the
overlay run-time routines.
Execution speed: Some execution time is consumed when the
overlay run-time code in the task image must change the
mapping of the FCSRES's APR from one overlay to another, but

less time is used than with a cluster.
•

Case 3
Link to the memory-resident FCSRES and have the OTS code
present in your task image.
Link the application task with
this TKB option:
LIBR=FCSRES:RO
This is appropriate when FCSRES is necessary, but
justify having a permanent F4PRES on your system.

you

cannot

Virtual and physical memory characteristics: one APR is used
for FCSRES. The OTS code is included in the application task
image, likely thousands of bytes.
(This may need to be
overlaid.)
The task root also incurs a load of 1132 decimal
bytes: 650 decimal from FCSRES.STB (autoload vectors, segment
and region descriptors}, and 482 decimal from the overlay
run-time routines.

1-60

RSX-llM V4.l RELEASE NOTES
Execution speed: Some execution time is consumed when the
overlay run-time code in the task image must change the
mapping of resident libraries' APRs from one library to
anocner.
Mo~e
execution time is used if you overlay the OTS
code in the task image.
•

Case 4
Link to F4PRES with revectored FCS, so that FCS code is
present in your task image. This combination is never the
best choice because F4PRES and your application tasks will
include FCSJMP and FCSVEC with no benefit. However, tasks
will link and execute correctly. Link the application task
with this TKB option:
LIBR=F4PRES:RO

•

Case 5
Link to an F4PRES containing FCS.
with this TKB option:

Link the

application

task

LIBR=F4PRES:RO
This is appropriate when F4PRES is necessary; you do not need
a permanent FCSRES on your system, and no critical application
tasks would profit from the increased address space of a
clustered FCSRES and F4PRES.
This combination tends to contain more OTS code in the same
number of APRs than case 6 because only the FCS used by F4PRES
is present, leaving more room for OTS code.
If your task contains macro subroutines that use FCS, try to
use the FCS routines already contained in F4PRES, like OFNB$,
OFID$,or DELET$.
Otherwise, the task will contain large
amounts of FCS code.
Virtual and physical memory characteristics:
used.
There is no overlay overhead due
library.
Execution speed: There is no
resident library.
•

overlay

two APRs are
to the resident

overhead

due

the

Case 6
Link F4PRES to a non-memory-resident FCSRES (LIBR=FCSRES:RO in
the F4PRES TKB command file).
Link the application task to
F4PRES with this TKB option:
LIBR=F4PRES:RO
If you have a non-memory-resident FCSRES on your system, this
may be appropriate.
Note that case 5 tends to include more
OTS code in the same number of APRs.
If FCS routines are called from the task image, a space
problem can occur.
(FCS routines might be called by either
OTS code in the task image, or your macro subroutines.) FCSRES
entry points are available only to a task or resident library
linked directly to FCSRES; they are not available to a task
linked to F4PRES in this case. Thus, any FCS routine called
in your task will bring a number of FCS modules into the task
image.

1-61

RSX-llM V4.l RELEASE NOTES
Virtual and physical memory characteristics:
used.
There is no overlay overhead due
library.
Execution speed: There is no
resident library.
•

overlay

two APRs are
to the resident

overhead

due

the

Case 7
Link to a non-memory-resident FCSRES and have the OTS code
present in your task image.
Link the application task with
this TKB option:
LIBR=FCSRES:RO
This is appropriate when the non-memory-resident FCSRES is
necessary, but you cannot justify having a permanent F4PRES on
your system.
Virtual and physical memory characteristics: one APR is used
for FCSRES.
The OTS code is included in the application task
image, likely thousands of bytes.
(This may need to be
overlaid.)
Execution speed: There .is no
resident library.

1.5.11

overlay

overhead

due

the

RSX-llM/M-PLUS Executive Reference Manual

1.5.11.1 Change to Executive Directives - For the Attach Region
(ATRG$) and Create Region (CRRG$)directives, the Executive will return
the directive error status IE.PNS if the region specified in the
directive is not a common or if the common is not installed.

1.5.11.2 Corrections to Executive Reference Manual - The following
changes should be made to the RSX-llM/M-PLUS Executive Reference
All the changes apply to Chapter 5.
Manual.
On page 5-7,
the first sentence under "Macro Expansion:"
• should
read "Most of the directive descriptions expand the $
form of the macro."

• ALTP$
On page 5-11, add the following return code and definition
the list of DSW return codes:

IE.RSU -- Resource (the task's header)
unavailable because
task is checkpointed with outstanding I/O.
•

CINT$
1.

On page 5-18,
paragraph:

add

the

following

text

the

last

However, be aware that including the symbol definition
file can cause references to system subroutines to be
resolved from that file instead of from the system
library.
To avoid this problem, explicitly include the
required library
modules
before
specifying
the

1-62

RSX-llM V4.l RELEASE NOTES
Executive symbol definition file.
Specify the /SS
switch with the file so the Task Builder will resolve
any symbols that are still undefined.
(Specifying the
/SS switch prevents the Task Builder from trying to use
multiply defined symbols.)
2.

•

For corrections to the CINT$ example, beginning on page
5-25, see the June 1980 issue of the Software Dispatch,
Sequence 7.1.1.1 N, pages 79 through 84.

GCCI$
On page 5-76, the Command Buffer Format list should be in
following order:
G.CCDV
G .CCUN
G.CCCT
G.CCCL
G.CCTC
G.CCFL

the

Octal unit number of issuing terminal {l)
Number of characters (1)
Terminator (1)
Flags {l)

G.CCBF
•

GCII$
On page 5-80, add the following Local Symbol Definitions:
G.CIBF
G .CIBL
G.CICN
G .CIDV
G.CIUN

Buffer address
Buffer length
Radix-50 CLI name
ASCII terminal name
Terminal unit number

QIOW$
On page 5-116, the parameter
mandatory in the FORTRAN call.

•

efn

(event

flag

number)

RDAF$
On page 5-125, the Macro Call should define buf as the address
of a 4-word buffer.

RPOI$
1.

On pages 5-130 and 5-131, the second paragraph in the
definitions of itask and task should be changed to the
following:
On RSX-llM-PLUS systems, any task may specify a new
name for the requested task as long as the requested
task is not a CLI task.
For both systems, the requested (specified in the tname
parameter) task must be installed in the ••• tsk format.

On page 5-131, in the Macro Expansion, the line
.ASCII

/dev/

;ASCII NAME OF TI: OF REQUESTED TASK

should be the last line in the expansion.

1-63

RSX-llM V4.l RELEASE NOTES
e

RUN$
On pages 5-140 and 5-141, the smg parameter
Call and the Macro Call is mandatory.

•

the

FORTRAN

SCLI$
On page 5-148, in the Macro Expansion, the line
• RAD50

;CLI NAME

/cli/

should be the last line in the expansion.
•

SDAT$
On page 5-150, the text of the NOTE should
the following text:

replaced

with

When a local event flag is specified, the flag is set for
the sending task. When a common event flag is specified,
the flag is set for all tasks. When a group-global event
flag
is specified, the flag is set for all tasks within
the specified group.
For all event flags, a significant
event is always declared.

• SDRC$
On page 5-153, in the Macro Expansion, change the line
.BYTE

.WORD

;EVENT FLAG NUMBER = 2

and delete the line
.BYTE
•

16.

;EXIT STATUS BLOCK CONSTANT

SMSG$
1.

On page 5-163,
following lines:
Change SMSG$
Change .BYTE
Change • WORD

the

Macro

SM.ERR
DIC,8.
SM.ERR

Expansion,

change

the

to SMSG$ SM.SER
to • BYTE 1 71 , 8 •
to .WORD SM.SER

and delete from the list of Local Symbol

Definitions

the

line
S.MERR -- Error Log Target Identifier
2.

On page 5-164, change the definition of IE.ULN
to
•specified LUN is not assigned to a mass storage device.•

STIM$
On page 5-196, in
S.TISC.

the

list

1-64

offsets,

S.TICS

should

CHAPTER 2
RMS-11 VERSION 2.0 RELEASE NOTES

2.1

NEW FEATURES FOR RMS-11 VERSION 2.0

The following new features appear in the RMS-11 V2.0 access methods.

2.1.1

Support for Clustering and Task Independence

The memory-resident library RMSRES can be clustered with any other
resident library that supports clustering;
this capability allows
RMS-11 to share task virtual memory with other libraries.
See your
FMS-11 and language documentation to determine whether a particular
library supports clustering.
Task-independence means that once a program is linked with RMSRES, the
library can be rebuilt or replaced without requiring that the task
linked to it be rebuilt.
Linking with RMSRES requires use of the RMSRLX.ODL file.
Include the
element RMSROT in the .ROOT statement of your ODL file, and the
indirect reference @LB:[l,l]RMSRLX in your ODL file.
If you used
RMSRLX.ODL in this manner with Vl.8, no change should be required (if
you made reference to the RMSALL factor, this is no longer necessary
but will do no harm).
To use this library as a cluster library, you simply specify the CLSTR
option when linking the task.

2.1.2

Subset Library Support

Two versions of the RMS-11 resident library are provided. RMSRES is a
full-function
library
that
supports
all
file organizations.
RMSRESSUB.TSK is a subset library that supports access to only
sequential and relative file organizations.
(Attempts to access
indexed files using this library will result in the error code
ER$ENV.)

2.1.3

Disk-Overlaid RMS-11

New versions of the RMS-11 Vl.8 ODL
distribution kit.
These ODL files are:
•

files

are

provided

the

RMSllS. ODL
Designed to use minimal virtual address space for support of
sequential and relative file organizations, this ODL file adds
about 6.SKB to the task size.

2-1

RMS-11 VERSION 2.0 RELEASE NOTES
•

RMSllX.ODL
Designed to use minimal virtual address space for full support
of all file organizations, this ODL file is structured to add
about lOKB to the task size.

RMS12X.ODL
This ODL file adds about 12KB to the task size, supports all
file organizations, and offers a good compromise between
performance for record operations on indexed files and use of
task virtual address space.

•

RMSll.ODL.
This is a prototype ODL file that you can tailor to
needs.

your

own

The Vl.8 ODL files will still work with RMS-11 V2.0 but the new
versions of the ODL files will be more efficient, generally requiring
less memory and less disk space for the task image.
For more
information on Vl.8 comparisons, see Section 2.3.
In addition, two new ODL files are provided with V2.0:
e

RMS12S.ODL
Supporting only sequential and relative file organizations,
this ODL file adds about 9KB to the task size and is designed
to offer a good compromise between performance and use of task
virtual address space.

•

DAPllX.ODL
Structured to add about 14KB to the task size, this ODL file
is designed to use minimal virtual address space for support
of all file organizations and (on systems with the required
DECnet support) remote access facilities.

2el.4

Remote File and Record Access via DECnet

If suitable DECnet facilities exist on your system and on the target
system, RMS-11 V2.0 will allow file and record access to files
residing on other network nodes, provided that such nodes include an
RMS-11-based file access listener (FAL).
For most purposes, remote access is indistinguishable from local
access, although performance may not be equivalent. The following
general limitations apply:
•

RMS-11 generally does not support remote
not supported locally.

•

Certain RMS-11 functions (wildcard support, PARSE, SEARCH,
ENTER, REMOVE, RENAME, and transmission of device, directory,
and file identifiers) are not supported by the data access
protocol (DAP} used, and hence cannot be executed remotely.

•

Certain FALs do not support the full set of RMS-11 functions
expressible via DAP, and hence further limit remote access.
For example, the current RSTS/E RMS-11 FAL does not support
record access to indexed files.

2-2

functions

that

are

RMS-11 VERSION 2.0 RELEASE NOTES
•

High-level languages may not
specification necessary to
node.

allow expression of the file
establish contact with a remote

To operate upon a remote file, your program must include a node
specification for the remote file and you must include the RMS-11
remote access code when you build your task.

2.1.4.1 Remote Node Specification - You must include a remote node
specification at the start of the file name string or the default name
string you provide to an OPEN, CREATE, or ERASE operation.
In
addition, your file name string and default name string must conform
to the DIGITAL Command Language (DCL) file specification syntax rules,
and the file specification resulting from the merging of these two
strings must conform to the file specification conventions on the
destination system as well.
In general, a file specification consists of the
(in the order and with the delimiters shown):

following

elements

node::device:[directory]filename.type;version
where the elements beyond the node specification conform to the
conventions of the target system.
Elements not present will be
defaulted according to the conventions of the target system.
The node element is of the form:
node"user password"::
where node is the (required) destination node name and •user password•
is an (optional) access control string containing login information
acceptable to the remote system.
If •user password• is provided, the device and directory defaults and
access privileges of that remote account are acquired; if not, the
device and directory defaults and access privileges of the default
DECnet account on the remote system are acquired.

2.1.4.2 Linking Programs with RMSDAP Support - To link your program
with remote RMSDAP modules, you can either use the disk-overlaid
version or reference the DAPRES resident library:
•

To link with the disk-overlaid version,
reference
the
DAPllX.ODL file in your ODL file. As with other RMS-11 ODL
files, you reference the RMS-11 root modules as RMSROT, and
specify other RMS-11 modules as the cotree RMSALL.

•

To link with the DAPRES resident library, use the ODL file
DAPRLX, and specify RMSRES and DAPRES in your TKB command
file. RMSRES and DAPRES can be specified as single resident
libraries or as clustered resident libraries.

Note that DAPRES is a clusterable, task-independent library as defined
previously for RMSRES.

2-3

RMS-11 VERSION 2.0 RELEASE NOTES
2.1.4.3 RMSDAP
Environments - RMS-11-based
FALs
are
currently
available on VAX/VMS, RSTS/E, RSX-llM, and RSX-llM-PLUS systems. The
version of data access protocol that is used must be Version 5.6 or
later;
this means that you must have at least Version 2.0 of
DECnet/E, Version 3.1 of DECnet for RSX-llM, version 1.1 of DECnet for
RSX-llM-PLUS, or Version 2.0 of DECnet/VAX.
For more information on remote access using RMS-11, see Appendix B
the RSX-llM/M-PLUS RMS-11 User's Guide.

2.1.5

New File and Directory Operations

RMS-11 V2.0 supports several new file and directory operations.

2.1.5.1 ENTER/REMOVE - Your program can use the ENTER operation to
create a directory entry for a file~ You can delete the directory
entry for a file by using the REMOVE operation;
this operation does
not affect either the existence of the file or the file contents.

2.1.5.2 RENAME - RENAME is a new RMS-11 operation that can be used to
replace the directory entry for a file (that is, change the name of a
file). The file specification for the new directory entry must not
specify a new device or node for the file, but can specify a different
directory, file name, file type, and file version.

2.1.S.3 PARSE - PARSE is a new RMS-11 operation that can be
analyze a file specification.

used

The PARSE operation merges the file specification with the default
file specification and with the system defaults, and analyzes the
result. If you specify wildcarding, the PARSE operation constructs a
match-pattern;
this match-pattern can be used by later wildcard
SEARCH operations.

2.1.S.4 SEARCH - SEARCH is a new RMS-11 operation that can be used to
find
the
next
(or first)
file that matches a match-pattern
(constructed as the expanded string by a previous PARSE operation).

2.1.6

Wildcardin9

You specify wildcardin9 by including wildcard characters in the file
specification (or the default file specification). Wildcards can be
specified in the directory entry, file name, type, and version.
See the RSX-llM/M-PLUS RMS-11 Macro Programmer's Guide for a full
explanation
of
how
to use the new directory-C>perations and
wildcarding. You may also want to examine the demonstration programs
that are provided.

2-4

RMS-11 VERSION 2.0 RELEASE NOTES
2.1.7

Random Access to Fixed-Format Disk Sequential Files

For disk sequential files with records of fixed format, random access
for GET, FIND, and PUT operations can be specified. This kind of
random access is very similar-to random access to relative files, with
some exceptions.
Your program specifies key access by setting the RB$KEY code in the
1-byte RAC field of the RAB, and by specifying the address of a
0
relative record number 0 in the KBF field of the RAB. Key size must
be specified as 4 in the KSZ field of the RAB.
Some differences from relative file handling are the following:
e

There is no initialization of the space in the file.
If the
first operation is a random PUT to the file at relative record
number 5, the 0 cells 0 preceding record number 5 may contain
0
garbage 0 : that is, whatever data happened to be there.
(This is similar to VAX-11 RMS.)

•

There is also no maximum record number {except as limited by
the 4-byte specification of the key).
If your program
specifies a random PUT operation at relative record number
999, the file will be extended to the appropriate size (but
not initialized).

•

A PUT operation overwrites any existing record in
location.

•

There is no support for
file.

2.1.8

DELETE

operations

the
a

target

sequential

Increased Device Independence

Files with stream and VFC record formats can now be created on
unit-record devices to avoid the need for special-case code in
copy-type operations.
•

In the case of VFC files, the record header is thrown away on
output unless it is a "print format" file, which RMS-11 now
supports as VAX-11 RMS does.

•

For stream files, if none of the 3 carriage control bits is
set (print format, carriage control, or FORTRAN carriage
control), and if the last character is not a line feed, form
feed, or vertical tab, then carriage-return/line feed (CR/LF)
is appended at the end of the record.

•

For stream files, where either the carriage control or FORTRAN
carriage control attribute is set, if the last two characters
of the record are CR/LF, the trailing CR/LF is stripped off,
and then definition of the carriage control (CR or FTN)
attribute is applied.

For similar ease-of-copying reasons, RMS-11 now allows creation of
relative and indexed files for output to nondisk devices (although for
magnetic tape, record format must be variable length or fixed length).

2-5

RMS-11 VERSION 2.0 RELEASE NOTES
2.1.9

More Usable Block I/0 Facilities

The following enhancements have been made for block I/O:
•

Block I/O can now be used to copy files without
"fix up" the file header attributes.

the

need

Block I/O READ operations now generally respect the logical
EOF
header attribute
(exceptions are documented in the
RSX-llM/M-PLUS RMS-11 user's Guide and in the RSX-llM/M-PLUS
RMS-11 Macro Programmer's Guide).
I/O can also be used for sequential access, by zeroing
• Block
the RAB BKT field, allowing sequential copy and update
operations.
•

2.1.10

Extends are now performed automatically, when necessary,
during block I/O access.
The only exception is for sequential
files that are accessed write-shared. In this case, automatic
extends are not allowed because there is no mechanism for
coordinating the updating of the file header attributes.

Sharing for Relative and Indexed Files

For increased symmetry, flexibility, and compatibility with VAX-11
RMS, RMS-11 V2.0 incorporates a change to previous file sharing
semantics for relative and indexed files on RSX-llM/M-PLUS systems.
This change affects only write-accessors who specify read sharing (the
default) for record access to a relative or indexed file. Although it
is largely transparent in functional terms, in some cases it will have
a noticeable effect upon the performance of the writer.
In previous versions of RMS-11, the performance .of the writer was
dependent upon whether any write-sharing read-only accessors were
already present when the writer requested access:
1.

If such a reader was present, the writer obtained shared
access
to
the file,
although additional writers were
prohibited. RMS-11 internal algorithms did not allow the
writer to "cache" buckets unless the bucket remained locked;
this limitation affected performance for certain types of
operations.

If no such reader was present, the writer obtained exclusive
access to the file.
No subsequent RMS-11 readers could
obtain access, regardless of their sharing specifications.
RMS-11 internal algorithms allowed this writer to cache
buckets when possible, thus improving performance by reducing
disk I/O.

RMS-11 V2.0
dependency:

has

been

changed

eliminate

this

access-order

When a write-accessor specifies read-sharing
(the default),
shared access is always granted as described in (1) above.
Subsequent write-sharing readers can obtain access even if
the writer was the first to access the file.

A writer desiring the performance advantages of exclusive
access can specify "no sharing" (new for RMS-11 V2.0), in
which case access is granted as described in (2) above.

2-6

RMS-11 VERSION 2.0 RELEASE NOTES
The performance difference between case 1 and case 2 will be most
evident for sequential PUT operations to a relative file with multiple
records in each bucket, or for sequential GET/UPDATE sequences to a
relative file with multiple records per bucket or to an indexed file
by primary key.
If extra RMS-11
internal buffers are provided to
improve performance, they will be ineffective for a writer unless "no
sharing" is specified.

2.1.11

RMS-11 Utilities

2.1.11.l New File Design Utility - The RMS-11 File Design Utility
(RMSDES)
is a new utility that allows you to interactively design and
create files.
RMSDES supersedes the RMS-11 File Definition Utility
(RMSDEF) •
Some of the features of RMSDES are as follows:
•

Full RMS-11 file structure capabilities -- You can design and
create any type of RMS-11 file to contain your data records,
tailoring it to meet
your
program's
data
processing
requirements exactly.

•

Error detection -- RMSDES can detect many kinds of errors and
omissions in the attribute information you supply.
Because
RMSDES is interactive, you can correct the errors immediately,
before you create and load records into the file.

•

Saved file description -- You can save a description of a file
design for future use, whether or not you have created a file
based on the description. This is useful
if you want to
complete an unfinished file design at a later date, or modify
a file design to accommodate a new use.

•

Copied file description
RMSDES can construct a
file
description based on the attributes of an existing data file.
You can either create a new file like the existing file,
or
modify the file design before creating a new file.

•

Default calculations -- RMSDES can calculate defaults for many
attributes.

•

Extensive help facilities are provided for RMSDES.

2.1.11.2 New Features
for
RMSDSP - RMSDSP
reorganized and much more readable format.
following new features:

has
a
completely
It also includes the

•

The combination of options /BP/FU now displays more complete
information about the contents of backup container files.

•

The size field lists high block as well.

•

The protection information is "decomposed" into system, owner,
group, and world protection fields.

•

RMSDSP lists the file owner.

2-7

RMS-11 VERSION ·2.0 RELEASE NOTES
2.1.11.3 New Features for RMSCNV - RMSCNV has been rewritten and is
smaller and generally faster than the 1.8 version.
It has the
following new features:
•

The /CA switch can be used to dynamically create an output
file, by copying file attributes from another file.
(That is,
you do not need to run RMSDES or RMSDEF to create the output
file before doing the conversion if you already have a
prototype file whose attributes can be copied for the output
file.)

•

The /IM switch can be used to
mode.

•

The /EO switch can be used to change ASCII stream files that
end with a CTRL/Z character to end with null characters.
This
switch is provided for help in converting certain non-RMS-11
stream files into a format readable by RMS-11 V2.0.
(See also
Section 2.3.6, Other RMS-11 version 1.8 Compatibility Notes.)

•

The /KN:keyname switch can be used to convert files based on a
key name {as opposed to a key number, as in the /KR switch).

•

The /ML switch allows you
memory allocation.

•

The /SL switch, summary listing, has been significantly
enhanced.
It now produces several summaries: summaries of
options used for the conversion, summaries of the file
attributes for the files involved in the conversion, a message
summary of errors and warnings, and a processing summary.

•

Remote
access
capability
is
provided
for
suitable
configurations.
Your system and the target system must
include DECnet support
(at least V2.0 of DECnet/E).
The
target system must also include an RMS-11-based file access
listener (FAL), and you must rebuild RMSCNV to include the
remote
access
capability
(see
Section 2.8.3, Utility
Configurations) •

2.1.11.4
•

copy

files

explicitly

set

image

the

(block)

limit

Additional Utility Features RMS!FL has been rewritten and incorporates
fixes.

number

bug

In addition, the algorithms for allocating work file space for
sorting have been changed;
in most cases, the amount of space
needed for the sort should be decreased.
The /DE switch has been enhanced to allow specification
different device for RMSIFL's temporary files.

•

Command and ODL files are provided for rebuilding the RMS-11
utilities to use different forms of the RMS-11 access methods.
See Section 2.8.3, Utility Configurations.

•

All utilities
displays.

format

for

messages

•

The error message format has been changed
except RMSDEF and RMSIFL.

for

all

now

use

lowercase

2-8

and

utilities

RMS-11 VERSION 2.0 RELEASE NOTES
2.2

SUMMARIES OF TECHNICAL CHANGES

The following sections summarize the new software features for RMS-11.
The summaries of technical changes also appear in the front matter of
each manual.
The title of each manual is followed by a letter
the manual is a new {N) or revised {R) version.

indicating

whether

In addition to the new and revised manuals listed in the following
sections, the RMS-11 V2.0 documentation set includes a new manual,
RSX-llM/M-PLUS RMS-11:
An Introduction, which introduces RMS-11
concepts, terminology, and operations.
The RSX-llM Mini-Reference
also contains a new section on RMS-11 utilities and error codes.
NOTE
All new RMS-11 features
are
fully
accessible only to MACR0-11 programmers.
See
your
high-level
language
documentation for supported features.

2.2.1

RSX-llM/M-PLUS RMS-11 User's Guide (R)

This revision of the RSX-llM/M-PLUS RMS-11 User's Guide documents
following technical changes:

the

•

RMS-11 Version 2.0 supports random access to fixed-format disk
sequential files and sequential block access to disk files of
any format and organization.

•

The RMS-11 Version
2.0
resident
libraries
are
task
independent.
This means that once a program is linked with
this library, the library can be rebuilt or replaced without
requiring that the task linked to it be rebuilt.

RMS-11 Version 2.0 contains no
• RMS
SEQ memory-resident library

library equivalent to the
included with RMS-11 Version
1.8. The RM SR ES resident library or the disk-resident ODL
files can be used to obtain equivalent functionality and
performance.

•

New versions of the RMS-11 Version 1.8 ODL files are provided.
These ODL files are RMSllS.ODL, RMSllX.ODL, RMS12X.ODL, and
RMSll.ODL. The Version 1.8 ODL files will still work with
Version 2.0, but the new versions will be more efficient.
RMS-11 Vl.8 ODL structures other than RMSllS.ODL, RMSllX.ODL,
and RMS12X.ODL may not work correctly with the RMS-11 V2.0
code; when in doubt, verify them by comparison with the V2.0
RMSll.ODL file.
In addition, two new ODL files are provided
with Version 2.0: RMS12S.ODL and DAPllX.ODL.

•

Files with stream and VFC records can now be created on
unit-record devices to avoid the need for special-case code in
copy-type operations.
For VFC files, the record header is thrown away
unless the file is a "print format" file.

2-9

output

RMS-11 VERSION 2.0 RELEASE NOTES
For stream files, if none of the 3 carriage control bits is
set (print format, carriage control, or FORTRAN carriage
control), and if the last character is not a linefeed,
formfeed, or vertical tab, the carriage-return/linefeed
(CR/LF) is appended at the end of the record.
For stream files, if either the carriage control or FORTRAN
carriage control attribute is set, and if the last 2
characters of the record are CR/LF, the trailing CR/LF is
stripped off and then definition of the carriage control
attribute (CR or FTN) is applied.
•

For similar ease-of-copying reasons, RMS-11
now
allows
creation of relative and indexed files for output to nondisk
devices (for magnetic tape, however, the record format must be
variable length or fixed length) •

•

The RMS-11 File Design Utility (RMSDES) is a new utility that
allows you to design and create files interactively. It is
fully documented in the RSX-llM/M-PLUS RMS-11
Utilities
manual.

•

RMS-11 version 2.0 supports five new directory operations:
ENTER, PARSE, REMOVE, RENAME, and SEARCH. These operations
are fully documented in the RSX-llM/M-PLUS RMS-11 Macro
Programmer's Guide.

•

RMS-11 Version 2.0 supports a new wildcard file specification
facility and a new print-record output handling format. These
are also fully documented in the macro programmer's guide.

•

User-provided interlocks allow a special, limited form of
sequential file sharing among a group of accessors that
includes at most one read/write accessor and any number of
read-only accessors.

•

If suitable DECnet facilities exist on your system and on the
target system, RMS-11 Version 2.0 will allow file and record
access to files on remote network nodes, if those nodes
include an RMS-11-based file access listener (FAL).

•

For magnetic tape, RMS-11 now allows fixed-format
be less than 18 bytes.

Files with stream or VFC records can now be created on
unit-record devices.
In addition, RMS-11 now allows the
creation of relative and indexed files for output to nondisk
devices, although they will be treated as sequential files.

records

and <ESC> are no longer recognized as
record
• <CTRL/Z>
terminators for stream files, and <CTRL/Z> is no longer
recognized as a file terminator for stream files.
•

RMS-11 Version 2.0 pads stream files with null characters, to
the high block of the file (not just to the end of the current
block) •

•

The memory-resident library RMSRES can be clustered
other resident library that supports clustering.

with

•

An optional subset library, containing support for
and relative files only, is available.

sequential

2-10

any

RMS-11 VERSION 2.0 RELEASE NOTES
2.2.2

RSX-llM/M-PLUS RMS-11 Macro Programmer's Guide (R)

This revision of the RSX-llM/M-PL-US RMS-11
documents the following technical changes:

Macro

Programmer's

Guide

The new operation macros $ENTER, $PARSE, $REMOVE, $RENAME,
and $SEARCH are documented, along with the related NAM block
fields FNB, RSA, RSL, and RSS.

•

The new facility
documented.

•

The extension of access sharing is documented, along with the
related masks FB$UPI and FB$NIL for the SHR field of the FAB.

•

Random access to a sequential file with fixed-length records
(similar to random access to a relative file) is documented.

•

The new print-format record-output handling is documented,
along with the related symbol FB$PRN for the RAT field of the
FAB.

•

The new sequential block access is documented; the previous
block access (formerly called block I/O) is now called VBN
access (virtual block number access).

•

Block access can now be used to copy RMS-11 files without the
need to modify the file's attributes manually.

•

The addition of the success handler facility for file
operation macros ($CLOSE, $CREATE, $DISPLAY, $ERASE, $EXTEND,
and $OPEN) is documented.

•

Increased device transparency for
record
access
copy
operations is supported. VFC and stream record formats are
supported on unit-record devices. Relative and indexed files
can be created for record access on nondisk devices, although
they will appear as and be processed as sequential files
there.

•

The obsolete RMS-11 initialization macros $INIT and $INITIF
are no longer documented. These macros are now defined as
no-ops in the RMS-11 macro library RMSMAC.MLB;
their
previous functions are no longer needed because RMS-11 is now
self-initializing. However, programs that use the $!NIT and
$INITIF macros in their previous senses remain valid under
RMS-11 Version 2.0.

for

wildcard

file

Each XAB type now has a distinct name;
• new
names:
ALL block
DAT block
KEY block
PRO block
SUM block

specification

the following are the

Area allocation XAB
File date XAB
File key XAB
File protection XAB
File summary XAB

• The following symbol declaration macros are documented:
FAB$BT
NAM$BT
RAB$BT
XAB$BT
XBAOF$

XBDOF$
XBKOF$

Declare FAB value and mask symbols
Declare NAM block value and mask symbols
Declare RAB value and mask symbols
Declare XAB value and mask symbols
L., - _,_
Declare nJ...J... JJ.J.UI.,;""
symbols
Declare DAT block symbols
Declare KEY block symbols
1' TT

2-11

RMS-11 VERSION 2.0 RELEASE NOTES
XBPOF$
XBSOF$

Declare PRO block symbols
Declare SUM block symbols

•

The description of each operation macro includes the use
meaning of each associated control block field.

•

The value of each RMS-11 user symbol is documented.

•

The structure
documented.

each

RMS-11

user

control

block

and

field for
FAB has a new LRL (longest record length)
• The
sequential files (corresponding to the VAX-11 RMS XAB LRL
field) •
•

The date/time XABs have changed in size from 36 to
bytes.

•

For ANSI magnetic tape, RMS-11 allows fixed-format records to
be less than 18 bytes.

•

<CTRL/Z> and <ESC> are no longer recognized as record
terminators for stream files;
and <CTRL/Z> is no longer
recognized as a file terminator for stream files.

•

RMS-11 now pads stream files with null characters to the high
block of the file (not just to the end of the current block).
This means that RMS-11-created stream files can be read by
programs that do not recognize the EOF value from the file
header.

2.2.3

octal

RSX-llM/M-PLUS RMS-11 Utilities (N)

The RSX-llM/M-PLUS RMS-11 Utilities manual is a new manual for this
release, replacing Chapter 9 of the RMS-11 User's Guide for RMS-11
Version 1.8. It documents the following technical changes:
e

The RMS-11 File Design Utility (RMSDES) is a new utility that
allows you to interactively design and create files. RMSDES
supersedes the RMS-ii File Definition Utility (RMSDEF).

The RMS-11 File Display Utility (RMSDSP)
provides more
information about magnetic tape files and about backup files
on disk and on magnetic tape (container files), and provides
an optional detailed display for backup files. The displays
also appear in a more readable format, and the size field
shows both the allocated and used sizes of the file.

The /DE switch to the RMS-11 Indexed File Load Utility
(RMSIFL) has been enhanced to allow specification of a
different device for RMSIFL's temporary files.

•

The /SL switch to the RMS-11 File Conversion
Utility
(RMSCNV), the File Back-Up Utility (RMSBCK), and the File
Restoration Utility {RMSRST) has been modified to append
summary listings of processing to a single file if that file
exists.

•

Five switches have been added to the RMS-11 File Conversion
Utility (RMSCNV):
the /CA switch, the /EO switch, the /IM
switch, the /KN switch, and the /ML switch. The /CA switch
creates au output file with the attributes of an existing
file; the /EO switch changes ASCII stream files that end
2-12

RMS-11 VERSION 2.0 RELEASE NOTES
with a CTRL/Z character to end with null characters;
the /IM
switch reads and writes records in block mode;
the /KN
switch reads an indexed file using a key name;
and the /ML
switch explicitly sets the limit of memory allocatione
The
/PD switch no longer requires a number sign (i) before an
octal padding character or quotation marks around an ASCII
padding character unless it is a lowercase character, a
space, or a tab.
•

In addition, RMSCNV file conversion operations can now
specify files on remote nodes.
On systems with DECnet
network capabilities and on which RMSCNV has Data Access
Protocol
(DAP)
support, RMSCNV file conversions can take
place not only locally, but over the network as well.
You
can convert files between a local and a remote node, or
between two remote nodes.

•

One switch has been added to the RMS-11 File Restoration
Utility (RMSRST): /CV. The /CV switch converts file version
numbers from octal to decimal for files created and backed up
on RSX-llM/M-PLUS systems and restored to VAX/VMS systems;
and from decimal to octal for files created and backed up on
VAX/VMS systems and restored to RSX-llM/M-PLUS systems.

utilities now display information in lowercase letters,
• All
and the error message format for all utilities (except
RMSDEF) has been changed.

2.3

COMPARISONS WITH RMS-11 VERSION 1.8

Conversion from RMS-11 Vl.8 to RMS-11 V2.0 has been made transparent
where possible.
Structural changes required by eeature additions,
however, may be significant to some programs.

2.3.1

Memory-Resident Library (RMSRES)

RMSRES now contains all RMS-11 support code
code in the task. The library is also:

save

for

minor

linkage

•

"Task-independent," which means that it can be rebuilt
replaced and the tasks that use it need not be rebuilt

•

"Clusterable," which means that it can share task virtual
memory with other libraries that support "clustering• (see
your FMS and language documentation)

These features required changes in the RMSRLX.ODL file,
the file
normally used to build tasks using RMSRES. Tasks that used RMSRLX.ODL
with RMS-11 Vl.8 should continue to build properly using the new
RMSRLX.ODL and RMSRES. Build files that used RMSRES but did not use
RMSRLX.ODL with RMS-11 Vl.8 must be changed to use (or incorporate the
contents of) the new RMSRLX.ODL file.

2.3.2

Me•ory-Resident Library (RMSSEQ)

RMS-11 V2.0 contains
no
library
equivalent
to
the
RMSSEQ
memory-resident library included with RMS-11 Vl.8. RMSSEQ offered no
advantages in use of task virtual memory, and no advantages in use of
system physical memory which are not equally attainable through use of
2-13

RMS-11 VERSION 2.0 RELEASE NOTES
disk-overlaid RMS-11 at negligible performance cost.
In addition,
structural constraints made it impossible for RMSSEQ to be clusterable
or task-independent.
The improved packaging of the full-function library RMSRES should make
it a suitable replacement for RMSSEQ in most environments. Where this
is inappropriate, disk-overlaid or non-overlaid RMS-11 can be used.

2.3.3

Memory-Resident Library (DAPRES)

If your system includes the necessary DECnet facilities, the new
resident library DAPRES provides support for remote file and record
access as well as local access.
Like RMSRES, DAPRES is both
task-independent and clusterable.
In particular, a task using RMSRES
may include remote-access support via DAPRES with negligible increase
in task virtual address space requirement by clustering the two
libraries: the file DAPRLX.ODL should be used to generate this
configuration.

2.3.4

Disk-Overlaid RMS-11

Structural changes to the RMS-11 code were performed so that the
RMS-11 Vl.8 ODL files RMSllX, RMS12X, and RMSllS would remain valid.
Most other ODL structures will probably continue to be valid, although
validity cannot be guaranteed for all cases.
Use of Vl.8 ODL
structures with V2.0 code may require more task virtual address space
than with Vl.8 code.
The new versions of RMSllX, RMS12X, and RMSllS use approximately the
same (or slightly less)
task virtual address space as their Vl.8
counterparts used with the Vl.8 code.
If your system includes the
necessary DECnet facilities, the new file DAPllX.ODL provides support
for remote file and record access as well as local access.
The ODL MAKRMSODL.CMD is not provided and should not be used with V2.0
of RMS-11.
However, a prototype ODL file, RMSll.ODL, is provided, and
contains extensive comments. This file is not meant to be used
directly; but may be helpful in designing your own ODL structures or
in modifying the structure of the above ODL files to suit your special
needs.
A restriction on ODL structures involves the RMS-11 entry point
modules ROxxxx (where xxxx represents the leading characters of the
RMS-11 operation name, for example, ROPUT). These modules, which were
not explicitly referred to in previous RMS-11 ODL files, must not be
referred to in RMS-11 ODL files for V2.0;
if they are, a multiple
definition for symbols of the form $RMxxx will occure

2.3.5

Non-Overlaid RMS-11

While the total end-to-end size of RMS-11 has decreased despite
addition of new features, the space savings and feature additions have
not been spread evenly throughout. Most of the added features have
occurred
in the areas of file/directory operations and record
operations for sequential files.

2-14

RMS-11 VERSION 2.0 RELEASE NOTES
The result is that applications using non-overlaid RMS-11
for
sequential-file-only access may experience an increase in virtual
address space requirements for the RMS-11 code.
If this presents a
proo1em,
it
should normaiiy be possible to select a suitable RMS-11
disk-overlay structure without noticeable performance impact.

2.3.6

Other RMS-11 Version 1.8 Compatibility Notes
•

The utility RMSDFN is no longer supported.

•

There is no longer a distinction between "standard" RMS-11 and
"llK"
RMS-11.
All RSX-llM/M-PLUS systems automatically
include the appropriate files needed for RMS-11,
including
indexed support.

•

Programs that have been compiled under RMS-11 Vl.8 should in
virtually
all
cases
still
run
under
V2.0, without
recompilation when relinked. Such programs, however, will not
be able to take advantage of any new features in Version 2.0
of RMS-11.

•

Tasks already built using RMS-11 Vl.8 should continue to run
correctly (without rebuilding) on RSX-llM V4.l.
However, it
is possible that RMS-11 Vl.8 (or prior) tasks will not execute
correctly on versions of RSX-llM after V4.l.
RMS-11 V2.0 has
been implemented to anticipate this possible change
in
RSX-llM:
this allows you one full release cycle to convert
any such tasks to RMS-11 V2.0.

•

In general, RMS-11 V2.0 cannot be run on a previous version of
RSX-llM.
RMS-11 V2.0 depends on new features included in the FllACP and
on the new structure of TKB autoload vectors in V4.l of
RSX-llM;
do not try to use old versions of TKB to link RMS-11
V2.0 programs.
Note: The reverse situation can also cause certain problems.
Because of the change in TKB autoload vector format, a task
that was linked with new TKB but old RMS-11 (Vl.8 or before),
and
that
uses
RMS-11
asynchronously,
will
behave
unpredictably.

•

With RMS-11 V2.0, some changes to the SYSLIB modules have been
made;
several modules have been placed in SYSLIB to maintain
compatibility with previous releases.
As a result, you must be careful to reference RMSLIB as a
"search"
library before referring to SYSLIB when building
tasks that use non-overlaid RMS-11.
(This is only necessary
if you need to make an explicit reference to SYSLIB as a
"search" library when task-building.)

•

MACR0-11 programs using RMS-11 should always check for
by checking the value of the appropriate STS field.

errors

With Vl.8, the C-bit may have been returned on RMS-11 errors.
However,
this is not a defined error return and has not been
maintained in RMS-11 v2.o.
and <ESC> are no longer
• <CTRL/Z>
terminators for stream files,
and

recognized as
record
<CTRL/Z>
is no longer
recognized as a file terminator for stream files.

2-15

RMS-11 VERSION 2.0 RELEASE NOTES
Note that RMSCNV has a new switch, /EO, which can be used to
convert stream files which were created by a non-RMS-11
program, and which used <CTRL/Z> as the file terminator.

2.4

•

The expanded string is now an output from the OPEN
operations by file-id.

•

RMS-11 now makes a check that at least 2 keys fit into a
bucket.
Therefore, with a bucket size of 1, the maximum key
size is 243.

•

When block I/O is used, OPEN and DISPLAY operations no longer
return relative or indexed file key XAB, allocation XAB, or
summary XAB information.

ERASE

MISCELLANEOUS INFORMATION
•

Note that all the new features provided in RMS-11 are fully
accessible only to the MACR0-11 programmer;
for high-level
languages, check the language documentation for supported
features.

•

For magnetic tape, RMS-11 now allows ANSI fixed format tape
records to be less than 18 bytes.
In addition, RMS-11
supports the full set of ANSI tape names as quoted strings.
This includes the full set of ANSI 'a' characters, up to 17
bytes.

•

Several RMS-11 demonstration programs have been included on
the distribution kit. These sample programs are provided as
MACR0-11 sources and task images; they illustrate how to use
the new PARSE/SEARCH/RENAME/ERASE operations and wildcarding
facilities.
A GSA source routine is also included
to
illustrate how to extend the task in the event of RMS-11 pool
exhaustion.
The names of the programs are PARSE,
and GSA.

•

2.5

and

SEARCH,

RENAME,

ERASE,

The RMSIFL and RMSDES utilities and the remote access (DAP)
support code in RMS-11 V2.0 will run only on CPUs that support
the EIS instruction set.

PROBLEMS FIXED WITH RJllS-11 VERSION 2.0
•

The problem that was reported for RMS-11 Vl.8 on GET after
FIND on alternate keys (Dispatch article number 48.2.20) has
been fixed for RMS-11 V2.0.

•

RMSIFL Vl.8 did not load indexed files correctly if the key
type was integer.
{Not all records could be accessed by key
value.) This problem has been fixed in the new version of
RMSIFL.

•

RMS-11 now pads stream files with nulls, to the high block of
the file
(not just to the end of the current block}. This
will make RMS-11-created stream files readable by programs
that do not recognize the EOF value from the file header.

2-16

RMS-11 VERSION 2.0 RELEASE NOTES
2.6

KNOWN PROBLEMS WITH RMS-11 VERSION 2.0
•

Under some circumstances, the deferred

write

option

may

cause

the

;rrl"\t"\r'O~
."='
... . . , ... _.....,.

2.7

•

Use of the mass-insertion feature may occasionally
error ER$DME.

•

When you use RMSDES and specify a GET command, RMSDES
incorrectly requests write access on the GET file.
In some
cases, an ER$FLK or ER$PRV error may result if your task does
not have write access to the file.

RMS-11 FILES AND PLACEMENT ON THE DISTRIBUTION KIT

File Name

Destination

Comments

RMSMAC.MLB

LB: [ l, 1]

RMSLIB.OLB

LB: [ 1, 1]

RMSDAP.OLB

LB: [ 1, 1]

Can be deleted if you are not using
MACR0-11 RMS-11 programs.
Object library for RMS-11 local
access.
Object library for RMS-11 remote
access. Can be deleted if you do
not need remote access.

RMSBCK.TSK

LB: [ 1, 54]

RMSRST.TSK

LB: [1,54]

RMSDEF.TSK

LB: [1,54]

RMSDSP. TSK

LB: [ 1, 54]

RMSCNV.TSK

LB: [ 1, 54]

RMSDES.TSK

LB: [ 1, 54]

RMSIFL.TSK

LB: [ 1, 54]

RMSDES.IDX

LB: [ 1, 2]

Indexed help file used by RMSDES.

RMSll. ODL
RORMSl .MAC
RMSllS. ODL
RMS12S.ODL
RMSllX. ODL
RMS12X.ODL
RMSRLX.ODL
DAPllX. ODL
DAPRLX.ODL

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

Prototype ODL file.
For use with the prototype ODL.
ODL file for sequential.
ODL file for sequential.
Standard indexed file ODL.
Indexed file ODL.
ODL for use with RMSRES.
ODL for use with overlaid RMSDAP.
ODL for use with DAPRES.

RMSRES.TSK

LB: [ 1, 1]

RMSRES.STB
RMSRES.MAP

LB: [ 1, 1]
LB: [ 1 , 3 4]

TSK image for linking against
RMSRES.
STB file for RMSRES.
Map file for RMSRES.

RMSBCK utility;
RMSRES.
RMSRST utility;
RMSRES.
RMSDEF utility;
RMSRES.
RMSDSP utility;
RMSRES.
RMSCNV utility;
RMSRES.
RMSDES utility;
RMSRES.
RMSIFL utility;
RMSRES.

does not use
does not use
does not use
does not use
does not use
does not use
does not use

(Continued on next page)

2-17

Rl'IS-11 VERSION 2.0 RELEASE NOTES
File Name

Destination

Comments

RMSRESSUB.TSK
RMSRESSUB.MAP

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

Subset library.
Map file for subset library.

DAPRES. TSK

LB: [1,1]

DAPRES.STB
DAPRES.MAP

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

Task image for RMSDAP resident
library.
STB file for DAPRES.

RMSRES.CMD,
RMSRES.ODL

LB: [l, 24]

For rebuilding RMSRES.

DAPRES.CMD,
DAPRES.ODL

LB: [l, 24]

For rebuilding DAPRES.

BCKNON.CMD,
BCKNON.ODL
BCKNRN.CMD,
BCKNRN.ODL

LB: [l, 24]

For rebuilding the overlaid
version of RMSBCK.
For rebuilding the residentlibrary version of RMSBCK.

CNVNON.CMD,
CNVNON.ODL
CNVNRN.CMD,
CNVNRN.ODL
CNVNOO.CMD,
CNVNOO.ODL
CNVNRR.CMD,
CNVNRR.ODL

LB: [1,24]

LB: [l I 24]

LB: [l, 24]
LB: [l, 24]
LB: [l, 24]

DEFNON.CMD,
DEFNON.ODL
DEFNRN.CMD,
DEFNRN.ODL

LB: [ 1, 24]

DESNON.CMD,
DESNON.ODL
DESNRN.CMD,
DESNRN.ODL,
RMSDES.ODL

LB: [1,24]

DSPNON. CMD,
DSPNON.ODL
DSPNRN.CMD,
DSPNRN.ODL

LB: [l, 24]

LB: [1,24]

LB: [ 1, 24]

I FLNON. CMD,
IFLNON.ODL
IF LN RN • CM D,
IFLNRN.ODL

LB: [ 1, 24]

RSTNON.CMD,
RSTNON.ODL
RSTNRN.CMD,
RSTNRN.ODL

LB: [ 1, 24]

RMSUTL.OLB,
RMSODL.ODL

LB: [ 1, 24]

For rebuilding the overlaid
version of RMSCNV.
For rebuilding the residentlibrary version of RMSCNV.
For rebuilding the overlaid
version of RMSCNV, with RMSDAP.
For rebuilding the residentlibrary version of RMSCNV,with
RMSDAP.
For rebuilding the overlaid
version of RMSDEF.
For rebuilding the residentlibrary version of RMSDEF.
For rebuilding the overlaid
version of RMSDES.
For rebuilding the residentlibrary version of RMSDES.
For rebuilding the overlaid
version of RMSDSP.
For rebuilding the residentlibrary version of RMSDSP.
For rebuilding the overlaid
version of RMSIFL.
For rebuilding the residentlibrary version of RMSIFL.
For rebuilding the overlaid
version of RMSRST.
For rebuilding the residentlibrary version of RMSRST.
For rebuilding several utilities.

(Continued on next page)

2-18

RMS-11 VERSION 2.0 RELEASE MOTES
File Name

Destination

Comments

GSA.MAC

LB: [200 I l]

PARSE.MAC,
SEARCH.MAC,
RENAME.MAC,
ERASE.MAC,
PARSE.TSK,
SEARCH.TSK,
RENAME.TSK,
ERASE.TSK

LB: [200I1]

Demonstration program included
as an illustration of how to extend
an RMS-11 task in the event
of pool exhaustion.
Demonstration programs for the
new directory and wildcarding
facilities.

Note that all RMSDAP files can be deleted if you are not using
to access files on remote nodes.

2.8

RMS-11

RMS-11 VERSION 2.0 INSTALLATION

On most RSX-llM systems, all RMS-11 files are
system after system generation.

automatically

your

However, for systems that were generated using distribution kits on
RLOl/02 or RK06/07 disks or the magnetic tape versions of these kits,
the RMS-11 files must be transfer~ed after system generation. If your
system was not generated using one of these kits, you may want to skip
this section, and continue with Section 2.8.2, Startup Command
Procedures.

2.8.1

RLOl/02 and RK06/07 Procedures

To transfer RMS-11 files to RLOl/02 and RK06/07
execute the command procedure [l,2]RMSINSTAL.CMD.
fully documented in the RSX-llM System Generation
Guide.

2.8.2

disks, you must
This procedure is
and Installation

Startup Command Procedures

If all the RMS-11 files have been transferred to your system, all that
remains to be done is to install the resident libraries and RMS-11
utilities at system startup. To aid you in installing them, the file
LB: [l,2]STARTUP.CMD contains sample comments that can be edited to
become system startup commands.
You must allocate a partition for each resident library you are using,
using the SET command(s).
Note that you must allocate a partition
called RMSRES, and install in that partition either the full-function
resident library (RMSRES) or the subset library (RMSRESSUB.TSK). If
you always plan to use the same library (no alternating between the
full-function and the subset library), and you want to save disk
space, you can delete the task image you are not using.
But, if you delete the full-function RMSRES.TSK and plan to use
RMSRESSUB.TSK, you should rename RMSRESSUB.TSK to RMSRES.TSK.
user programs and RMS-11 utilities will always link against the
named RMSRES.

2-19

only
Then
task

RMS-11 VERSION 2.0 RELEASE NOTES
NOTE
If you are using the subset library and
you rebuild the RMS-11 utilities to use
the subset library, utility functions
involving
indexed
files
will
be
invalidated.

You can include the SET commands in your startup command file, or you
may want to include the RMSRES and DAPRES partitions permanently in
your system by doing the following:
•

Using the SET commands to include the necessary partitions.

•

Using the INSTALL commands to install the tasks in the running
system.

•

Using the SAVE command to save
system image.

RMSRES

and

DAPRES

into

the

See your RSX-llM/M-PLUS MCR Operations
these commands.

Manual

for

details

2.8.3

Utility Configurations

The RMS-11 utilities that are provided on
built to use disk-overlaid RMS-11.

the

distribution

kit

are

2.8.3.1 Utility Command and ODL Files - For each utility, a command
and ODL file is provided which can be used to build the utility using
disk-overlaid &~S-11. The names of the files are the following:
For RMSBCK:
For RMSRST:
For RMSCNV:
For RMSDSP:
For RMSDES:
For RMSDEF:
For RMSIFL:

BCKNON.CMD,BCKNON.ODL,RMSODL.ODL
RSTNON.CMD,RSTNON.ODL,RMSODL.ODL
CNVNON.CMD,CNVNON.ODL
DSPNON.CMD,DSPNON.ODL,RMSODL.ODL
DESNON.CMD,DESNON.ODL,RMSDES.ODL
DEFNON.CMD,DEFNON.ODL,RMSODL.ODL
IFLNON.CMD,IFLNON.ODL

For RMSCNV, two additional configurations are available, if you want
to use RMSCNV to access files on remote nodes. To build RMSCNV using
the clustered RMS-11 and RMSDAP resident libraries, you can use
For RMSCNV:

CNVNRR.CMD,CNVNRR.ODL

To build RMSCNV using disk-overlaid RMS-11 and RMSDAP, you can use
For RMSCNV:

CNVNOO.CMD,CNVNOO.ODL

2-20

RMS-11 VERSION 2.0 RELEASE NOTES
For each utility, a command and ODL file are provided which can be
used to build the utility using the resident library RMSRES. The
names of the files are the following:
For
For
For
For
For
For
For

RMSBCK:
RMSRST:
RMSCNV:
RMSDSP:
RMSDES:
RMSDEF:
RMSIFL:

BCKNRN.CMD,BCKNRN.ODL
RSTNRN.CMD,RSTNRN.ODL
CNVNRN.CMD,CNVNRN.ODL
DSPNRN.CMD,DSPNRN.ODL
DESNRN.CMD,DESNRN.ODL
DEFNRN.CMD,DEFNRN.ODL
IFLNRN.CMD,IFLNRN.ODL

2.8.3.2 Rebuilding the Utilities - To rebuild the utilities, you must
take the following 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
current account;
you may then want to put the utility in a system
account ([1,54]).
Each command file for a particular utility creates a utility of the
correct name.
So, for example, CNVNRN.CMD and CNVNON.CMD both produce
task images called RMSCNV.TSK; one is built against the resident
library and one is built with disk-overlaid RMS-11.
Finally, note that the RMSIFL utility command files include an EXTTSK
value that is used to increase the size of internal buffers, thereby
allowing RMSIFL to load larger-sized files and files with many area
and key definitions.
The default EXTTSK which is specified is fairly large. If you want a
smaller version of RMSIFL, you can simply install RMSIFL with a
smaller increment using the /INC switch.
The /INC switch will
override the EXTTSK directive.
The EXTTSK value however, must be greater than 2048
If the value is too small, you may get the
exhausted," or a SORTs error code.

2.9

(decimal)
words.
error "IFL memory

REPORTING PROBLEMS

Software Performance Reports {SPRs) allow you to report any problems
directly to DIGITAL. The general procedure for submitting an SPR is
described in Sections 1.4 and 1.4.1.
The following additional
information should be submitted with SPRs on RMS-11:
1.

Include the version number and patch level of the RMS-11 that
you are using.

Indicate whether you are using a programming language to
process the file(s) and include the version number and patch
level of the language.

2-21

RMS-11 VERSION 2.0 RELEASE NOTES

If RMS-11 abo.rts (or if some other task crashes and RMS-11
appears to be the cause) , include a post-mortem dump and a
map of the task involved.

Include copy(s) of the file(s)

If the errors are reproducible, include copies of the files
that
can
cause
the
error.
If the problem is not
reproducible, include a copy of the corrupt file if possible.

For RMS-11 utilities, include also a description of the
command line(s) or interactive session that led to the error.
Include a listing of
possible.

the

involved, in RMSBCK format.

actual

2-22

error

that

occurred,

CHAPTER 3
RSX-11S VERSION 4.1 RELEASE NOTES

CHAPTER 3
RSX-llS VERSION 4.1 RELEASE NOTES

3.1

NEW FEATURES FOR RSX-llS V4.l

RSX-llS V4.l software is an update of the memory-resident RSX-llS
operating system~
The major new functions of RSX-118 V4.l are
documented in the following sections.

3.1.1

New Devices

RSX-llS V4.l supports the same new devices that RSX-llM V4.l supports.

3.2

NOTES ON SOFTWARE

The following sections describe incompatibilities that exist between
RSX-llS
V4.l
and
previous versions and provide miscellaneous
information.

3.2.1

Host Hardware Configuration Requirements for RSX-llS SYSGEN

To do an R8X-118 SYSGEN, the host system must be mapped
least 64K words of memory.

3.2.2

and

have

Fixing Tasks on RSX-llS with PLAS Support

To correct problems caused by the logic in VMR that determines whether
tasks are overlaid or nonoverlaid, VMR now has a new method for
determining how tasks (regardless of whether they are overlaid or
nonoverlaid) are fixed into memory.
Instead of using two different methods to fix tasks into memory as in
previous releases, VMR now requires that all tasks in a RSX-llS system
with PLAS support be fixed by issuing the following VMR command line:
VMR>INS task/FIX=YES
Using the VMR INSTALL /FIX command provides access to the label block,
thus allowing VMR to determine whether the task is overlaid or not.
Note that this is a significant change from the way tasks were fixed
in PLAS systems in previous releases.
Only the memory-resident
overlaid tasks had to be fixed using this command;
now all tasks in
the PLAS system must be fixed using the VMR INSTALL /FIX command.

3-1

RSX-llS VERSION 4.1 RELEASE NOTES
3.2.3

VMR Support for Systems Larger than 124.K Words

VMR for RSX-llM V4.0 did not support fixing tasks above the 124.K word
limit even though RSX-llS V4.0 contained support for systems larger
than 124.K words. VMR for RSX-llM V4.l now contains limited support
for systems larger than 124.K words. This limited support will enable
you to do the following:
•

Fix tasks above the 124.K word limit (using FIX)

•

Load drivers above the 124.K word limit (using LOAD)

•

Install commons above the 124.K word limit (using INS)

However, the support is limited, and there are two restrictions
must be adhered to:

which

•

llSGEN still creates a maximum system
image
file
of
498(decimal) blocks for a system of 124.K words. To fix tasks
above 124.K words, you must first create another copy of the
system image file large enough for the system size.

•

The VMR SAV command still can only be used for systems smaller
than 124.K words.

3.2.4

RSX-llS System Generation

3.2.4.1 Performing an RSX-llS V4.l
System
Generation
on
an
RSX-llM-PLUS Vl.O Host - If you intend to
perform
an
RSX-llS
V4.l system generation while running under an RSX-llM-PLUS Vl.O
system,
you
must
update
the
Vl.O
indirect object library
([l,24]IND.OLB), and rebuild indirect before performing the system
generation.

A concatenated object file, INDFIX.OBJ, is in UFD (1,54] of the
RSX-llS distribution kit.
(This object file is on the first volume in
multimedia kits.) Refer to Section 1.3.2.1 of these Release Notes for
more information on this file.
The procedure for updating is as follows:
1.

Set the UIC to [1,24].

Copy INDFIX.OBJ to the disk that has IND.OLB.

Issue the following command:
LBR IND/RP=INDFIX

Assign the logical
devices.

Verify that RSXllM.STB resides in [1,54].

Task-build Indirect:

Install the new indirect task image.

names

IN:

and

MP:

their

proper

TKB @INDBLD.

When you have completed this sequence of steps,
perform an RSX-llS V4.l system generation.

3-2

you

are

ready

RSX-llS VERSION 4.1 RELEASE NOTES
NOTE
It is not necessary to

update

indirect

if your host is RSX-llM-PLUS V2.0.

3.3

NOTES TO THE RSX-llS SYSTEM GENERATION AND INSTALLATION GUIDE

The following sections contain
supplements the information in
Installation Guide.

information
the RSX-llS

that
modifies
and
System Generation and

Distribution Kits

3.3.1

RSX-llS V4.l is now distributed on the following media:
1.

One RK06 cartridge disk

One RK07 cartridge disk

One RLOl cartridge disk

One RL02 cartridge disk

One magnetic tape, 9-track, 800 bpi, 2400-foot

One magnetic tape, 9-track, 1600 bpi, 2400-foot

Note that RSX-118 is no longer distributed on RK05 disks.
All
references to the RK05 distribution kit in the manual no longer apply.

3.3.2

Q-Bus Terminal Interfaces

Section 2.1 of the manual implies that you can only choose UNIBUS
terminal
interfaces (for example, DHll and DZll) for your system.
If
you have a Q-bus machine (for example, a
PDP-11/23-PLUS), you can
choose a Q-bus terminal interface (for example, a DLVll or DZVll) for
the Q-bus machine.

3.3.3

Transferring Task Image Piles Using FLX

On page 2-7, the FLX command lines to transfer task image files from a
Files-11 format to either an RT-11
format or a DOS-11 format are
incorrect.
To transfer an image file from Files-11 format to DOS-11
format, type the following command lines:
FLX>C'f :/Z E/DO
FLX>/DO=[l,50]SIP.TSK/RS
To transfer an image file from Files-11 format to RT-11
the following command lines:

format,

type

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

description

FLX,

see

3-3

the

RSX-llM/M-PLUS

Utilities

RSX-llS VERSION 4.1 RELEASE NOTES
3.3.4

SETTIM

The sections of the manual that refer to SETTIM as a separate
subroutine
(Sections 2.5 and 4.5.1.5) do not apply. SETTIM is a
FORTRAN callable subroutine that is stored in SYSLIB.
See the
RSX-llM/M-PLUS Executive Reference Manual for
information on the
SETTIM subroutine.

Building a Resident Subset FCS Library

3.3.5

The following information on how to build
library for RSX-llS V4.l supersedes the
4.7.l.3.

a resident
information

subset FCS
in Section

Create the resident library by assembling the file
[2,200]11SRES.MAC
and building it according to the directions given in the file itself.
Two new entry points, .FCTYP and
.FLUSH, have been added to make
subset FCS conform to standard FCS.
The following descriptions of the
information in 2.7.3.

new

entry

points

.FCTYP

Returns with Rl clear to indicate
I/O-only version of FCS.

.FLUSH

This routine
success.

NOP

for

this

record

supplement

the

record

FCS

and

returns

For more information on building, defining, and loading resident
libraries, see the RSX-llM/M-PLUS Task Builder Manual and the RSX-llM
System Generation and Installation Guide.

3.4

SYSGEN DIALOGUE FROM AN RSX-llM HOST

3.4.l

Introduction

This section contains the actual terminal
system generation on an RSX-llM host.

dialogue

from

RSX-llS

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

DLVll terminal interface

3-4

the

RSX-llS VERSION 4.1 RELEASE NOTES
The following software support is included:
•

Large (20K) RSX-llS Executive

•

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

TKTN

•

XDT

•

System-controlled partitions

•

Basic MCR with support
error-message text

•

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

all

OTL

•

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

all

SIP

RSDVlH

•

RSX-llS Subset File Control Services (FCS)

for

OPEN,

ATL/TAL,

and

full

The system generation is being performed on an RSX-llM V4.l RL02
release kit baseline system disk.
The RSX-llS release kit consists of
one RL02, labeled llSKITl.
Questions calling for a YES/NO answer can be answered by pressing
RETURN key for a NO answer.

the

You can also answer questions asking for a value and displaying a
default value by pressing the RETURN key to specify the default
answer.
Notes:
•

You may want to do a preliminary system generation before you
do your actual SYSGEN.
To do a preliminary SYSGEN (PREPGEN),
you invoke the command file for Phase I
of the SYSGEN
(@llSGEN)
and answer YES to the question, •no you want to
inhibit execution of MCR commands (PREPGEN)?•

3-5

RSX-llS VERSION 4.1 RELEASE NOTES
Phase I continues, but the answers you give to the questions
are placed in a saved answer file instead of being used
immediately. When Phase I finishes, you reinvoke llSGEN.CMD
to run the phase again. This time, you do not inhibit MCR
command line execution and the SYSGEN procedure uses the
answers in the saved answer file.
Doing a PREPGEN saves time and prevents mistakes. The sample
dialogue in the following section shows a PREPGEN being done
before the actual SYSGEN.
•

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

3-6

RSX-llS VERSION 4.1 RELEASE NOTES
3.4.2

Actual Dialogue -- RSX-llS System Generation on an RSX-llM Host

RSX-11M V4+1 BL35-A

>RED

124.K MAPPED <BASELINE>

DL~=SY:

>RED DL:=LB:
>MOU DL.:RSXM35
>@DL:E1,2JSTARTUP
>* PLEASE ENTER TIME AND DATE <HR:MN DD-MMM-YY> [SJ: 13:02 15-MAR-83
>TIM 13:02 15-MAR-83
>* ENTER LINE WIDTH OF THIS TERMINAL CD D:132.J:
>SET /BUF=TI:132+
>ACS SY!/BLKS=512+
>@ <EDF>
>MOU DL1:11SIUT1
>PIP DLo:c200,200J/NV=DL1:c2,20J11SGEN.CMD,11SGEN2+CMD
>DMO DL1!
DMO -- TTO:
dismounted from DLl:
Final dismount initiated
13:11:00 *** Dll! -- Dismount comPlete

***

>@11SGEN

>; RSX-11S Version 4.1 BL35-A SYstem Generation done on RSX-11M

>; Disital EGuiPment Corporation' MaYnard1 Mass.
>; All Rishts Reserved+

>;
>;

>; RL01/RL02 distribution kit

>*
>*
>*
>*

3. Do you want to inhibit execution of MCR commands <PREPGEN>? CY/NJ:
5. Are You seneratins an unmaPPed system? [Y/NJ!

6. Use an inPut saved answer file? [Y/NJ!
9. Name of outPut saved answer file ED: SYSSAVED.CMDJ [SJ:

>; Phas~ I outPut saved answers created in file DLO!E200,200JSYSSAVED.CMD;1
>J
>* 16. Enter device for EXCPRV disk when it is ready (ddu!) [D! DLl:J [SJ: DL1:
>MOU DL1: EXCPRV

>; Target confisuration
);

>* 1+ Processor TYPe ED: 11/34] (SJ: 11/23
>* 2. Does Processor have a switch resister? [Y/N D!NJ:
>* 3. Memory size (in K-word blocks> ED R!16.-1920. D:16.J: 128.
>* 4. Include suPPort for K-series devices? EY/N D!NJ:
>* 6. Floating Point Processor <FP-11) Present? [Y/N D:NJ: Y
>* a. Extended instruction set <EIS> Present? EY/N D:NJ:
>* 10. Line freauency!
A- 60 Hz
B- 50 Hz
ED! AJ (SJ:
>* 11. KW11-Y Watchdos timer support? EY/N D!NJ:
>* 1 .:.. Memory parity support? [Y/N D:NJ: Y
~)

>;
>; The response to the following auestion specifies the hishest interrupt
>; vector.

If you respond with a value less than or eaual to 400, SYSGEN

>; will assisn the value associated with the hishest interrupt vector
>; specified during the PeriPheral Section. Therefore' if your system
); will include devices that are not specified during the PeriPheral
>; Section and which have vectors above 400 (devices such as K-series and
>; certain communication devices), specify that value in the next auestion.

>* 14. Hishest interrupt vector [0 R:0-774 D:OJ:
);
For device confisuration: "*" Prints device table, •.• Terminates inauirY
);
?'

•1• Prints current confisuration
Enter devices and number of controllers for devices which reauire drivers
15. DPvices [SJ!

3-7

RSX-llS VERSION 4.1 RELEASE NOTES
>;

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

>;
);

Device codes for A/D and industrial/laboratorY devices:
AD- AD01-D A/D Converter
AF- AFC11 A/D Converter
AR- AR11 Laboratory Subsystem
IC- ICR11/ICS11 Industrial Control S~bsystem
IP- IP11/IP300 Industrial Control Subsystem
IS- DRS11/DSS11 Industrial Control Subsystem
U'1-· L.PA 11 l..abo rato ry Subsystem
LS- LPS11 Laboratory Subsystem
UD- LJDC11 Universal Disital Controller
Device codes for Interprocessor communication devices:

XB- DA11-B Interprocessor Link

:·,.;

XL- Tll.l:!-E TriterPrl'.lf:'essor Link

XM- DMC11-E/DMR11 Interprocessor Link

XP- DP11 Synchronous Interface

>;
>;
>;
>;
>;

XQ- DQ11 SYnchronous Interface
XU- DU11 Synchronous Interface
XW- DUP11 Synchronous Interface
Device codes for unit record devices:

>;
>;

CR- CR11/CM11-E Card Reader
GR- VT11/VS60 GraPhics Subsystem

};

LP- LA11/LP11/LS11/LV11/LN01 Line Printer
PP- PC11 PaPer Tape Punch
PR- PC11/PR11 Paper Tape Punch and Reader

>;
>;
);
:::-;
}j

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

>;
>;
?'

>;
>;
>;
>;
>;
>;
>;
>;
>;
);

>;
>;

);

>;
);
);

>;
>;

Device codes for disk devices:
DB- RP04/RP05/RP06 Disk Drive
[ID- TU58 Cartridsfe DECtape I I
DF- RF11 Fi :<ed Head Disk Drive
DK- RK03/F:K05 Disk Drive
DL- RL01/RL02 Di sit~ Drive
DM- RK06/RK07 Disk Drive
DP- RP02/RP03 Disk Drive
DR- RM02/RM03/RM05/RM80/RP07 Disk Drive
DS- RS03/RS04 Fixed Head Disk fl rive
DT- TU56 DECtape
DU- RA60/RABO/RA81/RC25/RD51/RX50 Disk Drive
DX- RX01 Flo?PY Disk Drive
DY- RX02 Fl O?P\:I [lisk
EM- ML11 Non-Rotatinsf Electronic Memor!:I
Device codes for Masnetic taPe devices:
CT- TU60 Cassette Tape Drive
MF- TU78 MastaPe Drive
MM- TU16/TU45/TU77/TE16 Mastape Drive
MS- TS11/TU80/TSU05 Mastape Drive
MT- TU10/TE10/TS03 MastaPe Drive
Device codes for terminal interface devices:
YH- DH11/DHV11 Asynchronous Terminal Interface
YJ- DJ11 As!:lnchronous Terminal Interface
YL- DL11-A/-B/-C/-D/-E/-J/-W As';;lnchronous Terminal Interface
YZ- DZ11/DZU11 As!:lnchronous Terminal Interface
Device codes for Pseudo devices:
CO- console device
NL- null device
Enter responses as: devl=number controllers,dev2=number controllersr •••
If a devices is specified without the number of controllers, the number
of controllers defaults to 1.
EMamPlei DKrDH=2,YLrNL.

3-8

RSX-llS VERSION 4.1 RELEASE NOTES

);

>; Processor!11/23

Memory Size:128K,MaPPed

SYstem:RSX-118

); Host confisuration

>*
>*
>*
>*

1.
3.
4.
5.

>* EOS

Is a line Printer available? CY/NJ!
Does the listinS/maP device have at
Assembly listinss device (ddu!) CD:
MaP device for Executive and device

Y
least 120 columns? CY/NJ: Y
"NL!"J [SJ:
drivers (ddu!) CD! DLl!J [SJ!

* Do you want to: <CR>-continue R-rePeat section E-exit P-Pause [SJ:

>; Executive 0Ptians

Answer Y<ES) if the following suPPort is desired

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

6. Executive Common? CY/NJ: y
7+ Memory manasement CPLAS> directives? [Y/NJ! Y
8. Send/Receive bY reference directives? CY/NJ: Y
9, Get maPPins context directive? [Y/NJ: Y
Address checkins support will be included
I/O rundown support will be included
15. Loadable device drivers? [Y/NJ! y
16. Should the default for all aPPlicable drivers be loadable? CY/NJ: Y
AST support will be included
18. Include suPPort for Cancel Selective Marktime? [Y/NJ: y
19. Task termination and device not ready messases <TKTN>? CY/NJ: y
20. Power fail recovery? CY/NJ: Y
22. Larde C20K> Executive? CY/NJ: y
23. Losical device assisnment? CY/NJ: y
25. Do You intend to include a user-written driver? CY/NJ:
30. Executive Debusgins Tool <XDT>? CY/NJ: y
32. Include support for communications Products <such as DECnet>? CY/NJ:
33. SYstem controlled Partitions? CY/NJ! y
36. Group global eveni flags? CY/NJ: y

:;,;
>;
);
>;
>;
);
>;
>* 37.
);

>;
);

);

>;
>;
>;
>;

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

For directives:
* - Prints the table
- Terminates inauirY
Z
Gets all valid directives and terminates inauirY
Enter code for system directives (SJ: *
A- Get Partition Parameters
c- Send/Receive
E- E:<tend task
G- Get sense switch
I- Stop bit
K- Parent offsPrins tasking

B- Get task Parameters
D- Alter Priority
F- Connect to interr•JPt vector
H- Set system time
J- SPecifY reauested exit AST
L- Parent offsPrin!:i task ins with chainins

Enter responses as code1code2code3 •••

Ce.s.: ABCDF.>

37. Enter code for system directives [SJ: ~
SGN -- WARNING -- CPU does not have switch resister
-- Get sense switch directive not included
38. Number of Pre-allocated QIO Packets CD R:0.-15. D:5.J:
39. Size of data transfer vector in words CD R:0.-33. D:33.J:
40. Round-robin scheduling interval in ticks CD R:0.-1000. D:5.J:
41. Hishest Priority class for consideration CD R:l.-249. D:150.J:
42. Lowest Priority class for consideration CD R:l.-150. 0:1.J:
46. Seconds between Printer not ready messases CD R:0.-255. D:3o.J:
48. System crash re~ister and stack dumP device CSR CO R:0-177700 D:177564J:
51. Crash dump analysis:
A- PANIC B- Crash Dump Anal~sis <CDA> CD:
BJ [SJ:
52. CDA outPut notification device CSR CO R:16000d-177700 D:177564J:
53. Enter CDA memor~ dump device mnemonic (ddu:> CS R:3-4J: DL1:
54. Enter CDA memory dump device CSR (0 R:160000-177700 D:174400J:

>* EDS *

Do YOU

~ant

to: <CR>-continue R-repeat section E-exit

3-9

P-Pau~~

[SJ:

RSX-llS VERSION 4.1 RELEASE NOTES
); Terminal driver oPtions
);

1. Terminal driver desired CA/B/C/D, * Prints table) [SJ: *

>;
>;
>;
);
);

Terminal drivers:

>*
>*
>;

ABCD-

Tailorable ,half duPle>'
Tailored half duplex <user-oriented)
Full duPlex
Baseline half duPlex

1. Terminal driver desired CA/B/C/D, * Prints table) [SJ: C
2. Unsolicited inPut timeout value in seconds [D R:0.-255. 0:120.J:
Answer Y<ES> if the followinS support is desired

>;
>*

);
>*
>*
>*
>*
>*
>*
>*
>*

6. Unsolicited inPut character AST? [Y/NJ: Y
8. Breakthroush write? [Y/NJt Y
CTRL/R support will be included
10. Escape seouence handlins? [Y/NJ: Y
11. Get multiple characteristics? [Y/NJ: Y
12. Set multiple characteristics? [Y/NJ: Y
13. Get terminal driver oPtions? [Y/NJ: Y
17. Read after PromPt? [Y/NJ: Y
20. CRT rubout support? CY/NJ: Y
25. Hardware unrecoverable input error notification? [Y/NJ: Y
26. Device indePendent cursor positionins? [Y/NJ: Y

);

>* EDS * Do YOU want to: <CR>-continue R-rePeat section E-exit P-Pause [SJ:
);

);

>;
>;

);

~Ystem

DPtions

Answer Y<ES> if the followins support is desired

>;
>* 11. What name would you like to sive your system [D: RSX11SJ ES R:0-6J:

>* EDS * Do you want to: <CR>-continue R-rePeat section E-exit P-Pause [SJ!
};

);

Thinldns

>;
>~

End of Executive option seneration at 13:40:10 on 15-MAR-83

>; Peripheral confiSuration
>;

;,
};
>;
>;

Parameters aPPearinS in souare brackets •[ ••• J• can only be
specified for the first controller of a Particular device.
Parameters aPPearins in Parentheses •c ••• )• onlY need be specified
if
the indicated oPtion is Present on the tarset system.

>;
);
>;

The
default for loadable drivers has been set to *TRUE*•
To override this settins enter R (resident> as the first Parameter
for
the
first
controller
of
the
sPecified
device.

); A/D and Laboratory devices: None specified

>;
); Interprocessor communication devices: None specified
); Unit record devices: LP
>; Enter [L/R,J vectorr CSR, Printer option
>;
(,[KMC timeout count <O=no KMC>, KMC vector' KMC CSRJ> for:
>* 16. LP controller 0 [D! 200,177514,LA1BO,o,300,160130J [SJ!
); Disks! DD, DL
Enter EL/R,J vector, CSR, nu111be r of drives for!
>*

3. DD controller 0

en: 300 '176500]

[SJ!
CSJ!

3. DL controller 0 [II: 160,174400]
c:
-z
I\ 1 /01 "~
w...,.
Contr 0 !Jni t o. .. ::> an C•I
l\L.V .I., f't....V.:;.
53. Contr 0 •Jni t 1 • is an RL01/RL02

,.. r. •

L .L• t

01 "1 ,

r\L-V.&.~

[II: RL01J

3-10

' '2
, ,2

""''
[SJ! RL02
r~,.

I,.."" .....

,.._
ri..L.V.:!

,,LP11-B

RSX-llS VERSION 4.1 RELEASE NOTES
);
>; Tapes: None specified

>;
>; Non-PhYsical

(pseudo) devices:

co, NL, TI, CL, LB, SY

>; Terminal interface devices: YL, YZ

>;
>; Enter vector, CSR, E=DL11-E modem sUPPort/NO=no for:

>;
>* 21. YL controller 0 CD: 60,177560,NOJ

CSJ:

);

>; Enter vectorr CSR, highest line number <O to 7> [, answer sPeedJ for:

>;
>* 24. YZ controller 0 CD:

>;
>* EOS

,,,300J

* Do you want to! <CR>-continue R-rePeat section E-exit P-pause CSJ:

>; End of interrupt vector area has been set to 400
>;
>; Create Executive build files

>;
>;
>*

1. Do You wish to edit any of the Executive files? [Y/NJ:

>;
>* EDS * Do You want to: <CR>-continue R-rePeat section E-exit P-Pause CSJ:

>;
>;
>;
>? PrePare for task building

>; Clean-up extraneous obJect files

>;
>;
>* EDS

* Do You want to: <CR>-continue R-repeat section P-Pause CSJ:

>; End of 11SGEN Phase I at 13:53:06 on 15-MAR-83
>;
To continue tYPe: @c200,200J11sGEN2
>1
>@ <EDF>

>
>@11SGEN

>; RSX-118 Version 4.1 BL35-A System Generation done on RSX-11M

>I CoPYright <C> 1979,1981,1983
>; Disital EauiPment Corporation, Maynard, Mass.
>; All Rishts Reserved.

>;
.:·,

>; RL01/RL02 distribution kit

>;
>*
>*
>*

>*
>*

3.
4.
5.
6.
7.

Do You want to inhibit execution of MCR commands CPREPGEN>? CY/NJ:
Have You made a COPY of the distribution kit? CY/NJ: y
Are you seneratins an unmapped system? CY/NJ:
Use an input saved answer file? CY/NJ: Y
Name of input saved answer file CD: SYSSAVED.CMDJ [SJ:

>; Phase I inPut saved answers
>; created on 15-MAR-83 at 13!16!20
>; by 11SGEN version 2.0
>; are from file DLO!C200,200JSYSSAVED.CMD;1
>*

9. Name of outPut saved answer file CD! DL0!(200,200JSYSSAVED.CMDJ CSJ!

>; Phase I outPut saved answers created in file DLO:c200,200JSYSSAVED.CMD;2

....

...·'

3-11

RSX-llS VERSION 4.1 RELEASE NOTES
Use saved host confisuration? EY/NJ: Y
>* 10
Use saved PeriPheral confiSuration? [Y/NJ: Y
>* 11 . SkiP
end of section <EDS) breakpoints? [Y/NJ: Y
>* 12.
SkiP end of execution <EOX> breakpoints? [Y/NJ: Y
>* 13.
>* 14. Clean UP files from Previous GENs? [Y/NJ:
>* 16. Enter device for EXCPRV disk when it is read~ Cddu:> rD: DL1:J [SJ:
»

>MOU DU: EXCPRV
>PIP /FR
DLO: has 14667. blocks free' 5813+ blocks used out of 20480.
Larsest contisuous space = 9578. blocks
1400. file headers are freer 136. headers used out of 1536.
>SET /UIC=E11r10J
>; Tarset confisuration

>;
>; Processor:11/23
>;

Memor~

Size:128KrMaPPed

S~stem:RSX-11S

Floatins Point Processor
Parity Memory

>; Host confisuration
>; Executive 0Ptions
>;
>; Terminal driver oPtions
>;
>; System 0Ptions
>;
>;

Thinkins •••

>; End of Executive option seneration at 13:58:41 on 15-MAR-83
,,.:·

>; PeriPheral confiSuration
>;
aPPearins in sauare brackets •r ••• J• can only be
for the first controller of a particular device.
Parameters aPPearins in Parentheses •( ••• )• onlY need be specified
if
the indicated option is Present on the tarset sYstem.

Parameters

>;
>;

sPecifi~d

>;
>;
>;
>;

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

>; A/D and Laboratory devices: None specified
>;

>; Interprocessor communication devices: None specified
>; Unit record devices: LP

>; Disks: DDr DL
>;
>; Tapes: None sPecified
>;
>; Non-physical (pseudo) devices: co, NL• Tir Clr LBr SY
>; Terminal interface devices: Ylr YZ
>SET /UIC=[1,24J ! Creatins TTDRVBLD.CMD
>SET /UIC=[11,10J
>; End of interrupt vector area has been set to 400

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

>; Start of Executive assembly at 14:04:55 on 15-MAR-83
3-12

RSX-llS VERSION 4.1 RELEASE NOTES
>;
>SET /UIC=C11,24J
>MAC @DL1:RSXASM

>; End of Executive assembly at 14:32:15 on 15-MAR-83
>;
>;
>; Start of device drivers assembly at 14:32!16 on 15-MAR-83

>MAC @DLltRSXDRVASM
)j

>; End of Device drivers assembly at 14:49:56 on 15-MAR-83

>;
>ASN =LB:

>; PrePare for task buildinS

>SET /UIC=C1,24J
>PIP RSX11S.OBS=.(11,24J*.OBJ
>PIP TTDRV.OBJ=(11,24J*.TTY
>INS $LBR
>LBR RSX11S/CR:100.:1010.:128.=RSX11S+OBS
>LBR TTDRV/CR:J0.:256.:64.=TTDRV
>PIP /NV=[11,10JRSXBLD.CMD
>PIP C11,10JRSXBLD.CMD;*/DE/NM
>REM LBR

); Clean-up extraneous obJect files
>PIP RSX11S.OBS;*/DE/NMrTTDRV.OBJ;*,C11,24J*.OBJ;*'*•TTY;*
>REM MAC
>DMO DL1: EX CF' RV
DMD -- TTO:
dismounted from DL1!
DMO -- TTO:
dismounted from DL1!
***Final dismount initiated ***
14:55:58
DLt: -- Dismount complete

***

>;
>; Fnd of 11SGEN Phase I at 14!55!59 on 15-MAR-83
........,

To continue tYPe: @c200,200J11SGEN2

>;
>SF.T /11Ir.=C200,200J
>@ <EOF>

>
>@c200,200J11SGEN2

>; RSX-11S Version 4.1 BL35-A System Generation Phase I I

>; CoPYrisht CC> 1975, 1981, 1983
>; Disital EauiPment Corp., Maynard, MA.
>; All Rishts Reserved.
>;

01754

Build The Executive And All Reauired Tasks

); This command file will Produce the tarset system on your SY: disk.
>; If it i~ an RK05 or an RL01, this command file will delete a number
>; of files from this disk to make room for those reauired to comPlete
>; this 11SGEN. You must be runnins on an expendable COPY of
>; Your disk. Note however, that the disk will be left in a
>; state such that RSX-118 sysSens may be Performed at a later
>; date. In addition, the sysSen itself may be terminated and
>; may be restarted at Just about any Point to rebuild Particular
>; Pieces of the system.
>* In what UIC is SGNPARM.CHD if not C200,200J CSJ:

>; RL01/RL02 distribution kit 11SGEN version 2.0 for RSX-11H BL35-A
>; Continuation from 11SGEN PHASE I done on 15-MAR-83 at 14:55:48
>TIM
15:00:37 15-MAR-83

3-13

RSX-llS VERSION 4.1 RELEASE NOTES
>; The maP device specified must already be mounted with UIC (1,J4J.
>; If it is notr respond to the next auestion with ~z and do so.

>* In which device is the EXCPRV disk EDDU:J ESJ: DL1:
>MOU DL1:EXCPRV
>ASN SY:=LB:
>; ExPanded comments Provide a complete descriPtion of every steP in
>; this 11SGEN command file+ On the other handr short comments
>; Provide virtually no explanatory text.
>* Do you want expanded comments? EY/NJ: Y
);

); Make room on the baseline disk to comPlete the 11SGEN
>SET
>PIP
>PIP
>PIP
>PIP
>PIP

/UIC=E1r1J
[1r34l*•*/PU/NM
C1r54JCTDRV+TSK;*/DE/NM,DBDRV.TSK;*,DPDRV.TSK;*,DRDRV+TSK;*
E1r54JCTDRV+STB;*/DE/NM,DBDRV.STB;*,DPDRV.STB;*,DRDRV.STB;*
E200r200JSYSGEN2.CMD;*/DE/NM
/FR

DLO: has 14549. blocks free' 5931. blocks used out of 20480.
Larsest conti~uous space = 9578. blocks
1401. file headers are freer 135. headers used out of 1536.
>; Create RSX-11S subset system library
>; if You have not already done so.

>INS SY:$LBR
>* Have You already created 11SLIB.OLB? EY/NJ:
>LBR LB:11SLIB/CR:30.:896.:320.
>REM LBR
>* Have You already built the Exec? EY/NJ:
>SET /UIC=(1,24J
);

>; Purse Exec build command files and assemblY. Prefix files
>PIP RSXBLD.CMD/PU/NM
>PIP E11,10JRSXMC.MAC/PU/NM

>; Now we build the Executive
);
);
>;
>;

If you must make chanses to the Executive build files
answer Yes to the followinS auestion. Edit RSXBLD.CMD
by issuin~ the com~and EDI LB:RSXBLD.CMD. 11SGEN2 will
build the Executive after you resume from the Pause.

>* Do YOU wish to edit the Executive build file? CY/NJ:
>INS SY:$TKB
>TKB @LB:RSXBLD
>* Did the Executive build successfully? EY/NJ: Y

>;
>; You now need the Executive maps to layout
>; the Partitions in Your new system.
);

>* Do You have the maps already? EY/NJ:
>LOA LP:
>PIP LP:=DL1:c1.34JRSX11S.MAPrEXCOM1+MAP.EXCOM2+MAP
>UNL LP:
>; Look in the map of the Exec for the sYmbol •$SYTop• which
>; indicates the last address allocated to the Exec. User
>; Partitions may start at anY location beyond this ~ddress
>; as Ions as they fall on a 64 bYte boundary. See the RSX-11H
>; SYsSen manual for a descriPtion of how to set UP Partitions.
>; You may wish to stop at this time to layout Your Partitions.
>SET /UIC=E1,64J
>* Do YOU want to build anY loadable drivers now? CY/NJ: Y

>;
>; Fuild Loadable drivers

3-14

RSX-llS VERSION 4.1 RELEASE NOTES
>* 3. Device for driver's maps [D: NL:J [SJ:
>SET /UIC=Clr24J
);

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

); When all drivers are built, strike carriase return.
>* 5. Driver 2-character device mnemonic [SJ: DD
>* 6. Drive Partition name [D: DRVPARJ [SJ:
>TKB @DLl:DDDRVBLD
>* 5. Driver 2-character device mnemonic [SJ: DL
>* 6. Drive Partition name CD: DRVPARJ [SJ:
>TKB @DLl:DLDRVBLD
>* 5. Driver 2-character device mnemonic [SJ: LP
>* 6. Drive Partition name CD: DRVPARJ [SJ:
>TKB @DL1:LPDRVBLD
>* 5+ Driver 2-character device mnemonic [SJ:
>SET /UIC=[1,64J
>REM TKB
>SET /UIC=[1,24J
>PIP RSX11S.OBJ;*/DE/NM
>* Have You already built the full duplex terminal driver? CY/NJ:
?r

Now we build the full duplex terminial driver

>; The task build command file for the full duplex terminal drive
>; specifies that it run in Partition TTPAR, havins a lensth of
>; 40000 octal.
);

>* Do You wish to edit the build command file for the terminal driver? CY/NJ:
>INS SY:$TKB
>TKB @LB:TTDRVBLD.CMD
>* Did the terminal driver build successfully? [Y/NJ: Y
>REM TKB
>* List full duplex terminal driver maP? CY/NJ: Y
>LOA LP:
>PIP LP:~DL1:[1,34JTTDRV.MAP
>UNL LP:
>* Do YOU want to continue and build the PrivileSed tasks? CY/NJ: Y
>DMO DLl:
DMO -- TTO:
dismounted from DL1:
Final dismount initiated
1s:15:2a *** DLl: -- Dismount complete

***

);

>; PTePare to assemble and build the RSX-11S Privilesed
>; software components.
>;
>;
>;
>;
>;
);
>;

The tasks TKTN, BASMCRr OTL, and SIP must be assembled, and the
task build command files Possibly edited before they can be built.
The tasks RSDV05r RSDV52r and RSDV1H need onlY to be built, but
their command files may also be edited before they are built.
It is not necessary to save/Print the assembly listinss;
Howeverr we recommend that YOU save/Print the task build
maps. This is esPeciallY important when seneratins
); an unmaPPed system -- without maps it will be difficult
>; to determine Partition limits.

>;
>* Assembly list device for Privilesed tasks <DDNN:> CD: NL:J [SJ:
>*Map device for Privilesed tasks <DDNN:> CD: SY:J [SJ:
>* Have You already built task TKTN? CY/NJ:
>; Task TKTN will be included in Your 11S system as a result

>; of your selection in 11SGEN Phase I.
>; The Privilesed tasks BASMCRr OTLr and SIP were sPeciallY desfsned
>; for use in the RSX-118 environment. Their inclusion in the system
); is oPtional. If desired' they will be assembled and built under
); control of this command file.

3-15

RSX-llS VERSION 4.1 RELEASE NOTES

>* Do YOU wish to include BASMCRr OTL, or SIP in Your system? [Y/NJ: Y

>;
>;
>;
>;
>;

The tasks RSDU05, RSDU52, and RSDU1H dYnamicallY disPlaY the
the status of memorw on a sraPhics terminal and can be built
for the UT05B terminal' VT52 terminal, and VT100 terminal
resPectivelw. These tasks disPlaw which tasks are in memory
and where in memory thew reside, which task is currently
>; runnins, and the status of pool.

>* Do wou want to include RSDV05, RSDU52, or RSDV1HT (Y/NJ: Y
>; The RSX-11S subset file control services CFCS> are dist>; ributed as a sinsle file containins the concatenated obJect
>; modules. They cannot be Placed in the RSX-11M system obJect
>; library <SYSLIB.OLB>. However, users who reauire this FCS
>; should link with the RSX-11S subset of SYSLIB <11SLIB.OLB>
>; created durins this Swssen.
>* Do YOU wish to include the RSX-11S subset FCST [Y/NJt Y
>;
>;
>;
>;

If You have Previouslw done an RSX-11S Swssen on this disk~ all
of the files were transferred to the UFD (2,20J. These were
oPtionallw deleted by the Swssen Process. Therefore' unless
it was specified to delete the files or thew were later
>; deleted independently, there is no need to COPY all of the
>; files from the release kit asain.
};

>* Do You have to COPY the files from the release kit? (Y/NJ: Y
>*Enter device and unit of RSX-11S distribution kit <DDNN:> (SJ: DLl:
>; Place the RSX-11S release kit cartridse disk in drive DLl:

>;
>* Is the disk ready in drive DLl:? (Y/NJ: Y
>SET /UIC=[2,20J
>INS SY:$UFD
>UFD sv:r2,20J
>REM UFD
>PIP *·*;*/DE/NM
>MDU DL1:11SKIT1
>PIP SYt=DLlt
>DMO DLlt
DMO -- TTO:
dismounted from DLl:
*** Final dismount initiated ***
15:20:46 *** DL1: -- Dismount complete
>SET /UIC=(11,10J
>INS SYt$UFD
>UFD SY:(11,10J
UFD -- Directory already exists
>REM UFD
>* Do You wish to make corrections to RSX-115 source modules? [Y/NJ:
>INS SY:$MAC
>SET /UIC=[1,24J
>MAC @TKNASM
>PIP TKNASM.CMD;*/DE
>REM MAC

>; The task build command file for TKTN sPecifies that it run in
>; Partition SYSPAR, havins a lensth of 3700 octal.
>; If You must chanse the Partition name or lensth,
>; wou will have to edit its task build command file.
>* Do wou have to edit the task build command file for TKTN? (Y/NJ:
>INS SY:$TKB

>TKB @TKN11SBLD.CMD
>REM TKB

>; BASMCR is a Privilesed task which suPPlies a subset <or basic
>; set> of the RSX-11M MCR commands. It can not be included if
>; durins SYsSen Phase I ~ou indicated that ~ou did not want an~
>; from 6400 to 14000 octal on mapped s~stems.

3-16

RSX-llS VERSION 4.1 RELEASE NOTES
>* Do you want to include task BASMCR? CY/NJ: Y
>I NS SY aUFII
>UFD SY!C16dOJ
>UFD SY!C16,24J
>REM UFD
>SET /UIC=[16,10J
>PIP BMPRE.MAC;*/DE/NM
>PIP *•MAC;*/RM/NM
>PIP [16,*l*•*;*/DE/NM
>PIP [16,10J=[2,20JBMPRE.MAC
>PIP C16,10J/EN=[2r20JABOBAS.MAC,ATLBAS,BRKBAS,ERRBAS,ERRMSG
>PIP [16,10J/EN=[2,20JFMTDV.MAC,FNDUCB,GNBLK,GETNUM,KEYWD
>PIP [16,10J/EN=[2,20JLKLST+MAC,MCRBAS,QPEBAS,PRSBAS,REDBAS
>PIP C16,10J/EN=[2,20JREMBAS.MAC,RPSBAS,RUNBAS,TI~BAS
>SET /UIC=C16,24J
>;
>;
);
>;

The size of BASIC MCR is dePendent uPon the inclusion of
conditional assembly code. The inclusion of the code is
controlled by symbol definitions aPPearins in an assembly
Prefix file. The default for these conditionals is
>; exclusion. The followins options, alons with the corres>; Pondins control symbols, are available:
:::- ;

>;
);

R$$ATL - ATL/TAL COMMANDS
R$$ERM - ERROR MESSAGE TEXT
R$lOPE - OPEK COMMAND

>; To include an oPtion locate the desired conditional sYmbol

>i and remove the semicolon at the besinnins of the line.

>; example:

);

*PL ;RUATL
;R$$ATL = 0
*C ;; 11
R$$ATL = 0

For

; INCLUDE ATL
;INCLUDE ATL

); RePeat this for all desired options. Note that the symbols
>~ aPPear on consecutive lines in alphabetical order in the file.

>* Do YOU wish to edit the assembly Prefix file for BASMCR1 CY/NJ:
>INS SYUEIII
>EDI [16,10JBHPRE.MAC
[00029 lines read inJ
[Pase
1J
*PL ; RUATL
;RS$ATL
0
*C /;//
R$$ATL
0
*PL ; RUERH
;R$$ERH
0
*C 1;11
R$$ERH
0
*PL ; RUOPE
;R$$0PE
0
*C ;;11
R$$0PE
0

INCLUDE ATL
INCLUDE ATL
INCLUDE ERROR MESSAGES
INCLUDE ERROR .MESSAGES
INCLUDE OPEN
INCLUDE OPEN

*EX

CExitJ
>REH EDI
>INS SY:$HAC
>HAC @BASMCRASH.CHD
>REH MAC
>SET /UIC=[1'24J
>PIP [16,10JBMPRE.HAC;*/DE/NH
>PIP C16,10l*.HAC;*/RH/NH
>PIP BASMCR.OBJ=C16r24J*.OBJ
>PIP [16r24J*•*;*/DE/NH
>INS SY:SLBR
>LBR BASMCR/CR:21.:64.:64.=BASHCR
>REH LBR
>PIP BASHCR.OBJ;*/DE/NH

3-17

RSX-llS VERSION 4.1 RELEASE NOTES
);

>; The task build command file for BASMCR specifies that it
>; run in Partition MCRPAR, lensth 14000 octal <maPPed).
>; If You must chanse the Partition name or lensthr
>; You will have to edit its task build command file.

>* Do YOU wish to edit the task build command file for BASMCR? [Y/NJ:
>INS SY:HKB
>TK~·@BASMCRBLD+CMD

>REM TKB
);
>;
);
);
);

OTL is a Privilesed task which is the RSX-115 on-line task loader.
It Performs the installr load, and fix functions for tasks which
were created on a host development sYstem and copied via FLX to a
load medium. DePendins on the number of load devices, etc, OTL
ranses from 8000 to 15000 octal on maPPed systems.

>* Do wou want to include task OTL? CY/NJ: Y
>INS SY:$UFD
>UFD SY: [20, 10]
>UFD SY:C20r24J
>REM UFD
>SET /UIC=C20r10J
>PIP SY:OTLPRE.MAC;*/DE/NM
>PIP SY:*.MAC;*/RM/NM
>PIP [20r*l*•*;*/DE/NM
>PIP [20r10J=C2r20JOTLPRE.MAC
>PIP C20r10J/EN=[2r20JOTL.HAC,OTLCD•OTLCH,OTLERR
>PIP [20,10J/EN=[2r20J-OTLHD.HAC,OTLLBrOTLLDrOTLQIOrOTLRD
>SET /UIC=C20•24J

);
);
>;
);
);
>;
>;
);
);
);
);
);
>;
);
>;

The size of OTL is dependent upon the inclusion of conditional
asseablY code.
The inclusion of the code is done in two ways,
bw a sinsle sw•bol definition and bw aacro calls aPPearins
in an assembly Prefix file+
The first controls the inclusion
of error aessase text. To include this oPtionr locate the
symbol R$$ERM, and remove the seaicolon fro• the besinnins
of the line. The default for error aessase text is exclusion.
For exaaPle:
*PL ;R$$ERH
;R$$ERH=O
*C 1;11
RUERH=O
The other tYPe of oPtion concerns the exclusion of unwanted

>; device support. For each of the OTL load devices which
>; were included in SYsSen Phase I• corresPondins suPPort will be
); senerated in OTL. Naturally~ suPPort will not be senerated for
>; those OTL load devices which were not included in Swssen Phase I.
); The followins devices alons wjth corresPondins control sYabols
); •aw be SUPPorted by OTL:

>;
);
);

PR11
RX11
RX21
TA11
TC11
TH11
TSl 1
TU16
TU58

PAPER TAPE READER ------ PR
RX11 FLEXIBLE DISK ----- DX
RX211 FLEXIBLE DISK ---- DY
CASSETTE TAPE ---------- CT
DECTAPE ---------------- DT
TH/THA/THB11 HAGTAPE --- HT
TS04 HAGTAPE ----------- HS
TJ/TWU16-45 MAGTAPE ---- HH
TUSS CARTRIDGE --------- DD

);
);
); To exclude OTL SUPPort for a device which has been senerated into
>; your RSX-118 Executiver locate the correspondins device swabol
>; and Place a seaicolon at the besinnins of the line. For exaaPle:
*PL PR11
INCLUD
>;

*C 11;1

);

PR11rPS$R11

;PC11/PR11 SUPPORT

3-18

RSX-llS VERSION 4.1 RELEASE NOTES
); Perform this for all of the above devices which will be part of
>; your RSX-115 Executive, but for which You do not want OTL
>; support. Note that the symbols aPPear on consecutive lines in
>i alphabetical order in the file+

>* Do you wish to edit the assembly Prefix file for OTL? EY/NJ: Y
>INS sv:sEDI
>EDI E20r10JOTLPRE.MAC
[00036 lines read inJ
[Pase
OJ
*PL ;R$$ERH
[00036 lines read inJ
;R$$ERM=O
*C /;//
R$$ERM=O
*EX
[Exit]
>REM EDI
>INS sv:sMAC
>MAC @OTLASM.CMD
>REM MAC
>SET /UIC=[1,24J
>PIP [20r10JOTLPRE.MAC;*/DE/NM
>PIP [20r10l*+MAC;*/RM/NM
>PIP OTL.OBJ=[20r24J*.OBJ
>PIP [20,24l*•*;*/DE/NM
>INS SY:$LBR
>LBR OTL/CR:21.;12B.:64.=0TL
>LBR OTL=[2r20JBLXIOM
>REM LBR
>PIP OTL.OBJ;*/DE/NM
);

>; The task build command file for OTL specifies that it
); run in Partition OTLPAR, lensth 15000 octal <maPPed).
>; If You must chanse the Partition name or lensthr
>; you will have to edit its task build command file.
);
>* Do You wish to edit the task build command file for OTL? CY/NJ:
>INS sv:sTKB
>TKB @OTLBLD.CMD
>REM TKB
>; SIP is a Privileged task which Performs the RSX-11S system
); image Preservation duties. It replaces the RSX-11M SAU MCR
>; command. DePending on the number of load devices' etc, SIP
>; ran~es from 3700 to 7400 octal on maPPed systems.
);

>* Do YOU want to include task SIP? EY/NJ: Y

>INS sv:sUFD
>UFD SY:E21r10J
>UFD sv:r21,24J
>REM UFD
>SET /UIC=[21,10J
>PIP SY:SIPPRE.MAC;*/DE/NM
>PIP sv:*.MAC;*/RM/NM
>PIP [21r*l*•*;*/DE/NM
>PIP E21110J=[2120JSIPPRE.MAC
>PIP E21110l/EN=E2r20JSIP.MAC,SIPBOOrSIPCDrSIPERR
>PIP C21110J/EN=[2r20JSIPLD.MACrSIPQIO
>SET /UIC=E21r24J
); The size of SIP is dePendent upon conditional assembly code
There are onlY a few minor
>; differences. OTL suPPorts the paper tape reader usins the
>; control sYmbol PR11; SIP on the other hand ~UPPorts the paper
>; tape ?unch usinS the control symbol PP11. In addition, OTL
>; suPPorts DECtape II cartridses usinS control symbol TU58 and
); TS11 masnet{c tape drives usinS the control symbol TS11.
>; Edit S!PPRE.MAC in the same waw described for OTL. For examPle:

>; in exactly the same manner as OTL.

3-19

RSX-llS VERSION 4.1 RELEASE NOTES

*PL PP:l.1.

>;
>;

INCLUD

PP11,P$$P11

;pc11/PR11 SUPPORT

INCLUD

PP11,P$$P11

;pc11/PR11 SUPPPRT

>;
>* Do YDlr wish to edit the assembly Prefix file for SIP? [Y/NJ: Y
>INS SY:$EDI
>EDI [21,lOJSIPPRE.MAC
[00036 lines read inJ
C:Pase
OJ
*PL ; RUERM
[00036 lines read in]
;R$$ERM=O
*C I U !

RHERM=O
*EX
[ E~-:i t J
>REM EDI
>INS SY: $MAC
>MAC @SIF'ASM.CMit
>REM MAC
>SET /UIC=[1,24J
>PIP [21,lOJSIPPRE+MAC;*/DE/NM
>PIP [21,10l*+MAC;*/RM/NM
>PIP SIP.OBJ=[21,24J*.OBJ
>PIP [21,24l*·*;*/DE/NM
>INS SY!$LBF:
>LBR SIP/CR:20.:64.:64.=SIP
>REM LBF:
>PIP SIP.OBJ;*/DE/NM
>;
);
);
>;

The task build command file for SIP specifies that it
run in Partition SIPPAR' lensth 7400 octal <mapped),
If !:IOU must chanse the Partition name or lensth,
You will have to edit its task build command file.

>* Do You wish to edit the task build command file for SIP? [Y/NJ:
>INS svanrn
>TKB @SIPBLD.CMD
>REM TKB
>SET /UIC="[1,24J
>PIP RMD.OLB/NV=[2,20JRMDHAP.OLB
>* Do YOU want to include task RSDV05'? [Y/NJ:
>* Do !:IOIJ want to include task RSDV52? CY /NJ:
>* Do !:IOU want to include task RSDV1H!' CY IN J: y

);

>; The task build command file for RSDV1H sPecifies that it
>; run in Partition RSDV1Hr lensth 40000 (octal).
>; If YOU must chanse the Partition name or lensth,
>; will have to edit the task build command file.

!:IOU

>* Do You wish to edit the task build command file for RSDVlH? EY/NJ:
>INS SY: $TKB
>TKB @RSDV1HBLD.CMD
TKB --

*DIAG*-S~mbol

HEADER not found for patch

>REM TKB

>; Add subset FCS to the RSX-115 system obJect

>SET /UIC=[1r1J

>INS SY:SLBR
>LBR LB:11SLIB/RP=[2,20JFCS11S
>REH LBR
>PIP LB:11SLIB.OLB/PU/NM
>SET /UIC=[1,64J
>PIP *·*/PU/NM
>PIP [1,24l*•*/PU/NM

3-20

librar~

RSX-115 VERSION 4.1 RELEASE NOTES
); The operation left to be performed is that of the final
>; configuration of the virgin executive using Virtual MCR+

>* Do You want to confisure the Exec at this time usin~ VMR? [Y/NJ: Y
>; The contents of Your RSX-115 release kit currently resides
>; under the UFD (2120]+ If your SY: disk is not an RK06/07 or an
>; RP04/05/06 You may want to delete these files. Leaving.
>; them on the disk will save the ti~e of re-copying them the next
); time You Perform an RSX-11S Sysgen. If Your SY: disk is an RK05r
>; they will be automatically deleted.

};

>* Do You want to delete the RSX-116 kit from this disk? CY/NJ:
>; We will now make a COPY of your target system
>PIP RSX11S.SYS/NV/CO/BL:498.=RSX11S.TSK
>; If sou wish to make a COPY of Your task or system image file
); on another device we will Pause now to allow you to do so.

>* Do YOU wish to coPY your system to another device? [Y/NJ:
>; RSX11S.TSK is a backup COPY of the 11S system YOU have Just built.
>; If YOU do not wish to retain itr we will delete it now.

>* Do ~ou wish to delete the system backup file RSX11S.TSK1 [Y/NJ:
>; Your target system is now ready to set UP Partitions and install
>; the reauired tasks. The Procedure to follow is:
>;
1) Run Virtual MCR
2) Extend POOL sPace to base of first Partition
3) Set UP Your Partitions
3B) Load needed drivers
3C) Set up a Partition for the Directive Common
4> Install tasks <BASMCR, OTL, SIP, TKTN>
5) Fix tasks into (virtual> memory
6) OPtionallY set the time and save a COPY of THE
system on a bootable medium
7> Exit from virtual MCR and boot in your tarset system
VMR examPle:
>VMR
RUN VIRTUAL MCR
ENTER FILENAME:RSX11S.SYS ! VMR PROMPTS FOR FILE NAME
VMR>SET /POOL=XXX
EXTEND POOL TO FIRST PARTITION BASE
VMR>SET /MAIN=TTPAR:xxx:xxx:TASK !SET UP FULL DUPLEX TT PARTITION
VMR>SET /MAIN=DRVPAR:xxx:xxx:TASK ! SET UP DRIVER PARTITION
VMR>SET /MAIN=EXCOM1:xxx:xxx:coM ! SET 1ST EXEC. COMMON
VMR>INS EXCOM1
!INSTALL 1ST EXECUTIVE COMMON
VMR>SET /MAIN=EXCOM2:xxx:xxx:coM ! SET 2ND EXEC. COMMON
VMR>INS EXCOM2
!INSTALL 2ND EXECUTIVE COMMON
VMR>SET /MAIN=SYSPAR:xxx:xxx:TASK
SET UP TKTN PARTITION
VMR>SET /MAIN=MCRPAR:xxx:xxx:TASK
SET UP MCR PARTITION
VMR>SET /MAIN=OTLPAR:xxx:xxx:TASK
SET UP OTL PARTITION
VMR>SET /MAIN=SIPPAR:xxx:xxx:TASK
SET UP SIP PARTITION
VMR>SET /MAIN=RSDU1H:xxx:xxx:TASK
!SET UP RSDV1H PAR
VMR>SEl /MAIN=GEN:xxx:xxx:sYS ! IF SYSTEM CONTROLLED PAR.
VMR>SET /MAIN=GEN!XXX!XXX!TASK ! IF USER CONTROLLED PARTITION
VMR>LOA XX!
LOAD XXDRV
VMR>INS/FIX TKN
INSTALL & FIX TKTN
VMR>INS/FIX BASMCR
INSTALL & FIX BASIC MCR
VMR>INS/FIX OTL
INSTALL & FIX OTL
VMR>INS/FIX SIP
INSTALL & FIX SIP
NMR>INS/FIX RSDVlH
INSTALL & FIX RSDV1H
VMR>TIM 10:45 11/10/77
SET TIME AND DATE
VMR>SAV DX!RSX11S
SAVE SYSTEM ON RX01 FLOPPY
VMR>~z
EXIT FROM VIRTUAL MCR

3-21

RSX-llS VERSION 4.1 RELEASE NOTES
End of VMR example

>; Now we will run Virtual MCR so that you may initialize
>; your sYste~. Be sure to define all reauired Partitions
>; at this ~ime' because the SET function is not SUPPorted
>; in RSX-11S BASIC MCR. Furthermore, if YOU Plan to
>; include BASIC MCR and OTL in your system' they must
); be installed and fixed into memory. Other tasks,
>; such as SIP and TKTN may be loaded into a runnin~
); RSX-118 system usins OTL.
);

);
>;

NOTE! Since LOAD and UNLOAD are not supported on
a runnins RSX-11S system, all reauired loadable
drivers must be loaded usins VMR.

>;
>;

NOTE! You have reauested to include the
);
directive common. You must install the
;,
common Prior to exittins Virtual MCR
>;
or your RSX-11S system will not boot.
>INS SY!SVMR
>VMR
Enter filename: RSX11S
VMR>SET /POOL=*
VMR>SET /MAIN=TTPAR:*:400:TASK
VMR>LOA TT:
VMR -- *DIAG*-Loadable driver larSer than 4K
VMR>SET /MAIN=DRVPAR:*:*:SYS
VMR>LOA DD:
VMR>LOA DL!
VMR>LOA LP:
VMR>SET /TOP=DRVPAR!-*
VMR -- *DIAG*-Installed tasks may no lenser fit in Partition
VMR>SET /MAIN=EXCOM1:*:2oo:coM
VMR>INS EXCOM1
VMR -- *DIAG*-Partition reduced to executive common size
VMR>SET /MAIN=EXCOM2!*!200!COM
VMR>INS EXCOM2
VMR -- *DIAG*-Partition reduced to executive common size
VMR>SFT /MAIN=SYSPAR!*!101!TASK
VMR>SET /MAIN=MCRPAR!*!137!TASK
VMR>SET /MAIN=OTLPAR:*:150!TASK
VMR>SET /MAIN=SIPPAR!*!74!TASK
VMR>SET /MAIN=RSDV1H!*!400!TASK
VMR>SET /MAIN=GEN:*:*:svs
VMR>INS TKN/FIX=YES
VMR>INS BASMCR/FIX=YES
VMR>INS OTL/FIX=YES
VMR>INS SIP/FIX=YES
VMR>INS RSDV1H/FIX=YES
VMR>REA RSDV1H 1 TT1!
VMR>REA RSDV1H 2 TT1!
VMR>TIM 16!29 15-MAR-83
VMR>SAV DD!11S
UMR>~7

>; When this command file completes, your RSX-11S system is
>; ready to run.
>;
>REM VMR
>SET /UIC=C200,200J
>TIM
16!28!00 15-MAR-83
>@

<EDF>

3-22

RSX-llS VERSION 4.1 RELEASE NOTES
TESTING MEMORY

0128+KW
START? DD
XDT:

35-A

XDT>G

RSX11S V4+1 BL35-A

>·
TIM

16:30:16 15-MAR-83

3-23

RSX-llS VERSION 4.1 RELEASE NOTES
3.5

SYSGEN ON A RSX-llM-PLUS HOST SYSTEM

This section contains information on preparing for your RSX-llS SYSGEN
on an RSX-llM-PLUS host.
For the most part, the actual dialogue and procedures for the RSX-llS
SYSGEN are the same as those for an RSX-llM host. The procedure for
performing an RSX-llS SYSGEN on an RSX-llM-PLUS host is the same as is
currently documented.
The only differences are in the numbering and
wording of some of the questions. These changes are reflected in the
RSX-llS SYSGEN on a RSX-llM host.

3.6

SYSGEN ON A VAX/VMS HOST SYSTEM

This section contains information on preparing for your RSX-llS SYSGEN
on a VAX/VMS host.
For the most part, the actual dialogue and procedure for performing an
RSX-118 SYSGEN on a VAX/VMS host is the same as is currently
documented. The only difference is in the numbering and wording of
some of the questions.
These changes are reflected in the RSX-118
SYSGEN on a RSX-llM host.
Also, if you have disk quota checking on your SYS$LOGIN device (your
work disk), it must be disabled before you begin your RSX-llS system
generation. This is because the compatibility mode task, MAC, needs
to create temporary work files in UICs that probably do not have an
established disk quota on SYS$LOGIN. Otherwise, MAC cannot assemble
any files during llSGEN.
To disable disk quota checking, invoke the Disk
{DISKQUOTA} by issuing the following command line:

Quota

Utility

$ RUN SYS$SYSTEM:DISKQUOTA
When the DISKQUOTA prompt
following command lines:

appears

your

terminal,

issue

the

DISKQ>USE diskname:~
DISKQ>DISABLE ~
DISKQ> tTRL/z)
$

where diskname:

is the name of the SYS$LOGIN device.

Now disk quota checking is disabled and you are ready
RSX-llS SYSGEN.

3-24

begi~

your

RSX-llM/RMS-11/RSX-llS
Release Notes
AA-2573H-TC
READER'S COMMENTS
NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company's discretion. If you require a written reply and are eligible to receive one under Software
Performance Report (SPR) service, submit your comments on an SPR form.

Did you find this manual understandable, usable, and well organized? Please make suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent.

D
D
D
D
D
D

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify)

Organization
Street
C i t Y - - - - - - - - - - - - - - - - - - - - - - - State _ _ _ _ _ _ Zip Code - - - - - -

DoNotTear-FoldHereandTape -

No Postage
Necessary

111111

if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

BSSG PUBLICATIONS ZK1-3/ J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03061

- -

DoNotTear-FoldHere

.s..J
4l

tlO

1.§
<

I ....

·a

I
I