Digital PDFs

AA-L997D-TC

June 1985

177 pages

Original

5.5MB

Document:	RSTS/E V9.0 Maintenance Notebook
Order Number:	AA-L997D-TC
Revision:	0
Pages:	177
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsts_e/V09/1_General_Information_and_Installation/AA-L997D-TC_RSTS_E_V9.0_Maintenance_Notebook_Jun85.pdf

OCR Text

RSTS/E
Maintenance Notebook
Order No. AA-L997D-TC

June 1985
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

V9.0

SOFTWARE VERSION:

RSTS/E

V9.0

digital equipment corporation, maynard, massachusetts

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

The postage-paid READER'S COMMENTS form on the last page of this
document requests your critical evaluation to assist us in preparing future
documentation.

The following are trademarks of Digital Equipment Corporation:

~D~DD~DTM
DEC
DECmail
DEC mate
DECnet
DECtape
DECUS
DECwriter

DIBOL
FMS-11
LA
MASSBUS
PDP
P/OS
Professional
Q-BUS
Rainbow

ReGIS
RSTS
RSX
RT
UNIBUS
VAX
VMS
VT
Work Processor

RSTS/E V9.0 Maintenance Notebook, June 1985
Table of Contents

Page iii

CONTENTS
Preface
1.0

Notebook Maintenance

2.0

RSTS/E Component.Subcomponent Assignments

3.0

Software Performance Reports

3.1
4.0

Software Performance Report Guidelines
Procedures for Updating RSTS/E Software

4.1

Monitor Patching

4.2

Commonly Used System Program (CUSp) Module Replacement

4.3

Commonly Used System Program (CUSp) Patching

4.4 Update Kits
4.4.1 Off-Line Patching
4.4.2 On-Line Patching
4.4.3 Optional Feature Patches
5.0

Software Product Descriptions (SPDs) and Option Bulletins

5.1

Software Product Descriptions (SPDs)

5.2

Option Bulletins

6.0
6.1

RSTS/E Articles
Cumulative Index of RSTS/E V9.0 Maintenance Notebook Articles

RSTS/E V9.0 Maintenance Notebook, June 1985
Introduction

Page v

Preface

The RSTS/E Maintenance Notebook is a maintenance notebook
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 V9.0. In general,
this
is a composite of all optional layered software articles previously
published for RSTS/E, which still apply to the product when run on
RSTS/E V9.0.
The RSTS/E Software Dispatch 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.
The RSTS/E Software Dispatch contains articles for RSTS/E and its
layered software.
Each month, you should take apart the RSTS/E
Software Dispatch and merge the new articles by sequence number in
your maintenance notebook.
All articles published are summarized in the Cumulative Index. There
is also an index of the version and edit levels for all the Commonly
Used System Programs (CUSPs). These indexes are updated as necessary
in the RSTS/E Software Dispatch.

RSTS/E V9.0 Maintenance Notebook, June 1985
Notebook Maintenance

1.0

Page 1-1

Notebook Maintenance

Each month you should take apart the RSTS/E Software Dispatch and
merge the new articles by sequence number in your notebook.
If an
article is a replacement, discard the supers~ded article.
Each
article addresses a single topic and its title glves the symptom or a
one-line problem description. This information appears at the top of
each page. For example:
RSTS/E Software Dispatch, Month year
RSTS/E V9.0
BASIC-PLUS
BASIC-PLUS Patches

Seq 4.1.4 F
1 of 2

DEFAULT TO NOEXTEND MODE - BASIC-PLUS FEATURE PATCH

The system components and subcomponents are listed in Section 2.0.
That list will be 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. 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,
an example being the "4.1.4" shown in the upper right corner of the
sample heading. Replacement articles are identified as such.
In
general,
articles
with
an
issue
number
of
zero
(component. subcomponent. 0) are provided to list problems corrected by
a replacement module for the affected component. These articles will
be superseded each time a new replacement module is issued for the
component.

RSTS/E V9.0 Maintenance Notebook, June 1985
Notebook Maintenance

Each article's sequence number will be followed
identifying the type of article, as explained below:

Page 1-2

letter,

M = Mandatory
These articles describe problems corrected by a replacement
module.
In some cases, these articles will 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
These articles include patches that extend or configure
non-standard capabilities into the product. These functions
will be 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

These
articles
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 V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
2.0

RSTS/E Component.Subcomponent Assignments

The component.subcomponent numbers outlined below appear
to be filed following Section 6.1 of this notebook.

RSTS/E MONITOR
0.0
0.1
0.2

RSTS/E V9.0 General Notes
System Notes
System Management Guidelines

1.0
1.1
1.2

Initialization
INIT.SYS Program Patches
INIT.SYS Program Notes

2.0
2.1
2.2
2.3
2.4
2.5

System Installation and Update
Installation/Update Notes
Installation/Update .COM files
BPLGEN.SAV
BUFCHK.TSK
SYSGEN.SAV

3.0
3.1

Monitor
Monitor Patches
Monitor Notes
Terminal Service Patches
Terminal Service Notes
File Processor Patches
File Processor Notes
Device Driver Patches
Device Driver Notes
FMS Monitor Patches
FMS Monitor Notes

3.2
3.3
3.4
3.5

3.6
3.7
3.8
3.9
3.10

4.0
4.1

4.2
4.3
4.4
4.5
4.6
4.7
4.8

4.9
4.10

Page 2-1

BASIC-PLUS
BASIC-PLUS Patches
BASIC-PLUS Notes
Programming Hints
Math Packages
Matrix Functions
PRINT-USING
Record I/O
Virtual Core
String Arithmetic
Non-Standard BASIC-PLUS Features

articles

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
5.0
5.1
5.2

RSTS/E 2780 Device Driver
RSTS/E 2780 Device Driver Patches
RSTS/E 2780 Device Driver Notes

6.0
6.1
6.2

System Files
System Files Notes
BACKUP.TSK
CSPLIB.LIB
ERR. ERR
INIT.SYS
LOGIN.COM
RECOVR.COM
START. COM
SYSGEN.SIL
SYSINI.COM

6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
7.0
7.1
7.2

7•3
7.4
7.5
7.6

7.7
7.8
7.9

DECnet/E Monitor Package V2.1
Package Notes
DECNET.OBJ
NSPSUB.OBJ
NSP.OBJ
NET.OBJ
TRN.OBJ
SES.OBJ
XDDVR.OBJ
XDDINT.OBJ
RSTS/E UTILITIES

8.0
8.1
8.2

Help Package (HELP$)
Package Notes
HELP.TSK

9.0
9.1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
9.9
9.10
9.11

TECO Package (TECO$)
TECO Notes
TECO.RTS
TECO.TEC
VTEDIT.TEC
TECO.INI
TYPE.TEC
SQU.TEC
LOCAL.TEC
TECKBM.TEC
SEARCH.TEC
TECO.DOC

Page 2-2

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
System Library ( $ )
10.0
Library Notes
10.1
ACTMGR.TSK
10.2
ATPK.TSK
10.3
10.4
DIRECT.TSK
DSKINT.TSK
10.5
10.6
FILCOM.TSK
LOGIN.TSK
10.7
10.8
LOGOUT.TSK
MAKSIL.TSK
10.9
10.10 ONLPAT.SAV
10.11 REORDR.TSK
10.12 SHUTUP.TSK
10.13 SWITCH.TSK
10.14 SYSTAT.TSK
10.15 TERMGR.TSK
10.16 UTLMGR.TSK
Auxiliary Library (AUXLIB$)
11.0
Package Notes
11.1
11.2
BPCREF.TSK
BPCRFl.TSK
11.3
COPY.TSK
11.4
DISPLY.TSK
11.5
DSKCVT.TSK
11.6
11.7
FIT.TSK
FLINT.TSK
11.8
GRIPE.TSK
11.9
11.10 ODT.TSK
11.11 PMDUMP.TSK
11.13 RUNOFF.TSK
11.14 TALK.TSK
Error Control Package (ERROR$)
12.0
Package Notes
12.1
ANALYl.TSK
12.2
ANALY2.TSK
12.3
ANALY3.TSK
12.4
ANALYS.TSK
12.5
ERRCPY.TSK
12.6
ERRDAT.FIL
12.7
ERRDET.TSK
12.8
ERRDIS.TSK
12.9
12.10 ERRINT.TSK
12.11 MSCPER.FIL

Page 2-3

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
RESTOR Package (RESTOR$)
13.0
Package Notes
13.1
BACCOM.TSK
13.2
BACCON.TSK
13.3
BACDIR.TSK
13.4
13.5
BACDSK.TSK
13.6
BACENT.TSK
BACFRM.TSK
13.7
13.8
BACLAB.TSK
BACLOD.TSK
13.9
13.10 BACLST.TSK
13.11 BACMNT.TSK
13.12 BACKUP.PRM
13.13 RESTOR.TSK
Operator Services and Spooling Package (OPSER$)
14.0
14.1
Package Notes
14.2
BATCH.DCD
BATCH.TSK
14.3
BATDCD.TSK
14.4
BATDEC.TSK
14.5
BATIDL.TSK
14.6
14.7
BATRUN.TSK
14.8
CHARS.QUE
OPSER.TSK
14.9
14.10 OPSRUN.TSK
14.11 PLEASE.TSK
14.12 QUE.TSK
14.13 QUEMAN.TSK
14.14 QUMRUN.TSK
14.15 SPLIDL.TSK
14.16 SPLRUN.TSK
14.17 SPOOL.TSK
15.0
15.1
15.2
15.3
15.4
15.5

Print/Batch Services Package (PBS$)
Package Notes
FORMS.SYS
PBS.TSK
PBSMGR.TSK
QUE.SYS

Page 2-4

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
Unsupported Package (UNSUPP$)
16.0
Package Notes
16.1
BPDA.TSK
16.2
B2CREF.TSK
16.3
CONNEC.TSK
16.4
DIALER.TSK
16.5
DSKDMP.TSK
16.6
DUMP.TSK
16.7
EMTCPY.TSK
16.8
FLOAT.TSK
16.9
16.10 LQSTAT.TSK
16.11 MEMORY.TSK
16.12 MONEY.TSK
16.13 QSTATS.TSK
16.14 RNO.TSK
16.15 RSTSFL.OBJ
16.16 SRCCOM.SAV
16.17 STATUS.TSK
16.18 VT55.TSK
17.0
17.1
17.2
17.3
17.4
17.5
17.6
17.7

Layered Product Update Package (UPDATE$)
Package Notes
AUTOED.TSK
BUILD.TSK
CPATCH.TSK
CSPCOM.TSK
CSPCOM.OLB
UTILTY.TSK

Device Test Pack~ge (TEST$)
18.0
Package Notes
18.1
CPEXER.TSK
18.2
CPUTST.TSK
18.3
DDEXER.TSK
18.4
DSKSEK.TSK
18.5
DTEXER.TSK
18.6
18.7
DXEXER.TSK
DSKEXR.TSK
18.8
KBEXER.TSK
18.9
18.10 LPEXER.TSK
18.11 MTEXER.TSK
18.12 PPEXER.TSK
18.13 PREXER.TSK

Page 2-5

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments

Page 2-6

RSTS/E DOCUMENTATION
19.0
Documentation
19.1
RSTS/E Documentation Directory
19.2
RSTS/E V9.0 Release Notes
19.3
RSTS/E V9.0 Maintenance Notebook
19.4
RSTS/E System Installation and Update Guide
19.5
RSTS/E System Manager's Guide
19.6
RSTS/E System User's Guide
19.7
RSTS/E Guide to Writing Command Procedures
19.8
RSTS/E Utilities Reference Manual
19.9
Introduction to the EDT Editor
19.10 PDP-II SORT/MERGE User's Guide
19.11 RSTS/E RUNOFF User's Guide
19.12 EDT Editor Manual
19.13 RSTS/E Task Builder Reference Manual
RSTS/E Task Builder Reference Manual Update
19.14 RSTS/E Programmer's Utilities Manual
RSTS/E Programmer's Utilities Manual Updatel
RSTS/E Programmer's Utilities Manual Update2
19.15 RSTS/E RTl1 Utilities Manual
19.16 PDP-II TECO User's Guide
19.17 BASIC-PLUS Language Manual
19.18 RSTS/E Programming Manual
19.19 RSTS/E System Directives Manual
19.20 IAS/RSX-II ODT Reference Manual
19.21 PDP-II MACRO-II Language Reference Manual
PDP-II MACRO-II Language Reference Manual Update
19.22 RSTS/E RMS-ll MACRO Programmer's Guide
19.23 RSTS/E RMS-ll: An Introduction
19.24 RSTS/E RMS-ll User's Guide
19.25 RSTS/E RMS-ll Utilities Manual
19.26 RSTS/E Quick Reference Guide
19.27 Introduction to BASIC
19.28 EDT Quick Reference Guide

AA-2642G-TC
AA-5246G-TC
AA-L997D-TC
AA-2669H-TC
AA-2762F-TC
AA-EZI2A-TC
AA-CF03A-TC
AA-EZI1A-TC
AA-K443A-TC
AA-CI67A-TC
AA-3337B-TC
AA-M476A-TK
AA-5072C-TC
AD-5072C-Tl
AA-D749A-TC
AD-D749A-Tl
AD-D749A-T2
AA-M213A-TC
AA-K420B-TC
AA-2623D-TC
AA-EZ09A-TC
AA-EZI0A-TC
AA-M507A-TC
AA-V027A-TC
AD-V027A-Tl
AA-P507A-TC
AA-P508A-TC
AA-P510A-TC
AA-P509A-TC
AA-EZI3A-TC
AA-0155B-TK
AA-M477A-TK

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
RUN-TIME SYSTEMS SUPPORT
20.0
20.1
20.2
20.3
20.4

DCL Run-time System and utilities
Package Notes
DCL.RTS
DCLUTL.TSK
PRELIN.TSK

21.0
RSX Run-time System and Utilities
21.1
Package Notes
21.2
CRF.TSK
LBR.TSK
21.3
MAC.TSK
21.4
21.5
PAT.TSK
21.6
RSX.RTS
21.7
RSXMAC.SML
STK.TSK
21.8
SYSLIB.OLB
21.9
21.10 TKB.TSK
RT-11 Run-time System and Utilities
22.0
22.1
Package Notes
CREF.SAV
22.2
HOOK.SAV
22.3
22.4
LIBR.SAV
22.5
LINK.SAV
MACRO.SAV
22.6
22.7
ONLPAT.SAV
22.8
PAT.SAV
22.9
PIP.SAV
22.10 RT11.RTS
22.11 SAVRES.SAV
22.12 SILUS.SAV

Page 2-7

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
OPTIONAL SOFTWARE
23.0
23.1

EDT V3.0
Package Notes

24.0

(Reserved)

25.0
25.1
25.2
25.3

RSTS/E 2780 Package V3.0
Package Notes
RJ2780
RSTS/E 2780 User's Guide (DEC-11-0RJEA-B-D)

26.0

(Reserved)

27.0
27.1

FMS-11 Vl.5
Package Notes

28.0

(Reserved)

29.0

(Reserved)

30.0

(Reserved)

•

Page 2-8

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
DECnet/E Utilities V2.1 (DECNET$)
31.0
Package Notes
31.1
DTRECV.TSK
31.2
DTSEND.TSK
31.3
31.4
EVTLOG.TSK
FAL.TSK
31.5
31.6
LSN.TSK
MIRROR.TSK
31.7
NCP.TSK
31.8
31.9
NCUCVT.TSK
31.10 NET.TSK
31.11 NFT.TSK
31.12 NETCPY.TSK
31.13 NETCVT.TSK
31.14 NETFNC.BAS
31.15 NETMLB (.MLB and .SML)
31.16 NETOFF.TSK
31.17 NETPAT.SAV
31.18 NETSLP.TSK
31.19 NPKDVR.TSK
31.20 TLK.TSK
32.0
32.1
32.2
32.3
32.4
32.5
32.6
32.7
32.8

DECnet/E V2.l Documentation
DECnet/E V2.1 Release Notes
DECnet/E V2.0 System Manager's Guide
DECnet/E V2.0 Network Programming in BASIC-PLUS and
BASIC-PLUS-2
DECnet/E V2.0 Network Programming in MACRO
DECnet/E V2.0 Network Programming in FORTRAN
DECnet/E V2.0 Network Programming in COBOL
DECnet/E V2.0 System User's Manual
DECnet/E V2.0 Installation Manual

33.0

(Reserved)

34.0

(Reserved)

35.0

(Reserved)

36.0
36.1

DECmail-11 V2.0
Package Notes

37.0

(Reserved)

38.0

(Reserved)

39.0

(Reserved)

40.0
40.1

RPG V8.8
Package Notes

41.0

(Reserved)

Page 2-9

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments

Page 2-10

42.0

(Reserved)

43.0

(Reserved)

44.0

(Reserved)

45.0
45.1

DECdx/RSTS Vl.0
Package Notes

46.0
46.1

INDENT Vl.4
Package Notes

47.0
47.1

ADE V2.4
Package Notes

48.0
48.1

BASIC-PLUS-2 V2.3
Package Notes

49.0
49.1

DATATRIEVE-l1 V3.1
Package Notes

50.0
50.1
50.2
50.3
50.4

KMC Drivers and Utilities
Package Notes
IBM Interconnect (II) Driver
KMCll (XK) Driver
KMCUT

51.0
51.1
51.2
51.3
51.4
51.5
51.6

RSTS/E 3271 Protocol Emulator V2.l
Package Notes
(Reserved)
3271 Microcode (CRAM)
3271 Microcode (RAM)
MTO
RSTS/E 3271 Protocol Emulator V2.1 Release Notes
(AA-H474C-TC)
RSTS/E 3271 Protocol Emulator User's Guide (AA-D365A-TC)
DIBOL Interface

51.7
51.8
52.0
52.1
52.2
52.3
52.4
52.5
52.6
52.7
52.8
53.0
53.1

RSTS/E High Performance 2780/3780 Emulator Vl.l
Package Notes
2780 Microcode (CRAM)
2780 Microcode (RAM)
3780 Microcode (CRAM)
3780 Microcode (RAM)
RJESPL
RSTS/E 2780/3780 High Performance Emulator Vl.l Release
Notes (AA-J458B-TC)
RSTS/E High Performance 2780/3780 Emulator User's Guide
(AA-J177A-TC)
SORT/MERGE V3.0
Package Notes

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
54.0
54.1

ADE V2.3
Package Notes

55.0
55.1

FORTRAN IV V2.6
Package Notes

56.0
56.1

COBOL-81 V2.3
Package Notes

57.0
57.1

FORTRAN-77 V5.0
Package Notes

58.0
58.1

FORTRAN-77 DEBUG Vl.0
Package Notes

59.0

(Reserved)

60.0
60.1

Message Router Vl.0
Package Notes

61.0

(Reserved)

62.0
62.1

PLXY-ll Vl.3
Package Notes

63.0

(Reserved)

64.0

(Reserved)

65.0

(Reserved)

66.0
66.1

PRO IV Vl.0
Package Notes

67.0

(Reserved)

68.0
68.1

MENU-ll V2.0
Package Notes

69.0
69.1

DECword/DP Vl.2
Package Notes

70.0
70.1
70.2
70.3

COBOL-ll V4.4
Package Notes
COBOL Compiler - NON-CIS
COBOL Compiler - CIS

71.0
71.1
71.2

OMS-500 V2.1
Release Notes
DMS-500 User's Guide

Page 2-11

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments

Page 2-12

These are the component numbers for the ISAM and RAM package:
71.3
71.4
71.5
71.6
71.7
71.8
71.9
71.10
71.11
71.12
71.13
71.14
71.15
71.16
71.17
71.18

DMSFSS.BAS
DMSISO.BAS
DMSRAO.BAS
DMSISR.BAS
DMSISC.BAS
DMSRAR.BAS
DMSISA.BAS
DMSRAA.BAS
DMSFSU.BAS
DMSFSX.BAS
DMSUTL.BAS
IAMGEN.BAS
IAMCRI.BAS
IAMDMP.BAS
IAMVFY.BAS
IAMFNS.BAS

These are the component numbers for the DSORT package:
71.19
71.20
71.21
71.22
71.23
71.24
71.25

DSORT.BAS
DSORTD.BAS
DSORTF.BAS
DSORTX.BAS
DSORTS.BAS
DSORTM.BAS
DSORTO.BAS

72.0

(Reserved)

73.0
73.1

DIBOL V5.1A
Package Notes

74.0

(Reserved)

75.0
75.1

RMS-l1 V2.0
Package Notes

76.0
76.1

DIBS-11/CTS500 Vl.0
Package Notes

77.0

(Reserved)

78.0

(Reserved)

79.0

(Reserved)

80.0

(Reserved)

81.0
81.1

