Digital PDFs

AA-L997E-TC

August 1980

262 pages

Original

14MB

Document:	RSTS/E Maintenance Handbook
Order Number:	AA-L997E-TC
Revision:	0
Pages:	262
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsts_e/V10/AA-L997E-TC_RSTS_E_Maintenance_Handbook_Aug1990.pdf

OCR Text

RSTS/E Maintenance Notebook
Order Number: AA-L997E-TC

August 1990
This notebook is a working document that contains published articles on software problems,
programming notes, documentation corrections, and optional feature patches. System Managers
should keep this document current by incorporating articles published each month in the RSTSIE
Software Dispatch.

Operating System and Version: RSTS/E Version 10.0
Software Version:

Digital Equipment Corporation

RSTS/E Version 10.0

August 1990
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 only be used or copied in accordance
with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment not supplied by Digital Equipment
Corporation or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in
subparagraph (c)(1 )(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
© Digital Equipment Corporation 1990. All rights reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document requests the user's critical evaluation
to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation:
ALl-IN-1
DEC/CMS
DECdx
DEC/FMS-11
DECmail
DECnet
DECnetiE
DECSA
DECserver
DECsystem-10
DECSYSTEM-20
DECUS
DECworld
DELUA
DEONA

DEUNA
DIBOL
EDT
lAS
LA
LN01
Micro/RSX

OS/8
PDP
PDP-11
PDT
a-BUS
RMS-11
RSTS

RSX
RT
RT-11
TOPS-10
TOPS-21
UlTRIX
UNIBUS
VAX
VAXmate
VMS
VT
WPS-PLUS
Rainbow

~DmDDmDN

IBM is a registered trademark of International Business Machines Corporation.
RMS is a trademark of American Management Systems, Inc.

CONTENTS
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Using the RSTS/E V10.0 Maintenance Notebook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Component.Subcomponent Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Software Performance Reports ...........................................
3.1 Software Performance Report Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11
11

4 Procedures for Updating RSTS/E Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Monitor Patching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Commonly Used System Program (CUSP) Module Replacement . . . . . . . . . . . . . . .
4.3 Installation Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Patches and Replacement Modules for Optional Layered Products .............

13
13
14
14
14

5 Software Product Descriptions and Option Bulletins. . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Software Product Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Option Bulletins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17
17
17

6 RSTS/E V10.0 Articles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iii

Preface
The RSTS / E Maintenance Notebook is a guide for documentation corrections, published
software problems and solutions, and programming notes. Subordinate software information
is also included. The RSTS / E Software Dispatch Review and the RSTS / E Software Dispatch
are designed so that their articles may be merged into the Maintenance Notebook.
The RSTS / E Software Dispatch Review contains articles published for optional layered
software supported on RSTS/E VIO.O. In general, this is a composite of all optional layered
software articles previously published for RSTS/E that still apply to the product when run
on RSTS/E VIO.O.
The RSTS / E Software Dispatch contains articles for RSTS/E and its layered software. It
is published monthly and distributed to customers who have purchased a software service
contract from Digital. (Contact your local Digital office for more information on how to
obtain a software service contract if you do not already have one.)
Each month, take apart the RSTS / E Software Dispatch and merge the new articles by
sequence number into your maintenance notebook.
All published articles are summarized in the Cumulative Index at the end of this notebook.
This index is updated as necessary in the RSTS / E Software Dispatch.

Preface v

Using the RSTS/E V10.0 Maintenance Notebook

When you receive the RSTS / E Software Dispatch, take it apart and merge the new articles
by sequence number into your notebook. If an article replaces an existing article, discard
the replaced article. Each article addresses a single topic; its title gives the symptom or a
one-line problem description and appears at the top of each page. For example:

Seq. No. 4.1.4 F
Default to NOEXTEND Mode - BASIC·PLUS Feature Patch
System components and subcomponents are listed in Section 2. The list is updated periodically as products become available or obsolete. Articles for each subcomponent are
assigned a sequencing number which uniquely identifies the article within that component
and subcomponent category. As each new article is published for a subcomponent, it is
assigned the next higher sequence number. The entire number is defined as the component.subcomponent.issue number (for example, 4.1.4 shown in the upper right corner of the
sample heading). Replacement articles are identified as such.
Each article's sequence number is followed by a letter which identifies the type of article as
follows:

•

M = Mandatory
These articles describe problems corrected by a replacement module. In some cases,
these articles also include a patching procedure you can follow to correct a problem.
You are required to install replacement modules or apply patches described in a "M"
article unless told otherwise.

•

F = Feature
Feature articles include patches that extend or configure nonstandard capabilities into
the product. These functions are treated as a supported part of the product for the
duration of the current release.

•

R = Restriction
These articles discuss areas that will not be patched in the current release because they
require major modifications or because they are not consistent with the design of the
product. Restrictions, except those described as permanent, are reviewed and modified
when possible as part of the normal release cycle.

•

N = Note
Articles designated as "N" provide explanatory information that supplements the documentation set and provides more detailed information about a program or package. They
also provide procedural information to make it easier to use a program or package.

RSTS/E V10.0 Maintenance Notebook

2 Component.Subcomponent Assignments
The component. subcomponent numbers outlined below appear on articles to be filed following the Cumulative Index in this notebook.

RSTSIE MONITOR
0.0

RSTS/E V10.0 General Notes

0.1

System Notes

0.2

System Management Guidelines

1.0

Initialization

1.1

INIT.SYS Program Patches

1.2
1.3

INIT.SYS Program Notes
INIT.SYS Restrictions

2.0
2.1
2.2
2.3

System Installation and Update

3.0
3.1
3.2
3.3
3.4
3.5

Executive

Installation/Update Notes
Installation/Update .COM files
Installation/Update Restrictions

Monitor Patches
Monitor Notes
Monitor Restrictions
Terminal Service Patches
Terminal Service Notes

3.6

Terminal Service Restrictions

3.7
3.8

File Processor Patches

3.9
3.10
3.11
3.12
3.13
3.14

File Processor Restrictions

3.15

FMS Monitor Restrictions

4.0
4.1

4.2
4.3
4.4
4.5
4.6

File Processor Notes
Device Driver Patches
Device Driver Notes
Device Driver Restrictions
FMS Monitor Patches
FMS Monitor Notes

BASIC-PLUS
BASIC-PLUS Patches
BASIC-PLUS Notes
BASIC-PLUS Restrictions
Programming Hints
Math Packages
Matrix Functions

RSTS/E V10.0 Maintenance Notebook

4.7
4.8
4.9
4.10
4.11

PRINT·USING
Record 1/0
Virtual Core
String Arithmetic
Optional BASIC· PLUS Features

5.0

(Reserved)

6.0
6.1
6.2

System Flies

7.0
7.1
7.2
7.3

DECnet/E Monitor Package V4.1

System Files Notes
System Files Restrictions

DECnetlE Monitor Patches
Package Notes
Package Restrictions

RSTSIE UTILITIES
8.0
8.1
8.2

Help Package (HELP$)

9.0
9.1
9.2

TECO Package (TECO$)

10.0
10.1
10.2

System Library ($)

11.0
11.1
11.2

Auxiliary Library (AUXLlB$)

12.0
12.1
12.2

Error Logging Package (ERROR$)

13.0
13.1
13.2

RESTOR Package (RESTOR$)

Package Notes
Package Restrictions

Library Notes
Library Restrictions

Package Notes
Package Restrictions

RSTS/E V10.0 Maintenance Notebook

14.0

Operator Services and Spooling Package (OPSER$)

14.1

Package Notes

14.2

Package Restrictions

15.0

Print/Batch Services Package (PBS$)

15.1

Package Notes

15.2

Package Restrictions

16.0

Unsupported Package (UNSUPP$)

16.1

Package Notes

16.2

Package Restrictions

17.0

Layered Product Update Package (UPDATE$)

17.1

Package Notes

17.2

Package Restrictions

18.0

Device Test Package (TEST$)

18.1

Package Notes

18.2

Package Restrictions

19.0

Operator/Message Services Package (OMS$)

19.1

Package Notes

19.2

Package Restrictions

20.0

CUSP Source Package (SOURCE$)

20.1

Package Notes

20.2

Package Restrictions

21.0

SORT/MERGE V3.0 (SORT$)

21.1

Package Notes

21.2

Package Restrictions

22.0

RMS-11 V2.0 (RMS$)

22.1

Package Notes

22.2

Package Restrictions

23.0

EDT V3.0 (EDT$)

23.1

Package Notes

23.2

Package Restrictions

24.0

(Reserved)

25.0

(Reserved)

RSTS/E V10.0 Maintenance Notebook 5

RSTSIE DOCUMENTATION
26.0

RSTS/E Documentation Directory

AA-2642H-TC

26.2

RSTS/E V10.0 Release Notes

AA-S246H-TC

26.3

RSTS/E V10.0 Maintenance Notebook

AA-L997E-TC

26.4

RSTS/E System Installation and Update Guide

AA-2669K-TC

26.S

RSTS/E System Manager's Guide

AA-2762H-TC

26.6

RSTS/E System User's Guide

AA-EZ12B-TC

26.7

RSTS/E Guide to Writing Command Procedures

AA-CF03A-TC

26.8

RSTS/E Utilities Reference Manual

AA-EZ11A-TC

26.9

Introduction to the EDT Editor

AA-K443A-TC

26.10

PDP-11 SORT/MERGE User's Guide

AA-CI67B-TC

26.11

RSTS/E RUNOFF User's Guide

AA-3337B-TC

26.12

EDT Editor Manual

AA-M476A-TK

26.13

RSTS/E Task Builder Reference Manual

AA-S0720-TC

26.14

RSTS/E Programmer's Utilities Manual

AA-D749A-TC

RSTS/E Programmer's Utilities Manual Update 1

AD-D749A-T1

RSTS/E Programmer's Utilities Manual Update 2

AD-D749A-T2

26.1S

RSTS/E RT11 Utilities Manual

AA-M213A-TC

26.16

PDP-11 TECO User's Guide

AA-K420B-TC

26.17

BASIC-PLUS Language Manual

AA-2623D-TC

26.18

RSTS/E Programming Manual

AA-EZ09B-TC

26.19

RSTS/E System Directives Manual

AA-EZ1 OB-TC

26.20

IAS/RSX-11 ODT Reference Manual

AA-MS07A-TC

26.21

PDP-11 MACRO-11 Language Reference Manual

AA-KX10A-TC

PDP-11 MACRO-11 Language Reference Manual Update

AD-KX108A-T1

RSTS/E RMS-11 MACRO Programmer's Guide

AA-PS07A-TC

26.22

Documentation

26.1

26.23

RSTS/E RMS-11: An Introduction

AA-PS08A-TC

26.24

RSTS/E RMS-11 User's Guide

AA-PS10A-TC

26.2S

RSTS/E RMS-11 Utilities Manual

AA-PS09A-TC

26.26

RSTS/E Quick Reference Guide

AA-EZ13C-TC

26.27

Introduction to BASIC

AA-01SSB-TK

26.28

EDT Quick Reference Guide

AA-M477A-TK

26.29

RSTS/E V10.0 Internals and Data Structures Manual

AA-PB60A-TC

RSTS/E V10.0 Maintenance Notebook

RUN-TIME SYSTEMS SUPPORT
27.0

DCl Run-time System and Utilities

27.1

Package Notes

27.2

Package Restrictions

28.0
28.1
28.2
29.0

RSX-11 Emulator and Utilities
Package Notes
Package Restrictions
RT-11 Emulator and Utilities

29.1

Package Notes

29.2

Package Restrictions

30.0

(Reserved)

OPTIONAL SOFTWARE
31.0

DECnetlE Utilities V4.1 (DECNET$)

31.1

Package Notes

31.2

Package Restrictions

32.0

DECnet/E V4.1 Documentation

32.1
32.2

DECnetlE V4.1 Release Notes

M-M269D-TC

DECnetlE V4.1 System Manager's Guide

M-H50SD-TC

32.3

DECnetlE V4.0 Network Programming in BASIC-PLUS
and BASiC-PlUS-2

32.4

DECnetlE V4.0 Network Programming in MACRO

32.S

DECnetlE V4.0 Network Programming in FORTRAN

32.S

DECnetlE V4.0 Network Programming in COBOL

32.7

DECnetlE V4.0 Guide to User Utilities

M-H504C-TC

32.8

DECnetlE V4.0 Network Installation and Update Guide

AA-K714C-TC

33.0
33.1
33.2
34.0

PDP-11 C V1.0
Package Notes
Package Restrictions
WPS-PLUS/RSTS V1.1

34.1

Package Notes

34.2

Package Restrictions

35.0

(Reserved)

36.0

DECmall-11 V3.1

RSTS/E V10.0 Maintenance Notebook

36.1

Package Notes

36.2

Package Restrictions

37.0

(Reserved)

to
44.0
45.0

OECdx/RSTS V1.0

45.1

Package Notes

45.2

Package Restrictions

46.0

(Reserved)

47.0

(Reserved)

48.0

BASIC-PlUS-2 V2.6

48.1

Package Notes

48.2

Package Restrictions

49.0

OATATRIEVE-11 V3.3A

49.1

Package Notes

49.2

Package Restrictions

50.0

(Reserved)

to
54.0
55.0

Package Notes

55.2

Package Restrictions

56.0

COBOL-51 V3.0

56.1

Package Notes

56.2

Package Restrictions

57.0

FORTRAN-77 VS.4

57.1

Package Notes

57.2

Package Restrictions

58.0

1'01'-11 Symbolic Debugger V2.1

58.1

Pacakge Notes

58.2

Package Restrictions

59.0

FORTRAN IV V2.8

55.1

(Reserved)

RSTS/E V10.0 Maintenance Notebook

60.0

(Reserved)

61.0

(Reserved)

62.0

PLXY-11 V1.3

62.1

Package Notes

62.2

Package Restrictions

63.0
to
67.0

(Reserved)

68.0
68.1
68.2

MENU-11 V2.0
Package Notes
Package Restrictions

69.0
to
72.0

(Reserved)

73.0
73.1
73.2

DIBOL VS.1
Package Notes
Package Restrictions

74.0
to
89.0

(Reserved)

90.0
90.1
90.2

."
User Assigned Components
- For Development Use

91.0
to
99.0

User. Assigned Components - For User Use

Package Notes
Package Restrictions

RSTS/E V10.0 Maintenance Notebook 9

3 Software Performance Reports
Each new installation is provided with Software Performance Report (SPR) forms. The SPR
form allows you to suggest enhancements to, or report problems with Digital software or
documentation. When you discover a problem, complete an SPR and mail it to the local SPR
Center (see the inside back cover of the SPR form).
Responses will be sent to the name and address appearing on the form. You can obtain
additional SPR forms by writing to the local SPR Center.
SPR response service is provided at no charge for one year after installation and may be
continued by subscription thereafter.
3.1

Software Performance Report Guidelines

These guidelines for RSTS/E SPR completion ensure that adequate information is included
to prevent delays in processing.
For all types of actual or suspected software problems, include the following with the SPR:
•

A complete description of the problem

•
•

The CPU type
The system disk type

•
•
•

The amount and type of memory
A log file showing the error and the steps you followed to cause it
If possible, a simple program or procedure which can be used to reproduce the problem

•

Any additional information which you may think is relevant

For problems associated with the RSTS/E monitor or crash analysis package (ANALYS),
also include:
•

The crash dump printed by ANALYS (which includes annotations, a listing of the symbol
table, and a list of all installed patches)

•

A machine readable copy (preferably a backup on 9-track or TK50 magnetic tape) of
your monitor and CRASH.SYS file

When submitting an SPE, concerning a Digital-supplied utility (CUSP), also include:
•
•

The name of the CUSP
A RUN of the CUSP which displays the header line, version number, and the occurring
problem, if possible

•

A listing of the account(s), and the account(s) attributes, in which the problem occurs

•

A complete listing of the CUSP (preferably on magnetic tape) if your installation has
made any nonstandard changes

l
RSTS/E V10.0 Maintenance Notebook

•

Listings of all relevant input and output files

•

A log file showing the problem
NOTE
No SPR, monitor or CUSP, will be considered unless ALL relevant Mandatory
patches published to date have been applied. Before submitting an SPR, you
should review the relevant section(s) of the Maintenance Notebook to ensure that
all Mandatory updates and patches to the program or package have been installed.

RSTS/E V10.0 Maintenance Notebook

Procedures for Updating RSTS/E Software

This section briefly describes the update procedures to be used for maintenance of RSTSIE
VIO.O. The procedures to be followed for updating the monitor and system programs when

installing a new RSTSIE system are described in the RSTS IE System Installation and Update Guide. The procedures for updating the software as part of normal system maintenance
are described in the RSTS IE System Manager's Guide.
Most corrections to RSTSIE software are done by replacing the affected components with
updated versions distributed on the next release of RSTSIE. These replacement modules are
automatically installed as part of the RSTSIE installation and update process.
In cases where a critical problem is discovered, Digital publishes an article in the RSTS IE
Software Dispatch describing the problem and suggesting possible workarounds until the
module is replaced in the next VIO update release. If no reasonable work-arounds are
available, a patching procedure may be included in the article so you can correct the defective
module. Step-by-step instructions on how to apply the patch are included.
Unless otherwise stated, Mandatory patches published in the RSTS IE Software Dispatch
should be installed as soon as possible. Since not all Mandatory patches apply to every
installation, patches to unused or optional components will fail when you attempt to apply
them. In such cases, the patch article describes how the patch will fail if it does not apply
to your system.
Be sure to file and maintain all RSTS IE Software Dispatch articles, even for unused components. Your site may choose at some future time to install additional components; these
components will then have to be brought up to the latest support level.
Some RSTS I E Software Dispatch articles include Feature patches, allowing you to modify
a component to enable an optional feature of that component. These Feature patches are
optional and not required to keep a component at its current support level. However, if you
encounter problems in a component containing optional features, you must report which
Feature patches have been installed when submitting a Software Performance Report (SPR).

4.1

Monitor Patching

Normally, problems discovered in a RSTSIE monitor are corrected by replacing the defective
component during the installation and update procedure. You must rebuild your system's
monitor each time you receive a new RSTSIE update to install any corrections made to the
monitor components.
If it should become necessary for you to apply a patch to your system's monitor, the RSTS IE
Software Dispatch article describing the problem will also explain how to apply the patch.
Normally, changes to the RSTSIE monitor are made using the off-line PATCH option of
INIT.SYS or the on-line program $ONLPAT.SAY. General descriptions of these patching
tools and how to use them are included in the RSTS IE System Installation and Update
Guide and the RSTS IE System Manager's Guide.

RSTS/E V10.0 Maintenance Notebook 13

The patching article includes specific instructions on how to apply the patch. The expected
dialogue is shown in the article as it should appear when you install the patch. If any
deviation occurs, you should immediately do the following:
2.

Halt the patching process
Restore any changes already made to their former values

Determine where the discrepancy occurred

4.2 Commonly Used System Program (CUSP) Module Replacement

Like the monitor, corrections to individual RSTSIE programs are made by replacing the
defective module with a replacement from the VIO.O Installation Kit. These replacement
modules are automatically installed whenever you install or update the package containing
the replacement program. For example, if a replacement module for the HELP.TSK program
is included on a RSTSIE installation kit, then that module will replace the copy ofHELP.TSK
on your system whenever you install or update the HELP package.
All replacement modules for bundled software will automatically be applied whenever you
install or update your RSTSIE software.
4.3 Installation Kits

RSTSIE Installation Kits contain the minimal software necessary to create a RSTSIE system, as well as replacement modules and/or patches for software supported under RSTSIE
VIO.O. The RSTSIE VIO.O Installation Kit contains all patches published in the RSTS IE
Vl0.0 Maintenance Notebook and in the RSTSIE Vl0.0 Software Dispatch Review. Each
subsequent RSTSIE Installation Kit will contain all of the components from the previous
installation kit, plus any new modules and/or patches published in the RSTS IE Software
Dispatch. Thus, you only need the most recent RSTSIE installation kit to update your
system to the current revision level.
Note that in some cases, patches previously published in the RSTS IE Software Dispatch will
become obsolete, since the correction provided by the patch is included in the replacement
module itself. In such cases, a new Dispatch article is published to supersede the previous
patch article.
The Cumulative Index published in the RSTS IE Software Dispatch indicates which installation kit first contained a patch or module replacement.
Procedures for using the installation kit to update standard RSTSIE software can be found
in the RSTS IE System Installation and Update Guide. Procedures for updating optional
layered software are usually found in the appropriate installation manual for the product.
4.4 Patches and Replacement Modules for Optional Layered Products

The RSTSIE VIO.O Installation Kit also contains patches and replacement modules for optional layered products. 1b install layered product patches or replacement modules, you
must first transfer all of the patches, replacement modules, and command files for that
product to a patch account (PATCH$ by default) on your system. This step is required for
both disk. and tape installation kits.

14 RSTS/E V10.0 Maintenance Notebook

1b transfer layered product update components from the RSTSIE installation kit to the
PATCH$ account, perform either of these steps:
•

During the installation procedure, type YES to the prompt:
Do you want to transfer the layered product update components from the
Installation kit ?

•

Invoke the DCL copy update command procedure by typing the DeL command line:
$ @[O,l]COPYUP package_name

where package_name is the name of the layered product you want to update.

RSTS/E V10.0 Maintenance Notebook 15

Software Product Descriptions and Option Bulletins

Periodically, new or revised Software Product Description (SPD) bulletins appear in the
RSTS / E Software Dispatch for various software products marketed by Digital. This section
of the notebook provides a convenient place to file these SPDs for future reference.

5.1

Software Product Descriptions

The Software Product Description (SPD) is the document that describes a software product.
Every SPD has a unique number, for example SPD 13.1.20. This number appears on the
first page of the SPD bulletin, at the far right hand side of the Product Name.
Note that the last part of the SPD number is the revision level, with 0 being assigned for
original issues of SPDs.

5.2

Option Bulletins

Periodically, new or revised Option Bulletins appear in the RSTS / E Software Dispatch for
various products marketed by Digital. This section of the notebook provides a convenient
place to file these bulletins. There is no filing scheme for option bulletins.

RSTS/E V10.0 Maintenance Notebook

6 RSTS/E V10.0 Articles
This section is the repository for all RSTSIE articles. It includes problem solutions, optional
feature patches, documentation errata, programming hints, and tips for better operation of
RSTSIE.
Anyone who installs a RSTSIE system (whether online under time sharing or as the initial version of the system) should become familiar with these articles. This should be a
continuing process of education as subsections are added and updated.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 0.1.1 N

RSTS/E V10.0 Component Summary
RSTS/E V10.O
RSTS/E Vl0.0 General Notes
System Notes

This article will be used to provide an updated list of all software components included
with RSTSIE VlO.O. Appendix C of the RSTS / E System Installation and Update Guide
contains a current list of these software components. If the list changes, this article will be
superseded to contain the current list.
Neither Appendix C of the RSTS / E System Installation and Update Guide nor this article
includes optional layered product components or temporary modules created during installation. Modules belonging to an optional package included with RSTS/E will only be present
if you choose to install that package on your system.
Listed with each module is its standard protection code and its expected location on your
system. Note that file protection codes play a critical role in the overall security of your
system. You should not change the protection code of any file included with RSTS/E unless
directed to do so. Changing a file's protection code to a different value may compromise
security or cause the program to fail in unpredictable ways.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 0.1.2 N

Announcing New Hardware Support forRA92 Disks
RSTS/E VI0.0
General Notes
System Notes

RA92 disk drives are now available for use on PDP-ll systems. RA92 disks are highperformance 1.5 gigabyte (GB) drives. They feature static dual porting like other Digital
Storage Architecture (DSA) family disks. They use the same form factor as the existing
RA90 disk drive. Two RA92 drives fit in a 10.5-inch high portion of a standard rack (using
physical space equivalent to one RA8l). Up to six drives can be configured in the RA92CIFIHJJ cabinet. Up to eight drives can be configured in the SA800 storage array. Up to
six RA92 drives can be configured with up to eight RA70 drives in the SA850 storage array
cabinet (for a total of over 10 GB in a single 60-inch high cabinet). The RA92-NA is a single
drive to add to existing SA6xx or SA8xx storage array cabinets. The drives connect to Q-bus
systems using the KDA50 controller and to UNIBUS systems using the UDA50 controller.

Configuration Data

RA92 disks are initialized with a cluster size of 64. On systems that have many small files,
RA92 disks are recommended for use as auxiliary storage, rather than as the system disk.
For this reason, the SA850 is an ideal configuration using the RA70 as the system disk, and
the RA92 as a private disk.
PDP-lls support a maximum of two UDA50IKDA50 type controllers. Each controller can be
configured with a maximum of four drives. These drives can consist of any combination of
RA60, RA70, RA80, RA8l, RA82, RA90, or RA92 drives.
Where multiple systems are configured, larger numbers of drives can be configured to share
the same storage array cabinet, while being cabled to different systems.

RSTS/E Software Dispatch, July 1991

Seq. No. 0.1.3 N

Announcing New Hardware Support for DECserver 90l
RSTS / E VIO.O
General Notes
System Notes

The DECserver 90L is Digital's newest terminal server. Through it, you can connect up to
eight terminals or printers to your Ethernet network. The DEC server 90L is not downline
loaded; therefore, it can be configured in mixed networks or networks that contain only
RSTS/E systems. The server can be mounted in the new DEChub 90 distribution system
providing a maximum of 64 terminal ports.
The DECserver 90L has a maximum terminal speed of 38.4K bytes per second and supports
one session per terminal port. The DECserver 90L can be used for terminals or printers but
cannot be used for modem connections. It also offers security capabilities through the use of
password protection.
The DECserver 90L provides the ideal terminal server for RSTS/E sites upgrading from
hardwired terminals to an Ethernet Local Area Network (LAN), since only one session at a
time can be used. With its read-only memory (ROM) based microcode (no downline loading),
it is also the ideal terminal server for sites with only RSTS/E systems.

RSTS/E Software Dispatch, July 1991

Seq. No. 1.1.1 M

INIT Can Fail During Some RQDX Controller Accesses --..
Mandatory Patch
RSTS/E Vl0.0
Initialization
INIT.SYS Program Patches

Problem
During some accesses of disks on RQDX controllers, INIT can hang or abort with an unexpected trap through vector 4. This can occur during the DSKINT option, during rebuilding
of a disk, or after a power failure.

Solution
The following patching procedure corrects the problem. This problem will be corrected in afuture release.

Procedure

This is a required patch to the RSTSIE INIT.SYS Program. Since patching the distribution medium is not recommended, the patch must be installed every time the COpy
option is used to copy INIT.SYS from the distribution medium. Any copy of the patched
INIT.8YS will propagate the fix.

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? INIT.SYS

This patch can also be installed using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? INIT.SYS
File found in account [0,1]

(RETURN for manual patch installation)

The patch is as follows:
Base address? PATCH
Offset address? 4
Base
Offset Old
045352 000004 103003
045352 000006 004737
045352 000010 005226
045352 000012 000261
045352 000014 000207
045352 000016 000000
045352 000020 000000
045352 000022 ??????
Offset address? AZ

New?
? 103005
? 10046
? 4737
? GETCLK
? 12600
? 261
? 207
(CTRL/Z for new offset)
? AZ
(CTRL/Z for new base)

RSTS/E Software Dispatch, January 1991

Seq. No. 1.1.1 M

Base address? $$0101
Offset address? 0
Base
Offset Old
152034 000000 ??????
152034 000002 ??????

New?
? Q!l
? AC

(up-arrow/C to exit;CTRL/C for INIT)

RSTS/E Software Dispatch, January 1991

Seq. No. 1.2.1 N

Unnecessary Error Message When Booting 800 BPI Tape on TM02
RSTS/E Vl0.0
Initialization
INIT.SYS Notes
An unnecessary error message prints when an 800 BPI magnetic tape on a TE16 subsystem
that uses a TM02 formatter is booted from the Option: prompt of INIT.SYS. For example:
MHO Error

MTCS1

MTWC

MTFC

MTCS2

MTDS

MTER

MTTC

144270

000000

001007

000100

154640

102100

102300

The error message you receive may be different.
This message prints as a result of the density autosizing process that occurs on TM02
formatters and does not indicate an actual hardware error.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 1.3.1 R

First TMSCP Drive on System Must Be Unit 0 -

INIT.SYS Restriction

RSTS/E V10.O
Initialization
INIT.SYS Restrictions
If your system contains only one TMSCP tape drive (TUB1 or TK50), it must be designated
unit O. If you have two drives and unit 0 does not work, you must make the working drive
unit 0 and either disconnect the non-working drive or use the HARDWR DISABLE option
of INIT.SYS to disable it.

The controller number must also match the drive number. For example:
•

Valid:
Name

Address Vector Comments

MUO:

174500
160504

MU1:

•

P350
P354

TU81
TK50

Units: 0(TU81}
Units: 1 (TK50)

Invalid:
Name

Address Vector Comments

MUO:

174500
160504

MU1:

P350
P354

TU81
TK50

Units: 1(TU81}
Units: o (TK50)

RSTS/E V10.0 Maintenance Notebook

Seq. No. 1.3.2 R

MT/MM Tapes Must Be Booted From Unit 0 -

INIT.SVS Restriction

RSTS / E Vl0.0
Initialization
INIT.SYS Restrictions
Magnetic tape distributions of RSTS or any bootable recovery tapes of RSTS must be booted
from unit zero. This problem affects MM and MT drives.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 2.1.1 N

Installation Flag Files
RSTS/E Vl0.0
System Installation and Update
Installation / Update Notes

Flag files are files of zero length that are used by the Installation Procedure as status
indicators. The flag files used in VIO.O are:
1.

The file VEROOL.SYS in account [1,2]

Any file with a filetype of .OOL

These flag files should not be deleted. Doing so may cause certain layered product installations and updates to fail.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 2.3.1 R

RSTS/E Version 10.0 Installation Procedure Restrictions
RSTS/E VIO.O
System Installation and Update
Installation / Update Restrictions

Problem
The following restrictions exist in the RSTSIE Version 10.0 installation procedure:
1.

During installation, if you answer NO to any of the "Do you want to proceed" prompts,
when you do proceed, the installation will assume that the installation kit is on the device
that was used to originally install RSTSIE on your system. It will override the device
you may have already specified to the installation procedure.
If you know that you will be answering NO to any of the "Do you want to proceed"
prompts, then ensure that the installation kit is on the device used to originally install
RSTSIE on your system. This device will be the default for the "Installation device"
prompt.

If you are installing the SORTIMERGE package to a target disk, that is, a disk other than
the system disk, the system logical LB: will be assigned to the target disk. The logical
will be reassigned back to its original assignment after SORTIMERGE is installed, but
it can cause problems for the other users on the system during the installation. Also,
if the installation is aborted, then the logical may not be reassigned back to its original
assignment.

If you are going to install the SORTIMERGE package to a target disk, inform your users
that the system logical LB: will not be available. After the installation is complete,
ensure that the logical is assigned to its original assignment.

RSTS/E Software Dispatch, December 1990

Seq. No. 2.3.2 R

Cannot Mount Disks at the Beginning of the Installation
Procedure
RSTS/E VIO.O
System Installation and Update
Installation / Update Restrictions

Problem
When you update an earlier version of RSTSIE to RSTSIE Version 10.0, the installation
procedure prompts you, "Are you ready to proceed?". Previously, you could have answered
"NO" to this prompt to allow you to issue the DCL MOUNT command to mount auxiliary
disks before continuing the installation.
In Version 10.0, the disk MOUNT function has been moved from the DIGITAL Command
Language (DCL) run-time system (DCL.RTS) to the DCLAUX.TSK program.
As a result of this change, you can no longer mount disks after answering "NO" to the first "Are
you ready to proceed?" prompt, because the DCLAUX program has not yet been restored at
this point in the installation. Instead, you must wait until the required _SY:[1,2] components
(including DCLAUX) have been restored. It will be restored after the first "Are you ready to
proceed?" prompt. This means that you will be allowed to mount auxiliary disks at the next
"Are you ready to proceed?" prompt, which is after the Monitor section.
Once your system has been updated to RSTSIE Version 10.0, this problem will not occur. This
restriction will be lifted in a future release of RSTSIE.

RSTS/E Software Dispatch, February 1991

Seq. No. 2.3.3 R

Monitor Installation on Target Disk Uses System Disk for
Template
RSTS/E V10.O
System Installation and Update
Installation / Update Restrictions

Problem
If you inf!tall a monitor on a target disk, the default for the "Template monitor" prompt will
be the currently installed monitor on the system disk, instead of a monitor on the target disk.

Solution
If you do not want to use that monitor for the template, then type a question mark (?) and
press <RETURN> to display a list of the monitors on the target disk. Then, enter the name
of the monitor you wish to use as the template monitor.

RSTS/E Software Dispatch, February 1991

Seq. No. 2.3.4 R

Online Monitor Installation Fails if Prebuilt Monitor Chosen
RSTSIE VI0.0
System Installation and Update
Installation I Update Restrictions

Problem
If you specify "SY:" as the RSTStE distribution device to the installation procedure to perform

an online monitor installation, the installation procedure allows you to choose the prebuilt
monitor or to build your own monitor. If you choose the prebuilt monitor, the installation
procedure aborts. The prebuilt monitor is only available when you install from the RSTStE
distribution kit.

Solution
This problem is a restriction for RSTStE Version 10.0. If you want to install the prebuilt
monitor, you must use your RSTStE distribution kit. This problem will be fixed in a future
release.

RSTS/E Software Dispatch, April 1992

Seq. No. 3.1.1 M

DEASSIGN SYS Call Can Crash System - Mandatory Patch
RSTS/E VI0.0
Executive
Monitor Patches

Problem
The DEASSIGN SYS call, when issued without paratneters, causes the command recall buffer
to be corrupted in such a way that recalling a command line can crash the system. In
addition, it does not deassign some logicals as expected. Since this SYS call is used by the
LOGIN program, the crash can occur shortly after issuing a LOGIN command from a loggedin account.

Solution
The following patching procedure corrects this problem. This problem will be corrected in a
future release.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executives. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

(RETURN for installed monitor SIL)

This patch can be installed using ONLPAT, the online patching program. Note, however,
that if the patch is applied on line to the installed monitor SIL, it will not take effect
until the system is rebooted.
RUN $ONLPAT
Command File Name? <CR>
(RETURN for patch installation)
File to patch? <CR>
(RETURN for installed monitor SIL)
File found in account [0,1]

The patch is as follows:
Module name? EMT
Base address? CAL@OVR
Offset address? 3540
Base
Offset Old
New?
?????? 003540 012701 ? 137
?????? 003542 000010 ? EMTPAT@OVR
(CTRL/Z for new offset)
?????? 003544 000401 ? AZ
Offset address? AZ
(CTRL/Z for new base)
Base address? EMTPAT@OVR
Offset address? 0
Base
Offset Old
New?
?????? 000000 000000 ? 12701
?????? 000002 000000 ? 10
?????? 000004 000000 ? 5726
?????? 000006 000000 ? 207

RSTS/E Software Dispatch, February 1991

Seq. No. 3.1.1 M

?????? 000010 000000
?????? 000012 000000
?????? 000014 000000
?????? 000016 000000
?????? 000020 000000
?????? 000022 000000
?????? 000024 000000
?????? 000026 000000
?????? 000030 ??????
Offset address? AZ
Base address? FSS@OVR
Offset address? 6056
Base
Offset Old
?????? 006056 005764
?????? 006060 000030
?????? 006062 001352
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0301
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

? 5764
? 30
? 1004
? '12716
? CLRLOG@OVR-76
? 12746
? CLRLOG@OVR
? 207
(CTRL/Z for new offset)
? AZ
(CTRL/Z for new base)
New?
? 4737
? EMTPAT@OVR+10
? AZ
(CTRL/Z for new offset)
(CTRL/Z for new base)
(CTRL/Z for new module)

New?
? Q!1

? AC

(up-arrow/C to exitiCTRL/C for INIT)

RSTS/E Software Dispatch, February 1991

Seq. No. 3.1.2 M

Protection Violation Error When Issuing the .RTS Directive Mandatory Patch
RSTS/E Vl0.0
Executive
Monitor Patches

Problem
Applications that issue the .RTS directive to transfer control to another run-time system
while preserving the job context may fail with a "?Protection violation" error. The call fails to
account for the size of the job header region when checking to see if the job size has exceeded
the maximum size allowed by the run-time system to which you are transferring control.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? EMT
Base address? CAL@OVR
Offset address? 256
Base
Offset Old
?????? 000256 126163
?????? 000260 000024
?????? 000262 000034
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0301
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? 240
? 120263
? AZ
CTRL/Z for new offset
CTRL/Z for new base
CTRL/Z for new module

New?
? Q!2
? AC

RSTS/E Software Dispatch, July 1991

up-arrow/C to exitiCTRL/C for INIT

Seq. No. 3.1.3 M

(

Run-Time System May Become Permanent -

Mandatory Patch

RSTSIE VlO.O

Executive
Monitor Patches

Problem
During the Create a Job system function call, the job's header area is copied to the new
job. This copy is done by swapping the header out to disk. If the new job changes runtime systems while it is being swapped back into memory, the incorrect run-time system
usage values will be incremented and decremented. This may result in the run-time system
becoming permanently locked into memory.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? RSTS
Base address? SWRTS
Offset address? 42
Base
Offset Old
?????? 000042 001001
?????? 000044 110000
?????? 000046 060063
Offset address? AZ
Base address? PATCH
Offset address? 0

New?
? 4737
? PATCH
? AZ
CTRL/Z for new offset
CTRL/Z for new base

RSTS/E Software Dispatch, November 1991

Seq. No. 3.1.3 M

Base
Offset Old
?????? 000000 000000
?????? 000002 000000
?????? 000004 000000
?????? 000006 000000
?????? 000010 000000
?????? 000012 000000
?????? 000014 000000
?????? 000016 000000
Offset address? AZ
Base address? $$0301
Offset address? a
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? 1404
? 122761
? 34
? 25
? 1001
? 110000
? 207
CTRL/Z for new offset
? AZ
CTRL/Z for new base
New?
? Q!4
? AC

up-arrow/c to exit;CTRL/C for INIT

RSTS/E Software Dispatch, November 1991

Seq. No. 3.3.1 R

DCl log File Corruption on Full Disk -

Monitor Restriction

RSTSIE Vl0.0
Executive
Monitor Restrictions
If the disk on which a DeL or Batch log file is being written becomes full, no more data is
written to the log file. As space on the disk becomes available,the resultant log file may
contain one or two blocks of random data.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 3.4.1 F

Changing Special LOGIN Terminal -

Terminal Service Feature Patch

RSTSIE V10.O
Executive
Terminal Service Patches
The number of jobs that can log in to a RSTSIE system is limited by the swapping space
available, the JOB MAX set at system startup time, and the login setting (set by the SET
SYSTEMI[NO]LOGINS command). However, the console terminal (KBO:) is a special ter~
minaI, and can log in regardless of the login setting, provided that swapping space and JOB
MAX permit.
With the following patch, one or two special keyboards can be selected, or this feature can
be disabled entirely.

Procedure
1.

This is a feature patch to the RSTSIE VIO.O monitor. It may be installed in any target
monitor SIL.

Decide which terminals should be allowed to log in regardless of the login setting, and
use those numbers as m and n in the patch in step 5. If you want to allow only one
terminal, use its number as m and use -1 in place of n. If you want to disable this
feature, use -1 in place of both m and n. Be sure you include the decimal point after
the new value of m or n so that it is inte:rpreted as a decimal number.

The patch described in Step 5 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

(RETURN for installed monitor SIL)

This patch can be installed manually using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR> (RETURN for manual installation)
File to patch? <CR>
(RETURN for installed monitor SIL)
File found in account [0,1]

This feature patch is contained in the file PA0304.001 as part of the UPDATE package.
To t:ransfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure. 1

The patch file for this patch requires manual editing to include installation specific parameters before it can be successfully
installed.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 3.4.1 F

The patch is as follows:
Module name? KIN
Base address? •• CTZ .@OVR
Offset address? 0
Offset Old
New?
Base
?????? 000000 000000 ? m.*2
?????? 000002 001407 ? "Z
Offset address? "Z
Base address? .. CTY .@OVR
Offset address? 0
Offset Old
New?
Base
?????? 000000 177777 ? n.*2
?????? 000002 001404 ? "Z
Offset address? "Z
Base address? "Z
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!l
?????? 000002 ?????? ? "C

RSTS/E V10.0 Maintenance Notebook

(or -1, from step 2)
(CTRL/Z for new offset)
(CTRL/Z for new base)

(or -1, from step 2)
(CTRL/Z for new offset)
(CTRL/Z for new base)
(CTRL/Z for new module)

(up-arrow/C to exit; CTRL/C for INIT)

Seq. No. 3.4.2 F

Input Escape Sequence Handling -

Terminal Service Feature Patch

RSTS/E Vl0.0
Executive
Terminal Service Patches
RSTS/E allows multiple character incoming escape sequences. The RSTS / E Programming
Manual fully describes the escape sequence handling.
One of the multicharacter escape sequences is ESCape followed by "P", followed by one
modifier character. On the VT52 terminal, the upper left-hand key on the auxiliary keypad
(usually blue) generates ESC P. When the VT100 terminal is operating in VT52 mode, the
upper left-hand key on the auxiliary keypad (usually labeled "PF1") generates ESC P. If
the terminal user types this key and then any other graphic key, the whole sequence is
gathered by the terminal service and delivered to the application program. None of the
sequence is echoed. Thus, the blue key can be considered a "function" key to be followed by
some function code character.
On the other hand, some existing applications using the VT52 may expect this key to generate a stand-alone escape sequence with no required (or desired) modifier character. You
may install the following patch to change the terminal service so that the ESCape, "P" sequence does not expect a modifier character. Note that this patch affects all terminals on
the system.
Procedure
1.

This is a feature patch to the RSTS/E monitor. It may be installed in any target monitor
SIL.

The patch described in Step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

(RETURN for installed monitor SIL)

This patch can be installed manually using ONLPAT, the on-line patching program:
RUN $ONLPAT
Command File Name? <CR> (RETURN for manual installation)
File to patch? <CR>
(RETURN for installed monitor SIL)
File found in account [0,1]

This feature patch is contained in the file PA0304.002 as part of the UPDATE package.
To transfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 3.4.2 F

The patch is as follows:
Module name? KIN
Base address? .. ESCP@OVR
Offset address? 0
New?
Base
Offset Old
?????? 000000 050001 ? Q&177400
(CTRL/Z for new offset)
?????? 000002 ????j? ? ~Z
Offset address? ~Z
(CTRL/Z for new base)
Base address? ~Z
(CTRL/Z for new module)
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!2
?????? 000002 ?????? ? ~C (up-arrow/C to exit; CTRL/C for INIT)

2 RSTS/E V10.0 Maintenance Notebook

Seq. No. 3.4.3 M

Host-Initiated lAT Connections May Crash System .. Mandatory
Patch
RSTS / E V10.O
Executive
Terminal Service Patches

Problem
An attempt to establish a LAT connection from your RSTS/E system (a Host-Initiated Connection) to a busy port on a terminal server may crash the system.

Solution
The following patch procedure corrects the problem.

Procedure

This is a required patch to the RSTS/E Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

(RETURN for installed monitor SIL)

The patch is as follows:
Module name? LAT
Base address? LATAPP@OVR
Offset address? 2200
Base
Offset Old
New?
?????? 002200 077067 ? 77072
?????? 002202 000137 ? AZ
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!4
?????? 000002 ?????? ? AC

RSTS/E Software Dispatch, December 1990

(CTRL/Z for new offset)
(CTRL/Z for new base)
(CTRL/Z for new module)

(up-arrow/C to exit;CTRL/C for INIT)

Seq. No. 3.4.4 M

Three Problems in Terminal Service -

Mandatory Patch

RSTS/E V10.0
Executive
Terminal Service Patches

Problem
Three problems were discovered in terminal service for Version 10.0. They are as follows:
1.

If a terminal is closed while output is being sent to the terminal, and is then reopened
before the output completes, some terminal attributes may be lost after the OPEN occurs. The terminal attributes that may be lost include the terminal open modes, private
delimiters, and terminal characteristics.
For example, if output is sent to the terminal, followed by a CLOSE, then the terminal
is opened in transparent controls mode, it is possible that the mode will be lost before
a read from the terminal takes place. Furthermore, the setting of one or more private
delimiters or terminal characteristics after the OPEN can be lost, because ofthe buffered
output continuing to be sent to the terminal after the OPEN occurs.

Under certain conditions, command line editing and command recall through the use of
the arrow and functions keys can become disabled at the DIGITAL Command Language
(DCL) level, even though the terminal characteristics indicate these features are enabled.
The function keys (for example, F12), and the arrow keys cause an escape sequence to
be displayed on the screen instead of performing their line editing and command recall
functions.

On certain central processing units (CPUs), commands entered at the RSX keyboard
monitor are treated as "program input" for purposes of command line recall, instead of
"keyboard monitor" commands. As a result, switching to another keyboard monitor from
RSX will cause any saved RSX commands to be erased. Levels of command line recall
are described in the RSTS / EVersion 10.0 System User's Guide, page 1-14.

Solution
The following patching procedure corrects these problems. They will be corrected in a future
release.

Procedure
1.

This is a required patch to the RSTS/E Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

(RETURN for installed monitor SILl

(
RSTS/E Software Dispatch, March 1991

Seq. No. 3.4.4 M

(RETURN for patch installation)
(RETURN for installed monitor SIL)

The patch to correct these problems is as follows:
Module name? KBD
Base address? KBDVRM@OVR
Offset address? 2620
Base
Offset Old
New?
120242 002620 000200 ? 204
120242 002622 000040 ? AZ
(CTRL/Z for new offset)
Offset address? 3650
Base
Offset Old
New?
120242 003650 026761 ? <CR>
(no change; verify only)
120242 003652 ?????? ? Q-2
120242 003654 ?????? ? AZ
(CTRL/Z for new offset)
Offset address? 3754
Base
Offset Old
New?
120242 003754 016402 ? 4737
120242 003756 000022 ? KBDPAT@OVR+76
120242 003760 042702 ? AZ
(CTRL/Z for new offset)
Offset address? AZ
(CTRL/Z for new base)
Base address? KBDPAT@OVR
Offset address? 76
Base
Offset Old
New?
120000 000076 000000 ? 16402
120000 000100 000000 ? 22
120000 000102 000000 ? 42761
120000 000104 000000 ? 2200
120000 000106 000000 ? 10
120000 000110 000000 ? 207
120000 000112 ?????? ? AZ
(CTRL/Z for new offset)
Offset address? AZ
(CTRL/Z for new base)
Base address? AZ
(CTRL/Z for new module)
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!10
?????? 000002 ?????? ? AC
(Up-arrow/C to exit; CTRL/C for INIT)

RSTS/E Software Dispatch, March 1991

Seq. No. 3.4.5 M

Problem with TEeO Mode -

Mandatory Patch

RSTS/E V10.0
Executive
Terminal Service Corrections

Problem
When you type command strings at a terminal, TECO considers certain ASCII characters to
have special meaning. Most of the special characters are immediate action commands that
cause TECO to perform a specified function immediately instead of waiting for the double
ESCAPE that terminates a command string. Immediate action commands can be entered at
any point in a command string, even in the middle of a command or text argument. A list of
immediate action commands can be found in Table 4-1 of the PDP-11 TECO User's Guide.
The immediate action commands that begin with the Ctrl/G character do not function as
expected in Version 10.0. In order for the commands to be recognized by TECO, you must
pr~ss a delimiter such as the Return key.

Solution
The following patching procedure corrects this problem.

NOTE
TECO is an unsupported component of the RSTSIE Distribution Kit.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? KIN
Base address? TERINC@OVR
Offset address? 1630

RSTS/E Software Dispatch, May 1991

Seq. No. 3.4.5 M

Base
Offset Old
New?
121306 001630 004767 ? 137
121306 001632 002064 ? TERINC@OVR+2136
CTRL/Z for new offset
121306 001634 000261 ? AZ
Offset address? AZ
CTRL/Z for new base
Base address? AZ
CTRL/Z for new module
Module name? KBD
Base address? KBDVRM@OVR
Offset address? 2334
Base
Offset Old
New?
120242 002334 004737 ? <CR> no change; verify only
120242 002336 145002 ? KBDPAT@OVR+1l2
CTRL/Z for new offset
120242 002340 001144 ? AZ
Offset address? AZ
CTRL/Z for new base
Base address? KBDPAT@OVR
Offset address? 112
Base
Offset Old
New?
120000 000112 000000 ? 4737
120000 000114 000000 ? TTISGL@OVR
120000 000116 000000 ? BNE+2
120000 000120 000000 ? 105761
120000 000122 000000 ? 32
120000 000124 000000 ? 207
120000 000126 000000 ? AZ
CTRL/Z for new offset
Offset address? AZ
CTRL/Z for new base
Base address? AZ
CTRL/Z for new module
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!20
?????? 000002 ?????? ? AC
up-arrow/C to exit;CTRL/C for INIT

RSTS/E Software Dispatch, May 1991

Seq. No. 3.4.6 M

Inappropriate Character Echoing -

Mandatory Patch

RSTS/E VI0.0
Executive
Terminal Service Corrections
*** Supersedes June 1991 RSTSIE Software Dispatch Seq. No. 3.4.6 M***

Problem
When the error "?Keyboard wait exhausted" (ERR=15%) is returned to a program, character
echoing sometimes behlives inappropriately. Characters can be echoed more than once on the
terminal, often with the whole command redisplayed when a new character is typed. This
behavior. makes it nearly impossible to distinguish what is truly on the command line. In
other situations, character echoing can stop altogether.
The behavior depends on how the program deals with error 15. If the program resumes to
do some processing, character echoing may stop. If the program issues another read request,
the duplicate character echoing may result.
The behavior described above can also differ depending on the ![NO]ANSI and the ISCOPE
terminal characteristic settings.
Some known examples of failures are:
•

After a full logout on a hardwired terminal that is permanently set to ISCOPE, if you
type ahead while the logout information is printed, then hit another character after a
few seconds, characters will be displayed twice.

•

If the unsupported ATPK program is run interactively (ATPK LOGFIL=KB:), character
echoing will stop after a few seconds until a delimiter or the DELETE key is hit.

•

Any user program that traps error 15, and reissues a read request, may see either characters echoed more than once, or perhaps no echoing of characters at all.

NOTE
This patch supersedes June 1991 Article 3.4.6 M, which could result in the
system either crashing or hanging. This would only occur after a job which
had detached continued running and exited a program. The patch procedure
detailed in step 4b removes the June 1991 patch and fixes the problem.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

NOTE
This solution results in a minor restriction involving the displaying of the
command line after a "?Keyboard wait exhausted" error occurs. After this
error is generated, if at the next prompt the user types either CTRUR or
CTRLfI', or if a broadcast to the terminal occurs, the command line (if any)
may not be positioned correctly on the screen when it is redisplayed. This

RSTS/E Software. Dispatch, September 1991

Seq. No. 3.4.6 M

could cause difficulty editing a command line. This condition is only a problem at the interactive level, and may be cleared by hitting any delimiter such
as RETURN or CTRUC.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 below can be installed using the PATCH option ofINIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

This patch supersedes a previously published patch. If you did not install the June
1991 Article 3.4.6 M, apply the patch described in step 4a; otherwise, install the patch
described in step 4b.
a.

Apply this patch only if you did not install the June 1991 Article 3.4.6 M:
Module name? DSK
Base address? TIM
Offset address? 242
Base
Offset Old
?????? 000242 142761
?????? 000244 000040
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? 407
? AZ

CTRL/Z for new offset
CTRL/Z for new base
CTRL/Z for new module

New?
? Q!40
? AC

up-arrow/C to exitiCTRL/C for INIT

Apply this patch only if you did install the June 1991 Article 3.4.6 M:
Module name? DSK
Base address? TIM
Offset address? 242
New?
Base
Offset Old
?????? 000242 152761 ? 407
?????? 000244 000040 ? <CR>
?????? 000246 000105 ? 104
?????? 000250 000404 ? 152761
?????? 000252 000100 ? AZ
Offset address? AZ
Base address? AZ
Module name? KBD
Base address? KBDVRM@OVR
Offset address? 2666
New?
Base
Offset Old
?????? 002666 042761 ? 142761
?????? 002670 020040 ? 40
?????? 002672 000104

no chanqei verify only
CTRL/Z for new offset
CTRL/Z for new base
CTRL/Z for new module

CTRL/Z for new offset

RSTS/E Software Dispatch, September 1991

Seq. No. 3.4.6 M

Offset address? ~Z
CTRL/Z for new bas8
Base address? ~Z
CTRL/Z for new module
Module name? KIN
Base address? TERINC@OVR
Offset address? 4304
New?
Base
Offset Old
?????? 004304 042761 ? 142761
?????? 004306 020040 ? 40
CTRL/Z for new offset
?????? 004310 000104 ? AZ
CTRL/Z for new base
Offset address? ~Z
CTRL/Z for new module
Base address? ~Z
Module name? TERCLS
Base address? TERCLS@OVR
Offset address? 1246
Base
Offset Old
New?
?????? 001246 012361 ? 112361
no change; verify only
?????? 001250 000044 ? <CR>
?????? 001252 112323 ? 112361
?????? 001254 042713 ? 45
?????? 001256 020100 ? 112361
?????? 001260 000240 ? 103
CTRL/Z for new offset
?????? 001262 042761 ? ~Z
Offset address? ~Z
CTRL/Z for new base
Base address? AZ
CTRL/Z for new module
Module name? GEN
Base address? SCH@OVR
Offset address? 3542
Base
Offset Old
New?
?????? 003542 004737 ? 016704
?????? 003544 120000 ? 052544
CTRL/Z for new offset
?????? 003546 105064 ? ~Z
Offset address? AZ
CTRL/Z for new base
Base address? GENPAT@OVR
Offset address? 0
Base
Offset Old
New?
120000 000000 011204 ? 0
120000 000002 132764 ? 0
120000 000004 000040 ? 0
120000 000006 000105 ? 0
120000 000010 001410 ? 0
120000 000012 042764 ? 0
120000 000014 020040 ? 0
120000 000016 000104 ? 0
120000 000020 152764 ? 0
120000 000022 000100 ? 0
120000 000024 000104 ? 0
120000 000026 105064 ? 0
120000 000030 000106 ? 0
120000 000032 013704 ? 0
120000 000034 001016 ? 0
120000 000036 000207 ? 0
up-arrow/C to exit;CTRL/C for INIT
120000 000040 ?????? ? ~C

RSTS/E Software Dispatch, September 1991

Seq. No. 3.4.7 M

Private Delimiters Cause Problems with Command Recall Mandatory Patch
RSTS / E VIO.O
Executive
Terminal Service Corrections

Problem
Setting a private delimiter character (or mask) causes improper behavior when recalling
commands. The most severe problems occur when you set the RETURN character (ASCII
13) as a private delimiter. For example, if you issue the Digital Command Language (DCL)
command SET TERMINAL / DELIMITER=13, the following may result:
•

A system crash. If you leave DCL then recall a command upon returning, or if you issue
the DCL RECALL command with a text or index parameter, the system may crash.

•

A disjointed RECALLIALL display. The display may contain extraneous characters, may
contain commands that you did not type at that level, or may loop continuously, forcing
you to hit CTRLlC to exit the loop.

Another problem may result from setting any character other than RETURN as a private
delimiter. When recalling a command, the monitor processes each character of the command.
If the command contains a private delimiter, the delimiter will cause the monitor to send the
partial command to the program or run-time system, satisfying the read. The monitor will
then continue to send the rest of the characters of the recalled command.
This may result in undesirable behavior.
For example, suppose you issue the DCL command SET TERMINAL / DELIMITER="E",
which makes "E" a private delimiter. If you then hit the up arrow (to recall the SET TERMINAL command), the monitor will recall the "S", and upon encountering the private delimiter
"E", will execute S as a command. The monitor will continue to send characters to your terminal, executing the command every time an "E" is encountered, until the last character of
the SET TERMINAL command is processed.

Solution
The following patching procedure corrects these problems. They will be corrected in a future
release.
The monitor will now recall a command either to the end of the command, or until the first
private delimiter is encountered. In the example, the monitor will stop sending characters to
your terminal as so()n as it sees the private delimiter (E), displaying but not executing the
command S. All characters following the delimiter in the recalled command will be ignored.
They can be recalled later, once the private delimiter is removed.

NOTE
Digital recommends that you do not use private delimiters at the DeL level,
since if not properly used, could cause the unexpected execution of a command before you have a chance to complete it.

l
RSTS/E Software Dispatch, June 1991

Seq. No. 3.4.7 M

Procedure
1.

This is a required patch to the RSTS/E Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? KBD
Base address? TERREC@OVR
Offset address? 762
Base
Offset Old
New?
131634 000762 010446 ? 4437
131634 000764 010546 ? KBDPAT@OVR+l26
CTRL/Z for new offset
131634 000766 013777 ? "Z
Offset address? 1036
Base
Offset Old
New?
131634 001036 120227 ? 4737
131634 001040 000015 ? CHKDLM@OVR
131634 001042 001463 ? 103436
131634 001044 004737 ? 120227
131634 001046 144526 ? 15
131634 001050 103433 ? 1460
131634 001052 012704 ? "z
CTRL/Z for new offset
Offset address? "Z
CTRL/Z for new base
Base address? KBDPAT@OVR
Offset address? 126
Base
Offset Old
New?
120000 000126 000000 ? 4737
120000 000130 000000 ? CHKDLM@OVR
120000 000132 000000 ? 103403
120000 000134 000000 ? 10546
120000 000136 000000 ? 137
120000 000140 000000 ? TERREC@OVR+766
120000 000142 000000 ? 5726
120000 000144 000000 ? 137
120000 000146 000000 ? TERREC@OVR+1016
120000 000150 ?????? ? "z
CTRL/Z for new offset
Offset address? "z
CTRL/Z for new base
Base address? "z
CTRL/Z for new module
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!100
?????? 000002 ?????? ? "c
up-arrow/C to exitiCTRL/C for INIT

RSTS/E Software Dispatch, June 1991

Seq. No. 3.4.8 M

Characters Lost When Data Error Received -

Mandatory Patch

RSTS/E VI0.0
Executive
Terminal Service Corrections

Problem
It is possible that some characters could be lost if a program issues a series of conditional
reads to check for the presence of a complete command line.

This problem will only occur when an escape sequence is entered while a conditional sleep is
occurring. Furthermore, this problem will only occur if the conditional sleep is immediately
followed by a conditional read which results in a "?Data error on device" error because the
escape sequence was not completely processed by the monitor at the time of the read.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? KBD
Base address? KBDVRM@OVR
Offset address? 10532
Base
Offset Old
New?
120242 010532 122702 ? 402
120242 010534 000200 ? AZ
CTRL/z for new offset
Offset address? AZ
CTRL/Z for new base
Base address? AZ
CTRL/Z for new module
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!200
?????? 000002 ?????? ? AC
up-arrow/C to exit;CTRL/C for INIT

RSTS/E Software Dispatch, June 1991

Seq. No. 3.4.9 M

Command Recall May Crash System -

Mandatory Patch

RSTS/E VIO.O
Executive
Terminal Service Corrections

*** Supersedes July 1991 RSTSIE VIO.O Software Dispatch Seq. No. 3.4.9 ***
Problem
Under certain rare circumstances, recalling a command may crash the system or result in
a corrupted RECALL!ALL display. This problem can only occur if command line recall is
used after detaching and reattaching to a job on which command line recall is not currently
available.

NOTE
This patch supersedes July 1991 Article 3.4.SM. The original patch results
in the incorrect behavior of command line recall while in the BASIC-PLUS
runtime system: when recalling lines longer than 90 characters, only a portion of the previous command was recalled. The enclosed patch corrects this
behavior.

Solution
The following patching procedure corrects this problem. This procedure applies whether or
not patch 3.4.9M is already installed. This problem will be corrected in RSTS/E Version 10.1
and later.

Procedure

This is a required patch to the RSTS/E Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RSTS/E Software Dispatch, June 1992

RETURN for patch installation
RETURN for installed monitor SIL

Seq. No. 3.4.9 M

The patch is as follows:
Module name? KBD
Base address? KBDVRM@OVR
Offset address? 2672
Base
Offset Old
New?
?????? 002672 000104 ? <CR> no change; verify only
?????? 002674 ?????? ? 105061
?????? 002676 ?????? ? 106
?????? 002700 012737 ? AZ
CTRL/Z for new offset
Offset address? AZ
CTRL/Z for new base
Base address? TERREC@OVR
Offset address? 2
Base
Offset Old
New?
?????? 000002 004537 ? 4737
?????? 000004 ?????? ? KBDPAT@OVR+202
?????? 000006 ?????? ? 240
?????? 000010 ?????? ? 240
?????? 000012 103772 ? AZ
CTRL/Z for new offset
Offset address? AZ
CTRL/Z for new base
Base address? KBDPAT@OVR
Offset address? 202
New?
Base
Offset Old
?????? 000202 000000 ? 4537
?????? 000204 000000 ? CALLM@OVR
?????? 000206 000000 ? RECOK@OVR
?????? 000210 000000 ? KINAP5@OVR
?????? 000212 000000 ? 103003
?????? 000214 000000 ? 4737
?????? 000216 000000 ? TERREC@OVR+2424
?????? 000220 000000 ? 261
?????? 000222 000000 ? 207
CTRL/Z for new offset
?????? 000224 ?????? ? "Z
CTRL/Z for new base
Offset address? AZ
CTRL/Z for new module
Base address? "Z
Module name? RSTS
Base address?· $$0304
Offset address? 0
New?
Base
Offset Old
?????? 000000 ?????? ? Q!400
up-arrow/C to exit;CTRL/C for INIT
?????? 000002 ?????? ? AC

RSTS/E Software Dispatch, June 1992

Seq. No. 3.4.10 M

Forced Characters Echoed Even Under NOECHO Patch

Mandatory

RSTSIE VIO.O
Executive
Terminal Service Corrections

Problem
As a result of the new Version 10.0 "Echo on Read" feature, characters are not echoed unless a
read is outstanding. A problem occurs if you force to a terminal on which echoing is disabled
with the intention that the forced characters are not to be displayed. If echoing is re-enabled
on the terminal before a read is posted, the characters will be displayed. This is not the
desired effect.

Solution
The following patching procedure corrects this problem. Note, however, that only the first
command forced to the terminal will honor the current state of echoing. Any characters
entered after a delimiter are placed in a special "type ahead" buffer and are not processed or
displayed until a subsequent read takes place.
This problem will be corrected in a future release.

Procedure

This is a required patch to the RSTS/E Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.8YS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RSTS/E Software Dispatch, August 1991

RETURN for patch installation
RETURN for installed monitor SIL

Seq. No. 3.4.10 M

The patch is as follows:
Module name? KBD
Base address? KBDVRM@OVR
Offset address? 5710
Base
Offset Old
New?
?????? 005710 132761 ? 4737
?????? 005712 004000 ? KBDPAT@OVR+160
?????? 005714 000001 ? 401
CTRL/Z for new offset
?????? 005716 001262 ? "Z
Offset address? "Z
CTRL/Z for new base
Base address? KBDPAT@OVR
Offset address? 160
Base
Offset Old
New?
120000 000160 000000 ? 132761
120000 000162 000000 ? 4000
120000 000164 000000 ? 1
120000 000166 000000 ? 1401
120000 000170 000000 ? 104412
120000 000172 000000 ? 152761
120000 000174 000000 ? 40
120000 000176 000000 ? 104
120000 000200 000000 ? 207
120000 000202 ?????? ? "z
CTRL/Z for new offset
Offset address? "z
CTRL/Z for new base
Base address? "z
CTRL/Z for new module
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!1000
up-arrow/C to exit;CTRL/C for INIT
?????? 000002 ?????? ? "C

RSTS/E Software Dispatch, August 1991

Seq. No. 3.4.11 M

Problem Processing Escape Sequences as Type Ahead Mandatory Patch
RSTS/E Vl0.0
Executive
Terminal Service Corrections

Problem
With echo on read, characters typed while a sleep occurs will be placed into a special "type
ahead" buffer. A sleep statement is terminated whenever a delimiter is typed on the terminal.
The delimiter is placed into the type ahead buffer, and the job is made runnable.
The escape character (ASCII 27) is a standard delimiter on RSTSIE. Thus, an escape character
or an escape sequence will cause a sleeping job to wake up. When an escape sequence is
allowed, it is the end of the escape sequence that terminates a sleep. In Version 10.0, when
an escape sequence is entered, the escape character wakes up the job, rather than the last
character of the escape sequence.
This behavior can cause problems in applications that issue conditional reads before the
entire escape sequence has been processed. A conditional read will result in a "?Data error
on device" error if there is not a complete line waiting to be read. This should not happen if
a sleep just awoke as the result of a line typed at the terminal.

NOTE
Sleeps can also awake because of events outside the control of your program. Examples of such an event are the setting of the system time or the
reception of a message for message receivers. The unexpected awakening of
your program can be avoided by using a WAIT statement and trapping for
"?Keyboard wait exhausted" errors, as opposed to SLEEPs and trapping for
"?Data error on device" errors.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.8YS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

(

RSTS/E Software Dispatch, August 1991

Seq. No. 3.4.11 M

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? KIN
Base address? TERINC@OVR
Offset address? 1244
Base
Offset Old
New?
?????? 001244 120227 ? 4737
?????? 001246 000015 ? KINPAT@OVR+74
?????? 001250 001405 ? "Z
CTRL/Z for new off.set
Offset address? "z
CTRL/Z for new base
Base address? KINPAT@OVR
Offset address? 74
Base
Offset Old
New?
120000 000074 000000 ? 120227
120000 000076 000000 ? 15
120000 000100 000000 ? BEQ+22
120000 000102 000000 ? 120227
120000 000104 000000 ? 33
120000 000106 000000 ? BNE+10
120000 000110 000000 ? 4537
120000 000112 000000 ? TERINC@OVR+4100
120000 000114 000000 ? BR+13
120000 000116 000000 ? 112761
120000 000120 000000 ? 200
120000 000122 000000 ? 41
120000 000124 000000 ? 5726
120000 000126 000000 ? 207
120000 000130 000000 ? 105761
120000 000132 000000 ? 41
120000 000134 000000 ? BEQ+2
120000 000136 000000 ? 4537
120000 000140 000000 ? TERINC@OVR+1342
120000 000142 000000 ? 5727
120000 000144 000000 ? 264
120000 000146 000000 ? 207
120000 000150 ?????? ? "Z
CTRL/Z for new offset
Offset address? "Z
CTRL/Z for new base
Base address? "Z
CTRL/Z for new module
Module name? RSTS
Base address? $$0304
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!2000
?????? 000002 ?????? ? "C
up-arrow/C to exit;CTRL/C for INIT

RSTS/E Software Dispatch, August 1991

Seq. No. 3.4.12 M

Host-Initiated Connections to Some Servers May Fail
Mandatory Patch
RSTS/E VIO.O
Executive
Terminal Service Corrections

Problem
RSTS/E does not allow host-initiated connections to terminal servers, such as the DECserver
90L, that use the LAT Version 5.2 protocol. This problem is only seen when attempting to
access a printer or modem device connected to a server running the Version 5.2 protocol.
Users iogging into the RSTS/E system from these servers will not experience this problem.
Issuing a SHOW SERVER command at your terminal server's Local> prompt will display the
version of the LAT protocol used by that server.

Solution
The following patching procedure corrects the above problem. It will be corrected in a future
release.

Procedure

This is a required patch to the RSTS/E Version 10.0 executives. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? LAT
Base address? LATAPP@OVR
Offset address? 1634
Base
Offset Old
New?
?????? 001634 001016 ? 101016
?????? 001636 105761 ? AZ
CTRL/Z for new offset
Offset address? AZ
CTRL/Z for new base
Base address? AZ
CTRL/Z for new module
Module name? RSTS
Base address? $$0304
Offset address? 0

RSTS/E Software Dispatch, October 1991

Seq. No. 3.4.12 M

Base
??????
??????

Offset
000000
000002

Old
??????
??????

New?
? Q!4000
? AC
up-arrow/C to exit;CTRL/C for INIT

RSTS/E Software Dispatch, October 1991

Seq. No. 3.4.13 M

Problem with Echo Control Mode -

Mandatory Patch

RSTS / E V10.O
Executive
Terminal Service Corrections

Problem
Occasionally, programs written to use echo control mode receive an INUSE error (ERR=3).
This causes the program to either behave improperly or abort.
For example, DECword (or a similar word processing utility) sometimes aborts with a fatal
error during program startup.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? KBD
Base address? KBDVRM@OVR
Offset address? 3404
Base
Offset Old
New?
?????? 003404 001004 ? 240
CTRL/Z for new offset
?????? 003406 026161 ? AZ
CTRL/Z for new base
Offset address? AZ
CTRL/Z for new module
Base address? ~Z
Module name? RSTS
Base address? $$0304
Offset address? 0
New?
Base
Offset Old
?????? 000000 ?????? ? Q!10000
up-arrow/C to exit;CTRL/C for INIT
?????? 000002 ?????? ? ~C

RSTS/E Software Dispatch, June 1992

Seq. No. 3.5.1 N

Modem Support on RSTS/E
RSTS/E Vl0.0
Executive
Terminal Service Notes

Notes on the DF224 Scholar Modem
When using the DF224 Scholar Modem on a RSTSIE system, RSTS requires that the Modem
Response option be set to abbreviated. Failing to set the response option to abbreviated may
cause speed select problems with modems connected to a terminal line which is set to autobaud.

RSTS also suggests that the Input Character Echo option be disabled when using the DF224
autodial feature. Disabling this feature will prevent text intended for the modem (i.e., the
telephone number) from being echoed back to the program.
The state of both these features can be altered by either changing a switch setting on the
switch pack located internally on the module, or through the soft select menu. If you alter
the state of these features by using the menu, then the settings will revert back to their
default state if the unit is powered down. Therefore, RSTS recommends that the states be
changed by changing the internal switch settings. To do this, you must set switch S1 to
the OFF position to disable Input Character Echo, and switch S3 to the OFF position to
set the Modem Response to abbreviated. Please refer to page A-3 of the Scholar 2400 Modem Owner's Manual (EK-DF224-0M-PRE) for a diagram of the switchpack and its factory
default settings.
Some DF224 modem may send "garbage" characters to the terminal just prior to sending
the disconnect message after the remote modem drops carrier. This is the way the modem
operates and is not a problem with RSTSIE.
NOTE
RSTSIE will only support Scholar Modems of revision level Bl or later. Determining
the revision level of your modem can be done by looking for a small white sticker
on the underside of the enclosure. This sticker should read "C.S. REv. Bl ECO".
Older versions of the DF224 have also shown over-speed problems which resulted
in intermittent loss of characters. This problem was corrected in revision level Bl.
Please also note that the DF224 Owner's Manual states that the Scholar Modem is
capable of transmitting data at 600 baud. The Scholar Modem at revision level Bl
does not support 600 baud.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 3.5.1 N

Notes on the DF112 Modem
The DF1l2-AA modem is a replacement for the DF03. It provides full-duplex asynchronous
mode for terminal data communication and synchronous mode for network data communication. The DF1l2 has auto dial capability and operates at both 300 and 1200 baud.

When the DF1l2 is connected to a DZll interface, the BUSY jumper or switch on the EIA
distribution panel must be disconnected for the line on which the modem is connected.
Interfaces other than the DZl1 do not require any special setup for dial-in communications.

Using Autodial (Dial-out) Features
RSTSIE requires that a modem be active before allowing communication with it. RSTSIE
detects activity by monitoring the presence of certain modem control signals. Supported
modems will assert these signals if the host system asserts the Data Terminal Ready (DTR)
signal. On RSTSIE, a program that wants to do this should execute the Hang Up a Dataset
SYS call (FO=-9) on the keyboard to which the modem is connected prior to dialing. For
example:
10
20

S$=SYS(CHR$(6%)+CHR$(-9%)+CHR$(45%)+CHR$(-1%»
!Set DTR on KB45:
OPEN 'KB45:' AS FILE #1%
!Open the keyboard

NOTE
It is important that the SYS call to set DTR be called prior to opening the terminal.
This call causes necessary parameters in the keyboard DDB to be reset.

Once DTR is established, the phone number can be passed to the modem and communication can begin. Please refer to the owner's manual that accompanied your modem for any
programming considerations.
RSTSIE follows strict modem control rules on the DHll interface with the DMll-BB option,
and on DHVlllDHUll-type interfaces. In particular, RSTSIE will not allow data to be sent
to a modem controlled keyboard unless the "Clear To Send" (CTS) signal has been asserted
.by the terminal device. Many modems do not normally assert this signal until a call has
been received, and may therefore require special setup or a nonstandard RS232 cable to
work as a dial-out modem on RSTSIE.

•

DF03Modem
To allow the data to be sent to the DF03, the CTS signal must be tied high in the DF03
modem. This can be done by turning S2-10 (jumper W30) on, as described on page 5-15
of the DF03 Modem Family User Guide (EK-ODF03-UG-002), or page 6-6 of the DF03
Modem User Guide (EK-ODF03-UG-001).

•

DF112 Modem
Unlike the DF03 modem, the DF1l2 does not have a switch pack setting to assert the
CTS signal. Therefore, the signal must be set high by connecting pin 5 to pin 4 within
the cable connector which plugs into the modem.

2 RSTS/E V10.0 Maintenance Notebook

Seq. No. 3.5.1 N

NOTE
RSTSIE does not support auto mal capability on the DHll interface for the
DF112 modem. Unlike the DHVlllDHUU type interface, attempting to set the
CTS signal high by tying to an existing signal win cause that signal to go low.
The DF112 can be used on DHU interfaces for mal-in purposes only.

•

DF224 Scholar Modem
The DF224 Scholar Modem automatically raises CTS when the DTR signal is raised
by the host. Therefore, other than disabling the Input Character Echo option and the
abbreviated modem response option described above, no other changes are required.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 3.5.2 N

Unexpected Abort From Captive Command File Will Not Hang Up
Dialup Line
RSTS/E VIO.O
Executive
Terminal Service Notes
To terminate a connection on a dialup line, the Terminal Driver deasserts the DTR (Data
Terminal Ready) modem control signal, which causes the modem to disconnect from the
telephone line. This is normally handled by the LOGOUT system utility. However, if you
access the system from a captive account over a dialup line and the command procedure you
are running aborts abnormally (without using LOGOUT), DTR will not be deasserted and
thus the connection will not be terminated.

A workaround to this is to trap all possible errors within the command procedure and exit
by using the LOGOUT command.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 3.7.1 M

Attaching to a Detached Job May Crash System - Mandatory
Patch
RSTS/E V10.O
Executive
File Processor Patches

Problem
An attempt to attach to a detached job that originated from a LAT connection may crash the
system.

Solution
The following patch procedure corrects the problem.

Procedure

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

(RETURN for installed monitor SIL)

This patch can be installed using ONLPAT, the online patching program. Note, however,
if the patch is applied on line to the installed monitor SIL, it will take effect immediately

unless you installed the overlay file. If you installed the overlay file, then you must
remove and reinstall the file for the patch to take effect. (See step 5.)
RUN $ONLPAT
Command File Name? <CR>
(RETURN for patch installation)
File to patch? <CR>
(RETURN for installed monitor SIL)
File found in account [0,1]

The patch is as follows:
Module name? OVR
Base address? LOG3
Offset address? 410
Base
Offset Old
?????? 000410 016146
?????? 000412 000006
?????? 000414 014302
Offset address? 426
Base
Offset Old
?????? 000426 012661
?????? 000430 000006
?????? 000432 016502
Offset address? 750
Offset Old
Base
?????? 000750 105261
?????? 000752 000006
?????? 000754 077014

New?
? 10546
? 5005
? AZ
(CTRL/Z for new offset)
New?
? 12605
? 240
? AZ
(CTRL/Z for new offset)
New?
? 4767
? 760-754
? AZ
(CTRL/Z for new offset)

RSTS/E Software Dispatch, December 1990

Seq. No. 3.7.1 M

Offset address? 760
Base
Offset Old
?????? 000760 000000
?????? 000762 000000
?????? 000764 000000
?????? 000766 000000
?????? 000770 000000
?????? 000772 ??????
Offset address? "Z
Base address? LOG3SI
Offset address? 0
Base
Offset Old
?????? 000000 000760
?????? 000002 ??????
Offset address? "Z
Base address? "Z
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? 5705
? BEQ+2
? 105261
? 6
? 207
(CTRL/Z for new offset)
? "Z
(CTRL/Z for new base)
New?
? 772
? "Z

New?
? Q!l
? "C

(CTRL/Z for new offset)
(CTRL/Z for new base)
(CTRL/Z for new module)

(up-arrow/C to exit;CTRL/C for INIT)

If you used the $ INSTALUOVERLAY command, then you must issue the following
commands for the patch to take effect:
$ REMOVE/OVERLAY<CR>
$ INSTALL/OVERLAY filespec<CR>

RSTS/E Software Dispatch, December 1990

Seq. No. 3.7.2 M

Dynamic Region Creation Can Crash System Patch

Mandatory

RSTS/E V10.O
Executive
File Processor Patches

Problem
Use of the UU.RTS directive to create a dynamic region can cause a memory corruption that
will, at some later time, cause the system to crash.

Solution
The following patching procedure corrects the problem. This problem will also be corrected
in a future release.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executives. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

(RETURN for installed monitor SIL)

This patch can be installed using ONLPAT, the online patching program. Note, however, that if the patch is applied on line to the installed monitor SIL, it will take effect
immediately (see step 5).
RUN $ONLPAT
(RETURN for patch installation)
Command File Name? <CR>
(RETURN for installed monitor SIL)
File to patch? <CR>
File found in account [0,1]

The patch is as follows:
Module name? OVR
Base address? RTS1
Offset address? 440
Base
Offset Old
?????? 000440 016246
?????? 000442 000006
?????? 000444 042726
?????? 000446 174000
?????? 000450 001005

New?
? 42762
? 174000
? 6
? 240
(up-arrow/C to exit;CTRL/C for INIT)
? "c

RSTS/E Software Dispatch, January 1991

Seq. No. 3.7.2 M

File to patch?
Module name? OVR
Base address? RTS6
Offset address? 156
Offset Old
Base
?????? 000156 005767
?????? 000160 ??????
?????? 000162 001431
Offset address? 200
Offset Old
Base
?????? 000200 003422
?????? 000202 110562
?????? 000204 000006
?????? 000206 032762
Offset address? 730
Base
Offset Old
?????? 000730 000000
?????? 000732 000000
?????? 000734 000000
?????? 000736 000000
?????? 000740 000000
?????? 000742 000000
?????? 000744 000000
Offset address? "Z
Base address? RTS6SI
Offset address? 0
Base
Offset Old
?????? 000000 000730
?????? 000002 ??????
Offset address? "Z
Base address? "Z
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

(same as step 2/3 above)

New?
? 5737
? TYPCRE
(CTRL/Z for new offset)
? "Z
New?
? 4767
? 524
? 240
? "Z

(CTRL/Z for new offset)

New?
? BLE+3
? 10562
? 6
? 207
? 5126
? 207
(CTRL/Z for new offset)
? "Z
(CTRL/Z for new base)

New?
? 744
? "Z

New?
? Q!2
? "C

(CTRL/Z for new offset)
(CTRL/Z for new base)
(CTRL/Z for new module)

(up-arrow/C to exit;CTRL/C for INIT)

If you used the $ INSTALUOVERLAY command, then you must issue the following
commands for the patch to take effect:
$ REMOVE/OVERLAY<CR>
$ INSTALL/OVERLAY filespec<CR>

RSTS/E Software Dispatch, January 1991

Seq. No. 3.7.3 M

Previous System logical Assignment Not Replaced
Mandatory Patch
RSTS/E V10.O
Executive
File Processor Patches

Problem
The previous system logical assignment is not replaced when you have two disks with identical
Pack IDs mounted and you attempt to reassign to the second disk a system logical which has
been assigned to the disk that was mounted first.

Solution
The following patching procedure corrects this problem. However, this patch will introduce a
slight incompatibility with current and previous releases of RSTSIE. Currently, when you use
the ASSIGN/SYSTEM command to assign a system logical of9 characters or less to a mounted
disk that does not have a name in the NAME field of a SHOW DISK list, the logical is placed
in the disk logical list. Issuing a subsequent SHOW DISK will display the assigned logical in
the NAME field for that device. If you dismount the disk, the logical will go away. With the
installation of this patch, the logical is always placed in the system logical list. The logical
will not appear in a SHOW DISK list and will not go away when the disk is dismounted.
The logical can only be removed from the list by issuing the DEASSIGN/SYSTEM command.
Note, however, that specifying a logical on the MOUNT command will continue to work as it
always has and is removed when the disk is dismounted.
This problem will be corrected in a future release.

Procedure

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

This patch can be installed using ONLPAT, the online patching program. Note, however,
that this patch will take effect immediately (see step 5).
RUN $ONLPAT
Command File Name? <CR>
File to patch? <CR>
File found in account [0,1]

RSTS/E Software Dispatch, April 1991

RETURN for patch installation
RETURN for installed monitor SIL

Seq. No. 3.7.3 M

The patch is as follows:
Module name? OVR
Base address? SLNO
Offset address? 402
Base
Offset Old
New?
?????? 000402 001425 ? BR+25
?????? 000404 004537 ? AZ
CTRL/Z for new offset
Offset address? AZ
CTRL/Z for new base
Base address? AZ
CTRL/Z for new module
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
New?
?????? 000000 ??????? Q!4
?????? 000002 ?????? ? 1C
up-arrow/C to exitiCTRL/C for INIT

If you have used the $ INSTALL / OVERLAY command or the $ LOAD / OVERLAY=XXX
command, then you must issue the following commands for the patch to take effect:
$ REMOVE/OVERLAY
$ INSTALL/OVERLAY filespec
$ UNLOAD/OVERLAY=xxxx
$ LOAD/OVERLAY=xxxx

RSTS/E Software Dispatch, April 1991

Seq. No. 3.7.4 M

Spawned Job May Fail to Execute -

Mandatory Patch

RSTS / E Vl0.0
Executive
File Processor Patches

Problem
Jobs that are created by the "Create a Job" system call may not execute the requested program
after they have been logged in. While this problem is dependent on the contents of memory
in the job issuing the "Create a Job" sys-call, it is more likely to happen when the spawn is
issued from an I & D space program.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? OVR
Base address? SLI2
Offset address? 174
Base
Offset Old
?????? 000174 116364
?????? 000176 000006
?????? 000200 000006
?????? 000202 116300
?????? 000204 000006
?????? 000206 016364
Offset address? "'z
Base address? "'Z
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? 12700
? 2
? 110064
? 6
? 240
? "'Z
CTRL/Z for new offset
CTRL/Z for new base
CTRL/Z for new module

New?
? Q!10
? AC

RSTS/E Software Dispatch, April 1991

up-arrow/C to exit;CTRL/C for INIT

Seq. No. 3.7.4 M

If you have used the $ INSTALL/OVERLAY command, then you must issue the following commands for the patch to take effect:
$ REMOVE/OVERLAY
$ INSTALL/OVERLAY filespec

RSTS/E Software Dispatch, April 1991

Seq. No. 3.7.5 M

Characters May Not Echo When Setting Host to VMS SystemMandatory Patch
RSTS / E Vl0.0
Executive
File Processor Patches

Problem
After making a network connection to a VMS system, character echoing sometimes stops,
especially when entering the EDT editor. Echoing only occurs after two delimiters are entered.
NOTE

Setting host to a VMS system requires the use of DECNET$:NETUNS.TSK,
an unsupported RSTSIE utility.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure
1.

This is a required patch to the RSTS/E Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? OVR
Base address? UUOO
Offset address? 466
Base
Offset Old
?????? 000466 000207
?????? 000470 104456
Offset address? 654
Base
Offset Old
?????? 000654 000000
?????? 000656 000000
?????? 000660 000000
?????? 000662 000000
?????? 000664 000000
?????? 000666 000000
?????? 000670 000000
?????? 000672 000000

Letters 000, Digit 0
New?
? 472
? "'z

CTRL/Z for new offset

New?
? 122761
? 2
? -34
? BNE+ll
? 62701
? 20
? 24141
? BEQ+5

RSTS/E Software Dispatch, July 1991

Seq. No. 3.7.5 M

?????? 000674 000000
?????? 000676 000000
?????? 000700 000000
?????? 000702 000000
?????? 000704 000000
?????? 000706 000000
?????? 000710 ??????
Offset address? AZ
Base address? UUOOSI
Offset address? 0
Base
Offset Old
?????? 000000 000654
?????? 000002 ??????
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

?
?
?
?
?
?
?

162704
12
12124
12124
12124
207
AZ
CTRL/Z for new offset
CTRL/Z for new base
Letters 000, Digit 0, Letters SI

New?
? 710
? AZ

New?
? Q!20
? AC

CTRL/Z for new offset
CTRL/Z for new base
CTRL/Z for new module

up-arrow/C to exit;CTRL/C for INIT

If you used the $ INSTALL / OVERLAY command or the $ LOAD /OVERLAY=SYSTEM_
CALLS command, then you must issue the following commands for the patch to take
effect:
$ REMOVE/OVERLAY
$ INSTALL/OVERLAY <filespec>
$ UNLOAD/OVERLAY=SYSTEM CALLS
$ LOAD/OVERLAY=SYSTEM CALLS

RSTS/E Software Dispatch, July 1991

Seq. No. 3.7.6 M

System Hangs After Setting Terminal Width - Mandatory Patch
RSTS / E VIO.O
Executive
File Processor Patches

Problem
Under certain circumstances, the system may hang after setting the width of a terminal to a
smaller value than its current width. This may happen if the width is changed on a terminal
that is currently in a KB read state. The system hang could occur after a broadcast to that
terminal or if a command recall key is pressed on that terminal.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? OVR
Base address? TRM2
Offset address? 122
Base
Offset Old
?????? 000122 116100
?????? 000124 000021
?????? 000126 042700

New?
? 5000
? 156100
? 21

RSTS/E Software Dispatch, August 1991

Seq. No. 3.7.6 M

?????? 000130 177400
?????? 000132 160300
?????? 000134 012737
?????? 000136 034240
?????? 000140 177776
?????? 000142 110361
?????? 000144 000021
?????? 000146 116103
?????? 000150 000020
?????? 000152 042703
?????? 000154 177400
?????? 000156 160003
?????? 000160 100001
?????? 000162 005003
?????? 000164 110361
?????? 000166 000020
?????? 000170 012737
Offset address? 756
Base
Offset Old
?????? 000756 000000
?????? 000760 000000
?????? 000762 000000
?????? 000764 000000
?????? 000766 000000
?????? 000770 000000
?????? 000772 000000
?????? 000774 000000
?????? 000776 000000
?????? 001000 ??????
Offset address? AZ
Base address? TRM2SI
Offset address? 0
?????? 000000 000756
?????? 000002 ??????
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

? 160300
? 12737
? PR5
? PS
? 110361
? 21
? 5003
? 156103
? 20
? 160003
? 100001
? 5003
? 110361
? 20
? 4767
? 756-170
CTRL/Z for new offset
? AZ
New?
? 105761
? 106
? 1405
? 160061
? 106
? 100002
? 5061
? 106
? 207
CTRL/Z for new offset
? AZ
CTRL/Z for new base

? 1000
? AZ

New?
? Q!40
? AC

CTRL/Z for new offset
CTRL/Z for new base
CTRL/Z for new module

up-arrow/C to exit;CTRL/C for INIT

If you used the $ INSTALL / OVERLAY command, then you must issue the following
commands for the patch to take effect:
$ REMOVE/OVERLAY
$ INSTALL/OVERLAY <filespec>

Additionally, if you issued the $ LOAD / OVERLAY=TERMINAL command, then you
must issue the following commands for the patch to take effect:
$ UNLOAD/OVERLAY=TERMINAL
$ LOAD/OVERLAY=TERMINAL

RSTS/E Software Dispatch, August 1991

RSTS/E Software Dispatch, December 1991 (Seq. 3.7.7 M)
Job's Private Memory Maximum is Incorrect for Spawned Logged-in
Jobs - Mandatory Patch
RSTS/E V10.0
Monitor
File Processor Corrections

Problem
The job's private memory maximum value for a spawned logged-in
job is incorrect if the calling job does not have TUNE privilege. The value is 2K larger than it should be. This is only a
display problem which is visible when issuing the DCL SHOW USER
command. It will not adversely affect system or job performance.
Solution
The patching procedure detailed below corrects the above problem. This problem will be corrected in some future release.
Procedure
1. This is a required patch to the RSTS/E V10.0 executive. It
must be installed in all target monitor SILs.
2. The patch described in Step 4 below can be installed using
the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

3. This patch can be installed using ONLPAT, the on-line patching program. Note, however, that this patch will take effect
immediately (see step 5 below).
RUN $ONLPAT
Command File Name? <CR>
File to patch? <CR>
File found in account [0,1]

RETURN for patch installation

RETURN for installed monitor SIL

4. The patch is as follows:
Module name? OVR
Base address? SLI1
Offset address? 326
Base
Offset Old
?????? 000326 111460
?????? 000330 000020
?????? 000332 142760
Offset address? 734
Base
Offset Old
?????? 000734 000000
?????? 000736 000000
?????? 000740 000000
?????? 000742 000000
?????? 000744 000000
?????? 000746 ??????
Offset address? AZ
Base address? SLI1SI

New?
? 4767
? 734-332
? AZ
CTRL/Z for new offset
New?
? 111460
? 20
? 12705
? 1
? 207
? AZ
CTRL/Z for new offset
CTRL/Z for new base

Offset address? 0
Base
Offset Old
?????? 000000 000734
?????? 000002 ??????
Offset address? ~Z
Base address? AZ
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? 746
? .... Z

CTRL/Z for new offset
CTRL/Z for new base
CTRL/Z for new module

New?
? QIlOO
? .... C
up-arrow/C to exit;CTRL/C for INIT

One of the following two steps will probably be necessary.
pick the appropriate one:
5. For the patch to take effect, use the following commands to
set the new monitor name and reboot the system:
$ SET SYSTEM/MONITOR=name
$ RUN $SHUTUP

6. If you have used the $ INSTALL/OVERLAY command, then you must
issue the following commands for the patch to take effect:

$ REMOVE/OVERLAY
$ INSTALL/OVERLAY filespec

RSTS/E Software Dispatch, December 1991 (Seq. 3.7.8 M)
POSSIBLE MEMORY CORRUPTION - MANDATORY PATCH
RSTS/E V10.0
Monitor
File Processor Corrections

Problem
When the ·Create a Job- system call is used to log a job into a
Keyboard Monitor that is less than 3 K-words in size, a timing
condition exists that may cause memory to become corrupted.
This can result in program failures such as traps to 4 or memory
management violations.
Solution
The patching procedure detailed below corrects the above problem. This problem will be corrected in some future release.
Procedure
1. This is a required patch to the RSTS/E V10.0 executive. It
must be installed in all target monitor SILs.
2. The patch described in Step 4 below can be installed using
the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

3. This patch can be installed using ONLPAT, the on-line patching program. Note, however, that this patch will take effect
immediately (see step 5 below) .
RUN $ONLPAT
Command File Name? <CR>
File to patch? <CR>
File found in account [0,1]

RETURN for patch installation
RETURN for installed monitor SIL

4. The patch is as follows:
Module name? OVR
Base address? LOG 9
Offset address? 536
Offset Old
Base
?????? 000536 113700
?????? 000540 ??????
?????? 000542 004537
Offset address? 754
Offset Old
Base
?????? 000754 000000
??????
... 11·· 000756 000000
?????? 000760 000000
?????? 000762 000000
?????? 000764 000000
?????? 000766 000000
?????? 000770 ??????
Offset address? "Z
Base address? LOG9SI

New?
? 4767
? 212
? "Z

CTRL/Z for new offset

New?
? 62760
? 2
? 60
? 113700
? FIJOB
? 207
CTRL/Z for new offset
? "Z
CTRL/Z for new base

Offset address? 0
Base
Offset Old
?????? 000000 000754
?????? 000002 ??????
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? 770
? AZ

CTRL/Z for new offset
CTRL/Z for new base
CTRL/Z for new module

New?
? Q!200
? AC
up-arrow/C to exitiCTRL/C for INIT

5. If you have used the $ INSTALL/OVERLAY command, then you must
issue the following commands for the patch to take effect:
$ REMOVE/OVERLAY
$ INSTALL/OVERLAY filespec

Seq. No. 3.7.9 M

File Utility Directive May Truncate File - Mandatory Patch
RSTS/E V10.O
Executive
File Processor Patches

Problem
When the File Utility sys-call (UU.FUT directive) is used to set the date of last access of a
file, the file's size may be truncated.
The PIP program uses the UU.FVT directive to set the date oflast access when the !RETAIN
qualifier is used. This sometimes causes PIP to truncate the new file.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure

This is a required patch to the RSTSJE Version 10.0 executives. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

RETURN for patch installation
RETURN for installed monitor SIL

The patch is as follows:
Module name? OVR
Base address? FUT1
Offset address? 74
Base
Offset Old
?????? 000074 012546
?????? 000076 006202
?????? 000100 131603
Offset address? 146
Base
Offset Old
?????? 000146 010315
?????? 000150 105216
?????? 000152 012403
Offset address? 634

New?
? 167
? 642-100
? "Z
CTRL/Z for new offset
New?
? 4767
? 654-152
CTRL/Z for new offset
? "Z

RSTS/E Software Dispatch, June 1992

Seq. No. 3.7.9 M

Base
Offset Old
?????? 000634 005726
?????? 000636 000207
?????? 000640 000000
?????? 000642 000000
?????? 000644 000000
?????? 000646 000000
?????? 000650 000000
?????? 000652 000000
?????? 000654 000000
?????? 000656 000000
?????? 000660 000000
?????? 000662 000000
?????? 000664 000000
?????? 000666 000000
?????? 000670 000000
?????? 000672 000000
?????? 000674 000000
?????? 00067'6 000000
?????? 000700 000000
?????? 000702 000000
?????? 000704 000000
?????? 000706 000000
?????? 000710 000000
?????? 000712 000000
?????? 000714 000000
?????? 000716 ??????
Offset address? "Z
Base address? FUTISI
Offset address? 0
Base
Offset Old
?????? 000000 000640
?????? 000002 ??????
Offset address? "Z
Base address? "Z
Module name? RSTS
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? <CR> no chanqe; verify on~y
? 5726
? 207
? 10146
? 12546
? 6202
? 167
? 100-654
? 10315
? 105266
? 2
? 16603
? 12
? 1412
? 16365
? 30
? 2
? 116303
? 27
? 1404
? 5065
? 10
? 110365
? 12
? 207
? "Z
C'l'RL/Z for new offset

C'l'RL/Z for new base
New?
? 716
? "Z

C'l'RL/Z for new offset
C'l'RL/Z for new base
C'l'RL/Z for new modul.e

New?
? Q!400
? "C
up-arrow/C to exit;CTRL/C for INIT

If you used the $ INSTALL / OVERLAY command, then you must issue the following

commands for the patch to take effect:
$ REMOVE/OVERLAY
$ INSTALL/OVERLAY filespec

Additionally, if you used the $ LOAD / OVERLAY command. then you must issue the
following commands for the patch to take effect:
$ UNLOAD/OVERLAY=FILE UTILITY
$ LOAD/OVERLAY=FILE_UTILITY

RSTSIE Software Dispatch, June 1992

Seq. No. 3,10.1 M

Some TMSCP Operations May Retry Forever -

Mandatory Patch

RSTS/E VIO.O
Executive
Device Driver Corrections

Problem
During some sequences of operations on TMSCP tape drives (TK50 or TU81), or MSCP disk
drives (DU type disks), it is possible that the driver retries the operation forever. It appears
that the job hangs in an MU, nu, or MTA wait state, and the job cannot be killed.

Solution
The follo¥t'ing patching procedure corrects this problem. It will be correct~d in a future release.

Procedure
1.

This is a required patch to the RSTSIE Version 10.0 executive. It must be installed in
all target monitor save image libraries (SILs).

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? <CR>

RETURN for installed monitor SIL

This patch can be installed using O~LPAT, the online patching program. Note, however,
that if the patch is applied on line to the installed monitor SIL, it will not take effect
until the system is rebooted.
RUN $ONLPAT
Command File Name? <CR>
File to patch? <CR>
File found in account [O,lJ

RETURN for patch installation
RETUR~ for installed monitor SIL

The patch is as follows:
Module name? MCP
Base address? CPH@OVR
Offset address? 3632
Offset Old
Base
?????? 003632 005065
?????? 003634 000000
??????
003636 005065
?????? 003640 000020
?????? 003642 005065
?????? 003644 000006
?????? 003646 012765
?????? 003650 000003
?????? 003652 000012
?????? 003654 012765
Offset address? 3732

New?
? 12765
? 3
? 12
? 240
? <CR> no change; verify only
? <CR> no change; verify only
? 5015
? 5065
? 20
CTRL/Z for new offset
? "z

RSTS/E Software Dispatch, November 1991

Seq. No. 3.10.1 M

Offset Old
New?
Base
?????? 003732 004767 ? <CR> no change; verify only
?????? 003734 177674 ? 177704
CTRL/Z for new offset
?????? 003736 013746 ? ~Z
Offset address? ~z
CTRL/Z for new base
Base address? UQPORT@OVR
Offset address? 776
Base
Offset Old
New?
?????? 000776 132764 ? 4737
?????? 001000 000100 ? MCPPAT@OVR
?????? 001002 ?????? ? 240
?????? 001004 001020 ? 1005
CTRL/z for new offset
?????? 001006 062702
Offset address? ~z
CTRL/Z for new base
Base address? MCPPAT@OVR
Offset address? 0
New?
Base
Offset Old
120000 000000 000000 ? 132764
120000 000002 000000 ? 100
120000 000004 000000 ? CMT@OVR+17
120000 000006 000000 ? 1405
120000 000010 000000 ? 12700
120000 000012 000000 ? 3
120000 000014 000000 ? 132764
120000 000016 000000 ? 100
120000 000020 000000 ? CMT@OVR+17
120000 000022 000000 ? 207
CTRL/Z for new offset
120000 000024 ?????? ? ~z
Offset address? ~z
CTRL/Z for new base
Base address? ~Z
CTRL/Z for new module
Module name? RSTS
Base address? $$0310
Offset address? 0
Base
Offset Old
New?
?????? 000000 ?????? ? Q!l
?????? 000002 ?????? ? ~C
up-arrow/C to exit;CTRL/C for INIT

(

RSTS/E Software Dispatch, November 1991

(

Seq. No. 3.12.1 R

DB/DR Driver May log Errors for Wrong Unit Restriction

DRSEEK/DBSEEK

RSTS/E V10.O
Executive
Device Driver Restrictions
The DB and DR overlapped seek disk drivers (DBSEEK and DRSEEK) may count or log
errors for the wrong disk unit if there is heavy DBIDR disk activity and an attempt is made
to mount a unit that is spun down or is off line.

RSTS/E V10.0 Maintenance Notebook

Seq. No.3.12.2 R

Swapping MSCP/TMSCP Unit Numbers May Cause Crash
MSCP/TMSCP Device Driver Restriction
RSTS / E VIO.O
Executive
Device Driver Restrictions

On systems having multiple UDA50-A MSCP controllers, a system crash may result if disk
unit numbers are swapped between two drives on different UDA50-A controllers during
timesharing.
The preferred workaround is to only swap drive numbers between controllers when timesharing is not running. The best method is to shut the system down and swap the unit
numbers when the Start timesharing prompt appears. Mter swapping the unit numbers,
reboot the system disk and restart timesharing.

RSTS/E Vl0.0 Maintenance Notebook

Seq. No. 4.1.1 F

Special PRINT-USING Characters -

BASIC-PLUS Feature Patch

RSTS/E V10.O
BASIC-PLUS
BASIC-PLUS Patches
The PRINT-USING option of BASIC-PLUS provides for floating dollar sign, comma insertion
every three digits to the left of the decimal point, and printing of the decimal point. The
$ sign is used for the currency symbol in the United States and Canada, but various other
symbols are used for other monetary systems. In the United Kingdom it would be useful
to float the Pound Sterling symbol (or whatever ASCII character is used to represent that
symbol) instead of the $ sign. In France, a floating Franc symbol (or F) would be generally
more useful than the floating $ sign. The role of the comma and period are also reversed in
France (for example, 9,999,999.02 should be printed as 9.999.999,02).
To accommodate these differences in monetary systems, PRINT-USING is coded to allow
substitution of any character for the floating currency symbol, the decimal point character,
and the every-three-digits character. These three characters are defined by three words in
the BASIC-PLUS Run-Time system. System defaults and several suggestions are shown in
the following table:
Location

Usage

Default

England

France

.. PUCH+O

Floating currency symbol

$ (044)

& (046)

F (106)

.. PUCH+2

Decimal point character

. (056)

, (054)

.. PUCH+4

Every three digits character

, (054)

. (056)

Substitution of different characters, such as those listed under England and France, is done
with a simple patch. Any change will affect both the PRINT-USING format string and the
output produced. For example, if the suggestions under France were installed, the following
PRINT-USING statement would result in the output shown:
PRINT USING "FF#.######,##", 3673298.02, 4545.20
F3.673.298,02
F4.545,20

Since any change in this area does render the PRINT-USING documentation slightly incorrect, an appropriate note should be published for users of the system.

Seq. No. 4.1.1 F 1

Seq. No. 4.1.1 F

Procedure
1.

This is a feature patch to the BASIC-PLUS Run-Time system. It may be installed in
any BASIC-PLUS Run-Time system configured with Print-Using.

Determine the three special characters you want to use for the floating currency symbol,
the decimal point character, and the every-three-digits character. The chosen characters
can be entered as either:

where x is the chosen printable character

where n is the octal value of the chosen character

where n is the decimal value of the chosen character

The patch described in Step 5 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]BASIC.RTS
File found in account [0,1]

(RETURN for manual installation)
(BASIC-PLUS run-time system name)

This feature patch is contained in the file PA0401.001 as part of the UPDATE package.
To transfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure. 1
5.

The patch is as follows:
Base address? .. PUCH
Offset address? 0
Base
Offset Old
?????? 000000 000044
?????? 000002 000056
?????? 000004 000054
?????? 000006 ??????

New?
? 'f
,
?
,
?
? AC

(currency sign
(decimal point
("every three"
(up-arrow/C to

from Step 2)
from Step 2)
from step 2)
exit;CTRL/C for INIT)

If the above patch was installed using ONLPAT, it will take effect the next time the
Run-Time system is reloaded. If the Run-Time system has been INSTALLED, execute
the following commands:
$ UNLOAD/RUNTIME_SYSTEM BASIC

(BASIC-PLUS run-time system name) 2

The patch file for this patch requires manual editing to include installation specific parameters before it can be successfully
installed.

'The UNLOAD command will not remove the run-time system, but simply instructs the monitor to reload it the next time
a job requests it.

Seq. No. 4.1.1 F

Seq. No. 4.1.2 F

Default Scale Factor -

BASIC-PLUS Feature Patch

RSTS/E Vl0.0
BASIC-PLUS
BASIC-PLUS Patches
The BASIC-PLUS default SCALE factor may be modified by utilizing the procedure in this
article. A complete description of SCALE factors is included in the BASIC-PLUS Language
Manual.
Procedure
1.

This is a feature patch to the BASIC-PLUS Run-Time system. It may be installed in
any BASIC-PLUS Run-Time system configured with the 4-word, scaled math package.

Determine the new BASIC-PLUS default SCALE factor. This default SCALE factor
must be between 0 and 6 inclusive.

The patch described in Step 5 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT, the on-line patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]BASIC.RTS
File found in account [0,1]

(RETURN for manual installation)
(BASIC-PLUS run-time system name)

This feature patch is contained in the file PA0401.002 as part of the UPDATE package.
To transfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure. 1
5.

The patch is as follows:
Base address? .. SCA.
Offset address? 0
Base
Offset Old
?????? 000000 000000
?????? 000002 ??????

New?
? n
? AC

(from Step 2)
(up-arrow/C to exit; CTRL/C for INIT)

If the above patch was installed using ONLPAT, it will take effect the next time the

run-time system is reloaded. If the run-time system has been INSTALLED, execute the
following commands:
$ UNLOAD/RUNTIME_SYSTEM BASIC

(BASIC-PLUS run-time system name) 2

The patch file for this patch requires manual editing to include installation specific parameters before it can be successfully
installed.
2 The UNLOAD command will not remove the run-time system, but simply instructs the monitor to reload it the next time
a job requests it.
1

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 4.1.3 F

Omitting Scale Factor Warning Message Patch

BASICGPlUS Feature

RSTS/E Vl0.0
BASIC-PLUS
BASIC-PLUS Patches

Normally, if a BASIC-PLUS program is compiled with one SCALE factor and then is run
under a different job SCALE factor, the %SCALE Factor Interlock warning message is
printed and execution proceeds using the program's SCALE factor. It may be desirable to
omit the printing of this message.
Procedure
1.

This is a feature patch to the BASIC-PLUS run-time system. It may be installed in any
BASIC-PLUS run-time system configured with the 4-word, scaled math package.

The patch described in Step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT, the on-line patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]BASIC.RTS
File found in account [0,1]

(RETURN for manual installation)
(BASIC-PLUS run-time system name)

This feature patch is contained in the file PA0401.003 as part of the UPDATE package.
To transfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure.
4.

The patch is as follows:
Base address? .. SCE.
Offset address? 0
Base
Offset Old
?????? 000000 104577
?????? 000002 000207

New?
? 240
? AC

(for no warning message)
(up-arrow/C to exit; CTRL/C for INIT)

If the above patch was installed using ONLPAT, it will take effect the next time the
run-time system is reloaded. If the run-time system has been INSTALLED, execute the

following commands:
$ UNLOAD/RUNTIME_SYSTEM BASIC

(BASIC-PLUS run-time system name) 1

The UNLOAD command will not remove the ron-time system, but simply instructs the monitor to reload it the next time
a job requests it.

RSTS/E V10.0 Maintenance Notebook

Seq. NOI. 4.1.4 F

Default to NOEXTEND Mode -

BASIC-PLUS Feature Patch

RSTS/E VIO.O
BASIC-PLUS
BASIC-PLUS Patches
Normally, BASIC-PLUS defaults to EXTEND mode. To change this default to NO EXTEND
mode, apply the patch in this article.
Procedure
1.

This is a feature patch to the BASIC-PLUS run-time system. It may be installed in any
BASIC-PLUS run-time system.

The patch described in Step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT, the on-line patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]BASIC.RTS
File found in account [0,1]

(RETURN for manual installation)
(BASIC-PLUS run-time system name)

This feature patch is contained in the file PA0401.004 as part of the UPDATE package.
To transfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure.
4.

The patch is as follows:
Base address? .. XTN.
Offset address? 0
Base
Offset Old
?????? 000000 020000
?????? 000002 ??????

New?
? 0
? AC

If the above patch was installed using ONLPAT, it will take effect the next time the
run-time system is reloaded. If the run-time system has been INSTALLED, execute the
following commands:
$ UNLOAD/RUNTIME_SYSTEM BASIC

(up-arrow/C to exit; CTRL/C for INIT)

(BASIC-PLUS run-time system name) 1

The UNLOAD command will not remove the ron-time system, but simply instructs the monitor to reload it the next time
a job requests it.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 4.1.5 F

Immediate Mode from .BAS File -

BASIC-PLUS Feature Patch

RSTSIE V10.O
BASIC-PLUS
BASIC-PLUS Patches
Normally, BASIC-PLUS does not allow immediate-mode commands to appear in the file
accessed by the OLD command. This may be desirable in environments where this feature
was used in previous versions of BASIC-PLUS. To allow BASIC-PLUS to accept immediate
mode commands in files, apply the patch in this article.
Procedure
1.

This is a feature patch to the BASIC-PLUS run-time system. It may be installed in any
BASIC-PLUS run-time system.
The patch described in Step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT, the on-line patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]BASIC.RTS
File found in account [0,1]

(RETURN for manual installation)
(BASIC-PLUS run-time system name)

This feature patch is contained in the file PA0401.005 as part of the UPDATE package.
To transfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure.
4.

The patch is as follows:
Base address? .• IBAS
Offset address? 0
Base
Offset Old
?????? 000000 001401
?????? 000002 104767

New?
? 401
? AC

(up-arrow/C to exit; CTRL/C for INIT)

If the above patch was installed using ONLPAT, it will take effect the next time the
run-time system is reloaded. If the run-time system has been INSTALLED, execute the

following commands:
$ UNLOAD/RUNTIME_SYSTEM BASIC

(BASIC-PLUS run-time system name) 1

1 The UNLOAD command will not remove the nm-time system, but simply instructs the monitor to reload it the next time

a job requests it.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 4.1.6 F

Disabling the CCl SYS Call -

BASIC-PLUS Feature Patch

RSTS/E V10.O
BASIC-PLUS
BASIC-PLUS Patches
Normally, BASIC-PLUS allows any user to execute any valid CCL command on the system
with SYS call 14. However, some installations may choose to disable this feature to discourage users from writing programs that will simulate the features of a standard run-time
system. The patch in this article prevents BASIC-PLUS from executing SYS call 14. 1 It
will not prevent the use of SYS call 14 from other languages such as BASIC-PLUS-2 or
MACRO-H.
Procedure
1.

This is a feature patch to the BASIC-PLUS run-time system. It may be installed in any
BASIC-PLUS run-time system.

The patch described in Step 4 can be installed using the PATCH option of init.sys:
Option: PATCH
File to patch? BASIC.RTS

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT, the on-line patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]BASIC.RTS
File found in account [0,1]

(RETURN for manual installation)
(BASIC-PLUS run-time system name)

This feature patch is contained in the file PA0401.006 as part of the UPDATE package.
To transfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure.
4.

The patch is as follows:
Base address? .. CCL.
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? UUOBAD
? AC
(up-arrow/C to exit; CTRL/C for INIT)

If the above patch was installed using ONLPAT, it will take effect the next time the
run-time system is reloaded. If the run-time system has been INSTALLED, execute the

following commands:
$ UNLOAD/RUNTIME_SYSTEM BASIC

(BASIC-PLUS run-time system name) 2

This patch will disable the execution of the system wide LOGIN. COM file when logging in, if the LOGIN program has
been compiled with BASIC-PLUS (.BAC file type).

The UNLOAD command will not remove the run-time system, but simply instructs the monitor to reload it the next time
a job requests it.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 4.1.7 M

DATEO/o Is Now a Reserved Keyword - Mandatory Patch
RSTS/E V10.O
BASIC-PLUS
BASIC-PLUS Patches

Problem
RSTSIE Version 10.0 BASIC-PLUS now reserves the keyword DATE%. Attempting to OLD
a BASIC-PLUS program that contains the variable DATE% or the integer array DATE%()
under RSTSIE Version 10.0 BASIC-PLUS will result in the error "?Arguments don't match".
Already compiled BASIC-PLUS programs that use the keyword DATE% will continue to function as before.

Solution
Because this is an incompatibility with previous versions of BASIC-PLUS, applying the following patch will change the reserved keyword DATE% to D?TE%. Once this patch is applied,
programs containing the variable DATE% or the integer array DATE%() can be OLDed without an error.

Procedure

This is a required patch to the BASIC-PLUS run-time system. It must be installed in
all BASIC-PLUS run-time systems.

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

This patch can be installed using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l)BASIC.RTS
File found in account [0,1)

(BASIC-PLUS run-time system name)

(RETURN for manual patch installation)
(BASIC-PLUS run-time system name)

The patch is as follows:
Base address? LA
Offset address? 634
Base
Offset Old
?????? 000634 005101
?????? 000636 ??????

New?
? 5077
? AC

RSTS/E Software Dispatch, January 1991

(up-arrow/C to exit;CTRL/C for INIT)

Seq. No. 4.1~7 M

(BASIC-PLUS run-time system name)

NOTE
The UNLOAD command will not remove the run-time system, but it will
instruct the monitor to reload it the next time a job requests it.

RSTS/E Software Dispatch, January 1991

Seq. No. 4.1.8 F

RADO/o Is Now a Reserved Keyword - BASIC-PLUS Feature Patch
RSTS IE VIO.O
BASIC-PLUS
BASIC-PLUS Patches

Problem
RSTS/E Version 10.0 BASIC-PLUS now contains a new function RAD%. (See article 4.2.1
N for a description of the new function.) An attempt to OLD a BASIC-PLUS program that
contains the variable RAD% or the integer array RAD%() under RSTS/E Version 10.0 BASICPLUS will result in the error "?Arguments don't match". Already compiled BASIC-PLUS
programs that use the keyword RAD% will continue to function as before.

Solution
Because this is an incompatibility with previous versions of BASIC-PLUS, applying the following patch will change the reserved keyword RAD% to R?D%. Once this patch is applied,
programs containing the variable RAD% or the integer array RAD%() can be OLDed without
an error.
If you do not have programs that use the variable RAD% or the integer array RAD%(), then
do not apply this feature patch.

Procedure
1.

This is a feature patch to the BASIC-PLUS run-time system. It can be installed in any
BASIC-PLUS run-time system.

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

(BASIC-PLUS run-time system name)

This patch can be installed using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]BASIC.RTS
File found in account [0,1]

(RETURN for manual patch installation)
(BASIC-PLUS run-time system name)

The patch is as follows:
Base address? LA
Offset address? 1742
Base
Offset Old
?????? 001742 040504
?????? 001744 ??????

New?
? 37504
? AC
(up-arrow/C to exit;CTRL/c for INIT)

RSTS/E Software Dispatch, February 1991

Seq. No. 4.1.8 F

If the patch was installed using ONLPAT, it will take effect the next time the run-time
system is reloaded. If the run-time system has been INSTALLED, execute the following
command:
$ UNLOAD/RUNTIME BASIC<CR>

(BASIC-PLUS run-time system name)

NOTE
The UNLOAD command will not remove the run-time system but will
instruct the monitor to reload it the next time a job requests it.

RSTS/E Software Dispatch, February 1991

Seq. No. 4.2.1 N

New BASIC-PLUS Function - RADO/o
RSTS/E V10.O
BASIC-PLUS
BASIC-PLUS Notes

RSTS/E Version 10.0 BASIC-PLUS contains a new function, RAD%. This function provides
the complement of the RAD$ function, that is, it will convert a 3-character string of RAD-50
characters into its integer equivalence.
Because the BASIC-PLUS Language Manual was not updated for RSTS/E Version 10.0, this
function is described in this article. Also, the online help for BASIC-PLUS functions does not
describe this function.
A related article, 4.1.8 F, describes how to change the reserved keyword RAD% to R?D% to
avoid compatibility problems with existing BASIC-PLUS programs, if necessary.
Format:
int-exp

RAD%(str-exp)

Syntax Rules:
1.

RAD% only converts the first three characters of the specified string. The remainder of
the string is ignored.

The first three characters of the string must be RAD-50 characters. If any of the three
characters are not RAD-50 characters, then the error "%Illegal argument" will result.
Note that lowercase letters will also generate the "%Illegal argument" error, as they
are not considered to be RAD-50 characters. Appendix D of the RSTS / E Programming
Manual describes the RAD-50 character set.

If the string is less than three characters in length, then the function will convert it as
a 3-character string with trailing spaces.
Example:
PRINT RAD% ("ABC")
1683
Ready

RSTS/E Software Dispatch, February 1991

Seq. No. 4.11.1 N

The BASIC-PLUS Debug Facility
RSTS/E V10.O
BASIC-PLUS
Optional BASIC-PLUS Features

A feature of BASIC-PLUS, the Debug facility, is now available as a supported feature in
RSTS/E VIO.O.
The Debug commands extend the present BASIC-PLUS immediate-mode debugging commands by allowing you to trace the flow of your program and to set breakpoints. These
commands provide a subset of the functions provided by the BASIC-PLUS-2 debugging facility, and are only available as immediate-mode commands. They cannot be used within
BASIC-PLUS programs. The commands are used in one of two ways:
e

By issuing them between the OLD and RUN of a program and, thereafter, whenever a
breakpoint is hit

•

By including STOP statements within the program, and then issuing the Debug commands when the first STOP statement is encountered and, thereafter, whenever another
STOP statement or breakpoint is hit

Any Debug commands are disabled when:
tl

A RUN program-name command is successfully executed

A NEW, OLD, or EXIT command is executed

Any valid CCL command is executed

TRACE/UNTRACE

The TRACE command causes BASIC-PLUS to print the message at line nnn (where nnn
represents a line number) each time that a line number is encountered or the current line
number changes.
The UNTRACE command disables any previous invocation of the TRACE command.
BREAK/UNBREAK

The BREAK command allows you to specify that execution should stop any time that a
specified line number is encountered. Up to 10 such breakpoints can be set. The BREAK
command is of the form:
BREAK [ NI, N2, N3 ... , NIO J

where Nn represents a line number between 1 and 32767.
When a breakpoint is encountered, BASIC-PLUS prints the message Break at line nnn and
returns to Ready as though a STOP statement had been executed. At this point you can
examine or change the values of variables, execute the DUMP command, or execute any
other legal command. Type CONT (continue) to resume execution.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 4.11.1 N

If the BREAK command is issued without a line number argument, BASIC-PLUS will

BREAK each time that a new line is encountered. The UNBREAK command is used to
disable breakpoints, and is of the form:
UNBREAK [ Nl, N2, N3,

... , N10 ]

If no line numbers are specified, all breakpoints are disabled.

Understanding Line Numbers in the Debug Facility
This section discusses the actual implementation of the Debug facility in the BASIC-PLUS
run-time system, and should help to explain certain anomalies that you may encounter.

The Debug code is entered whenever an internal construct called a statement header is
encountered. Statement headers are generated for the following BASIC-PLUS elements:

•
•
•
•
•
•
•

Line numbers
DIMENSION statements
DATA statements
FOR statements
NEXT statements
DEF statements
FNEND statements

When a statement header is encountered, BASIC-PLUS first checks to see if the BREAK or
TRACE feature has been requested. If not, program execution continues.
If BREAK or TRACE has been requested, BASIC-PLUS now compares the current line number with the previously encountered line number. If they are the same, program execution

continues.
If a different line number has been encountered, BASIC-PLUS then checks to see if the
statement header represents a function definition (DEF) statement. If so, program execution

continues.
Because of the internal structure of BASIC-PLUS, it is not possible to BREAK at a function
definition. As you can see from the algorithm used, any attempt to BREAK at a function
definition is rejected while the program is being executed, rather than when the BREAK
command is specified.
If the BREAK feature has been requested, BASIC-PLUS compares the current line number
with the list of breakpoints that have been requested. If the current line number is included
in the breakpoint list, BASIC-PLUS prints Break at line nnn, and returns to keyboard

monitor (Ready) state.
If the TRACE feature has been requested, BASIC-PLUS prints at line nnn and proceeds

with execution of the program.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 4.11.1 N

Enabling the Debug Facility
The Debug facility requires approximately 160 (decimal) additional words in the BASICPLUS run-time system. In most cases, this means that one or more of the other optional
features (String Arithmetic, Print Using, etc.) must be omitted to prevent the BASIC-PLUS
run-time system from exceeding 16K words in size.
To enable Debug, answer Y to the Debug? question during installation or update of BASIC-

PLUS.
Note that enabling Debug also enables the DUMP facility, described in Article 4.11.2 N.

RSTS/E V10.0 Maintenance Notebook 3

Seq. No. 4.11.2 N

The BASIC-PLUS Dump Facility
RSTS/E Vl0.0
BASIC-PLUS
Optional BASIC-PLUS Features
A feature of BASIC-PLUS, the Dump facility, is now available as a supported feature in
RSTSIE VIO.O.
The DUMP command provides an extension to the present BASIC-PLUS immediate mode
debugging commands by allowing you to take a snap-shot dump of your current job. Mter
dumping your program, you can use the BPDA (BASIC-PLUS Dump Analyzer) program to
display the contents of all variables used by the program. In addition, you can continue
executing your program after issuing the DUMP command; this allows you to inspect the
state of the program at several stages of execution.
The DUMP command is only available as an immediate-mode command (that is, it cannot
be used in a BASIC-PLUS program), and has the syntax:
DUMP file-specification

If no device name is specified, the public disk structure (SY:) is used. If no filename is
specified, the current program name is used. If no file type is specified, .PMD is used.

The BASIC-PLUS Dump Analysis Program
After the DUMP command has been issued, you can use the BPDA program to print the
contents of each variable that is used in the program, as well as the contents of the buffer
of any open files.

The BPDA program asks for an input file name. The default file type is .PMD. There is no
default for the file name. Wildcards are illegal.
When BPDA asks for the output file name, responding with <CR> will direct the output to
your terminal. If no filename is specified, the input filename is used with the default file
type .PDA.
You may also respond to the Input file? query with a command of the form:
outfile = infile

Security Notes
Access to the Dump facility should be carefully controlled, as it may be used by unscrupulous
users to obtain confidential information, such as student grades or payroll information. The
following two mechanisms help protect against this:

•

Non-privileged users are normally prevented from using the DUMP command on programs that are running from compiled files. This capability may be removed if desired
(see article Seq 4.11.3 F).

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 4.11.2 N

•

Whether or not non-privileged users are allowed to use the DUMP command on programs that are executed from compiled files, they still may not use the DUMP command
on a program that uses temporary privileges, since the BASIC-PLUS run-time system
clears the program from memory before a non-privileged user returns to keyboard monitor state.

Some installations may find it desirable to generate two versions of the BASIC-PLUS runtime system, one which includes the Debug and Dump facilities, which would be used for
development, and another which does not include either facility, which would be used for
production. This would prevent the potential problems described above, while providing the
Dump facility for development work.
Enabling the Dump Facility
The Dump facility is enabled automatically when the Debug facility is selected during an
installation or update of BASIC-PLUS. See Article 4.11.1 N for a description of the Debug
facility.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 4.11.3 F

Enabling Dump from Compiled Files for Non-Privileged Users BASIC-PLUS Feature Patch
RSTS/E V10.O
BASIC-PLUS
Optional BASIC-PLUS Features
Normally, if the Dump facility is enabled (see article Seq 4.11.2 N), BASIC-PLUS will not
allow some users to dump programs that are executing from compiled files, even though
they may dump programs that are executing from source files. This protection prevents
users from dumping programs which may contain confidential information in their variable
strings or file buffers. In order to use the DUMP command, the user must have WACNT,
WWRITE, SYSIO and RDMEM privileges.
Some installations, however, may want to allow all users to dump all BASIC-PLUS programs
to which they have RUN access, regardless of whether the program is compiled.
The following patching procedure will cause BASIC-PLUS to allow all users to dump programs that they are executing. (Note that a program whose protection code includes the
128. bit for temporary privileges is always cleared from a non-privileged user's job space
before returning the keyboard monitor (Ready) state. Hence, a nonprivileged user can never
dump such a program.)
Procedure
1.

This is a feature patch to the BASIC-PLUS run-time system. It may be installed in any
BASIC-PLUS run-time system.

The patch described in Step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT, the on-line patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]BASIC.RTS
File found in account [0,1]

(RETURN for manual installation)
(BASIC-PLUS run-time system name)

This feature patch is contained in the file PA0411.003 as part of the UPDATE package.
To transfer this file to the UPDATE$ account, select the package name UPDATE during
the system installation or update procedure.
4.

The patch is as follows:
Base address? .. NPD.
Offset address? 0
Base
Offset Old
?????? 000000 004767
?????? 000002 ??????
?????? 000004 005046

New?
? NOP
? NOP
? AC

(up-arrow/C to exit; CTRL/C for INIT)

RSTS/E V10.0 Maintenance Notebook

Seq. No. 4.11.3 F

(BASIC-PLUS run-time system name) 1

The UNLOAD command will not remove the run-time system, but simply instructs the monitor to reload it the next time
a job requests it.

2 RSTS/E V10.0 Maintenance Notebook

Seq. No. 6.2.1 R

RESTORE/VERIFY/NOREPLACE Can Enter Infinite Sleep State
RSTS/E VlO.O
System File Restrictions
BACKUP.TSK

Problem
If /NOREPLACE and NERIFY are both specified with either RESTORE or BACKUP/COPY,
and there are many files that are "not replaced," then BACKUP can enter an infinite sleep
state.
The reason this happens is that whenever a file is not replaced, it is added to a list kept in
dynamic memory space, so that the verify operation will know not to do the verify on those
files. With a large number of files not replaced, BACKUP eventually runs out of dynamic
memory space and sleeps.
The workaround to this problem is to specify either /NOREPLACE or NERIFY, but not both
in anyone operation if there are going to be a large number of files "not replaced."
This is a BACKUP restriction for Version 10.0.

RSTS/E Software Dispatch, March 1991

Seq. No. 6.2.2 R

BACKUP/IMAGE Fails to Maintain Pack Attributes
RSTS / E V10.O
System Files
System File Restrictions

Problem
There is a problem in BACKUPIIMAGE where, if the /OUT_L-\BEL and /INITIALIZE qualifiers are used, the program uses the default pack attributes for a BACKUP set rather than
the input disk pack attributes. This problem is a restriction for RSTSIE Version 10.0.
You can avoid this problem by not specifying the lOUT_LABEL qualifier on the BACKUPIIMAGE
command. However, this will result in the output disk having the same pack label as the
input disk. If this is not desirable, you can preinitialize the disk by using the DSKINT Utility
or the Digital Command Language (DCL) Initialize Command (Th"'1TIALIZE), assigning the
pack attributes and label you want instead of using the /Oti"CL\BEL qualifier.
This restriction may be lifted in some future release of RSTSIE.

RSTS/E Software Dispatch, October 1991

Seq. No. 6.3.1 M

BACKUP Can Fail to Back Up Some File Data - Mandatory Patch
RSTS / E VIO.O
System Files
BACKUP.TSK

Problem
Under certain conditions involving system loading, BACKUP can fail to back up some file
data. Failure indications are:
•

"?Some file data may be missing... "

•

Errors during a BACKUPIDIRECTORY or RESTORE

•

Verification errors during a verify pass

Solution
The following patching procedure corrects this problem. This problem will be corrected in a
future release.

Procedure

This is a required patch to [O,l]BACKUP.TSK.

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? BACKUP.TSK/N

This patch can be installed using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
(RETURN for patch installation)
File to patch? [O,l]BACKUP.TSK/N
File found in account [0,1]

The patch is as follows:
Base address? 74:10512
Offset address? 1340
Base
Offset Old
010512 001340 012767
010512 001342 001000
010512 001344 003700
010512 001346 012746
Offset address? 2506
Base
Offset Old
010512 002506 004767
010512 002510 001660
010512 002512 012701
Offset address? "Z
Base address? 3:0
Offset address? 41156
Base
Offset Old
000000 041156 000000

New?
? 137
? 41156
? 240
(CTRL/Z for new offset)
? "Z
New?
? 13700
? 41204
(CTRL/Z for new offset)
? "z
(CTRL/Z for new base)
New?
? 12701

RSTS/E Software Dispatch, February 1991

Seq. No. 6.3.1 M

000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000

041160
041162
041164
041166
041170
041172
041174
041176
041200
041202
041204
041206

000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000

?
?
?
?
?
?
?
?
?
?
?
?

34
4737
105060
12737
1000
105734
10037
41204
137
102034
-1
"C
(up-arrow/C to exit;CTRL/c for INIT)

RSTS/E Software Dispatch, February 1991

Seq. No. 6.3.2 M

BACKUP/INITIALIZE Can Exit with Error -

Mandatory Patch

RSTS/E Vl0.0
System File Corrections
BACKUP.TSK

Problem
If the /INITIALIZE qualifier is specified with any of the BACKUP commands (BACKUP,
RESTORE, BACKUP/COPY, BACKUP/IMAGE), and if the disk to be initialized has a large
number of bad blocks, then BACKUP can exit with the following error after you respond with
a "Y' to the prompt "Proceed (Y or N)?":
?Unexpected error 31 in BCKSUB at 62404

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure

This is a required patch to [O,l]BACKUP.TSK.

The patch described in step 4 can be installed using the PATCH option of INIT.syS:
Option: PATCH
File to patch? BACKUP.TSK/N

This patch can be installed using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
(RETURN for patch installation)
File to patch? [O,l]BACKUP.TSK/N
File found in account [0,1]

The patch is as follows:
Base address? 45:5060
Offset address? 14014
Base
Offset Old
005060 014014 063767
005060 014016 000444
005060 014020 005200
005060 014022 000732
Offset address? "Z
Base address? 3:0
Offset address? 41206
Base
Offset Old
000000 041206 000000
000000 041210 000000
000000 041212 000000
000000 041214 000000
000000 041216 000000
000000 041220 000000
000000 041222 000000

New?
? 4737
? 41206
? 240
(CTRL/Z for new offset)
? "Z
(CTRL/Z for new base)

New?
? 63737
? 444
? 67636
? 23727
? 67636
? 1000
? 2402

RSTS/E Software Dispatch, March 1991

Seq. No. 6.3.2 M

000000
000000
000000
000000

041224
041226
041230
041232

000000
000000
000000

??????

? 4737
? 63034
? 207
? AC
(up-arrow/C to exit;CTRL/C for INIT)

RSTS/E Software Dispatch, March 1991

Seq. No. 6.3.3 M

BACKUP/VERIFY=ONlY Rewinds Before Execution - Mandatory
Patch
RSTS/E Vl0.0
System File Corrections
BACKUP. TSK

Problem
BACKUPNERIFY=ONLY always rewinds the tape before executing the verify. That means
that the NERIFY=ONLY qualifier cannot be used to verify multiple backup sets on a tape
without rewinding the tape between each verify operation.

Solution
The following patching procedure corrects this problem. It will be corrected in a future release.

Procedure

This is a required patch to [O,l]BACKUP.TSK.

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? [O,l]BACKUP.TSK/N

This patch can be installed using ONLPAT, the online patching program.
$ RUN $ONLPAT
Command file name? <CR>
RETURN for patch installation
File to patch? [O,l]BACKUP.TSK/N
File found in account [0,1]

The patch is as follows:
Base address? 3:0
Offset address? 41232
Base
Offset Old
000000 041232 000000
000000 041234 000000
000000 041236 000000
000000 041240 000000
000000 041242 000000
000000 041244 000000
000000 041246 000000
000000 041250 000000
000000 041252 ??????
Offset address? AZ
Base address? 122:0
Offset address? 62
Base
Offset Old
000000 000062 052767
000000 000064 000004
000000 000066 104746
000000 000070 ??????

New?
? 32737
? 4000
? 3734
? 1003
? 52737
? 4
? 3732
? 207
? AZ
CTRL/Z for new offset

CTRL/Z for new base
New?
? 4737
? 41232
? 240
up-arrow/c to exit; CTRL/C for INIT
? AC

RSTS/E Software Dispatch, June 1991

Seq. No. 6.3.4 M

BACKUP/BUFFER_SIZE=OPTIMUM May Not Select the Optimum
Buffer Size - Mandatory Patch
RSTS / E Vl0.0
System File Corrections
BACKUP.TSK

Problem
When running the backup utility (BACKUP), if you specify IBUFFER_SIZE=OPTIMUM,
BACKUP will set a buffer size that ensures the most efficient use of memory to produce
the fastest BACKUP operation.
If you do not specify a buffer size but you do specify an MU: or MS: (streaming) tape for input
or output, then BACKUP will automatically use the IBUFFER_SIZE=OPTIMUM qualifier to
ensure that the tape device can transfer data fast enough to maintain streaming.
The optimum buffer size prior to Version 10.0 was 55K words, which was appropriate for a
default block size of 2048 and a maximum block size of 7680.
For Version 10.0 and later, the maximum block size is 28672, and the default block size is
28672 for disk and 16384 for tape. This means that an optimum buffer size of 55K words is
no longer adequate.

Solution
The following patching procedure increases the optimum buffer size to 85K words. This
problem will be corrected in a future release.

Procedure

This is a required patch to [O,l]BACKUP.TSK.

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? [O,l]BACKUP.TSK/N

This patch can be installed using ONLPAT, the online patching program.
$ RUN $ONLPAT
Command file name? <CR>
RETURN for patch installation
File to patch? [O,l]BACKUP.TSK/N
File found in account [0,1]

The patch is as follows:
Base address? 145:17326
Offset address? 3452
Base
Offset Old
New?
017326 003452 000067 ? 125
017326 003454 125243 ? AC

RSTS/E Software Dispatch, July 1991

up-arrow/C to exit; CTRL/C for INIT

Seq. No. 6.3.5 M

BACKUP May Sleep Indefinitely -

Mandatory Patch

RSTS/E Vl0.0
System Files
System File Corrections

Problem
A race condition exists in BACKUP where it sometimes sleeps indefinitely after attempting
to write the remaining pending output to tape.

Solution
The following patching procedure corrects this problem. It will be corrected in Version 10.1
and later.

Procedure

This is a required patch to [O,l]BACKUP.TSK

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? [O,l]BACKUP.TSK/N

This patch can be installed using ONLPAT, the online patching program.
$RUN $ONLPAT
Command file name? <CR>
RETURN for patch installation
File to patch? [O,l]BACKUP.TSK/N
File found in account [0,1]

The patch is as follows:
Base address? 74:0
Offset address? 224
Base
Offset Old
000000 000224 004767
000000 000226 007404
000000 000230 004767
Offset address? 326
Base
Offset Old
000000 000326 000545
000000 000330 104377
Offset address? "Z
Base address? 3:0
Offset address? 41252
Base
Offset Old
000000 041252 000000
000000 041254 000000
000000 041256 000000
000000 041260 000000
000000 041262 000000
000000 041264 000000
000000 041266 000000
000000 041270 000000
000000 041272 000000
000000 041274 ??????

New?
? 4737
? 41252
? "Z
CTRL/Z for new offset
New?
? 543
? "Z

CTRL/Z for new offset
CTRL/Z for new base

New?
? 12746
? 543
? 104377
? 4737
? 77610
? 12746
? 545
? 104377
? 207
up-arrowIe to exit; CTRL/C for INI'!'
? "C

RSTS/E Software Dispatch, June 1992

Seq. No. 10.2.1 R

PIP Sometimes Loops When Copying Files Into Themselves PIP. SAV Restriction
RSTS/E Vl0.0
System Library ($)
Library Restrictions
When using PIP to copy files into themselves (that is, when the target files are the same
as the source files) on a system disk initialized as New Files Last (NFL) and you specify
that disk's device name differently on the input and output side of the command line, PIP
will continue copying files in an endless loop; it will not properly detect the last file in the
directory. Under such circumstances, you must type CtrllC to terminate the operation.
For example, if your system disk is _DUl: and you issue the following command, PIP will
loop endlessly copying files:
$ PIP _SY: [1,2]=_OU1:[1,2]*.*/LOG

To prevent this, do not specify a device name for the system disk, or specify identical device
names on both the input and output side of the PIP command line, for example:
$ PIP [1,2]= OU1: [1,2]*.*/LOG
$ PIP OU1:[1,2]= OU1: [1,2]*.*/LOG
$ PIP =SY: [1,2]=_SY: [1,2]*.*/LOG

RSTS/E V10.0 Maintenance Notebook

Seq. No. 10.2.2 R

Problem
If your job currently does not have WACNT or GACNT privileges and you use the Digital
Command Language (DCL) LOGIN command to log into another account, the group and user
LOGIN.COM will only be executed if you entered the password correctly the first time LOGIN
so prompts you. If you receive an "?Invalid entry - try again" error and then supply a correct
PPN and password, the group and user LOGIN.COM may not be executed.

NOTE
Any account in which the user is expected to remain in LOGIN. COM should
have the CAPTIVE account attribute set.
The workaround is to issue the DCL LOGIN command again, without any parameters, when
you have logged into the other account.
This is a restriction for RSTSIE Version 10.0. It may be fixed in a future release of RSTSIE.

RSTS/E Software Dispatch, May 1991

Seq. No. 10.3.1 M

LOGIN May Not Always Execute Your Group and User
LOGIN.COM - Mandatory Patch
RSTS/E V10.O
System Library ($)
Library Corrections

Problem
If your job currently does not have WACNT or GACNT privileges and you use the Digital

Command Language (DCL) LOGIN command to log into another account, the group and
user LOGIN.COM will only be executed if you entered the password correctly the first time
LOGIN prompts you for it. If you receive an "?Invalid entry - try again" error and then supply
a correct PPN and password, the account's group and user LOGIN.COM may not be executed.

NOTE
Any account in which the user is expected to remain in LOGIN.COM should
have the CAPTIVE account attribute set.

Solution
The correction to this problem is to modify the system-wide [0,1]LOGIN.COM file. Using an
editor, change the line that currently reads:
$_IF P6.EQS."" THEN

GOSUB 0

to read:
$_IF P6.EQ.O THEN _GOSUB 0

This article replaces the May 1991 Software Dispatch Article Seq. No. 10.2.2 R. This problem
will be corrected in a future release.

RSTS/E Software Dispatch, August 1991

Seq. No. 11.2.1 R

ODT Displays large Addresses Incorrectly -

ODT.T5K Restriction

RSTSIE V10.O
Auxiliary Library (AUXLIB$)
Package Restrictions
ODT.TSK will not display addresses greater than 177777(8) correctly. It accesses the correct
location and displays the contents of the address correctly. It is only the display of the address
itself that is incorrect.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 12.2.1 R

ANALYS Incorrectly Shows Virtual Disk As locked Out Restriction

ANALYS

RSTS/E V10.O
Error Logging Package (ERROR$)
Package Restrictions

In the monitor dump section of the ANALYS report, the virtual disk area of the Memory
Layout is incorrectly shown as locked out.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 14.1.1 N

Notes on the Use of Serial Printers
RSTS/E V10.O
Operator Services and Spooling Package (OPSER$)
Package Notes
See Article 15.1.1 for information about using serial printers. Although it is a PrintlBatch
Services (PBS) article, it is applicable to OPSER as well.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 15.1.1 N

Notes on the Use of Serial Printers
RSTS/E Vl0.0
Print / Batch Services Package (PBS$)
Package Notes

During a power down and power up sequence, some serial terminals may send spurious
characters to the host processor. The ASCII code of these characters appears to be random,
but they occasionally take on the value of control characters (for example, CtrllC). Since the
program printing on the terminal may not expect input of any kind from the terminal, these
spurious characters may result in unexpected errors; for example, a Ctr1JC may cause the
program to exit, and a CtrlJO will cause all further output to be discarded without printing.
There is no way for the software to protect against all possible spurious inputs. RSTSIE is
able to protect against all spurious input except CtrlJS (XON) and CtrllQ (XOFF) via the
MODE 32% option on the OPEN statement. However, spurious XONIXOFF characters can
still cause loss of synchronization between the host system and the terminal. The only way
to prevent this problem is to ensure that any serial terminal used as a printer is never
powered off or powered on while it is ALLOCATEd or OPENed.
Another problem concerns loss of data when the printer is powered off. Most serial printers
contain an internal buffer which is used to hold characters which have been received from the
host processor but which have not yet been printed. When the printer goes OFFLINE (either
because the ONLINE/OFFLINE switch is placed in the OFFLINE position, or because some
exception condition, such as a paper jam, has been detected) this buffer may still contain
some unprinted data. If the printer is placed back ONLINE, printing will resume with no
loss of data. If, however, the terminal is turned off, the buffer is cleared and any data in
the buffer is lost. The only protection against this loss is to ensure that the printer is not
powered off while it is printing.
In summary, DIGITAL recommends that any serial printer to be used under RSTS/E timesharing be powered on before system start-up and that it remain on whenever it is in use.
If the terminal is powered off, loss of data and unexpected errors may result.
Another kind of problem has been encountered when spooling to the LA180S serial printer.
This problem concerns the manner in which the terminal device handles printed lines that
are longer than the width of the terminal. When a line is printed on the LA180S, the device
prints characters until it gets to the physical right margin. At that point, the logic of the
terminal inhibits further printing until a carriage return character moves the print head
back from the margin. When a CR is encountered in such a situation, the LA180S also
generates a line-feed, causing spacing to a new line. Since most print lines are terminated
by a CRILF sequence, however, the second LF will, again, cause spacing to a new line,
leaving one line blank. Thus, printing a line which is longer than the width of the LA180S
(for example, longer than 132 characters) will cause a blank line on the printed output.
When performing normal print operations under RSTSIE, the user win not ordinarily encounter this problem. The RSTS/E Terminal Service ordinarily keeps track of the characters
printed on the terminal and explicitly issues a CRILF sequence to the terminal when the
print head reaches the right margin (as defined by the !WIDTH qualifier in a SET TERMINAL command). Thus, lines printed to that terminal which are longer than the width of
RSTS/E V10.0 Maintenance Notebook

Seq. No. 15.1.1 N

the terminal result in printing of all characters, but on multiple lines. The only programs
which will have trouble are those which need to keep track of vertical position on the page
(for example, the line printer spooler) and, therefore, invoke the special MODE (Mode 4%)
to inhibit the automatic CRILF by terminal service. Files printed by such programs will
have blank lines after each line which was longer than the terminal width. There is no
practical software remedy for this problem.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 15.3.1 M

Changing Printer Forms May Disable PBS Print Servers
RSTSIE VIO.O
Print I Batch Services Package (PBS$)
Package Corrections

Problem
If a print entry is in a FORMS_WAIT state, and you change an assigned print server's form
to match that of the entry, PBS changes the entry's status to READY, indicating that the
entry can be started. The entry is then started on the server. However, in certain cases, PBS
does not change the entry's status to STARTED. The entry remains in a READY state, even
though it started printing. Several errors can occur as a result, the most common of which
are as follows:
1.

If you delete the entry while it is printing, PBS deletes the entry from its queue, but does
not notify the server to terminate printing. The job will continue printing to completion.

If another print server is available with the entry's form, the entry may be started on
that server too. The same job will be printed twice, on two different printers.

If any errors occur, the print server that last processed the entry becomes disabled and cannot
process any more print jobs. Furthermore, if you attempt to shut PBS down, PBS responds
with the message, "PrintlBatch Services will stop after completing 1 job," even though no
jobs are started. You must manually remove the PBS job and restart PBS to clear these
conditions.

Solution
The following patching procedure corrects this problem. Note that the patch will take effect
the next time PBS is started. The problem will be corrected in RSTSIE Version 10.1.

Procedure

This is a required patch to PBS.TSK The patching procedures for both versions ("RMS
Resident Library" and "No RMS Resident Library") of PBS.TSK follow. The version
running on your system is determined at installation time.

Shut down PBS.
$STOP!QUEUE!MANAGER

This patch must be installed using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? PBS$:PBS.TSK

RSTS/E Software Dispatch~ June 1992

RETURN for patch installation

Seq. No. 15.3.1 M

Apply the patch as follows:

For the "RMS Resident Library" version, use this patch:
Base address? 31:3222
Offset address? 15562
Offset Old
Base
003222 015562 112763
003222 015564 000000
003222 015566 000020
003222 015570 004737
003222 015572 052136
003222 015574 103012
003222 015576 010546
Offset address? 15622
Offset Old
Base
003222 015622 010100
003222 015624 022760
003222 015626 000003
003222 015630 000014
003222 015632 001325
Offset address? "Z
Base address? 2:2442
Offset address? 0
Offset Old
Base
002442 000000 000000
002442 000002 000000
002442 000004 000000
002442 000006 000000
002442 000010 000000
002442 000012 000000
002442 000014 000000
002442 000016 000000
002442 000020 000000
002442 000022 000000
002442 000024 000000
002442 000026 000000
002442 000030 000000
002442 000032 000000
002442 000034 000000
002442 000036 000000
002442 000040 000000
002442 000042 000000
002442 000044 000000
002442 000046 000000
002442 000050 000000
002442 000052 000000
002442 000054 000000
002442 000056 ??????

New?
? 4737
? 52136
? 103017
? 112763
? 5
? 20
CTRL/Z for new offset
? "Z
New?
? 4737
? 2442
? 4737
? 2502
? "Z

CTRL/Z for new offset
CTRL/Z for new base

New?
? 10246
? 10102
? 10046
? 10346
? 16300
? 20
? 5001
? 12703
? 5
? 4737
? 50210
? 12603
? 12600
? 12602
? 62716
? 4
? 105063
? 20
? 10100
? 22760
? 3
? 14
? 207
up-arrow/C to exit
? "C

RSTS/E Software Dispatch, June 1992

Seq. No. 15.3.1 M

For the "No RMS Resident Library" version, use this patch:
Base address? 31:3152
Offset address? 15562
Base Offset Old
New?
003152 015562 112763 ? 4737
003152 015564 000000 ? 52252
003152 015566 000020 ? 103017
003152 015570 004737 ? 112763
003152 015572 052252 ? 5
003152 015574 103012 ? 20
CTRL/Z for new offset
003152 015576 010546 ? "Z
Offset address? 15622
New?
Base Offset Old
003152 015622 010100 ? 4737
003152 015624 022760 ? 2442
003152 015626 000003 ? 4737
003152 015630 000014 ? 2502
CTRL/Z for new offset
003222 015632 001325 ? "Z
CTRL/Z for new base
Offset address? "Z
Base address? 2:2442
Offset address? 0
New?
Base Offset Old
002442 000000 000000 ? 10246
002442 000002 000000 ? 10102
002442 000004 000000 ? 10046
002442 000006 000000 ? 10346
002442 000010 000000 ? 16300
002442 000012 000000 ? 20
002442 000014 000000 ? 5001
002442 000016 000000 "? 12703
002442 000020 000000 ? 5
002442 000022 000000 ? 4737
002442 000024 000000 ? 50324
002442 000026 000000 ? 12603
002442 000030 000000 ? 12600
002442 000032 000000 ? 12602
002442 000034 000000 ? 62716
002442 000036 000000 ? 4
002442 000040 000000 ? 105063
002442 000042 000000 ? 20
002442 000044 000000 ? 10100
002442 000046 000000 ? 22760
002442 000050 000000 ? 3
002442 000052 000000 ? 14
002442 000054 000000 ? 207
up-arrow/C to exit
002442 000056 ?????? ? "C

Restart PBS.
$ START/QUEUE/MANAGER

RSTS/E Software Dispatch, June 1992

Seq. No. 22.2.1 R

RMS-11 Does Not Correctly Handle Underscores -

RMS Restriction

RSTSIE V10.O
RMS-ll V2.0 (RMS$)
Package Restrictions

RMS-ll Access Methods does not correctly handle a file specification which contains an
underscore in front of the device name. RMS-ll ignores the underscore.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 22.2,2 R

RMS-11 May Incorrectly Report Error on Remote Access of Indexed
File - RMS Restriction
RSTS/E V10.0
RMS-11 V2.0 (RMS$)
Package Restrictions
Keyed access on a remote indexed file will incorrectly report .a Record Not Found error when
the target record's key size is described as zero on a key whose datatypeis non-string. This
is documented as a correct way to pass a nonstring key, but currently works .correctly only
for local operations.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 27.1.1 N

Attributes Are lost When RMS File Is Copied to DOS Format Tape
RSTS / E Vl0.0
DeL Run-time System and Utilities
Package Notes
Because the DOS magnetic tape format does not provide a way to store RMS attribute
information, RMS files that are copied to DOS magtape will lose their attributes and may
be rendered unusable. The COPY command will not issue a warning when this happens.
To store RMS files on magnetic tape, use one of the following methods, all of which will
retain RMS attributes:
CD

Use ANSI format instead of DOS

Use the BACKUP utility

Use RMSBCK, the RMS-ll backup utility

RSTS/E V10.0 Maintenance Notebook

Seq. No. 27.1.2 N

Exclamation Marks in BROADCAST Commands
RSTS/E VI0.0
DeL Run-time System and Utilities

Package Notes
Exclamation marks in continuation lines cannot be used with the BROADCAST command.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 27.2.1 R

MOUNT Command With /OVERRIDE Qualifier -

DCl Restriction

RSTS/E V10.O
DeL Run-time System and Utilities

Package Restrictions
When issuing a MOUNT command with the IOVERRIDE qualifier and without a pack label,
the logical name, if specified, must not have a colon (:) appended.
Use a command of the following format:
MOUNT DU1:/0VERRIDE/PRIVATE MYDISK

Do not use:
MOUNT DU1:/0VERRIDE/PRIVATE MYDISK:

RSTS/E V10.0 Maintenance Notebook

Seq. No. 27.3.1 M

Creating Global Symbols in Nested Command Files Can Cause
an Unexpected Error - Mandatory Patch
RSTS/E V10.O
DCL Run-time System and Utilities
DCL Package Corrections

Problem
When a nested command procedure creates global symbols and exits, returning to the previous
command procedure, the symbol table may become too large to fit in memory. When this
happens, Digital Command Language (DCL) displays the fatal error:
??Program failure in DCL
?Not enough available memory

DCL is then left in an unpredictable state, and the job must be removed.

Solution
The following patching procedure corrects this problem. The correct action is for DCL to abort
the command procedure and display the error message:
??Symbol table full

Procedure

This is a required patch to the DCL run-time system. It must be installed in all DCL
run-time systems.

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

This patch can be installed using ONLPAT, the online patching program:
~UN

$ONLPAT
Command File Name? <CR>
File to patch? [O,l]DCL.RTS
File found in account [0,1]

RSTS/E Software Dispatch, July 1991

RETURN for patch installation

Seq. No. 27.3.1 M

The patch is as follows:
Base address? DCLCFP
Offset address? 14640
Base
Offset Old
New?
102674 014640 012746 ? 22705
102674 014642 000020 ? 4
102674 014644 010546 ? 1406
102674 014646 004567 ? 12746
102674 014650 151140 ? 20
102674 014652 121112 ? 10546
102674 014654 022705 ? 4537
102674 014656 000002 ? $$CAL2
102674 014660 001402 ? CLSPFB
102674 014662 005745 ? 5305
102674 014664 000765 ? 77513
102674 014666 042767 ? "z
CTRL/Z for new offset
Offset address? "Z
CTRL/Z for new base
Base address? DCLSYM
Offset address? 6422
Base
Offset Old
New?
160036 006422 004737 ? <CR> no change; verify only
160036 006424 045212 ? PATCH
160036 006426 110467 ? "z
CTRL/Z for new offset
Offset address? "Z
CTRL/Z for new base
Base address?-- PATCH
Offset address? 0
Base
Offset Old
' New?
101576 000000 000000 ? 105737
101576 000002 000000 ? FIRQB
101576 000004 000000 ? 1412
101576 000006 000000 ? 4737
101576 000010 000000 ? QCKSTP
101576 000012 000000 ? 5037
101576 000014 000000 ? LCAPTR
101576 000016 000000 ? 12700
101576 000020 000000 ? STFL.E
101576 000022 000000 ? 5726
101576 000024 000000 ? 105037
101576 000026 000000 ? CMDLVL
101576 000030 000000 ? 261
101576 000032 000000 ? 207
Up-arrow C to exit;Ctrl/C for INIT
101576 000034 000000 ? "C

For this patch to take effect, execute the following command:
$ UNLOAD/RUNTIME DCL

NOTE
The UNLOAD command will not remove the run-time system, but simply
instructs the monitor to reload it the next time a job requests it.

RSTS/E Software Dispatch, July 1991

Seq. No. 27.3.2 M

Using F$SEARCH Can Cause an Unexpected Error Patch

Mandatory

RSTS/E VI0.0
DCL Run-time System and Utilities
DCL Package Corrections

Problem
When no free channels are available and a command procedure issues the F$SEARCH function, Digital Command Language (DCL) displays the following error message, followed by a
register dump.
??Program failure in DCL
??Odd address trap

DCL may be left in an unpredictable state and the job may need to be removed.

Solution
The following patching procedure corrects this above problem. The correct action for DCL to
take is to display the following error message at the command line containing theF$SEARCH:
?No channels available

Procedure

This is a required patch to the DCL run-time system. It must be installed in all DCL
run-time systems.

The patch described in step 4 can be installed using the PATCH option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

This patch can be installed using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? [O,l]DCL.RTS
File found in account [0,1]

RSTS/E Software Dispatch, July 1991

RETURN for patch installation

Seq. No. 27.3.2 M

The patch is as follows:
Base address? DCLFUN
Offset address? 6540
Base
Offset Old
147350 006540 010146
147350 006542 010405
147350 006544 004737
147350 006546 121206
147350 006550 012603
147350 006552 103750
147350 006554 010467
147350 006556 032376
147350 006560 074405
147350 006562 050567
147350 006564 032372
147350 006566 016705
147350 006570 024366
147350 006572 010165

New?
? 10446
? 10146
? <CR> no change; verify only
? <CR> no change; verify only
? <CR> no change; verify only
? 103002
? 5026
? 746
? 10437
? PFBCHN
? 74416
? 52637
? F$SCHN
up-arrow/C to exit;C'l'RL/C for INI'l'
? AC

To make this patch take effect, execute the following command:
$ UNLOAD/RUNTIME DCL

NOTE
The UNLOAD command will not remove the run-time system, but simply
instructs the monitor to reload it the next time a job requests it.

RSTS/E Software Dispatch, July 1991

Seq. No. 28.1.1 N

Using the RSX-11 CRF Utility
RSTS / E Vl0.0
RSX-ll Emulator and Utilities
Package Notes
The RSX-ll utility CRF.TSK is included on the RSTS distribution kit as an unsupported
utility. It is installed in the system library ([1,2]) account with other components in the
RSX-ll package.
This program will create cross-reference listings from the binary cross reference (.CRF) files
optionally produced by the RSX-ll task builder (TKB) and RSX-ll MACRO assembler
(MAC). The cross reference file created by MAC lists page and line number references to
data items and routines, whereas the cross reference file created by TKB lists the names
of the object modules which reference these items. The following are examples of these two
types of output:
MACRO Assembler output:
CRF
CREATED BY MACRO ON 15-JUN-85 AT 06:02
SYMBOL CROSS REFERENCE
SYMBOL VALUE
REFERENCES
CR
= 000015
#4-180
FF
000014
#4-180
HT
= 000011
#4-180
LF
= 000012
#4-180
L$$IST
1-1
1-2
2-53
******
= 000001
#4-39
RSTS
#4-38
R$$l1M = 000000
SPA
= 000040
#4-180
VT
= 000013
#4-180
V1145
4-157
= ******
$$$VER = 034066
#3-2
#5-1

PAGE 1
CREF
07.065

4-182

Task Builder output:
CRF
CREATED BY TKB
ON 15-JUN-85 AT 06:23
GLOBAL CROSS REFERENCE
SYMBOL VALUE
REFERENCES ...
A.BTTN 000002
# DIRSYM
A.DFUI 000102
# FCSGBL
CRFIN
A.LULU 000002
# DIRSYM
A.LUNA 000004
# DIRSYM
A.LUNU 000006
# DIRSYM
A.TRBA 000002
# DIRSYM
BADDIR 000001
FIP
# ERR
BAD~AM
000002
FIP
# ERR

PAGE 1
CREF
07.065

The first step is to cause MAC or TKB to create a binary cross-reference file, which is used
by the CRF utility to produce the cross-reference listing. To request that MAC or TKB
produce this file, specify the fCR switch in the command line to these programs. For MAC
the switch is included with the listing file specification and for TKB it is included with the
map file specification. For example:
$ RUN $MAC
MAC>TEST,TEST/CR=TEST
MAC>"Z
$

RSTS/E V10.0 Maintenance Notebook

Seq. No. 28.1.1 N

The binary file created has the same name as the listing or map file and its file type is
always .CRF.
CRF.TSK is then run, using either the RUN command or the CRF CCL if installed. When
run using the RUN command, CRF will prompt with CRF>. Typing CtrllZ to this prompt
will cause an exit to your default RTS. The command line is a single RSTS/E file specification
of the file into which the cross reference listing is to be placed. The default file type for this
file is .LST. If the file specified already exists, CRF appends the listing to it; otherwise, a
new file is created. The CRF output is variable length records and, therefore, if the file
specified for output already exists, it must also be a variable length file. The listing file
produced by MAC and the map file created by TKB are both variable length files making
them prime candidates. For example:
$ RUN $CRF
CRF>TEST.LST
CRF>"Z
$

This will cause the cross-reference listing to be appended to the TEST.LST listing file which
was originally created by MAC. CRF can also append the cross-reference listing to the MAP
file generated by TKB. For example:
$ RUN $CRF
CRF>TEST.MAP
CRF>"Z
$

In either case, the binary cross-reference file TEST.CRF, which was created by MAC or TKB,
will be deleted automatically by CRF.
CRF requires the binary cross-reference file to have the same name as the output file with
a file type of .CRF. Since CRF always deletes this file when it is done, you must copy this
file into a non-.CRF file before running CRF if you wish to keep a copy of it.
CRF also accepts as input an indirect command file (preceded by @) which can contain a list
of file specifications. Each specification in the file will be processed as if it was separately
entered to the CRF> prompt. The default file type for the command file is .CMD. CRF only
allows one level of command indirection.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 28.2.1 R

RSX-11 Utilities Do Not Handle All RSTS/E File Specifications RSX-11 Package Restriction
RSTS/E Vl0.0
RSX-ll Emulator and Utilities
Package Restrictions
Several RSX-ll utilities do not properly handle all RSTSIE file specifications. Table llists
those RSX-ll tasks which do not handle various parts of a RSTSIE Filespec.
Table 1: RSX-11 Utilities -

Utility

RSTS/E Filespec Restrictions

Allow Logical Name
Longer than six
Characters?

Allow Logical Name
Containing Dollar ($)
Sign?

Allow Om itted
Fields in PPN?

TKB

Yes

MAC

Yes

PAT

Yes

LBR

Yes

RSTS/E V10.0 Maintenance Notebook

Seq. No. 29.1.1 N

Use of Underscore in RT 11 Utilities
m

RSTS/E Vl0.0
RT-l1 Emulator and Utilities
Package Notes

RSTS/E allows the use of the underscore C) character before a device name in a file specification to indicate that the device name is not to undergo logical translation. Utilities provided
with the RT-ll emulator will allow the use of the underscore character; however, due to the
nature of the emulator, it is still possible for the device name to undergo translation before
a file is opened.
In the RT-ll emulator, file specifications given to a utility are scanned using the RT-U CSI
(command string interpreter). At this time, the device designation mayor may not undergo
logical translation (depending on whether or not the underscore was used). The CSI returns
RT-ll file description blocks to the utilities.
When the utility program then requests the emulator to open a file, the file open code
does an additional logical translation on the specified device name. This is an unavoidable
consequence of allowing logical device names to be specified in RT-ll file description blocks.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 29.2.1 R

Disk Unit Numbers Greater Than Nine May Not Be Displayed Correctly
- RT-11 Package Restriction
RSTS / E Vl0.0
RT-ll Emulator and Utilities
Package Restrictions

The following utilities will not correctly print the disk name and unit number in error
messages for DU disks with unit numbers greater than nine:
• LINKSAV
• LIBR.SAV
.MACRO.SAV
For example, if the source file TESTOI does not exist on disk DU15, you will get this error
message:
$ RUN $MACRO
*DU15:TEST01=DU15:TESTOl
?MACRO-F-File not found DVE:TEST01.MAC
DU15:TEST01=DU15:TESTOl

RSTS/E V10.0 Maintenance Notebook

Seq. No. 31.2.1 R

SET EXECUTOR SEGMENT BUFFER SIZE May Fail Without Warning
- NCP. TSK Restriction
RSTS/E VI0.0
DECnet / E Utilities V4.1 (DECNET$)
Package Restrictions
The NCP Command SET EXECUTOR SEGMENT BUFFER SIZE n does not work when the
EXECUTOR STATE is ON. The command should fail with an appropriate error but instead
appears to succeed without taking any action.

RSTS/E V10.0 Maintenance Notebook 1

Seq. No. 31.2.2 R

SHOW NODE Command May Fail -

NCP.TSK Restriction

RSTS/E V10.O
DECnet / E Utilities V4.1 (DECNET$)
Package Restrictions

When attempting to issue a command such as:
SHOW NODE node address COUNTERS

and the node node_address is not defined in your volatile database, NCP will report that
the node does not exist, even though you may have an active link to it.
The workaround is to ensure that all the nodes you normally access are defined in your
volatile parameter file.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 31.2.3 R

Network Parameter File Will Not Hold More Than 26,000 Nodes DECnet/E Package Restriction
RSTS /E V10.O
DECnet / E Utilities V4.1 (DECNET$)
Package Restrictions
DECnetIE will not successfully create a network parameter file for networks with more than
26,000 nodes. To successfully create the node database NETPRM.SYS, you must specify a
Maximum Nodes value smaller than 26,000.

RSTS/E V10.0 Maintenance Notebook

Seq, No. 31.2.4 R

SET HOST May Give Erroneous Error Message Restriction

NETUNS.TSK

RSTS IE Vl0.0
DECnet IE Utilities V4.1 (DECNET$)
Package Restrictions
When you SET HOST from RSTSIE to some versions of VMS and log off the VMS system,
DECnetlE may display the following message:
%Logical link failure to remote node xxxxxx
NSP reason code = 0
Control returned to node xxxxxx

This error message is triggered by the receipt of an unexpected message from the VMS node
during the disconnect, The error message is extraneous; no actual error has occurred and
the user session is not otherwise affected.
Similarly, when you SET HOST to RSTSIE from some versions of VMS, the same error may
be displayed. In such cases, the remote job on the RSTSIE system is left detached.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 31.2.5 R

Network File Transfers May Not Correctly Preserve Protection Codes
- NFT.TSK/FAl.TSK Restriction
RSTS/E Vl0.0
DECnet / E Utilities V4.1 (DECNET$)
Package Restrictions
NFT (the Network File Transfer program) and FAL (the File Access Listener) do not always
preserve protection codes when creating files. Protection codes for the output files are computed by adding together the default system protection code and the codes for executable
(64), protected (128), or executable and privileged (64+128) as set on the input file.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 31.3.1 M

SHOW and LIST Commands Display Inappropriate Information
- Mandatory Patch
DECnet / E Utilities for RSTS / E Vl O. 0
DECnet / E Utilities Corrections

Problem
The SHOW KNOWN NODES and LIST KNOWN NODES commands display inappropriate
information. When the executor node record is purged, the first node in the database is
displayed twice. If no nodes are defined in the database, the error message "Error getting
network device DDB" is displayed.

Solution
The following patching procedure corrects this problem. It win be corrected in a future release.

Procedure

This is a required patch to NCP.TSK.

The patch described in step 4 cannot be installed using the PATCH option of INIT.SYS.

This patch must be installed using ONLPAT, the online patching program:
RUN $ONLPAT
Command File Name? <CR>
File to patch? DECNET$:NCP.TSK
File found in account [0,16)

RETURN for patch installation

The patch is as follows:
Base address? NOREIN
Offset address? 610
Base
Offset Old
122500 000610 001000
122500 000612 000016

New?
? 1010
? AC

RSTS/E Software Dispatch, May 1991

up-arrowie to exit

Seq. No. 34.1.1 N

list Processing Message "No room left. ..

WPS-PLUS / RSTS
List Processing

Problem
When using List Processing, you might receive one of the following error messages:
..

"No room left to run list processing"

"No room left for this operation - DOCUMENT_TOO_LARGE"

Solution
If either of these error messages occur, it indicates that WPS List Processing has exceeded
the maximum allowable space allocation for a single list processing transaction. The space
allocation value is affected by the interaction of several factors, specifically:
to

Number of items in the list document

Text size of each item in the list document

Text size of the form document

File size of the list, form, and output documents

The result of exceeding this space allocation is that no additional text can be written to the
output document.
Unfortunately, when the error occurs, the output document is not saved, and the error message overwrites the current record selected counter which is updated as list processing advances. This makes it difficult to determine how many records were processed before the
error occurred.
The easiest way to resolve this limitation is to divide the list document in half and retry. If
either half still fails, divide it in half again. Repeat as necessary.
Another method would be to process the same list and form document again while visually
monitoring the record count until the error occurs again. Decrease the record count by five
percent and use that value to determine into how many files the list document should be
divided. The reason for the five percent reduction is to allow a margin of additional text
added to the form document.

RSTS/E Software Dispatch, April 1991

Seq. No. 49.1.1 N

Instructions Missing in DATATRIEVE-11 V3.3 Installation Guide
DATATRIEVE-ll for RSTS / E VIO.O
DDMF

Problem
There are no instructions in the DATATRIEVE-ll V3.3 Installation Guide that describe the
procedure to restart the DTR-ll task DDMF after a system shutdown.

Solution
The DATATRIEVE-ll task images will reside in the directory [1,2]. If your system shuts
down, make sure DECnet is running on your system, then you can restart ~he DDMF task
image with the following commands:
$ RUN DECNET$:NCP
NCP> DEFINE OBJECT 30 FILE SY: [1,21DDMF.TSK NAME DDMF
NCP> SET OBJECT 30 FILE SY:[1,2]DDMF.TSK NAME DDMF

You can include these commands in the startup file, [O,1]START.COM, along with the command in Section 4.3.5, Restart Mer Shutdown, in the Installation Guide:
$ DEFINE/COMMAND/SYSTEM DTR $DTR.TSK

RSTS/E Software Dispatch, January 1991

Seq. No. 57.2.1 A

IF-THEN-ELSE Statement Embedded Within DO-LOOP Causes
Infinite Loop - Restriction
FORTRAN/77
FORTRAN /77 Package Restrictions

Problem
Incorrect code is generated when there is an IF-THEN-ELSE statement within a DO-LOOP'
This causes the registers to be restored incorrectly, and an infinite loop occurs. This only
happens when the optimizer is enabled during compilation, either by having the lOP qualifier
defined as the default or by specifYing it directly on the command line.

Workaround
The workaround to this problem is to use the !NOOP qualifier when compiling your programs.
This will not optimize your code, but it will prevent the infinite loop problem from occurring.

Solution
An update that contains the correction to this problem will be available in a future RSTSIE
operating system layered product update. This update will replace the CODEXI module in
F77.0LB, and the new library will be used to rebuild the compiler.

RSTS/E Software Dispatch, October 1991

Seq. No. 79.1.1 R

SAVE, REPLACE, and LIST Sometimes Lose Lines of Source
Text - Restriction
RSTS/E VI0.0
BASIC-PLUS-2 for RSTS/E VI0.0
Restrictions
Supersedes Seq. No. 4.3.1 R, December 1991 RSTSIE Software Dispatch

Problem
The SAVE, REPLACE, and LIST commands sometimes lose lines of source text.
Therefore, a program maintained by use of a sequence of an OLD command, editing commands, and a REPLACE command can be corrupted. No warning is given until a subsequent
attempt at compilation - and perhaps not even then, should the loss of text be such as to
result in a still syntactically valid program.
The problem is triggered by a source line that is either explicitly continued (by being terminated with an ampersand character) or that is not continued (because of being the last source
line in a numbered BASIC-PLUS-2 statement). When such a source line is stored in the
compiler's work file, and when the last byte of the source line happens to fall into the last
byte of a disk block in the work file, then SAVE, REPLACE, and LIST can fail.
The SAVE, REPLACE, and LIST commands all work by retrieving source text from the compiler'S work file. When such a source line is retrieved, an erroneous condition is set up in
which the next implicitly continued statement to be retrieved may cause a truncation: all
source lines following the next implicitly continued statement up through the end ofthe work
file block in which it occurs will not be retrieved. The truncation can occur from any number
of blocks farther down in the work file and can even occur on a subsequent SAVE, REPLACE,
or LIST command.
Note that whether the last byte of a source line falls on the last byte of a work file block is
determined by the number of bytes from the beginning of the source file. Thus, the problem
is very sensitive to source text. The action of inserting or removing a space character in a
comment can cause the truncation phenomenon to appear or to vanish.

Workaround
Because only the SAVE, REPLACE, and LIST commands are affected, the problem can be
avoided by using other program-maintenance techniques, such as making changes to source
programs by use of an editor.
The OLD command is not affected. The sequence of OLD plus COMPILE works correctly.

Solution
An update containing the correction to this problem will be available in a future RSTSIE
layered-product update. This update will replace the KM:ON module in the RSTLIB.OLB,
and the new library will be used to rebuild the compiler.

RSTS/E Software Dispatch, April 1992

RSTS/E V10.0 Cumulative Index

This is a complete listing of all articles for RSTSIE VlO and layered products. Missing sequence numbers may pertain to problems unique to other versions of the same product or
other major operating systems.
Unassigned articles are indicated: RESERVED.
Flags are currently being installed for all articles. The flags and definitions are as follows.

•

M = Mandatory Patch. These patches correct errors in the software product. All users
are required to apply these patches to maintain consistent "user level" unless the accompanying article specifies otherwise.

•

F = Optional Feature Patch. These patches extend or configure functionality into the

product. These functions will be treated as a supported part of the product for the
duration of the current release and may be incorporated in a future release.

•

R = Restriction. These articles discuss areas that will not be patched in the current release because they require major modification or because they are not consistent with the
design of the product. Restrictions, except those described as permanent, are reviewed
and modified when possible as part of the normal release cycle.

•

N = Note. These articles provide explanatory information that supplements the manual
set and provide more detailed information about a program or package. They also provide
procedural information to make it easier to use a program or package.

•

* = Article appeared in the RSTS / E V10.0 Maintenance Notebook, August 1990.

•

+ = Article appeared in the RSTS / E Software Dispatch Review, August 1990.

•

- = Article is being republished.

Sequence

Title

Released

Corrected

Mon/Yr

RSTS/E Vi 0.0 Component Summary
Announcing New Hardware Support for RA92 Disks
Announcing New Hardware Support for DECserver 90l

V10.0
V10.0
V10.0

N/A
N/A
N/A

Aug 90 *
Jul91
Jul91

INIT.SYS Program Patches
1.1.1 M
INIT Can Fail During Some RQDX Controller Accesses
- Mandatory Patch

V10.0

N/A

Jan 91

V10.0

N/A

Aug 90 *

V10.0
V10.0

N/A
N/A

Aug 90 *
Aug 90 *

General Notes
System Notes
0.1.1 N
0.1.2 N
0.1.3 N

Initialization

Initialization
INIT.SYS Notes
1.2.1 N
Unnecessary Error Message When Booting 800 bpi
Tape on TM02
INlT.SYS Restrictions
1.3.1 R
First TMSCP Drive on System Must Be Unit 0
1.3.2 R
MT/MM Tapes Must Be Booted From Unit 0

RSTS/E Software Dispatch, August 1991

RSTS/E V10.0 Cumulative Index

System Installation and Update
Installation/Update Notes
Installation Flag Files
2.1.1 N
Installation/Update Restrictions
2.3.1 R
RSTS/E Version 10.0 Installation Procedure
Restrictions
2.3.2 R
Cannot Mount Disks at the Beginning of the
Installation Procedure
2.3.3 R
Monitor Installation on Target Disk Uses
System Disk for Template

V10.0

N/A

Aug 90 *

V10.0

N/A

Dec 90

V10.0

N/A

Feb 91

V10.0

N/A

Feb 91

V10.0

N/A

Feb 91

V10.0

N/A

Jul 91

V10.0

N/A

Aug 90'

V10.0
V10.0
V10.0

N/A
N/A
N/A

Aug 90'
Aug 90'
Dec 90

V10.0
V10.0
V10.0
V10.0

N/A
N/A
N/A
N/A

Mar 91
May 91
Jun 91
Jun 91

V10.0

N/A

Jun 91

V10.0

N/A

Jul 91

V10.0

N/A

Aug 91

V10.0

N/A

Aug 91

V10.0
V10.0

N/A
N/A

Aug 90'
Aug 90'

V10.0

N/A

Dec 90

V10.0

N/A

Jan 91

V10.0

N/A

Apr 91

V10.0
V10.0

N/A
N/A

Apr 91
Jul91

V10.0

N/A

Aug 91

V10.0

N/A

Aug 90 *

Executive
Monitor Patches

, 3.1.1 M
,Y.

3.1.2 M

DEASSIGN SYS Call Can Crash System
- Mandatory Patch
Protection Violation Error When Issuing the
. RTS Directive - Mandatory Patch

Monitor Restrictions
DCl Log File Corruption on Full Disk
3.3.1 R
Terminal Service Corrections
3.4.1 F
Changing Special Login Terminal
3.4.2 F
Input Escape Sequence Handling
3.4.3 M
Host-Initiated LAT Connections May Crash System
- Mandatory Paich
#' 3.4.4 M
Three Problems in Terminal Service - Mandatory Patch
/3.4.5 M
Problem with TECO Mode - Mandatory Patch
",3.4.6 M
Inappropriate Character Echoing - Mandatory Patch
",3.4.7 M
Private Delimiters Cause Problems with
Command Recall - Mandatory Patch
,,.3.4.8 M
Characters lost When Data Error Received
- Mandatory Patch
... 3.4.9 M
Command Recall May Crash System
- Mandatory Patch
Forced Characters Echoed Even Under NOECHO
...,3.4.10 M
- Mandatory Patch
,3.4.11 M
Problem Processing Escape Sequences as Type Ahead
- Mandatory Patch
Terminal Service Notes
3.5.1 N
Modem Support on RSTS/E
3.5.2 N
Unexpected Abort from Captive Command File Will Not
Hang Up Dialup Line
File Processor Patches
.,.3.7.1 M
Attaching to a Detached Job May Crash System
- Mandatory Patch
; 3.7.2 M
Dynamic Region Creation Can Crash System
- Mandatory Patch
,,3.7.3 M
Previous System logical Assignment Not Replaced
- Mandatory Patch
Spawned Job May Fail to Execute - Mandatory Patch
0#"3.7.4 M
,.-3.7.5 M
Characters May Not Echo When Setting Host
to VMS System - Mandatory Patch
System Hangs After Setting Terminal Width
13.7.6 M
- Mandatory Patch
Device Driver Restrictions
3.12.1 R
DB/DR Driver May log Errors for Wrong Unit

RSTS/E Software Dispatch, August 1991

RSTS/E V10.0 Cumulative Index

Sequence

Title

Released

Corrected

Mon/Yr

3.12.2 R

Swapping MSCPITMSCP Unit Numbers May Cause
Crash

V10.0

N/A

Aug 90 *

V10.0
V10.0
V10.0
V10.0
V10.0
V10.0
V10.0

N/A
N/A
N/A
N/A
N/A
N/A
N/A

Aug 90'
Aug 90'
Aug 90 *
Aug 90'
Aug 90'
Aug 90'
Jan 91

V10.0

N/A

Feb 91

V10.0

N/A

Feb 91

V10.0
V10.0
V10.0

N/A
N/A
N/A

Aug 90'
Aug 90'
Aug 90'

V10.0

N/A

Mar 91

V10.0

N/A

Feb 91

V10.0

N/A

Mar 91

V10.0

N/A

Jun 91

V10.0

N/A

Jul91

BASiC·PLUS
BASIC-PLUS Patches
4.1.1 F
Special PRINT-USING Characters
4.1.2 F
Default SCALE Factor
4.1.3 F
Omitting SCALE Factor Warning Message
4.1.4 F
Default to NOEXTEND Mode
4.1.5 F
Immediate Mode from .BAS File
4.1.6 F
Disabling the CCl SYS Cali
-,4.1.7M
DATE% Is Now a Reserved Keyword
- Mandatory Patch
4.1.8 F
RAD% Is Now a Reserved Keyword
- BASIC-PLUS Feature Patch
BASIC-PLUS Notes
4.2.1 N
New BASIC-PLUS Function -

RAD%

Optional BASIC-PLUS Features
4.11.1 N
The BASIC-PLUS DEBUG Facility
4.11.2 N
The BASIC-PLUS DUMP Facility
4.11.3 F
Enabling DUMP from Compiled Files for Nonprivileged
Users

System File Restrictions
BACKUP.TSK
6.2.1 R
RESTORENERIFY/NOREPlACE Can Enter Infinite
Sleep State
System File Corrections
BACKUP.TSK
",6.3.1 M
BACKUP Can Fail to Back Up Some File Data
- Mandatory Patch
BACKUP/INITIALIZE Can Exit with Error
"" 6.3.2 M
- Mandatory Patch
F' 6.3.3 M
BACKUPNERIFY=ONlY Rewinds Before Execution
- Mandatory Patch
BACKUP/BUFFER_SIZE=OPTIMUM May Not Select
'" 6.3.4 M
the Optimum Buffer Size - Mandatory Patch

RSTS/E Software Dispatch, August 1991

RSTS/E V10.0 Cumulative Index

Released

Corrected

Mon/Yr

V10.0

N/A

Aug 90'

V10.0

N/A

May 91

V10.0

N/A

Aug 91 -

Auxiliary Library (AUXLlB$)
Library Restrictions
11.2.1 R
ODT Displays Large Addresses Incorrectly

V10.0

N/A

Aug 90'

Error Logging Package (ERROR$)
Package Restrictions
12.2.1 R
ANALYS Incorrectly Shows Virtual Disk as Locked Out

V10.0

N/A

Aug 90'

Operator Services and Spooling Package (OPSER$)
Package Notes
14.1.1 N
Notes on the Use of Serial Printers

V10.0

N/A

Aug 90'

Print/Batch Services Package (PBS$)
Package Notes
15.1.1 N
Notes on the Use of Serial Printers

V10.0

N/A

Aug 90'

V10.0
V10.0

N/A
N/A

Aug 90'
Aug 90'

Sequence

Title

RSTS/E Utilities
System Library ($)
Library Restrictions
10.2.1 R
PIP Sometimes Loops When Copying Files into
Themselves
10.2.2 R
LOGIN May Not Always Execute Your Group and User
LOGIN.COM
Library Corrections
10.3.1 M
LOGIN May Not Always Execute Your Group and User
LOGIN.COM

RMS-11 V2.0 (RMS$)
Package Restrictions
22.2.1 R
RMS-11 Does Not Correctly Handle Underscores
22.2.2 R
RMS-11 May Incorrectly Report Error on Remote
Access of Indexed File

RSTS/E Software Dispatch, August 1991

RSTS/E V10.0 Cumulative Index

Sequence

Title

Released

Corrected

Mon/Yr

V10.0

N/A

Aug 90'

V10.0

N/A

Aug 90 *

V10.0

N/A

Aug 90'

V10.0

N/A

Jul91

V10.0

N/A

Jul91

V10.0

N/A

Aug 90'

V10.0

N/A

Aug 90'

V10.0

N/A

Aug 90 *

V10.0

N/A

Aug 90 *

V10.0

N/A

Aug 90 *

V10.0
V10.0

N/A
N/A

Aug 90'
Aug 90 *

V10.0
V10.0

N/A
N/A

Aug 90'
Aug 90 *

N/A

May 91

Run-Time Systems Support
DCl Run-time System and Utilities
Package Notes
27.1.1 N
Attributes Are Lost When RMS File Is Copied to DOS
Format Tape
27.1.2 N
Exclamation Marks in BROADCAST Commands
Package Restrictions
MOUNT Command with IOVERRIDE Qualifier
27.2.1 R
Package Corrections
Creating Global Symbols in Nested Command Files
"'" 27.3.1 M
Can Cause an Unexpected Error - Mandatory Patch
,.27.3.2 M
Using F$SEARCH Can Cause an Unexpected Error
- Mandatory Patch
RSX-11 Emulator and Utilities
Package Notes
Using the RSX-11 CRF Utility
28.1.1 N
Package Restrictions
RSX-11 Utilities Do Not Handle All RSTS/E File
28.2.1 R
Specifications
RT-11 Emulator and Utilities
Package Notes
29.1.1 N
Use of Underscore in RT-11 Utilities
Package Restrictions
29.2.1 R
Disk Unit Numbers Greater Than Nine May Not Be
Displayed Correctly

Optional Software
DECnet/E Utilities V4.1 (DECNET$)
Package Restrictions
SET EXECUTOR SEGMENT BUFFER SIZE May Fail
31.2.1 R
Without Warning
31.2.2 R
SHOW NODE Command May Fail
31.2.3 R
Network Parameter File Will Not Hold More Than
26,000 Nodes
31.2.4 R
SET HOST May Give Erroneous Error Message
31.2.5 R
Network File Transfers May Not Correctly Preserve
Protection Codes

DECnetlE Utilities for RSTS/E V10.0
DECnetlE Utilities Corrections
31.3.1 M
SHOW and LIST Commands Display Inappropriate
Information - Mandatory Patch

RSTS/E Software Dispatch, August 1991

RSTS/E V10.0 Cumulative Index

Sequence

Title

Released

Corrected

Mon/Yr

Announcing PDP-11 C for RSTS/E V1.0

N/A

Aug 90 +

N/A

Apr 91

N/A

Jan 91

PDP-11 C V1.0
33.0.1 N

WPS-PLUS/RSTS

list Processing
34.1.1 N

List Processing Message "No room left ... "

DATATRIEVE for RSTS/E Vi 0.0
49.1.1 N

Instructions Missing in DATATRIEVE-11 V3.3
Installation Guide

RSTS/E Software Dispatch, August 1991

RSTS/E Version 10.0 Cumulative Index

This is a complete listing of all articles for RSTSIE Version 10 and layered products. Missing
sequence numbers may pertain to problems unique to other versions of the same product or
other major operating systems.
Unassigned articles are indicated: RESERVED.
Flags are currently being installed for all articles. The flags and definitions are as follows.

•

F = Optional Feature Patch. These patches extend or configure functionality into the
product. These functions will be treated as a supported part of the product for the
duration of the current release and may be incorporated in a future release.

•

* = Article appeared in the RSTS I E ~rsion 10.0 Maintenance Notebook, August 1990.

•

+ = Article appeared in the RSTS I E Software Dispatch Review, August 1990.

•

- = Article is being republished.
Released

Corrected

Mon/Yr

V10.0
V10.0
V10.0

N/A
N/A
N/A

Aug 90'
Jul91
Jul 91

V10.0

N/A

Jan 91

INIT.SYS Notes
Unnecessary Error Message When Booting 800 bpi
1.2.1 N
Tape on TM02

V10.0

N/A

Aug 90'

INIT.SYS Restrictions
First TMSCP Drive on System Must Be Unit 0
1.3.1 R
MTIMM Tapes Must Be Booted from Unit 0
1.3.2 R

V10.0
V10.0

N/A
N/A

Aug 90'
Aug 90'

Sequence

Title

General Notes
System Notes
RSTS/E V10.0 Component Summary
0.1.1 N
Announcing New Hardware Support for RA92 Disks
0.1.2 N
Announcing New Hardware Support for DECserver 90l
0.1.3 N
Initialization
. INIT.SYS Program Patches
11.1.1 M
INIT Can Fail During Some RQDX Controller Accesses
- Mandatory Patch

RSTS/E Software Dispatch, June 1992

RSTS/E Version 10.0 Cumulative index

Released

Corrected

Mon/Yr

V10.0

N/A

Aug 90·

V10.0

NlA

Dec 90

V10.0

N/A

Feb 91

V10.0

N/A

Feb 91

V10.0

N/A

Apr 92

V10.0

N/A

Feb 91

V10.0

N/A

Jul91

V10.0

N/A

Nov 91

V10.0

N/A

Aug 90'

V10.0
V10.0
V10.0

N/A
N/A
NlA

Aug 90'
Aug 90'
Dec 90

V10.0
V10.0
V10.0
V10.0

N/A
NlA
NlA
N/A

Mar 91
May 91
Sep 91 Jun 91

V3.4.8

V10.0

NlA

Jun 91

13.4.9

V10.0

NlA

Jun 92 -

V10.0

N/A

Aug 91

V10.0

N/A

Aug 91

V10.0

NlA

Oct 91

V10.0

NlA

Jun 92

V10.0
V10.0

N/A
NlA

Aug 90'
Aug 90'

V10.0

N/A

Dec 90

V10.0

N/A

Jan 91

Sequence

Title

System Installation and Update
Installation/Update Notes
Installation Flag Files
2.1.1 N
Installation/Update Restrictions
RSTS/E Version 10.0 Installation Procedure
2.3.1 R
Restrictions
Cannot Mount Disks at the Beginning of the
2.3.2 R
Installation Procedure
Monitor Installation on Target Disk Uses
2.3.3 R
System Disk for Template
Online Monitor Installation Fails if Prebuilt
2.3.4 R
Monitor Chosen

Executive
Monitor Patches
DEASSIGN SYS Call Can Crash System
/3.1.1 M
- Mandatory Patch
Protection Violation Error When Issuing the
3.1.2 M
.RTS Directive - Mandatory Patch
Run-lime System May Become Permanent
3.1.3 M
- Mandatory Patch
Monitor Restrictions
DCl log File Corruption on Full Disk
3.3.1 R
Terminal Service Corrections
Changing Special login Terminal
3.4.1 F
Input Escape Sequence Handling
F
Host-Initiated LAT Connections May Crash System
3.4.3 M
- Mandatory Patch
Three Problems in Terminal Service - Mandatory Patch
Problem with TECO Mode - Mandatory Patch
M
. }.4.6 M
Inappropriate Character Echoing - Mandatory Patch
Private Delimiters Cause Problems with
1/3.4.7 M
Command Recall - Mandatory Patch
Characters lost When Data Error Received
M
- Mandatory Patch
Command Recall May Crash System
M
- Mandatory Patch
Forced Characters Echoed Even Under NOECHO
/s.4.10 M
- Mandatory Patch
Problem Processing Escape Sequences as Type Ahead
{3.4.11 M
- Mandatory Patch
Host-Initiated Connections to Some Servers May Fall
3.4.12 M
- Mandatory Patch
Problem with Echo Control Mode - Mandatory Patch
3.4.13 M

..J3.4.2

~.4.4M
?s.4.5

Terminal Service Notes
Modem Support on RSTS/E
3.5.1 N
Unexpected Abort from Captive Command File Will Not
3.5.2 N
Hang Up Dialup Line
File Processor Patches
Attaching to a Detached Job May Crash System
/3.7.1 M
- Mandatory Patch
Dynamic Region Creation Can Crash System
/3.7.2 M
- Mandatory Patch

RSTS/E Software Dispatch, June 1992

RSTS/E Version 10.0 Cumulative Index

/Sequence
3.7.3 M

;?a.7.4
M
3.7.5 M
A.7.s M
1!V 3.7.7 M

TItle

Released

Corrected MonlYr

Previous System Logical Assignment Not Replaced
- Mandatory Patch
Spawned Job May Fail to Execute - Mandatory Patch
Characters May Not Echo When Setting Host
to VMS System - Mandatory Patch
System Hangs After Setting Terminal Width
- Mandatory Patch
Job's Private Memory Maximum Inforrect for
Spawned Logged-in Jobs - Mandatory Patch
Possible Memory Corruption - Mandatory Patch
File Utility Directive May Truncate File
- Mandatory Patch

V10.0

N/A

Apr 91

V10.0
V10.0

N/A
NJA

Apr 91
Jul91

V10.0

N/A

Aug 91

V10.0

N/A

Dec 91

V10.0
V10.0

N/A
N/A

Dec 91
Jun 92

3.7.8 M
3.7.9 M

Device Driver Corrections
Some TMSCP Operations May Retry Forever
3.10.1 M
- Mandatory Patch

V10.0

N/A

Nov 91

Device Driver Restrictions
DB/DR Driver May Log Errors for Wrong Unit
3.12.1 R
Swapping MSCPITMSCP Unit Numbers May Cause
3.12.2 R
Crash

V10.0
V10.0

N/A
N/A

Aug 90'
Aug 90'

V10.0
V10.0
V10.0
V10.0
V10.0
V10.0
V10.0

N/A
NJA
NJA
N/A
N/A
NJA
N/A

Aug 90'
Aug 90'
Aug 90'
Aug 90'
Aug 90'
Aug 90'
Jan 91

V10.0

N/A

Feb 91

V10.0

N/A

Feb 91

Optional BASIC-PLUS Features
The BASIC-PLUS DEBUG Facility
4.11.1 N
The BASIC-PLUS DUMP Facility
4.11.2 N
Enabling DUMP from Compiled Files for Nonprivileged
4.11.3 F
Users

V10.0
V10.0
V10.0

N/A
N/A
N/A

Aug 90·
Aug 90·
Aug 90'

System Flies
System File Restrictions
RESTORENERIFY/NOREPLACE Can Enter Infinite
S.2.1 R
Sleep State
BACKUPIIMAGE Failes to Maintain Pack Attributes
S.2.2 R

V10.0

N/A

Mar 91

V10.0

N/A

Oct 91

V10.0

N/A

Feb 91

V10.0

N/A

Mar 91

V10.0

N/A

Jun 91

V10.0

NJA

Jul91

BASIC-PLUS
BASIC-PLUS Patches
Special PRINT-USING Characters
4.1.1 F
Default SCALE Factor
4.1.2 F
Omitting SCALE Factor Warning Message
4.1.3 F
Default to NOEXTEND Mode
4.1.4 F
Immediate Mode from .BAS File
4.1.5 F
Disabling the CCL SYS Call
~4.1.SF
.
4.1.7 M
DATE% Is Now a Reserved Keyword
- Mandatory Patch
RAD% Is Now a Reserved Keyword
4.1.8 F
- BASIC-PLUS Feature Patch
BASIC-PLUS Notes
New BASIC-PLUS Function 4.2.1 N

RAD%

/system File Corrections
S.3.1 M
BACKUP Can Fail to Back Up Some File Data
- Mandatory Patch
BACKUPIlNITIALlZE Can Exit with Error
S.3.2M
- Mandatory Patch
BACKUPNERIFY=ONLY Rewinds Before Execution
/S.3.3 M
- Mandatory Patch
BACKUPIBUFFER_SIZE=OPTIMUM May Not Select
~S.3.4M
the Optimum Buffer Size - Mandatory Patch

RSTS/E Software Dispatch, June 1992

RSTS/E Version 10.0 Cumulative Index

Released

Corrected

Mon/Yr

V10.0

NlA

Jun 92

V10.0

NlA

Aug 90·

V10.0

N/A

May 91

V10.0

NlA

Aug 91 -

V10.0

NlA

Aug 90·

Error logging Package (ERROR$)
Package Restrictions
ANALYS Incorrectly Shows Virtual Disk as Locked Out
12.2.1 R

V10.0

N/A

Aug 90·

Operator Services and Spooling Package (OPSER$)
Package Notes
Notes on the Use of Serial Printers
14.1.1 N

V10.0

NlA

Aug 90·

Print/Batch Services Package (PBS$)
Package Notes
Notes on Ihe Use of Serial Printers
15.1.1 N

V10.0

NlA

Aug 90·

V10.0

NlA

Jun 92

V10.0
V10.0

NlA
NlA

Aug 90·
Aug 90·

Sequence
,/

/6.3.5M

Title
BACKUP May Sleep Indefinitely -

Mandatory Patch

RSTS/E Utilities
System Library ($)
Library Restrictions
10.2.1 R
PIP Sometimes Loops When Copying Files into
Themselves
LOGIN May Not Always Execute Your Group and User
10.2.2 R
LOGIN.COM

Ubrary Corrections
LOGIN May Not Always Execute Your Group and User
10.3.1 M
LOGIN.COM
Auxiliary Library (AUXLlB$)
Ubrary Restrictions
ODT Displays Large Addresses Incorrectly
11.2.1 R

Package Corrections
Changing Printer Forms May Disable PBS
15.3.1 M
Print Servers

RMS-11 V2.0 (RMS$)
Package Restrictions
RMS-11 Does Not Correctly Handle Underscores
22.2.1 R
RMS-11 May Incorrectly Report Error on Remote
22.2.2 R
Access of Indexed File
Run-Time Systems Support
Del Run-time System and Utilities
Package Notes
Attributes Are Lost When RMS File Is Copied 10 DOS
27.1.1 N
Format Tape
Exclamation Marks in BROADCAST Commands
27.1.2 N

V10.0

NlA

Aug 90·

V10.0

NlA

Aug 90·

Package Restrictions
MOUNT Command with IOVERRIDE Qualifier
27.2.1 R

V10.0

N/A

Aug 90·

V10.0

NlA

Jul91

V10.0

NlA

Jul91

;t;..ackage Corrections
27.3.1 M
Creating Global Symbols in Nested Command Files
/:
Can Cause an Unexpected Error - Mandatory Patch
27.3.2 M
Using F$SEARCH Can Cause an Unexpected Error
- Mandatory Patch

RSTS/E Software Dispatch, June 1992

RSTS/E Version 10.0 Cumuiative Index

RSX-11 Emulator and Utilities
Package Notes
28.1.1 N
Using the RSX-11 CRF Utility
Package Restrictions
28.2.1 R
RSX-11 Utilities Do Not Handle All RSTS/E File
Specifications

RT-11 Emulator and Utilities
Package Notes
29.1.1 N
Use of Underscore in RT-11 Utilities
Package Restrictions
29.2.1 R
Disk Unit Numbers Greater Than Nine May Not Be
Displayed Correctly

V1O.O

N/A

Aug 90'

V10.0

N/A

Aug 90'

V10.0

N/A

Aug 90'

V10.0

N/A

Aug 90'

V10.0

N/A

Aug 90 •

V10.0
V10.0

N/A
NlA

Aug 90 •
Aug 90'

V10.0
V10.0

N/A
N/A

Aug 90'
Aug 90'

N/A

May 91

N/A

Aug 90 +

N/A

Apr 91

N/A

Jan 91

Optional Software
DECnetiE Utilities V4.1 (DECNET$)
Package Restrictions
31.2.1 R
SET EXECUTOR SEGMENT BUFFER SIZE May Fail
Without Warning
SHOW NODE Command May Fail
31.2.2 R
31.2.3 R
Network Parameter File Will Not Hold More Than
26,000 Nodes
SET HOST May Give Erroneous Error Message
31.2.4 R
31.2.5 R
Network File Transfers May Not Correctly Preserve
Protection Codes

DECnetiE Utilities for RSTS/E Vi 0.0
DECnetiE Utilities Corrections
31.3.1 M
SHOW and LIST Commands Display Inappropriate
Information - Mandatory Patch

PDP-ii C Vi.0
33.0.1 N

Announcing PDP-11 C for RSTS/E V1.0

WPS-PLUS/RSTS
List Processing
34.1.1 N
List Processing Message 'No room left .. :

DATATRIEVE for RSTS/E Vi0.0
49.1.1 N

Instructions Missing in DATATRIEVE-11 V3.3
Installation Guide

RSTS/E Software Dispatch, June 1992

RSTS/E Version 10.0 Cumulative Index

Sequence

Title

Released

Corrected

Mon/Yr

N/A

NlA

Oct 91

V10.0

N/A

Apr 92-

FORTRANm
FORTRANJ77 Package Restrictions
57.2.1 R
IF-THEN-ELSE Statement Embedded Within
DO-LOOP Causes Infinite Loop - Restriction

BASIC-PLUS-2 for RSTS/E
Restrictions
79.1.1 R

SAVE, REPLACE, and LIST Sometimes Lose Lines
of Source Text - Restriction

RSTS/E Software Dispatch, June 1992

How to Order Additional Documentation

Technical Support
If you need help deciding which documentation best meets your needs, call 800-343-4040 before placing
your electronic, telephone, or direct mail order.

Electronic Orders
To place an order at the Electronic Store, dial 800-DEC-DEMO (800-332-3366) using a 1200- or 2400-baud
modem. If you need assistance using the Electronic Store, call 800-DIGITAL (800-344-4825).

Telephone and Direct Mail Orders
Your Location

Call

Contact

Continental USA,
Alaska, or Hawaii

800-DIGITAL

Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

Puerto Rico

809-754-7575

Local Digital subsidiary

Canada

800-267-6215

Digital Equipment of Canada
Attn: DECdirect Operations KA02/2
P.O. Box 13000
100 Herzberg Road
Kanata, Ontario, Canada K2K 2A6

International

Local Digital subsidiary or
approved distributor

Internal 1

USASSB Order Processing - WMOlE15
or

U.S. Area Software Supply Business
Digital Equipment Corporation
Westminster, Massachusetts 01473

lFor internal orders, you must submit an Internal Software Order Form (EN-01740-07).

)

Reader's Comments

RSTS/E Maintenance Notebook
AA-L997E-TC

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

I rate this manual's:
Accuracy (software works as manual says)
Completeness (enough information)
Clarity (easy to, understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

I would like to see more/less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

NamefI'itle

Dept.

Company

Date

Mailing Address
Phone

Do Not Tear - Fold Here and Tape - -

- -

- - -

- -

~ -

I
I
I
I
I
I
I
I

NO POSTAGE
NECESSARY
IF MAilED
IN THE
UNITED STATES

~DmDDmDTM

BUSINESS REPLY MAil
FIRST- CLASS MAIL PERMIT NO.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

I
I
I

DIGITAL EQUIPMENT CORPORATiON
CORPORATE USER PUBLICATIONS
CONTINENTAL BOULEVARD MK01-2/E12
PO BOX 9501
MERRIMACK NH 03054-9982

III, ,, " II ,II" , ,I,I, ,I" II ,I" I,I" I,I I, ,I I, ill, " I
_ _ _ _ _ _ _ _

Do Not Tear - Fold Here _ _ - _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ --j

I
I
I
i
I
I
I
I

IS
I~
I~

I~0r<
s·
(l)

Reader's Comments

RSTS/E Maintenance Notebook
AA-l997E-Te

I rate this manual's:
Accuracy (software works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

D
D
D
D
D
D
D
D

D
D
0
D
D
D
D
D

I would like to see morelless

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

Nametritle

Dept.

Company

Date

Mailing Address
Phone

Do Not Tear - Fold Here and Tape - -

- -

~DmDDmD ™

NO POSTAGE

N~~~~i~Y

UNITED STATES

BUSINESS REPLY MAIL
FIRST- CLASS MAil PERMIT NO.33 MAYNARD MASS.
POSTAGE WilL BE PAID BY ADDRESSEE

DIGiTAL EQUIPMENT CORPORATION
CORPORATE USER PUBLICATIONS
CONTINENTAL BOULEVARD MK01-2/E12
PO BOX 9501
MERRIMACK NH 03054-9982

III " ,,I II, II 01 , , I,I, I I,,II ,I, ,LI" I,,I,I , I,IIi I
Iii

_ _ _ _ _ _ _ _

Do Not Tear - Fold Here _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ~

c::
....

I ~.
i
I
I
I
I
I
I
I
I
I