DECgraph-ll Vl.2
Package Notes

RSTS/E V9.0 Maintenance Notebook, June 1985
Component.Subcomponent Assignments
82.0

(Reserved)

83.0

(Reserved)

84.0

(Reserved)

85.0

(Reserved)

90.0
90.1

User Assigned Components - For Development Use
Package Notes

91.0

User Assigned Components - For User Use

to
99.0

Page 2-13

RSTS/E V9.0 Maintenance Notebook, June 1985
Software Performance Reporting (SPRs)

3.0

Page 3-1

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
installation and may be continued by subscription thereafter.
3.1

after

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, the
should be included with the SPR:

following

A complete description of the problem.

The CPU type.

The system disk type.

The amount and type of memory_

If possible, a simple program or procedure which can be
used to reproduce the problem.

Any additional
relevant.

information

For problems associated with
package (ANALYS), also include:

the

which

you

may

think

RSTS/E monitor or crash analysis

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
magnetic tape) of your monitor and CRASH.SYS file.
Your
media will be returned with your SPR answer.

RSTS/E V9.0 Maintenance Notebook, June 1985
Software Performance Reporting (SPRs)

Page 3-2

When submitting an SPR concerning a DIGITAL-supplied
also include:

utility

(CUSp),

The name of the CUSP.

2•

A "RUN" of the CUSP which displays the header line,
version number, and the problem which is occurring,
if
possible.

A list of any optional feature patches installed.

Whether the program runs under BASIC-PLUS (.BAC version)
or RSX (.TSK version).

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

A complete listing of the CUSP (preferably on magnetic
tape) if your installation has made any non-standard
changes.

Listings of all relevant input and output files.

the

account(s)

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 V9.0 Maintenance Notebook, June 1985
Procedures for Updating RSTS/E Software

4.0

Page 4-1

Procedures for Updating RSTS/E Software

This section briefly describes the updating procedures to be used for
maintenance of RSTS/E V9.0.
The procedures to be followed for
updating the monitor and system programs when installing a new RSTS/E
system are described in the RSTS/E System Installation and Update
Guide. The procedures for updating the software as part of normal
system maintenance are described in the RSTS/E System Manager's Guide.
Most corrections to RSTS software are done by replacing the affected
components with updated versions distributed on the next release of
RSTS/E (V9.1,
V9.2,
etc.).
These
replacement
modules
are
automatically installed as part of the RSTS installation and update
process.
In cases where a critical problem is discovered, DIGITAL will publish
an article in the RSTS/E Software Dispatch describing the problem and
suggesting possible work-arounds until the module is replaced in the
next V9 update release.
If no reasonable work-arounds are available,
a patching procedure will be included in the article so you can
correct the defective module.
Step-by-step instructions on how to
apply the patch will be included.
Unless otherwise stated, Mandatory patches published in the RSTS/E
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 will describe how the patch will fail if
it does not apply to your system.
Be sure to file and maintain all 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 Dispatch articles may include "Feature" patches, allowing you to
modify a component to enable an optional feature of that component.
These Feature patches are optional and are 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).

RSTS/E V9.0 Maintenance Notebook, June 1985
Procedures for Updating RSTS/E Software
4.1

Page 4-2

Monitor Patching

Normally, problems discovered in a RSTS/E 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 RSTS/E 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/E Software Dispatch article describing the
problem will also explain how to apply the patch.
Normally,
changes
to the RSTS/E monitor are made using the off-line PATCH option of
INIT.SYS or the on-line program $ONLPAT.SAV. General descriptions of
these patching tools and how to use them are included in the RSTS/E
System Installation and Update Guide and the RSTS/E System Manager's
Guide.
The patching article will include specific instructions on how to
apply the patch. The expected dialogue will be shown in the article
as it should appear when you install the patch.
If any deviation
occurs, you should immediately:

4.2

Halt the patching process

Restore any changes already made to their former values

Determine where the discrepancy occurred

Commonly Used System Program (CUSp) Module Replacement

Like the monitor, corrections to individual RSTS/E programs are made
by replacing the defective module with a replacement from the V9.0
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 RSTS/E installation kit,
then that
module will replace the copy of HELP.TSK on your system whenever you
install or update the HELP package.
Note that you no longer need to copy replacement modules for the
RSTS/E CUSPs to disk with PATCPY before beginning the installation or
update.
All replacement
modules
for
bundled
software
will
automatically be applied whenever you install or update your RSTS/E
software.

RSTS/E V9.0 Maintenance Notebook, June 1985
Procedures for Updating RSTS/E Software
4.3

Page 4-3

Installation Kits

RSTS/E Installation Kits contain the minimal software necessary to
create a RSTS/E system, as well as replacement modules and/or patches
for software supported under RSTS/E V9.0. The RSTS/E V9.0 Installation
Kit contains all patches published in the RSTS/E V9.0 Maintenance
Notebook and in the RSTS/E V9.0 Software Dis atch Review.
Each
subsequent RSTS/E Installation Kit V9.1, V9.2, etc. will contain all
of the components from the previous installation kit, plus any new
modules and/or patches published in the RSTS/E Software Dispatch.
Thus, you only need the most recent RSTS/E installation kit to update
your system to the current revision level.
Note that in some cases, patches previously published in the RSTS/E
Software Dispatch will become obsolete, since the correction provided
by the patch will be included in the replacement module itself.
In
such cases, a new Dispatch article will be published to supersede the
previous patch article.
The cumulative index published in the RSTS/E Software Dispatch will
indicate which installation kit (V9.0, V9.l, etc.) first contained a
patch or module replacement.
Procedures for using the installation kit to update standard RSTS/E
software can be found in the RSTS/E System Installation and Update
Guide. Procedures for updating optional layered software are usually
found in the appropriate installation manual for the product.

RSTS/E. V9.0 Maintenance Notebook, June 1985
Procedures for Updating RSTS/E Software
4.4

Page 4-4

Patches and Replacement Modules for Optional Layered Products

The RSTS/E V9.0 Installation Kit also contains patches and replacement
modules for optional layered products.
Information on how to update
layered products will be included with each installation kit in the
file UPDATE.DOC.
This file is automatically copied to the UPDATE$
account on your system whenever you install the UPDATE package during
a system installation or update. Be sure to read the information in
the UPDATE.DOC file before updating any RSTS/E layered product.
Note that PBUILD is no longer included with RSTS/E. To update those
layered products that used PBUILD in the past, you must now mount the
original layered product distribution kit and use the BUILD/PATCH or
PATCH option of BUILD.TSK.
To 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 now required for both disk and tape installation
kits.
To
transfer layered product update components from the RSTS/E
installation kit to the PATCH$ account, perform either of these steps:
1. During the installation procedure, type "YES" to the prompt:
Do you want to transfer the layered
components from the Installation kit?

product update

2. Invoke the DCL "copy update" command procedure by
DCL command line:

typing

the

$ @[O,l]COPYUP "package name"
where "package
want to update.

name"

is the name of the layered product you

For more information on updating a layered product, please read the
file UPDATE$:UPDATE.DOC included with the UPDATE package on all RSTS/E
V9.0 Installation Kits.

RSTS/E V9.0 Maintenance Notebook, June 1985
SPDs and Option Bulletins

5.0

5.1

Page 5-1

Software Product Descriptions (SPDs)
and
Option Bulletins

Software Product Descriptions (SPDs)

Periodically, new or revised Software Product Description (SPD)
bulletins will appear in the RSTS/E Software Dispatch for various
software.products marketed by DIGITAL. This section of the notebook
is provided as a convenient place to file these SPDs for future
reference.
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
right hand side of the PRODUCT NAME:
line.

far

Note that the last part of the SPD number is the revision level, with
o being assigned for original issues of SPDs.

5.2

Option Bulletins

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

RSTS/E V9.0 Maintenance Notebook, June 1985
RSTS/E Articles

6.0

Page 6-1

RSTS/E Articles

Section 6.0 is the repository for all RSTS/E articles.
This section
will
include
problem
solutions,
optional
"Feature" patches,
documentation errata, programming hints, and tips for better operation
of RSTS/E.
Anyone who installs a RSTS/E system (whether on-line 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 sub-sections are added and updated.
The section which follows is an index to all articles included in the
original RSTS/E Maintenance Notebook.
This index will be updated
monthly as new articles are published in the RSTS/E Software Dispatch.

RSTS/E V9.0 Maintenance Notebook, June 1985
Cumulative Index of All Articles
6.1

Page 6-2

Cumulative Index of RSTS/E V9.0 Maintenance Notebook Articles
Sequence

Component
RSTS/E MONITOR
RSTS/E V9.0 GENERAL NOTES
System Notes
RSTS/E V9.0 COMPONENT SUMMARY
ANNOUNCING RSTS/E V9.0

0.1.1 N
0.1.2 N

System Management Guidelines
USING SAVE/RESTORE ON A TWO-DISK SYSTEM

0.2.1 N

Initialization
INIT.SYS Program Notes
DEVICES WITH NON-STANDARD UNIBUS ADDRESSES AND VECTORS

1.2.1 N

Monitor
Monitor Patches
DISABLING THE USE OF DATA SPACE

3.1.1 F

Terminal Service Patches
CHANGING SPECIAL LOGIN TERMINAL
INPUT ESCAPE SEQUENCE HANDLING

3.3.1 F
3.3.2 F

Terminal Service Notes
UNDERSTANDING TERMINAL PARITY AND STOP BIT SETTINGS
MODEM CONTROL ON PRIVATE, LEASED LINES

3.4.1 N
3.4.2 N

File Processor Patches
CONTROLLING EMT LOGGING

3.5.1 F

Device Driver Patches
USING THE CSS PAPER TAPE READER ON RSTS/E

3.7.1 F

BASIC-PLUS
BASIC-PLUS Patches
SPECIAL PRINT-USING CHARACTERS
DEFAULT SCALE FACTOR
OMITTING SCALE FACTOR WARNING MESSAGE
DEFAULT TO NOEXTEND MODE
IMMEDIATE MODE FROM .BAS FILE
NO PPN'S IN CATALOG COMMAND
DISABLING THE CCL SYS CALL
CLEAR I/O BUFFERS USED BY OPEN STATEMENTS
FORCE "ILLEGAL STATEMENT" ERROR WHEN USING OBSOLETE
SEND/RECEIVE

4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.1.7
4.1.8

F
F
F
F
F
F
F
M

4.1.9 F

RSTS/E V9.0 Maintenance Notebook, June 1985
Cumulative Index of All Articles

Non-Standard BASIC-PLUS Features
THE BASIC-PLUS DEBUG FACILITY
THE BASIC-PLUS DUMP FACILITY
CHANGING THE BASIC-PLUS DEBUG KEYWORDS
ENABLING THE BASIC-PLUS DUMP FEATURE
ENABLING DUMP FROM COMPILED FILES FOR NON-PRIVILEGED USERS
CHANGING THE BASIC-PLUS D?MP KEYWORD

Page 6-3

4.10.1
4.10.2
4.10.3
4.10.4
4.10.5
4.10.6

N
N
F
F
F
F

RSTS/E 2780 DEVICE DRIVER
2780 Device Driver Patches
BUFFER LIMIT CHECKING
DISCONNECT COMMAND HANDLING
DP11 TRANSMIT HANG CONDITION
DU11/DP11 TRANSMIT HANG CONDITIONLOSS OR DUPLICATION OF DATA
DOUBLE CLOSE ALTERS MONITOR
GET/PUT INTERLOCK PROBLEM
2780 HANDLER FAILURE PROBLEM
LOCAL BINARY TRANSMIT PROBLEM

5.1.1 M
5.1.2 M
5.1.3 M
5.1.4 M
5.1.5 M
5.1.6 M
5.1.7 M
5.1.8 M
5.1.9 M

2780 Device Driver Notes
INSTALLING AND TROUBLE-SHOOTING 2780'S

5.2.1 N

RSTS/E UTILITIES
Error Control Package (ERROR$)
Package Notes
UNDERSTANDING "PA MEMORY SYSTEM" ERROR LOGS

12.1.1 N

Operator Services and Spooling Package (OPSER$)
Package Notes
NOTES ON USE OF THE SERIAL LA180 (LA180S) TERMINAL
USING TWO OR MORE PRINTERS TO SERVE A QUEUE

14.1.1 N
14.1.2 N

RUN-TIME SYSTEMS SUPPORT
DCL
Package Notes
FILE SPECIFICATIONS IN DCL
SETTING UP THE DeL LINK COMMAND

20.1.1 N
20.1.2 N

RSTS/E V9.0 Maintenance Notebook, June 1985
Cumulative Index of All Articles

Page 6-4

RSX Utilities
Package Notes
USING RTSODT FOR DEBUGGING RUN-TIME SYSTEMS

21.1.1 N

CRF.TSK
USING THE RSX CRF UTILITY

21.2.1 N

RT-l1 Run-time System and Utilities
Package Notes
USE OF UNDERSCORE IN RTl1 EMULATOR UTILITIES
USING RTSODT FOR DEBUGGING RUN-TIME SYSTEMS

22.1.1 N
22.1.2 N

HOOK.SAV
NOTES ON HOOK.SAV

22.3.1 N

OPTIONAL SOFTWARE
RSTS/E 2780 PACKAGE V3.0
RJ2780
FAILURE TO CLEAR 'JOB ACTIVE' ON ATTACH
LOCAL BINARY TRANSMIT FAILURE

25.2.1 M
25.2.2 M

RSTS/E Maintenance Notebook, June 1985

Seq 0.1.1 N

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

1 of 11

RSTS/E V9.0 COMPONENT SUMMARY
This table lists all of the software components included with RSTS/E
V9.0.
It does not include 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 current version/edit level,
its
standard protection code, and its expected location on your system.
Note that file protection codes playa 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.
This article will be superseded whenever a component is added, deleted
or replaced in a later release of RSTS/E.
System Installation and Update
Component

Edit

Prot

Location
--------

BPLGEN.SAV
BUFCHK.TSK
COPYUP.COM
INSTAL. COM
SYSGEN.SAV
UPDATE.COM

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

<124>
<124>
<104>
<104>
<124>
<104>

SYSGEN$:
[0,1J

Edit

Prot

Location

SYSGEN$:
SYSGEN$:
[0,1J

[O,lJ

System Files
Component

--------

BACKUP.TSK
CSPLIB.LIB
ERR
.ERR
INIT .SYS
LOGIN .COM
RECOVR.COM
START .COM
SYSGEN.SIL
SYSINI.COM

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

<104>
<60>
<40>
<60>
<104>
<124>
<124>
<60>
<124>

[[°°,,11 JJ
[0,1J
[0,1J
[0,1J
[0,1J
[0,1J
[0,1J
[0,1J

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.1 N
2 of 11

HELP
Prot

Component
---------

Edit

HELP

V9.0-14
V9.0-14

<232>
<40>

HELP$:
HELP$:

Edit

Prot

Location

.TSK
.HLP

Location
--------

TECO
Component

--------

---------

CRTRUB.MAC
CRTRUB.OBJ
FMTMAC.TEC
FMTMAC.TES
GEXIT .OBJ
LOCAL .TEC
LOCAL .TES
SCREEN.OBJ
SCRINS.OBJ
SCROLL.OBJ
SEARCH.TEC
SEARCH.TES
SQU
.TEC
SQU
.TES
TECKBM.TEC
TECKBM.TES
TECO .DOC
TECO . INI
TECO .RTS
TECO .TEC
TECO .TES
TECOIN.TES
TECOLB.OBJ
TECORN.DOC
TYPE .TEC
TYPE .TES
VTEDIT.DOC
VTEDIT.TEC
VTEDIT.TES

V39.00
V39.00
V39.00
V39.00
V9.0-39
V39.00
V39.00
V39.00
V39.00
V39.00
V39.00
V39.00
V39.00
V39.00
V40
V03.00
V40.00
V40.00
V40.00
V03.00
V40
V39.00
V39.00
V39.00
V39.00
V39.00

<60>
<60>
<104>
<40>
<60>
<104>
<40>
<60>
<60>
<60>
<104>
<40>
<104>
<40>
<104>
<40>
<40>
<40>
<60>
<104>
<40>
<40>
<60>
<40>
<104>
<40>
<40>
<104>
<40>

TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$ :
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$ :
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:
TECO$:

RSTS/E Maintenance Notebook, June 1985

Seq 0.1.1 N

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

3 of 11

System Library
Component

Edit

Prot

Location

ACTMGR.TSK
ATPK . TSK
AUTOED.TSK
BUILD .TSK
COMMON. MAC
CPATCH.TSK
CSPCOM.TSK
DIRECT.TSK
DSKINT.TSK
ERR
.STB
FILCOM.TSK
LOGIN .TSK
LOGOUT.TSK
MAKSIL.TSK
ONLCLN.TSK
ONLPAT.SAV
PIP
.SAV
PLEASE.TSK
QUE
.TSK
REORDR.TSK
SAVRES.SAV
SHUTUP.TSK
SWITCH.TSK
SYSTAT.TSK
TERMGR.TSK
UTILTY.TSK
UTLMGR.TSK

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

<232>
<232>
<124>
<124>
<40>
<124>
<124>
<232>
<124>
<40>
<104>
<232>
<232>
<104>
<232>
<104>
<232>
<232>
<232>
<124>
<124>
<232>
<232>
<232>
<232>
<124>
<232>

[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1, 2]
[1, 2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]
[1,2]

(see note 1)
(see note 1)
(see note 1)
(see note 1)

(see note 2)
(see note 2)

(see note 1)

Note 1
These programs are "dispatcher" programs that chain to
the actual program located in the UPDATE$ account.
Note 2
These programs are "dispatcher" programs that chain
the actual program located in the OPSER$ account.

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.1 N
4 of 11

Auxiliary Library
Component

Edit

Prot

BPCREF.TSK
BPCRFl.TSK
COPY .TSK
DISPLY.TSK
DSKCVT.TSK
FIT
.TSK
FLINT .TSK
GRIPE .TSK
ODT
.TSK
PMDUMP.TSK
QUOLST.TSK
RUNOFF.TSK
TALK .TSK

Location
--------

---------

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

<104>
<104>
<104>
<232>
<124>
<124>
<104>
<232>
<104>
<104>
<232>
<104>
<232>

AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:
AUXLIB$:

Edit

Prot

Location
--------

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

<124>
<124>
<124>
<124>
<232>
<60>
<232>
<232>
<232>
<60>

ERROR$:
ERROR$:
ERROR$:
ERROR$ :
ERROR$:
ERROR$:
ERROR$ :
ERROR$ :
ERROR$ :
ERROR$:

Error Control
Component

--------ANALY1.TSK
ANALY2.TSK
ANALY3.TSK
ANALYS.TSK
ERRCPY.TSK
ERRDAT.FIL
ERRDET.TSK
ERRDIS.TSK
ERRINT.TSK
MSCPER.FIL

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.1 N
5 of 11

RESTOR
Component

Edit

Prot

Location
--------

BACCOM.TSK
BACCON.TSK
BACDIR.TSK
BACDSK.TSK
BACENT.TSK
BACFRM.TSK
BACLAB.TSK
BACLOD.TSK
BACLST.TSK
BACMNT.TSK
BACKUP.HLP
BACKUP.PRM
RESTOR.TSK

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

<252>
<252>
<252>
<252>
<252>
<252>
<252>
<252>
<252>
<252>
<60>
<60>
<252>

RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:
RESTOR$:

Prot

Location

Operator Services (OPSER)
Component

Edit

--------

BATCH .DCD
BATCH .TSK
BATDCD.TSK
BATDEC.TSK
BATIDL.TSK
BATRUN.TSK
CHARS .QUE
OPSER .TSK
OPSRUN.TSK
PLEASE.TSK
QUE
• TSK
QUEMAN.TSK
QUMRUN.TSK
SPLIDL.TSK
SPLRUN.TSK
SPOOL .TSK

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

<60>
<232>
<232>
<232>
<232>
<232>
<60>
<232>
<232>
<232>
<232>
<232>
<232>
<232>
<232>
<232>

OPSER$:
OPSER$:
OPSER$:
OPSER$:
OPSER$:
OPSER$:
OPSER$:
OPSER$:
OPSER$:
OPSER$: (see note)
OPSER$: (see note)
OPSER$:
OPSER$:
OPSER$:
OPSER$:
OPSER$:

Note
These programs have corresponding "dispatcher" programs
in the system library ($)
account,
for
backward
compatibility with programs or command procedures that
reference these programs in the $ account.

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.1 N
6 of 11

Print/Batch Services (PBS)
Component
---------

Edit

FORMS .SYS
PBSMGR.TSK
PBS
.SYS
PBS
.TSK
PBSERR.ERR

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

<40>
<232>
<188>
<232>
<40>

Edit

Prot

Location
--------

PBS$:
PBS$:
PBS$:
PBS$:
PBS$ :

Unsupported Software
Component
BPDA .BAS
BPDA .TSK
B2CREF.DOC
B2CREF.HLP
B2CREF.TSK
CMTAB . MAC
COMND . MAC
CONNEC.BAS
CONNEC.TSK
DIALER. BAS
DIALER. DOC
DIALER.TSK
DSKDMP.BAS
DSKDMP.HLP
DSKDMP.TSK
DSKPEK.OBJ
DUMP .SAV
EMTCPY.BAS
EMTCPY.TSK
ERMSG . MAC
FLOAT .BAS
FLOAT .TSK
FMTCM . MAC
HYPHEN. MAC
INDEX . MAC
LQSTAT.BAS
LQSTAT.TSK

Location
--------

---------

<60>
<104>
<40>
<60>
<104>
<60>
<60>
<60>
<104>
<60>
<60>
<104>
<60>
<60>
<124>
<60>
<104>
<60>
<124>
<60>
<60>
<124>
<60>
<60>
<60>
<60>
<124>

UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:
UNSUPP$:

RSTS/E Maintenance Notebook, June 1985

Seq 0.1.1 N

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

7 of 11

Unsupported Software
Component
---------

Edit

MEMORY. BAS
MEMORY.TSK
MONEY • BAS
MONEY .TSK
PINDX • MAC
QSTATS.B2S
QSTATS.DOC
QSTATS.TSK
RNCMD . MAC
RNFIO . MAC
RNPRE . MAC
RNO
.RNO
.TSK
RNO
RNOBLD.CMD
RNOBLD.ODL
RNORSX.MAC
RSTSFL.DOC
RSTSFL.HLP
RSTSFL.OBJ
RSTSFL.OLB
RUNOFF.MAC
SRCCOM.SAV
START • MAC
STATUS.B2S
STATUS.TSK

V9.0-14
V9.0-14
V9.0-l4
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14

Prot

Location
--------

<60>
<124>
<60>
<124>
<60>
<60>
<60>
<124>
<60>
<60>
<60>
<60>
<104>
<60>
<60>
<60>
<60>
<60>
<60>

<60>
<60>
<104>
<60>
<60>
<124>

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.1 N
8 of 11

Layered Product Update
Component

Edit

Prot

AUTOED.TSK
BUILD .TSK
CPATCH.TSK
CSPCOM.TSK
CSPCOM.OLB
UPDATE. DOC
UTILTY.TSK

V9.0-14
V9.0-14

<124>
<124>
<124>
<124>
<60>
<60>
<124>

V9.0~14

V9.0-14
V9.0-14
V9.0
V9.0-14

Location

-------UPDATE$:
UPDATE$:
UPDATE$:
UPDATE$:
LB:
UPDATE$:
UPDATE$:

(see
(see
(see
(see

note)
note)
note)
note)

(see note)

Note
These programs have corresponding "dispatcher" programs
in
the
system library ($)
account,
for backward
compatibility with programs or command procedures that
reference these programs in the $ account.
Device Test
Component

Edit

Prot

Location
--------

CPEXER.TSK
CPUTST.TSK
DSKSEK.TSK
DTEXER.TSK
DXEXER.TSK
DSKEXR.TSK
KBEXER.TSK
LPEXER.TSK
MTEXER.TSK
PPEXER.TSK
PREXER.TSK

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-l4
V9.0-14
V9.0-14
V9.0-14

<124>
<124>
<124>
<124>
<124>
<124>
<124>
<124>
<124>
<124>
<124>

TEST$:
TEST$:
TEST$:
TEST$:
TEST$:
TEST$:
TEST$:
TEST$ :
TEST$ :
TEST$:
TEST$ :

---------

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.1 N
9 of 11

DCL Runtime System and Utilities
Component

Edit

Prot

BP2
.LNK
C81
.LNK
DCL
.RTS
DCLUTL.TSK
DIBOL .LNK
DMS
.LNK
F77
.LNK
PRELIN.TSK
RSX11 .LNK

Location
--------

---------

V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-14
V9.0-l4
V9.0-14

<40>
<40>
<232>
<232>
<40>
<40>
<40>
<232>
<40>

[1, 2]
[1, 2]
[ 0 , 1]
[1,2]
[1,2]
[1, 2]
[1, 2]
[1, 2]
[1, 2]

Prot

Location

RSX Runtime System and Utilities
Component

Edit

--------

---------

CRF
.TSK
LBR
.TSK
MAC
.TSK
ODT
.OBJ
ODTID .OBJ
PAT
.TSK
RSX
.RTS
RSXMAC.SML
STK
.TSK
SYSLIB.OLB
TKB
.TSK

V05.03c
V06.00
V05.03c
09.009
DOl.0l
V02.02
V9.0.;..14
09.009
09.009

<104>
<104>
<104>
<40>
<40>
<104>
<60>
<40>
<104>
<40>
<104>

[1, 2]
[1, 2]
[1,2]
LB:
LB:
[1,2]
[0,1]
LB:
[1, 2]
LB:
[1, 2]

Prot

Location

RT-ll Runtime System and Utilities
Component

Edit

--------

---------

CREF .SAV
HOOK .SAV
LIBR .SAV
LINK .SAV
MACRO .SAV
PAT
.SAV
RTll
.RTS
SILUS .SAV
SYSLIB.OBJ
SYSMAC.SML

V05.03a
V9.0-14
V04.00
V08.02R
V05.03c
V04.00
V9.0-14
V9.0-14

<104>
<124>
<104>
<104>
<104>
<104>
<60>
<104>
<40>
<40>

[ 1, 2 ]
SYSGEN$:
[ 1, 2 ]
[ 1, 2 ]
[1,2]
[1,2]
[0,1]
[1,2]
[1, 2]
[ I, 2 ]

RSTS/E Maintenance Notebook, June-1985.

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.1 N
10 of 11

BASIC-PLUS Runtime System
Component
---------

Edit

BASIC .RTS

V9.0-l4

<60>

[0 , 1 ]

Component
---------

Edit

Prot

Location

EDT
.LIB
EDT
.TSK
EDTI00.DOC
EDT200.DOC
EDT52 .DOC
EDTHEL.HLP
EDTKIT.DOC

V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0

<60>
<104>
<40>
<40>
<40>
<40>
<60>

EDT$:
EDT$ :
EDT$:
EDT$ :
EDT$:
LB:
EDT$:

Component
---------

Edit

Prot

Location

MGEFIL.ODL
MGELIB.OLB
MGEREC.ODL
MGESHR.OLB
MGEUTL.TSK
SMRES .LIB
SMRES .STB
SMRES .TSK
SMSHR .ODL
SRTFIL.ODL
SRTLIB.OLB
SRTREC.ODL
SRTSHR.OLB
SRTTRN.TSK
SRTUTL.TSK
STMGFL.ODL
STMGRC.ODL

V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0
V3.0

Prot

Location
--------

EDT V3.0
--------

SORT V3.0
--------

<40>
<40>
<40>
<40>
<104>
<60>
<40>
<40>
<40>
<40>
<40>
<40>
<40>
<104>
<104>
<40>
<40>

LB:
LB:
LB:
LB:
SORTS :
[0,1]
LB:
LB:
LB:
LB:
LB:
LB:
LB:
SORTS:
SORTS :
LB:
LB:

RSTS/E Maintenance Notebook, June 1985

Seq 0.1.1 N

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

11 of 11

RMS V2.0
Component
---------

Edit

DAP11X.ODL
DAPRES.LIB
DAPRES.STB
DAPRES.TSK
DAPRLX.ODL
RORMSl.MAC
RMSll .ODL
RMS11S.0DL
RMSIIX.ODL
RMS12S.0DL
RMS12X.ODL
RMSBCK.TSK
RMSCNV.TSK
RMSDAP.OLB
RMSDEF.TSK
RMSDES.HLP
RMSDES.TSK
RMSDSP.TSK
RMSIFL.TSK
RMSLBA.LIB
RMSLBB.LIB
RMSLBC.LIB
RMSLBD.LIB
RMSLBE.LIB
RMSLBF.LIB
RMSLIB.OLB
RMSMAC.MLB
RMSRES.LIB
RMSRES.STB
RMSRES.TSK
RMSRLX.ODL
RMSRST.TSK

V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.000
V2.001
V2.0
V2.000
V2.0
V2.001
V2.002
V2.006
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.0
V2.002

Prot

Location
--------

<40>
<60>
<40>
<40>
<40>
<40>
<40>
<40>
<40>
<40>
<40>
<104>
<104>
<40>
<104>
<40>
<104>
<104>
<104>
<60>
<60>
<60>
<60>
<60>
<60>
<40>
<40>
<60>
<40>
<40>
<40>
<232>

LB:
RMS$:
LB:
LB:
LB:
LB:
LB:
LB:
LB:
LB:
LB:
RMS$:
RMS$:
LB:
RMS$:
LB:
RMS$:
RMS$:
RMS$:
RMS$:
RMS$:
RMS$:
RMS$:
RMS$:
RMS$:
LB:
LB:
RMS$:
LB:
LB:
LB:
RMS$:

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.2 N
1 of 6

ANNOUNCING RSTS/E VERSION 9.0

RSTS/E V9.0, which has been in development for over 2 years,
includes
major enhancements to most of the RSTS/E system. These range from
DCL-based integrated system and account management to streaming
support for TU80 tape drives. Overall the enhancements in RSTS/E V9.0
are focused on five major goals. These goals are:
- Complete and integrate the DCL-based user interface
- Provide operational compatibility with VMS
- New fast BACKUP with support for streaming tape drives
- Improve system security
- Provide faster, easier installation and update
PRODUCT DESCRIPTION
DCL Command File Processing
The new RSTS/E DCL command file processor is based on the VMS model
and is fully integrated with the RSTS/E system at command level. This
feature allows users to define command procedures, define their own
commands on a per user basis and automate many user and system
management tasks.
It is subset compatible with VMS command file
processing, so many command procedures can be moved from a RSTS/E
system to a VMS system and back again without modification. This can
also help to reduce the level of complexity required to manage VMS and
RSTS/E systems kept in the same area or involving the same people,
since many functions can be accessed by using similar command
procedures.
The DCL command processor is a text processor whose performance is
generally slower than most other high-level languages.
For this
reason, you should consider performance when deciding what langauge is
best suited to a particular task. DCL should be viewed as a "command
level" language that best handles the execution and control of system
or user commands.

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.2 N
2 of 6

Logging In
One impact of DCL command processing performance concerns logging in.
When logging in on V9.0,
the LOGIN program will chain to the
system-wide login command file, LOGIN.COM, located in account [0,1] on
the system disk. This file contains commands to be performed for all
users logging in to the system. Users in turn can create their own
LOGIN command files to define new commands,
read mail,
assign
logicals, or perform any other task as part of the login sequence.
Some tasks that were previously done in the LOGIN program are now done
in the system login command procedure.
For example, printing of the
$NOTICE.TXT file at your terminal is now handled by the system
LOGIN.COM file, rather than the LOGIN program.
Because login command files are normally executed "silently"
(no
echoing of the commands at your terminal), the login sequence ln V9.0
may appear slower than in the past. This will, of course, depend on
the size of the system login command file and each user's login
command file, as well as system load, resources, etc.
Login delays were a recognized problem during the V9.0 field test.
Since the start of field test, much effort went into optimizing the
system login command file to minimize its processing time.
Because of these efforts, most users logging in to a light- or
medium-loaded V9.0 system with the distributed system LOGIN.COM file
will notice only a slight delay (less than five seconds) between
entering their password and the display of the DCL prompt. On
heavily-loaded systems, the delay may be longer.
DIGITAL is investigating ways of making DCL command processing faster
in the future.
This effort will further reduce any delays during
login.
DCL is Extended to the Entire RSTS/E System
In past releases of RSTS/E users were required to learn many different
utilities and their syntax to fully utilize the power of the RSTS/E
system.
In RSTS/E V9.0 there are over 100 modifications to DCL which
solve this problem.
These range from new qualifiers on existing
commands to the addition of entirely new commands which add major new
capabilities to the RSTS/E system.

RSTS/E Maintenance Notebook, June 1985

Seq 0.1.2 N

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

There are many illustrations
RSTS/E V9.0 system:

3 of 6

V9.0

modifications thoughout the

- The new DCL based integrated account management
function which replaces many separate utilities
such as UTILTY, MONEY and REACT.
- The new batch processor uses DCL command files
and executes them at the time specified by the user.
- The new BACKUP function is accessed using DCL commands.
New BACKUP Utility Increases Capabilities and Throughput
The new BACKUP utility includes four main areas of improvement:
increased capabilities, backup sets which are in VMS compatible
format, support for the new Asynchronous I/O directives,
and support
for streaming tape drives such as the TU80.
Writing and reading backup sets in VMS compatible format makes it easy
to transfer data from a PDP-II to a VAX and back again.
Full streaming support for streaming tape drives such as the TU80 will
allow users to backup their systems in a fraction of the time which is
now required.
It also lays the groundwork for support of future
streaming tape drives.
Security Enhancements
Since RSTS/E is used primarily in the commercial environment, RSTS/E
users are particularly concerned with security. Steady progress was
made in this area in the course of past releases;
however, RSTS/E
V9.0 has moved a giant step forward with five major areas of
improvement:
- Multiple privilege attributes by account
- Longer passwords
- Hashed passwords
- System password
- Enhanced disk quota checking and enforcement

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.2 N
4 of 6

Multiple privilege attributes by account eliminates the use of "all or
nothing" accounts and implements the VMS
model
of
privilege
attributes.
Using this model, users are given only those privileges
which they require and no others.
Their account number (PPN)
no
longer denotes a privilege level.
This gives the system manager
tighter control over what users are allowed to do on the system.
Passwords have been lengthened from a maximum of 6 characters to 14
characters.
Optionally by account, passwords can be set up so that
they are no longer available for lookup and are hashed so that they
can not be retrieved.
Another feature of the new security system is the use of captive
accounts. These are accounts which are setup to startup a program,
such as a menu of selectable options or an application like word
processing, and when the user exits from the program RSTS/E logs the
user out of the system.
Another aspect of security is the ability to control system resources.
RSTS/E V9.0 features increased control of disk usage through logged in
and logged out quotas. This allows the system manager to allocate and
control disk resources effectively.
Conversion to these new approaches can be done either gradually or all
at once depending on the needs of the system.
Separate I&D Space Support for User Programs
Standard 16-bit addressing allows user programs to grow to 32KW before
overlaying is required. With RSTS/E V9.0 users can now address'upto a
maximum of 64KW through the use of separate Instruction and Data (1&D)
space. This will lead_to improved performance and lessen overlay
complexity.
Currently the languages that support I&D space are
BASIC-Plus-2 V2.3, Macro (MAC), and Fortran 77.
Virtual Disk
System managers can allocate a portion of contiguous unused memory to
be a virtual disk. This memory is considered to be a file-structured
device and can be accessed by user programs in the same way that other
disks are accessed except that data accesses occur at memory speeds
rather than disk speeds.

RSTS/E Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes

Seq 0.1.2 N
5 of 6

Enhanced 8-Bit Character Support
The RSTS/E monitor has been enhanced to support 8-bit characters such
as the multinational character set. Many of the CUSPs will now accept
8-bit characters but may not fully use them. BASIC-PLUS has not been
enhanced to include this support.
Autobaud Detection
Autobaud detection support includes baud rates from 110 to 9600 baud.
Speeds can be detected for dial-up and directly connected terminals.
Faster, Easier Installation and Updating
The installation and SYSGEN processes have been made far simpler and
include defaults and help that was not available in previous releases.
When installing a system (after the first time) previous answers can
be automatically used as input into the installation process.
In some
cases installation and updating time can be reduced by 80%.
Memory Requirements
Due to the greatly enhanced capabilities, the memory required has also
increased.
The increase is not extreme and PDP 11/34 systems will
continue to be supported, but users will have less space to run jobs
than they do when running under RSTS/E V8.0.
Performance
RSTS V9.0 generally uses more processing overhead than previous
versions, due to the many new features added to the monitor.
Most
light- to medium-loaded systems will not notice this extra overhead,
while heavily loaded systems may see some performance loss.
Your
system's performance will depend on your type of processor, amount of
memory, type and organization of disks, and the number and types of
jobs running on your system.
Performance in some areas of the system is better.
For example, the
new BACKUP package allows you to backup your disks faster than before.
Also,
the new virtual disk feature allows systems with sufficient
memory to reduce disk accesses by keeping frequently used or heavily
overlaid programs on the virtual disk in memory.

RSTS/E Maintenance Notebook, June 1985

Seq 0.1.2 N

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Notes
DIGITAL is currently investigating
performance on RSTS in the future.

6 of 6
other

ways

improve system

Compatibility with RSTS/E version 8.0-7
RSTS/E Version 9.0 is generally upwards compatible from Version 8.0-7
at the program level. Features which could affect this compatibility,
such as mUltiple privileges and quotas, can be installed in a way
which is compatible with their Version 8.0 implementation. A complete
description of these differences can be found in the RSTS/E Version
9.0 Release Notes.
Quality Evaluation
RSTS/E Version 9.0 has received the highest level of quality testing
of any RSTS system ever. An extensive package of regression tests and
installation tests has been performed on all of the development base
levels for the product.
Field testing has been performed for eight
months at over 30 sites, with a consensus among the sites that they
would recommend running V9.0.
ORDERING/AVAILABILITY INFORMATION
RSTS/E Version 9.0 is scheduled to be available in June,
1985.
For
specific service availability and pricing information, please contact
your local DIGITAL Account Manager.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Management Guidelines

Seq 0.2.1 N
1 of 2

USING SAVE/RESTORE ON A TWO-DISK SYSTEM
This article describes the procedure for using SAVE/RESTORE to backup
the disks on a system which has only two disk drives and no magnetic
tape drives.
On such a system, you can backup the system disk by
shutting down the RSTS/E system and using the SAVRES option of INIT.
It is impossible, however, to perform such a backup of the non-system
disk, since the procedure would require that the system disk, the disk
being backed up, and the SAVE volume all be mounted simultaneously,
and hence would require three or more disk drives, or'a magnetic tape
drive.
The solution presented in this article is to place a copy of the
INIT.SYS system initialization code on the non-system disk, allowing
it to run as the "system" disk for off-line SAVE/RESTORE operations.
This procedure has one drawback:
the INIT.SYS initialization code
requires about 600 blocks on the non-system disk
(about 11% of an
RK05).
If you have small disks, such as RK05's or RLOl's, you should
consider expanding your hardware to
include another disk drive or
magnetic tape unit.
For disks larger than RLOl's, the overhead of
having the INIT.SYS initialization code on each non-system disk
is
usually small enough to be tolerable, although you must decide based
on your system's needs.
You should put the INIT.SYS initialization code ([O,l]INIT.SYS) on the
non-system disk immediately after initializing the disk with DSKINT.
This ensures that there
is enough space for
INIT.SYS.
After
generating the monitor, run-time system, and system library, perform
the procedures outlined below.
In the following example, the notation
"SYO:" denotes the disk drive on which your normal system disk is
mounted, and "xxn:" denotes the other disk drive, which is used for
various purposes in the procedure:
1.

If you have not yet initialized the non-system disk that you plan
to use, initialize it using the DCL INITIALIZE command or the
DSKINT utility. Then mount the disk using the MOUNT command.

Issue the commands given below:
$ COpy [O,l]INIT.SYS xxn:[O,l]/CLUSTER SIZE=16
$ RUN SYSGEN$:HOOK.SAV<cr>
<HOOK's header line>
*xxn:[O,l]INIT.SYS<cr>
Hook complete
*AZ
$

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E V9.0 General Notes
System Management Guidelines
3.

Seq 0.2.1 N
2 of 2

Your non-system disk is now ready to use. You may dismount it and
mount it as a public or private disk if you desire. When you wish
to back up that disk, you must shut down your system, bootstrap
the non-system disk, and mount a scratch disk in place of your
normal system disk.
You may now use the SAYRES option of INIT to
SAVE or IMAGE-copy your non-system disk to the backup disk.
NOTE
Every time you install an update, you must delete
the copies of INIT.SYS on any other disks to which
you have copied it, and
repeat
the
above
procedure.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Initialization
INIT.SYS Program Notes

Seq 1.2.1 N
1 of 2

DEVICES WITH NON-STANDARD UNIBUS ADDRESSES AND VECTORS
Some installations have devices which are installed at non-standard
UNIBUS addresses or which vector to non-standard locations.
INIT does
not automatically recognize these devices.
Of course,
the best
solution is to have field service reconfigure these devices so that
they conform to the standard.
Appendix C of the RSTS/E System
Installation and Update Manual contains the information you need to
determine the correct UNIBUS addresses and vectors for all devices
supported by RSTS/E.
Note that extra units such as the second RX,
second PR, etc., do not have "homes" and must use the CSR option.
If re-configuration is not possible, you can use the HARDWR option of
INIT.
The CSR suboption sets non-standard UNIBUS addresses and the
VECTOR suboption sets non-standard
vectors.
DIGITAL
strongly
recommends that you use only the CSR suboption. This tells INIT to
find the device at its non-standard UNIBUS address,
but lets INIT
determine the device's vector.
If the device is functioning properly,
INIT will find the device's non-standard vector. The only device for
which- INIT cannot determine a vector is the card reader.
If a card
reader has a non-standard vector, you must use the VECTOR sUboption.
The PA611 paper tape reader must be powered on for INIT to find its
vector. Use the VECTOR sUboption if you intend to start your system
with a PA611 paper tape reader powered off.
Be careful when you assign non-standard vectors to devices.
INIT
checks all device vectors (assigned through the VECTOR suboption or
automatically determined) against a table of reserved locations.
INIT
also checks to see if any vector location is used by more than one
device. Any conflict will print the message:
Vector for Device XXn: (vvv) already in use - device disabled
where vvv is the octal address of the erring vector.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9 .. 0
Initialization
INIT.SYS Program Notes
The RSTS/E reserved
vectors, are:
Addresses
0-2
4-36
40-56

Seq 1.2.1 N
2 of 2

locations,

which

may

not

used

RSTS/E usage
Detection of jumps to 0 and traps to 0
System trap vectors
Reload start addresses, failure HALT

100-102
104-106
110-112
114-116

KW11-L line frequency clock vector
KWI1-P crystal clock vector
Jump to 0 handling
Memory parity trap vector

144-146

Crash dump handling

234-236
240-242
244-246
250-252

Statistics handling
PIRQ trap vector
FPP or FIS exception trap vector
Memory Management Unit trap vector

device

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 3.1.1 F

RSTS/E V9.0
Monitor
Monitor Patches

1 of 2

DISABLING THE USE OF DATA SPACE - MONITOR FEATURE PATCH
PROBLEM:
Some systems may find it desirable to permanently disable the use of
data space by the monitor because optional software generated into the
system is not compatible with the monitor using data space.
If your
monitor contains any unsupported software, such as a locally written
device driver, then it is unlikely to work with data space. The only
supported monitor software which works with data space is software
that comes from either the RSTS/E V9.0, DECnet/E V2.1,
FMS-ll VI.5,
RSTS/E 3271 Protocol Emulator, or RSTS/E High Performance 2780/3780
Protocol Emulator distribution kits.
Note that data space will
automatically not be used if your system includes the optional
RSTS/E-2780 (RJ2780) package.
SOLUTION:
The patching procedure detailed as follows will cause the monitor to
never use data space,
regardless of whether the processor it 1S
running on supports it or not.
Note
This patch does not disable user-mode instruction and
data
space.
Non-standard
monitor code may need
modification before attempting to run any user programs
which use separate instruction and data space.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V9.0
installed in any target monitor SIL.

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

monitor.

installed

using

It
the

may

PATCH

(RETURN for installed monitor SIL)

This patch can be installed manually using ONLPAT,
the on-line
patching program.
Note,
however,
that if the patch is applied
online to the installed monitor SIL, it will not take effect until
the system is re-booted.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Monitor Patches

Seq 3.1.1 F
2 of 2

RUN $ONLPAT
Command File Name? <cr>
File to patch? <cr>
File found in account [0,1]

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

This feature patch is contained in the file PA0301.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.
4.

The patch is as follows:
Module name? DEFALT
Base address? .. NODS
Offset address? 0
Base
Offset Old
001000 000000 000000
001000 000000
000
001000 000001
000
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0301
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?

? \
? -1
? AZ

New?
? Q!1
? 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)

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Terminal Service Patches

Seq 3.3.1 F
1 of 2

CHANGING SPECIAL LOGIN TERMINAL - TERMINAL SERVICE FEATURE PATCH
The number of jobs that can log in to a RSTS/E system is limited by
the swapping space available, the JOB MAX set at system start-up time,
and the login setting (set by the SET SYSTEM/[NO]LOGINS command).
However,
the console terminal (KBO:) is a special terminal, 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
selected, or this feature can be disabled entirely.

can

may

PROCEDURE:
1.

This is a feature patch to the RSTS/E V9.0
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
interpreted as a decimal number.

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

installed

USIng

the

PATCH

(RETURN for installed monitor SIL)

This patch can be installed manually
patching program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? <cr>
File found in account [0,1]

monitor.

using

ONLPAT,

the

on-line

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

This feature patch is contained in the file PA0303.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.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Terminal Service Patches

Seq 3.3.1 F
2 of 2
NOTE

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

The patch is as follows:
Module name? TER
Base address? .. CTZ.
Offset address? 0
Base
Offset Old
?????? 000000 000000
?????? 000002 001407
Offset address? AZ
Base address? .• CTY.
Offset address? 0
Base
Offset Old
?????? 000000 177777
?????? 000002 001404
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0303
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? m.*2
? AZ

New?
? n.*2
? AZ

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

(or -1,
(CTRL/Z
(CTRL/Z
(CTRL/Z

from step 2)
for new offset)
for new base)
for new module)

New?

? Q!1
? AC

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

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Terminal Service Patches

Seq 3.3.2 F
1 of 2

INPUT ESCAPE SEQUENCE HANDLING - TERMINAL SERVICE FEATURE PATCH
RSTS/E allows mUltiple character incoming escape
RSTS/E
Programming
Manual fully describes the
handling.

sequences.
The
escape sequence

One of the multi-character escape sequences is ESCape followed by "PH,
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, "PH
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
installed in any target monitor SIL.

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

installed

using

It
the

may

PATCH

(RETURN for installed monitor SIL)

This patch can be installed manually
patching program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? <cr>
File found in account [0,1]

monitor.

using

ONLPAT,

the

on-line

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

This feature patch is contained in the file PA0303.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

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Terminal Service Patches

Seq 3.3.2 F
2 of 2

update procedure.
4.

The patch is as follows:
Module name? TER
Base address? .. ESCP
Offset address? 0
Base
Offset Old
?????? 000000 050001
?????? 000002 ??????
Offset address? AZ
Base address? AZ
Module name? RSTS
Base address? $$0303
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? Q&177400

? AZ

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

New?
? Q!2

? AC

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

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Terminal Service Notes

Seq 3.4.1 N
1 of 1

UNDERSTANDING TERMINAL PARITY AND STOP BIT SETTINGS
Terminal Parity
The DCL command SET TERMINAL/[NO]PARITY[=ODD1EVEN] controls the format
in which data characters are sent to a terminal.
/NOPARITY (the
default) sends the full 8 bits of a byte out to a terminal.
If the
/NOEIGHTBIT characteristic is set, /PARITY=EVEN and /PARITY=ODD trim
the byte to 7 bits of data and then set or clear the eighth bit to
achieve the correct parity setting.
(Note: Binary Output Mode is
"Data Binary Output Mode". /NOPARITY yields 8 bit data,
/PARITY=EVEN
and /PARITY=ODD yield 7 bit data if the /NOEIGHTBIT characteristic is
set.)
The DLIIA/B/C/D/E and DJll interfaces do not have programmable
hardware parity generation.
For these interfaces, terminal service
generates the output parity bit. The DHl1, DHVll, DHUl1 and DZll have
programmable hardware parity generation, which is used by terminal
service.
Stop Bit Settings
Terminal interfaces with programmable baud rate settings (DHl1, DHV11,
DHUll and DZll) also have programmable stop-bit settings. RSTS will
automatically select 2 stop bits for speed settings of 110 baud or
less and 1 stop bit for speeds greater than 110 baud. Older
mechanical terminals, such as the ASR33
(which runs at 110 baud),
require the time delay of 2 stop bits for synchronization. Modern
terminals need only 1 stop bit.
When converting from baud rates to characters per second (CPS),
the
correct number of stop bits becomes clear. Asynchronous communication
consists of 1 start bit, 8 data bits, and 1 or 2 stop bit(s}.
(110 BITS PER SECOND)
------------------------- = 110/11 = 10 CHARACTERS PER SECOND
(1+8+2 BITS PER CHARACTER)
(300 BITS PER SECOND)
------------------------- = 300/10 = 30 CHARACTERS PER SECOND
(1+8+1 BITS PER CHARACTER)

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Terminal Service Notes

Seq 3.4.2 N
1 of 2

MODEM CONTROL ON PRIVATE, LEASED LINES
Some RSTS/E installations use private, leased phone lines for terminal
connections.
If the line has no modem or no modem control (for
example, data signals only) then the line should be set as a local
line using the DCL command SET TERMINAL/NODIALUP.
In this case the
private, leased line is simply a long local connection. On the other
hand, many private, leased lines do use modem control.
When using modem control, there are five modem signals used by RSTS/E:
1.

Ring Indicator (Circuit CE, pin 22)
This signal is true if the modem's "phone" is ringing.
RSTS/E
does not control this signal~ the modem does. Private, leased
lines normally do not "ring."

Carrier Detect (Circuit CF, pin 8)
This signal is true when the modem is receiving carrier from
the modem on the other end of the line. RSTS/E does not
control this signal~ the modem does.

Clear to Send (Circuit CB, pin 5)
This signal is true when it is "OK to send data" to the other
modem. RSTS/E does not control this signal~ the modem does.

Data Terminal Ready (Circuit CD, pin 20)
This signal is controlled by RSTS/E,
not the modem.
When
RSTS/E sets this signal to true, the modem answers the phone
(if it is not already answered) and sends carrier to the modem
at the other end of the connection.

Request to Send (Circuit CA, pin 4)
This signal is controlled by RSTS/E,
not the modem.
When
RSTS/E sets this signal to true, the modem tells the other
modem it is now "clear to send".

RSTS/E always sets and clears Data Terminal Ready and Request to
together.

Send

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Terminal Service Notes

Seq 3.4.2 N
2 of 2

The normal sequence for a dial-up modem line is:
1.

Someone calls in.

The modem asserts Ring Indicator.

RSTS/E sets Data Terminal Ready and Request to Send.

The modem answers the phone and sends out carrier and Clear to
Send. The Ring Indicator goes off.

The other end sends carrier and Request to Send.
sets Carrier Detect and Clear to Send.

RSTS/E enables the line for data communication.

Data communication occurs •..

The other end drops carrier.
and Clear to Send.

RSTS/E starts a 5 second timeout.

The timeout expires.
Request to Send.

The modem

The modem clears Carrier

Detect

RSTS/E clears Data Terminal Ready and

10. The connection is now broken.
In addition, RSTS/E polls all modem lines once each second.
If
Carrier Detect has come on without a Ring Indication, the line will be
enabled by setting Data Terminal Ready and Request to Send.
If
Carrier Detect is on when the system is initially started, this
happens immediately. So, to use a modem-controlled private, leased
line as a local line:
1.

Strap the Ring Indicator signal false. This ensures that
RSTS/E never sees a "ringing" line to get confused about.

Strap the Carrier Detect and Clear to Send signals true. This
ensures that RSTS/E will immediately enable the line by
setting Data Terminal Ready and Request to Send.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
File Processor Patches

Seq 3.5.1 F
1 of 8

CONTROLLING EMT LOGGING - FILE PROCESSOR FEATURE PATCH
If you included EMT Logging when you generated your system,
you may
want to modify the set of directives which the monitor passes to your
logging program. The following procedure allows you to enable or
disable EMT logging for each of the directives which can be logged.

PROCEDURE:
1.

This is a feature patch to the RSTS/E V9.0 monitor.
It may be
installed in any target monitor SIL which has been generated to
include the EMT Logging feature.
If you attempt to
install this
patch on a SIL that does not include the EMT logging feature, the
patch will fail with the error, "?Address above module bounds."

Note that as supplied, the patch disables logging for each of the
directives.
DIGITAL recommends that you retain a copy of the
patch in this form, to use as a starting point for creating later
versions, should your requirements change.

Decide which directives you want to have logged.
For each one,
locate the appropriate segment(s) of the patch.
The value under
"New?" will be "Q!lOO", which is the value to disable logging.
To
enable logging
(reversing the sense of the patch), replace this
value with "Q&\lOO".

Note that some directives can be
invoked via CALFIP,
some VIa
.UUO,
and some via either CALFIP or .UUO.
The following patch
contains three sections:
the first controls those directives
which can be invoked via either CALFIP or .UUO.
(The second and
third control those directives invoked via CALFIP alone and
.UUo
alone,
respectively.)
You will need to make TWO changes for any
directive appearing in the first group:
once for
the CALFIP
invocation path, and once for the .UUO invocation path.
The paired directives appear next to each other in the first
group. Directives appear in ascending order by CALFIP code for
the first two groups, and by .UUO code for the third group;
these
codes are the MACRO values documented In the RSTS/E System
Directives Manual.

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 3.5.1 F

RSTS/E V9.0
Monitor
File Processor Patches
5.

2 of 8

The patch described in Step 7 can be
option of INIT.SYS:
Option: PATCH
File to patch? <cr>

installed

using

the

PATCH

(RETURN for installed monitor SIL)

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

This feature patch is contained in the file PA0305.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.
NOTE
The patch file for this patch requires manual
editing to include installation specific parameters
before it can be successfully installed.
7.

The patch is as follows:

Module name? RSTS
Base address? EMLTBL
Offset address? 0
Base
Offset Old
??????
000000 ??????
Offset address? AZ
Base address? $$0305
Offset address? 0
Base
Offset Old
??????
000001 ??????
??????
000002
???
Offset address? AZ
Base address? $EMLFQ
functions
Offset address? ASSFQ/2
Base
Offset Old
??????
000012 ??????
??????
000014 ??????
Offset address? AZ

; Verify EMT Logging generated
New?
? AZ

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

New?
? Q!l
? AZ

(CTRL/Z for new offset)
(CTRL/Z for new base)
Beginning of paired CALFIP - UUO
ASSIGN function, CALFIP flavor

New?

? Q!IOO
? AZ

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

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
File Processor Patches

Seq 3.5.1 F
3 of 8

Base address? $UUOSN
Offset address? UU.ASS-UU$MIN
; ASSIGN function, UUo flavor
Base
Offset Old
New?
??????
000047
???? Q!100
??????
000050
???? AZ
(CTRL/Z for new offset)
Offset address? AZ
(CTRL/Z for new base)
Base address? $EMLFQ
Offset address? DEAFQ/2
: DEASSIGN function, CALFIP
flavor
Base
Offset Old
New?
??????
000013
??? ? Q!lOO
??? ? AZ
(CTRL/Z for" new offset)
??????
000014
Offset address? AZ
(CTRL/Z for new base)
Base address? $UUOSN
Offset address? UU.DEA-UU$MIN
: DEASSIGN function, UUO flavor
Base
Offset Old
New?
??????
000050 ?????? ? Q!lOO
??????
000052 ??????? AZ
(CTRL/Z for new offset)
Offset address? AZ
(CTRL/Z for new base)
Base address? $EMLFQ
Offset address? DALFQ/2
: DEASSIGN ALL function, CALFIP
flavor
Base
Offset Old
New?
??????
000014 ?????? ? Q!100
??????
000016 ?????? ? AZ
(CTRL/Z for new offset)
Offset address? AZ
(CTRL/Z for new base)
Base address? $UUOSN
Offset address? UU.DAL-UU$MIN
: DEASSIGN ALL function, UUO
flavor
Base
Offset Old
New?
??????
000051
??? ? Q!lOO
??????
000052
(CTRL/Z for new offset)
???
Offset address? AZ
(CTRL/Z for new base)
Base address? $EMLFQ
Offset address? LOKFQ/2
; LOOKUP function, CALFIP flavor
Base
Offset Old
New?
??????
000011
??? ? Q!lOO
??????
000012
(CTRL/Z for new. offset)
??? ? AZ
Offset address? AZ
(CTRL/Z for new base)
Base address? $UUOSN
Offset address? UU.LOK-UU$MIN
; LOOKUP function, UUO flavor
Base
Offset Old
New?
??????
000056 ?????? ? Q!100
??????
000060 ?????? ? AZ
(CTRL/Z for new offset)
Offset address? AZ
: End of paired CALFIP - UUO functions
Base address? $EMLFQ
: Beginning of CALFIP-only functions
Offset address? CLSFQ/2
: CLOSE function
Base
Offset Old
New?

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
File Processor Patches

Seq 3.5.1 F

4 of 8

??????
000000 ?????? ? Q!100
??????
000002 ?????? ? AZ
(CTRL/Z for new offset)
; OPEN function
Offset address? OPNFQ/2
Base
Offset Old
New?
??????
000001
??? ? Q!100
(CTRL/Z for new offset)
???
??????
000002
Offset address? CREFQ/2
; CREATE function
Base
Offset Old
New?
??????
000002 ?????? ? Q!100
??????
000004 ?????? ? AZ
(CTRL/Z for new offset)
Offset address? DLNFQ/2
; DELETE function
Base
Offset Old
New?
??????
000003
??? ? Q!IOO
(CTRL/Z for new offset)
???
??????
000004
; RENAME function
Offset address? RENFQ/2
Base
Offset Old
New?
??????
000004 ?????? ? Q!100
??????
000006 ?????? ? AZ
(CTRL/Z for new offset)
; DIRECTORY (wildcard) function
Offset address? DIRFQ/2
Base
Offset Old
New?
??????
000005
??? ? Q!IOO
(CTRL/Z for new offset)
??????
000006
???
Offset address? RSTFQ/2
; RESET function
Base
Offset Old
New?
??????
000010 ?????? ? Q!100
??????
000012 ?????? ? AZ
(CTRL/Z for new offset)
Offset address? CRTFQ/2
; CREATE Temporary file function
Base
Offset Old
New?
??????
000015
??? ? Q!100
??????
000016
???
(CTRL/Z for new offset)
Offset address? CRBFQ/2
; CREATE Binary file function
Base
Offset Old
New?
??????
000016 ?????? ? Q!100
??????
000020 ?????? ? AZ
(CTRL/Z for new offset)
Offset address? RUNFQ/2
; RUN function
Base
Offset Old
New?
??????
000017
???? Q!100
??????
000020
???? AZ
(CTRL/Z for new offset)
Offset address? AZ
; End of CALFIP-only functions
Base address? $UUOSN
; Beginning of UUO-only functions
Offset address? UU.TB3-UU$MIN
; Monitor Tables III function
Base
Offset Old
New?
??????
000000 ?????? ? Q!100
??????
000002 ?????? ? AZ
(CTRL/Z for new offset)
Offset address? UU.SPL-UU$MIN
; SPOOL function
Base
Offset Old
New?
??????
000001
???? Q!100
??????
000002
???? AZ
(CTRL/Z for new offset)

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
File Processor Patches
Offset address? UU.DMP-UU$MIN
Base
Offset Old
New?
??????
000002 ?????? ? Q!lOO
??????
000004 ?????? ? AZ
Offset address? UU.FIL-UU$MIN
Base
Offset Old
New?
??????
000003
???? Q!lOO
??????
000004
???? AZ
Offset address? UU.ATR-UU$MIN
Base
Offset Old
New?
??????
000004 ?????? ? Q!lOO
??????
000006 ?????? ? AZ
Offset address? UU.LOG-UU$MIN
Base
Offs(~
Old
New?
??????
OOOO~~
?????? ? Q!100
??????
000014 ?????? ? AZ
Offset address? UU.RTS-UU$MIN
Base
Offset Old
New?
??????
000013
???? Q!100
??????
000014
???? AZ
Offset address? UU.NAM-UU$MIN
Base
Offset Old
New?
??????
000014 ?????? ? Q!100
??????
000016 ?????? ? AZ
Offset address? UU.ACT-UU$MIN
Base
Offset Old
New?
??????
000016 ?????? ? Q!lOO
??????
000020 ?????? ? AZ
Offset address? UU.DAT-UU$MIN
Base
Offset Old
New?
??????
000017
???? Q!lOO
??????
000020
???? AZ
Offset address? UU.PRI-UU$MIN
function
Base
Offset Old
New?
??????
000020 ?????? ? Q!lOO
??????
000022 ?????? ? AZ
Offset address? UU.TB2-UU$MIN
Base
Offset Old
New?
??????
000021
???? Q!lOO
??????
000022
???? AZ
Offset address? UU.BCK-UU$MIN
function
Base
Offset Old
New?
??????
000022 ?????? ? Q!100
000024 ?????? ? AZ
??????
Offset address? UU.HNG-UU$MIN
Base
Offset Old
New?

Seq 3.5.1 F
5 of 8

; Snapshot dump function
(CTRL/Z for new offset)
; FILe statistics function
(CTRL/Z for new offset)
; Read/Write attributes function
(CTRL/Z for new offset)
; Set number of logins function
(CTRL/Z for new offset)
; RTS/RESLIB control functions
(CTRL/Z for new offset)
; RTS name for file function
(CTRL/Z for new offset)
; Accounting dump function
(CTRL/Z for new offset)
; System date/time function
(CTRL/Z for new offset)
; Priority/Run Burst/Size

(CTRL/Z for r•.::w offset)
; Monitor Tables II function
(CTRL/Z for new offset)
; File backup statistics

(CTRL/Z for new offset)
; Hangup dataset function

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
File Processor Patches
??????
000024 ?????? ? Q!100
??????
000026 ?????? ? AZ
Offset address? UU.FCB-UU$MIN
Base
Offset Old
New?
??????
000025
???? Q!100
??????
000026
???? AZ
Offset address? UU.POK-UU$MIN
Base
Offset Old
New?
??????
000027
???? Q!IOO
??????
000030
???? AZ
Offset address? UU.TBI-UU$MIN
Base
Offset Old
New?
??????
000032 ?????? ? Q!100
??????
000034 ?????? ? AZ
Offset address? UU.NLG-UU$MIN
function
Base
New?
Offset Old
??????
000033
???? Q!100
000034
???? AZ
??????
Offset address? UU.YLG-UU$MIN
Base
Offset Old
New?
??????
000034 ?????? ? Q!100
000036 ?????? ? AZ
??????
Offset address? UU.PAS-UU$MIN
Base
Offset Old
New?
??????
000035
???? Q!100
000036
???? AZ
??????
Offset address? UU.DLU-UU$MIN
Base
Offset Old
New?
??????
000036 ?????? ? Q!100
000040 ?????? ? AZ
??????
Offset address? UU.MNT-UU$MIN
Base
Offset Old
New?
??????
000040 ?????? ? Q!100
000042 ?????? ? AZ
??????
Offset address? UU.LIN-UU$MIN
Base
Offset Old
New?
??????
000041
???? Q!100
000042
???? AZ
??????
Offset address? UU.BYE-UU$MIN
Base
Offset Old
New?
??????
000042 ?????? ? Q!IOO
??????
000044 ?????? ? AZ
Offset address? UU.ATT-UU$MIN
Base
Offset Old
New?
??????
000043
???? Q!lOO
000044
???? AZ
??????
Offset address? UU.DET-UU$MIN

Seq 3.5.1 F
6 of 8

(CTRL/Z for new offset)
; FCB/WCB/DDB data function
(CTRL/Z for new offset)
; POKE function
(CTRL/Z for new offset)
; Monitor Tables I function
(CTRL/Z for new offset)
; Disable further log ins

(CTRL/Z for new offset)
; Enable logins function
(CTRL/Z for new offset)
; Create PPN function
(CTRL/Z for new offset)
; Delete PPN function
(CTRL/Z for new offset)
; Disk/Terminal functions
(CTRL/Z for new offset)
; LOGIN function
(CTRL/Z for new offset)
; LOGOUT function
(CTRL/Z for new offset)
; ATTACH function
(CTRL/Z for new offset)
; DETACH function

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
File Processor Patches
Base
Offset Old
New?
??????
000044 ?????? ? Q!100
??????
000046 ?????? ? AZ
Offset address? UU.ERR-UU$MIN
Base
Offset Old
New?
??????
000046 ?????? ? Q!lOO
??????
000050 ?????? ? AZ
Offset address? UU.ZER-UU$MIN
Base
Offset Old
New?
??????
000052 ?????? ? Q!lOO
??????
000054 ?????? ? AZ
Offset address? UU.RAD-UU$MIN
function
Base
Offset Old
New?
??????
000053
???? Q!lOO
??????
000054
???? AZ
Offset address? UU.DIR-UU$MIN
Base
Offset Old
New?
??????
000054 ?????? ? Q!100
??????
000056 ?????? ? AZ
Offset address? UU.TRM-UU$MIN
function
New?
Base
Offset Old
??????
000055
??? ? Q!lOO
??????
000056
??? ? AZ
Offset address? UU.CHE-UU$MIN
Base
Offset Old
New?
??????
000060 ?????? ? Q! 100
??????
000062 ?????? ? AZ
Offset address? UU.CNV-UU$MIN
Base
Offset Old
New?
??????
000061
??? ? Q!lOO
??????
000062
??? ? AZ
Offset address? UU.SWP-UU$MIN
Base
Offset Old
New?
??????
000064 ?????? ? Q!lOO
??????
000066 ?????? ? AZ
Offset address? UU.JOB-UU$MIN
Base
Offset Old
New?
??????
000065
??? ? Q!100
??????
000066
??? ? AZ
Offset address? UU.PPN-UU$MIN
New?
Base
Offset Old
??????
000066 ?????? ? Q!lOO
??????
000070 ?????? ? AZ
Offset address? UU.SYS-UU$MIN
Base
Offset Old
New?
??????
000067
??? ? Q!100

Seq 3.5.1 F
7 of 8

(CTRL/Z for new offset)
: Error message text function
(CTRL/Z for new offset)
: ZERO device/PPN function
(CTRL/Z for new offset)
: Read/Write accounting data

(CTRL/Z for new offset)
: Directory (index) function
(CTRL/Z for new offset)
: Terminal characteristics

(CTRL/Z for new offset)
: Disk caching control function
(CTRL/Z for new offset)
: Date/Time conversion function
(CTRL/Z for new offset)
: System file control function
(CTRL/Z for new offset)
: Job creation function
(CTRL/Z for new offset)
: PPN wildcard lookup function
(CTRL/Z for new offset)
: Job status function

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
File Processor Patches
??????
000070
??? ? "'Z
Offset address? UU.STL-UU$MIN
Base
New?
Offset Old
??????
000072 ?????? ? Q! 100
??????
000074 ?????? ? "'Z
Offset address? UU.ONX-UU$MIN
Base
New?
Offset Old
??????
000076 ?????? ? Q!100
??????
000100 ?????? ? "'C

Seq 3.5.1 F

8 of 8
(CTRL/Z for new offset)
: Stall system function
(CTRL/Z for new offset)
: Open next function
(up-arrow/C to exit: CTRL/C
for INIT)

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Device Driver Patches

Seq 3.7.1 F
1 of 2

USING THE CSS PAPER TAPE READER ON RSTS/E- DEVICE DRIVER FEATURE PATCH
PROBLEM:
The paper tape reader device driver included in the RSTS/E
library does not work with the CSS paper tape reader (PA6ll).

object

SOLUTION:
The paper tape reader driver for RSTS/E is for Digital Equipment
Corporation model PCll. The following optional patch will make the
driver compatible with the CSS paper tape reader model PA6ll.
Note
that after applying this patch, the device driver does not work with
model PCll.
PROCEDURE:
1.

This is a feature patch to the RSTS/E monitor.
It may be
installed in any target monitor SIL that supports paper tape
readers.
If this support was not" included in the monitor during
your system generation,
the patch will fail with a "Symbol not
found in STB" error after you specify .. PCSS as the Base Address.

The patch described in Step 4 below can
PATCH option of INIT.SYS:
Option: PATCH
File to patch? <cr>

installed

using

the

(RETURN for installed monitor SIL)

This patch can be installed manually
patching program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? <cr>
File found in account [0,1]

using

ONLPAT,

the

on-line

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

This feature patch is contained in the file PA0307.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.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Monitor
Device Driver Patches
4.

Seq 3.7.1 F
2 of 2

The patch is as follows:
Module name? RSTS
Base address? .. PCSS
Offset address? 0
Base
Offset Old
?????? 000000 100200
?????? 000002 ??????
Offset address? AZ
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? 100100
? AZ
(CTRL/Z for new offset)
(CTRL/Z for new base)
New?

? Q!l
? AC

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

RSTS/E V9.0 Maintenance Notebook, June 1985

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

Seq 4.1.1 F
1 of 3

SPECIAL PRINT-USING CHARACTERS - BASIC-PLUS FEATURE PATCH
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
(e.g., 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 table below:
Location
.. PUCH+O
.. PUCH+2
.. PUCH+4

Usage
Floating currency symbol
Decimal point character
Every three digits character

Default

England

France

$ (044)
. (056)
, (054)

& (046)

F (106)
, (054)
• (056)

• (056)
, (054)

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
documentation slightly incorrect,
published for users of the system.

does
render
the
PRINT-USING
an appropriate note should be

RSTS/E V9.0 Maintenance Notebook, June 1985

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

Seq 4.1.1 F
2 of 3

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:
'x
n
n.

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
option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

using

the

PATCH

(BASIC-PLUS run-time system name)

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

installed

using

ONLPAT,

the

on-line

(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.
NOTE
The patch file for this patch requires manual
editing to include installation specific parameters
before it can be successfully installed.

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 4.1.1 F

RSTS/E V9.0
BASIC-PLUS
BASIC-PLUS Patches
5.

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

3 of 3

New?

? 'f
? '
? '

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

from Step 2)
from Step 2)
from Step 2)
exit:CTRL/C

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)

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 V9.0 Maintenance Notebook, June 1985

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

Seq 4.1.2 F
1 of 2

DEFAULT SCALE FACTOR - BASIC-PLUS FEATURE PATCH
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.
SCALE factor must be between 0 and 6 inclusive.

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

using

the

default
PATCH

(BASIC-PLUS run-time system name)

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

installed

This

using

ONLPAT,

the

on-line

(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.
NOTE
The patch file for this patch requires manual
editing to include installation specific parameters
before it can be successfully installed.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
BASIC-PLUS Patches
5.

2 of 2

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

Seq 4.1.2 F

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)

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 V9.0 Maintenance Notebook, June 1985

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

Seq 4.1.3 F
1 of 2

OMITTING SCALE FACTOR WARNING MESSAGE - BASIC-PLUS FEATURE PATCH
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
option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

installed

using

the

PATCH

(BASIC-PLUS run-time system name)

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

using

ONLPAT,

the

on-line

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

This feature patch is contained ln 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)

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
BASIC-PLUS Patches
5.

Seq 4.1.3 F
2 of 2

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)

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 V9.0 Maintenance Notebook, June 1985

Seq 4.1.4 F

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

1 of 2

DEFAULT TO NOEXTEND MODE - BASIC-PLUS FEATURE PATCH
Normally, BASIC-PLUS defaults to EXTEND mode. To change this
to NOEXTEND mode, apply the patch in this article.

default

PROCEDURE:
1.

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

It may

The patch described in Step 4 can be
option of INIT.SYS:

PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

installed

using

the

(BASIC-PLUS run-time system name)

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

using

ONLPAT,

the

on-line

(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

(up-arrow/C to
for INIT)

exit~

CTRL/C

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
BASIC-PLUS Patches
5.

Seq 4.1.4 F
2 of 2

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)

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 V9.0 Maintenance Notebook, June 1985

Seq 4.1.5 F

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

1 of 2

IMMEDIATE MODE FROM .BAS FILE - BASIC-PLUS FEATURE PATCH
Normally, BASIC-PLUS does not allow immediate-mode commands to appear
in the file accessed by the "OLD" command. This m<;iy be desi::able ln
environments where this feature was used in preVlOUS verSlons 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.
be installed in any BASIC-PLUS run-time system.

It may

The patch described in Step 4 can be
option of INIT.SYS:

PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

installed

using

the

(BASIC-PLUS run-time system name)

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

using

ONLPAT,

the

on-line

(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)

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
BASIC-PLUS Patches
5.

Seq 4.1.5 F
2 of 2

(BASIC-PLUS run-time system name)

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 V9.0 Maintenance Notebook, June 1985

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

Seq 4.1.6 F
1 of 2

NO PPN'S IN CATALOG COMMAND - BASIC-PLUS FEATURE PATCH
Normally, BASIC-PLUS allows any user to list the contents of another
user's directory with the CATALOG [P,PN] command. The patch in this
article prevents BASIC-PLUS from accepting a project, programmer
number in the CATALOG command. Thus, only the user's own directory
may be listed.
PROCEDURE:
1.

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

It may

The patch described in Step 4 can be
option of INIT.SYS:

PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

installed

using

the

(BASIC-PLUS run-time system name)

This patch can be installed manually
patching program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [O,lJBASIC.RTS
File found in account [O,lJ

using

ONLPAT,

the

on-line

(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? •• CAT.
Offset address? 0
Base
Offset Old
?????? 000000 000401
?????? 000002 000006

New?
? 5064
? AC

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

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
BASIC-PLUS Patches
5.

Seq 4.1.6 F
2 of 2

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)

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 V9.0 Maintenance Notebook, June 1985

Seq 4.1.7 F

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

1 of 2

DISABLING THE CCL SYS CALL - BASIC-PLUS FEATURE PATCH
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.
Note
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).
PROCEDURE:
1.

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

It may

The patch described in Step 4 can be
option of init.sys:

PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

using

the

(BASIC-PLUS run-time system name)

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

installed

using

ONLPAT,

the

on-line

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

This feature patch is contained in the file PA0401.007 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 V9.0 Maintenance Notebook, June 1985

Seq 4.1.7 F

RSTS/E V9.0
BASIC-PLUS
BASIC-PLUS Patches
4.

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

2 of 2

New?
? UUOBAD
(up-arrow/C to exit: CTRL/C
? AC
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 cOIT@ands:
$ UNLOAD/RUNTIME_SYSTEM BASIC

(BASIC-PLUS run-time system name)

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 V9.0 Maintenance Notebook, June 1985

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

Seq 4.1.8 M
1 of 1

CLEAR I/O BUFFERS USED BY OPEN STATEMENTS
- MANDATORY BASIC-PLUS PATCH
PROBLEM:
BASIC-PLUS does not clear I/O buffers used by OPEN statements.
This
affects security, as it allows users to examine portions of memory
allocated to buffers created by the OPEN command.
SOLUTION:
This problem is corrected by a patch contained in the command file
BASIC.CMD and is automatically applied whenever you install or update
BASIC-PLUS.
Note
If you update the BASIC-PLUS runtime system while it is
installed, you must unload it before the correction will
take effect. To unload the BASIC-PLUS runtime system,
issue the command:

$ UNLOAD/RUNTIME_SYSTEM BASIC
The UNLOAD command does not remove the run-time system;
it simply instructs the monitor to reload it the next
time a job requests it.

RSTS/E V9.0 Maintenance Notebook, June 1985

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

Seq 4.1.9 F
1 of 2

FORCE "ILLEGAL STATEMENT" ERROR WHEN USING OBSOLETE SEND/RECEIVE
- BASIC-PLUS FEATURE PATCH
PROBLEM:
Send/Receive SYS call 18 (SYS(CHR$(6%)+CHR$(18%)+ ..• ) in BASIC-PLUS is
obsolete and should not be used. New applications should use SYS call
22 for all send/receive functions.
SOLUTION:
The patching procedure detailed in Step 4 will cause BASIC-PLUS to
generate
an
"?Illegal
Statement" error whenever the obsolete
Send/Receive SYS call (SYS(CHR$(6%)+CHR$(l8%)+ .... ) is used.
This
patch will help to identify programs which use this obsolete SYS call
so they may be changed to the new format Send/Receive SYS call
(Refer
to RSTS/E Programming Manual for information).
Note
Some programs in the OPSER (Operator Services and
Spooling) package still use SYS call 18 for send/receive
functions.
You should not apply this feeature patch if
you are still using the OPSER package. The Print/Batch
Services package does not use SYS call 18.
PROCEDURE:
1.

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

It may

The patch described in Step 4 can be
option of INIT.SYS:

PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

using

the

(BASIC-PLUS run-time system name)

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

installed

using

ONLPAT,

the

on-line

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

RSTS/E V9.0 Maintenance Notebook, June 1985

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

Seq 4.1.9 F
2 of 2

This feature patch is contained in the file PA0401.009 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? .• S18.
Offset address? 0
Base Offset Old
?????? 000000 111302
?????? 000002 ('\1 ('\,)IIC.

New?
? 104771

V..LV~""%V

(up-arrowie to exit;
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)

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 V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.1 N
1 of 4

THE BASIC-PLUS DEBUG FACILITY
A feature of BASIC-PLUS, the DEBUG facility, is available with RSTS/E
as an unsupported feature,
and may be changed or removed in future
versions of BASIC-PLUS.
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:
- 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 1S
hit.
Any DEBUG commands are disabled when:
- A "RUN <program-name>" command is successfully executed
- A NEW, OLD, or EXIT command is executed
- Any valid CCL command is executed
The keywords used with the DEBUG facility have been implemented with
the second character of each keyword changed to a question mark ("?").
The patch described in article Seq 4.10.3 F may be used to change the
question marks to the characters required to make the keyword names
match the names of their respective functions (for example, "T?ACE" is
changed to "TRACE"). Note that, if this patch is applied, any program
with a variable or function name that represents a variant of TRACE,
UNTRACE, BREAK, or UNBREAK (such as TRACE%, FNBREAK$, etc.) will not
compile until the variable name is changed.
For the purposes of this discussion, assume that the patch described
above has been installed.
If you include the DEBUG features,
but
choose not to install the patch,
replace all occurrences of the
keywords below as follows:
With
Patch
TRACE
UNTRACE
BREAK

Without
Patch
T?ACE
U?TRACE
B?EAK

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 4.10.1 N

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features
UNBREAK

2 of 4

U?BREAK

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
command.

invocation

the

TRACE

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 [ N1, N2, N3 ••• , N10 ]
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 (if enabled, see article
Seq 4.10.2 N), or execute any other legal command.
Type "CONT"
{continue} to resume execution.
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.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.1 N
3 of 4

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

FOR statements

NEXT statements

DEF statements

FNEND statements

DATA 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 V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.1 N

4 of 4

SUPPORT POLICY FOR THE BASIC-PLUS DEBUG FEATURE
DIGITAL makes no commitment, expressed or implied,
to support the
BASIC-PLUS run-time system, or any BASIC-PLUS System programs (CUSPs)
used with that run-time system, if the DEBUG feature is enabled in the
BASIC-PLUS run-time system.
If you experience problems with the DEBUG feature, please submit an
FYI-type (priority 5) Software Performance Report (SPR). While making
no commitment to fix problems reported with the DEBUG facility,
DIGITAL would like to know about any problems that you encounter.
ENABLING THE DEBUG FACILITY
The DEBUG facility requires approximately 160
(decimal)
additional
words
in the BASIC-PLUS 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 include the DEBUG facility
in your BASIC-PLUS run-time system,
append "/D" to the name you select at the "BASIC-PLUS RTS name ?"
query.
For example:
BASIC-PLUS RTS name ? <BASIC> BASIC/D

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.2 N
1 of 2

THE BASIC-PLUS DUMP FACILITY
A feature of BASIC-PLUS, the DUMP facility, is available with RSTS/E
as an unsupported feature,
and may be changed or removed in future
versions of BASIC-PLUS.
The keyword D?MP has been implemented to write a post-mortem dump to
the specified file on a random-access device if the patch described in
article Seq 4.10.4 F is installed. To change the keyword to DUMP,
also install the patch described in article Seq 4.10.6 F. Note that,
if this patch is installed, any program with a variable or function
named DUMP, DUMP%, DUMP$, FNDUMP(), etc. will not compile until the
name of the variable is changed.
For the purposes of this discussion, assume that the patch described
above has been installed.
If you enable the DUMP facility, but choose
not to install this patch, replace all occurrences of "DUMP" with
"D?MP" in the discussion below.
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. After 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 (i.e.,
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
Wildcards are
is ".PMD". There is no default for the file name.
illegal.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.2 N
2 of 2

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>
The DUMP facility has not been implemented as a standard feature
because it could be used to obtain confidential information, such as
student grades or payroll information, in applications where a user
could type CTRL/C and examine the contents of buffers and variables.
If the feature is enabled, however, there are two mechanisms available
to protect against this kind of situation:
- Non-privileged users are normally prevented from using the DUMP
command on programs that are running from compiled files.
This
restriction may be removed if desired (see article Seq 4.10.5 F).
- 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 run-time system, one for development and one for
production. This would prevent the potential problems described
above, while providing the DUMP feature for development work.
SUPPORT POLICY FOR THE BASIC-PLUS DUMP FACILITY
DIGITAL makes no commitment, expressed or implied,
to support the
BASIC-PLUS run-time system, or any BASIC-PLUS System programs (CUSPs)
used with that run-time system, if the DUMP facility is enabled.
If you experience problems with the DUMP feature,
please submit an
FYI-type (priority 5) Software Performance Report (SPR). While making
no commitment to fix problems reported with the DUMP facility, DIGITAL
would like to know about any problems that you encounter.

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 4.10.3 F

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

1 of 2

CHANGING THE BASIC-PLUS DEBUG KEYWORDS - BASIC-PLUS FEATURE PATCH
PROBLEM:
If support for the DEBUG facility has been included in the BASIC-PLUS
run-time system, the keywords BREAK, TRACE, UNBREAK, and UNTRACE are
initially enabled with the second character of the keyword changed to
a question mark ("?"),
for example, B?EAK, T?ACE, U?BREAK, and
U?TRACE.
SOLUTION:
The following patching procedure will replace the question marks with
the correct characters,
thus changing the keywords to BREAK, TRACE,
UNBREAK, and UNTRACE.
NOTE
If this patch is installed, any program with a variable
or function name of one of these keywords, such as
BREAK% or FNTRACE$, will fail to compile until the
variable name has been changed.
PROCEDURE:
1.

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

It may

The patch described in Step 4 can be
option of INIT.SYS:

,PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

using

the

(BASIC-PLUS run-time system name)

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

installed

using

ONLPAT,

the

on-line

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

This feature patch is contained in the file PA04l0.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.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features
4.

2 of 2

The patch is as follows:
Base address? • .BEA.
Offset address? 0
Base
Offset Old
?????? 000000
077
?????? 000001
???
Offset address? "'Z
Base address? · .TAC.
Offset address? 0
Base
Offset Old
7?7??? 000000
077
?????? 000001
???
Offset address? "'Z
Base address? • .UBR.
Offset address? 0
Base
Offset Old
?????? 000000
077
?????? 000001
???
Offset address? "'Z
Base address? • . UTR.
Offset address? 0
Base
Offset Old
?????? 000000
077
?????? 000001
???

Seq 4.10.3 F

New?
? 'R
? "'Z

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

New?

? ;R

? "'Z

New?
? 'N
? "'Z

New?
? 'N
? "'C

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

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

(BASIC-PLUS run-time system name)

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 V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.4 F
1 of 2

ENABLING THE BASIC-PLUS DUMP FEATURE - BASIC-PLUS FEATURE PATCH
PROBLEM:
The (unsupported) BASIC-PLUS "DUMP" feature is initially disabled.
Some installations may choose to enable this feature, even though it
is unsupported.
(See article Seq 4.10.2 N for a complete description
of the DUMP feature. See article Seq 4.10.6 N to change the keyword
from "D?MP" to "DUMP".)
SOLUTION:
The following patching procedure will enable the DUMP feature.
PROCEDURE:
1.

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

It may

The patch described in Step 4 can be
option of INIT.SYS:

PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

using

the

(BASIC-PLUS run-time system name)

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

installed

using

ONLPAT,

the

on-line

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

This feature patch is contained in the file PA04l0.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.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features
4.

2 of 2

The patch is as follows:
Base address? •. PMD.
Offset address? 0
Base
Offset Old
?????? 000000 104755
?????? 000002 ??????

Seq 4.10.4 F

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

If this patch was installed using ONLPAT, i.t will take effect the
next time THE run-time system is reloaded.
If the run-time system
h.::llc
4 4 ..... t...I

hoon

AJ",-""' • •

Tl\T<::fTlllT.T.H'n

........ ..., . . 4~ ..... -... ...... 4t."

ovo,..,,+o
"-4'-,.".'-' ..... """'--

fTlUH'
... .& ... ......,

$ UNLOAD/RUNTIME SYSTEM BASIC

f"1"\1 1 nl.T; l"'In
'!J

... ....., . . . . . . ' " ' ....... .I ...

"'I"\mm.::lll"'l~c.
""",",&"U'''\,.A''&\",A.~.

(BASIC-PLUS run-time system name)

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 V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.5 F
1 of 2

ENABLING DUMP FROM COMPILED FILES FOR NON-PRIVILEGED USERS
- BASIC-PLUS FEATURE PATCH
PROBLEM:
Normally, if the DUMP feature is enabled (see article Seq 4.10.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.
SOLUTION:
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
non-privileged user can never DUMP such a program.)
PROCEDURE:
1.

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

It may

The patch described in Step 4 can be
option of INIT.SYS:

PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

using

the

(BASIC-PLUS run-time system name)

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

installed

using

ONLPAT,

the

on-line

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

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.5 F
2 of 2

This feature patch is contained in the file PA04l0.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? .. NPD.
Offset address? 0
Base
Offset Old
?????? '000000 004767
??????

??????
6.

??????

000004

005046

New?
? NOP
? NOP
? 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)

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 V9.0 Maintenance Notebook, June 1985

Seq 4.10.6 F

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features

1 of 2

CHANGING THE BASIC-PLUS D?MP KEYWORD - BASIC-PLUS FEATURE PATCH
PROBLEM:
The DUMP command, which is disabled unless the patch described in
article Seq 4.10.4 F is installed, has been implemented with the
keyword "D?MP." Some installations may desire to change this keyword
to "DUMP."
SOLUTION:
The following patching procedure will change the keyword "D?MP" to
"DUMP." If this patch is installed, please note that any program which
uses a variable or function name such as DUMP% or FNDUMP$, will not
compile until the variable name is changed.
PROCEDURE:
1.

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

It may

The patch described in Step 4 can be
option of INIT.SYS:

PATCH

Option: PATCH
File to patch? BASIC.RTS
3.

using

the

(BASIC-PLUS run-time system name)

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

installed

using

ONLPAT,

the

on-line

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

This feature patch is contained in the file PA04l0.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.

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 4.10.6 F

RSTS/E V9.0
BASIC-PLUS
Non-standard BASIC-PLUS Features
4.

The patch is as follows:
Base address? .. DMP.
Offset address? a
Base
Offset Old
New?
?????? 000000
077? 'u
?????? 000001
???? AC

2 of 2

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

If this 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 cOIT@ands;
$ UNLOAD/RUNTIME_SYSTEM BASIC

(BASIC-PLUS run-time system name)

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 V9.0 Maintenance Notebook, June 1985

Seq 5.1.1 M

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

1 of 1

BUFFER LIMIT CHECKING - MANDATORY 2780 DEVICE DRIVER PATCH
PROBLEM:
The RSTS/E extended buffering scheme in effect since V06B obsoletes
the buffer limit checking code in the 2780 device driver. This buffer
limit checking code was removed from the DUll/DUPll version of the
driver, but was left in the DP1l version. Certain valid buffer
addresses will cause the DPll version to fail.
SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This patch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
Note
This patch will fail when applied to a monitor that is
not configured to include DPll devices.
For further details on how to generate a RSTS/E
RSTS/E System Installation and Update Guide.

monitor,

see

the

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

Seq 5.1.2 M
1 of 1

DISCONNECT COMMAND HANDLING - MANDATORY 2780 DEVICE DRIVER PATCH
PROBLEM:
If the 2780 device driver receives a disconnect command (DLE EOT) ,
it
mistakenly releases its buffers and line table. A subsequent close
will cause modification of critical monitor memory.
A system crash
may occur thereafter.
SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This patch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
For further details on how to generate a RSTS/E monitor, see the
RSTS/E System Installation and Update Guide.

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 5.1.3 M

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

1 of 1

DPll TRANSMIT HANG CONDITION - MANDATORY 2780 DEVICE DRIVER PATCH
PROBLEM:
Under certain load conditions, when the 2780 package issues the error
'Send Error - Transmit Hang - Redial Required', critical locations in
the monitor can be modified. This will cause a subsequent system
crash.
SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This patch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
Note
This patch will fail when applied to a monitor
not configured to include DP1l devices.

that

For further details on how to generate a RSTS/E monitor, see the
RSTS/E System Installation and Update Guide.

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 5.1.4 M

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

1 of 1

DU11/DUP11 TRANSMIT HANG CONDITION
PATCH

MANDATORY

2780

DEVICE

DRIVER

PROBLEM:
Under certain load conditions, when the 2780 package issues the error
'Send Error - Transmit Hang - Redial Required', critical locations in
the monitor can be modified. This will cause a subsequent system
crash.
SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This patch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
Note
This patch will fail when applied to a monitor that is
not configured to include DUl1/DUPl1 devices.
For further details on how to generate a RSTS/E
RSTS/E System Installation and Update Guide.

monitor,

see

the

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

Seq 5.1.5 M
1 of 1

LOSS OR DUPLICATION OF DATA - MANDATORY 2780 DEVICE DRIVER PATCH
PROBLEM:
Occasionally the loss or duplication of data occurs.
There is
indication from the 2780 package that any trouble had occurred.

SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This p~tch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
For further details on how to generate a RSTS/E
RSTS/E System Installation and Update Guide.

monitor,

see

the

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

Seq 5.1.6 M
1 of 1

DOUBLE CLOSE ALTERS MONITOR - MANDATORY 2780 DEVICE DRIVER PATCH
PROBLEM:
The 2780 Device Driver does not protect itself against closing the RJ:
device twice in all cases. A double close can alter monitor memory
and cause a system crash.
SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This patch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
For further details on how to generate a RSTS/E monitor, see the
RSTS/E System Installation and Update Guide.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

Seq 5.1.7 M
1 of 1

GET/PUT INTERLOCK PROBLEM - MANDATORY 2780 DEVICE DRIVER PATCH
PROBLEM:
Due to timing considerations on systems with zero turn-around delay,
it is possible for a bid from a remote unit to be processed before the
completion of the routine for End Of Transmission.
This causes the
driver to receive the bid when it "thinks" it is in transmit mode and
the GET/PUT INTERLOCK error is triggered.
SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This patch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
For further details on how to generate a RSTS/E monitor, see the
RSTS/E System Installation and Update Guide.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

Seq 5.1.8 M
1 of 1

2780 HANDLER FAILURE PROBLEM - MANDATORY 2780 DEVICE DRIVER PATCH
PROBLEM:
When the RSTS/E system is under heavy load, it is possible for the
notification of the receipt of a bid to be passed back with a receive
buffer address of zero. When the driver attempts to requeue the
buffer, it is considered a fatal error.
SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This patch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
For further details on how to generate a RSTS/E monitor, see the
RSTS/E System Installation and Update Guide.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Patches

Seq 5.1.9 M
1 of 1

LOCAL BINARY TRANSMIT PROBLEM - MANDATORY 2780 DEVICE DRIVER PATCH
PROBLEM:
If the default transmit command is 2780 or GEN, it should be possible
to send, as part of a multiple file transfer, a file or files in
binary mode. This is done by using the "/B" switch to override the
transmit command for those files which should be sent untranslated.
Currently, the mode of the first file controls the mode for the
complete transfer.
SOLUTION:
This problem is corrected by a patch contained in the file RJ2780.CMD
in the SYSGEN$ account. This patch is automatically applied whenever
you generate a RSTS/E monitor that includes support for the RJ2780
package.
For further details on how to generate a RSTS/E monitor, see the
RSTS/E System Installation and Update Guide.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Notes

Seq 5.2.1 N
1 of 8

INSTALLING AND TROUBLESHOOTING 2780'S
Installing a communication package involves a minimum of two vendors
and more likely three or four.
The most time-consuming aspect of
installation can be pinpointing a problem.
When installing A to
communicate with B, the problem may be in one of seven areas:
A's software (either code or SYSGEN parameters)
- A's hardware
- A's modem
- Phone line
- B's modem
- B's hardware
- B's software
Sometimes a given symptom can have several possible causes. Then it
is necessary to go through a step-by-step elimination procedure.
Here are some ideas and suggestions which may be
difficulties arise in installation of 2780 packages.
1.

helpful

when

What is a 2780 and what is its protocol?

For those who are unfamiliar with what a 2780 emulator is emulating,
here is a short description of what it is and what its protocol is
like.
The 2780 is an unintelligent, hard-wired
terminal
which
can
communicate to an IBM host or to another 2780.
It reads cards and
transmits them over a synchronous link to another computer.
It
receives data back and prints it. The model 2 2780 can also receive
back data for a card punch.
The 2780 sends 80 character card image records, blocked into a maximum
of a 400 character block. For reception, it prints or punchs a file
according to a peripheral selection code (basically, an ESC 4 sends a
file to the punch).
It is able to accept horizontal tabs and handles
them according to the spacing of a special HT record which is sent at
the beginning of the file.
The block size is again a maximum of 400
characters.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Notes

Seq 5.2.1 N
2 of 8

A synchronous protocol is used to enable the data to be sent back and
forth.
The protocol determines who speaks, when, and whether or not
the other end heard them correctly.
When there is synchronous
communication, the two modems sample the line at a preset speed (2000
times a second or 4800, etc.), and the data is sent in blocks with one
character directly following another.
Every message~ therefore,
whether a single control character or a 400 character block is
preceded by four SYNC characters and followed by a PAD. The SYNC
characters are used to allow the hardware to tell when valid data is
coming (as opposed to noise on the line), and the PAD is used to make
sure that the final significant character is fully received.
Every
data record sent has a CRC (cyclic redundancy check) computed on its
characters, and following each record and block (IUS, ETB, and ETX) is
a two-character checksum which is used to make sure the data was
received correctly.
The major control characters used in the 2780 protocol are:
ENQ

(enquiry):

(1) Used to request permission to send
data (bid);
(2) Used to request resending of a
missed response.

ACKO (acknowledge):

( 1) Used to give permission to send
data:
( 2 ) Used to accept every other data
block.

ACK1 (acknowledge):

Used to accept every other data block.

NAK

(negative acknowledge):

Used to reject a data block.

STX

(start of text):

Used to indicate
data block.

ETB

(end of block):

Used to indicate the
block.

ETX

(end of text):

Normally used to indicate the end of
the final block of the job.

IUS

(intermediate record end): Used to indicate the end of a

EOT

(end of transmission):

the beginning of a
end

Used
to
indicate
transmission and give up
line.

data

record.

completed
control of

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Notes

Seq 5.2.1 N
3 of 8

A sample job might be sent as follows:
A

ENQ -->

;request permission to send
<-- ACKO

STX DATAl ETB -->

;permission given
;block of data

<-- ACKl

STX DATA2 ETB -->

;acknowledge correct reception
;another block

<-- ACKO

STX DATA3 ETB -->
<-- NAK

STX DATA3 ETB -->

;rejection of data
;resending of data block

<-- ACKl

STX DATA4 ETX -->
ENQ -->

;.3 second silence request for response
<-- ACKl

STX DATA4 ETX -->

;response shows did not see block,
since an ACKO is the expected
response for DATA4
;block re-sent

<-- ACKO

EOT -->

;transmission complete
<-- ENQ

;other side requests permission to
send data

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Notes
2.

Seq 5.2.1 N
4 of 8

What to check before installation of the software.

There are some questions to be asked before 2780 installation.
What operating system will you be communicating with? If it is not
another PDP-II, is it one of the usual
IBM systems?
If
it
is a
different system (for example, a Univac 1108 with a Comterm front end
or an RPG program running on a System 3, etc.) has a demo test been
done with the system, and what problems, if any, were encountered?
What kind of moderns are being used?
If they are not identical, are
they compatible.
If they are the same type, are the options the same
on both?
If
it
is a local connection are modern eliminators being
used, or are null modems being used? Null moderns require a clocking
option on the computer hardware to provide transmit clocking.
Are the
moderns for a speed higher than is warranted by the software?
RSXIlM,
RSXllD, and RSTS/E are not warranted to work over 4800 baud.
Make sure that the modern has been grounded on the same ground as the
hardware.
The communications interface and many moderns can be
affected by being plugged into a device which is grounded differently.
Is the DPll, DUll, or DUPll the furthest forward device on the bus
(except the system disk) which operates at hardware level 5? If there
is a DRll or DZll on the system, it will probably be necessary to
raise the hardware level of the communications interface to 6. This is
because the DRll often is programmed to remain at
interrupt level
until the silo is emptied (the DZll has no silo and must interrupt per
character).
Have the diagnostics been run for the communications interface and the
KGll? The DP,
DU, or DUP should be checked out with the turn-around
plug at the end of the modem cable or with the modern in maintenance
mode.
Two manuals are shipped with the 2780 software. They are the 2780 RCS
Users Guide* and the 2780 RCS Installation Notes
(DEC-ll-CCDNA-A-D).
Relevant chapters should be read in advance of installation.
There
will be some overlap between this article and the manuals, but in many
ways they should complement each other.

* DEC-ll-ORJEA-B-D is for RSTS/E 2780 only.
DEC-II-CRCSA-A-D, DNl, DN2, DN3, and DN4 are for the other 2780's.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Notes
3.

Seq 5.2.1 N
5 of 8

Initial attempt to run

One of the more frustrating circumstances is to bring up the package,
issue a transmit command, and have it do absolutely nothing. Silence,
however, can be just as informative as a message.
This section will itemize the things that can go wrong in the sequence
in which they would be encountered.
It is specified when systems
react in different ways.
The systems involved are RTll, RSXI1M,
RSXI1D, and RSTS/E.
a.

Run the program for the first time and
(1) there is a trap to 4 in RTll and RSTS/E
(2) there is an odd address trap abort in RSXIIM or D

Probably the device address of the DUll or DUPll is incorrect.
They
are floating device address devices.
Check that the device was
installed at the correct address (for example, if the DUll is the only
floating device on the system it will be at 760040, if the DUPll is
the only floating device it will be at 760050) and also that the
system was told the same address.
RSTS/E calculates the address
during boot, RTll, RSXIIM and D have it specified during taskbuild.
The KGll may also be missing. This is the hardware CRC calculator.
If it is missing the software cannot run.
b. Run the program and get ready to make the connect to the other
system.
Dial the phone, receive the beep from the other end, and
push (or pull) the data button and
(1) the data light does not corne on
(2) the DSR (or MR) indicator does not light.
Usually a dial-out modern will not give DSR (data set ready) until DTR
(data terminal ready)
has been presented by the communications
interface
(1) check that the light is not just burned out
(2) check that you have put the system on-line (all systems
but RSTS/E)
(3) check that the DTR bit is on in the status word
(4) check that a valid but incorrect device address was not
used (RTll, RSXllM and D)
(5) check that the hardware diagnostics were run,
including
the one using the modern cable.
(6) check that the cable is securely plugged into the modern
With a leased line,
the modem often has DSR strapped on.
In that
case, this type of error may not be discovered until later in the
procedure (see c. and d.). There are now some dial-out moderns (for

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Notes
example, some MILGO modems) which have DSR strapped
will react the same as the leased line modems.

Seq 5.2.1 N
6 of 8
on

also.

They

The program has been run and the connection established; a
transmit transfer command is issued and a modem (or data set)
not ready message is given.
(1) the data set is not ready (for example, DSR is not up)
(2) a valid, but incorrect, device address has been used.

This is at the same stage as c. The first transmit command has
been issued, but nothing happens. There are several possible
causes.
(1) Incorrect interrupt vector (RSX11M and D). Since in these
systems interrupt vector is specified at build time, check
that it corresponds to the actual hardware vector.
(2) No response to the bid (RT11, RSX11M and D). These systems
do an infinite retry on the bid if they get no response.
(RSTS/E does a timeout). Unfortunately, this cause is
really a symptom with mUltiple causes of its own.
Some
possibilities are:
(a) the remote end software is not up (usually leased
line) or the connection was not made (a dial-out modem
with DSR strapped on).
(b) the modems have different speeds (for example, 2000
baud talking to 2400).
(c) the modem is not sending out the signal (this can
usually be checked by finding out whether the other
side has seen the bid).
(d) the other end is responding, but the turn-around time
is too fast (usually on a two-wire dial-out system
where there are echo suppressers on the line).
(e) the other end is responding but the modem either does
not see it (receive strength too low) or the modem
does not pass it back (bad receive leads on the
modem), or our hardware does not see it (bad receive
chip or modem cable
this should be caught by
diagnostics or actual zero turn-around delay (see
f •))•

To determine whether or not the bid is actually being sent
out, check the receive end to see if it has gone into receive
mode. If it is in receive mode, but the transmitting side is
still in control mode, the bid is being seen but the response
is not (or the response is not considered valid).

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Notes

Seq 5.2.1 N
7 of 8

A transmit command is given and the program aborts.
In RTll
if the wrong interrupt vector has been specified, the program
is aborted and the monitor reprompts. In RSXllM if the 2780
is running in a partition that can be 'shuffled' the program
may have been moved. This will have completely unpredictable
effects, since the interrupt will jump to where the correct
code used to be.

When attempting to transmit there are frequent transmit abort
errors. Each system has its own version of the error message,
but they all indicate that either eight attempts to send a
data block were NAKed, or eight attempts to get a valid
response were ignored.
On RSTS/E V06B and later releases, a status request will show
whether the data is being NAKed or timed-out. In the other
packages an error request will show the number of NAKs. If the
transmit is aborting, but there are few or no NAKs the problem
is timeouts.
If the first block is not being accepted, the KGll may not be
working correctly. If it is improperly seated the program may
be sending out a CRC of zeros. This should be easily caught
by diagnostics.
On a multi-user system the package should not be run at a
higher speed than is warranted.
On a multi-user system with a DHll or DZ11, the communications
interface should be at hardware bus request level 6.
Other possibilities
delays, bad modems,
lines.

are:
modems with different turn-around
incompatible modems, and noisy phone

If there is an actual zero turn-around delay (not just a modem
with no delay, but a system with a front-end which is capable
of responding without any processing delays) it is possible to
have the response return while our hardware is sending
trailing
pads.
Either a mlnImum delay time should be
installed or the number of trailing pads should be decreased.
g.

Transmit works fine, but files cannot be received.
Most of the suggestions for f. should be checked. Two of the
most likely ones are running at too high a speed for the
system, or having the communication interface at level 5 on a
system with high DHll or DZll load.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Device Driver
2780 Device Driver Notes

Seq 5.2.1 N
8 of 8

If no data from the other side is accepted at all it is quite
possible that the other system is SYSGEN'd to support either a
3780 or a HASP Workstation instead of a 2780. Our data will be
acceptable to their side,
since the 2780 is, in effect, a
subset of the other two.
In both cases, the data block can be
too long (they will both send up to 512 characters and the
2780 can only accept 400) and the CRC calculations are done on
the complete block instead of on each record. The usual
indication is that we consistently NAK the very first block
that they attempt to send to us.
If the other side is SYSGEN'd as a 2780, but is sending too
long a record (over 132 data characters plus a two character
escape sequence) most of our packages will now accept the
record and truncate it
(as long as there were no other
problems with the data). The user will be informed as to the
number of truncated records at the end of the reception.
h.

The package has been transmitting and receiving without
difficulty.
It is in the middle of transmitting and all
activity stops. The package is in transmit mode, but nothing
is going out.
This is usually caused by losing DSR on a modem which will not
give CTS (clear to send) to a RTS (request to send) if DSR has
been lost (for example, BELL 208B modems). Check the modem,
and if this is correct, try to push the talk button and then
the data button to try to re-establish the connection.
If
that does not work you will have to redial. RSTS/E V06B (and
later releases) will timeout in 30 seconds and terminate
transmit.
The other packages will not terminate
until
operator intervention has taken place.

Installation is complete when the program has been brought up, a
connection made, and files transmitted and received.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Error Control Package (ERROR$)
Package Notes

Seq 12.1.1 N
1 of 2

UNDERSTANDING "PA MEMORY SYSTEM" ERROR LOGS
The following information is logged when a memory error causes a
trap or an instruction abort. These logs can be recognized by the
fact that "MEM ERR" is not zero.
CACHECTL

This is the data RSTS/E sets into the Cache Control Register
(777746).
It is meaningless for systems without cache
memory.

ADDR LSB

These words contain the address of the word in memory
failed.

ADDR MSB

On the PDP-ll/70,
they are the contents of the Low Error
Address Register (777740) and High Error Address Register
(777742). Bits <15:14> of ADDR MSB indicate the cycle type
of the failure.
On other processors, these words are
assembled from the other logged information.

MEM ERR

On processors with cache, this is the contents of the Memory
System Error register (777744). On other processors, this
word always contains 100000 (CPU Abort, no cache error).
If
the same cache group fails twice in the same minute, that
cache group will be disabled.

which

The remaining registers are not logged on the 11/70, which does not
have accessible memory CSRs.
In any case, they are not meaningful
unless the error occurred in main memory.
CSR

This is the address of the CSR which indicated an error.

(CSR)

This is the contents of that CSR. A second entry is also
printed for an MSIIM or MSl1L with the extended address
function selected.

K Range

This tells how finely the CSR contents can resolve the
location of the error. For all current memory controllers
(MFII-LP, MFII-UP, MFII-WP, MFl1S-K, MMII-DP, MMII-YP,
and
MSIl-JP), this value is 1, indicating that the CSR locates
the error to within lK words.
For older semiconductor
memory controllers (MSll-AP, MSll-BP, and MS1l-CP) that do
not provide the address of the error in the CSR, this value
is the number of lK-word blocks (up to 31.) controlled by
the CSR.

# Fail

When it discovers a CSR announcing an error, RSTS/E looks
through all memory in the range of the error (see above) to
find which words actually have errors.
Thus,
for
a

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Error Control Package (ERROR$)
Package Notes

Seq 12.1.1 N
2 of 2

controller which resolves the error location to within 1words, RSTS/E checks 1024. words (or 512. if the memory is
interleaved). This word tells how many words in the range
had an error indication.
Base Adr

To get the physical address of the start of the range
mentioned above,
add two zero digits (six bits) to this
value.

Fail #n

The next words in the error log tell which words in the
given range actually have errors. The addresses are given
as byte offsets from the base given above. Up to five such
offsets may be logged.

Once a second, except on II/70's, RSTS/E checks all memory CSRs for
errors that do not cause traps or aborts. The logs for these errors
can be recognized by the fact that "MEM ERR" is zero.
These errors
include uncorrectable errors detected on NPR cycles, and correctable
(single-bit) ECC errors. Uncorrectable errors are logged whenever
they are detected, but only one correctable error will be logged for
each CSR, for each time RSTS/E is started. When a correctable error
is logged, only the CSR address and CSR contents will be meaningful.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Operator Services and Spooling Package (OPSER$)
Package Notes

Seq 14.1.1 N
1 of 2

NOTES ON THE USE OF THE SERIAL LA180 (LA180S) TERMINAL
The first part of this article describes the behavior of the Serial
LA180 terminal
(called the LA180S) when its power is turned off,
either at system start-up time or at some later time
during
timesharing, and makes recommendations to prevent loss of data.
If any terminal (including an LA180S) is powered off when the system
is booted,
the device appears to the system to be operational.
If a
user tries to print a file on the terminal,
the system will send
characters to the device at the usual speed and assume that they are
being printed properly. Obviously, since the device is powered off,
the characters are not being printed, but the device cannot return any
indication of that fact to the system. The entire file will be sent
as if it were printing.
If a spooler is started on such a KB:
line, any files queued to that
spooler will be sent, just as if the device were printing properly.
The queue will gradually empty, and any files queued with /DELETE will
be deleted.
Since there is no method by which the software can differentiate
between a terminal which is powered off and one which is printing
properly, it is highly recommended that the person starting up a
RSTS/E system check to ensure that all terminal devices which are
ordinarily spooled are powered on and properly online before system
start-up is'performed.
A second class of problems involves the behavior of the LA180S when it
is powered off or powered on after it has been ALLOCATEd or OPENed.
During its,power down and power up sequence, the LA180S terminal may
send spurlOUS 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, CTRL/C). 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: a CTRL/C may cause the program to exit;
a CTRL/O will cause
all further output to be discarded without printing;
and so on.
There is no way for the software to protect against all possible
spurious inputs. RSTS/E is able to protect against all spurious input
except CTRL/S (XON) and CTRL/Q (XOFF) via the MODE 32% option on the
OPEN statement. However, spurious XON/XOFF 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 the LA180S is never
powered off or powered on while it is ALLOCATEd or OPENed.

RSTS/E V9.0 Maintenance Notebook, June 19S5

RSTS/E V9.0
Operator Services and Spooling Package (OPSER$)
Package Notes

Seq 14.1.1 N
2 of 2

A final problem concerns loss of data when the LAISOS is powered off.
The LA1SOS contains 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 LAISOS 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
terminal 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 LAISOS is not powered off while it is
-nrinrinrr
1::'- _ •• ,,_ .... '::J.

In summary, DIGITAL recommends that any LA1SOS terminal 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 an
LA1SOS. 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 LA1SOS, 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 LAISOS also generates
a
line-feed, causing spacing to a new line. Since most print lines are
terminated by a CR/LF 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 LAISOS (for example, longer
than 132 characters) will cause a blank line on the printed output .
. p When performing normal print operations under RSTS/E, the user will
not ordinarily encounter this problem. The RSTS/E Terminal Service
ordinarily keeps track of the characters printed on the terminal and
explicitly issues a CR/LF 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 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 CR/LF 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 V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
Operator Services and Spooling Package (OPSER$)
Package Notes

Seq 14.1.2 N
1 of 1

USING TWO OR MORE PRINTERS TO SERVE A QUEUE

It is possible to have two or more printers serve a single print
queue.
For example, you can have two printers serve the LPO: queue,
which is the default queue. Ordinary print jobs (those queued to
LPO:) would be printed on either printer.
This feature is most useful when you have two or more similar printers
in the same vicinity.
It is not generally useful to have a fast and a
slow printer serve the same queue,
nor to have two printers In
different locations serve the same queue.
A different form can be mounted on each printer.
If this is done,
spooling package will automatically select the printer that has
correct form for a particular job. Or, if the correct form is
mounted on any available printer, the spooling package will hold
job.

the
the
not
the

Start up each spooler by running the SPOOL program,
as discussed in
the RSTS/E System Manager's Guide. Specify the same queue name for
each -- for example, specify LPO: if the spoolers are to serve the
LPO: queue.
But you must use the /NAME:rcvrid switch to ensure that
each spooler is given a different receiver ID. Otherwise,
the SPOOL
program will print the message "?Duplicate receiver ID."
In the following example, the devices LPO: and
queue named LPO:.

LPl:

both

serve

the

RUN OPSER$:SPOOL
#LPO:/NAME:LPO/PHYSICAL:LPO:
Detaching ...
RUN OPSER$:SPOOL
#LPO:/NAME:LP1/PHYSICAL:LP1:
Detaching ...
To avoid confusion, a queue should not have the same name as a printer
that serves another queue.
For example, if queue LPO:
is served by
printers LPO: and LPl:, then you would not want to name another queue
LPl:.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
DCL
Package Notes

Seq 20.1.1 N
1 of 1

FILE SPECIFICATIONS IN DCL
The rules about file specifications
restrictive than elsewhere in RSTS/E.

DCL

are

The special PPN character "I" does not work in DCL.
point is used as the comment delimiter.

slightly
The

exclamation

The special PPN characters "@", "%", "&", and "I" are accepted in the
current version, but their use is not supported. They are reserved
DCL characters, and may have other meanings in the future.
The special PPN character "$" is legal and supported in DCL.
continue to designate the system library [1,2].

will

The traditional RSTS/E file specification switches /MODE, /SIZE, and
/RONLY cannot be used in DCL. Many of the same features are available
through DCL, but you must use DCL notation. Protection codes in angle
brackets ("<nn>") cannot be used in DeL.
The DCL syntax for
protection codes is "/PROTECTION:nn".
Parentheses ("C)") cannot be used to delimit the project-programmer
number of a file in DCL.
Brackets ("[]") must be used instead.
Parentheses are reserved DCL characters.
The single-character wildcard "?" works in DCL, but it is unsupported.
It may have a different meaning in the future.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
DCL
Package Notes

Seq 20.1.2 N
1 of 7

SETTING UP THE DCL LINK COMMAND
This article explains how to set up your system so that the DCL LINK
command can be used.
If you intend that the LINK command will be
used, you should read this article before you install any layered
languages.
Other aspects of setting up DCL are described in the
RSTS/E System Installation and Update Guide and the RSTS/E System
Manager's Guide.
The DCL LINK command provides a simple way of linking programs.
It
lets you link programs in two RT11-based languages (FORTRAN-IV and
MACRO-II) and five RSX-ll-based languages (BASIC-PLUS-2, COBOL-8l,
DIBOL, FORTRAN-77, and MACRO/RSX). With several of these languages,
the LINK command also lets you specify an overlay structure using a
simple dialogue.
The requirements for setting up the LINK command depend on what
languages you want to be able to link with, and whether you want to be
able to link with FMS. The following paragraphs explain how to set
LINK up for each language.
The default language assumed by the LINK command is BASIC-PLUS-2. You
may wantto change this default if your installation does not have
BASIC-PLUS-2, or if you prefer that a different language be the
default. To do this you could assign the GLOBAL symbol LINK :==
LINK/language in the system-wide LOGIN.COM file.
Disabling Languages
You should disable linking with a particular language if your
installation does not have all of the files or other requirements
for that language. The following table shows what file to delete
for each language to be disabled.
These files are installed
automatically.
Language to Disable

File to Delete

All RSX-based languages
BASIC-PLUS-2
COBOL-8I
DIBOL
FORTRAN-IV
FORTRAN-77
MACRO/RTll
MACRO/RSX

[l,2]PRELIN.TSK
LB:BP2.LNK
LB:C8l.LNK
LB:DIBOL.LNK and LB:DMS.LNK
(none)
LB:F77.LNK
(none)
LB:RSX1l.LNK

If a user tries to link with a language you have disabled in
manner, DCL will display the message "?Command not installed."

this

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
DeL
Package Notes

Seq 20.1.2 N

2 of 7

Requirements for RTll-based Languages
MACRO-II
Location

Required File

When Installed

SY:[1,2]
SY:[1,2]

LINK.SAV
SYSLIB.OBJ

RSTS/E System Generation
RSTS/E System Generation

LINK/RTII is automatically disabled if LINK.SAV is not present.
If
LINK.SAV is not present and a user types LINK/RTII, DCL will display
the message "?Command not installed.!!
FORTRAN-IV V2.5
Location

Required File

When Installed

SY:[l,2]
SY:[1,2]
SY: [ I , 2 ]

LINK.SAV
SYSLIB.OBJ
FORLIB.OBJ

RSTS/E System Generation
RSTS/E System Generation
FORTRAN-IV Installation

Note:
1. When you install FORTRAN-IV you have the options of either
including the FORTRAN library routines in SYSLIB.OBJ or
putting them separately, in FORLIB.OBJ.
For LINK/FOR to work
properly, select FORLIB.OBJ.
2. LINK/FOR is automatically disabled if LINK.SAV is
not
present.
If LINK.SAV is not present and a user types
LINK/RTIl, the system will display the message "?Command not
installed."

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
DeL
Package Notes

Seq 20.1.2 N
3 of 7

Requirements for RSX-based Languages
All of the RSX-based languages have certain linking
in common:
Location

Required File
------------PRELIN.TSK
TKB.TSK
RMSRES.TSK
RMSRES.STB
RMSRES.LIB
RMSLIB.OLB
SYSLIB.OLB
RMSRLX.ODL

--------

SY:[1,2]
SY:[1,2]
LB:
LB:
RMS$:
LB:
LB:
LB:

requirements

When Installed
-------------RSTS/E Installation
RSTS/E RSX Emulator Build
RSTS/E RMS Installation
RSTS/E RMS Installation
RSTS/E RMS Installation
RSTS/E RMS Installation
RSTS/E RSX Emulator Build
RSTS/E RMS Installation

Note:
1. When you generate your system specify RSX emulation in the
monitor and resident library support. Answer YES to the
questions "Resident libraries ?" and "RSX directives ?"
2. Install the RSX Emulator Package.
3. Establish a
library account with the system-wide logical
name LB:.
(This is done automatically during the RSX
installation.)

4. Install the
library.

RMS

package.

Select

the

RMSRES resident

5. ADD the RMSRES resident library.

6. Ensure PRELIN.TSK (pre-link) program has a protection code
of 232.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
DCL
Package Notes

Seq 20.1.2 N
4 of 7

Forms Management System
You can use Digital's Forms Management System (FMS) with any of
the RSX-based languages.
There are certain requirements for
setting up the LINK command to link FMS into the program:
Location

Required File

When Installed

LB:
LB:
SY: [ 0 , 1] ( us ua 11 y )
LB:
LB:
LB:

FDVRES.TSK
FDVRES.STB
FDVRES.LIB
FDVRES.OLB
HLLDFN.OBJ
FDVDRS.OBJ

FMS
FMS
FMS
FMS
FMS
FMS

Installation
Installation
Installation
Installation
Installation
Installation

Note:
1. ADD the FDVRES resident library.
2. You must have the
appropriate
high-level
language
interface file in account LB:.
These are:
HLLBP2.0BJ for
BASIC-PLUS-2:
HLLDBL.OBJ for DIBOL:
HLLFOR.OBJ
for
FORTRAN-77;
and HLLCOB.OBJ for COBOL-81.
They are
installed during FMS Installation.
BASIC-PLUS-2 V2.3
Location

Required File

When Installed

LB:
LB:
LB:
SY:[O,l] (usually)
LB:
LB:
LB:

BP2.LNK
BASICS.TSK
BASICS.STB
BASICS. LIB
BASRMS.OLB
BP2COM.OLB
BP2IC7.0DL

RSTS/E Installation
BASIC-PLUS-2 Installation
BASIC-PLUS-2 Installation
BASIC-PLUS-2 Installation
BASIC-PLUS-2 Installation
BASIC-PLUS-2 Installation
BASIC-PLUS-2 Installation

Note:
1. ADD the BASICS resident library.
2. If you gave a name other than BP2COM to the BASIC-PLUS-2
object library, then edit the file LB:BP2.LNK, and change
LB:BP2COM.OLB to the appropriate file specification.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
DCL
Package Notes

Seq 20.1.2 N
5 of 7

COBOL-81 V2.3
Location

Required File

When Installed

SY:[1,2]
SY:[1,2]

C810DL.TSK
ATPK.TSK

SY:[1,2]

PIP.SAV

COBOL-81 Installation
RSTS/E Standard CUSP
Build
RSTS/E System Generation

Additionally, if you select CIS (Commercial Instruction Set)
when you install COBOL-8l:
LB:
LB:
SY:[O,1] (usually)

C81CIS.TSK
C81CIS.STB
C81CIS.LIB

COBOL-81 Installation
COBOL-81 Installation
COBOL-81 Installation

If you select NONCIS when you install COBOL-8l:
LB:
LB:
SY:[O,l] (usually)

C81LIB.TSK
C81LIB.STB
C81LIB.LIB

COBOL-81 Installation
COBOL-81 Installation
COBOL-81 Installation

Note:
1. ATPK's protection code must include 128.
In other words,
it must be a privileged program.
The standard CUSP
installation procedure sets ATPK's protection code to 232,
which is satisfactory.
2. ADD the COBOL resident library, C81CIS or C81LIB.
If [1,2]PIP.SAV or [1,2]C8l0DL.TSK is not present,
the LINK
command will fail with "?Can't find file or account."
If
[1,2]ATPK is not present,
the LINK command will fail with
"?Unexpected error in PRELIN ..• ?Can't find file or account."

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
DeL
Package Notes

Seq 20.1.2 N

6 of 7

DIBOL V5.1A, using RMS
Location

Required File

When Installed

LB:
LB:
LB:
SY:[O,l] (usually)
LB:
LB:

DIBOL.LNK
DIBOLR.TSK
OIBOLR.STB
OIBOLR.LIB
RMSUSL.OLB
RMSOSL.OLB

RSTS/E Installation
OIBOL Installation
DIBOL Installation
OIBOL Installation
DIBOL Installation
DIBOL Installation

Note:
1. When you install OIBOL V5.1A select the
(rather than OMS).

RMS

I/O

package

OIBOL V5.1A, using OMS
Location

Required File

When Installed

LB:
LB:
LB:
SY:[O,l] (usually)
LB:
LB:

OMS.LNK
DIBOLO.TSK
DIBOLO.STB
OIBOLO.LIB
DMSUSL.OLB
OMSOSL.OLB

RSTS/E Installation
OIBOL Installation
orBOL Installation
OIBOL Installation
DIBOL Installation
DIBOL Installation

Note:
1. When you install DIBOL V5.1A select the
(rather than RMS).

DMS

I/O

package

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 20.1.2 N

RSTS/E V9.0
DeL
Package Notes

7 of 7

FORTRAN-77 V5.0-l4
Location

Required File

When Installed

LB:
LB:
LB:

F77.LNK
F4POTS.OLB
RMSI1M.ODL

RSTS/E Installation
FORTRAN-77 Installation
FORTRAN-77 Installation

Note:
1. When you install the FORTRAN-77 V5.0 compiler select the
RMS I/O package (rather than FCS).
2. When you install FORTRAN-77 you have the option of either
including the FORTRAN library routines in SYSLIB.OLB or
putting them separately in F4POTS.OLB.
For LINK/F77 to
work properly, select F4POTS.OLB.
3. Edit the file LB:RMSI1M.ODL.
"LB:[l,l]" to "LB:".

Change all occurrences of

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSX Emulator and Utilities Package
Package Notes

Seq 21.1.1 N
1 of 1

USING RTSODT FOR DEBUGGING RUN-TIME SYSTEMS
A version of ODT is provided on the RSTS/E V9.0 distribution kit as an
unsupported feature which can be linked with user-written run-time
systems.
To use RTSODT with run-time systems that are assembled and task-built
under the RSX run-time system you may specify "RTSODT" in the ODL
file.
For example:
ODTBLD.ODL

*** RSXODT.RTS OVERLAY DESCRIPTION ***
RSXODT VERSION V7.2
• NAME
• ROOT

RSXODT
RSXODT-LB:SYSLIB/DL-RSXEMU-RSXPMD-RSXRUN-RSXPLA-RSXKBM-ODT

RSXRTS MUST BE THE FIRST MODULE LINKED IN ANY RSX BASED RTS
RSXODT MUST BE THE LAST MODULE LINKED IN IF YOU WANT ODT

RSXEMU:
RSXPMD:
RSXRUN:
RSXPLA:
RSXKBM:
ODT:

• FCTR
• FCTR
• FCTR
• FCTR
• FCTR
• FCTR
• END

LB:SYSLIB/LB:RSXRTS:RSXIO:RSXAST:RSXSST:RSXDIR
LB:SYSLIB/LB:RSXPMD
LB:SYSLIB/LB:RSXRUN
LB:SYSLIB/LB:RSXPLA
LB:SYSLIB/LB:RSXKBM:RSXAT:RSXHLP:RSXMCR
LB:SYSLIB/LB:RTSODT

Refer to article Seq 22.1.2 N for a description of the use of RTSODT
with run-time systems that are assembled and linked under the RTII
run-time system.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSX Emulator and Utilities Package
CRF.TSK

Seq 21.2.1 N
1 of 2

USING THE RSX CRF UTILITY
The RSX utility CRF.TSK is included on the RSTS distribution kit as an
unsupported product.
It is installed in the system library ($)
account with other components in the RSX package.
This program will create cross-reference listings from the binary
cross reference (.CRF)
files optionally produced by the RSX task
builder (TKB) and RSX 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 tha
names of the object modules which reference these items.
The
following are examples of these two types of output:
MACRO Assembler output:
CREATED BY MACRO ON 15-JUN-85 AT 06:02
CRF
SYMBOL CROSS REFERENCE
REFERENCES
SYMBOL VALUE
CR
000015
#4-180
=
#4-180
FF
000014
=
HT
#4-180
= 000011
LF
000012
#4-180
=
2-53
L$$IST = ******
1-1
1-2
RSTS
#4-39
= 000001
R$$11M = 000000
#4-38
SPA
000040
#4-180
=
VT
#4-180
= 000013
V1145
4-157
= ******
#5-1
$$$VER = 034066
#3-2

PAGE 1
CREF
07.065

4-182

Task Builder output:
CRF

CREATED BY

TKB

ON 15-JUN-85 AT 06:23

PAGE 1
CREF

GLOBAL CROSS REFERENCE
SYMBOL

VALUE

REFERENCES .••

A.BTTN
A.DFUI
A.LULU
A.LUNA
A.LUNU
A.TRBA
BADDIR
BADNAM

000002
000102
000002
000004
000006
000002
000001
000002

# DIRSYM
CRFIN
# DIRSYM
# DIRSYM
# DIRSYM
# DIRSYM
# ERR
# ERR

# FCSGBL

FIP
FIP

07.065

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSX Emulator and Utilities Package
CRF.TSK

Seq 21.2.1 N
2 of 2

More details on the CRF output can be found in the RSTS/E Programmer's
Utilities Manual.
To request that MAC or TKB produce a binary cross-reference file,
specify the /CR 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.
The binary file
created has the same name as the listing or map file and its file type
is always .CRF.
CRF.TSK is run using either the RUN command or the CRF ceL if
installed.
When run using the RUN command, CRF will prompt with
"CRF>". Typing CTRL/Z 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.
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.
CRF requires the binary cross-reference file to have the same name as
the output file with a file type of ".CRF". CRF always deletes the
binary ".CRF" file when it is done. Therefore, if it is desirable to
keep the binary file, it must be copied to a non-".CRF" file prior to
running CRF.TSK.

RSTS/E V9.0 Maintenance Notebook, June 1985

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

Seq 22.1.1 N
1 of 1

USE OF UNDERSCORE IN RT-ll EMULATOR UTILITIES
RSTS/E allows the use of the underscore ( ) 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-ll 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 V9.0 Maintenance Notebook, June 1985

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

Seq 22.1.2 N
1 of 1

USING RTSODT FOR DEBUGGING RUN-TIME SYSTEMS
A version of ODT is provided on the RSTS/E distribution kit as an
unsupported feature which can be linked with user-written run-time
systems.
To use RTSODT with run-time systems that are assembled and linked
under the RT11 run-time system, execute the following commands:
RUN $LBR.TSK<cr>
LBR>RTSODT.OBJ=LB:SYSLIB/EX:RTSODT<cr>
LBR>AZ
Ready
RUN $PIP.SAV<cr>
*RTSODT.OBJ=RTSODT.OBJ/RMS:FB<cr>
*AZ
Ready
You may now include RTSODT.OBJ in the list of input files during the
LINK. For example:
RUN $LINK<cr>
*RT110D/Z,RT110D/W,RT110D=RT11/X/H:#177776/U:#4000/C<cr>
*#ERR.STB,#RTSODT<cr>
*PATCH<cr>
*AZ
Ready
Refer to article Seq 21.1.1 N for a description of the use of RTSODT
with run-time systems that are assembled and linked under the RSX
run-time system.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RT-11 Emulator and Utilities Package
HOOK.SAV

Seq 22.3.1 N
1 of 4

NOTES ON HOOK.SAV
HOOK.SAV is a program which will write a bootstrap program on RSTS/E
file-structured disks and magnetic tapes. Though it is intended only
for use during system installation, it can be used to make any RSTS/E
file-structured disk or tape bootable.
Creating a bootable RSTS/E File-structured Disk
Mount the disk to be HOOKed:
$ MOUNT xxn:packid/NOSHARE
Copy INIT.SYS from your system disk to the output device:
$ COpy SYO:[O,1]INIT.SYS xxn:[O,l]INIT.SYS/CLUSTER SIZE=16
Then, run HOOK.SAV:
$ RUN SYSGEN$:HOOK.SAV<cr>
<HOOK's header line>
*xxn:[O,l]INIT.SYS<cr>
Hook complete
*AZ
$
Creating a bootable RSTS/E DOS-format Magnetic Tape
Mount a scratch magnetic tape on a tape drive.
(Note that HOOK.SAV
will zero the tape before using it.) Then, run HOOK.SAV:
$ RUN SYSGEN$:HOOK.SAV<cr>
<HOOK's header line>
*xxn:[O,1]INIT.SYS/D(:n.],SYO:[O,1]INIT.SYS<cr>
Hook complete
*AZ
$

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 22.3.1 N

RSTS/E V9.0
RT-11 Emulator and Utilities Package
HOOK.SAV

2 of 4

NOTES
1.

Magnetic tape density:
dev:filnam; as follows:
/D:800.
/D
/D:1600.
/D:1600

Specify

"/D:n"

after

the

"output"

Set 800 BPI, odd parity
Same as /D:800.
Set 1600 BPI, phase encoded
Same as /D:1600.

Note:
o /D:800 (no dot) is an illegal specification
o If /D
used.

not

specified, the drive's current settings are

o HOOK will allocate the tape drive to you, in DOS format,
the density that you specify (or do not specify).
2.

Normally, HOOK finds the bootstraps for disks and magnetic tapes
in SYO:[O,l]INIT.SYS.
If, as may happen on a deve;opment machine,
[O,l]INIT.SYS does not have the most recent version of the
appropriate bootstrap, you can specify an alternate file in which
to find the bootstraps. Hence, a full HOOK command line looks
like:
<outdev:filename> , <file for mt-only> , <bootstraps>
The bootstrap file should look like INIT.SYS.

HOOK writes magnetic tapes with DOS labels.
If the tape is
written at 800 bpi, the name of the first file on the tape will be
[O,l]MTBOOT.SYS.
If the tape is written at 1600 bpi, the name of
the first file will be [O,l]MSBOOT.SYS. Note that the difference
is important; the 800 bpi bootstrap is significantly different
from the 1600 bpi bootstrap.

If no filename is specified with the device specification for
magnetic tape, the default name INIT.SYS is used, with the current
PPN.
In other words, if you are logged in under [123,1] and
specify
MTO:/D:800.,[0,1]FOO.FOO
the
files
on
the
"[123,1]INIT.SYS".

tape

wi 11

"[O,l]MTBOOT.SYS"

and

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 22.3.1 N

RSTS/E V9.0
RT-11 Emulator and Utilities Package
HOOK.SAV

3 of 4

If you have any reason to wonder if a magnetic tape is bootable,
check the directory, which should have 2 files with legal RSTS/E
filenames. The first file should be 1 block long (2 blocks on
SAVE set tapes, which are bootable tapes created by SAVRES).
If
the directory looks unusual, it is not a bootable RSTS/E tape.
5.

The following might be useful information.
Standard command lines:
DLO:[O,l]INIT.SYS
Load and execute [O,l]INIT.SYS when DLO: is booted.
MM1:[O,1]INIT.SYS/D:1600,DRO:[0,1]INIT.SYS
Load and execute MM1:[0,1]INIT.SYS when MM1:
is booted;
copy the file to be executed from DRO:[0,1]INIT.SYS;
set
the density to 1600 bpi.
Non-standard command line:
DB3:[O,1]INIT.SYS,,[4,4]NEWINI.SYS
Load and execute [0,1]INIT.SYS when DB3: is
the bootstrap from [4,4]NEWINI.SYS.
6.

booted;

get

possible Errors:
?Can't open disk NFS
Someone else is using the disk to be HOOKed, or you do
not have WRTNFS and SYSMOD privileges.
?Can't open [0,1]SYO:INIT.SYS
You must have WREAD,WRTNFS, and SYSMOD privileges to
run HOOK.SAV
?Directory error
The output disk is not a valid RSTS/E
disk.

file-structured

?File high limit too large
The file to be loaded by the bootstrap program is too
large.
?Error reading boot block
An I/O error occurred while reading
HOOKed;
it may be offline.

the

disk

RSTS/E V9.0 Maintenance Notebook) June. 1985

Seq 22.3.1 N

RSTS/E V9.0
RT-ll Emulator and Utilities Package
HOOK.SAV

4 of 4

?Error writing boot block
An I/O error occurred while writing the bootstrap
program; the disk may be write-locked.
?Error reading INIT.SYS
An I/O error occurred while reading INIT.SYS.
?Explicit unit number required
The device name specified must
unit number.

include

explicit

?Ill cmd?
UI"\I"\T....
ro '" T 7
.I.l.Vvn. • .;:)ft V

could

not

interpret

the specified command

line.
?Illegal density
The density that you specified cannot be used on
tape drive.

this

?Illegal overlay number in INIT
You are using an obsolete version of INIT.SYS.
?INIT.SYS is not a SAY format SIL
You are using an obsolete version of INIT.SYS.
?INIT.SYS is too fragmented
Occurs on disk if the INIT.SYS file being hooked is
sufficiently fragmented across the disk that the boot
block pointers to INIT do not fit in the boot block.
Solution:
make INIT contiguous or as a minimum use a
clustersize of 16 for INIT.
?Not a bootable device
HOOK.SAV cannot write a bootstrap for that device.
?Null file can't be hooked
Self explanatory.
?No BOOT in STB
You are using an obsolete version of INIT.SYS.
Second input file required for magtape hook
You must specify a file to be copied to
tape.
?UFD open failure
An I/O error occurred.

the

magnetic

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 25.2.1 M

RSTS/E V9.0
RSTS/E 2780 Package V3.0
RJ2780

1 of 3

FAILURE TO CLEAR 'JOB ACTIVE' ON ATTACH - MANDATORY RJ2780 PATCH
NOTE
This patch appeared in an earlier issue of the RSTS/E
V06B-02 Software Dispatch (September, 1977) as a patch
to the RSTS/E V06B RJ2780.BAS program. Since the same
program is used under the V9.0 system, this patch is
being republished for the RSTS/E V9.0 Software Dispatch
Review.
Because of this,
the edit level remains at
"V06B-03".
If you have applied the earlier V06B patch,
do not apply this patch again.
PROBLEM:
Once RJ2780 has been put into SPOOL mode, an ATTACH should cause any
job being sent by QUEMAN to be REQUEUEd, and all variables in the
RJ2780 program itself concerning that job to be cleared.
Processing
should then resume,
taking input from the terminal to which the
program is ATTACHed. When SPOOL mode is re-entered,
the same job
should be sent by QUEMAN,
and processed by the RJ2780 program.
Instead, the RJ2780 program becomes confused when it receives a new
SPOOL command, and the NEWJOB sent by QUEMAN causes an error message
and the job is not processed.
SOLUTION:
The following patch causes reset of all variables upon ATTACH.
PROCEDURE:
1.

For purposes of the discussion, we will assume that the required
program to be patched is located on the public disk structure.
In
the patching procedure, we will refer to the program by its most
simple name format: <program name>.BAS. The person performing the
patching operation should,
if necessary,
replace all program
references with suitable text according to the requirements of the
installation.
Also, for purposes of presenting the patching procedure, we assume
that the patching operation will be performed in a privileged
account.

RSTS/E V9.0 Maintenance Notebook, June 1985

Seq 25.2.1 M

RSTS/E V9.0
RSTS/E 2780 Package V3.0
RJ2780

2 of 3

This mandatory patch is contained in the file PA2502.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.

To apply the patch automatically,
system commands:

perform

the

following

RSTS/E

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - RJ2780.BAS=RJ2780.BAS<cr>
#[logfile=]UPDATE$:PA2502.001<cr>
4.##To apply the patch manually, perform the following RSTS/E
system commands.
RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - RJ2780.BAS=RJ2780.BAS<cr>
#[logfile=]<cr>
*H/6!/V<cr>
6!
EDIT
03
*G/03/I/A/V<cr>
6!
EDIT
03A
*H/7!/V<cr>
7!
EDIT DATE
02-JUN-77
*G/02-JUN-77/-9C/06-JUL-77/V<cr>
7!
EDIT DATE
06-JUL-77
*H/21!/V<cr>
21!
VER/ED
EDIT DATE
REASON
*G/REASON/I<cr>
<If>
--r<tab>6B-03A<tab><tab>6-JUL-77<tab>FIX ATTACH/DETACH PROBLEM WITH<lf>
!<tab><tab><tab><tab><tab>QUEMAN COMMUNICATION.<esc>*V<cr>
!
QUEMAN COMMUNICATION.
*H/l010<tab>/V<cr>
1010
I$="V06B-03"
*G/03/I/A/V<cr>
1010
I$="V06B-03A"
*H/1492<tab>/V<cr>
1492
M$="ATTACH"
*G/DETACH%=/V<cr>
\ DETACH%=((E3% AND 1%)<>0%)

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Package V3.0
RJ2780

Seq 25.2.1 M
3 of 3

*OAI<cr>
<tab>\ INJOB%,ABTJOB%=O%<lf>
<esc>*V<cr>
\ DETACH%=((E3% AND 1%)<>0%)
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete
#AZ
File to patch - AZ
Ready
5.

To re-compile the program and re-enter it into the system library,
type the following RSTS/E commands.
OLD RJ2780<cr>
Ready
COMPILE $RJ2780<cr>
Ready

The person making the changes to the program should now take
whatever
steps
are
necessary,
according
to installation
guidelines, to save the new version of the program.

The source (.BAS) version of the program
from the public structure.

should

now

removed

RSTS/E V9.0 Maintenance

Note~ook,

June 1985

Seq 25.2.2 M

RSTS/E V9.0
RSTS/E 2780 Package V3.0
RJ2780

1 of 3

LOCAL BINARY TRANSMIT FAILURE - MANDATORY RJ2780 PATCH
NOTE
RJ2780.BAS as released with RSTS/E V06B is used on all
V06B and later versions of RSTS/E. For this reason, the
edit level of the program remains at "V06B-03".
PROBLEM:
If the default transmit command is 2780 or GEN, it should be possible
to send, as part of a mUltiple file transfer, a file or files in
binary mode. This is done by using the "/B" switch to override the
transmit command for those files which should be sent untranslated.
Currently, the mode of the first file of a multiple file transfer
controls the mode for the complete transfer.
SOLUTION:
The following patching procedure will correct this problem.
NOTE
The mandatory 2780 Device Driver patch described In
article Seq 5.1.9 M, published in this notebook, must be
installed along with this patch.
PROCEDURE:
1.

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Package V3.0
RJ2780
2.

Seq 25.2.2 M
2 of 3

The command file for this patch appears in patch kit version "A"
or later.
If you do not have this distribution you can produce a
command file by specifying a file for [logfile=] in the following
procedure.
To apply
commands:

the patch manually, perform the following RSTS/E system

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - RJ2780.BAS=RJ2780.BAS<cr>
#[logfile=]<cr>
*H/61/V<cr>
6!
EDIT
03A
*G/03A/I/B/V<cr>
6!
EDIT
03AB
*H/7!/V<cr>
7!
EDIT DATE
06-JUL-77
*G/06-JUL-77/-9C/23-MAR-79/V<cr>
7!
EDIT DATE
23-MAR-79
*H/21!/G/REASON/V<cr>
21!
VER/ED
EDIT DATE
REASON
*I<cr>
<If>
--r<tab>6B-03AB<tab><tab>23-MAR-79<tab>FIX LOCAL BINARY PROBLEM.<esc>*V<cr>
6B-03AB
23-MAR,...79
FIX.LOCAL BINARY PROBLEM.
*H/I010<tab>/V<cr>
1010
I$="V06B-03A"
*G/03A/I/B/V<cr>
1010
I$="V06B-03AB"
*H/4010<tab>/V<cr>
4010
FIELD #1%, 134% AS Bl$
*lOAV<cr>
! FIELD THE RJ: BUFFER.
*I<cr>
<tab>\ PUTBIN%=NEWBIN%<lf>
<esc>*V<cr>
! FIELD THE RJ: BUFFER.
*H/4130<tab>/V<cr>
4130
F$=LEFT(CHR$(27%)+F$,MAXLEN%) IF X.TEST% AND 128%
*8AV<cr>
\
RETURN
*I<cr>
<tab>\ PUTBIN%=NEWBIN%<lf>
<esc>*V<cr>
\
RETURN

RSTS/E V9.0 Maintenance Notebook, June 1985

RSTS/E V9.0
RSTS/E 2780 Package V3.0
RJ2780

Seq 25.2.2 M
3 of 3

*H/4230<tab>/V<cr>
4230
E%,E2%=O%
*3AV<cr>
\ PUTBIN%=(R% OR (Bl% AND B2%)) AND 1%
*G/PUTBIN/-6C/NEWBIN/V<cr>
\ NEWBIN%=(R% OR (Bl% AND B2%)) AND 1%
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete
#AZ
FTIe to patch - AZ
Ready
3.

To re-compile the program and re-enter it into the system library,
type the following RSTS/E commands:
OLD RJ2780<cr>
Ready
COMPILE $RJ2780<cr>
Ready

The person making the changes to the program should now take
whatever
steps
are
necessary,
according
to installation
guidelines, to save the new version of the program.

The source (.BAS) version of the program
from the public structure.

should

now

removed

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

In Canada
call 800-267-6146

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

DIRECT MAIL ORDERS (U.S. and Puerto Rico*)
DIGITAL EQUIPMENT CORPORATION
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (Canada)
DIGITAL EQUIPMENT OF CANADA LTD.
940 Belfast Road
Ottawa, Ontario, Canada K1 G 4C2
Attn: A&SG Business Manager

INTERNATIONAL
DIGITAL EQUIPMENT CORPORATION
A&SG Business Manager
c 10 Digital's local subsidiary
or approved distributor

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

with the Local Digital Subsidiary:

809-754-7575

RSTS/E
Maintenance Notebook
AA-L997D-TC

Reader's Comments
Note: This form is for document comments only. DIGITAL will use comments submitted on this form at
the company's discretion. If you require a written reply and are eligible to receive one under
Software Performance Report (SPR) service, submit your comments on an SPR form.
Did you find this manual understandable, usable, and well-organized? Please make suggestions for
improvement. _________________________________________________

Did you find errors in this manual? If so, specify the error and the page number. _______________

Please indicate the type of user/reader that you most nearly represent.

o
o
o
o
o

Name

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __
Date _______________________

Organization __________________________________________________
Street ___________________________________________________________
Code
City ___________________________________ State _ _ _ _ _ _ Zip or
Country

I
I
I
I
I
I
I

-------Do Not Tear· Fold Here and Tape - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1

IIIIII

No Postage
Necessary
if Mailed in the
United States

BUSINESS REPL V MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

AnN: Office Systems Publications MK01-2/E02
RSTS/E Documentation
DIGITAL EQUIPMENT CORPORATION
CONTINENTAL BOULEVARD
MERRIMACK, N.H. 03054

-------Do Not Tear· Fold Here and Tape - - ..... - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

.,""
c

oj
oj

(

~
l
I

.
(

<II!