Digital PDFs

AA-L997B-TC

June 1982

372 pages

Original

71MB

Document:	RSTS/E V7.2 Maintenance Notebook
Order Number:	AA-L997B-TC
Revision:	0
Pages:	372
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsts_e/V07.2/AA-L997B-TC_RSTS_E_V7.2_Maintenance_Notebook_Jun82.pdf

OCR Text

~---~---------~~~---- -- ---

RSTS/E
RSTS/E V7.2
Maintenance Notebook
Order No. AA- L997B- TC

~D~DDmD

wore

RSTS/E V7.2
Maintenance Notebook
Order No. AA-L997B-TC

June 1982
This notebook describes optional feature patches for RSTSIE. It is a
working document that system maintainers should keep current by adding published articles on software problems, programming notes, and
documentation corrections. These articles are published in the RSTSIE
Software Dispatch.

OPERATING SYSTEM AND VERSION:

RSTS/E

V7.2

SOFTWARE VERSION:

RSTS/E

V7.2

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:
DEC
DECUS
DECnet
PDP
UNIBUS
VAX

VT
DECsystem-10
DEC SYSTEM 20
DECwriter
DIBOL
Edusystem

lAS
MASSBUS
PDT
RSTS
RSX
VMS

~D~DDmD

6/82-14

RSTS/E V7.2 Maintenance Notebook, June 1982
Table of Contents

Page C-l

TABLE OF CONTENTS
Preface
1.0

Notebook Maintenance

2.0

RSTS/E Component. Subcomponent Assignments

3.0

Software Performance Reports

3. 1 Software Performance Report Guidelines
4.0

5.0

6.0

Patching Procedure
4.1

Monitor Patching

4.2

Commonly Used System Program (CUSP) Patching

4.3

Patch Kits
4.3. 1 Off-Line Patching
4.3.2 On-line Patching
4.3.3 Optional Feature Patches

RSTS/E Articles
5.1

Cumulative Index of All RSTS/E V7.2 Maintenance Notebook Articles

5.2

Patch Levels for Commonly Used System Programs (CUSPs)

5.3

Protection Codes for Commonly Used System Programs (CUSPs)

5.4

Compiling CUSPs under BASIC-PLUS-2 or RSX (CSPCOM)

Software Product Descriptions (SPDs) and Option Bulletins
6.1

Software Product Descriptions (SPDs)

6.2

Option Bulletins

RSTS/E V7.2 Maintenance Notebook, June 1982
Introduction

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 V7.2. In general, this is a composite of
all optional layered software articles previously published for RSTS/E V7. 1 ,
which still apply to the product when run on RSTS/E V7.2.
The RSTS/E Software Dispatch is provided for 90 days after each software
installation of a RSTS/E system by DIGITAL, and is addressed to the software
contract established by the DIGITAL field office. After 90 days, the customer
may purchase the Self Maintenance Service to continue recelvlng the RSTS/E
Software Dispatch.
Contact your local Digital office for more information.
The RSTS/E Software Dispatch is published monthly, and 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
notebook.
Anyone who is about to generate RSTS/E V7.2 must incorporate all "Mandatory"
patches as part of the system generation and BUILD procedures.
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 indices are updated each month in the RSTS/E Software Dispatch.

RSTS/E V7.2 Maintenance Notebook, June 1982
Notebook Maintenance

1.~

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 superseded article. Each article addresses a single
topic and its title gives 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 V7.2
BASIC-PLUS
BASIC-PLUS Patches

Seq4.1.4F
1 of 2

DEFAULT TO EXTEND 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.

RSTS/E V7.2 Maintenance Notebook, June 1982
Notebook Maintenance

Page 1-2

A flag will appear after the sequencing number:
M = MANDATORY:

These patches correct errors in the software
product.
All users are required to apply these
patches
unless
the
accompanying
article
specifies otherwise.

F = FEATURE:

These patches 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
or
package.
They
also
provide
program
procedural information to make it easier to use
a program or package.

Page 2-1

RSTS/E V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments

2.11

RSTS/E Component. Subcomponent Assignments

The component. sUbcomponent numbers outlined below appear
filed following Section 5.4 of this notebook.
RSTS/E MONITOR
RSTS/E V7.2 General Notes
System Notes
Initialization
INIT.SYS Program Patches
INIT.SYS Program Notes

2.11
2. 1

2.2

System Generation
SYSGEN Patches
SYSGEN Notes

3.11
3. 1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9

Executive
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

4.11

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

4. 1

4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10

5.11
5. 1

5.2

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

6.11

(Reserved)

7.11
7.1

DECnet/E Package V2.11
NSPITRN/SES

articles

V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments

RSTS/E

8.0'

(Reserved)

9.1i5

TECO
TECO Notes
TECO.RTS
TECO.TEC
VTEDIT.TEC
TECO.INI
TYPE.TEC
SQU.TEC
LOCAL.TEC
TECKBM.TEC
SEARCH.TEC

9. 1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
9.9
9. 1QJ

RSTS/E UTILITIES
HJ.~

10. 1

10.2
10.3
110.4

113.5
10.6
10.7
10'.8
10.9
10'.10
H1.11

10'.12
10. 13
10'.14
110. 15
10. 16
10.17

10. 18
113.19
10.20
10.21
10.22
10.23
10.24

10.25
10.26
10.27
10.28
10.29
10.30
1!2J. 31
10.32

System Utilities Package
Package Notes
BUILD
DIRECT
DISPLY
VT05 (VT5DPY)
VT50' (VT50PY)
(Reserved)
DSKINT
GRIPE
INIT
(Reserved)
LOGIN
LOGOUT
MONEY
ODT
PLEASE
(Reserved)
(Reserved)
REACT
REORDR
SHUTUP
(Reserved)
SYSTAT
TALK
TTYSET
UMOUNT
UTILTY
(Reserved)
S\HTCH
VT55
DEM055
HELP

Page 2-2

V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments

RSTS/E

11.01
11. 1

11.2
11.3

11.4
11.5
11.6
11.7
11.8

11.9
11. 10
11.11
11. 12
11. 13

11 . 14
11 . 15
11. 16
11, 17

11. 18
11. 19
11.20
11 .21
11.22
12.CIi
12. 1
12.2
12.3

12.4
12.5
12.6
12.7
- 12.8

12.9
12.10

Data Manipulation Package
Package Notes
COPY
(Reserved)
(Reserved)
FILCOM
FLINT
(Reserved)
(Reserved)
RUNOFF
BPCREF
BPCRF1
PMDUMP
(Reserved)
(Reserved)
FIT
MAKSIL
DSKDMP
STATUS
QSTATS
LQSTAT
BPDA
B2CREF
Error Control Package
Package Notes
ANALYl
ANALYS
ERRCPY
ERRDET
ERRDIS
ERRINT
ERRBLD
ANALY2
ANALY3

Page 2-3

RSTS/E V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments
13. (iJ
13. 1
13.2
13.3
13.4
13.5
13.6
13.7
13.8
13.9
13.10
13. 11
13.12

13.13
13.14
13. 15
13.16
14.~

14. 1

14.2
14.3
14.4

14.5
14.6
14.7

14.8
14.9
14. 10
14. 11

14. 12
14.13
14. 14

14. 15

Backup Package
Package Notes
BACCOM
BACCON
BACDEL
BACDIR
BACDMP
BACDSK
BACENT
BACFRM
BACLAB
BACLOD
BACLST
BACMNT
BACPRM
BACKTO
BACKUP
Spooling and Operator Services Package
Package Notes
OPSER
OPSRUN
QUE
QUEMAN
QUMRUN
CHARS
SPOOL
SPLIDL
SPLRUN
BATDCD
BATCH
BATIDL
BATDEC
BAT RUN

15.~

(Reserved)

16.9

System Management Guidelines

17 .~
17.1
17.2
17.3
17.4
17.5
17.6
17.7

Automated Patching Facility Package
Package Notes
PATCPY
PBUILD
CPATCH
AUTOED
ONLPAT.SAV
ATPK

Page 2-4

RSTS/E V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments

18.0
18.1
18.2
18.3
18.4
18.5
18.6
18.7
18.8
18.9
18. 10
18. 11
18. 12
18. 13

Device Test Package
Package Notes

DSKSEK
DSKEXR
LPEXER
PPEXER
PREXER
DXEXER
DTEXER
CPEXER
CPUTST
KBEXER
MTEXER
DDEXER

Page 2-5

RSTS/E V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments

Page 2-6

RSTS/E DOCUMENTATION
19. "

19. 1
19.2
19.3
19.4
19.5
19.6
19.7
19.8
19.9
19.113
19. 11
19.12
19. 13

19. 14
19.15
19. 16
19.17
19. 18
19.19
19.20
19.21
19.22
19.23
19.24
19.25
19.26
19.27
19.28
19.29
19.30
19.31

Documentation
RSTS/E Documentation Directory
AA-2642E-TC
RSTS/E System Generation Manual
AA-2669F-TC
RSTS/E System Manager's Guide
AA-2762D-TC
RSTS/E System User's Guide
AA-5133C-TC
BASIC-PLUS Language Manual
AA-2623D-TC
RSTS/E Programming Manual
AA-2726D-TC
RSTS/E RUNOFF User's Guide
DEC-11-URUNA-B-D
RSTS/E DCL User's Guide
AA-L426A-TC
RSTS/E V7.2 Release Notes
AA-5246D-TC
RSTS/E Pocket Guide
DEC-11-0RFCA-A-D
RSTS/E Primer
AA-54!l8A-TC
Introduction to BASIC
AA-13155A-TK
RSTS/E Task Builder Reference Manual
AA-5072B-TC
RSTS/E Task Builder Manual Update
ad-5072B-T1
RSTS/E V7.2 Maintenance Notebook
AA-L997A-TC
RMS-11 MACRO Programmer's Reference Manual
AA-H683A-TC
(Reserved)
(Reserved)
PDP-11 MACRO-11 Language Reference Manual
AA-5!l75B-TC
EDT Editor Manual
AA-J726A-TC
EDT Editor Reference Card
AV-J756A-TC
Introduction to the EDT Editor
AA-K443A-TC
(Reserved)
IAS/RSX ODT Reference Manual
AA-M5!l7A-TC
RSTS/E System Directives Manual
AA-D748B-TC
RSTS/E Programmer's Utilities Manual
AA-D749A-TC
RSTS/E Programmer's Utilities Manual Update1 AD-D749A-T1
RSTS/E Programmer's Utilities Manual Update2 AD-D749A-T2
RSTS/E RT11 Utilities Manual
AA-M213A-TC
PDP-11 SORT Reference Manual
AA-3341C-TC
PDP-11 SORT Reference Manual Update
AA-3341C-T1
PDP-11 TECO User's Guide
DEC-11-UTECA-B-D
AA-H235A-TC
RMS-11 Installation Guide
AA-D538A-TC
RMS-11 User's Guide
RMS-11 User's Guide Update
AA-D538A-T 1
RSTS/E Documentation Notes
AA-M5!l7A-TC

RSTS/E V7.2 Maintenance Notebook, June 1982
Component.Subcomponent Assignments
RUN-TIME SYSTEMS SUPPORT
21rJ.1rJ
20. 1
211.2
20.3
211.4
20.5

DCL
Package Notes
DCL.RTS
DCL.DCL
PRELIN
SHOTER

21.1rJ
21.1
21.2
21.3
21.4
21.5
21.6
21.7
21.8
21.9
21.111
21. 11
21.12
21. 13
21. 14
21. 15

RSX Emulator and Utilities Package
Package Notes
(Reserved)
RSX.RTS
TKB.TSK
MAC.TSK
LBR.TSK
SYSLIB.OLB
RSXMAC.SML
PAT.TSK
(Reserved)
CSPCOM.TSK
CSPCOM.OLB
CRF.TSK
RNO.TSK
SLOTKB.TSK

22.1rJ
22.1
22.2
22.3
22.4
22.5
22.6
22.7
22.8
22.9
22.10
22.11
22.12
22.13
22.14
22. 15
22.16
22.17
22.18
22.19

RT-11 Emulator and Utilities Package
Package Notes
RT 11. RTS
CREF.SAV
(Reserved)
HOOK.SAV
LIBR.SAV
LINK.SAV
LOGIN.SAV
LOGOUT.SAV
MACRO.SAV
PAT. SAY
(Reserved)
PIP.SAV
SILUS.SAV
SYSBAT.SAV
SYSGEN.SAV
UTILTY.SAV
ONLCLN.SAV
SAVRES.SAV

Page 2-7

RSTS/E V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments
SUBORDINATE SOFTWARE
23.0'
23.1

EDT V2
Package Notes

24.1!J
24. 1
24.2
24.3
24.4
24.5
24.6
24.7
24.8
24.9
24.10
24. 11
24.12
24.13
24.14
24.15
24.16
24.17
24.18
24.19
24.20
24.21
24.22
24.23
24.24
24.25
24.26

DMS-5@1O V@2
Package Notes
DMSUTL
DMSFSS
DMSlSR
DMSlSC
DMSRAR
DMSlSA
DMSRAA
DMSFSU
DMSlSO
DMSRAO
DMSFSX
lAMGEN
lAMCRl
lAMDMP
lAMVFY
lAMPRl
lAMFNS
DSORT
DSORTD
DSORTF
DSORTX
DSORTS
DSORTM
DSORTO
DMS-5@@ User's Guide (DEC-11-0RDUA-B-D)

25,0'
25. 1
25.2
25.3

RSTS/E 2789 PACKAGE V3.0'
Package Notes
RJ278@
RSTS/E 278@ User's Guide CDEC-l1-0RJEA-B-D)

Page 2-8

RSTS/E V7,2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments
26.0
26, 1
26.2
26.3
26.4
26.5

DIBOL-l1/DECFORM V4.5
Release Notes
Installation Guide
CTS-5@~ DIBOL-11 Language Reference Manual
CTS-500 DIBOL-l1 User's Guide
DECFORM User's Manual

These are the DMS DIBOL components
DBLRES.LIB ( and .TSK and .STB)
26.6
DBLLIB.OLB
26.7
FOCOMP.RT3 (and . T3K)
26.8
FOCOMP,MLB
26.9
26, 1G'
DECF0
DECFl
26. 11
ISMUTL
26. 12
SORTG
26.13
SORTM
26. 14
DBUUD
26.15
DMSDBL.CTL
26. 16
DMSDMO.CTL
26.17
DECSM.OBJ
26. 18
Reserved
26.19-26.39
These are the RMS DIBOL components
DBRRES.LIB (and .TSK and .STB)
26.40
DBRLIB.OLB
26.41
FOCOMR. RTS (and FOCOMR.TSK)
26.42
FOCRMS
26.43
26.44
DECF0R
DECF1R
26.45
DBRRMS.ODL
26.46
DBROPN.ODL
26.47
DBRALL,ODL
26.48
DBRSR.ODL
26.49
DBRRAN.ODL
26.50
DBRISM.ODL
26.51
DBRRES.ODL
26.52
DBRSEQ.ODL
26.53
FOCOMR.ODL
26.54
RMSDBL,CTL
26.55
RMSDMO.CTL
26.56
RMSDMR.CTL
26.57
FOCOMR.MLB
26.58
DECSMR.OBJ
26.59
Reserved
26.60-26.69

Page 2-9

RSTS/E V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments
These components are common to DMS and RMS DIBOL
26.70
26.71

DICOMP.TSK
RSDDT

27.0
27. 1

FMS-l1 Vl.5
Package Notes

28.0
28. 1
28.2
28.3
28.4

INDENT Vl. 1
Package Notes
INDENT.SAV
INDENT.RTS
INDENT Drivers

29.0
29. 1

DX/RSTS V3. 1
Package Notes
(Reserved)

31.9
31.1
31.1
31.2
31.3
31.4
31.5
31.6
31.7
31.8
31.9
31.1(3
31 . 11
31. 12
31.13
31. 14
31. 15
31. 16
31.17
31.18

31. 19
31 . 2(5

31. 21
31.22
31.23

31.24
31.25
31.26

31. 27
31.28

31.29
3 1 . 3(5

DECnet/E Utilities V2.0
Package notes
Package notes
NCP Object patches
NCP.TSK
reserved (NML Object patches)
reserved (NML.TSK)
TLK. BAS
TLK Task image patches
LSN.BAS
LSN Task image patches
NETOFF.BAS
NETOFF Task image patches
NETCPY.BAS
NETCPY Task image patches
NETFNC.BAS
NETFNC Task image patches
NET Object patches
NET.TSK
NPKDVR Object patches
NPKDVR.TSK
NFT Object patches
NFT.TSK
FAL Object patches
FAL. TSK
NETACT.BAS
NETACT Task image patches
NCUCVT.BAS
NCUCVT Task image patches
EVTLOG Object patches
EVTLOG. TSK
MIRROR Object patches

Page 2-10

V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments

RSTS/E

31. 31
31.32
31.33
31.34
31.35
31.36
31.37
31.38
31.39
31. 40
31. 41
31. 42
31.43
31.44
31.45
31.46
31. 47
31.48
31.49
31 . 5(3
31.51

Page 2-11

MIRROR.TSK
DTR Object patches
DTR.TSK
DTS Object patches
DTS.TSK
NETSLP.BAS
NETSLP Task image patches
MSRSUB (RT-l1)
MSRSUB (RSX-l1)
DNEHLL (RT-11)
DNEHLL (RSX-l1)
NETMLB
DNECCI
DECnet/E V2.0 Release Notes
DECnet/E V2.0 System Manager's Guide
DECnet/E V2.0 Network Pgmg in Basic-Plus and Basic-Plus-2
DECnet/E V2.0 Network Pgmg in Macro
DECnet/E V2.0 Network Pgmg in FORTRAN
DECnet/E V2.0 Network Pgmg in COBOL
DECnet/E V2.0 System User's Manual
DECnet/E V2.0 Installation Manual

32.0

(Reserved)

33.0

(Reserved)

34.0

(Reserved)

35.0

(Reserved)

36.0

(Reserved)

37.0
37. 1
37.2
37.3
37.4

DECAL V2
Package Notes
QUIZ
CREATE
SORTl

38.0

(Reserved)

RSTS/E V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments
39.0"

Page 2-12

(Reserved)
(Reserved)

41.0"

(Reserved)

42.0"

(Reserved)

43.0"

(Reserved)

44.0'
44. 1
44.2

SORT-11 V0'2 (as part of RSTS/E V7.2)
Package Notes
SORT Object Library Patches

45.0'
45.1
45.2
45.3
45.4
45.5
45.6
45.7
45.8
45.9

BASIC-PLUS-2 V1.6
Package Notes
BASIC2 Compiler Patches
BASIC2 Run-Time System Patches
BP2COM Run-Time System Patches
BASIC2 Object Library Patches
BP2COM Object Library Patches
BASRMS Object Library Patches
TRANSLATOR Utility Patches
PDP-11 BASIC-PLUS-2 Language Reference Manual (AA-H774A-TC)
PDP-11 BASIC-PLUS-2 Language Reference Manual Update
(AD-H774A-T1 )
BASIC-PLUS-2 RSTS/E User's Guide (AA-H772A-TC)
BASIC-PLUS-2 RSTS/E User's Guide Update (AD-H772A-T1)
BASIC-PLUS-2 RSTS/E Installation Guide (AA-0"156B-TC)
BASICS Resident Library Patches
B2RESQ Utility
B2XREF Utility
BASIC-PLUS-2 V1.6 Pocket Reference Card CAV-K0'14A-TC)

45.10
45. 11
45.12
45.13
45.14
45.15
46.0'

(Reserved)

47.0'

(Reserved)

RSTS/E V702 Maintenance Notebook, June 1982
Component. Subcomponent Assignments
48.0
48. 1
48.2
48.3
48.4
48.5
48.6
48.7
48.8
48.9
48.10
48. 11
48. 12
48. 13

RMS-11 Vl.B
Package Notes
RMSLIB
RMSSEQ
RMSRES
RMSUTL
RMSBCK
RMSCNV
RMSDEF

49.0

(Reserved)

59.~

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

50.1
50'.2
5003
50.4
51.0
51. 1
51.2
51. 3
51.4
51.5
51.6
51.7
51. 8
52.0
52. 1
52.2

52.3
52.4
52.5
52.6
52.7

Page 2-13

R~lSDFN

RMSDSP
RMSIFL
RMSRST
RMSMAC

RSTS/E 3271 Protocol Emulator V2.1
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
RSTS/E High Performance 2780/3780 Emulator Vl.1
Package Notes
2780 Microcode (CRAM)
2780 Microcode CRAM)
3780 Microcode (CRAM)
3780 Microcode (RAM)
RJESPL
RSTS/E 2780/3780 High Performance Emulator V1. 1 Release Notes
CAA-,J L!58B~TC)

52.8

RSTS/E High Performance 2780/3780' Emulator User's Guide
CAA-J 177 A-Te)

53.0

(Reserved)

54.0

(Reserved)

RSTS/E V7.2 Maintenance Notebook, June 1982
Component. Subcomponent Assignments
55.~

(Reserved)

56.~

(Reserved)

57.~

(Reserved)

58.~

(Reserved)

59.~

(Reserved)

6~.e

DECWORD/DP V1. 1
Package Notes

6~. 1

61.~

61. 1
61. 2
61.3
61. 4
61.5
61. 6
61.7
61. 8
61.9
61. W
61 . 11
61. 12

Page 2-14

COBOL-11 V4.1
Package Notes
COBOL Compiler - NON-CIS
COBOL Compiler - CIS
COBOL Object Library - NON-CIS
COBOL Object Library - CIS
COBOL ODL
COBOL Utili ties
COBOL Interactive Debugger - CIS
COBOL Interactive Debugger - NON- CIS
PDP-11 COBOL Language Reference Manual (AA-1749E-TC)
PDP-11 COBOL Language reference Manual Update (AD-1749E-T1)
PDP-11 COBOL User's Guide (AA-1757E-TC)
PDP-11 COBOL Installation Guide (AA-1745E-TC)

62.~

(Reserved)

63.13
63.1
63.2
63.3
63.4

FORTRAN IV V2.5
Package Notes
COMPILER
OTS
RSTS/E FORTRAN IV Installation Guide/Release Notes
(AA-C762C-TC)

64.13
64.1
64.2
64.3

FORTRAN IV-PLUS V3.e
Package Notes
COMPILER
OTS

RSTS/E V7.2 Maintenance Notebook, June 1982
Component.Subcomponent Assignments

DECWORD/DP V1.9
65.9
Package Notes
65.1
DECWORD/DP Release Information
65.2
DECWORD/DP Directory
65.3
How to Install DECWORD/DP
65.4
How to Manage DECWORD/DP
65.5
Beginner's Guide to DECWORD
65.6
How to Use DECWORD
65.7
DECWORD Quick Reference Guide
65.8
Glossary of DECWORD Terms
65.9
How to Use DECWORD List Processing
65.10
How to Use DECWORD Options
65. 11
DECWORD for WPS-8 Users
65.12
DECWORD Basic User Course
65.13
Editing and Handling Documents
65.14
User Defined Keys
65.15
Document Conversion
65.16
List Processing
65.17
Spelling Error Detection
65.18
Communications
65. 19
Spoolers and Printer Utilities
65.20
Training Utility
65.21
66.0
66.1

COBOL-81 V1.9
Package Notes

67.9
67.1

PDP-11 FORTRAN-77/RSTS/E V4.9
Package Notes

68.9
68.1

DATATRIEVE V2.4
Package Notes

69.9

(Reserved)

79.0
7IJ. 1

COBOL-11 V4.4
Package Notes

71.9
71.1
71.2

DMS-5IJ0 V2.1
Release Notes
DMS-5IJIJ User's Guide

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

DMSFSS.BAS
DMSISO.BAS
DMSRAO.BAS
DMSISR.BAS
DMSISC.BAS
DMSRAR.BAS
DMSISA.BAS
DMSRAA.BAS

Page 2-15

V7.2 Maintenance Notebook, June 1982
Component.Subcomponent Assignments

RSTS/E

71 . 11

71. 12
71. 13
71. 14
71 . 15

71.16
71. 17

71. 18

DMSFSU.BAS
DMSFSX.BAS
DMSUTL.BAS
IAMGEN.BAS
lAMeRI. BAS
IAMDMP.BAS
IM1VFY. BAS
IAMFNS.BAS

These are the component numbers for the DSORT package
71. 19
71.2!J

71. 21
71.22

71.23
71.24

71. 25

DSORT.BAS
DSORTD.BAS
DSORTF.BAS
DSORTX.BAS
DSORTS.BAS
DSORTM.BAS
DSORTO.BAS
User Assigned Components - For Development Use
Package Notes

91.0' - 99.0

User Assigned Components - For User Use

Page 2-16

RSTS/E V7,2 Maintenance Notebook, June 1982
Software Performance Reporting (SPRs)

Page 3-1

3.0 Software Performance Reports
Each new installation is provided with Software Performance Report (SPR)
forms.
The SPR form enables the user to suggest enhancements to, or report
problems, with DIGITAL software or documentation.
When a problem
is
encountered, an SPR should be completed and mailed 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.
Additional SPR forms may be obtained by writing to the local SPR Center. SPR
response is provided at no charge for one year after installation and may be
continued by subscription thereafter.
3.1

Software Performance Report Guidelines

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

following

should

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 information which you may think is relevant.

For problems associated with the RSTS/E
CANALYS). also include:

Monitor

crash

analysis

package

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

If possible, a machine readable copy (preferrably 9-track magnetic
tape) of your monitor and CRASH.SYS file.
Your media will be
returned with your SPR answer.

Page 3-2

RSTS/E V7.2 Maintenance Notebook, June 1982
Software Performance Reporting (SPRs)
3.

Listings of your maps, CONFIG.MAC, and SYSGEN.CTL files created
during SYSGEN. Note that the .MAP files are necessary, even
though ANALYS prints some of the same information.

When submitting an SPR
(CUSP), also include:

concerning

DIGITAL

supplied BASIC-PLUS program

The name of the CUSP.

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

A list of any optional feature patches installed.

Whether the program was compiled under BASIC-PLUS, BASIC-PLUS-2,
or CSPCOM. In the latter two cases, also include the name of the
run-time system under which the program was running.

Under what account(s) the problem occurs, distinguishing between
privileged and non-privileged behavior.

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

Listings of all relevant input and output files.

version

tape)

NOTE
No SPR, monitor or CUSP, will be considered unless ALL relevant
Mandatory patches published to date have been applied.
Before
submitting
an
SPR, the user should review the relevant
section(s) of the Maintenance Notebook, to insure that ALL
Mandatory patches to the program or package have been applied.
SPR turnaround time for CUSPs running under the BASIC-PLUS
run-time system can be reduced by including a "DUMP" of the
Seq 4.1@.4 F,
and
CUSP.
See
articles
Seq 4.1@.2 N,
Seq 4.10.6 F.

RSTS/E V7.2 Maintenance Notebook, June 1982
Patching Procedure

4.9

Page 4-1

Patching Procedure

This section briefly describes the patching procedures to be used for
maintenance of RSTS/E V7.2. Programs included in the patching package are
ONLPAT for the monitor, INIT, BASIC PLUS, RT-11 run-time system, RSX-11M
run-time system, and ATPK, BUILD, PBUILD, PATCPY, CPATCH, and AUTOED for the
CUSPs. The procedures to be followed for patching the monitor and CUSPs when
generating a new RSTS/E system are described in the RSTS/E System Generation
Manual.
NOTE
The RSTS/E Software Dispatch will contain announcement articles
as new RSTS/E V7.2 autopatch kits become available. These
articles, to be published as Seq 17.1.n N, will contain general
procedures to be followed when applying patch kits, and indicate
components which have patches that did not appear on the
previous
kit.
The
articles
may
also contain special
instructions which might be necessary to install and/or patch
various products on RSTS/E V7.2. Each announcement/instruction
article is also included on the corresponding patch kit in
account
[1,2J;
the
name of the file is in the form
"PATCHz.DOC" , where HZ" reflects the version of the patch kit,
e.g., "PATCHA.DOC".
Note
that
if
instructions
included
in
patch
kit
announcement/instruction articles conflict
with
procedures
described in the standard RSTS/E documentation kit, the article
takes precedence for the specified patch kit. The announcement
article should always be read prior to trying to apply the patch
kit or generating a system.
Be sure to read article Seq 17.1.1 N before generating your
system if you received Patch Kit "A" with your distribution kit.
Some patches to the monitor or INIT code must be applied manually with the
INIT PATCH option before the system can be started for autopatching. Any
patches requiring such special attention will be clearly marked in their
accompanying article.
The programs used for automated patching can also be used for manual patching.
The procedures for manual patching with these programs can be found in the
RSTS/E System Manager's Guide.

RSTS/E V7.2 Maintenance Notebook, June 1982
Patching Procedure

Page 4-2

Two types of patching will be used for RSTS/E software:
1) Monitor patching
and 2) CUSP patching. Other optional software supplied may require different
patching procedures. In all cases, however, the patching procedure will be
described in the accompanying patch article.
Unless otherwise stated, all patches published in the RSTS/E Software Dispatch
are MANDATORY patches which must be made to the affected component as soon as
possible. Since not all components will be included at each installation,
patches to unused components will fail when the attempt is made to apply them.
The system manager should file all articles, however, even for unused
components, since the installation might choose at some future time to install
additional components and these components will then have to be brought up to
the latest support level.
Some articles will detail the procedure to patch a component in order for the
installation to use an optional feature of that component. These optional
"Feature" patches are not required to keep a component at its current support
level.
If problems occur with a component containing optional features,
however, the installation must report which optional feature patches are in
use when filing the Software Performance Report (SPR).
Next, some discussion of documentation conventions needs to be presented. The
following list of syntactic elements provides a description of certain
terminal keys which have non-printing functions:
~C

up-arrow/C or Control-C
NOTE
The syntactic element ,,~C" refers only to "up-arrow/C"
(i.e., typing upper-shift 6 followed by the character
"C") when used in patches using the program ONLPAT.

CTRL/C
<tab>
<If>
<ff>
<cr>
~Z or CTRLIZ
<esc>

Control-C
Horizontal tab
Line feed
Form feed
Carriage return
Control-Z
Escape (Alt Mode or SEL)

When one of these syntactic elements appears in the documentation, it
signifies that the associated keyes) is (are) pressed if input is desired or
the appropriate terminal action occurs if an output operation is being
described.

RSTS/E V7.2 Maintenance Notebook, June 1982
Patching Procedure

Page 4-3

An optional item will be indicated by enclosing it in square brackets (this
does not apply to project-programmer numbers). For example, a line of the
following form appears in most CUSP patch articles:
#[logfile=JKB:/CS:64049
Replacing "[logfile=J" with an actual file specification will allow
produce a patch command file when applying a patch. For example,

you

#PA1012.003=KB:/CS:64049
4.1

Monitor Patching

Changes to the RSTS/E monitor will be made via the PATCH option of INIT.SYS
and lor the program ONLPAT, as described in the RSTS/E System Generation
Manual.
Articles discussing various monitor options and problem corrections will
contain the exact operator action required when using the PATCH option. The
expected dialogue will be shown in the article as it should appear when the
patch is made.
If any deviation occurs, the process should be halted, any
changes already made returned to their former values via the PATCH option, and
a determination made as to where the discrepancy occurred.
4.2

Commonly Used System Program (CUSP) Patching

The RSTS/E CPATCH program
maintenance purposes.

will serve as the CUSP program patching tool for

Refer to the RSTS/E System Manager's Guide for complete
commands and capabilities of CPATCH and PBUILD.

information

the

Each patch notice will be self-contained as a convenience to the person who
will be making the change. It is recommended that the date of the change and
the name of the person making the patch be written on the article at the time
the program modification is performed in order to keep an accurate record of
the status of the system library software.

RSTS/E V7.2 Maintenance Notebook, June 1982
Patching Procedure
4.3

Page 4-4

Patch Kits

RSTS/E patch kits contain machine readable patches for software supported
under RSTS/E V7.2. RSTS/E Patch Kit "A" contains all patches published in the
RSTS/E V7.2 Maintenance Notebook and in the RSTS/E V7.2 Software Dispatch
Review. Subsequent patch kits will contain these same patches plus new patches
published in the RSTS/E Software Dispatch. The cumulative index published in
the Software Dispatch contains a column indicating which is the first patch
kit that a new patch will appear in.
Procedures for using the patch kit to patch standard RSTS/E software can be
Procedures for patching
found in the RSTS/E System Generation Manual.
optional layered software are usually found in the appropriate installation
manual for the product.
The sections which follow provide general guidelines for using patch kits.
Information for using specific patch kits will be published as articles with
sequence numbers 17.1.n N. Please refer to those articles before attempting
to apply any patch kit.
4.3.1

OFF-LINE PATCHING

Off-line patching is done as part of the SYSGEN procedure.
following areas may be applied off-line:

Patches

for

the

o Initialization code
o the RSTS/E Monitor
o the BASIC-PLUS run-time system
o the RSX Emulator (Both Monitor emulation and the run-time system)
o DECnet/E V2.@
Patch command files exist on the patch kit for all of these components. Those
that do not currently have any mandatory patches exist in skeletal form only.
These patch command files should ALWAYS be called in automatically during
SYSGEN. This is done by answering "YES" to the appropriate questions during
the SYSGEN dialogue. For example,
QUESTION

DEFAULT

RESPONSE

Generate monitor?
Monitor name?
Monitor patching?
Patch file medium?
Patch file name?

#Y #
#RSTS#
#??#
#dev#
#$MONITR.CMD#

The patch file names on the patch kit are the same as the default names
printed by SYSGEN and should always be accepted.
Note that application of patches to Monitor code in all of these command files
may be done on-line using the PBUILD program with the command file EXEC.CMD.

Page 4-5

RSTS/E V7.2 Maintenance Notebook, June 1982
Patching Procedure
4.3.2

ON-LINE PATCHING

On-Line patching is done after the system
following procedure should be followed:
A.

installed

and

running.

If you received your kit on magnetic tape, transfer all patch files
from the patch kit distribution media to disk, using the PATCPY
program. PATCPY.BAS exists on the patch kit in account [1,2J and may
be used for this transfer. Digital recommends that the account to
which you are transferring the files have a clustersize of 16.
NOTE
If you use PATCPY to copy patch files for a single
package (see Chapter 6 of the RSTS/E System Generation
Manual), you MUST use the version of PATCPY included on
the patch kit. This version handles the most up-to-date
list of supported optional layered software;
the
released version of PATCPY may not handle all products.
Copy the patch files to an account as shown below:
RUN PATCPY
<PATCPY's header line>
Enter distribution device/PPN<SY:[1,2J>: dev:[1,2J
Enter output device/PPN<SY:[2@0,2@@J>: dev:[p,pnJ
Packages to patch? ALL<cr>
If
the specified output
optionally, create it.

account

does

not

exist,

PATCPY

will,

NOTE
Two patch tapes may be included in RSTS/E 8@@ BPI magnetic
tape kits.
If this is the case, and if you are using any of
the optional software contained on the second tape, you must
run PATCPY twice.
The list of command files published for
each patch kit indicates which products are included on the
second tape.

The

RSTS/E V7.2 Maintenance Notebook, June 1982
Patching Procedure

Page 4-6

If you wish to patch the CUSP library as part of a system BUILD
procedure, you may use the "BUILD/PATCH" function of the program
$BUILD:
RUN $BUILD
<BUILD's header line>
System Build <No> ? YES
Source Input Device <SY:> ?
Library Output Device <SY:> ?
Target System Device <SY0:> ?
Library Account <[1,2J> ?
Locate logical 'LB:' on <SY:[1, 1J> ?
Function (BUILD/PATCH, PATCH, BUILD) <BUILD/PATCH> ?
Patch file input location <SY: [200,200J> ?
Save patched sources <NO> ?
Run-Time System <BASIC> ?
Additional control file is <NONE>? <If>
If you only need to patch the library
response to the "Function" question.

programs,

Most other patches must be applied using the
format of the PBUILD dialogue is as follows:

specify
program

"PATCH"
PBUILD.

in
The

RUN $PBUILD
<PBUILD's header line>
Read files to patch from <SY:[1,2J>:
Compile patched programs <YES>:
Library device <SY: [1,2J>:
System device <SY0: [1,2J>:
Save patched sources <NO>:
#filnam
(name of the patch command file you are applying)
4.3.3

OPTIONAL FEATURE PATCHES

RSTS/E Patch Kits patch files for all optional Feature patches published in
the RSTS/E V7.2 Maintenance Notebook and the RSTS/E Software Dispatch. In
general, no command files exist for these files unless there are also
Mandatory patches for the component. If there are Mandatory patches for the
components, comment lines will appear in command files that include references
to any feature patches for the component. The referenced patches may be
automatically applied along with the mandatory patches by simply editing the
commented lines.
Note that some of the feature patch files require manual
editing (to supply installation-specific parameters) before they can be
appl ied.
Feature patches may be applied automatically by running el~ner $ONLPAT or
$CPATCH, as indicated in the associated article.
All patch file names
correspond to the article sequence number. For example, the patch file for

RSTS/E V7.2 Maintenance Notebook, June 1982
Patching Procedure

Page 4-7

BASIC-PLUS article Seq 4.1.4 F. "Default to EXTEND mode", is PA04!J1.004.
To apply this patch using $ONLPAT, you would type:
RUN $ONLPAT
Command File Name? PA0401.004
File to patch? (name of BASIC~PLUS run-time system)
Command File Name?

To use $CPATCH to apply
Password", you would type:

patch

Seq

1!J.12.8 F,

"Enable

Auxiliary

RUN $CPATCH
<CPATCH's header line>
File to patch - LOGIN.BAS=LOGIN.BAS
IIPA1012.002
Patch from SY:[P,PNJPA1012.002 complete.

trz
File to patch _

followed by the commands necessary to compile the
account.

program

into

the

desired

RSTS/E V7.2 Maintenance Notebook, June 1982
RSTS/E Articles

5.g

Page 5-1

RSTS/E Articles

Section 5.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 generates 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
Maintenance Notebook. This index will be updated monthly as new articles are
published in the RSTS/E Software Dispatch.
Note that all Mandatory and
Feature patches included in this list are included on the RSTS/E V7.2 Patch
Kit "A".

RSTS/E V7.2 Maintenance Notebook, June 1982
Cumulative Index of All Articles
5.1

Page 5-2

Cumulative Index of All RSTS/E V7.2 Maintenance Notebook Articles

Component

Sequence
Initialization

INIT.SYS Program Patches
CHANGE SAVRES DENSITY DEFAULT TO 1600 BPI
MAKING INOERROR THE DEFAULT
MAKING INOSTATS THE DEFAULT
CHANGING THE DEFAULT LINE FREQUENCY TO 50 HERTZ

1.1.1 F
1.1.2F
1.1.3F
1.1.4F

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

1.2.1 N

System Generation
Sysgen Notes
HOW TO CHANGE THE NUMBER OF SMALL BUFFERS SPECIFIED AT SYSGEN

2.2.1 N

Executive
Monitor Patches
MAKING RECEIVER DECLARATION NON-PRIVILEGED
FIRST FIT MEMORY ALLOCATION
CACHE REPLACEMENT TIME
DISABLING THE USE OF DATA SPACE

3.1.1 F
3.1.2 F
3.1.3 F
3.1.4 F

Terminal Service Patches
RESTRICTING TERMINAL MODES
IMMEDIATE MODEM HANG UP
CHANGING SPECIAL LOGIN TERMINAL
CHANGING A TERMINAL'S INPUT BUFFER QUOTA
INPUT ESCAPE SEQUENCE HANDLING
RESTRICTING PSEUDO-KEYBOARD MODES
INCREASING THE TIME ALLOWED FOR DIAL UP

3.3.1 F
3.3.2 F
3.3.3 F
3.3.4 F
3.3.5 F
3.3.6 F
3.3.7 F

Terminal Service Notes
2741 HARDWARE OPTIONS REQUIRED BY RSTS/E
2741 TERMINAL INTERFACE WIRING
UNDERSTANDING SYNCHRONIZATION DELAYS
UNDERSTANDING TERMINAL PARITY AND STOP BIT SETTINGS
MODEM CONTROL ON PRIVATE, LEASED LINES

3.4.1 N
3.4.2 N
3.4.3 N
3.4.4 N
3.4.5 N

RSTS/E V7.2 Maintenance Notebook, June 1982
Cumulative Index of All Articles

Page 5-3

File Processor Patches
AUXILIARY LIBRARY ACCOUNTS
CHANGING DEFAULT PROTECTION CODE
RESTRICTING DISK MODES
MAKING FIP SYS CALLS PRIVILEGED
RESTRICTING NON-PRIV ACCESS TO NON-FILE STRUCTURED DISKS
NON-PRIVILEGED WRITES TO NON-FILE STRUCTURED DISKS
ALLOWING CROSS ACCOUNT CREATIONS
ALLOWING CROSS ACCOUNT RENAME OPERATIONS
EXTENDING DIRECTORY LOOKUP
RESTRICTING NON-PRIVILEGED USE OF UU.TRM
ALLOWING USERS WITH TEMP PRIVS TO SET PRIV PROT CODES
MAKING REASSIGN A PRIVILEGED FUNCTION

3.5.2 F
3.5.3 F
3.5.4 F
3.5.5 F
3.5.6 F
3.5.7 F
3.5.8 F
3.5.9 F
3.5.1121 F
3.5.11 F
3.5.12 F

Device Driver Patches
SPECIAL LINE PRINTER DRUMS
CHANGING DEFAULT PRINTER FORM LENGTH
ALLOW SPECIAL CONTROL CHARACTERS
TU16/TE16/TU45/TU77 MAGNETIC TAPE DENSITY/PARITY DEFAULT
USING THE CSS PAPER TAPE READER ON RSTS/E V7.1
TS11 REWIND PROBLEMS - MANDATORY DEVICE DRIVER PATCH

3.7.1 F
'-3.7.2 F
3.7.3 F
3.7.4 F
3.7.5 F
3,7.6 F

FMS Monitor Patches
FMSTIO PATCH - MANDATORY FMS MONITOR PATCH

3.9.1 M

3.5.1 F

BASIC-PLUS
BASIC-PLUS Patches
SPECIAL PRINT-USING CHARACTERS
4. 1 • 1 F
DEFAULT SCALE FACTOR
4.1.2 F
OMITTING SCALE FACTOR WARNING MESSAGE
4.1.3 F
DEFAULT TO EXTEND MODE
4.1.4 F
NO IMMEDIATE MODE FROM .BAS FILE
4. L 5 F
NO PPN'S IN CATALOG COMMAND
4.1.6 F
DISABLING THE CCL SYS CALL
4.107 F
CLEAR I/O BUFFERS USED BY OPEN STATEMENTS
4.1.8 F
FORCE "ILLEGAL STATEMENT" ERROR IIHlEN USING OBSOLETE SEND/RECEIVE 4.1.9 F
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

4,1(0,1 N

4.10.2 N
LI.10'.3 F

4,10.4 F
L!.10'.5 F

4.10.6 F

RSTSIE V7,2 Maintenance Notebook, June 1982
Cumulative Index of All Articles

Page 5-4

TECO
TECO Notes
NOTE ON THE HANDLING OF THE IB+ AND IB2 SWITCHES

9.1.1 N

RSTS/E UTILITIES
System Utilities Package
DIRECT
ALLOW NON-PRIV ACCESS TO CROSS ACCT DIRECTORIES

10.3.1 F

LOGIN
INSTALLING USER MODIFICATIONS OR FEATURE PATCHES TO LOGIN
UNSCRUPULOUS PROGRAMS MAY CHAIN TO LOGIN
LOGIN CAN PRINT A MESSAGE FOR SPECIFIC ACCOUNTS
LOGIN CAN CHAIN TO A SPECIFIED PROGRAM
DON'T LOG ACCESS ATTEMPTS OVER DIAL-UP LINES
CHANGING LOGIN TO SET A DIFFERENT SWAP MAXIMUM
ENABLE LOGGED-OUT COMMANDS
ENABLE AUXILIARY PASSWORD

10.12.1 N
10.12.2 F
10.12.3 F
10.12.4 F
10.12.5 F
10.12.6 F
10.12.7 F
10.12.8 F

SHUTUP
CHANGING 'SHUTUP' SLEEP PARAMETERS

10.21.1 F

VT55
VT55 GRAPHICS DISPLAY TERMINAL SUPPORT

10.30. 1 N

Error Control Package
Package Notes

UNDERSTANDING "PA MEMORY SYSTEM" ERROR LOGS

12.1.1 N

Backup Package
BACDIR
DISABLE PRINTING OF "PLACED FILE, .. " WARNING MESSAGES

13.5.1 F

Spooling and Operator Services Package
Package Notes
NOTES ON USE OF THE SERIAL LA180 (LA180S) TERMINAL UNDER V7.1

14.1.1 N

QUE
DISABLE OPERATOR QUEUEING TO OTHER USERS ACCOUNT

14.4,1 F

QUMRUN
DISABLING 'JOB WITH DIFFERENT FORM NAME WAITING' MSG
RESTRICTING THE ASSIGNMENT OF BA:
DISABLE OPERATOR QUEUEING TO OTHER USERS ACCOUNT

14.6.1 F
14.6.2 F
14.6.3 F

RSTS/E V7.2 Maintenance Notebook, June 1982
Cumulative Index of All Articles

Page 5-5

SPLRUN
ELIMINATING EXTRA FORM FEEDS ON SPECIAL FORMS

14.1(~.1

BATRUN
$EOJ DOES NOT RESET ERROR CONDITION

14.15.1 F

System Management Guidelines
USING SAVE/RESTORE ON A TWO-DISK SYSTEM
USING BACKUP ON A TWO-DISK SYSTEM
CREATING A SYSTEM DISK RECOVERY MEDIUM

16.1.1 N
16.1.2N
16.1.3N

Automated Patching Facility Package
Package Notes
RSTS/E V7.1 PATCH KIT "A" PATCHING PROCEDURE

17.7.1 N

ATPK
NOTES ON ATPK
ALLOWING ATPK TO DETACH FOR NON-PRIVILEGED USERS
LIMITING THE USE OF THE $LOGIN COMMAND

17.7.1 N
17.7.2 F
17.7.3 F

RUN-TIME SYSTEMS SUPPORT
DCL
Package Notes
FILE SPECIFICATIONS IN DCL
DCL CAN TRANSLATE LOGICAL DEVICE NAMES TWICE
SETTING UP THE DCL LINK COMMAND
SOME DIFFERENCES BETWEEN DCL AND BASIC-PLUS
DCL.RTS
RUNNING DCL AT INCREASED PRIORITY
CHANGING DCL BASIC COMMAND DEFAULT FROM /BPLUS TO /BP2
CHANGING BASIC-PLUS KBM NAME IN DCL
CHANGING BASIC-PLUS-2 KBM NAME IN DCL
CHANGING DCL MACRO COMMAND DEFAULT FROM /RSX11 TO /RT11
CHANGING DCL FORTRAN COMMAND DEFAULT TO FORTRAN IV
CHANGING DCL FORTRAN COMMAND DEFAULT TO FORTRAN-lV-PLUS
CHANGING DEFAULT LANGUAGE FOR LINK TO FORTRAN IV OR RT11 MACRO
CHANGING DEFAULT LANGUAGE FOR LINK TO DIBOL
COBOL-81, FORTRAN-77, OR FORTRAN-lV-PLUS
PRELIN
ENABLE COBOL-81 AND FMS RESIDENT LIBRARIES TO CLUSTER

20. 1. 1 N
20.1.2 N
20.1.3 N
20.1.4 N
20.2. 1 F
20.2.2 F
20.2.3 F
20.2.4 F
20.2.5 F
20.2.6 F
20.2.7 F
20.2.8 F
20.2.9 F

20.4.1 F

RSTS/E V7.2 Maintenance Notebook, June 1982
Cumulative Index of All Articles

Page 5-6

RSX Emulator and Utilities Package
Package Notes
USING RTSODT FOR DEBUGGING RUN-TIME SYSTEMS
NOTES ON WRITING KEYBOARD MONITORS

21. 1. 1 N
21.1.2N

RSX.RTS
MAKING TASK IMAGES NON-SWAPPABLE
DISABLING POST-MORTEM DUMPS FOR CTRLIC ABORTS
CHANGE KEYBOARD ~1ONITOR PROMPT
CHANGE PROGRAM NAME OF KEYBOARD MONITOR
INVOKING A MENU PROGRAM

21.3.1 F
21.3.2 F
21.3.3 F
21.3.4 F
21.3.5 F

CRF.TSK
USING THE RSX CRF UTILITY

21.13.1 N

RT-11 Emulator and Utilities Package
Package Notes
USE OF UNDERSCORE IN RTll EMULATOR UTILITIES
USING RTSODT FOR DEBUGGING RUN-TIME SYSTEMS

22. 1. 1 N
22.1.2N

HOOK.SAV
NOTES ON HOOK.SAV

22.5.1 N

PIP.SAV
SETTING INEWFILE AS A DEFAULT PIP.SAV OPTION
TRANSFERRING FILES BY DATE OF LAST ACCESS
REQUIRING VOLUME I.D. SPECIFICATIONS WITH ANSI MAGNETIC TAPES
SETTING ILOG AS A DEFAULT PIP.SAV OPTION
MAKING IE RASE IMPLY IDELETE

22.13. 1 F
22.13.2 F
22. 13.3 F
22.13.4 F
22.13.5 F

SAVRES.SAV
CHANGE SAYRES DENSITY DEFAULT TO 160@ BPI
MAKING INOERROR THE DEFAULT
MAKING INOSTATS THE DEFAULT

22. 19. 1 F
22.19.2 F
22.19.3 F

Page 5-7

RSTS/E V7.2 Maintenance Notebook, June 1982
Patch Levels for Commonly Used System Programs (CUSPs)
5.2

Patch Levels for Commonly Used System Programs (CUSPs)

This report reflects the current Version/Edit level of all of the Commonly
Used System Programs (CUSPs) supplied as part of the standard RSTS/E V7.2-04
System Library Programs release.
System Utilities Package
BUILD V7.2-04
DSKINT V7.2-@4
V7.2-@4
INIT
MONEY V7.2-04
QUOLST V7.2-@4
SHUTUP V7.2-04
TALK
V7.2-@4
UTILTY V7. 2-04

DIRECT V7.2-@4
GRIPE V7.2-04
LOGIN V7.2-@4
ODT
V7.2-@4
REACT V7.2-04
SWITCH V7.2-04
TTYSET V7.2-@4
VT@5
V7.2-@4

DISPLY V7.2-@4
HELP
V7.2-04
LOGOUT V7.2-04
PLEASE V7.2-@4
REORDR V7.2-@4
SYSTAT V7.2-04
UMOUNT V7.2-04
VT50
V7.2-@4

BPCRF1 V7.2-@4
FIT
V7.2-@4
PMDUMP V7.2-@4

COpy
V7.2-04
FLINT V7.2-@4
RUNOFF V7.2-04

ANALY1 V7.2-@4
ERRBLD V7.2-@4A
ERRDIS V7.2-@4

ANALY2 V7.2-@4
ERRCPY V7.2-@4
ERRINT V7.2-@4

BACCON V7.2-@4
BACDMP V7.2-@4
BACFRM V7.2-@4
BACLST V7.2-@4
BACKTO V7.2-@4

BACDEL V7.2-04
BACDSK V7.2-@4
BACLAB V7.2-@4
BACMNT V7.2-@4
BACKUP V7.2-@4

Data Manipulation Package
BPCREF V7.2-@4
FILCOM V7.2-@4
MAKSIL V7.2-@4
Error Control Package
ANALYS V7.2-@4
ANALY3 V7.2-@4
ERRDET V7.2-04
Backup Package
BACCOM V7.2-04
BACDIR V7.2-@4
BACENT V7.2-@4
BACLOD V7.2-@4
BACPRM V7.2-04

Spooling and Operator Services Package
BATCH V7.2-04
BATIDL V7.2-@4
OPSER V7.2-@4
QUEMAN V7.2-@4
SPLRUN V7.2-@4

BATDCD V7.2-@4
BATRUN V7.2-04
OPSRUN V7.2-04
QUMRUN V7.2-@4
SPOOL V7.2-@4

BATDEC V7.2-04
CHARS V7.2-04
QUE
V7.2-@4
SPLIDL V7. 2-@4

RSTS/E V7.2 Maintenance Notebook, June 1982
Patch Levels for Commonly Used System Programs (CUSPs)

Page 5-8

Automated Patching Facility Package
ATPK
V7.2-04
ONLPAT V7.2-04

AUTOED V7.2-04
PATCPY V7.2-04

CPATCH V7.2-04
PBUILD V7.2-04

CPUTST V7. 2-04
DTEXER V7.2-04
LPEXER V7.2-04
PREXER V7.2-04

DSKEXR V7.2-04
DXEXER V7.2-04
MTEXER V7.2-04
DDEXER V7.2-04

Device Test Package
CPEXER V7.2-04
DSKSEK V7.2-04
KBEXER V7.2-04
PPEXER V7. 2-04
DCL
PRELIN V7.2-04

SHOTER V7.2-04

RSTS/E V7.2 Maintenance Notebook, June 1982
Protection Codes for Commonly Used System Programs (CUSPs)
5.3

Page 5-9

Protection Codes for Commonly Used System Programs (CUSPs)

This table lists the protection codes for the Commonly Used System Programs
(CUSPs) supplied as part of the standard RSTS/E V7.2 System Library Program
release. These protection codes are used when the programs are installed, and
should be used when re-compiling the programs after patching.
System Utilities Package
BUILD <124>
<124>
INIT
<124>
ODT
REORDR <124>
TALK
<232>
VT5DPY <232>

DIRECT <232>
LOGIN <232>
PLEASE <232>
SHUTUP <124 >
TTYSET <1@4>
VT50PY <232>

DSKINT <124>
LOGOUT <232>
QUOLST <232>
SWITCH <232>
UMOUNT <232>

GRIPE <232>
MONEY <1@4>
REACT <124>
SYSTAT <232>
UTILTY <124>

BPCRF1 <1@4>
FLINT <1@4>

COpy
<1@4>
MAKSIL <1@4>

FILCOM <1@4>
PMDUMP <1@4>

ANALY1 <124>
ERRCPY <124>

ANALY2 <124>
ERRDET <124>

ANALY3 <124>
ERRDIS <124>

BACCON <232>
BACDSK <232>
BACLOD <232>
BACKTO <232>

BACDEL <232>
BACENT <124>
BACLST <232>
BACKUP <232>

BACDIR <232>
BACFRM <232>
BACMNT <232>

BATDEC <124>
OPSER <124>
QUMRUN <124>

BATIDL <124>
OPSRUN <124>
SPLIDL <124>

CPATCH <124>

ONLPAT <124>

Data Manipulation Package
BPCREF <1@4>
FIT
<232>
RUNOFF <1@4>
Error Control Package
ANALYS <124>
ERRBLD <124>
ERRINT <124>
Backup Package
BACCOM <232>
BACDMP <232>
BACLAB <232>
BACPRM <124>

Spooling and Operator Services Package
BATCH <124>
BATRUN <124>
QUE
<232>
SPLRUN <124>

BATDCD <124>
CHARS <124>
QUEMAN <124>
SPOOL <124>

Automated Patching Facility Package
ATPK
<252>
PATCPY <124>

AUTOED <124>
PBUILD <124>

RSTS/E V7.2 Maintenance Notebook, June 1982
Protection Codes for Commonly Used System Programs (CUSPs)

Page 5-10

Device Test Package
CPEXER <124>
DTEXER <124>
MTEXER <124>

CPUTST <124>
DXEXER <124>
PPEXER <124>

DSKEXR <124>
KBEXER <124>
PREXER <124>

DCL
PRELIN <232>

SHOTER <124>

RSX Emulator Package
CRF.TSK
<104>
<104>
LBR.TSK
RNO.TSK
<104>
SYSLIB.OLB <40>

CSPCOM.OLB <40>
<104>
MAC.TSK
RSXMAC.SML <40>
<104>
TKB.TSK

CSPCOM.TSK <124>
PAT.TSK
<104>
SLOTKB.TSK <104>

<104>
HOOK.SAV
LOGIN.SAV <232>
ONLCLN.SAV <124>
SAVRES.SAV <124>
SYSGEN.SAV <124>

<104>
LIBR.SAV
LOGOUT.SAV <232>
<104>
PAT.SAV
SILUS.SAV <104>
UTILTY.SAV <104>

RT-11 Emulator Package
<104>
CREF.SAV
LINK.SAV
<104>
MACRO.SAV <104>
PIP.SAV
<232>
SYSBAT.SAV <124>

DSKSEK <124>
LPEXER <124>
DDEXER <124>

Page 5-11

RSTS/E V7.2 Maintenance Notebook, June 1982

Compiling CUSPs under BASIC-PLUS-2 or RSX <CSPCOM)
5.4

Compiling CUSPs under BASIC-PLUS-2 or RSX (CSPCOM)

The patching procedure included in those articles that patch BASIC-PLUS source
code refer to this section for the appropriate procedure to be followed if
BASIC-PLUS is not your system default run-time system. (The BUILD/AUTOPATCH
will perform all of these steps for you if you are installing patches from a
patch kit.)
The
sequence of commands for compiling BASIC-PLUS programs under the
BASIC-PLUS run-time system is (items in square brackets are patch or program
dependent):
BASIC/BPLUS

(if currently in DCL)

OLD PRGNAM.BAS
[APPEND APPEND. BAS]
COMPILE [SY0:J$PRGNAM[<prot>J
The paragraphs which follow describe the comparable commands
or RSX (CSPCOM) is your system default run-time system.

BASIC-PLUS-2

Note that the following CUSPs must always reside on SY0:, regardless
system default run-time system:
ATPK

INIT

LOGOUT

SHUTUP

UTILTY

your

Page 5-12

RSTS/E V7.2 Maintenance Notebook, June 1982
Compiling CUSPs under BASIC-PLUS-2 or RSX (CSPCOM)
BASIC-PLUS-2
If BASIC-PLUS-2 is your primary run-time system, first issue
BASIC/BP2 (if you are currently using DCL) or SWITCH to BP2COM.

the

command

If an article indicates that the program "should be compiled under the BASIC2
run-time system", the compile sequence is:
SCALE 13
OLD PRGNAM.BAS
[APPEND APPEND. BAS]
COMPILE [SY@:]$PRGNAM[<prot>]/TSK/CHA/LIN/NODEB
If an article indicates that the program "must be task built
BP2COM run-time system", use the following sequence of commands:

against

the

Programs which must be task built include those which must reside on SY@:,
well as FILCOM and FIT.

SCALE 13
OLD PRGNAM.BAS
[APPEND APPEND.BAS]
COMPILE PRGNAM.OBJ/CHA/LIN/NODEB/OBJ
RUN SY:[1,2]TKB.TSK
[SY@:]$PRGNAM.TSK/FP=PRGNAM.OBJ,LB:BP2COM.OLB/LB
I

HISEG=BP2COM
UNITS=12
ASG =S Y: 5: 6: 7 : 8: 9: 1@: 11 : 12
II

RUN SY:[l,2]PIP.SAV
PRGNAM.OBJ/DE:NO
[[SY@:]$PRGNAM.TSK<prot>/RE]

"'z

RSTS/E V7.2 Maintenance Notebook, June 1982
Compiling CUSPs under BASIC-PLUS-2 or RSX (CSPCOM)

Page 5-13

RSX (CSPCOM)
If RSX is
commands:

your

primary

run-time

system,

use

the

SWITCH RSX
RUN $CSPCOM
PRGNAM.OBJ/OBJ=PRGNAM.BAS[,APPEND.BAS]
.. Z
RUN SY: [1,2]TKB.TSK
PRGNAM.TSK/FP=PRGNAM.OBJ,LB:CSPCOM.OLB/LB
I

UNITS=12
ASG=SY: 5: 6: 7: 8: 9: 1(1: 11: 12
II

RUN SY:[1,2]PIP.SAV
PRGNAM.OBJ/DE:NO
[[SY@:]$PRGNAM.TSK<prot>/RE]
.. Z

following

sequence

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 1. 1 . 1 F

Initialization
INIT.SYS Program Patches

1 of 3

CHANGE SAVRES DENSITY DEFAULT TO 1600 BPI - INIT.SYS FEATURE PATCH
PROBLEM:
SAVRES, as released, defaults to the lowest density (of 800 BPI and 1600 BPI)
allowed by a given tape drive (normally 800 BPI) for all tape 1/0. It may be
desirable at some installations to have SAVRES default to the highest density
allowed by a given tape drive for more compact storage of data. This is
especially true if all drives on the system support 1600 BPI and the problem
described below is not applicable.
CAUTION
If the tape drive being used has a TM02 formatter, the hardware
bootstrap of a 1600 BPI tape will not be possible.
(You can
determine the formatter type by using the HARDWR LIST suboption
of INIT.) Therefore, if it is desirable for SAVRES to create
tapes which are bootable on such a drive it is recommended that
this patch not be installed. Normally, TU16 and TU45 drives use
a TM02 formatter, TE16 and TU77 drives do not.
SOLUTION:
The following feature patch will cause the SAVRES option of INIT.SYS to
default to the highest density allowed by a given tape drive for all tape 1/0.
This default can be overridden by attaching the IDENSITY:800 switch to the
device specification.
Refer also to article Seq 22.19.1 F, which supplies a
similar patch for SAVRES.SAV.
PROCEDURE:
l-

Since patching
This is a feature patch to the RSTS/E INIT. SYS Program.
the distribution medi urn is not recommended, the patch must be installed
every time the COPY option is used to copy INIT.SYS frum the distribution
medium. Any copy of the patched INIT.SYS will propagate the feature.

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

can

installed

using

the

PATCH

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Initialization
INIT.SYS Program Patches
3.

Seq 1.1.1 F
2 of 3

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

the

on-line

patching

(RETURN for manual patch installation)

The patch is also contained in a patch file appearing in patch kit version
II A" or later.
4.

New?
? "16
? "00
? 034377
? <If>
? <If>
? 1600.
? 800.
? "z

(no change; verify only)
(no change; veri fy only)
( CTRLlZ for new offset)
( CTRLlZ for new base)

(no change; verify only)
(no change; verify only)
(CTRLI Z for new offset)
( CTRLlZ for new base)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Ini tiali zation
INIT.SYS Program Patches
Base address? RESCTL
Offset address? 30
Base
Offset Old
?????? 000030 030070
?????? 000032 177460
?????? 000034 033061
?????? 000036 030060
?????? 000040 000377
?????? 000042 001440
?????? 000044 003100
?????? 000046 000000
Offset address? AZ
Base address? $$0101
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

Seq 1.1.1 F
3 of 3

New?
? "16
? "00
? 034377
? <If>
? <If>
? 1600.
? 800.
? AZ

(no change; verify only)
(no change; verify only)
(CTRLI Z for new offset)
( CTRLlZ for new base)

New?
? Q! 1
? AC

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

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 1.1.2 F

RSTS/E V7.2
Initialization
INIT.SYS Program Patches

1 of 2

MAKING INOERROR THE DEFAULT - INIT.SYS FEATURE PATCH
PROBLEM:
The INOERROR switch indicates that SAYRES should
conditions:
1.
2.

3.
4.

abort

under

the

following

A contiguous file is made non-contiguous
A placed file is "unplaced"
A bad comparison occurs
An unexpected bad block is encountered on the input RSTS/E
disk in a SAVE or IMAGE operation

Some installations, however, may always
circumstances.

want

SAYRES

abort

under

these

SOLUTION:
The following feature patch will make INOERROR, rather than IERROR, the
default in the SAYRES option of INIT.SYS. Note that the user may override the
default for a particular operation by specifying IERROR.
Refer also to
article Seq 22.19.2 F, which supplies a similar patch for SAVRES.SAV.
PROCEDURE:
1.

This is a feature patch to the RSTS/E INIT.SYS Program.
Since patching
the distribution medium is not recommended, the patch must be installed
every time the COpy option is used to copy INIT.SYS from the distribution
medium. Any copy of the patched INIT.SYS will propagate the feature.

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

can

installed

using

the

PATCH

Option: PATCH
File to patch? INIT.SYS

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

the

on-line

patching

(RETURN for manual patch installation)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Ini tiali zation
INIT.SYS Program Patches

Seq 1.1.2 F
2 of 2

The patch is also contained in a patch file appearing in patch kit version
"Ail or later.
4.

The patch is as follows:
Base address? .. NOER
Offset address? 2
Base
Offset Old
?????? 000002 0013010
?????? 000004 ??????
?????? 0001306 ??????
?????? 000010 ??????
?????? 000012 1300004
?????? 000014 ??????
Offset address? ~Z
Base address? $$0101
Offset address? 0
Offset Old
Base
?????? 0130000 ??????
?????? 000002 ??????

New?
? 4
? <If>
? <If>
? <If>
? 10
? AZ

(no change)
(no change)
(no change)

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

New?
? Q!2
? ~C

(up-arrowl C to exit; CTRLlC for INIT)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Initialization
INIT.SYS Program Patches

Seq 1.1.3 F
1 of 2

MAKING INOSTATS THE DEFAULT - INIT.SYS FEATURE PATCH
PROBLEM:
SAYRES always prints a summary report after completing a transfer unless the
INOSTATS (no statistics) switch is specified.
Certain installations may
prefer that this report NOT be printed unless specifically requested.
SOLUTION:
The following feature patch will make INOSTATS, rather than ISTATS, the
default in the SAYRES option of INIT.SYS. Note that the user may override
this default for a particular operation by specifying ISTATS. Refer also to
article Seq 22.19.3 F, which supplies a similar patch for SAVRES.SAV.
PROCEDURE:
1.

This is a feature patch to the RSTS/E INIT.SYS Program.
Since patching
the distribution medium is not recommended, the patch must be installed
every time the COpy option is used to copy INIT.SYS from the distribution
medi urn. Any copy of the patched INIT. SYS will propagate the feature.

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

can

installed

using

the

PATCH

Option: PATCH
File to patch? INIT.SYS
3.

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? INIT.SYS
File found in account [0,1J

the

on-line

patching

(RETURN for manual patch installation)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 1.1.3 F

RSTS/E V7.2
Initialization
INIT.SYS Program Patches
4.

2 of 2

The patch is as follows:
Base address? .. NOST
Offset address? 2
Base
Offset Old
?????? 000002 000040
?????? 000004 ??????
?????? 000006 ??????
?????? 000010 ??????
?????? 000012 000020
?????? 000014 ??????
Offset address? Z
Base address? $$0101
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

New?
? 20
? <lD
? GO
? GO
? 40
? Z
A

(no change)
(no change)
(no change)
( CTRLlZ for new offset)
(CTRLI Z for new base)

New?
? Q!4
? AC

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Initialization
INIT.SYS Program Patches

Seq 1.1.4 F
1 of 2

CHANGING THE DEFAULT LINE FREQUENCY TO 50 HERTZ - INIT.SYS FEATURE PATCH
PROBLEM:
When new Save Image Libraries (SIL's) are installed with INIT, the line
frequency will always default to 60 HERTZ. If your system uses an AC line
frequency of 50 Hz, then every installation of a new monitor requires that you
use the HARDWR HERTZ suboption to change this value.
SOLUTION:
The following INIT.SYS patch will set the default line frequency for the
installed monitor SIL and INIT.SYS to 50 Hz. Note that if you have previously
installed a monitor SIL with an unpatched copy of INIT.SYS, you must use the
HARDWR HERTZ suboption to change the line frequency for that monitor SIL (if
the monitor SIL is not currently installed, you must use the HERTZ suboption
to change its default line frequency the next time you install it).
This patch is most effective if applied before any SILs are installed. If you
are installing a monitor SIL for the first time, and you are using an INIT.SYS
which is patched as indicated below, the default line frequency will be 50 Hz.
PROCEDURE:
1.

This is a feature patch to the RSTS/E INIT.SYS Program.
Since patching
the distribution medium is not recommended, the patch must be installed
every time the COPY option is used to copy INIT.SYS from the distribution
medium. Any copy of the patched INIT.SYS will propagate the fix.

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

can

installed

using

the

PATCH

Option: PATCH
File to patch? INIT.SYS

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

the

on-line

patching

(RETURN for manual patch installation)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Ini ti ali zation
INIT.SYS Program Patches

Seq 1.1.4 F
2 of 2

This patch is contained in a patch file appearing in patch kit version "A"
or later.
4.

The patch is as follows:
Base address? .. DFHZ
Offset address? 0
Offset Old
Base
?????? 000000 000074
?????? 000002 ??????
Offset address? ~Z
Base address? $$0101
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

New?
50.

?
?

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

New?
? Q! 10
? ~C

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Initiali zation
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 re-configure these devices so that they conform to the
standard. Appendix C of the RSTS/E System Generation 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 V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Initialization
INIT.SYS Program Notes

Seq 1.2.1 N
2 of 2

The RSTS/E reserved locations, which may not be used as device vectors, are:
Addresses

RSTS/E usage

0-2
4-36
40-56

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
KW11-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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Generation
SYSGEN Notes

Seq 2.2.1 N
1 of 1

HOW TO CHANGE THE NUMBER OF SMALL BUFFERS SPECIFIED AT SYSGEN
It is often useful to be able to change the number of small buffers
monitor without repeating the entire system generation dialogue.

To do so, perform the following steps
1.

Edit CONFIG.MAC to indicate how many small buffers you want.
Change the
value of the symbol SMLBUF to indicate how many small buffers you want.

Reassemble TBL.MAC.

Relink and re-SILUS the monitor.

The value of SMLBUF indicates approximately how many general small buffers the
system will have if none are added during initialization. The value of SMLBUF
does not directly affect FIP small buffers.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.1.1 F

RSTS/E V7.2
Executive
Moni tor Patches

1 of 2

MAKING RECEIVER DECLARATION NON-PRIVILEGED - MONITOR FEATURE PATCH
The RSTS/E monitor normally requires that a job have permanent or temporary
privileges in order to declare itself to be a message receiver. There are
some production environments in which it is useful for non-privileged jobs to
have this capability. The following procedure allows you to patch the RSTS/E
monitor to remove the privileged status of the message receiver declaration
SYS call.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

The patch described below can be
INIT .SYS:
option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

Note that if you answered 'No' to the 'Resident Send/Receive' question
during system generation this patch will take effect immediately when
applied to the installed monitor SIL.
RUN $ONLPAT
Command File Name? <cr>
File to patch? <If>
File found in account [0,lJ

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"Ail or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Moni tor Patches
4.

2 of 2

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0301
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

Seq 3.1.1 F

New?
? Q! 1
? "c

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT, you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? <If>
Module name? OVR
Base address? .. RCVP
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 126427

(LINE FEED for installed monitor SIL)

New?
? 240
?

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

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.1.2 F

RSTS/E V7.2
Executive
Moni tor Patches

1 of 2

FIRST FIT MEMORY ALLOCATION - MONITOR FEATURE PATCH
When a residency request is made for a job or for a run-time system residency
without a specific load address, the RSTS/E monitor does a best fit
allocation: the job or run-time system is loaded into the smallest free area
in memory in which it fits. For some systems, especially those with a large
user memory region, a first fit allocation may result in better performance.
This monitor feature patch changes the memory
first fit.

allocation

from

best

fit

PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

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

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

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

It mbY be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
II Ail
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executi ve
Monitor Patches
4.

Seq 3. 1 .2 F
2 of 2

The patch is as follows:
Module name? GEN
Base address? .. FFIT
Offset address? 0
Base
Offset Old
?????? 000000 001627
?????? 000002 020203
Offset address? "z
Base address? "z
Module name? RSTS
Base address? $$0301
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

New?
? 627
? "z

New?
? Q!2
? "c

(CTRLI Z for new offset)
(CTRLI Z for new base)
(CTRLI Z for new module)

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

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.1,3 F

RSTS/E V7.2
Executive
Monitor Patches

1 of 2

CACHE REPLACEMENT TIME - MONITOR FEATURE PATCH
When data is installed in the disk cache, it will not be removed until a
certain minimum residency time has expired (unless the last block of a cluster
is read in sequential mode), The minimum residency time is meant to keep some
useful data in the cache, even when the cache is very small, and prevent
thrashing. For systems with large caches or rapidly changing disk access
patterns, it may be advantageous to reduce the minimum residency time from its
default value of 1 minute. The residency time may be changed to any integer
value in the range 0. to 65535. inclusive.
Refer to the RSTS/E System
Manager's Guide for a discussion of caching tradeoffs.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2" executive.
in any target monitor SIL.

Determine the new mInImum cache residency time in seconds. Use this value
as n in step 5 below. Be sure to include a period after the number so
that it is interpreted as a decimal number.

The patch described in Step 5 below
option of INIT.SYS:
Option: PATCH
File to patch? <If>

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

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

It may be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"Ail or later.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed,

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Monitor Patches
5.

Seq 3.1.3 F
2 of 2

The patch is as follows:
Module name? RSTS
Base address? •. CAGE
Offset address? 0
Offset Old
Base
?????? 000000 000074
?????? 000002 ??????
Offset address? "z
Base address? $$0301
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? n.
? "z

New?
? Q!4
? "c

( from step 2)
(CTRL/Z for new offset)
(CTRL/Z for new base)

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Monitor Patches

Seq 3.1.4 F
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 V7.2,
DECnet/E V2.0, FMS-11 V1.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.
Please refer to Section 1.1 of the RSTS/E V7.2 Release Notes for additional
information of Data Space.
SOLUTION:
The patching procedure detailed below will cause the monitor to never use Data
Space, regardless of whether the processor it is running on supports it or
not.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

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

can

installed

It may be installed
using

the

PATCH

(LINE FEED 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.
RUN $ONLPAT
Command File Name? <cr>
File to patch? <l f>
File found in account [0,1]

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Monitor Patches

Seq 3.1.4 F
2 of 2

This patch is contained in a patch file appearing in patch kit version "An
or later.
4.

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

New?
? \
? -1
? AZ

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

New?
? Q! 10
? AC

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Patches

Seq 3.3.1 F
1 of 2

RESTRICTING TERMINAL MODES - TERMINAL SERVICE FEATURE PATCH
The RSTS/E monitor normally allows any user to OPEN a terminal in binary mode
or echo control mode (if configured). There is a danger in the use of these
termin81 modes, since all characters (including CTRL/C) are passed to the user
program.
A novice user could easily find himself in a situation in which his
terminal does not respond. A malicious user could "lock up" a terminal in a
way which required the system manager to kill his or her job. The following
procedure allows you to patch the RSTS/E monitor to specify which terminal
OPEN modes require privileges.
Privileged users and non-privileged users
running privileged programs would still have full access to all available
terminal modes.
Attempts by non-privileged users to use restricted modes
would be rejected with no error message.
PROCEDURE:

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

Decide which terminal modes you wish to make privileged.
Consul t the
RSTS/E Programming Manual for the various modes which are available, and
determine the associated MODE values. Compute the sum, n, of the MODE
values corresponding to the modes you wish to restrict. If you calculate
the sum of the mode values in decimal, include a decimal point after the
value of n in the patch below so that it is interpreted as a decimal
number.

The patch described in Step 5 below
option of INIT.SYS:
Option: PATCH
File to patch? <If>

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

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

It may be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Patches

Seq 3.3.1 F
2 of 2

The patch is also contained in a patch file appearing in patch kit version
"Ali or later.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed.

The patch is as follows:
Module name? TER
Base address? .. KBMP
Offset address? -2
Base
Offset Old
?????? 177776 042702
?????? 000000 000000
?????? 000002 ??????
Offset address? Z
Base address? Z
Module name? RSTS
Base address? $$0303
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? Of>
? n
? AZ

(no change; verify only)
(from step 2)
(CTRL/Z for new offset)
(CTRL/Z for new base)
(CTRL/Z for new module)

New?
? Q! 1
? AC

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Patches

Seq 3.3.2 F
1 of 2

IMMEDIATE MODEM HANGUP - TERMINAL SERVICE FEATURE PATCH
When the carrier frequency drops on a modem line connecting a terminal to
RSTS/E, the monitor normally waits approximately 5 seconds before hanging up
the line. This allows recovery from transient line failures or accidental
unseating of a phone from an acoustic coupler. In certain areas, such as the
United Kingdom, computer systems are required to disconnect from such a line
within milliseconds.
The following patch causes RSTS/E to hang up a modem
line as soon as it detects loss of carrier signal on that line.
Note that
LOGIN automatically hangs up after an unsuccessful log-in attempt.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive. It may be installed
in any target monitor SIL that supports modem control.

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

can

installed

the

PATCH

(LINE FEED for installed monitor SIL)

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

using

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTSIE V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Executive
Terminal Service Patches
4.

Seq 3.3.2 F
2 of 2

The patch is as follows:
Module name? TER
Base address? .. UKMD
Offset address? 0
Offset Old
Base
?????? 000000 000404
?????? 000002 012704
Offset address? Z
Base address? Z
Module name? RSTS
Base address? $$0303
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

New?
? 240
? AZ

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

New?
? Q!2
? ~C

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Executive
Terminal Service Patches

Seq 3.3.3 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 LOGINS, NO LOGINS, and SET LOGINS functions of
UTILTY).
However, the console terminal (KB0:) is a special terminal, and can
log in regardless of the login setting, provided that swapping space and JOB
MAX permit.
With the patch given below, one or two special keyboards can be
this feature can be disabled entirely.

selected,

PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
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 below. If you wish
to allow only one terminal, use its number as m and use -1 in place of n.
If you wish 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 below
option of INIT.SYS:
Option: PATCH
File to patch? <If)

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr)
File to patch? <If)
File found in account [0,1J

It may be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Executive
Terminal Service Patches

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
Offset Old
Base
?????? 000000 000000
?????? 000002 001407
Offset address? ~Z
Base address? .. CTY.
Offset address? 0
Base
Offset Old
?????? 000000 177777
?????? 000002 001404
Offset address? "z
Base address? "z
Module name? RSTS
Base address? $$0303
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? m. *2 (or -1) ( from step 2)
? ~Z
( CTRL! Z for new offset)
(CTRL! Z for new base)
New?
? n.*2 (or -1) ( from step 2)
? ~Z
(CTRL!Z for new offset)
(CTRL! Z for new base)
(CTRL! Z for new module)

New?
? Q!lJ
? "c

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service patches

Seq 3.3.4 F
1 of 2

CHANGING A TERMINAL'S INPUT BUFFER QUOTA - TERMINAL SERVICE FEATURE PATCH
Inside every terminal's DDB (Device Data Block) is an "input buffer quota"
value.
The default value is 6. Since there are 30. characters in a buffer,
this is equal to 6 times 30. or 180. characters.
Terminal service will
attempt to buffer that many characters before telling the terminal to stop (by
sending it an XOFF). You can increase the input buffer quota value for one or
more high-speed input terminals by using this feature patch.
NOTE
There is no guarantee that a terminal will be able to allocate
its full buffer quota. A heavy system load may leave less than
the terminal's full buffer quota available. In addition, while
the installation of this patch will not have any direct adverse
effect on a system. it does cause more small buffers to be used.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

Decide which terminal will have its buffer quota altered, and use that
number as n in the patch below. Be sure you include the decimal point
after the value of n so that it is interpreted as a decimal number.
Also
decide i-lhat the new buffer quota for that termindl should be, and use that
number as m in the patch below. The legal values for mare 6. through
about 20. inclusive.

The patch described in step 5 below
option of INIT.SYS:
Option: PATCH
File to patch? <If>

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

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

It may be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Patches

Seq 3.3.4 F
2 of 2

The patch is also contained in a patch file appearing in patch kit version

"A" or later.

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

The patch is as follows:
Module name? RSTS
Base address? KBDDDB
Offset address? DDS.KB*n.+26
Offset Old
New?
Base
?????? ?????? 000006 ? m.
?????? ?????? 000000 ? Z
Offset address? Z
Base address? $$0303
Offset address? 0
Offset Old
Base
New?
?????? 000000 ?????? ? Q! 10
?????? 000002 ?????? ? AC
A

(n. is the KB number)
(from step 2)
(CTRL/Z for new offset)
(CTRL/Z for new base)

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 3.3.5 F

Executive
Terminal Service Patches

1 of 2

INPUT ESCAPE SEQUENCE HANDLING - TERMINAL SERVICE FEATURE PATCH

RSTS/E allows

multiple character incoming escape sequences.
Programming Manual fully describes the escape sequence handling.

RSTS/E

The

One of the multi-character escape sequences is ESCape followed by "P" followed
by one modifier character. On the VT52 terminal, the upper left hand key on
the auxiliary keypad (usually blue) generates ESC P. When the VT100 terminal
is operating in VT52 mode, the upper lefthand key on the auxiliary keypad
(usually labelled "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 standalone escape sequence with no required (or desired)
modifier character. You may install the following patch to change the
terminal service so that the ESCape, "P" sequence does not expect a modifier
character. Note that this patch affects all terminals on the system.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

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

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

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

It may be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.3.5 F

RSTS/E V7.2
Executive
Terminal Service Patches
4.

2 of 2

The patch is as follows:
Module name? TER
Base address? .. ESCP
Offset address? ~
Base
Offset Old
?????? ~~~~00 ~50001
?????? 0000~2 ??????
Offset address? ~Z
Base address? ~Z
Module name? RSTS
Base address? $$0303
Offset address? ~
Base
Offset Old
?????? ~~0~0~ ??????
?????? ~0~002 ??????

New?
?
?

Q&1774~0
~Z

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

New?
? Q!20
? ~C

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Patches

Seq 3.3.6 F
1 of 2

RESTRICTING PSEUDO KEYBOARD MODES - TERMINAL SERVICE FEATURE PATCH
The RSTS/E monitor normally allows any user to OPEN a pseudo keyboard with
mode 1%. which causes the controlled job to detach rather than be killed if
the controlling job closes the pseudo keyboard prematurely. There is a danger
in the use of this mode, since a non-privileged user could fill the system
with detached jobs. The following procedure allows you to patch the RSTSI E
monitor to specify which pseudo keyboard OPEN modes require privileges.
Privileged users and non-privileged users running privileged programs would
still have full access to all available pseudo keyboard modes.
If a
non-privileged user specifies a restricted mode, the mode value will be
ignored but no error message will be printed.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

Decide which pseudo keyboard modes you wish to make privileged.
Consult
the RSTS/E Programming Manual for the various modes which are available,
and determine the associated MODE values. Compute the sum, n, of the MODE
values corresponding to the modes you wish to restrict. If you calculate
the sum of the mode values in decimal, include a decimal point after the
value of n in the patch below so that it is interpreted as a decimal
number.

The patch described in Step 5 below
option of INIT.SYS:
Option: PATCH
File to patch? <If>

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

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

It may be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executi ve
Terminal Service Patches

Seq 3.3.6 F
2 of 2

The patch is also contained in a patch file appearing in patch kit version
"A" or 1 ater .
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? .. PKMP
Offset address? -2
Base
Offset Old
?????? 177776 142761
?????? 000000 000000
?????? 000002 ??????
Offset address'? ~Z
Base address? ~Z
Module name? RSTS
Base address? $$0303
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

New?
? <If>
? n
? ~Z

(no change; verify only)
(from step 2)
(CTRL/Z for new offset)
(CTRL/Z for new base)
(CTRL/Z for new module)

New?
? Q!40
? ~C

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Patches

Seq 3.3.7 F
1 of 2

INCREASING THE TIME ALLOWED FOR DIAL UP - TERMINAL SERVICE FEATURE PATCH
PROBLEM:
Terminal Service is distributed with a 30 second timeout limit for dialing to
a host.
This time may not be sufficient, for example, when dialing to a
long-distance number.
SOLUTION:
You can increase the timeout limit with the following patch.
We recommend
that you increase the timeout limit to 90 or 12£1 seconds. The maximum timeout
limit is 127 seconds.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

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

can

installed

It may be installed
using

the

PATCH

(LINE FEED for installed monitor SIL)

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Patches
4.

Seq 3.3.7 F
2 of 2

The patch is as follows:
Module name? TER
Base address? .• WRNG
Offset address? -2
Base
Offset Old
?????? 177776 13127134
?????? 131313131313 ??????
?????? 131313131313
???
?????? 13131313131
11313
Offset address? "z
Base address? "z
Module name? RSTS
Base address? $$03133
Offset address? 0
Offset Old
Base
?????? 1301301313 ??????
?????? 0131313132 ??????

New?
? <LF>
? \
? n.
? "z

(no change; verify only)
(n.=number of seconds 1-127.)
(the period indicates decimal)
(value as opposed to octal.)
(CTRL! Z for new offset)
(CTRL/Z for new base)
(CTRL/Z for new module)

New?
? Q! 1013
? .... C

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Notes

Seq 3.4.1 N
1 of 1

2741 HARDWARE OPTIONS REQUIRED BY RSTS/E
RSTS/E supports 2741-compatible terminals connected through DL11D and DL11E
single-line interfaces and through DH11 and DZ11 multiplexors. Certain 2741
hardware options are required for proper operation under RSTS/E.
The ability to detect "reverse break" is an option on 2741 terminals supplied
by some manufacturers, including IBM. A reverse break is a control sequence
sent by the computer to a terminal which is currently transmitting (keyboard
is unlocked). The purpose of the reverse break is to force the terminal into
the receive state (keyboard locked). RSTS/E sends a reverse break any time
the system has output for the 2741 terminal but internal status tables
indicate that the terminal is in the transmit state. If the terminal does not
recognize the reverse break sequence, lock the keyboard, and switch to the
receive state, the output will be lost and the terminal can end up in a
strange state.
IBM refers to the reverse break detection capability on the IBM 2741 Model
Communications Terminal as Feature #4708 - Receive Interrupt. This option
must be installed on all IBM 2741 terminals for correct operation under
RSTS/E.
The ATTENTION key is also optional on IBM 2741 terminals and is required for
operation under RSTS/E. The ATTN key generates a break which is interpreted in
several ways by RSTS/E software. The RSTS/E System User's Guide describes the
various functions of the ATTN key.
IBM refers to the ATTN key and the
associated break generation hardware as Feature #7900
Transmit Interrupt.
This option is commonly included on 2741 terminals supplied by IBM and is a
standard feature on many 2741-compatible terminals supplied
by
other
manufacturers.
NOTE
2741-compatible terminals are supported
upgrading from RSTS/E V7. 1 to RSTS/E V7. 2.

only

for

customers

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Notes

Seq 3.4.2 N
1 of 1

2741 TERMINAL INTERFACE WIRING
The DL11D and DL11E terminal line interfaces require a special configuration
for supporting the 2741. The configuration requires 6 data bits, 1 start bit,
1 stop bit, odd parity, 134.5 baud, and rotary switch position 3 for both
input and output (full counter-clockwise is position 1). The following jumpers
apply to each condition:
Condition

Jumper

6 Data bits

NB1
NB2

out
in

1 Stop bit

2SB
J9
J10
J 11

in
out
in
out

Odd parity

NP
EPS

in
in

The
134.5
baud
specification requires a 1.03296M
#18-05502-6). Refer to the DL11 Installation Procedure
pertinent to the DL11D and DL11E.

crystal (DEC part
for specifications

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Notes

Seq 3.4.3 N
1 of 3

UNDERSTANDING SYNCHRONIZATION DELAYS
DIGITAL's video terminals (VT50, VT52, VT100, etc.) use two special control
characters (commonly called XOFF and XON) to request the host computer to
suspend and resume data transmission.
One use of this synchronization
protocol allows the terminal to "freeze" a screen of data giving the user a
chance to read it before it has scrolled off the screen.
On VT50-series
terminals, this special mode, called HOLD SCREEN MODE, is enabled and disabled
with escape sequences. Once enabled, the terminal detects when a line is
about to be scrolled from the screen. The character received from the host
computer that would cause the scroll is line feed (LF). At this point, the
terminal sends an XOFF to the host and waits for the user to type the SCROLL
key. During this time, the terminal will accept and buffer in a temporary
storage area (called a silo) further characters received from the host. Even
if the host computer can cease transmission with no software delays, there are
delays in line transmission that cause a determinable number of characters to
be received by the terminal after it has sent the XOFF.
HOLD SCREEN MODE is just one use of this synchronization protocol.
Another
use is in the handling of the hard copy option of the VT50-series terminals.
The copier is slow (at least compared to the video screen) and the terminal
must ask the host computer to suspend transmission so that it does not miss
data when the copier is running.
The LA34 , LA38, and LA120 terminals use this synchronization protocol, and
when the LA180 DECprinter I is connected to the computer through a serial line
interface (referred to as the LA180S), it also uses this protocol.
If the
printer "gets behind" due to high line transmission speed or carriage restore
time, it requests the host to suspend data transmission.
The printer will
also send an XOFF if its ONLINE/OFFLINE switch is placed into the OFFLINE
position or if it runs out of paper.
The RSTS/E terminal service processing of the synchronization
enabled and disabled by the TTYSET commands STALL and NO STALL.
Below is the formula used for calculating the largest number
that would be received after the terminal has sent the XOFF:
1 + ( 3*Y/X ) + 2*D*Y

protocol
of

characters

where

X is the terminal's transmission rate in characters per second (CPS), Y is the
host computer's transmission rate in CPS, and D is the delay time in seconds
for a character to travel from one end of the line to the other.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.4.3 N

RSTS/E V7. 2
Executive
Terminal Service Notes

2 of 3

Note: This formula assumes that there is no host computer
software delay.
In reality there is always some delay at the
host computer. This delay might be very small or possibly
large, depending on system loading and other I/O interrupt
activity.
Considering the formula from left to right:
The 1 is the character storage requirement for the line
the XOFF in the first place.

feed

that

triggered

The 3*Y/X is due to the nature of the UART (Universal
Asynchronous
Receiver/Transmitter) in the terminal.
Since the UART is normally double
buffered, there can be up to two characters already in the UART's buffers when
the terminal decides to send the XOFF. Those two characters plus the XOFF
correspond to three character times of terminal to host transmit during which
the host may be sending to the terminal. Therefore, it is the ratio of the
host and terminal transmission rates that is important for three terminal
transmission times.
The 2*D is the total time delay for the line in both directions (the 2) to
clear.
During this time the host computer may have sent up to 2*D*Y
characters to the terminal.
The formula presented here is not completely correct for the VT50 series of
video terminals.
The VT50 does not double buffer transmission to the host
computer in its UART. On the other hand, the formula can be used as a worst
case formula to ensure correct operation of the XON/XOFF Synchronization
Protocol.
The following tables give the required size of the temporary storage area
(silo) given: 1) the transmission speed (baud rate) from the host computer to
the terminal, 2) the transmission speed from the terminal to the host
computer, and 3) the physical delay of the transmission line. Local terminal
connections have essentially a zero delay factor. The Phone Company specifies
a nominal worst case delay of 50ms in a coast-to-coast connection, assuming it
is not via satellite.
The horizontal scale of baud rates is the baud rate from the host computer
the terminal.

The vertical scale of baud rates is the baud rate from the terminal to the
host computer. Baud rates can be converted to characters per second (CPS) by
dividing the baud rate by 10 (1 start bit + 8 data bits + 1 stop bit = 10
bits), with the exception of 110 baud which corresponds to 10 CPS (1 start bit
+ 8 data bits + 2 stop bits) .

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.4.3 N

RSTS/E V7.2
Executive
Terminal Serv ice Notes

3 of 3
0ms Line Delay
Transmit Speed to Terminal

4800
145
97
49
25
13
7
4
3

9600
289
193
97
49
25
13
7
4

2400
97
73
49
37
31
28
27
26

4800
193
145
97
73
61
55
52
51

9600
385
289
193
145
121
109
103
100

By referring to the manual that came with your terminal,
which baud rate combinations are legal for your terminal.

you

can

Receive
Speed
from
Terminal
(X)

110
150
300
600
1200
2400
4800
9600

110
4
3
2
2

150
6
4
3
2

300
10
7
4
3
2
1
1

600
19
13
7
4
3
2

1200
37
25
13
7
4
3
2

(y)

2400
73
49
25
13
7
4
3
2

50ms Line Delay
Transmit Speed to Terminal

Receive
Speed
from
Terminal
(X)

110
150
300
600
1200
2400
4800
9600

110
5
4
3
3
2
2
2
2

150
7
6
4
3
3
3
3
3

300
13
10
7
6

5
4
4
4

600
25
19
13
10
9
8
7
7

1200
49
37
25
19
16

15
14
13

(y)

determine

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Notes

Seq 3.4.4 N
1 of 1

UNDERSTANDING TERMINAL PARITY AND STOP BIT SETTINGS
Terminal Parity
The TTYSET commands "NO PARITY", "EVEN PARITY", and "ODD PARITY" control the
format in which data characters are sent to a terminal. NO PARITY (the
default) sends the full 8 bits of a byte out to a terminal. EVEN PARITY and
ODD PARITY 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". NO PARITY yields 8 bit data, EVEN PARITY and ODD
PARITY yield 7 bit data.)
The DL11A/B/C/D/E and DJ11 interfaces do not have programmable hardware parity
generation.
For these interfaces, terminal service generates the output
parity bit. The DH11 and DZ11 have programmable hardware parity generation,
which is used by terminal service.
Stop Bit Settings
Terminal interfaces with programmable baud rate settings (DH11 and DZ11) also
have programmable stop-bit settings. RSTS/E 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)/(1+8+2 bits per character)=110/11=10 characters per second
(300 bits per second)/(1+8+1 bits per character)=300/10=30 characters per second

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Notes

Seq 3.4.5 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 (i.e., data signals
only) then the line should be set as a local line using the INIT SET option.
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 recelvlng 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
RSTS/E does not control this signal; the modem does.

other

modem.

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

and

clears

Data

Terminal

Ready

and

Request

Send

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Terminal Service Notes

Seq 3.4.5 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
Carrier Detect and Clear to Send.

RSTS/E enables the line for data communication.

Data communication occurs ...

The other end
Clear to Send.

RSTS/E starts a 5 second timeout.

The timeout expires.
Send.

drops

carrier.

Send.

The

modem

sets

The modem clears Carrier Detect and

RSTS/E clears Data Terminal Ready and Request to

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 V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.1 F
1 of 2

AUXILIARY LIBRARY ACCOUNTS - FILE PROCESSOR FEATURE PATCH
The standard system library for RSTS/E systems is account [1,2J. This account
is normally referenced by the $ character in file specifications. The special
characters!, %, and & can also be used to refer tothree auxiliary libraries.
The default assignments for these characters are [1,3J, [1,4J, and [1,5J,
respectively. Although the association of character with account is defined,
the three accounts must be created with REACT before the special characters
can be used successfully.
In some installations, the system manager may want to change the account
numbers referenced by the three special characters. The account numbers are
defined by four words in the RSTS/E monitor. The default account numbers are
altered with a simple patch as described below.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

It may be installed

Decide which account numbers you wish to use for the auxiliary library
characters.
You may change any or all of the default assignments
(although changing the assignment of the $ library character is strongly
discouraged).
To specify a new project-programmer number of [p,pnJ, type
a new value at the appropriate offset. The new value has the form:
p.*256.+pn.
where p is the new project number (followed by a decimal point to ensure
that it is interpreted as a decimal number), the multiplication shifts the
project to the high byte (again, do not omit the decimal point after the
256), and pn is the new programmer number (followed by a decimal pOint).
p and pn must be between 0 and 254, and p may not be zero.

The patch described in Step 5 below
option of INIT.SYS:
Option: PATCH
File to patch? <If>

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executi ve
File Processor Patches
4.

Seq 3.5.1 F
2 of 2

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

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed.
5.

In this example, the! account is patched to [100,250J. the % account is
left unchanged, and the & account is changed to [1,99J. You should type
in appropriate values for your system. The patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????
Offset address? ~z
Base address? .. PPN.
Offset address? 0
Base
Offset Old
?????? 000000 000402
?????? 000002 000403
?????? 000004 000404
?????? 000006 000405
?????? 000010 ??????

New?
? Q! 1
? ""z

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

New?
(No change to $)
? <l f>
? 100.*256.+250.
(New value for !)
(No change to %)
? <If>
? 1.*256.+99.
(New value for &)
(up-arrow/C to exit;CTRL/C for INrT)
? ,...c

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.5.2 F

RSTS/E V7.2
Executive
File Processor Patches

1 of 2

CHANGING DEFAULT PROTECTION CODE - FILE PROCESSOR FEATURE PATCH
When a user creates a file without specifying a protection code for that file,
and if the personal default protection code is not set, the RSTS/E monitor
creates that file with the system default protection code. This is normally
60., which allows the user read/write access to the file, but restricts all
non-privileged users from any access. The legal value range for the default
protection code is 0. to 63. inclusive. The following procedure allows you to
patch the RSTS/E monitor to change your system's default protection code.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

The patch described below can be
INIT.SYS:
Option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

Note that if you answered 'No' to the 'Resident file OPEN/CLOSE' question
during system generation this patch will take effect immediately when
applied to the installed monitor SIL.
RUN $ONLPAT
Command File Name? <cr>
File to patch? <If>
File found in account [0,1J

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches
4.

2 of 2

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

Seq 3.5.2 F

New?
? Q!2
? AC

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT, you will return to the "Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.

Proceed as follows (be sure you include the decimal point
value so that it is interpreted as a decimal number):
File to patch? <If>
Module name? OVR
Base address? .. DPRT
Offset address? 0
Base
Offset Old
?????? 000000
074
?????? 000001
364

after

the

new

(LINE FEED for installed monitor SIL)

New?
? n.
? AC

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

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.5.3 F

RSTS/E V7.2
Executive
File Processor Patches

1 of 2

RESTRICTING DISK MODES - FILE PROCESSOR FEATURE PATCH
The RSTS/E monitor normally allows any user to OPEN a disk file using any mode
except 4096. (the read regardless mode) or 256. (data caching), and requires
that a user have privileges to open a disk file with MODE 4096. or 256.
You may wish to allow non-privileged users to use mode 4096. or 256. or to
restrict one or more of the other disk modes (see the RSTS/E Programming
Manual for a complete list). The following procedure allows you to patch the
RSTS/E monitor to specify which disk file OPEN modes require privileges.
Privileged users and non-privileged users running privileged programs would
still have full access to all available modes. If a non-privileged user
specifies a restricted mode, the mode value will be ignored but no error
message will be printed.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

Decide which disk file modes you wish to make privileged.
Consult the
RSTS/E Programming Manual for the various modes which are available, and
determine the associated MODE values. Compute the sum, n, of the MODE
values corresponding to the modes you wish to restrict. If you wish to
restrict special update mode, but leave normal update mode unrestricted,
use a value of 4 (not 5). If you wish to restrict both update modes, use
4+1. You may type the addition directly to the new value question of
PATCH. Be sure to include a decimal point after each number so that it is
interpreted as decimal.

The patch described below can be
INIT.SYS:
Option: PATCH
File to patch? <If)

installed

using

the

It may be installed

PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

Note that if you answered 'No' to the 'Resident file OPEN/CLOSE' question
during system generation this patch will take effect immediately when
applied to the installed monitor SIL.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.3 F
2 of 2

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

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

New?
? Q!4
? "c

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 3 above.

point.

You

If you are using ONLPAT, you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 4 above.
Proceed as follows:
File to patch? <If>
Module name? OVR
Base address? .. DKNP
Offset address? 0
Base
Offset Old
?????? 000000 010400
?????? 000002 010037

(LINE FEED for installed monitor SIL)

New?
? n.
? "c

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.4 F
1 of 2

MAKING FIP SYS CALLS PRIVILEGED - FILE PROCESSOR FEATURE PATCH
The following FIP SYS calls are normally non-privileged:
-25.
-17.
+10.
+13.
+14.
+15.
+17.

File Attribute Read/Write
Change File's run-time system Name
Assign a Device
Zero a Device or Account
Read Accounting Data
Indexed Directory Lookup
Wildcard Directory Lookup

It is possible to make one or more of these SYS calls privileged. Doing so
will restrict the use of that SYS call to only privileged users and/or
privileged programs.
CAUTION
The standard CUSP programs assume that the above SYS calls are
non-privileged; unexpected results may occur using the CUSPs
if one or more of the above are made privileged.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

Decide which SYS call code you wish to make privileged.
Be sure to
include a decimal point after the SYS call code to ensure that it is
interpreted in decimal.

The patch described in Step 5 below
option of INIT.SYS:
Option: PATCH
File to patch? <If>

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? <l f>
File found in account [0,lJ

It may be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Executive
File Processor Patches

Seq 3.5.4 F
2 of 2

The patch is also contained in a patch file appearing in patch kit version

"A" or later.
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? RSTS
Base address? $$0305
Offset address? 0
Offset Old
New?
Base
?????? 000000 ?????? ? Q! 10
?????? 000002 ?????? ? ~Z
Offset address? ~Z
Base address? $UUOTB
Offset address? n.-UU$MIN*2
Offset Old
New?
Base
?????? ?????? ?????? ? Q!1
?????? ?????? ?????? ? ~C

(CTRL/Z for new offset)
(CTRLlZ for new base)
(from step 2)
(up-arrow/C to exit;CTRL/C for INIT)

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.5.5 F

RSTS/E V7.2
Executive
File Processor Patches

1 of 2

RESTRICTING NON-PRIVILEGED ACCESS TO NON-FILE STRUCTURED DISKS
- FILE PROCESSOR FEATURE PATCH
Normally, a non-privileged user is given read and write access to a non-file
structured disk if it was that user's open request which mounted the disk as
non-file
structured.
Certain
installations
may
wish
to
prohibit
non-privileged users from ever getting any access to a non-file structured
disk.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

The patch described below can be
INIT .SYS:
Option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches
4.

2 of 2

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

Seq 3.5.5 F

New?
? Q!20
? .... C

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT, you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? (If)
Module name? OVR
Base address? .. NFSP
Offset address? 0
Offset Old
Base
?????? 000000 001414
?????? 000002 101020

(LINE FEED for installed monitor SIL)

New?
? 1423
? .... C

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.6 F
1 of 2

NON-PRIVILEGED WRITES TO NON-FILE STRUCTURED DISKS
- FILE PROCESSOR FEATURE PATCH
Normally, a non-privileged user is given write access to a non-file structured
disk if it was that user's open request which mounted the disk as non-file
structured. Certain installations may wish to prohibit non-privileged users
from ever obtaining write access to a non-file structured disk.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

The patch described below can be
INIT.SYS:
option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Executive
File Processor Patches

2 of 2

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

Seq 3.5.6 F

New?
? Q!40
? AC

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT. you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? <If)
Module name? OVR
Base address? .• NFSW
Offset address? 0
Base
Offset Old
?????? 000000 001000
?????? 000002 005016

(LINE FEED for installed monitor SIL)

New?
? 1001
? AC

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

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.5.7 F

RSTS/E V7.2
Executi ve
File Processor Patches

1 of 2

ALLOWING CROSS ACCOUNT CREATIONS - FILE PROCESSOR FEATURE PATCH
Normally. a non-privileged job cannot create files in any account other than
its own. Some installations may wish to allow a non-privileged job to create
files in any account within its project number (i.e .• create files in any
[x,*J account if the job's account is [x,y]).
This feature patch changes the File Processor's cross account check to allow
any job to create files within its project. A non-privileged job still cannot
create files in accounts outside of its project number group,
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

The patch described below can be
INIT. SYS:
Option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

2 of 2

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

Seq 3.5.7 F

New?
? Q! 100
?

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT, you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? <If>
Mod ule name? OVR
Base address? .. XGRP
Offset address? 0
Base
Offset Old
?????? 000000 001334
?????? 000002 124237

(LINE FEED for installed monitor SIL)

New?
? 240
? "c

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.8 F
1 of 2

ALLOWING CROSS ACCOUNT RENAME OPERATIONS - FILE PROCESSOR FEATURE PATCH
Normally. a non-privileged job cannot rename files in any account other than
its own. Some installations may wish to allow a non-privileged job to rename
files in any account within its project number (i.e .• rename files in any
[x.*J account if the job's account is [x,y]).
This feature patch changes the File Processor's cross account check to allow
any job to rename files within its project. A non-privileged job still cannot
rename files in accounts outside of its project number group.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

The patch described below can be
INIT.SYS:
Option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

Note that if you answered 'No' to the 'Resident file DELETE/RENAME'
question during system generation this patch will take effect immediately
when applied to the installed monitor SIL.
RUN $ONLPAT
Command File Name? <cr>
File to patch? <If>
File found in account [0,lJ

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version

"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.5.8 F

RSTS/E V7.2
Executive
File Processor Patches
4.

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

2 of 2

New?
? Q!200
?

"'c

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT, you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? <If>
Module name? OVR
Base address? .. XGRR
Offset address? 0
Base
Offset Old
?????? 000000 001360
?????? 000002 126037

(LINE FEED for installed monitor SIL)

New?
? 240
? "'c

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.9 F
1 of 2

EXTENDING DIRECTORY LOOKUP - FILE PROCESSOR FEATURE PATCH
Normally, the FIP calls 15 (Directory look up on Index) and 17 (Directory look
up by File Name/Wildcard directory look up) will not allow a non-privileged
user to find information about any file on the system to which he or she does
not have read or run access. Some installations, where security is not an
issue, may find it desirable to allow non-privileged users to look up files to
which
they do not normally have access.
If this patch is applied,
non-privileged use of FIP calls 15 and 17 will return information about all
files.
Since PIP.SAV (for the /L command) and BASIC-PLUS (for the CATALOG
command) use these calls, these commands would
be
unrestricted
for
non-privileged users.
The DIRECT program does not use these calls; another
feature patch, Seq 10.3.1 F, may be used to extend its use.
NOTE
For consistency, Digital recommends that you either use
patches (Seq 3.5.9 F and Seq 10.3.1 F) or neither of them.

both

PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SILs.

The patch described below can be
INIT.SYS:
Option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

Note that if you answered 'No' to the 'Resident directory lookup' question
during system generation this patch will take effect immediately when
applied to the installed monitor SIL.
RUN $ONLPAT
Command File Name? <cr>
File to patch? <If>
File found in account [0,1J

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Executive
File Processor Patches

2 of 2

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 1
Base
Offset Old
?????? 000001
???
?????? 000002
???

Seq 3.5.9 F

New?
? Q! 1
? "c

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT. you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? <If>
Module name? OVR
Base address? .. DIRP
Offset address? 0
Base
Offset Old
?????? 000000 001415
?????? 000002 021037

(LINE FEED for installed monitor SIL)

New?
? 415

? C

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.10 F
1 of 4

RESTRICTING NON-PRIVILEGED USE OF UU.TRM - FILE PROCESSOR FEATURE PATCH
The UU.TRM directive allows a user to set various characteristics of a
terminal.
Some installations may wish to restrict a non-privileged user's
ability to set terminal characteristics.
Protection checking in UU.TRM is done with two 2-word bit masks. Each of the
40(8) bits in a mask corresponds to a FIRQB byte offset. If the bit is on,
the corresponding byte in the FIRQB must be zero for all non~privileged
callers.
If the corresponding byte in the FIRQB is not zero, a n?Protection
violation" error is returned.
The two-word mask at patch locations .. TRN 1 and .. TRM2 is checked when a
user specifies the job's console keyboard in the call. The
two-word mask at locations .. TRM3 and .. TRM4 is checked when a non-privileged
user specifies any other keyboard that the job owns .
non~privileged

.. TRMl AND .. TRM3 are masks for bytes 0-17(8) of the FIRQB, and .. TRM2 AND
.. TRM4 are the masks for bytes 20-37(8). For example, if the value 1 is ORed
into location .. TRM2. a non-privileged user could not change parity (byte 20)
at the job's console.
If none of these words are patched, the system is setup so that a
non-privileged user may change anything on the job's console, except speeds
and ring characteristics, and may change nothing on other terminals that job
owns (but the characteristics may still be read).
Note that by OR'ing value 10(8) into .. TRM3. the user is "not allowed" to
specify FQFUN (which must be 16. to invoke UU. TRM) , so a II ?Protection
violation ll error is returned without divulging the characteristics of any
non-console keyboard owned by the job.
The following is a table relating FIRQB byte number with its
mask word and value to "OR" to force the parameter to be zero.

corresponding

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

FIRQB
BYTE

MASK
WORD
Console

Non-console

1/21
2/22

•• TRMl/2
•• TRMl/2
• • TRMl/2

3/23

· . TRMl/2

· . TRM3/ 4
· . TRM3/ 4
· . TRM3/ 4
· . TRM3/ 4
· . TRM3/ 4
· . TRM3/ 4
· . TRM3I4
· .TRM3/4
· . TRM3I4
· . TRM3/4

0/20

4/24

• .TRMl/2

5/25
6/26

· . TRM1 /2
· . TRM1/2
· . TRMl /2
· . TRM 1/2

7/27

10/30
11131

12/32
13/33
14/34
15/35
16/36
17137

• • TRMl/2
•• TRMl/2

· . TRM1 /2
• • TRMl/2
• • TRMl/2

· . TRMl/2
•• TRMl/2

• • TRM3/4
• • TRM3/4

· . TRM3I4
· . TRM3/ 4
· . TRM3I4
· . TRM3/4

Seq 3.5. H'l F
2 of 4

OCTAL
VALUE

DECIMAL
VALUE

2
4

10
20
40
10

200
400
1000
2000
4000
10000
20000
40000
100000

4.
8.
16.
32.
64.
128.
256.
512.
1024.
2048.
4096.
8192.
16384.
32768.

Compute a value for .. TRMl by taking the values from the table above
corresponding to the bytes you wish to disable and adding them to give a value
II a"
which you will use in the patch.
Similarly compute a value for .. TRM2 and call this value "b" .
Similarly compute a value for .. TRM3 and call this value "c" .
Similarly compute a value for .. TRM4 and call this value II d II •
Apply these values in step 5 below.
NOTE
To allow non-privileged users to change terminal speeds on their
console, as was the case in V7.0, "a" should equal 0 and "b"
should equal 100.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

It may be installed

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches
2.

Seq 3.5. Hl F

3 of 4

The patch described below can be
INIT.SYS:
opt ion: PATCH
File to patch? <If>

installed

using

the

PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT, the on-line patching
program.
Note that this patch will take effect immediately when applied
to the installed monitor SIL.
RUN $ONLPAT
Command File Name? <cr>
File to patch? <If>
File found in account [0,1]

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

This patch is contained in a patch file appearing in patch kit version II A"
or later.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed.
4.

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 1
Base
Offset Old
?????? 000001
???
?????? 000002
???

New?
? Q!2
? "c

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.10 F
4 of 4

If you are using INIT, you will return to "Option: " at this

point.

You

must again select the PATCH option as in step 2 above.
If you are using ONLPAT, you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? <If>
Module name? OVR
Base address? .. TRM1
Offset address? 0
Base
Offset Old
?????? 000000 100000
?????? 000002 012702
Offset address? AZ
Base address? .. TRM2
Offset address? 0
Offset Old
Base
?????? 000000 000102
?????? 000002 005705
Offset address? AZ
Base address? .. TRM3
Offset address? 0
Offset Old
Base
?????? 000000 177700
?????? 000002 012702
Offset address? Z
Base address? .. TRM4
Offset address? 0
Offset Old
Base
?????? 000000 177777
?????? 000002 005200

(LINE FEED for installed monitor SIL)

New?
? a
? AZ

;Value from above
(CTRL/Z for new offset)
(CTRL/Z for new base)

New?
? b
? AZ

;Value from above
(CTRL/Z for new offset)
(CTRL/Z for new base)

New?
? c
? AZ

;Value from above
(CTRL/Z for new offset)
(CTRL/Z for new base)

New?
? d
? AC

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.11 F
1 of 2

ALLOWING USERS WITH TEMPORARY PRIVILEGES TO SET PRIVILEGED PROTECTION CODES
- FILE PROCESSOR FEATURE PATCH
The patch described below will allow a program using the FIP RENAME SYS call
(or BASIC-PLUS "NAME AS" command) with temporary privileges to set the 128 bit
in the protection code.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

The patch described below can be
INIT.SYS:
Option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

This patch can be installed manually using ONLPAT,
program.

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.5.11 F

RSTS/E V7.2
Executive
File Processor Patches
4.

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 1
Offset Old
Base
?????? 000001
???
?????? 000002
???

2 of 2

New?
? Q!4
? ... c

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT, you will return to the" Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? <If)
Module name? OVR
Base address? DLN0
Offset address? 612
Base
Offset Old
?????? 000612 001402
?????? 000614 042700
?????? 000616 000200
?????? 000620 105737

(LINE FEED for installed monitor SIL)

New?
? <LF>
? 240
? 240
? .. c

(no change; verify only)
(up-arrow/C to exit;CTRL/C for IN I!)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches

Seq 3.5.12 F
1 of

MAKING REASSIGN A PRIVILEGED FUNCTION - FILE PROCESSOR FEATURE PATCH

RSTS/E currently allows non-privileged users to reassign a device to another
user.
On some systems, it may be desirable to restrict the reassign function
to privileged users.
The patching procedure
privileged users.

detailed

below

restricts

device

reassignment

PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive.
in any target monitor SIL.

The patch described below can be
INIT.SYS:
Option: PATCH
File to patch? <If>

installed

using

the

It may be installed
PATCH

option

(LINE FEED for installed monitor SIL)

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
File Processor Patches
4.

2 of 2

The first part of the patch is as follows:
Module name? RSTS
Base address? $$0305
Offset address? 1
Base
Offset Old
?????? 000001
???
?????? 000002
???

Seq 3.5.12 F

New?
? Q! 10
? "c

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

If you are using INIT, you will return to "Option: " at this
must again select the PATCH option as in step 2 above.

point.

You

If you are using ONLPAT, you will return to the "Command File Name?"
question. Type RETURN for manual patch installation as in step 3 above.
Proceed as follows:
File to patch? <If)
Module name? OVR
Base address? ASS0
Offset address? 46
Base
Offset Old
?????? 000046 032711
?????? 000050 000400

(LINE FEED for installed monitor SIL)

New?
? 402
?

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches

Seq 3.7.1 F
1 of 4

SPECIAL LINE PRINTER DRUMS - DEVICE DRIVER FEATURE PATCH
Most DEC LPll line printer drums contain a character which corresponds to
octal code 040 (the ASCII SPACE character). This character may be a blank,
the British Pound Sterling character, or some other optional non-standard
character.
Normally, this character is irrelevant, since the LPll is usually
wired to print only ASCII codes 041 through 137 (octal) for the 64-character
set, or 041 through 176 for the 96-character set. The SPACE character (040),
"non-printing" characters (codes 000 to 011, 013, and 016 to 037), and
character codes greater than 137 (on printers with the 64-character set) all
print as spaces. The space is created by suppressing printer action, rather
than actually having a hammer strike a character position on the printer drum.
By making a simple wiring change to the LP11, the range of printing characters
can be extended to include ASCII code 040. If the printer drum contains a
special character in the 040 position, sending an 040 code to the printer will
cause that special character to be printed.
In conjunction with this change, you can patch the RSTS/E line printer driver
to allow special handling of ASCII 040 on a unit-by-unit basis. Normally, the
driver sends 040 codes (SPACEs) unchanged to the printer.
If the w1r1ng
change is not installed in the printer, this character will appear as a space,
regardless of the symbol on the line printer drum. The patch allows you to
specify an ASCII code which the driver will translate to 040 before sending it
to the printer. The special character will thus be printed. In addition, the
driver will translate all 040 codes to 037, which is a non-printing character
and appears as a space. Note that translation of 040 is performed only if the
special character translation is enabled.
Ideally, you should choose a character which is not commonly used for other
purposes but which can be typed and printed on any standard terminal. This
allows you to use any standard editor to insert the special character into
text destined for the printer. Remember that the conversion in the printer
driver overrides the standard symbol (if any) for the selected code.
For
_example, if you select the code 101 (the letter A), the special character is
printed in place of any A sent to the driver.
It would therefore be
impossible to print an A.
All normal printing characters have some meaning in RSTS/E or BASIC-PLUS. For
example, the "&" character ends a comment field in the EXTEND mode of
BASIC-PLUS, is an abbreviation for account [1,5J, and is a special character
in RUNOFF source files. The "@" character is seldom used in printed material,
but RSTS/E uses it as an assignable account designator.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches

Seq 3.7.1 F
2 of 4

If none of the printable characters is suitable, one of the ASCII control
characters (codes 001 to 037) may be used. For example, CTRL/F (006) can be
generated with most terminals and will echo and print as ~F, if UP ARROW mode
is selected with TTYSET. It has no meaning to any standard DEC terminal.
As system manager, you must choose the character which is appropriate for your
installation by studying the ASCII code table and considering your users'
needs. The procedure for installing the patch is described below.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive. It may be installed
in any target monitor SIL that includes line printer support.

Decide which line printer unit should have special character handling. If
more than one unit is to be patched, repeat the steps below for each unit
you wish to modify.

Select the character to represent the special printer symbol.
If this
character is a printable character (e.g., &), specify the new value in the
patch by simply typing

'&
and replacing the & with the character you have chosen. If the character
is a control character, specify its ASCII code as an octal number (or
decimal number followed by a decimal pOint), or as 'x-100 to represent
CTRL/x. For example, CTRL/N may be specified as
16
or as
14.

or as
'N-100
in the pa tch .

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Executive
Device Driver Patches

.4.

3 of 4

The patch described in Step 6 below
option of INIT.SYS:
option: PATCH
File to patch? <If>

Seq 3.7.1 F

can

installed

the

PATCH

(LINE FEED for installed monitor SIL)

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

using

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
IIAn or later.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed.
6.

In this example, the symbol n is used to denote the line printer unit
being modified. You should type the actual unit number (between zero and
the number of printers -1). The patch is as follows:
Module name? RSTS
Base address? LPDDDB
(n is the unit number)
Offset address? DDS.LP*n+30
Offset Old
New?
Base
?????? ?????? 000000 ? (new value from step 3)
?????? ?????? 000000 ? ~Z
(CTRL/Z for new offset)
Offset address? Z
(CTRL/Z for new base)
Base address? $$0307
Offset address? 0
New?
Base
Offset Old
?????? 000000 ?????? ? Q! 1
?????? 000002 ?????? ? AC
(up-arrow/C to exit;CTRL/C for INIT)
A

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches
7.

Seq 3.7.1 F

4 of 4

Install the hardware modification to the printer.
The modification
different for the several printer models, as listed below:

LP131 (23113)

Wiring change required to card cage backplane. Remove wire
A3A4-36 and connect this wire through a 1K pullup resistor
to +5 Volts.

LP132 (2410)

Change to AR16 Data Register Card. Remove card from slot
A3A24. Lift Pin 5 on Z15 and tie Pin 5 to ground.

LP134 (24713)

Wiring change required to card cage backplane. Remove wire
from A3A24-134 and connect this wire through a 1K pullup
resistor to +5 Volts.

LP05 (2230)

Insert jumper W1 on the Logic Control Board 29-21112.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 3.7.2 F

RSTS/E V7. 2
Executive
Device Driver Patches

1 of 2

CHANGING DEFAULT PRINTER FORM LENGTH - DEVICE DRIVER FEATURE PATCH
When a line printer is OPENed, the default, hardware, form length is set to
66. This is the actual form length for most applications. You can change the
default form length by installing the patch given below.
The legal form
length values are between 7. and 127. inclusive. Note that this patch changes
the default form length for ALL line printers on the system.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive. It may be installed
in any target monitor SIL which includes line printer support.

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

can

installed

the

PATCH

(LINE FEED for installed monitor SIL)

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

using

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches
4.

2 of 2

Be sure you include the decimal point after the new value so
interpreted as a decimal number.
The patch is as follows:
Module name? RSTS
Base address? .. LP66
Offset address? 0
Offset Old
Base
?????? 000000 000102
?????? 000002 112712
Offset address? "z
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

Seq 3.7.2 F

New?
? n.
? "z

New?
? Q!2
? "'c

that

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

(up-arrow/ C to ex it; CTRLlC for INIT)

If you are using the line printer spooling package, you must change the
control file (or files) which start the spoolers. Include the /DFLENGTH:n
switch in the command line for each spooler to specify the new default
form length.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches

Seq 3.7.3 F
1 of 2

ALLOW SPECIAL CONTROL CHARACTERS - DEVICE DRIVER FEATURE PATCH
All line printers supported by RSTS/E software use only 7-bit characters; the
sign bit of the character is always 0. In fact, the line printer driver
interprets characters with the sign bit "on" (ASCII values greater than 127.
decimal) as forms control characters if the special OPEN MODE 512%+n% is used.
(See the RSTS/E Programming Manual.) The line printer driver also uses
character values greater than 127. internally for space compression purposes
and to suppress trailing blanks.
Some RSTS/E installations have special line printers that require the use of
control characters with values greater than 127, even though the use of such
equipment is not supported. The feature patch descibed below will allow full
8-bit characters to be passed unmodified to the line printer.
CAUTION
The patch described below produces some side effects which must
be recognized before installation. First, if your line printer
cannot interpret 8-bit characters (all supported printers fall
into this category), do not install this patch or unpredictable
results may occur.
Second, this patch prevents the use of
software formatting (MODE 512%) and prevents internal space
compression, i.e., trailing blanks will be printed. Third, this
patch affects every line printer on your system.
The patch also has some effect on the spooling package.
Incorrect page counts will probably result if the RESTART or
REQUE options are used. In addition, unless the line printer
spooler start-up option ILPFORM:NO is used, a user specifying
LPFORM will probably crash the spooling package.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive. It may be installed
in any target monitor SIL that includes line printer support.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? <If)

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches
3.

Seq 3.7.3 F
2 of 2

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

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.
4.

The patch is as follows:
Module name? RSTS
Base address? .. LPSP
Offset address? 0
Base
Offset Old
?????? 000000 000000
?????? 000002 005061
Offset address? ~Z
Base address? $$0307
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 ??????

New?
? 002000
?

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

New?
? Q!4
? ~C

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches

Seq 3.7.4 F
1 of 2

TU16/TE16/TU45/TU77 MAGNETIC TAPE DENSITY/PARITY DEFAULT
- DEVICE DRIVER FEATURE PATCH
The default density and parity settings for TU16, TE16, TU45, or TU77 magnetic
tape (device MM) under RSTS/E V7.2 are 800 BPI and ODD parity. A program can
change the density and/or parity value for either file structured or non-file
structured operations by using the MAGTAPE function.
You can change your system's default settings for density and/or parity by
installing
the patch given below.
This is useful if you frequently
interchange tapes with other systems which use 1600-BPI
phase-encoded
defaults. It is also useful if you want to use the 1600-BPI recording mode as
your installation's standard.
NOTE
The 600-foot RSTS/E V7.2 distribution magnetic tapes for TU16,
TE16, TU45, and TU77 (including optional languages such as COBOL
and FORTRAN) are written at 800 BPI with ODD parity. If you use
this kind of distribution kit, do not install this patch until
after you have completed the system library build procedures,
including any optional software.
PROCEDURE:
1.

This is a feature patch to the RSTS/E V7.2 executive. It may be installed
in any target monitor SIL which is configured for TU16, TE16, TU45, or
TU77 magnetic tape.

Select the desired magnetic tape density and parity.
To use 1600 BPI
phase encoded mode, specify a new value of 0 in the patch. To return to
800 BPI and ODD parity, specify a new value of 140. Any other value will
cause file structured operations to fail.

The patch described in Step 5 below
option of INIT.SYS:
Option: PATCH
File to patch? <If>

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches
4.

Seq 3.7.4 F
2 of 2

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? <If>
File found in account [0.1J

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is as follows:
Module name? RSTS
Base address? .. MTDP
Offset address? 1
Base
Offset Old
?????? 000001
140
?????? 000002
???
Offset address? ~Z
Base address? $$0307
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 ??????

New?
? n
? ~Z

New?
? Q! 10
? AC

( from step 2)
(CTRLI Z for new offset)
(CTRL/Z for new base)

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches

Seq 3.7.5 F
1 of 2

USING THE CSS PAPER TAPE READER ON RSTS/E V7.2 - DEVICE DRIVER FEATURE PATCH
PROBLEM:
The paper tape reader device driver included in the RSTS/E V7.2 object library
does not work with the CSS paper tape reader (PA611).
SOLUTION:
The paper tape reader driver for RSTS/E V7.2 is for Digital Equipment
Corporation model PCll. The following optional patch will make the driver
compatible with the CSS paper tape reader model PA611.
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 V7.2 executive.
in any target monitor SILs.

The patch described in Step 4 below
option of INII.SYS:
Option: PATCH
File to patch? Of>

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

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

It may be installed

the

on-line

patching

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Executi ve
Device Driver Patches
4.

Seq 3.7.5 F
2 of 2

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

New?
? 100100
? ~Z

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

New?
? Q!20
? ~C

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

RSTS/E Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches

Seq 3.7.6 M
1 of 3

TS11 REWIND PROBLEMS - MANDATORY DEVICE DRIVER PATCH
PROBLEM:
Timing conditions associated with the rewind operation of the TS11 mag tape
drive can cause the RSTS/E TS11 driver to indicate that the TS11 is
unavailable, hung, or write-locked.
Under some conditions it is possible for a new request to be issued to the
TS11 unit before it has completed a rewind.
This extra request is not
acknowledged by the TS11 controller, as the controller is busy with the
rewind.
The RSTS/E driver expects a response from the controller within a
reasonable time following a request; long rewinds may exceed this time limit,
causing the driver to indicate that the device is unavailable to the user.
SOLUTION:
The patching procedure detailed below corrects the above problem.
PROCEDURE:
1.

This is a required patch to the RSTS/E V7.2 executive.
It must be
installed in all target monitor SILs configured with the TS11 magnetic
tape driver (MSDVR). Note that the patch will fail on systems not
configured for TS11 magnetic tape controllers.

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

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

RSTS/E Maintenance Notebook, June 1982

Seq 3.7.6 M

RSTS/E V7.2
Executive
Device Driver Patches

2 of 3

The patch is also contained in a command file ($MONITR.CMD)
patch kit version "A" or later.
4.

The patch is as follows:
Module name? RSTS
Base address? QUEL3Q
Offset address? W
Offset Old
Base
?????? 0000W 012100
?????? 000012 001403
?????? 000014 004567
Offset address? AZ
Base address? MSDVR
Offset address? 3734
Offset Old
Base
?????? 003734 004737
?????? 003736 ??????
?????? 003740 005064
Offset address? 0
Offset Old
Base
?????? 000000 000000
?????? 000002 000000
?????? 000004 000000
?????? 000006 00000Cf
?????? 00001Cf 000CfCfCf
?????? Cf00012 000000
?????? 0Cf0Cf14 00CfCf0Cf
?????? 000016 000000
?????? 0CfCf020 00Cf0Cf0
?????? 0CfCf022 0000Cf0
?????? CfCf0024 00Cf00Cf
?????? 0CfCf026 0000CfCf
?????? CfCfCf03Cf CfCf00CfCf
?????? 0CfCf032 CfCf0Cf0Cf
?????? 0CfCfCf34 0Cf000Cf
?????? 000036 0CfCf00Cf
?????? 0Cf004Cf Cf0CfCf00
?????? CfCfCf042 000Cf0Cf
?????? CfCf0044 00000Cf
?????? 00Cf046 0Cf00CfCf
?????? CfCfCfCf5Cf CfCfCf0CfCf
?????? Cf00052 Cf00Cf00
?????? 0Cf0054 Cf0Cf000
?????? 000056 000000
?????? 00Cf060 000Cf00

New?
? 137
? MSDVR
? AZ

New?
? 137
? MSDVR+72
? AZ
New?
? 13746
? 177776
? 12737
? 34240
? 177776
? 26127
? 2
? QMSCON
? 1410
? 12637
? 177776
? 12100
? 1-402
? 137
? QUEL3Q+14
? 137
? QUEL3Q+22
? 32764
? 30CfCf0
? 66
? 1764
? 52764
? 2
? 66
? 12637

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

(CTRL/Z for new offset)

appearing

RSTS/E Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
Device Driver Patches
????17 eJeJeJ062 c;mc;meJeJ
???17? 0eJ0eJ64 000000
171717 000066 0eJ000eJ
?1717? 000070 000000
1717?? 00eJ072 000000
??1717 0eJ0074 eJ00000
?17??? 00eJ076 000000
?17?17 000100 eJ00000
171717 000102 000000
?17?17 0eJ0HJ4 ?1717?
Offset address? Z
Base address? $$eJ307
Offset address? 0
Offset Old
Base
?????? 000eJ00 ??????
?????? 000002 ??????

Seq 3.7.6 M

3 of 3
? 177776
? 12601
? 12600
? 207
? 5064
? 66
? 4737
? QUEL3Q
? 20'7
? Z
A

New?
? Q!40
? AC

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

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

RSTS/E Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
FMS Monitor Patches

Seq 3.9.1 M
1 of 3

FMSTIO PATCH - MANDATORY FMS MONITOR PATCH
PROBLEM:
This patch to the RSTS/E V7.2 monitor code is required to correct a problem
that may cause the system to crash when inputting an FMS mixed picture field.
Failure to install this patch may result in a crash of the system when
running FMS applications.
NOTE
This patch is for RSTS/E V7.2 ONLY. It is
NOT to be applied to RSTS/E V7.1. Also,
the patch described in the "FMS-11/RSTS
Installation Guide and Release Notes" is
to be applied to RSTS/E V7.1 ONLY.
That
patch is NOT to be applied to RSTS/E V7.2.

SOLUTION:
The patching procedure detailed below corrects the above problem.
PROCEDURE:
1.

This is a required patch to the RSTS/E V7.2 executive.
It must be
installed in all target monitor SILs which include FMS-11 support in the
monitor. This code is included if you answer "Yes" to the "FMS-11
support" question during system generation. If the FMS-11 code was not
included in the monitor during your system generation, the patch will fail
with a "Module not found in SIL" error after you specify FMS as the Module
name.

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

can

installed

using

the

PATCH

(LINE FEED for installed monitor SIL)

RSTS/E Maintenance Notebook, June 1982

RSTS/E V7.2
Executive
FMS Monitor Patches
3.

Seq 3.9.1 M
2 of 3

(RETURN for manual patch installation)
(LINE FEED for installed monitor SIL)

The patch is also contained in a command file ($MONITR.CMD)
patch kit version "A" or later.
4.

The patch is as follows:
Module name? FMS
Base address? $FMSSE
Offset address? 456
Offset Old
Base
?????? qqq456 1124132
?????? qqq4613 13134767
?????? 131313462 13136156
?????? 131313464 1133q133
?????? 131313466 q135265
?????? 13qq4713 1313131336
?????? 131313472 131313771
?????? 13q13474 13773113
?????? 131313476 13165132
Offset address? 6131313
Base
Offset Old
?????? 131361313q 11213132
?????? 1313613132 13134767
?????? 1313613134 131313634
?????? 1313613136 113313133
?????? 13q6q113 q135265
?????? 131361312 13qq1336
?????? 13q61314 131313771
?????? 131361316 137711q
?????? 13q6q213 1304767
Offset address? "z
Base address? FMSPAT
Offset address? 13
Offset Old
Base
?????? 000000 13130000
?????? 13q0002 13qq0qq

New?
? qq1313"(
? FMSPAT+313
? 1313132413
? 1313132413
? q131324 13
? 1313132413
? 1313132413
? 13q132413
(CTRL/Z for new offset)
? "z
New?
? 131313137
? FMSPAT+13
? 1313132413
? qq1324 13
? 13q132413
? 13q1324 13
? 13qq2413
? qq1324 13
(CTRL/Z for new offset)
? "z
(CTRL/Z for new base)
New?
? 1120132
? 0134737

appearing

RSTS/E Maintenance Notebook, June 1982

Seq 3.9.1 M

RSTS/E V7.2
Executive
FMS Monitor Patches
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????
??????

eJeJeJeJeJ4
eJeJeJeJeJ6
0eJeJ01eJ
00eJeJ12
0010014
0eJ0!016
131300210
!o!o(JeJ22
(JeJeJ024
00eJ026
0eJeJ030
000032
eJ(J(J034
!00eJeJ36
000040
000042
000044
000046
00eJ05eJ
000052
000054
000056
0eJ0!060

3 of 3

eJeJeJeJeJeJ
eJeJeJeJeJeJ
eJ0eJeJeJeJ
eJ0eJeJeJeJ
1010 10 10 !OeJ
13 eJeJ(J 00
10 10 !OeJ!O 0
!OeJ 13010 10
(J00eJ(JeJ
0eJeJeJ00
000eJ00
010 (JeJ 0eJ
0001300
eJ0!OeJ00
00010100
000000
00eJ000
00000eJ
0eJ0000
0(JeJ000
(J00eJ00
0013000
??????

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

$FMSSE+6642
leJ3eJeJ3
eJ05265
eJeJeJ!036
01010771
!OeJ57(Jl
0101401
077112
eJeJ0137
$FMSSE+602eJ
112402
(JeJ4737
$FMSSE+6642
103003
005265
000036
000771
005703
eJ01401
077312
000137
$FMSSE+476
(up-arrow/C to exit; CTRL/C for INIT)
? AC

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
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+0
· . PUCH+2
· . PUCH+4

Usage
Floating currency symbol
Decimal point character
Every three digits character

Defaul t

England

France

$ (044)

(046)
(056)
, (054)

F (106)

(056)
, (054)

, (054)
(056)

Substitution of different characters, such as those listed under England and
France above, 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 "FFtl.fllIll1l1l1l.tllI" , 3673298.02, 4545.20
F3.673.298.02
F4.545.20
Since any change in this area does render the PRINT-USING documentation
slightly incorrect, an appropriate note should be published for users of the
system.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
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 wish 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 below
option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

can

installed

the

PATCH

(BASIC-PLUS run-time system name)

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

using

the

on-line

patching

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

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

New?
? If
? I
? I
? ~C

(currency sign from step 2)
(decimal point from step 2)
("every three" from step 2)
(up-arrow/ C to exit; CTRLI C for INIT)

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.1.1 F

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches
6.

3 of 3

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 ADDed, or if it is your system default run-time system, execute the
following commands:
RUN $UTILTY<cr>
<UTILTY's header line>
HUNLOAD BASIC<cr>
HEXIT<cr>

(BASIC-PLUS run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run-time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
HLOAD BASIC/STAY/ADDR:nnn<cr>
HEXIT<cr>
Re~dy

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.1.2 F

RSTS/E V7. 2
BASIC-PLUS
BASIC-PLUS Patches

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 must be between 0 and 6 inclusive.

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

can

factor.
be

installed

default

using

the

SCALE
PATCH

(BASIC-PLUS run-time system name)

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

This

the

on-line

patching

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches
5.

2 of 2

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

Seq 4.1.2 F

New?
? n
? ~C

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

(BASIC-PLUS run-time system name)

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.1,3 F

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches

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

can

installed

using

the

PATCH

(BASIC-PLUS run-time system name)

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

the

on-line

patching

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

The patch is also contained in a patch file appearing in patch kit version
"An or later.
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 V7.2 Maintenance Notebook, June 1982

Seq 4.1.3 F

RSTS/E V7. 2
BASIC-PLUS
BASIC-PLUS Patches
5.

2 of 2

(BASIC-PLUS run-time system name)

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.1.4 F

RSTS/E V7. 2
BASIC-PLUS
BASIC-PLUS Patches

1 of

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

To change

this

default

NOTE
In future releases of RSTS/E, BASIC-PLUS will change its default
from NOEXTEND mode to EXTEND mode. Digital recommends that you
install this patch to prepare your users for the transition.
Note that when the default is changed, a Feature patch will be
provided to change the default back to NOEXTEND mode. Please
also note that the use of EXTEND mode will ease any transition
to other versions of BASIC-PLUS or BASIC-PLUS-2.

PROCEDURE:
1.

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

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? BASIC.HTS

can

system.

installed

using

may

the

PATCH

(BASIC-PLUS run-time system name)

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

the

on-line

patching

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

The patch is also contained in a patch file appearing in patch kit version
II Ail or later.
4.

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

New?
? 20000
?

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

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.1.4 F

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches
5.

2 of 2

(BASIC-PLUS run-time system name)

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
BASIC-PLUS
BASIC-PLUS Patches

Seq 4.1.5 F
1 of 2

NO IMMEDIATE MODE FROM .BAS FILE - BASIC-PLUS FEATURE PATCH
Normally, BASIC-PLUS allows immediate-mode commands to appear in the file
accessed
by
the "OLD" command.
This may be undesirable in hostile
environments where, for example, students could write programs which included
"UNSAVE" commands.
To prevent BASIC-PLUS from accepting immediate mode
commands in files, apply the patch in this article.
NOTE
In future releases of RSTS/E, BASIC-PLUS will change its default
to not allow immediate-mode commands to be executed from a
program file accessed by the "OLD" command. This will be done
to increase compatibility with other products. A Feature patch
will be provided to allow users to continue using this feature.
PROCEDURE:
1.

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

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch?BASIC.RTS

can

installed

using

may

the

PATCH

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0,1JBASIC.RTS
File found in account [0,1J

system.

the

on-line

patching

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

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.1.5 F

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches
4.

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

2 of 2

New?
? 1401
? AC

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

(BASIC-PLUS run-time system name)

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
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,PNJ 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
installed in any BASIC-PLUS run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

can

system.

installed

may

using

the

PATCH

(BASIC-PLUS run-time system name)

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

the

on-line

patching

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

The patch is also contained in a patch file appearing in patch kit version
Art or later.

The patch is as follows:
Base address? .. CAT.
Offset address? 0
Base
Offset Old
?????? 000000 000401
?????? 000002 000006

New?
? 5064
? "c

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

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.1.6 F

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches
5.

2 of 2

the above patch was installed using ONLPAT. i t will take effect the
next time the run-time system is reloaded. If the run-time system has
been ADDed, or if it is your system default run-time system, execute the
following commands:
If

RUN $UTILTY<cr>
<UTILTY's header line>
#UNLOAD BASIC<cr>
fIEXIT<cr>

(BASIC-PLUS run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run-time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
#LOAD BASIC/STAY/ADDR:nnn<cr>
IIEXIT<cr>
Ready

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches

Seq 4.1.7 F
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.
PROCEDURE:
1.

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

The patch described in Step 4 below
option of init.sys:
Option: PATCH
File to patch? BASIC.RTS

can

system.

installed

may

using

the

PATCH

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0.1JBASIC.RTS
File found in account [0,lJ

the

on-line

patching

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

The patch is also contained in a patch file appearing in patch kit version
nA" or later.
4.

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

New?
? UUOBAD
?

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches
5.

Seq 4.1.7 F
2 of 2

(BASIC-PLUS run-time system name)

system

had

(BASIC-PLUS run-time system name)

been

RSTSIE V7.2 Maintenance Notebook, June 1982

RSTSIE V7.2
BASIC-PLUS
BASIC-PLUS Patches

Seq 4.1.8 F
1

of 3

CLEAR lID BUFFERS USED BY OPEN STATEMENTS - BASIC-PLUS FEATURE PATCH
PROBLEM:
BASIC-PLUS does not clear 1/0 buffers used by OPEN statements.
SOLUTION:
The

patching

procedure detailed belolrl will cause BASIC-PLUS to clear
OPEN statements. This patch need only be applied
when high security is needed.
1/0 buffers used by

NOTE:

Applying this patch will cause BASIC-PLUS file commands (OLD,
SAVE, REPLACE) to execute more slowly.

PROCEDURE:
1.

This is a feature patch to the BASIC-PLUS Run-Time System.
be installed on any BASIC~PLUS Run-Time System.

The patch described in
PATCH option of INIT.SYS:

Step 4 below can be

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

This patch can be
patching program:

installed

It may

installed using the

(BASIC-PLUS Run-Time System name)
manually

using

ONLPAT, the on-line

RUN $ONLPAT
Command File Name? <cr>
(RETURN for manual patch installation)
File to patch? [0,1JBASIC.RTS
(BASIC-PLUS Run-Time System name)
File found in account [0,1J
The patch is also contained in a patch
version "A" or later.

file appearing in patch kit

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
BASIC-PLUS
BASIC-PLUS Patches
4.

2 of 3

The patch is as follows:
Base address? RC
Offset address? 6774
Base Offset Old
?????? 0'0'6774 0'05062
?????? 006776 000006
?????? 007000 016764
Offset address? "z
Base address? PA
Offset address? 102
Base Offset Old
?????? 000102 000000
?????? 000104 000000
?????? 000106 000000
?????? 000110 000000
?????? 000112 000000
?????? 000114 000000
?????? 000116 000000
?????? 0'00120' 000000
?????? 000122 000000
?????? 0'0'0124 00'000'0
?????? 000126 000000
?????? 0'00130' ??????

Seq 4. 1. 8 F

New?
? 4737
'I PA+102
A
? Z

New?
? 5062
? 6
? 10046
? 10246
? 66202
? 10
? 105022
? 77002
? 12602
? 12600
? 207
? AC

(CTRLlZ for new offset)
( CTRLIZ for neVI base)

(up-arrow/C to E;Xit;)
(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 ADDed, or if it is your system default
run-time system, execute the following commands:
RUN $UTILTY<cr)
<UTILTY's header line>
#UNLOAD BASIC<cr)
#EXIT<cr>
Ready

(BASIC-PLUS Run-Time System name)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches

Seq 4.1.8 F
3 of 3

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.
If, in addition to being previously ADDed, the run-time system
had been ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
#LOAD BASIC/STAY/ADDR:nnn<cr>
1tEXIT<cr>

(BASIC-PLUS Run-Time System name)

Ready

NOTE:

IF IT IS NECESSARY, THE PATCH SPACE THIS
RE-USED FOR MANDATORY PATCHES.

PATCH USES MAY BE

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.1.9 F

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches

1 of 2

FORCE "ILLEGAL STATEMENT" ERROR WHEN USING OBSOLETE SEND/RECEIVE BASIC-PLUS FEATURE PATCH
PROBLEM:
The BASIC-PLUS distributed with RSTS/E V7.1 is the last release of RSTS/E
which will support Send/Receive SYS call 18 (SYS(CHR$(6%)+CHR$(18%)+~ .. ).
SOLUTION:
The patching procedure detailed below will cause BASIC-PLUS to generate
an "?Illegal Statement" error whenever the obsolete Send/Receive SYS
call (SYS(CHR$(6%)+CHR$(18%)+ .... ) 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 1'1anual, Chapter 8 for information) .
NOTE:

IT IS SUGGESTED THAT YOU APPLY THE PATCH WHICH FOLLOWS TO A COpy
OF YOUR BASIC-PLUS RUN-TIME SYSTEM. YOU CAN THEN SWITCH TO THE
NEW RUN-TIME SYSTEM, OLD/COMPILE ALL USER WRITTEN PROGRAMS WHICH
YOU SUSPECT MAY USE SYS CALL 18, AND TRACK DOWN AND CHANGE THE
CALLS WITH LESS IMPACT ON YOUR SYSTEM.
THIS PATCH MUST NOT BE
APPLIED TO YOUR ACTUAL BASIC-PLUS RUN-TIME SYSTEM.

PROCEDURE:
1.

This is a feature patch to the BASIC-PLUS Run-Time System.
be installed on any BASIC-PLUS Run-Time System.

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

This patch can be
patching program:

installed

below can be

It may

installed using the

(BASIC-PLUS Run-Time System name)
manually

using

ONLPAT, the on-line

RUN $ONLPAT
Command File Name? <cr>
(RETURN for manual patch installation)
File to patch? [0,lJBASIC.RTS
(BASIC-PLUS Run-Time System name)
File found in account [0,lJ
The patch is also contained in a patch file
version "A" or later.

appearing in patch kit

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
BASIC-PLUS
BASIC-PLUS Patches

Seq 4.1.9 F
2 of 2

The patch is as follows:
Base address? SN
Offset address? 422
Base Offset Old
?????? 000422 111302
?????? 000424 010246
Offset address? AZ
Base address? ~Z
File to patch? Z

New?
? 104771

? ~Z

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

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 ADDed, or if it is your system default run-time
system, execute the following commands:
RUN $UTILTY<cr>
<UTILTY's header line>
#UNLOAD BASIC<cr>
IIEXIT<cr>

(BASIC-PLUS Run-Time System name)

Ready
NOTE: The UNLOAD command \vill not remove the run-time system, but
simply instructs the monitor to reload it the next time a job
requests it.
If, in addition to being previously ADDed, the run-time system had
been ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
#LOAD BASIC/STAY/ADDR:nnn<cr>
#EXIT<cr>
Ready

(BASIC-PLUS Run-Time System name)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
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 V7.2 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:
1.

Issuing them between the OLD
whenever a breakpoint is hit.

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

and

RUN

a program and, thereafter,

Any DEBUG commands are disabled when:
1.
2.
3.

A "RUN <program-name>" command is successfully executed, or
A NEW, OLD, or EXIT command is executed, or
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
UN TRACE
BREAK
UNBREAK

Without
Patch
T?ACE
U?TRACE
B?EAK
U?BREAK

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.1.0.1 N
2 of 4

TRACE/UNTRACE
The TRACE command causes BASIC-PLUS to print the message "at line nnn" (where
"nnn" represents a line number) each time that a line number is encountered or
the current line number changes.
The UNTRACE command disables any previous invocation of the TRACE command.
BREAK/UNBREAK
The BREAK command allows you to specify that execution should stop any time
that a specified line number is encountered. Up to 1.0 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 [ N1, N2, N3 , ..• , N10 ]
If no line numbers are specified, all breakpoints are disabled.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
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
proceeds with execution of the program.

nnn"

and

RSTSIE V7.2 Maintenance Notebook, June 1982

RSTSIE V7.2
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 DIGITAL makes no
commitment to fix problems reported with the DEBUG facility, we 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
"Y/D" to SYSGEN's "Generate BASIC-PLUS?" query.

run-time

system,

respond

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
BASIC-PWS
Non-standard BASIC-PLUS Features

Seq 4. Hl.2 N
1 of

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
cannot be used in a BASIC-PLUS program), and has the syntax

(i.e.,

DUMP <file-specification>
If no device name is specified, the public disk structure ("sy:") is used. If
no filename is specified, the current program name is used. If no file type
is specified, ".PMD" is used.
THE BASIC-PLUS DUMP ANALYSIS PROGRAM
After the DUMP command has been issued, you can use the BPDA program to print
the contents of each variable that is used in the program, as well as the
contents of the buffer of any open files.
The BPDA program asks for an input file name. The default file type is
" . PMD". There is no default for the file name. Wildcards are illegal.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
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:
<out file>

= <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 CTRLIC 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.
1.

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 DIGITAL makes no
commitment to fix problems reported with the DUMP facility, we would like to
know about any problems that you encounter.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.H"3 F
1 of 3

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 ("?"),
i.e., B?EAK, T?ACE, U?BREAK, and U?TRACE.
SOLUTION:
The patching procedure detailed below 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
installed in any BASIC-PLUS run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

can

installed

using

may

the

PATCH

(BASIC-PLUS run-time system name)

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

system.

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
BASIC-PLUS
Non-standard BASIC-PLUS Features
4.

2 of 3

The patch is as follows:
Base address? .• BEA.
Offset address? 0
Base
Offset Old
?????? 131313131313
077
?????? 013130131
???
Offset address? "z
Base address? •• TAC.
Offset address? 0
Offset Old
Base
?????? 131313131313
077
?????? 13131313131
???
Offset address? "z
Base address? •• UBR.
Offset address? 0
Base
Offset Old
?????? 13131313013
1377
?????? 0131313131
???
Offset address? "z
Base address? •. UTR.
Offset address? 0
Offset Old
Base
?????? 13131313013
077
?'????? 0131313131
???

Seq 4.10.3 F

New?
? IR
? "z

New?
? 'N
? "z

New?
? 'N
? "c

( CTRLlZ for new offset)
( CTRLlZ for new base)

( CTRLlZ for new offset)
(CTRLlZ for new base)

(up-arrowl C to ex it; CTRLI 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 ADDed, or if it is your system default run-time system, execute the
following commands:
RUN $ UTI LTY <c r >
<UTILTY's header line>
HUNLOAD BASIC<cr>
IIEXIT<cr>

Ready

(BASIC-PLUS run-time system name)

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.10.3 F

RSTS/E V7.2
BASIC-PLUS
Non-standard BASIC-PLUS Features

3 of 3

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.
If, in addition to being previously ADDed, the run-time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
HLOAD BASIC/STAY/ADDR:nnn<cr>
IIEXIT<cr>
Ready

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
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 patching procedure detailed below will enable the DUMP feature.
PROCEDURE:
1.

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

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

can

installed

may

using

the

PATCH

(BASIC-PLUS run-time system name)

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

system.

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
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

? BNE+2
? AC

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

(BASIC-PLUS run-time system name)

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E

V7.2 Maintenance Notebook, June 1982

RSTS/E

V7.2

Seq 4. Hl.5 F

BASIC-PLUS
Non-standard BASIC-PLUS Features

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 non-privileged 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.
Some installations, however, may want to allow all users
BASIC-PLUS programs to which they have RUN access, regardless of
program is compiled.

to DUMP all
whether the

SOLUTION:
The patching procedure detailed below 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 (IiReady") state. Hence, a non-privileged user can never DUHP such a
program. )
PROCEDURE:
1.

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

The patch described in Step L! below
option of INIT,SYS:
Option: PATCH
File to patch? BASIC.RTS

can

installed

may

using

the

PATCH

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0,lJBASIC.RTS
File found in account [0.1J

system.

the

on-line

patching

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
BASIC-PLUS
Non-standard BASIC-PLUS Features

Seq 4.10.5 F
2 of 2

This patch is contained in a patch file appearing in patch kit version II A"
or later.

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

New?
? NOP
? NOP
?

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

(BASIC-PLUS run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run~time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
IILOAD BASIC/STAY/ADDR:nnn<cr>
IIEXIT<cr>
Ready

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 4.10.6 F

RSTS/E V7.2
BASIC-PLUS
Non-standard BASIC-PLUS Features

1 of 2

CHANGING THE BASIC-PLUS D?HP 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 patching procedure detailed below 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
installed in any BASIC-PLUS run-time system.

The patche described in Step 4 below can
option of INIT.SYS:
Option: PATCH
File to patch? BASIC.RTS

installed

using

may

the

PATCH

(BASIC-PLUS run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File. Name? <cr>
File to patch? [0,1JBASIC.RTS
File found in account [0,1J

system.

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq4.Hl.6F

RSTS/E V7.2
BASIC-PLUS
Non-standard BASIC-PLUS Features
4.

The patch is as follows:
Base address? .. DMP.
Offset address? 0
Offset Old
Base
?????? 000000
077
?????? 000001
???

2 of 2

New?
?
?

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

(BASIC-PLUS run-time system name)

system

had

(BASIC-PLUS run-time system name)

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
TECO
TECO Notes

Seq 9. 1 . 1 N
1 of 1

NOTE ON THE HANDLING OF THE IB+ AND IB2 SWITCHES
When TECO reads a page of text into the editing buffer, it stops when it
encounters a FORMFEED character, or when the buffer is full. In the latter
case, the last line in the buffer will be complete (i.e., it includes the line
delimiter), but no look-ahead is done to examine the next line in the file.
If TECO is used with the IB+ or IB2 switch to edit a very long BASIC-PLUS or
BASIC-PLUS-2 source program that is not segmented with FORM FEED characters,
chances are good that the last line in the buffer will not coincide with the
last line of a (numbered) multiple-line combination.
When the buffer is written to the output file, TECO assumes that the last line
in the buffer is the last line of a multiple-line combination, and terminates
it with a CARRIAGE-RETURN character, rather than with a LINEFEED (or
AMPERSAND)
CARRIAGE-RETURN
character combination.
This can cause the
remaining lines of that multiple-line combination to be lost when the program
is subsequently OLDed.
To avoid this problem, lengthy BASIC-PLUS or BASIC-PLUS-2 programs should be
segmented into smaller sections (approximately 150 to 200 lines) with FORMFEED
characters before editing them with TECO's 18+ or IB2 switches.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
DIRECT

Seq 10.3.1 F
1 of 2

ALLOW NON-PRIVILEGED ACCESS TO OTHER DIRECTORIES - DIRECT FEATURE PATCH
PROBLEM:
Non-privileged users are only allowed to list the directory information of
files on the system to which they have read or run access. However, some
installations, for which security is not a concern, may find it desirable to
allow non-privileged users to list all files in the system.
SOLUTION:
Another feature patch, Seq 3.5.9 F, extends the use of FIP calls 15 (Directory
look up on Index) and 17 (Directory lookup by File Name/Wildcard directory
lookup). Since DIRECT does not use these calls, a separate procedure is
necessary to cause DIRECT to allow non-privileged users to list directory
information of all files on the system.
NOTE
For consistency, Digital recommends that you either use
patches (Seq 3.5.9 F and Seq 10.3.1 F) or neither of them.

both

PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
We assume the executable version of the program will be stored in the
System Library Account ($). If this is not the case, replace references
to $ in step 3 below with the appropriate package or library account.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system default

If you are using CSPCOM or BASIC-PLUS-2, refer to Section 5.4 of the
RSTS/E V7.2 Maintenance Notebook for the correct procedure to compile the
program.
If you are using BASIC-PLUS-2, this program should be compiled
BASIC2 run-time system.

under

the

RSTS/E V7.2 Maintenance Notebook, June 198,2

RSTS/E V7.2
System utilities Package
DIRECT
2.

Seq 10.3.1 F
2 of 2

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - DIRECT.BAS:DIRECT.BAS<cr>
#[logfile=]KB:/CS:58126<cr>
*H/2! IV<cr>
2!
PROGRAM
DIRECT.BAS
*H/300<tab>/V<cr>
300
CROSS.PROTECT%=-1% &
*GI-1/-2C/0/V<cr>
300
CROSS.PROTECT%=0% &
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete
#"Z

File to patch -

Ready
3.

system

library,

type

OLD DIRECT<cr>
Ready
COMPILE $DIRECT<232><cr>
Ready
4.

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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2

Seq 10.12.1 N

System utilities Package
LOGIN

1 of

INSTALLING USER MODIFICATIONS OR FEATURE PATCHES TO LOGIN
When you install feature patches or your own patches to LOGIN, you should take
the following steps.
1.

Log into a privileged account at TWO terminals.

Copy LOGIN.(BAC,TSK) to LOGIN.OLD

Install the new version of LOGIN

Test the ne\.,r version extensively

Delete LOGIN.OLD

If a patch to LOGIN causes it to fail, and you have logged out of the ONLY
privileged, attached job on the system, the only way to recover is to crash
the system and stop it when INIT.(BAC,TSK) starts to execute. By logging in
to the second terminal, you can quickly restore the previous (working) version
of LOGIN, if necessary.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
LOGIN

Se q 10. 12 • 2 F
1 of 3

UNSCRUPULOUS PROGRAMS MAY CHAIN TO LOGIN - LOGIN FEATURE PATCH
PROBLEM:
Users, particularly in an educational environment, have been known to write
programs that simulate the LOGIN dialogue, store the account number and
password, and then CHAIN to LOGIN. In this way, a hostile user can gain
access to the accounts of other users without the knowledge (or permission) of
those users.
SOLUTION:
The patching procedure detailed below will cause LOGIN to report both the
original account and the new account when invoked by a logged-in job. While
this will not prevent a user from writing such a program, it will allow the
victimized user to report the account that was used to the system manager.
Note that the variable W$ has been defined in the patch as a null string
(W$="") at line 28000. The null string can be replaced with some message such
as "Please inform the System Manager" if desired.
Assume that the LOGIN-simulating program resides in account [2,219J. When the
patch described below has been installed, a typical run may look like this:
HELLO 1,224
Password:
Old Account:

[2,219J

New Account:

[1,224J

Please inform the System Manager.
Ready
PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
The executable version of the program must be stored in the System Library
Account ($) on the system disk.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system

default

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
System utilities Package
LOGIN

Seq 10.12.2 F
2 of 3

This patch is contained in a patch file appearing 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 procedure below.
NOTE
If you wish to have W$ indicate a particular message, the
patch file for this patch requires manual editing before i t
can be successfully installed.
Be sure to include the
quotes around the desired message. The patch verify line
which follows the insertion of the message will vary,
echoing the message you have chosen.
To apply the patch manually, perform the following RSTS/E system commands.

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - LOGIN.BAS=LOGIN.BAS<cr>
#[logfile=]<cr> -*H/2!/V<cr>
2!
PROGRAM
LOGIN. BAS
*H/15000<tab>/V<cr>
15000
GOSUB 22900 &
*18AV<cr>
!\ GOSUB 28000 IF W% &
*G/!/-1DV<cr>
\ GOSUB 28000 IF W% &
*H/28000<tab>/V<cr>
28000
PRINT &
*7AV<cr>
\ W$="" &
*GI'''' 1-2C/"" IV<cr>
<Insert a message here, if desired.>
\ W$='''' &
*EX<cr>
Patch from _KB:[P,PN]CPATCH.CMD complete
II" Z

File to patch Ready

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 10.12.2 F

RSTS/E V7.2
System utilities Package
LOGIN
3.

3 of 3

system

library,

type

OLD LOGIN<cr>
Ready
COMPILE SY0:$LOGIN<232><cr>
Ready
4.

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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
LOGIN

Seq 10. 12.3 F
1 of 2

LOGIN CAN PRINT A MESSAGE FOR SPECIFIC ACCOUNTS - LOGIN FEATURE PATCH
PROBLEM:
Some installations may choose, on occasion,
users of specific accounts.

establish

messages

for

the

SOLUTION:
The patching procedure detailed below will allow the System Manager, or anyone
else with access to a given account, to establish a message file that will be
printed anytime that someone logs in under that account. To create the file,
use $PIP (or a suitable text editor) to create the file "MESSAG. TXT" in the
appropriate account.
Each time that a user logs in, LOGIN will check for the presence of the file
"MESSAG. TXT" in that account. and print the contents of that file if it
exists. This file will be printed (if present) even if the system message
($NOTICE.TXT)
has been suppressed with a slash (II/n) in the account
specification.
Note that anyone with write-access to the file MESSAG.TXT, including users
that account, will be able to create, change, or delete the message.

PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
The executable version of the program must be stored in the System Library
Account ($) on the system disk.
The procedure below
run-time system.

assumes

CSPCOM

you

are

using

that
or

BASIC-PLUS

your

system

defaul t

BASIC-PLUS-2, refer to Section 5.4 of the
the

RSTS/E V7.2 Maintenance Notebook for the correct procedure to compile

program.
If you are using BASIC-PLUS-2, this program must be task built against the
BP2COM run-time system.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
System utilities Package
LOGIN
2.

Seq 10. 12.3 F
2 of 2

This patch is contained in a patch file appearing in patch kit version" Ail
or later. If you do not have this distribution you can produce a command
file by specifying a file for [logfile=] in the procedure below.
To apply the patch manually, perform the following RSTS/E system commands.

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch ~ LOGIN.BAS=LOGIN.BAS<cr>
#[logfile=]KB:/CS:64049<cr>
*H/2!/V<cr>
2!
PROGRAM: LOGIN.BAS
*H/32405<tab>/V<cr>
!RESUME 14020 IF ERL=14000% OR ERL=14010% &
32405
*G/! I -1DV<cr>
RESUME 14020 IF ERL=14000% OR ERL=14010% &
32405
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete

File to patch _

Ready
3.

system

library.

type

OLD LOGIN<cr>
Ready
COMPILE SY0:$LOGIN<232><cr>
Ready
4.

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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Utilities Package
LOGIN

Se q 1 0. 1 2 . 4 F
1 of 3

LOGIN CAN CHAIN TO A SPECIFIED PROGRAM - LOGIN FEATURE PATCH
PROBLEM:
Some installations may find it desirable to have LOGIN chain
program when some or all users log in.

specified

SOLUTION:
The patching procedure detailed below will cause LOGIN to chain to the
specified program, if it exists. (LOGIN will proceed normally if the program
does not exist.)
At line 22950, the variable MGR.PROG$ should be set to some program
follows:

name,

START

This will cause LOGIN to chain to the program "START" if it
exists in the current user's account.

/lSTART

This will cause LOGIN to ch&in to the program
exists in the user's group library ( [*,0J ).

$START

This will always cause LOGIN to chain to the program "START" if
it exists in the system library ( [l,2J ).

"START"

PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all progr&m references with
suit&ble text according to the requirements of your installation.
The executable version of the program must stored in the System Library
Account ($) on the system disk.
The procedure below
run-time system.

assumes

CSPCOM

you

are

using

that
or

HASIC-PLUS

your

system

default

BASIC-PLUS-2, refer to Section 5.4 of the
the

RSTS/E V7.2 Maintenance Notebook for the correct procedure to compile
program.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 10. 12. 4 F

RSTS/E V7.2
System Utilities Package
LOGIN

2 of 3

If you are using BASIC-PLUS-2, this program must be task built against the
BP2COM run-time system.
2.

This patch is contained in a patch file appearing 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 procedure below.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed.
Specifically, "START" should be
replaced with the desired program name (be sure to include
the quotes). The patch verify line which follows the
insertion of the program name will vary, echoing the program
name you have chosen.
To apply the patch manually, perform the following RSTS/E system commands.

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - LOGIN.BAS=LOGIN.BAS<cr>
It [logfile= ] <cr>
*H/2! IV<cr>

PROGRAM

*H/2295~<tab>/V<cr>

22950
MGR. PROG$='''' &
<Replace "START" with the desired program name>
*G/"" /-2C/"START" /V<cr>
22950
MGR.PROG$="START" &
*EX<cr>
Patch from _KB:[P,PN]CPATCH.C~1D complete

tr'z

File to patch Ready

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Utilities Package
LOGIN

Seq 10.12.4 F
3 of 3

Use this procedure if your system default run-time system is BASIC~PLUS;
otherwise, refer to Section 5.4 of the RSTS/E V7.2 Maintenance Notebook
for the correct procedure to compile the program.
To re-compile the program and re-enter it into the
the following RSTS/E commands.

system

library,

type

OLD LOGIN<cr>
Ready
COMPILE SY0:$LOGIN<232><cr>
Ready
4.

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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 10. 12.5 F

RSTS/E V7. 2
System utilities Package
LOGIN

1 of 2

DON'T LOG ACCESS ATTEMPTS OVER DIAL-UP LINES - LOGIN FEATURE PATCH
PROBLEM:
We assume that most installations will find it desirable to log all access
attempts made from dial-up lines. This enables an installation to keep track
of which accounts are being used to gain system access over dial-up lines and
what type of logged-out requests are made over these lines. This log is
normally sent to OPSER, but will be sent to KB0: if OPSER is not running.
SOLUTION:
For those systems that choose not to log access attempts over dial-up lines,
the patching procedure detailed below will prevent access attempts made over
dial-up lines from being logged to OPSER.
PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
The executable version of the program must be stored in the system Library
Account ($) on the system disk.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system

default

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 10. 12.5 F

RSTS/E V7.2
System Utilities Package
LOGIN

2 of 2

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - LOGIN.BAS=LOGIN.BAS<cr>
#[logfile=]KB:/CS:14877<cr>
*H/2!/V<cr)
2!
PROGRAM: LOGIN.BAS
*H/13100<tab>/V<cr>
13100
SEND.OPSER%=-l% IF (L.CLASS% AND JCLS.REM.BITX) &
*GI=/35C/0%/V<cr>
SEND.OPSER%=0% &
13100
*H/22500<tab>/V<cr>
22500
&
* 12AV<cr>
\ SEND,OPSER%=(TTINTF% AND 16384%)<>0% &
*GI=/22DV<cr>
\ SEND.OPSER%=0% &
*EX<cr>
Patch from _KB:[P,PN]CPATCH.CMD complete

File to patch _ AZ
Ready
3.

system

library,

type

OLD LOGIN<cr>
Ready
COMPILE SY0:$LOGIN<232><cr>
Ready
4.

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

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

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
LOGIN

Seq 1.0.12.6 F
1 of 3

CHANGING L'OGIN TO SET A DIFFERENT SWAP MAXIMUM - LOGIN FEATURE PATCH

PROBLEM:
The LOGIN system program sets the swap maximum to 31K words for all users.
This action means that all users run with a swap maximum of 31K words (or the
system Swap Maximum, if that is lower than 31K).
SOLUTION:
1.

The LOGIN program may be modified to set a swap maximum of less than 31K
words for non-privileged accounts. To do this, you must change the value
31% in the statement "J% = 31%" (very first statement in line 15010) to
any value less than or equal to the current default swap maximum used at
system start up time.
To change the swap maximum for non-privileged accounts,
desired swap maximum for "NN" in the patch below.

substitute

the

LOGIN may also be modified to lower the swap maximum for privileged
accounts. To do this, you must change the "J% = 31%" expression in the
second physical line at line number 15010. The statement on this line
checks for a 1 as the project number of the account.
To change the swap maximum for privileged accounts, substitute the desired
swap maximum for "ZZ" in the patch below.

PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
The executable version of the program must be stored in the System Library
Account ($) on the system disk.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system

default

If you are using CSPCOM or BASIC-PLUS-2, refer to Section 5.4 of the
RSTS/E V7.2 Maintenance Notebook for the correct procedure to compile the
program.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 10.12.6 F

RSTS/E V7. 2
System Utilities Package
LOGIN

2 of 3

If you are using BASIC-PLUS-2, this program must be task built against the
BP2COM run-time system.
2.

This patch is contained in a patch file appearing 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 procedure below.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed. Specifically, have "NN" and/or "zz"
indicate the desired swap maximums.
To apply the patch manually, perform the following RSTS/E system commands.

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - LOGIN.BAS=LOGIN.BAS<cr>
#[logfile=]KB:<cr>
*H/2! /V<cr>
PROGRAM
LOGIN. BAS
2!
*H/15010<tab>/V<cr>
J%=31% &
15010
(from Step 1)
*G/31/-2C/NN/V<cr>
(will vary, based on NN)
J%=NN% &
15010
*AV<cr>
\ J%=31% IF (ACCOUNT% AND -256%)=256% &
*G/31/-2C/ZZ/V<cr>
(from Step 2)
\ J%=ZZ% IF (ACCOUNT% AND -256%)=256% & (will vary, based on ZZ)
*EX<cr)
Patch from _KB:[P,PN]CPATCH.CMD complete

File to patch _

Ready
3.

system

library,

type

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
LOGIN

Seq 10.12.6 F

3 of 3

OLD LOGIN<cr>
Ready
COMPILE SY0:$LOGIN<232><cr>
Ready
4.

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 should now be removed from the
public structure.
As noted in the RSTS/E Programming Manual, it is
recommended that the system manager not replace the original LOGIN source
file with the modified version.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
LOGIN

Se q 10. 12 .7 F
1 of 2

ENABLE LOGGED-OUT COMMANDS - LOGIN FEATURE PATCH
PROBLEM:
LOGIN does not let users invoke any of the following programs if they are
logged out: HELP, SET, SYSTAT, and QUE. Some installations may want to allow
all users to be able to run these programs, even if they are not logged in.
SOLUTION:
The patching procedure detailed below allows logged out access to all
programs listed above.

the

PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
The executable version of the program must be stored in the System Library
Account ($) on the system disk.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system

default

This patch is contained in a patch file appearing in patch kit version irA"
or later. If you do not have this distribution you can produce a command
file by specifying a file for [logfile=] in the procedure below.
To apply the patch manually, perform the following RSTS/E system commands.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
System utilities Package
LOGIN

Seq 10.12.7 F
2 of 2

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - LOGIN.BAS=LOGIN.BAS<cr>
#[logfile=]KB:/CS:6686<cr>
*H/2! IV<cr>
2!
PROGRAM
: LOGIN.BAS
*H/32240<tab>/DV<cr>
32240
DATA
HELP,
$HELP, 4,
3
*H/32250<tab>/DV<cr>
32250
DATA
SET,
$TTYSET,3,
4
*H/32260<tab>/DV<cr>
4
32260
DATA
SYSTAT, $SYSTAT,2,
*H/32270<tab>/DV<cr>
32270
DATA
QUEUE, $QUE,
2,
4
*EX<cr>
Patch from _KB:[P,PN]CPATCH.CMD complete
#"Z

File to patch -

Ready
3.

system

library,

type

OLD LOGIN<cr>
Ready
COMPILE SY0:$LOGIN<232><cr>
Ready
4.

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 should now be
public structure.

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
System utilities Package
LOGIN

Seq H'.l. 12. 8 F

1 of 3

ENABLE AUXILIARY PASSWORD - LOGIN FEATURE PATCH
PROBLEM:
Some installations may find it desirable to augment system security by
requlrlng privileged users to supply an auxiliary password when logging in
over dial-up lines or when using DECnet/E.
SOLUTION:
The patching procedure detailed below enables code in LOGIN which will require
privileged users to supply an extra password in the cases noted above. (You
may wish to change the auxiliary password periodically, for additional
security. )
PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
The executable version of the program must be stored in the System Library
Account ($) on the system disk.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system

default

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
LOGIN

Seq 113. 12 .8 F
2 of 3
NOTE

The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed. Specifically, "AUXPASS" should be
replaced by the desired auxiliary password (be sure to
include the quotes). The patch verify line which follows
the insertion of the password will vary, echoing the
password you have chosen.
To apply the patch manually, perform the following RSTS/E system commands.
RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - LOGIN.BAS=LOGIN.BAS<cr>
#[logfile=]KB:<cr>
*H/2!/V<cr>

2!
PROGRAM
*H/13015<tab>/V<cr>
131315
L.PROJ%=M%(6%) &
*2AV<cr>
!\ GOSUB 1311313 &

*G/!/-DV<cr>

\ GOSUB 1311313 &
*H/225135<tab>/8AV<cr>
\ L. PASS$="" &
*GI""1-2C/"AUXPASS"/V<cr>

\ L.PASS$="AUXPASS" &
*EX<cr>
Patch from _KB:[P,PN]CPATCH.CMD complete
#"Z

File to patch -

Ready
3.

system

library,

type

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
LOGIN

Seq 10. 12.8 F
3 of 3

OLD LOGIN<cr>
Ready
COMPILE SY0:$LOGIN<232><cr>
Ready
4.

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 should now be
public structure.

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
SHUT UP

Seq 10.21.1 F
1 of 3

CHANGING 'SHUTUP' SLEEP PARAMETERS - SHUTUP FEATURE PATCH
PROBLEM:
In the" Initial Job Killing Phase", SHUTUP makes two passes through the system
job table looking for active jobs which can be logged off the system or
KILLed. For those jobs which are attached to a keyboard, the following text
string is FORCEd to the terminal's input buffer to simulate the log off
sequence:
CTRLlC

CTRLlC

"BYE/Y" <cr>

Since this method requires the running of the system LOGOUT program, the
actual logging off process can consume a fair amount of elapsed time after the
text string FORCE is made.
The SHUT UP program is initially set up with the following parameters which
control a program pause (SLEEP) at the end of the job table search pass:
SLEEP.BASE%
= 10%
SLEEP.INCREMENT% = 2%
The length of the SLEEP period in seconds is calculated as:
SLEEP time = SLEEP.BASE% + (SLEEP.INCREMENT% * <number of terminals
"killed"> )
where the number of terminals "killed" is the total number of jobs sent the
FORCE text string during the pass through the job table. For example, for 3
terminals, a period of 16 seconds results; for 10 terminals, a period of 30
seconds results.
Some installations may desire to change these parameters to alter the SLEEP
period during this phase of SHUTUP operation. A case in point is when a
system has at least one terminal running on the system at 110 baud.
At this
transmission speed, it requires 25-30 seconds just to type out the LOGOUT
message which appears after typing BYE/Y. Changing the value of SLEEP.BASE%
to 30% should eliminate this problem.
SOLUTION:
Below is presented a procedure for changing the
SLEEP.INCREMENT%.

value(s)

SLEEP.BASE%

and/or

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
System utilities Package
SHUTUP

Seq Hl.21.1 F
2 of 3

Assume the following parameter values for the edit session which follows:
xx = new SLEEP.BASE%
value
yy = new SLEEP.INCREMENT% value
PROCEDURE:
For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
We assume the executable version of the program will be stored in the
System Library Account ($). If this is not the case, replace references
to $ in step 3 below with the appropriate package or library account.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system default

This patch is contained in a patch file appearing 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 procedure below.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed. Specifically, change references
to "xx" and "yy" to the desired values.
To apply the indicated corrections manually, perform the following
system commands.

RSTS/E

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 10.21.1 F

RSTS/E V7. 2
System utilities Package
SHUTUP

3 of 3

RUN $CPATCH<cr>
<CPATCHis header line>
File to patch - SHUTUP.BAS=SHUTUP.BAS<cr>
fI[ logfil=] <cr>

*H/2!/V<cr>
2!
PROGRAM
SHUTUP
*H/1031<tab>/V<cr>
1031
SLEEP.BASE% ::: 10% &
*G/10/-2C/xx/V<cr>
1031
SLEEP.BASE% ::: xx% &
*AV<cr>
\ SLEEP.INCREMENT% ::: 2% &
*G/2/-C/yy/V<cr>
\ SLEEP.INCREMENT% ::: yy% &
*EX<cr>
Patch from [P,PN]CPATCH.CMD complete

File to patch _

Ready
3.

Use this procedure if your system default run-time system is BASIC-PLUS;
otherwise, refer to Section 5.4 of the RSTS/E V7.2 Maintenance Notebook
for the correct procedure to compile the program.
To re-compile the program and re-enter i t into the system library, type
the following RSTS/E commands.
OLD SHUTUP<cr>
Ready
COMPILE SY0:$SHUTUP<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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System utilities Package
VT55

Seq 10.30.1 N
1 of 1

VT55 GRAPHICS DISPLAY TERMINAL SUPPORT
Software support for the VT55 Graphics Display Terminal has been included in
RSTS/E. The software consists of the following files which may be installed on
the library account [1,2J:
VT55.BAS
DEM055.BAS
VT55.BAS is a collection of BASIC-PLUS callable routines that
to the VT55 terminal.

provide

To run the test program and assure correct operation of the graphic
of the terminal:

access

functions

1. Login to any account from a VT55
2. OLD $DEM055
3. APPEND $VT55
4. RUN
The program will prompt for the KB: number of the VT55, and then proceed with
a simple but thorough test of the terminal and its software.
A manual presently exists describing methods for programming the VT55 terminal
and it may be ordered from the Software Distribution Center.
VT55 Programming Manual

Order #: AA-4949A-TC

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Error Control Package
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
ADDR MSB

These words contain the address of the word in memory which failed.
On the PDP-11/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 five times in the same minute, that cache group will be
disabled.

The remaining registers are not logged on the 11/70, which does not have
accessible memory CSR's. 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 MS11M or MS11L 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 (MF11-LP, MF11-UP,
MF11-WP, MF11S-K, MM11-DP, MM11-YP, and MS11-JP), this value is 1,
indicating that the CSR locates the error to within 1K words. For
older semiconductor memory controllers (MS11-AP, MS11-BP,
and
MS11-CP) that do not provide the address of the error in the CSR,
this value is the number of 1K-word blocks (up to 31.) controlled by
the CSR.

II 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 controller which resolves the
error location to within 1K words, 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.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Error Control Package
Package Notes

Seq 12.1.1 N
2 of 2

Base Adr

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

mentioned

Fail /In

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 5 such offsets may be logged.

Once a second, except on 11/70's, RSTS/E checks all memory CSR's 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 V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Error Control Package
ERRBLD

Seq 12.8.1 M
1 of 3

CORRECT DATA FORMAT ERROR - MANDATORY ERRBLD PATCH
PROBLEM:
"?ERRBLD - %Data format error at Line 7060" is generated
run.

when

ERRBLD.TSK

SOLUTION:
The patching procedure detailed below corrects the above problem.
PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
We assume the executable version of the program will be stored in the
System Library Account ($). If this is not the case, replace references
to $ in Step 3 below with the appropriate package or library account.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system default

If you are using CSPCOM or BASIC-PLUS-2. refer to Section 5.4 of the
RSTS/E V7.2 Maintenance Notebook for the correct procedure to compile the
program.
If you are using BASIC-PLUS-2, this program should be compiled
BASIC2 run-time system.
~.

under

the

The command file for this patch appears in patch kit version "A" or later.
The patch will already have been applied if you utilized the patch kit
during your standard program build.
To apply the patch manually, perform the following RSTS/E system commands.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 12.8.1M

RSTS/E V7.2
Error Control Package
ERRBLD

2 of 3

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - ERRBLD.BAS=ERRBLD.BAS<cr>
#[logfile=]KB:/CS:7658<cr>
*H/2!/V<cr>
2!
PROGRAM
ERRBLD.BAS
*H/6!/:V<cr>
EDIT
04
6!
*G /04/1/ A/V<cr>
EDIT
04A
6!
*H/7! /V<cr>
71
EDIT DATE
07-MAY-82
*G/07-MAY-82/-9C/14-MAY-82/V<cr>
71
EDIT DATE
14-MAY-82
*H/20<tab>/V<cr>
20
! &
*G/REASON/AI<cr>
<tab>! V7.2-04A<tab>14-MAY-82<tab>CORRECT DATA FORMAT ERROR &<cr>
<esc> *V <cr>
! &

*H/1010<tab>/V<cr>
10'10
I$="V7.2-04" &
*G/04/I1A/V<cr>
1010
I$="V7.2-04AiI &
*H/9500<tab>/V<cr>
DATA
"-UDA",
9500
*G/! /V<cr>

69,

17, &

*0AI<cr>
<cr>
9510<esc>*V<cr>
! &
9510
*H/9600<tab>/V<cr>
9600
DATA
"Success", &
*G/!/V<cr>
&

"!OAr <cr>
<cr>
9610<esc>*V<cr>
9610
! -&-*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete
/lA Z
File to patch - Z
A

Ready

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Error Control Package
ERRBLD
3.

Seq 12.8.1 M

3 of 3

Use this procedure if your system default run-time system is BASIC-PLUS;
otherwise, refer to Section 5.4 of the RSTS/E V7.2 Maintenance Notebook
for the correct procedure to compile the program.
To re-compile the program and re-enter it into the system library, type
the following RSTS/E commands. Note that the program should then be RUN.
OLD ERRBLD<cr>
Ready
COMPILE $ERRBLD<cr>
Ready
RUN $ERRBLD<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 should now be
public structure.

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Backup Package
BACDIR

Seq 13.5.1 F
1 of 3

DISABLE PRINTING OF "PLACED FILE ••• " WARNING MESSAGES - BACDIR FEATURE PATCH
PROBLEM:
The "PLACED FILE ... " warning messages that are printed on the terminal during
a BACKUP or RESTORE operation may take extra time and use a great deal of
extra paper, especially if there are many placed files on the system.
Since
the same messages are output to the listing file, it may be considered
redundant for them to be output to the terminal as well, especially through
OPSER to KB0:.
SOLUTION:
The patching procedure detailed below suppresses
FILE ... " warning messages to the terminal.

the

logging

"PLACED

PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
We assume the executable version of the program will be stored in the
System Library Account ($). If this is not the case, replace references
to $ in Step 3 below with the appropriate package or library account.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system default

under

the

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

To apply the patch manually, perform the following RSTS/E system commands.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 13.5.1 F

RSTS/E V7. 2
Backup Package
BACDIR

2 of 3

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - BACDIR.BAS=BACDIR.BAS<cr>
#[10gfile=]KB:/CS:5708<cr>
*H/2! IV<cr>
BACDIR.BAS
PROGRAM
2!
*H/11080<tab>/V<cr>
11080
Y2%=Y2% OR 1024% &
*25AV<cr>
\ GOSUB 23100 &
*GI<tab>/I/!/V<cr>
\ GOSUB 23100 &
*H/11220<tab>/V<cr>
11220
IF Z0%(P0%,12%) AND 2% AND 00%=2% THEN &
*5AV<cr>
\ GOSUB 23100 &
*GI<tab>/I/!/V<cr>
\ GOSUB 23100 &
*EX<cr>
Patch from _KB:[P,PN]CPATCH.CMD complete
II" Z
File to patch - ~Z
Ready
3.

Use this procedure if your system default run-time system is BASIC-PLUS;
otherwise, refer to Section 5.4 of the RSTS/E V7.2 Maintenance Notebook
for the correct procedure to compile the program.
To re-compile the program and re-enter it into the
the following RSTS/E commands.
OLD BACDIR<cr>
Ready
COMPILE $BACDIR<232><cr>
Ready

system

library,

type

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Backup Package
BACDIR

Seq 13.5. 1 F
3 of 3

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 should now be
public structure.

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Operator Services and Spooling Package
Package Notes

Seq 14. 1 ,1 N
1 of 2

NOTES ON THE USE OF THE SERIAL LA180 (LA180S) TERMINAL UNDER RSTS/E V7.2
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 IDELETE will be deleted.
Since there is no method by which the software can accurately 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
powered off or powered on after it has been ASSIGNed or OPENed.

when

During its power down and power up sequence, the LA180S terminal may send
spurious characters to the host processor. The ASCII code of these characters
appears to be random, but they occasionally take on the value of control
characters (for example, CTRL/C). Since the program printing on the terminal
may not expect input of any kind from the terminal, these spurious characters
may ,resul t in unexpected errors:
a CTRLlC may cause the program to print
READY; a CTRL/O will cause all further output to be discarded without
printing;
etc.
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 eXOFF) 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 ASSIGNed or OPENed.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Operator Services and Spooling Package
Package Notes

Seq 14.1.1 N
2 of 2

The
A final problem concerns loss of data when the LA180S is powered off.
LA180S 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 LA180S 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 LA180S is not powered off while it is printing.
In summary, DIGITAL recommends that any LA180S 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 LA180S. This
problem concerns the manner in which the terminal device handles printed lines
which are longer than the width of the terminal.
When a line is printed on the LA180S, the device prints characters until it
gets to the physical right margin. At that point, the logic of the terminal
inhibits further printing until a carriage return character moves the print
head back from the margin. When a CR is encountered in such a situation, the
LA180S also generates a line-feed, causing spacing to a new line. Since most
print lines are terminated by a 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 LA180S (i.e., longer than 132
characters) will cause a blank line on the printed output.
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 parameter in a TTYSET 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 s~ooler) 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 V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Spooling and Operator Services Package
QUE

Seq 14.4.1 F
1 of 2

DISABLE OPERATOR QUEUEING TO OTHER USERS ACCOUNT - QUE FEATURE PATCH
PROBLEM:
Under BATCH, operators, as defined in OPSER's table of operators, can QUE
files to be printed or jobs to be run for another user. Some installations
may consider this too great a security risk.
SOLUTION:
The following patch disables the above mentioned feature. It does not affect
the operator's ability to modify or kill other users' jobs once they are in
the queue, as that poses no apparent threat to system security. It also does
not affect a privileged user's ability to QUE files or jobs to another
account. Refer to article Seq 14.6.3 F, which supplies a similar patch for
QUMRUN.
PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
The executable version of the program must be stored in the System Library
Account ($). Note that QUE canno~ reside in any other account.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system

default

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Spooling and Operator Services Package
QUE

Seq 14.4.1 F
2 of 2

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - QUE.BAS=QUE.BAS<cr>
#[logfile=]KB:/CS:11874<cr>
*H/2!/V<cr>
PROGRAM: QUE
2!
*H/2015<tab>/V<cr>
IF NOT PRIV% AND Y1%(0%,1%)<>SWAP%(P8%)+P9% THEN &
2015
*G/NOT PRIV%I-9C/P8%<>1%/V<cr>
2015
IF P8%<>1% AND Y1%(0%,1%)<>SWAP%(P8%)+P9% THEN &
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete
#"Z

File to patch -

Ready
3.

system

library,

type

OLD QUE<cr>
Ready
COMPILE $QUE<232><cr>
Ready
4.

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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 14.6.1 F

RSTS/E V7.2
Spooling and Operator Services Package
QUMRUN

1 of 2

DISABLING 'JOB WITH DIFFERENT FORM NAME WAITING' MESSAGE
- QUMRUN FEATURE PATCH
PROBLEM:
QUMRUN will print a message on the OPERATOR SERVICES CONSOLE whenever one of
the LP:
spoolers has no JOBs which it may print but there are eligible JOBs
waiting in the spooler's queue with a form name which is different from that
of the spooler. It may be desirable to disable this feature.
SOLUTION:
The following patch will disable this feature.
PROCEDURE:
1.

assumes

that

BASIC-PLUS

your

system default

under

the

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 14.6.1 F

RSTS/E V7. 2
Spooling and Operator Services Package
QUMRUN

2 of 2

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - QUMRUN.BAS=QUMRUN.BAS<cr>
#[10gfile=]KB:/CS:57315<cr>
*H/2! IV<cr>
2!
PROGRAM
QUMRUN.BAS
*H/1380<tab>/V<cr>
1380
DFORMS% = 0% &
*G/IF Z4% = 2%/11 AND 0%/V<cr>
\
IF Z4% = 2% AND 0% THEN &
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete
II" Z

File to patch -

Ready
3.

system

library,

type

OLD QUMRUN<cr>
Ready
COMPILE $QUMRUN<cr>
Ready
4.

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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 14.6.2 F

RSTS/E V7. 2
Spooling and Operator Services Package
QUMRUN

1 of 2

RESTRICTING THE ASSIGNMENT OF BA: - QUMRUN FEATURE PATCH
PROBLEM:
Some installations may find it desir6ble to limit the number of BATCH
which can be used for jobs that are queued to BA:.

streams

SOLUTION:
The patching procedure detailed below will cause QUMRUN to avoid
jobs to BA6: and BA7: unless the user has specified BA6: or BA7:.

assigning

PROCEDURE:
L

For purposes of this discussion, we will assume that the program to be
patched is located in your pr i v 11 eged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
We assume the executable version of the program will be stored in the
System Library Account ($). If this is not the case, replace references
to $ in step 3 below with the appropriate package or library account.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system default

If you are using CSPCOM or BASIC-PLUS-2,

refer to Section 5.4 of the
RSTS/E V7.2 Maintenance Notebook for the correct procedure to compile the
program.

If you are using BASIC-PLUS-2, this program should be compiled
BASIC2 run-time system.
2.

under

the

This patch is contained in a patch file appearing in patch kit version II A"
or later. If you do not have this distribution you can produce a command
file by specifying a file for [logfile::] in the procedure below.
To apply the patch manually. perform the following RSTS/E system commands.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 14.6.2 F

RSTS/E V7.2
Spooling and Operator Services Package
QUMRUN

2 of 2

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - QUMRUN.BAS=QUMRUN.BAS<cr>
U[logfile=]KB:/CS:1.0597<cr>
*H/2!/V<cr>
2!
PROGRAM
QUMRUN . BAS
*H/15.070<tab>/V<cr>
1507.0
DEF* FNN% &
*G/DFORMS2%/V<cr>
\
DFORMS2%=CFNC%CLEFTCO$CZ3%,2%),2%),Z.0%CZ7%,9%» AND &
*0AI<cr>
<tab>\<tab>DFORMS1%=.0% IF 0$CZ3%,0%)="BA" &<cr>
<tab><tab><tab>IF CZ.0%CZ7%,1%) AND 255%)=255% IF 0%CZ3%,1%»5% &<cr>
<esc>*V<cr>
DFORMS2%=CFNC%CLEFTCO$CZ3%,2%),2%),Z.0%CZ7%,9%» AND &
\
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete

File to patch _

Ready
3.

system

library,

type

OLD QUMRUN<cr>
Ready
COMPILE $QUMRUN<cr>
Ready
4.

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 C.BAS) version of the program
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Spooling and Operator Services Package
QUMRUN

Seq 14.6.3 F
1 of 2

DISABLE OPERATOR QUEUEING TO OTHER USERS ACCOUNT - QUMRUN FEATURE PATCH
PROBLEM:
Under BATCH, operators, as defined in OPSER I S table of operators, can QUE
files to be printed or jobs to be run for another user. Some installations
may consider this too great a security risk.
SOLUTION:
The following patch disables the above mentioned feature. It does not affect
the operator's ability to modify or kill jobs once they are in the queue, as
that poses no apparent threat to system security. It also does not affect a
privileged user's ability to QUE files/jobs to another account. Refer to
article Seq 14.4.1 F, which supplies a similar patch for QUE.
PROCEDURE:
1.

For purposes of this discussion. we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
We assume the executable version of the program will be stored in the
System Library Account ($). If this is not the case, replace references
to $ in step 3 below with the appropriate package or library account.
The procedure below
run-time system.

assumes

that

BASIC-PLUS

your

system default

refer to Section 5.4 of the
RSTS/E V7.2 Maintenance Notebook for the correct procedure to compile the
program.

If you are using CSPCOH or BASIC-PLUS-2,

If you are using BASIC-PLUS-2, this program should be compiled
BASIC2 run-time system.
2.

under

the

This patch is contained in a patch file appearing in patch kit version II A"
or later. If you do not have this distribution you can produce a command
file by specifying a file for [logfile=] in the procedure below.
To apply the patch manually, perform the following RSTS/E system commands.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Spooling and Operator Services Package
QUMRUN

Seq 14.6.3 F
2 of 2

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - QUMRUN.BAS=QUMRUN.BAS<cr>
#[10gfile=]KB:/CS:16561<cr>
*H/2!/V<cr>
PROGRAM: QUMRUN.BAS
2!
*H/10070<tab>/V<cr>
10070
IF (CVT$%(MID(M$.16%.2%»=0%) OR ONE.SHOT% THEN &
if 3AV<cr>
E%=-l% UNLESS VALID.OP% &
*G/UNLESS II/(P% AND 255%)=1% OR (/G/VALID.OP%/II AND T%<>6%)/V<cr>
E%=-1% UNLESS (P% AND 255%)=1% OR (VALID.OP% AND T%<>6%) &
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete

File to patch _

Ready
3.

system

library.

type

OLD QUMRUN<cr>
Ready
COMPILE $QUMRUN<cr>
Ready
4.

The person making the changes to the pr~gram 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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 14. 10. 1 F

RSTS/E V7.2
Spooling and Operator Services Package
SPLRUN

1 of 2

ELIMINATING EXTRA FORM FEEDS ON SPECIAL FORMS - SPLRUN FEATURE PATCH
PROBLEM:
At the beginning of each job, the spooler performs two top-of-form operations.
The purpose of this action is to ensure that the new job really starts at the
top of a new form, with at least one blank page between it and the last job.
When using special paper forms, however, it is usually necessary to do a forms
alignment. In this case, it may be annoying to have the extra top of form
executed, because it wastes a page of the form.
SOLUTION:
The following patch inhibits the extra top-of-form operation at the start of a
new job.
Note that it inhibits the action not only after a forms-alignment
process, but also at the beginning of any job. If this patch is used, it is
essential that the paper be very carefully aligned in the printer. If the
paper is misaligned, one job will begin on the same physical page as the end
of the previous job.
PROCEDURE:
1-

assumes

that

BASIC-PLUS

your

system default

under

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Spooling and Operator Services Package
SPLRUN

Seq 14.10.1 F
2 of 2

To apply the patch manually, perform the following RSTS/E system commands.
RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - SPLRUN.BAS=SPLRUN.BAS<cr>
U[logfile=]KB:/CS:32856<cr>
*H/2!/V<cr>
: SPLRUN.BAS
2!
PROGRAM
*H/3200/V<cr>
3200
GOSUB 14500 IF PRTLNE%<>1% &
*AV<cr>
\ NXTLNE%=2% \ RECLEN%=0% \ GOSUB 14800 &
*2KV<cr>
\ GO SUB 21000 &
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete

File to patch _ AZ
Ready
3.

system

library,

type

OLD SPLRUN<cr>
Ready
COMPILE $SPLRUN<cr>
Ready
4.

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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Spooling and Operator Services Package
BATRUN

Seq 14. 15. 1 F
1 of 3

$EOJ DOES NOT RESET ERROR CONDITION - BATRUN FEATURE PATCH
PROBLEM:
The $EOJ command does not reset the "running in error" flag in BATRUN.
Thus,
exceeding the ERROR level prevents succeeding $JOB commands from being
processed. Without this feature patch, a batch control file containing
multiple $JOB and $EOJ commands will terminate immediately once an error which
exceeds the error level is detected.
With this patch installed, all
succeeding $JOB commands within the control file will be processed, regardless.
of whether any previous job within the control file failed to complete
properly due to an exceeded error level condition.
SOLUTION:
The following patch will allow each $EOJ command to reset the
that processing can continue with the next $JOB command.

ERROR

flag

PROCEDURE:
1.

assumes

that

BASIC-PLUS

your

system default

under

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Spooling and Operator Services Package
BATRUN

Seq 14.15. 1 F
2 of 3

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - BATRUN.BAS=BATRUN.BAS<cr>
#[logfile=]KB:/CS:53265<cr>
*H/2!/V<cr>
2!
PROGRAM
BATRUN.BAS<cr)
*H/400<tab)/V<cr)
400
! &
*G/!<tab>E8%/V<cr)
E8%
RUNNING IN LOCAL ERROR STATE FLAG. &
*0AKV<cr>
E9%
RUNNING IN ERROR STATE FLAG. &
*H/11030<tab)/V<cr)
11030
I%=I%+2% IF CVT$%(MID(OUTPUT$,I%+1%,2%»=3328% &
*GI<tab>\ E9%,/4DGI-l%I-3C/0%/V<cr>
\ E9%,Z0%(J9%,50%)=FNE0%("ERROR LEVEL EXCEEDED",0%) IF &
*H/13010<tab>/V<cr>
130H'J
E8%=0% &
*G/E8%=0%1-6C/E9%=0%/V<cr>
13010
E9%=0% &
*H/17130<tab)/V<cr>
17130
GOSUB 11000 &
*G/FNW%=-l% IF E8%1-3C/E9%/V<cr>
\ FNW%=-l% IF E9% &
*EX<cr)
Patch from KB:[P,PN]CPATCH.CMD complete
tfA Z
File to patch _ Z
A

Ready
3.

Use this procedure if your system default run-time system is BASIC-PLUS;
otherwise, refer to Section 5.4 of the RSTS/E V7.2 Maintenance Notebook
for the correct procedure to compile the program.
To re-compile the program and re-enter it into the
the following RSTS/E commands.
OLD BATRUN<cr)
Ready
COMPILE $BATRUN<cr>
Ready

system

library,

type

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 14.15.1 F

RSTS/E V7.2
Spooling and Operator Services Package
BATRUN

3 of 3

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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
System Management Guidelines
Package Notes

Seq 16. 1 . 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 back up the system disk by shutting down the RSTS/E
system and using the SAYRES 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 SAVEl RESTORE operations. This procedure has one
drawback: the INIT.SYS initialization code requires about 450 blocks on the
non-system disk (about 10% of an RK05). If you have small disks, such as
RK05 I S or RL01 is, you may wish to make the dangerous choice of not backing up
your non-system disk(s) and thereby risk loss of data from hardware or
software failure, or you could consider expanding your hardware to include
another disk drive or magnetic tape unit. For disks larger than RL01'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 ([0,lJINIT.SYS) on the
non-system disk immediately after initiali zing the disk with DSKINT. Thi s
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 examples below, the notation "SY0:" 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.

Ensure that HOOK.SAV is on your system disk in account [1,2J.
This will
be the case if your SYSGEN target system was SY:. If this file does not
already exist in [l,2J, mount your distribution system disk (with the
IRONLY switch) on xxn: and use the following commands to copy HOOK.SAV to
your system disk (user responses are underlined):

RUN $PIP.SAV<cr>
*SY0:$*.*:xxn:$HOOK.SAV<cr>
*"'Z

Ready

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 16.1.1 N

RSTS/E V7.2
System Management Guidelines
Package Notes

2 of 2

If you have not yet initialized the non-system disk that you plan to use,
shut down the system, mount the disk on xxn:, and use DSKINT to initialize
the disk. You may then start timesharing.

Issue the commands given below:
RUN $PIP.SAV<cr)
*xxn:[0,1]*.*:[0,1]INIT.SYS<cr)
*~Z

Ready
RUN $HOOK.SAV<cr)
*xxn:[0,1]INIT.SYS(cr)
Hook complete
*~Z

Ready
4.

Your non-system disk is now ready to use. You may dismount it and mount
it as a public 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
SAVRES option of INIT to SAVE or IMAGE-copy your non-system disk to the
backup disk.
NOTE
If you ever patch [0,1]INIT.SYS on the system disk, be
sure
to
patch that file on all disks which have
[0,1]INIT.SYS.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.2 N
1 of

USING BACKUP ON A TWO-DISK SYSTEM
This article describes the procedure for using the RSTS/E V7.2 BACKUP package
to back up the disks on a system which has only two disk drives and no
magnetic tape drive. On such a system, you can back up the system disk
normally by dismounting the non-system disk. The only requirement is that the
BACKUP package exist entirely on the system disk. However, it is impossible
to take a normal backup of the non-system disk. Such a procedure would
require that the system disk, the disk being backed up, and the backup volume
all be mounted simultaneously. and hence would require three or more disk
drives.
The solution presented in this article is to place a minimal system on the
other disk, allowing it to run as the system disk during the backup. You must
follow this procedure for every RSTS/E file structured disk pack, public or
private, which you ever mount along with the system disk and which you want to
be able to back up. This procedure has one major drawback:
the minimal
system requires a large number of blocks on the non-system disk (approximately
1400). If you have RK05 or RL01 disks, you should not use this procedure.
Instead, use SAVE/RESTORE to preserve these disks. If you have RK06 disks,
carefully consider the consequences of using a large part of your non-system
disk capacity (almost 6% for RK06) for backup. If you do not wish to use such
a large part of your non-system disk capacity for backup, you should use
SAVE/RESTORE instead (see article Seq 16.1.1 N). The only disadvantage with
SAVE/RESTORE is that you cannot save or restore individual files, but must
copy an entire disk. For disks larger than RK06s, the overhead of having a
small system on each nonsystem disk is usually small enough to be tolerable,
although you must decide based upon your system's needs.
If you decide to build a small system on each non-system disk, you may use
your standard monitor SIL, the SYSGEN.SIL provided by Digital, or another SIL
generated especially for the purpose. The last choice allows you to build a
small, special-purpose monitor for use only during backup and restore, thereby
minimizing the disk space required. If you generate a special monitor, it
should support at least 2 jobs, your two disks, one terminal (KB0:), have
nothing resident, no options, and a minimal number of small buffers. (Note
that such a system may cause BACKUP to run slowly. If you can afford the disk
space and wish to optimize the system for speed, more options and/or small
buffers should be included.) Remember to install any applicable patches to the
SIL.
You should place the minimal system for backup on the non-system disk
immediately after initializing the disk with DSKINT. This placement ensures
that contiguous space is available for the required files. After generating
the monitor, run-time system, and system library (including the BACKUP
package), perform the procedures outlined below.
In the examples, the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.2 N
2 of 3

notation "SY0:" denotes the disk drive on which your normal system disk is
mounted, and "xxn:" denotes the other disk drive on the system, which is used
for various purposes in the procedure. Note that the procedure below assumes
that your primary run-time system is BASIC-PLUS (e.g., the Backup Package,
SHUTUP, and INIT are .BAC files). If these programs are in .TSK form on your
system, be sure to substitute the proper file type where appropriate.
1. Ensure that the monitor SIL you want to use for your small backup system is
on the system disk. Generate it or copy it if necessary.
2. If you have not yet initialized the non-system disk you plan to use, shut
down the system, mount the disk on xxn:, and use DSKINT to initialize the
disk. You may then start timesharing.

3. Issue the commands given below:
RUN $UTILTY<cr>
<UTILTY's header line>
HMOUNT xxn:packid/PRIVATE<cr>
HUNLOCK xxn:<cr>

H"Z
Ready
RUN $PIP.SAV<cr>
*xxn:[0,l]*.*/MO:16=[0,l]bbbbbb.RTS,[0,l]ERR.ERR<cr>
*xxn:[0,l]*.*=[0,l]INIT.SYS,[0,l]ssssss.SIL<cr>
where ssssss is the SIL you wish to use on your backup disk, and
bbbbbb is the run-time system under which SHUTUPf UTILTY, and the
BACKUP package were compiled
*xxn:$*.*/W=SY0:$BAC???BAC,$BACKUP.PRM,$BACKUP.HLP,$SHUTUP.BAC,$UTILTY.BAC<cr>
to copy SHUTUP, UTILTY, and the BACKUP package to the non-system disk
(use a file type of .TSK if appropriate)
*xxn:[0,1]SWAP.SYS/MO:16/SI:128=NL:
(if using BASIC-PLUS-2 or CSPCOM/RSX, use ISI:224 rather than ISI:128)

*"z

Ready
RUN $HOOK.SAV<cr>
*xxn:[0,l]INIT.SYS<cr>
Hook complete

*"Z
Ready

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.2 N
3 of 3

4. Shut down your system, and use the BOOT option of the initialization code
to bootstrap the disk xxn:. Use INSTALL to install the ssssss SIL, which
you copied in step 3. Use DEFAULT to set defaults for the backup system.
Specify 16K (28K for BASIC-PLUS-2 or RSX) as the SWAP MAX, and bbbbbb as
the default run-time system.
Your non-system disk is now ready to use. You may dismount it and mount it as
a public disk if you desire. When you wish to back up that disk, you must
shut down your system and bootstrap the non-system disk. Use START to start
timesharing from the small system on the non-system disk. Since INIT.BAC (or
INIT.TSK) was not moved to the non-system disk, the messages:
?Can't find file or account
?Program lost-sorry
Ready
will be printed. You may now do your backup. (Alternatively, you may want to
move INIT.BAC (or INIT.TSK) to your non-system disk at the time you moved the
BACKUP package. In this case, you can include a control file to bring up a
limited RSTS/E system and include the backup commands in the control file.)
Physically remove your normal system disk from SY0: and mount a backup volume
in its place. Then use the BACKUP package to preserve the files on the disk.
Use a similar procedure to restore any files to the disk. If you lose the
entire file structure of the disk, including the system and/or the BACKUP
package, you can restore the disk using a system recovery medium as described
in article Seq 16.1.3 N.
NOTE
If you ever patch or replace on the system disk any of the
BACKUP or system modules that you copied in the above procedure,
you must do so while the non-system disk is not mounted as a
public
disk.
After
replacing the module(s), mount the
non-system disk with the /PRIVATE switch and use PIP (with the
/UP switch, update in place, if the output file is INIT.SYS, the
monitor SIL, or the default run-time system) to change the file
on the non-system disk. Repeat for each disk used on drive xxn:
that contains a minimal system for backup purposes.
Also, if
any patches are installed to the RSTS/E monitor or the INIT.SYS
code, be sure to install them on all disks which contain copies
of a RSTS/E system.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.3 N
1 of 9

CREATING A SYSTEM DISK RECOVERY MEDIUM
Regular use of the RSTS/E BACKUP package provides protection against loss of
files if the system crashes, if disk errors occur, or if important files are
accidentally destroyed. However, the one situation from which BACKUP cannot
recover is when the system disk or one or more of the monitor files is
destroyed and the system cannot be started at all.
One option in such an
event is to use the RSTS/E distribution kit to regenerate the system, install
all patches, build the complete system library, and then restore the remaining
files on the system disk from the most recent backup. This is time consuming
and error prone. Recovery is much simpler if you have a "recovery medium li •
One means of creating a system disk recovery medium is SAVE/RESTORE.
SAVE/RESTORE runs much more quickly than BACKUP for saving an entire disk and
generates a boatable recovery medium. SAVE/RESTORE, however, cannot perform
selective backups or back up the system disk while the system is running.
DIGITAL recommends that you use a procedure, such as the one outlined below,
to regularly protect your system against the catastrophic loss of critical
files that might result from hardware or software failure.
1.

Use SAVE/RESTORE periodically (perhaps weekly) to back up all of your
disks.
This will provide you with a bootable medium that can be used to
restore your entire disk(s) in the event of catastrophic failure.

Use BACKUP to back up those files which have changed since SAVE/RESTORE
was last run.
This will allow you to recover files that have changed
recently without shutting dovm your system disk to back them up.

The remainder of this article tells you how to create a system recovery medium
(disk or tape) if for some reason you choose not to use SAVE/RESTORE on your
system
The resul ting recovery medium \.-Jill contain your fully patched
monitor, BASIC~PLUS (or appropriate) run-time system, and enough of the BACKUP
package to restore the rest of the system disk file structure.
The recovery
medium is bootable in a manner similar to the distribution medium and any
intermediate tape (or disk) which you may have created during SYSGEN"
0

In order to recover from destruction of the system disk, you will need the
recovery medium and a recent backup of your system disk. Note that this
backup must include an up-to-date version of the file [l,2JACCT.SYS so that
the recovery can enter all accounts properly.
If you ever change your
monitor, or install any patches in any of the files placed on the recovery
medium, you should rebuild that medium.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.3 N
2 of 9

To build the recovery medium, you must have ADDed the RT1l run-time system to
RSTS/E.
You must also have the programs PIP.SAV and HOOK.SAV in account
[1,2].

Follow the instructions in the following sections, depending on whether you
wish to build a recovery disk or magnetic tape. In the examples, the file
name RSTS.SIL is used as the monitor SIL. You should substitute the actual
file name for your system.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.3 N
3 of 9

Building a recovery disk
Using PIP, create the file RECQVR.CMD in [1,2] containing the following

text:

("[X,y]" is the account containing the BACKUP package)
("rrrrrr" is the run-time system under which the Backup Package is compiled)
("ccc" is the file type of the compiled programs)
RUN $PIP.SAV<cr>
*$RECQVR.CMD=KB:<cr>
SY0:[x,y]*.*<232>/RTS:rrrrrr=IN:[x,y]BAC???ccc<cr>
SY0:[x,y]*.*=IN:[x,y]BACKUP.PRM<cr>
SY0:[x,y]BACENT.ccc<104>/RE<cr>

"i"Z

Mount a formatted and initialized disk on a free disk drive. (The text below
uses xxn: as the device designator and "packid" as the pack identification for
the recovery pack.) If necessary, shut down your system and use DSKINT to
format a pack, or use the program DSKINT.BAC to re-initialize an already
formatted scratch pack.
Using UTILTY or UMQUNT, logically mount xxn:.
Follow the procedure
underlined) :

below

RUN $REACT<cr>
<REACT's header line>
System Account Manager
Function? E<cr>
Proj,Prog? x,y<cr>
Disk:Password? xxn:pppppp<cr>
Quota? <cr>
Cluster Size? <cr>
Account Name? nnnnnn<cr>
Proj,Prog? 1,2<cr>
Disk:Password? xxn:pppppp<cr>
Quota? <cr>
Cluster Size? <cr>
Account Name? nnnnnn<cr>
Proj ,Prog? "z
Ready

build the recovery disk (user responses are

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
System Management Guidelines
Package Notes

Seq 16.1.3 N
4 of 9

RUN $PIP.SAV(cr>
*xxn:[0,1]*.*/MO:16:SY:[0,1]RT11.RTS(cr>
*xxn:[0,1]*.*/MO:16:SY:[0,1]rrrrrr.RTS(cr>
*xxn:[0,1]*.*/MO:16:SY:[0,1]ERR.ERR(cr>
*xxn:[0,1]*.*:SY:[0,1]INIT.SYS,[0,1]RSTS.SIL(cr>
*xxn:$*.*:SY:$PIP.SAV,$UTILTY.SAV,$RECOVR.CMD(cr>
*xxn:$*.*:SY:$REACT.ccc,$ACCT.SYS(cr>
*xxn:[x,y]*.*:SY:[x,y]BAC???ccc(cr>
*xxn:[x,y]*.*:SY:[x,y]BACKUP.PRM(cr>
*xxn:$PIP.SAV(232)IRE(cr>

*"Z
Ready
RUN $HOOK.SAV(cr>
*xxn:[0,1]INIT.SYS(cr>
Hook complete

*"Z
Ready
Dismount
medium.

the

recovery

disk

and

save

it.

Also dismount the distribution

To recover from the destruction of the system disk or one or
system files, you need the recovery disk and a recent BACKUP.

the

Mount the recovery disk on one disk drive and bootstrap it. The RSTS/E
initialization code runs and prints a header and the OPTION: prompt.
On another disk drive, mount the disk on which to restore the system disk.
Using the DSKINT option, recreate your system disk with the same parameters
that you used at system generation time.
Then use the COPY option to move your monitor files to the new system disk.
Use the IA switch to copy all relevant files (see the RSTS/E System Generation
Manual). As part of the COpy option, INIT bootstraps that disk.
If
necessary, use the HARDWR option to change controller characteristics.
Then INSTALL your monitor SIL and use REFRESH to create the required system
files on your system disk. Use DEFAULT to change the system default run-time
system to RT11.
START the system on your new system disk and continue as follows:

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.3 N
5 of 9

?Can't find file or account
.ASSIGN xxn:IN
.MOUNT IN:packid/RO<cr>
.R IN:UTILTY<cr>
*ADD rrrrrr<cr>

*A Z

.R IN:$PIP.SAV<cr>
*$*.*=IN:$ACCT.SYS<cr>

*AZ

Now run REACT to create all the accounts on the new system disk that were on
the old system disk. Ignore the errors generated when REACT attempts to enter
an account that already exists, either on SY: or on another disk .
. R IN:REACT<cr>
<REACT's header line>
System Account Manager
Function? S<cr>

Function? AZ
.R IN:$PIP.SAV<cr>
*@IN:RECOVR.CMD<cr>
*A Z
.R IN:UTILTY<cr>
*REMOVE rrrrrr<cr>
*DISMOUNT IN:<cr>
*SHUTUP<cr>
Option:
Dismount the recovery disk from drive xxn:. Use DEFAULT to change the system
default run-time system back to rrrrrr. START the system. Your new system
disk now has enough of the BACKUP package to restore the entire disk from a
recent BACKUP.
Do this now, specifying that all files be superseded. Your
system disk is now ready to use.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16. 1 .3 N

6 of 9

Building a recovery magnetic tape
Using PIP, create the file RECOVR.CMD in [1,2J containing the following

text:

("[x, yJ" is the account containing the BACKUP package)
("rrrrrr" is the run-time system under which the Backup Package is compiled)
("ccc" is the file type of the compiled programs)
RUN $PIP.SAV<cr)
*$RECOVR.CMD:KB:<cr)
SY0:[x,yJ*.*<232)/RTS:rrrrrr:IN:[x,yJBAC???ccc<cr)
SY0:[x,yJ*.*:IN:[x,yJBACKUP.PRM<cr)
SY0:[x,yJBACENT.ccc<104)/RE<cr)

*"Z
Mount a magnetic tape on a free drive (referred to below as xxn:). Follow the
procedure below to build the recovery tape (user responses are underlined):
ASSIGN xxn:.DOS<cr)
Ready
RUN $PIP.SAV<cr)
*xxn:/ZE<cr)
Really zero xxn:/density:ddd/parity:ppp? YES<cr)
*"Z
Ready
In the following, "ddd" represents the tape unit density.
RUN $HOOK.SAV<cr)
*xxn:[0,1JINIT.SYS/D:ddd,SY:[0,1JINIT.SYS<cr)
Hook complete

*"Z
Ready

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.3 N
7 of 9

RUN $PIP.SAV(cr>
*xxn:[0,1]*.*:[0,1]RT11.RTS(cr>
*xxn:[0,1]*.*:[0,1]rrrrrr.RTS(cr>
*xxn:[0,1]*.*:[0,1]ERR.ERR(cr>
*xxn:[0,lJ:SY:[0,1]RSTS.SIL(cr>
*xxn:$*.*:SY:$PIP.SAV,$UTILTY.SAV,$RECOVR.CMD(cr>
*xxn:$*.*:$REACT.ccc,$ACCT.SYS(cr>
*xxn:[x,y]*.*:SY:[x,y]BAC???ccc(cr>
*xxn:[x,y]*.*:SY:[x,y]BACKUP.PRM(cr>
HAZ

Dismount the tape and save it.
To recover from the destruction of the system disk or one or
system files, you need the recovery tape and a recent BACKUP.

the

Mount the recovery tape on a tape drive (referred to below as xxn:) and
bootstrap it. The RSTS/E initialization code runs and prints a header and the
OPTION: prompt.
Mount the disk on which to restore the system disk.
Using the DSKINT option, recreate your system disk with the same parameters
that you used at system generation time.
Then use the COPY option to move your monitor files to the new system disk.
Use the IA switch to copy all files with the appropriate file types (see the
RSTS/E System Generation Manual). As part of the COPY option, INIT bootstraps
that disk.
If necessary, use the HARDWR option to change controller
characteristics.
Then INSTALL your monitor SIL and use REFRESH to create the required system
files on your system disk. Use DEFAULT to change the default run-time system
to RT11.
START the system on your new system disk and continue as follows:

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.3 N
8 of 9

?Can't find file or account
.ASSIGN xxn:.OOS<cr>
.ASSIGN xxn:IN<cr>
.R IN:PIP<cr>
*$*.*<232>=IN:$PIP.SAV/NO<cr>
*$*.*<104>=IN:$UTILTY.SAV/NO<cr>
*$*.*=IN:$RECOVR.CMD/NO<cr>
*$*.*<124>/RTS:rrrrrr=IN:$REACT.ccc/NO<cr>
*$*.*=IN:$ACCT.SYS/NO<cr>
*~z

.R UTILTY.SAV<cr>
"ADD rrrrrr<cr>

.R $REACT<cr>
<REACT's header line>
System Account Manager
Function? S<cr>

Function? ~Z
.R $PIP<cr>
*@$RECOVR.CMD<cr>
*$RECOVR.CMD/DE<cr>
*~Z

Dismount the recovery tape from drive xxn:.
Your new system disk now has
entire disk from a recent BACKUP.

enough of the BACKUP package to restore the

Do this now, specifying that all files be superseded.
Your system disk is now ready to use.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
System Management Guidelines
Package Notes

Seq 16.1.3 N

9 of 9

Notes on systems with multiple public disks
During the recovery procedure, after starting the system on your new system
disk, you must physically mount and write-enable the other disks in your
system's public structure. Type the command
MOUNT xxn:packid
for each non-system public disk, replacing xxn: with the disk name and unit,
and pac kid with the pack ID for that disk. This procedure ensures that all
required disk space is available for the recovery.
Take the following precautions when creating a recovery disk:
1.

If you can mount the recovery disk on an unused drive or in place of a
private disk, do so. This leaves the full public disk structure mounted.

If you cannot mount the recovery disk in addition to the full public
structure, you must dismount a non-system public disk. This disk must not
contain any of the files required for the creation of the recovery disk or
the actual recovery procedure. This disk can be dismounted while creating
the recovery disk, and need not be mounted until a recovery is complete.
If necessary, use PIP to copy files from this disk to another disk on the
public structure:
RUN $PIP.SAV<cr>
*out:*.*=in:file.typ<cr>
*A Z
In these commands, "in:" is the name and unit number of the disk to be
cleared of files, "out:" is the name and unit number of any other public
disk, and file.typ is a file to be moved.
NOTE
You must not specify wildcard filenames for input when
transferring files between public disks in the same account.
Repeat these commands to PIP to copy each file on in: necessary for
building the recovery disk or for the recovery procedure itself.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
Package Notes

Seq 17.1. 1 N
1 of 4

RSTS/E V7.2 PATCH KIT "A" PATCHING PROCEDURE
NOTE
This article appears on Patch Kit "A"
Pack ID for disk media is "PATCHA".
I.

$PATCHA.DOC.

The

INTRODUCTION

Patch Kit "A" contains "Mandatory" and optional "Feature" patches published in
the RSTS/E V7.2 Maintenance Notebook and RSTS/E V7.2 Software Dispatch Review.
Patches to be applied during System Generation:
1.

There are mandatory patches for the monitor (in $MONITR.CMD).

There are mandatory patches for DECnet/E support (in $DECNTC.CMD).

There are mandatory patches for RJ2780 support (in $RJ2780.CMD).

Other patches (requiring the use of PATCPY):
1.

There are mandatory patches to the standard CUSP library. These may be
applied when installing BUILD.CTL and specifying BUILD/PATCH.

The Patch Kit includes all patches published for optional layered software
that appear in the RSTS/E Software Dispatch Review. Please be sure to
read the sections which follow prior to installing optional layered
software.

The Patch Kit contains
Maintenance Notebook.

all feature patches included in the RSTS/E V7.2

Note that there are currently no articles corresponding to the Mandatory
RSTS/E patches noted above.
The articles will be published in an upcoming
issue of the V7.2 RSTS/E Software Dispatch.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
Package Notes
II.

Seq 17. 1. 1 N
2 of 4

PATCH COMMAND FILES FOR MANDATORY PATCHES

The following
patches.
Command
File

list

of all patch command files containing "Mandatory"

Component
to patch

Comment-s

Using ONLPAT:
MONITR. CMD
INIT.CMD
BASIC.CMD
RSXRTS.CMD
DECNTC.CMD
RJ2780.CMD

Monitor patches
Initialization code
BASIC-PLUS Run-Time System
RSX Emulator
DECnet/E monitor patches
RSTS/E 2780 Device Driver

Has Patches

Using PBUILD:
EXEC.CMD
RMS.CMD
UT2780. CMD
DECNET.CMD
BP2EIS.CMD
BP2FIS. CMD
BP2FPU.CMD
COBOL.V41
DECAL.CMD
DMSDBL.CMD
RMSDBL.CMD
DMS500.CMD
DMSDMS.CMD
DMSIAM.CMD
DMSDSR.CMD
DTR.V24
FORTRA.V25
F77.V40
INDENT.CMD

All of the above except RSX
RMS-l1 V1.8
RSTS/E 2780 library
DECnet/E V2.0 Utilities
BASIC-PLUS-2 Vl.6 (EIS)
BASIC-PLUS-2 Vl.6 (FIS)
BASIC-PLUS-2 Vl.6 (FPU)
COBOL V4.1
DECAL V2
DMS DIBOL-l1/DECFORM V4.5
RMS DIBOL-l1/DECFORM V4,5
DMS-500 V02 (complete)
DMS-500 V02 (ISAM/RAM only)
DMS-500 V02
DMS-5(J(J V02
DATATRIEVE V2.4
FORTRAN IV V2.5
FORTRAN-77 V4
INDENT V1. 1

Has Patches
Has Patches

1.7
1.2
6

6
6

See Note
See Note

1,2,5
8
8
1,2,3
1.2,3
1,2,3
1,2,3
1

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
Package Notes

Seq 17. 1. 1 N

3 of 4

Notation:
1.

Requires distribution kit for that component - answer the PBUILD "Read
files to patch from" question with "dev:", where dev: is the device on
which the appropriate distribution kit is mounted, unless additional
instructions are listed below.

During patching, you must be running under the BASIC-PLUS run-time system.

Prior to the installation of DMS-5~0 V02 on RSTS/E V7.2, you must be
running under the BASIC-PLUS run-time system. If you are not, you must
first switch run-time systems. For example,
RUN $SWITCH(cr>
Keyboard monitor to switch to?

BASIC(cr>

Various error messages may appear during the running of the demonstration
program as part of the installation procedure. These problems will be
corrected by the auto-patch kit.
Note that optional patch file PA2401.CMD, included in the Patch Kit,
repeat just the demonstration portion of the installation procedure.

will

The BASIC-PLUS feature patch which causes BASIC-PLUS to default to EXTEND
mode must not be installed to the BASIC-PLUS run-time system while DMS-500
V02 is building or being patched. The build procedure for DMS-500 V02
will fail if this patch is installed.
4.

Be sure to refer to Appendix D of the RSTS/E FORTRAN IV Installation Guide
(AA-C762C-TC) before attempting to apply FORTRAN IV V2.5 patches. As
noted in that document, all files to be patched must reside in the account
under which you are running. Therefore, the "Read files to patch from"
question should be answered with "[p,pnJ", where [p,pnJ is the current
user account.
Also note that the first "patch" or file prints procedures to be performed
after the installation of the patches.

For DECAL V2 patching, answer the "Read files to patch from" question with
"dev:[250,lJ",
where
dey:
is the device on which the DECAL V2
distribution kit is mounted.
This is necessary because the required
source files reside in that account. DECAL.CMD determines which account
patched sources are to be compiled on by asking the question:
Locate DECAL Package on (SY:[1,2J> ? [p,pnJ

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
Package Notes

Seq 17.1.1 N
4 of 4

If you use the BUILD/PATCH option to apply patches, several questions will
be asked BEFORE BASBLD IS ACTUALLY RUN so that alternate names and
accounts may be determined. These questions are very similar to those
asked in the BASIC-PLUS-2 installation procedure. Be sure to specify the
same answer for corresponding questions asked by the autopatch procedure
and the installation procedure (BASBLD).

This patch kit contains several RMSLIB articles published in the RSTS/E
V7.2 Software Dispatch Review. As described in article Seq 48.1.4 N, the
patch procedure now includes a method for patching
the
resident
library(ies) as well. The procedure:
a.

Applies initial patches to RMSLIB.

Rebuilds the resident libraries, if requested.
If the procedure was invoked using the BUILD
resident libraries are automatically rebuilt.

program,

the

If the procedure was invoked using the PBUILD program, you will
be prompted to determine whether or not you wish to rebuild the
libraries.
Be sure to use this method if you do NOT want to
re-build the libraries for some reason.

Applies ONLPAT patches to the resident libraries.

Applies final patches to RMSLIB.

Applies final patches to RMSUTL and RMSIFL.

Rebuilds the RMS utilities.

As noted in articles Sequence numbers 26.59.1N and 26.18. 1N, two DIBOL
Check Digit Modules which were omitted from the DIBOL distribution kit are
included on the Patch Kit. These modules will automatically be included
if you install DIBOL using the BUILD/PATCH option, or run PBUILD.
Note that there are currently no mandatory patches for DIBOL V4.5. The
patch kit will install only the Check Digit Modules.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK

Seq 17.7.1 N
1 of 10

NOTES ON ATPK

INTRODUCTION
ATPK (pronounced "at-pee-kayll) is included in RSTS/E V7.2 for use as a part of
the BUILD procedure.
It can also be used, however, as a general purpose
indirect command file processor.
ATPK can control a job by use of a
pseudo-keyboard (PK) and run programs from a script previously defined in a
command file. As an indirect command file processor, ATPK runs at the user's
keyboard and reports the job dialogue there as it happens. ATPK can also be
used as a simple batch processor, running detached and reporting the job's
dialogue in a log file.
STARTING UP ATPK
ATPK may be invoked in one of the following ways:

RUN $ATPK
*<startup command>
or, if the eCL is installed,
ATPK <startup command>

or
ATPK
*<startup command)
ATPK will accept either of the eeL commands iiATPK" or "@II if they have been
installed by the system manager.
<startup command> is of the form:
[<log file> =] <command file> [/(switches>J
Valid switches are:

Run ATPK detached (available only to

IDET

privileged users).
Note
that if a log file is not specified, output will be to the
keyboard whether or not ATPK detaches.
At the end of a
successful detached run, ATPK will kill itself.

IDEL

Delete command file on successful completion (used by BUILD).

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK

Seq 17.7.1 N
2 of 10

IRTS:<rts> Start the controlled job under the keyboard monitor <rts>.
If
<rts> is not a keyboard monitor RTS, no error will be reported
and the new job will start up under the system default RTS.
If
this switch is not specified, the job will start under the
user's current job default RTS.

ILOG

If the user is privileged, the controlled job and any jobs
started with the $LOGIN command will be created regardless of
whether logins have been disabled.

ICHA[IN]: <program> [;<line>] [=\<core common>\]
On successful completion, chain to <program> at line number
<line>, if specified, with <core common> loaded in core common,
if specified. Any character not contained in <core common> may
be used in place of the backslashes to delimit the <core common>
argument. Thi s switch allows BUILD to patch itsel f or ATPK and
then chain back to itself for the rest of the build.
The dialogue of the controlled job will normally be printed on the terminal.
If a log file is specified, the dialogue will also be printed there. If both
a log file and the IDET switch are specified, the dialogue will be printed
only in the log file.
The default file types for the command and log files are,
and . LOG.

respectively,

.CMD

PROCESSING THE COMMAND FILE
ATPK usually sends each line of the control file "as is" to the PK when the
job at the PK enters a program or monitor keyboard wait stall. Four
characters in the command file are handled specially, however:
$

as first character on line, indicates an ATPK command.
as first character on line, indicates a comment.
indicates a control character.
indicates that the next character is not a special character.
(i.e., an underscore character quotes the following character.)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Automated Patching Facility Package
ATPK

Seq 17.7.1 N

3 of 10

ATPK commands:
Any command file line beginning with a dollar sign ("$") will be considered an
ATPK command. Valid ATPK commands are:
$DISABLE LOG

Turn dialogue reporting
keyboard) off.

the

log

file

$ENABLE LOG

Resume printing the controlled job's dialogue in
log file (and/or at the keyboard).

the

$ALLOW NO ERRORS

Abort if any (fatal
or
warning)
encountered by the controlled job.

are

$ALLOW WARNING ERRORS

Abort if a fatal error is encountered
controlled job, but allow warning errors.

$ALLOW FATAL ERRORS

Do not abort if any errors are encountered by the
controlled job (default setting).

$WAIT

Accept a line of input from the keyboard and send it
as input to the controlled job. If a program is
running at the controlled job after this line has
been processed, continue accepting command lines from
the keyboard until the program has stopped running
and the controlled job is in a keyboard monitor wait
(i.e., SYSTAT would show the job in a "ftC" state).
After this command has been processed, input will
resume from the command file.

$@<command file>

Switch input command stream to <command file>.
ATPK
will abort if the command file is not found. No
nesting of these indirect command files is allowed;
ATPK will abort if it finds the "$@" command in the
<command file>.

$DETACH

Causes ATPK to detach.
This command may be used
after the $WAIT command to cause ATPK to detach after
user input at the start of the controlled job.

(and/or

errors
by

the

$LOGIN [KB[n]:] [(p,pn)] Log in a keyboard under the user's account or the
account specified by (p,pn). This command, which is
only available to privileged users, causes ATPK to
create a job running LOGIN with instructions to
attach to the specified keyboard and log in under the
specified account.
If (p,pn) is not specified, the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK

Seq 17.7.1 N

4 of 113

account that ATPK is running under will be used.
If
n is not specified (e.g., $LOGIN KB:), LOGIN will be
instructed to attach to the keyboard from which ATPK
was started. This may be useful to log the user back
in following a command that started up ATPK with the
IDET
switch.
If the keyboard specification is
missing altogether, a new job will be started at the
pseudo keyboard under ATPK's control. The current
job at the pseudo keyboard. if any. will first be
killed in this case. If LOGIN fails to attach or log
in at the pseudo keyboard under ATPK
an error
message will be printed and ATPK will abort. If
LOGIN fails at any other keyboard, no error will be
returned to ATPK.
COMMENTS:
Any line starting with an exclamation point (Ii! II) will be recorded in the log
and not sent to the controlled job.
CONTROL CHARACTERS:
Any character preceded by an uparrow ("A") will be converted to a control
character before being sent to the controlled job. If a command line consists
oniy of an uparrow followed by a single character, the single control
character will be sent to the controlled job with no extra line terminator.
QUOTED CHARACTERS:
Any "$" or "! II that is meant to be the first character of a line to be sent to
the controlled job, or any !!~IV or II II in the command file that is not to be
interpreted as a special character by ATPK must be preceded with the
underscore character.
Every underscore character (except those preceded by
another underscore character) will be removed from the command line before it
is sent to the controlled job.
USING ATPK FOR SILENT SYSTEM STARTUP
If it is desired, most of system startup may be controlled under ATPK.
INIT.BAC (or INIT.T3K) need only run long enough to invoke ATPK. At the end
of system startup, the ATPK log can be queued to the line printer.
This
section suggests guidelines for writing ATPK startup files and gives a sample
set of these control files.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 17.7.1 N

Automated Patching Facility Package
ATPK

5 of 10

When designing the ATPK startup command files, most of the functions of
INIT.BAC will have to be performed with UTILTY. The recommended procedure for
bringing a non-system disk online after a crash is to clean the disk with
ONLCLN.SAV and then MOUNT and UNLOCK the disk with UTILTY.
\\1hen starting up the spooling package under ATPK, t~;10 points in particular
should be noted.
First, the $LOGIN command should be used to re-log in the
pseudo keyboard after a spooling program detaches.
Secondly. when the
spooling programs are invoked, they generally prompt for input and then sleep
while awaiting a response. Since ATPK will not respond unless the controlled
program enters an input stall (as opposed to a sleep). ATPK will not detect
when the spooler needs the command line. This problem may be circumvented by
including the startup command(s) on the same command file line as the command
that invokes the spooling program. If the commands are separated with an
uparrow-M, ATPK will insert a carriage return (the equivalent of a CTRL/H)
between the commands, causing them to be sent to the pseudo keyboard at the
same time, but as separate lines,
The way ERRCPY is normally started up by INIT is as follows: INIT runs as job
1, attaches to KB0:, forces the commands to KB0: to run ERRINT, and then
exits, The system then processes the type-ahead on K00: and runs ERRINT
as
job 1.
To avoid using KB0: in this way for the silent system startup, two
chain entries have been added to ERRINT so that ATPK. running detached as job
1, can simply chain to ERRINT for normal or crash system startup. Chaining to
ERRINT at line 31020 can be used for normal startup; crash dump output will
not be used.
For a crash recovery, chaining to ERRINT at line 31030 will
cause crash dump output to be used.
Care must be taken when starting up certain programs by forcing to other
terminals under ATPK, so that timing problems do not develop. For example,
under INrI, VT50PY could be started up to run detached and report to a
terminal by logging in that terminal, forcing the command to run VT50PY.
forcing the VT50PY command line, and then forcing commands to modi
the
displayed options.
Since INII runs at a low priority, it would be prevented
from running while VT50PY was running, and would force the next line only when
VI5eJPY was ready.
If the same technique \4ere used; using ATPK's $LOGIN
cOlPxnand to log in the keyboard and then forcing the commands \<1i th UTILTY, all
the commands ldould be typed at the terminal before VT50PY had the chance to
detach. As it detaches, VT50PY briefly closes the keyboard. The typed-ahead
commands would then invoke LOGIN at the keyboard and prevent VT50PY from
gaining access to ito VI50PY may be started up under ATPK using commands such
as the following:

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Automated Patching Facility Package
ATPK

Seq 17.7.1 N
6 of 10

RUN $DISPLY
60/24/DCA/TAB/ECHO/DET/KB5:
$LOGIN
RUN $UTILTY
FORCE KB5: F1
FORCE KB5: P
FORCE KB5: -0
FORCE KB5: J-S
EXIT
Because of the way the $LOGIN command works, VT50PY will be given enough time
to open the keyboard (KB5: in the above example) before the other commands
are forced.
The following is a sample set of control files that could be used
system startup.
$START.CTL:
FORCE KB0: RUN $ATPK
FORCE KB0: $STRTUP.LOG=$START.CMDIDET/LOG/CHA:$ERRINT;31020
END
$CRASH.CTL:
FORCE KB0: RUN $ATPK
FORCE KB0: $STRTUP.LOG=$CRASH.CMD/DET/LOG/CHA:$ERRINT;31030
END
$START.CMD:
$@[ 1,2 ]RTS. CMD
$@[1,2]MOUNT.CMD
$@[ 1 ,2]TTY. CMD
$@[ 1, 2]SPOOL. CMD
$@[1,2]CCL.CMD
RUN $UTILTY
REMOVE LOGICAL LB
ADD LOGICAL DM1:[1,11]LB
LOGINS
SEND ALL RSTS/E IS NOW ON THE AIR ...
EXIT
RUN $QUE
Q LP0:IDELETE/PRI:200=$STRTUP.LOG
EXIT

for

silent

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK
$CRASH.CMD:
$@[ 1 ,2]RTS. CMD
$@[l,2]ANALYS.CMD
$@[l,2]CLEAN.CMD
$@[ 1. 2]MOUNT. CMD
$@[1,2]TTY.CMD
$@[1,2]SPOOL.CMD
RUN $QUE
Q LP0:/PRI:200=$ANALYS.DMP
EXIT
$@ [ 1 • 2 ] eeL. CM D
RUN $UTILTY
REMOVE LOGICAL LB
ADD LOGICAL DM1:[l,11]LB
LOGINS
SEND ALL RSTS/E IS NOW ON THE AIR ...
EXIT
RUN $QUE
Q LP0:/DELETE/PRI:200=$STRTUP.LOG
EXIT
$RTS.CMD:
RUN $UTILTY
SEND KB0:Adding run-time systems
ADD RT 11
ADD RSX
ADD BP2COM
ADD BASIC2
ADD BASIC
ADD BAS4F
EXIT
$ANALYS. CMD:
RUN $UTILTY
SEND KB0:Running ANALYS
EXIT
RUN $ANALYS
[0.1JCRASH.SYS
[1,2]ANALYS.DMP
[ l,2]ERRCRS.FIL

Seq 17.7. 1 N
7 of 10

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK

$CLEAN.CMD:
RUN $UTILTY
SEND KB0:Cleaning Disks
EXIT

RUN $ONLCLN
DB 1 :
~C

RUN $ONLCLN
DB2:
AC
$MOUNT.CMD:
RUN $UTILTY
SEND KB0:Mounting Disks
MOUNT DB1: PACK1
UNLOCK DB1:
MOUNT DB2:PACK2
UNLOCK DB2:
EXIT

:j;TTY.CMD:
RUN $UTILTY
SEND KB0:Setting Terminal Characteristics
EXIT

RUN $TTYSET
KB16:;VT52;SPEED 2400
KB17: ;VT100;SPEED 4800;GAG
EXIT

$SPOOL. CMD:
RUN $UTILTY
SEND KB0:Starting Spoolers
EXIT

RUN $OPSER MLOG OPSER.LOG;ALL ~MCHA KB0: AMDETACH
$LOGIN
RUN $QUEMAN AMDETACH/PRIORITY:0
$LOGIN
RUN $SPOOL AMLP0:/HEAD:2
$LOGIN
RUN $BATCH MBA0:/ERROR:FATAL/NOQUEUE/NODELETE
$LOGIN
A

Seq 17.7. 1 N
8 of 10

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK
$CCL.CMD:
RUN $UTILTY
SEND KB0:Adding CCL's.
ceL ATT-ACH=$LOGIN.*;PRIV 30000
CCL ATP-K=$ATPK.*;PRIV 30000
CCL BCK-=$RMSBCK.TSK;0
CCL BPC-REF=$BPCREF.*;30000
CCL BYE-=$LOGOUT.*;PRIV 0
CCL CCL-=[0,1]DCL.DCL;PRIV 0
eCL CNV-=$RMSCNV.TSK;0
CCL DCL-=[0,l]DCL.DCL;PRIV 0
CCL DEF-=$RMSDEF.TSK;0
CCL DFN-=$RMSDFN.TSK;0
eCL DES-=$RMSDES.TSK;0
CCL DIS-MOUNT=$UMOUNT.*;PRIV 30000
eCL DI-RECTORY=$DIRECT.*;PRIV 30000
eCL DSP-=$RMSDSP.TSK;0
CCL EDT-=$EDT.TSK;0
CCL FIT-=$FIT.*;PRIV 30000
ceL HELLO-=$LOGIN.*;PRIV 0
CCL HELP-=$HELP.*;30000
CCL IFL-=$RMSIFL.TSK;0
CCL LBR-=$LBR.TSK;0
CCL LIBR-=$LIBR.SAV;8208
CCL LIN-K=$LINK.SAV;8208
CCL LOG-IN=$LOGIN.*;PRIV 0
CCL MACR-O=$MACRO.SAV;8216
CCL MAC-=$MAC.TSK;0
CCL MAK-E=$TECO.TEC;0
CCL MOU-NT=$UMOUNT.*;PRIV 30000
CCL MU-NG=$TECO.TEC;0
CCL PAT-=$PAT.TSK;0
ceL PIP-=$PIP.SAV;8208
ceL PL-EASE=$PLEASE.*;PRIV 30000
eCL QU-EUE=$QUE.*·PRIV 30000
CCL RST-=$RMSRST.TSK;PRIV 0
ceL SE-T=$TTYSET.*;PRIV 30000
ceL SRT-=$SORT.TSK;0
CCL SU-BMIT=$QUE.*;PRIV 30000
CCL S\/-ITCH=$SWITCH. *; PRIV 30000
CCL SY-STAT=$SYSTAT.*;PRIV 30000
CCL TE-CO=$TECO.TEC;0
eeL TKB-=$TKB.TSK;0
ceL TY-PE=$TYPE.TEC;8
ceL UT-ILTY=$UTILTY.*;30000
EXIT

Seq 17.7.1 N

9 of 10

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK

Seq 17.7.1 N
10 of 10

OTHER FEATURES
By specifying a log file and KB: as your input file, you can make a copy of
interactive dialogue to queue to the line printer, etc. Note that ATPK will
not be completely transparent in such a session.
Any line typed at the
keyboard will not be sent to the PK until the next time the controlled job
enters a keyboard input wait state.
When inputting from the terminal, CTRL/Z's get passed on through to the
controlled job.
A CTRL/C at any time will cause the controlled job to be
killed, the log file closed, and ATPK to exit. A CTRL/C may be sent to the
job by typing uparrow-C.
INSTALLING ATPK AS A CCL COMMAND
The following sequence will install the CCL commands "ATPK" and "@" to run the
ATPK program. Either or both of the commands may be installed.
RUN $UTILTY<cr>
<UTILTY's header line>
HCCL ATP-K=[1,2JATPK.*;PRIV 30000<cr>
HCCL @-=[1,2JATPK.*;PRIV 30000<cr>
H~Z

(This assumes that ATPK is located on SY:[1,2J. Note that the DCL LINK command
assumes this location.)
ALLOWING ACCESS TO ATPK BY NON-PRIVILEGED USERS
ATPK is installed on the system with a protection code of <252>.
If
non-privileged users are to be allowed to run ATPK, it must be renamed to have
a protection code of <232> after the system installation is complete and after
any patches have been applied to ATPK and it is re-compiled.
SUPPORT POLICY FOR ATPK
ATPK is supported only as a part of the BUILD procedure.
DIGITAL makes no
commitment, expressed or implied, to support ATPK as an indirect command file
processor, or to supply an indirect command file processor in future releases
of RSTS/E that is compatible with the present version of ATPK.
If you experience problems when using ATPK as an indirect command file
processor, please submit an FYI-type (Priority 5) Software Performance Report
(SPR). While DIGITAL makes no commitment to fix problems reported with ATPK
as an indirect command file processor, we would like to know about any
problems that you encounter.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK

Seq 17.7.2 F
1 of 2

ALLOWING ATPK TO DETACH FOR NON-PRIVILEGED USERS - ATPK FEATURE PATCH
At some installations it may be desirable to allow non-privileged users to run
ATPK detached as a "mini batch processor", even though running a detached job
is usually a privileged operation under RSTS/E.
This optional patch will
allow ATPK to detach for any user if the IDET switch is specified at the end
of ATPK's startup command, or if the $DETACH command is encountered in the
command file.
PROCEDURE:
1.

assumes

that

BASIC-PLUS

your

system default

If you are using CSPCOM or BASIC-PLUS-2, refer to Section 5.4 of the
RSTS/E V7.2 Maintenance Notebook for the correct procedure to compile the
program.
If you are using BASIC~PLUS-2. this program must be task built against the
BP2COM run-time system,
2.

To apply the patch manually, perform the following RSTS/E system commands.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
Automated Patching Facility Package
ATPK

Seq 17.7.2 F
2 of 2

RUN $CPATCH(cr)
(CPATCH's header line)
File to patch - ATPK.BAS=ATPK.BAS(cr)
U[logfile=]KB:/CS:62461(cr)
*H/2!/V(cr)
2!
PROGRAM
ATPK. BAS
*H/3000(tab)/V(cr)
3000
! &
*G/IF DETACHED% IV(cr)
\ RETURN IF DETACHED% OR NOT PRIV% &
*I/!/V(cr)
\ RETURN IF DETACHED% lOR NOT PRIV% &
*EX(cr)
Patch from KB:[P,PN]CPATCH.CMD complete
(I" Z

File to patch -

Ready
3.

Use this procedure if your system default run-time system is BASIC-PLUS;
otherwise, refer to Section 5.4 of the RSTS/E V7.2 Maintenance Notebook
for the correct procedure to compile the program.
To re-compile the program and re-enter it into the system library, type
the following RSTS/E commands. Note the protection code of (232) to allow
non-privileged users to run ATPK.
OLD ATPK(cr)
Ready
COMPILE SY0:$ATPK(232)(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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK

Seq 17.7.3 F
1 of 2

LIMITING THE USE OF THE $LOGIN COMMAND - ATPK FEATURE PATCH
The $LOGIN command of ATPK provides an easy way for a privileged user to log
in under any account at any keyboard. While the $LOGIN command does not
compromise normal RSTS/E security (it is available only to privileged users),
it may be desirable to disable this feature at installations that have
implemented their own security measures.
This optional patch will cause ATPK to ignore any keyboard or account number
specification used with the $LOGIN command. The $LOGINcommand may still be
used to log a privileged user back in under his or her own account at the
pseudo keyboard after the job controlled by ATPK has detached or terminated.
PROCEDURE:
1.

assumes

that

BASIC-PLUS

your

system default

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
Automated Patching Facility Package
ATPK

Seq 17.7.3 F
2 of 2

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - ATPK.BAS=ATPK.BAS<cr>
#[logfile=]KB:/CS:28893<cr>
*H/2!/V<cr>
2!
PROGRAM
ATPK.BAS
*H/2900<tab>/V<cr>
2900
! &
*G/! \!V<cr>
!\ T0%=0% &
*-2JDV<cr>
\ T0%=0% &
*EX<cr>
Patch from KB:[P,PN]CPATCH.CMD complete
#"Z

File to patch -

Ready
3.

Use this procedure if your system default run-time system is BASIC-PLUS;
otherwise, refer to Section 5.4 of the RSTS/E V7.2 Maintenance Notebook
for the correct procedure to compile the program.
To re-compile the program and re-enter it into the system library, type
the following RSTS/E commands. Specify a protection code of <232> if ATPK
is to be runnable by non-privileged users on your system.
OLD ATPK<cr>
Ready
COMPILE SY0:$ATPK<252><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
public structure.

may

now

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 20. 1 • 1 N

DCL
Package Notes

1 of 1

FILE SPECIFICATIONS IN DCL
The rules about file specifications in DeL are slightly more restrictive
elsewhere in RSTS/E.
The special PPN character "!" does not work in DCL.
used as the comment delimiter.

than

The exclamation point

The special PPN characters !!@II, "%", "&", and "II" 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.
to designate the system library [1,2J.

It will continue

The traditional RSTS/E file specification switches 1 MODE , IS1ZE, IPOSIT10N,
ICLUSTERS1ZE, and IRONLY cannot be used in DCL. Many of the same features are
available through DeL, but you must use DCL notation.
Protection codes in
angle brackets ("<nn>") cannot be used in DeL. The DCL syntax for protection
codes is "/PROTECT10N:nn".
Parentheses (110") cannot be used to delimit the project-programmer number of
a file in DCL.
Brackets (II[JII) must be used instead. Parentheses are
reserved.
The single-character wildcard "?" works in DCL, but i t is unsupported.
have a different meaning in the future.

It may

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 20.1.2 N

RSTS/E V7.2
DCL
Package Notes

1 of 2

DCL CAN TRANSLATE LOGICAL DEVICE NAMES TWICE
PROBLEM:
DCL has two related problems in the translation of device names.
The system
can translate a logical device name twice, and can translate a name once even
if you precede it with an underscore.
The following example shows double translation.
$ ASSIGN

DB: FOO:

$ ASSIGN

NL: DB:

$ DIR FOO:
?Device not file-structured - file NL:?????????
$

What happens in the above example is that the system correctly translates the
logical name "FOO:" to "DB:", and then incorrectly retranslates the name "DB:"
to II NL:" .
The following example shows the underscore being ignored.
$ ASSIGN

NL: DB:

$ DIR DB:
?Device not file-structured - file NL:?????????
$

These problems occur only with the following commands.
APPEND
COPY
DIRECTORY
FORTRAN/FOR
LINK

MACRO/RT11
RENAME
SET PROTECTION

TYPE

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DeL

Seq 20.1.2 N

Package Notes

2 of 2

The problems occur only
specify a remote file.

with

local

operations;

they do not occur if you

SOLUTION:
You can work around the double-translation problem. Don't use the name of a
physical device as a logical device name. All physical device names consist
of two letters or of two letters followed by a number.
If you avoid using
these forms when you assign logical names, double translation will not occur.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
Package Notes

Seq 20.1.3 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 System Generation Manual and the System
Manager's Guide.
The DCL LINK command provides a simple way of linking programs. It lets you
link programs in two RTll-based languages (FORTRAN-IV and MACRO-ll) and five
RSX-ll-based languages (BASIC-PLUS-2, COBOL-81, DIBOL,
FORTRAN-77,
and
FORTRAN-lV-PLUS). 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
wish to change this default if your installation does not have BASIC-PLUS-2,
or if you prefer that a different language be the default. Refer to article
Seq 20.2.8 F if you wish to change the default language to FORTRAN IV or RTll;
Refer to article Seq 20.2.9 F if you wish to change the default language to
DIBOL, COBOL-81, FORTRAN-77, or FORTRAN-lV-PLUS.
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 when you install DCL.
Language to Disable

File to Delete

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

[1,2JPRELIN (.BAC or .TSK)
LB:BP2.LNK
(none)
LB:DIB.LNK
(none)
LB:F77.LNK
LB:F4P.LNK
(none)

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
DCL
Package Notes

Seq 20.1.3 N
2 of 7

Requirements for RTll-based Languages
MACRO-ll
Location

Required File

When Installed

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

LINK.SAV
SYSLIB.OBJ

RSTS/E System Generation
RSTS/E System Generation

LINK/RTll is automatically disabled if LINK.SAV is not present. If LINK.SAV
is not present and a user types LINK/RTll, the system will display the
message n?Command not available. n
FORTRAN-IV V2.5
Location

Required File

When Installed

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

LINK.SAV
SYSLIB.OBJ
FORLIB.OBJ

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

Also:
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.
LINK/FOR is automatically disabled if LINK.SAV is not present. If LINK.SAV
is not present and a user types LINK/RTll, the system will display the
message n?Command not available. n

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 20.1.3 N

DCL
Package Notes

3 of 7

Requirements for RSX-based Languages
All of the RSX-based languages have certain linking requirements in
These follow.
Location

Required File

When Installed

--------

-------------

--------------

SY:[1,2]

PRELIN
(.BAC or .TSK)
TKB.TSK
RMSRES.TSK
RMSRES.STB
RMSRES.LIB
RMSLIB.OLB
SYSLIB.OLB
RMSRLX.ODL

RSTS/E DCL Installation

SY:[1,2]
LB:
LB:
SY:[0,1] (usually)
LB:
LB:
LB:

common.

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

Also:
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
(This is done automatically during the RSX installation.)
4. Install the RMS package.

name

Select the RMSRES resident library.

5. ADD the RMSRES resident library.
6. The PRELIN (pre-link) program has a protection code of 232.

LB:.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 20.1.3 N

RSTS/E V7.2
DCL
Package Notes

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. These follow.
Location
LB:
LB:
SY:[0,1] (usually)
LB:
LB:
LB:

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

When Installed

--------------

FMS Installation
FMS Installation
FMS Installation
FMS Installation
FMS Installation
FMS Installation

Also:
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-lV-PLUS and FORTRAN-77, and HLLCOB.OBJ
for COBOL-81. They are installed during FMS Installation.
BASIC-PLUS-2 V1.6
Location

Required File

When Installed

LB:
LB:
LB:
SY:[0,1] (usually)
LB:
LB:
LB:

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

RSTS/E DCL 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

Also:
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 V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
Package Notes

Seq 20.1.3 N
5 of 7

COBOL-81
Location

Required File

When Installed

(If you select CIS (Commercial Instruction Set) when you
install COBOL-81:)
LB:
C81CIS.TSK
COBOL-81 Installation
COBOL-81 Installation
C81CIS.STB
LB:
SY:[0,lJ (usually) C81CIS.LIB
COBOL-81 Installation
(If you select NONCIS when you install COBOL-81:)
COBOL-81 Installation
LB:
C81LIB.TSK
COBOL-81 Installation
C81LIB.STB
LB:
SY:[0,1] (usually) C81LIB.LIB
COBOL-81 Installation

(In either case:)
SY:[1,2J
SY:[1,2]
SY:[l,2]

COBOL-8l Installation
C8l0DL. TSK
RSTS/E Standard CUSP Build
ATPK
(.BAC or . TSK)
RSTS/E System Generation
PIP.SAV

Also:
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 252, which is satisfactory.
2. ADD the COBOL resident library, C81CIS or C81LIB.
If [1,2]PIP.SAV or [1,2JC810DL.TSK is not present, the LINK command will
fail with "?Can't find file or account". If [l,2]ATPK is not present, the
LINK command will fail with "?Unex pec ted error in PRELIN
? Can't find
file or account".

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
Package Notes

Seq 20.1.3 N
6 of 7

DIBOL V4.5
Location

Required File

When Installed

LB:
LB:
LB:
SY:[0,1] (usually)
LB:

DIB.LNK
DBRRES.TSK
DBRRES.STB
DBRRES.LIB
DBRLIB.OLB

RSTS/E DCL Installation
DIBOL Installation
DIBOL Installation
DIBOL Installation
DIBOL Installation

Also:
1. When you install the DIBOL V4.5 compiler select the RMS 1/0 package
(rather than DMS).
FORTRAN-77 V4.0
Location

Required File

When Installed

LB:
LB:
LB:

F77.LNK
F4POTS.OLB
RMS11M.ODL

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

Also:
1. When you install the FORTRAN-77
package (rather than FCS).

V4.0 compiler select the RMS 1/0

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:RMS11M.ODL.
"LB:" .

Change all occurrences of "LB:[1,1]" to

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq20.1.3N

RSTS/E V7.2
DCL
Package Notes

7 of 7

FORTRAN-lV-PLUS V3.0
Location

Required File

When Installed

LB:
LB:
LB:

F4P.LNK
F4POTS.OLB
RMS11M .ODL

RSTS/E DCL Installation
FORTRAN-lV-PLUS Installation
FORTRAN-lV-PLUS Installation

Also:
1. When you install the FORTRAN-lV-PLUS
package (rather than FCS).

compiler select the RMS 1/0

2. When you install FORTRAN-lV-PLUS you have the option of either
including the FORTRAN library routines in SYSLIB.OLB or putting them
separately in F4POTS.OLB. For LINK/F4P to work properly, select
F4POTS.OLB.
3. Edit the file LB:RMS11M.ODL.
"LB:" .

Change all occurrences of "LB:[1, 1J" to

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
Package Notes

Seq 20.1.4 N
1 of 4

SOME DIFFERENCES BETWEEN DCL AND BASIC-PLUS
This section is for the new DCL user who is familiar with the command
environment of BASIC-PLUS (or of the RT11 or RSX run-time systems). It warns
you of some of the more common pitfalls.
In DCL, the input file specification goes first, and the output file
specification goes second.
They are separated by a space. You cannot type
embedded spaces within a file specification. Thus instead of:
PIP NEW.FIL=OLD.FIL
you would type:
$ COpy OLD.FIL NEW.FIL

DCL does not allow protection codes in angle brackets, nor the standard RSTS/E
file specification switches IMODE, ISIZE, ICLUSTERSIZE, IPOSITION, and IRONLY.
However, there are DCL equivalents for many of these. The IPROTECTION switch
is accepted both by BASIC-PLUS and by several DCL commands.
There are no DCL commands corresponding to ATTACH and HELLO. If you want to
use the ATTACH and HELLO commands while in the DCL environment, you must
install them as CCL commands.
Several DCL commands have
commands, but different
contrasts these commands:

the same names as familiar BASIC-PLUS or CCL
meanings or different syntax. The following list

1. APPEND
DCL:
Appends the contents of one file to the end of
files may contain text or anything else.

another

file.

The

BASIC-PLUS:
Merges the contents of a previously saved BASIC-PLUS source program
into a BASIC-PLUS program currently in memory.
(Use the IAPPEND
qualifier of PIP to append one file to another.)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
Package Notes

Seq 20.1.4 N
2 of 4

2. ASSIGN
DCL:
Establishes a logical name for a device or PPN. The syntax is
"ASSIGN device: logical", with a space required before the logical
name. (In DCL, the ALLOCATE command reserves a device for your use,
and the SET PROTECTION/DEFAULT command
changes
the
default
protection code for files you create.)
BASIC-PLUS:
Establishes a logical name for a device or PPN; reserves a device
for your use only; changes the default protection code for files
you create;
or associates a PPN with the @ character. The syntax
to assign a logical name is "ASSIGN device:logical", with no space
required before the logical name.

3. DISMOUNT
DCL:
The syntax is "DISMOUNT device: [labelJ", with
between the device name and the optional label.

a space required

CCL:
The syntax is "DISMOUNT device: [label]", with no space required
before the optional label. (The CCL and DCL commands also accept
different qualifiers.)
4. MOUNT
DCL:
The syntax is "MOUNT device: label", with a space
the device name and the label.

required

between

CCL:
The syntax is "MOUNT device:label", with no space required before
(The CCL and DCL commands also accept different
the label.
qualifiers. )

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
Package Notes

Seq 2fJ.1.4 N
3 of 4

5. PRINT
DCL;
Queues a file for printing.
BASIC-PLUS:
Displays the value of a variable, or outputs it into a file.
the QUE program to queue a file for printing.)

(Use

6. RENAME

DeL:
Changes the name and/or
"RENAME oldname newname".

type

file.

The

syntax

BASIC-PLUS:
Changes the name of the program currently in memory. (Use the
/RENAME qualifier of PIP to change to name and/or type of a file,)

7. SET
DCL:
This has several options:
and SET QUEUE.

SET HOST, SET TERMINAL,

SET

PROTECTION,

BASIC-PLUS:
Sets terminal characteristics.
8. SUBMIT

DCL and CCL:
Submits a file for batch processing. The syntax of the DCL and CCL
However, the qualifiers are
commands is essentially the same.
different.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
DCL
Package Notes

Seq 20.1.4 N
4 of 4

NOTE
In DCL, you can continue a command line by ending it with a hyphen.
example (underscored text is what you type):

For

$ COPY A.A, -

Continue:
Continue:
To:

B.B,C.C
D.D

This can surprise you if you type the CCL command "SYSTATI-" while in the
command environment.

DCL

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS

Seq 20.2.1 F
1 of 2

RUNNING DCL AT INCREASED PRIORITY - DCL.RTS FEATURE PATCH
This patch might significantly improve the speed with
responds to user input typed at the DCL command level.

which

your

system

This patch causes DCL to run at a CPU priority 4 greater than other programs.
Since the normal job priority is -8, DCL will generally run at a priority of
-4.
As soon as DCL invokes any CUSP or user program, the job's priority will
drop by 4, to its normal level. Without this patch, DCL runs at the same
priority as other programs.
This will cause RSTS/E to give preferential treatment to jobs at the DCL
command level. DCL will prompt them and issue error messages to them faster
than it otherwise would. Whether the improvement is significant depends on
how heavily your system is loaded.
This patch will also slightly degrade the speed of everything else on the
system that is running at a lower priority. At most RSTS installations,
nearly everything runs at a lower priority. Logged-out jobs and ERRCPY, the
error logger, run at priority 0, but most other things generally run at
priority -8. Since DCL consumes little CPU time, the effect on other jobs is
slight at most installations.
Try this patch and see how it affects performance.
We expect that
installations will find that the net effect of this patch is beneficial.

most

The patching procedure detailed below will cause DCL to run at a priority 4
greater than other programs.
PROCEDURE:
1.

This is a feature patch to the DCL run-time system.
in any DCL run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

can

It may

installed

using

(DCL run-time system name)

installed
the

PATCH

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS

Seq 20.2.1 F
2 of 2

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

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version" A"
or later.
4.

The patch is as follows:
Base address? •. PRIO
Offset address? 0
Offset Old
Base
?????? 000000 000000
?????? 000000
000
?????? 000001
000

New?
? \
? -1
? ~C

(up-arrowl C to ex it; CTRLI 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 ADDed, execute the following commands:
RUN $UTILTY<cr>
<UTILTY's header line>
"UNLOAD DCL<cr>
IIEXIT<cr>

(DCL run-time system name)

system

(DCL run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 20.2.2 F

RSTS/E V7.2
DCL
DCL.RTS

1 of 2

CHANGING DCL BASIC COMMAND DEFAULT FROM IBPLUS TO IBP2 ~ DCL.HTS FEATURE PATCH
PROBLEM:
The DCL BASIC command switches the user into BASIC-PLUS if IBPLUS is
specified, or into BASIC-PLUS-2 if IBP2 is specified.
If neither is
specified, the command switches the user into BASIC-PLUS.
Your installation
may find it convenient to make BASIC-PLUS-2 the default.
SOLUTION:
The patching procedure detailed below allows you to change DCLis
the BASIC command from IBPLUS to IBP2.

default

for

PROCEDURE:
1.

This is a feature patch to the DeL run-time system.
in any DCL run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

can

It may

installed

using

installed
the

PATCH

(DCL run-time system name)

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

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version" A"
or later.
4.

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

New?
? BP2$Q
? AC

(up~arrow/C

to exit;CTRL/C for INIT)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL. RTS
5.

Seq 20.2.2 F
2 of 2

(DCL run-time system name)

system

(DCL run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS

Seq 20.2.3 F
1 of 2

CHANGING BASIC-PLUS KBM NAME IN DCL - DCL.RTS FEATURE PATCH
PROBLEM:
DCL assumes that the keyboard monitor for BASIC-PLUS is called BASIC.
Your
installation may have installed BASIC-PLUS under a different name, such as
BAS4F. If so, you must patch DCL so that the BASIC/BPLUS command switches to
the correct keyboard monitor.
SOLUTION:
The patching procedure detailed below allows you to change
BASIC-PLUS keyboard monitor invoked by DCL.

the

name

the

PROCEDURE:
1.

This is a feature patch to the DCL run-time system.
in any DCL run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

can

installed

using

installed
the

PATCH

(DCL run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0,1JDCL.RTS
File found in account [0,1J

It may

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed.
Specifically, specify the name of
your BASIC-PLUS keyboard monitor. Note that the name should
be padded with 0's if it is less than 6 characters long.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS
4.

2 of 2

The patch is as follows:
Base address? ... BPL
Offset address? 0
Offset Old
Base
?????? 000000 041006
?????? 000000
006
?????? 000001
102
?????? 000002
101
?????? 000003
123
?????? 000004
111
?????? 000005
103
?????? 000006
000
?????? 000007
???

Seq 20.2.3 F

New?
? \
? Of>
? 'B
? 'A
? 'S
? 'I
? 'C
? 0
? ,..c

(no change; verify only)

(pad with 0's, if necessary)
(up-arrow/C to exit;CTRL/C for INIT)

(DCL run-time system name)

system

(DCL run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 20.2.4 F

RSTS/E V7.2
DCL
DCL.RTS

1 of 2

CHANGING BASIC-PLUS-2 KBM NAME IN DCL - DCL.RTS FEATURE PATCH
PROBLEM:
DCL assumes that the keyboard monitor for BASIC-PLUS-2 is called BP2COM. Your
installation may have installed BP2COM under a different name. If so, you
must patch DCL so that the BASIC/BP2 command switches to the correct keyboard
monitor.
SOLUTION:
The patching procedure detailed below allows you to change
BASIC-PLUS-2 keyboard monitor invoked by DCL.

the

name

the

PROCEDURE:
1.

This is a feature patch to the DCL run-time system.
in any DCL run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

can

installed

using

installed
the

PATCH

(DCL run-time system name)

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

It may

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed. Specifically, specify the name of
your BASIC-PLUS-2 keyboard monitor.
Note that the name
should be padded with 0's if it is less than 6 characters
long.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS
4.

2 of 2

The patch is as follows:
Base address? ... BP2
Offset address? 0
Offset Old
Base
?????? 000000
006
?????? 000001
102
?????? 000002
120
?????? 000003
062
?????? 000004
103
?????? 000005
117
?????? 000006
115
?????? 000007
???

Seq 20.2.4 F

New?
? <If>
? 'B
? 'P
? '2
? 'C

(no change; verify only)

? '0

? 'M
? "c

(pad with 0's, if necessary)
(up-arrow/C to exit;CTRL/C for INIT)

(DCL run-time system name)

system

(DCL run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
DCL
DCL. RTS

Seq 20.2.5 F
1 of 2

CHANGING DCL MACRO COMMAND DEFAULT FROM IRSX11 TO IRT11
- DCL.RTS FEATURE PATCH
PROBLEM:
The DCL MACRO command can invoke either the RT11 MACRO assembler or the
RSX-11M MACRO assembler.
If the user specifies MACRO/RT11 , then the RT11
MACRO assembler is invoked. If the user specifies MACRO/RSX11 , then the
RSX-11M MACRO assembler is invoked.

IRSX11 is the default.
If the user does not specify a assembler, then the
RSX-11M MACRO assembler is invoked.
Your installation may find it
default .

convenient

make

the

RT11

assembler

the

SOLUTION:
The patching procedure detailed below allows you to change DCL's default for
the MACRO command from IRSX11 to IRT11. With this patch installed, the MACRO
command will invoke the RT11 assembler if the user does not specify an
assembler.
PROCEDURE:
1.

This is a feature patch to the DCL run-time system.
in any DCL run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

can

installed

using

installed
the

PATCH

(DCL run-time system name)

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

It may

the

on-line

patching

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

HSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL. RTS

Seq 20.2.5 F
2 of 2

This patch is contained in a patch file appearing in patch kit version "A"
or later.
4.

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

New?
? HT 11 $Q
?

(up-arrowl C to ex it; CTRL! C for INIT)

(DCL run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run-time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr)
<UTILTY's header line>
"LOAD DCL/STAY/ADDR:nnn<cr>
IIEXIT<cr>
Ready

system

(DeL run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS

Seq 20.2.6 F
1 of 2

CHANGING DCL FORTRAN COMMAND DEFAULT TO FORTRAN IV - DCL.RTS FEATURE PATCH
PROBLEM:
The FORTRAN command can invoke either the PDP-11 FORTRAN-IV compiler or the
PDP-11
FORTRAN-lV-PLUS or FORTRAN-77 compiler.
If the user specifies
FORTRAN/FOR, then the FORTRAN-IV compiler is invoked (if your installation has
it). If the user specifies FORTRAN/F4P, then the FORTRAN-lV-PLUS compiler is
invoked (if your installation has it). If the user specifies FORTRAN/F77,
then the FORTRAN-77 compiler is invoked (if your installation has it).

IF77 is the default.
If the user does not specify a compiler, then the
not
have
FORTRAN-77 compiler is invoked.
If your installation does
FORTRAN-77, an error message is printed.
Your installation may find it convenient to change the default to IFOR.
SOLUTION:
The patching procedure detailed below allows you to make the
invoke FORTRAN-IV when the user does not specify a compiler.
Seq 20.2.7 F if you wish to make IF4P the default.

FORTRAN command
Refer to article

PROCEDURE:
1.

This is a feature patch to the DCL run-time system.
in any DCL run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? DCL. RTS

can

installed

using

installed
the

PATCH

(DCL run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0,1JDCL.RTS
File found in account [0,1J

It may

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS
4.

Seq 20.2.6 F
2 of 2

The patch is as follows:
Base address? .. FORF
Offset address? 0
Base
Offset Old
?????? 000000 000001
?????? 000002 000000
Offset address? Z
Base address? .. FORL
Offset address? 0
Base
Offset Old
?????? 000000 ??????
?????? 000002 177777

New?
? FOR
? "z

(CTRLlZ for new offset)
(CTRL!Z for new base)

New?
? FOR$Q
? AC

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

If the above patch was installed using ONLPAT, i t

next time the run-time system is reloaded.
been ADDed, execute the following commands:
RUN $UTILTY<cr>
<UTILTY's header line>
"UNLOAD DCL<cr)
IIEXIT<cr>

will take effect the
If the run-time system has

(DeL run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run-time
ADDe9 with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
IILOAD DCL/STAY!ADDR:nnn<cr>
tlEXIT<cr>
Ready

system

(DCL run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS

Seq 20.2.7 F
1 of 2

CHANGING DeL FORTRAN COMMAND DEFAULT TO FORTRAN-IV-PLUS
~

DCL.RTS FEATURE PATCH

PROBLEM:
The FORTRAN command can invoke either the PDP-l1 FORTRAN-IV compiler, the
PDP-l1 FORTRAN-lV-PLUS compiler, or the PDP-l1 FORTRAN-77 compiler. If the
user specifies FORTRAN/FOR, then the FORTRAN-IV compiler is invoked (if your
installation
has
it).
If
the user specifies FORTRAN/F4P, then the
FORTRAN-lV-PLUS compiler is invoked (if your installation has it).
If the
user specifies FORTRAN/F77 , then the FORTRAN-77 compiler is invoked (if your
installation has it).

IF77 is the default. If the user does not specify a compiler.
FORTRAN-77
compiler
is invoked.
If your installation does
FORTRAN-77. an error message is printed.

then the
not have

Your installation may find it convenient to change the default to IF4P,
SOLUTION:
The patching procedure detailed below allows you to make the FORTRAN command
invoke FORTRAN-lV-PLUS when the user does not specify a compiler. Refer to
article Seq 20.2.6 F if you wish to make FORTRAN IV the default.
PROCEDURE:
1.

This is a feature patch to the DCL run-time system,
in any DCL run-time system.

The patch described in Step 4 below
option of INIT,SYS:
Option: PATCH
File to patch? DCL.RTS

can

installed

using

installed
the

PATCH

(DCL run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr)
File to patch? [0,1]DCL.RTS
File found in account [0,lJ

It may

the

on-line

patching

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

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 20.2.7 F

RSTS/E V7.2
DCL
DCL.RTS

2 of 2

This patch is contained in a patch file appearing in patch kit version" A"
or later.

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

New?
? F4P$Q
? AC

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

(DCL run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run-time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY(cr>
<UTILTY s header line>
flLOAD DCL/STAY/ADDR:nnn(cr>
flEXIT<cr>
Ready

system

(DCL run-time system name)

had

been

RSTS/E

V7.2 Maintenance Notebook, June 1982

Seq 20.2.8 F

RSTSiE V7. 2
DCL
DCL.RTS

1 of 2

CHANGING DEFAULT LANGUAGE FOR LINK TO FORTRAN IV OR RT11 MACRO
- DCL.RTS FEATURE PATCH
PROBLEM:
The DCL LINK command can link programs written in any of several languages.
The LINK command accepts a qualifier that specifies what language the program
is written in. If the user does not specify such a qualifier, the LINK
command assumes that the program is written in BASIC-PLUS-2 (as if the user
had typed IBP2).
Your installation may find it convenient to change the default, especially if
you do not have BASIC-PLUS-2. You can change the default to FORTRAN-IV, RT11
MACRO, DIBOL, FORTRAN-77, FORTRAN-lV-PLUS, or COBOL-81.
SOLUTION:
The patching procedure detailed allows you to make the LINK command default to
IFOR or IRT11 when the user does not specify a language. Refer to article
Seq 20.2.9 F if you wish to
make
DIBOL,
COBOL-81,
FORTRAN-77,
or
FORTRAN-lV-PLUS the default.
PROCEDURE:
1.

This is a feature patch to the DCL run-time system.
in any DCL run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

can

installed

using

installed
the

PATCH

(DCL run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0,1JDCL.RTS
File found in account [0,lJ

It may

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E

V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL.RTS

Seq 20.2.8 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.

The patch which follows changes the default language used by the DCL LINK
command to FORTRAN-IV.
To default to RT11 MACRO, substitute RT11$Q for
FOR$Q:
Base address? .. LINL
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 00000~ 177777
Offset address? AZ
Base address? .• LINF
Offset address? 0
Offset Old
Base
?????? 000000 000002
?????? 000002 000004

? FOR$Q
? Z
A

(or use RT11$Q)
(CTRL/Z for new offset)
(CTRL/Z for new base)

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

(DCL run-time system name)

system

(DCL run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2

Seq 20.2.9 F

DCL
DCL. RTS

1 of 2

CHANGING DEFAULT LANGUAGE FOR LINK TO DIBOL, COBOL-81,
FORTRAN-77, OR FORTRAN-lV-PLUS - DCL.RTS FEATURE PATCH
PROBLEM:
The DCL LINK command can link programs written in any of several languages.
The LINK command accepts a qualifier that specifies what language the program
is written in. If the user does not specify such a qualifier, the LINK
command assumes that the program is written in BASIC-PLUS-2 (as if the user
had typed IBP2).
Your installation may find it convenient to change the default, especially if
you do not have BASIC-PLUS-2. You can change the default to FORTRAN-IV, RT11
MACRO, DIBOL, FORTRAN-77, FORTRAN-lV-PLUS, or COBOL-81.
SOLUTION:
The patching procedure detailed allows you to make the LINK command default to
Refer to
article Seq 20.2.8 F if you wish to make FORTRAN IV OR RT11 MACRO the default.

IC81, IDIB, IF77, OR IF4P when the user does not specify a language.

PROCEDURE:
1.

This is a feature patch to the DCL run-time system.
in any DCL run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? DCL.RTS

can

installed

using

installed
the

PATCH

(DCL run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0,1JDCL.RTS
File found in account [0,1J

It may

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
DCL
DCL. RTS

Seq 20.2.9 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.

The patch which follows changes the defaul t language used by the DCL LINK
command to COBOL-81. To default to DIBOL, substitute DIB$Q for C81$Q; to
default to FORTRAN~77,substitute F77$Q for C81$Q;
to
default
to
FORTRAN-IV~PLUS.substitute F4P$Q for C81$Q;
Base address? .. LINL
Offset address? 0
Offset Old
Base
?????? 000000 ??????
?????? 000002 177777

New?
? C81$Q
? AC

(or use DIB$Q, F77$Q. or F4P$Q)
(up-arrow/C to exit;CTRL/C for INIT)

(DCL run-time system name)

system

(DeL run-time system name)

had

been

RSTS/E V7,2 Maintenance Notebook, June 1982

RSTS/E V7.2
DeL

Seq 20.4.1 F

PRELIN

1 of 3

ENABLE COBOL-81 AND FMS RESIDENT LIBRARIES TO CLUSTER - PRELIN FEATURE PATCH
PROBLEM:
When you use the DCL LINK command to link a COBOL-81 program that uses FMS
(LINK/C81/FMS) , the command will fail with "?MEMORY ALLOCATION CONFLICT" if
you selected clustering when you built the FMS resident library.
Clustering
enables the FMS and COBOL-81 resident libraries to share the same range of
addresses. This makes 4K words of additional memory available to COBOL-81
programs
that use FMS.
For information on clustering, refer to the
installation instructions for FMS.
SOLUTION:
The patching procedure detailed below will enable the FMS and COBOL-81
resident libraries to cluster, provided that you select clustering when you
build the FMS resident library.
PROCEDURE:
1.

For purposes of this discussion, we will assume that the program to be
patched is located in your privileged account on the public disk
structure. If this is not the case, replace all program references with
suitable text according to the requirements of your installation.
We assume the executable version of the program will be stored in the
System Library Account ($). If this is not the case, replace references
to $ in Step 3 below with the appropriate package or library account.
The procedure below
run-time system,

assumes

that

BASIC-PLUS

your

system default

under

the

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 20.4. 1 F

RSTS/E V7.2
DeL
PRELIN
2.

2 of 3

RUN $CPATCH<cr>
<CPATCH's header line>
File to patch - PRELIN.BAS=PRELIN.BAS<cr>
#[logfile=]KB:/CS:36934<cr>
*H/2!/V<cr>
PRELIN.BAS
2!
PROGRAM
*H/1020<tab>/V<cr>
1020
PAT.CLSTR% = FALSE% &
*KI<cr>
PAT.CLSTR% = TRUE% &<cr>
<esc> *V <cr >
! BY DEFAULT DON'T CLUSTER FMS AND COBOL LIBRARIES &
*EX<cr>
Patch from _KB:[P,PNJCPATCH.CMD complete
flA Z
File to patch - "z
Ready

Use this procedure if your system default run-time system is BASIC-PLUS;
otherwise, refer to Section 5.4 of the RSTS/E V7.2 Maintenance Notebook
for the correct procedure to compile the program.
To re-compile the program and re-enter it into the
the following RSTS/E commands.
OLD PRELIN <cr >
Ready
COMPILE $PRELIN<232><cr>
Ready

system

library,

type

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 20.4.1 F

DeL
PRELIN

3 of 3

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 should now be
public structure.

removed

from

the

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
RSX Emulator and Utilities Package
Package Notes

Seq 21. 1 .1 N
1 of

USING RTSODT FOR DEBUGGING RUN-TIME SYSTEMS
A version of ODT is provided on the RSTS/E V7.2 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 RT11 run-time system.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
RSX Emulator and utilities Package
Package Notes

Seq 21.1.2 N
1 of 4

NOTES ON WRITING KEYBOARD MONITORS
A keyboard monitor is a program which accepts input from a job's "console"
terminal or "keyboard", and takes action on the input (called "commands", or
"keyboard monitor commands"). The result of a command may be the execution of
a program, such as the BASIC-PLUS "RUN" command, or a CeL command. A keyboard
monitor command may merely cause a change in the state of the job, such as the
allocation of a device to the job, or the definition of a user logical name.
Every job on a RSTS/E system must have a default run-time system, and every
run-time system which can be a job's default run-time system must have a
keyboard monitor. Whereas run-time systems are generally difficult to write,
and are normally written in MACRO-11, keyboard monitors are relatively easy to
write, and in theory may be written in any programming language.
A "feature" patch of the RSX run-time system, as described in article
Seq 21.3.5 F, provides a way for RSTS/E system programmers to implement their
own keyboard monitors without having to learn the mysteries of run-time
systems. However, some guidelines and precautions must be kept in mind.
First, let us examine some of the reasons why system programmers may
write their own keyboard monitors.
o

want

Change the user interface
RSTS first came into existence at a time when most terminals were Model 33
Teletypes (R) or equivalents, and video display terminals were rare. NOW,
several years later, many RSTS/E systems may not have any hardcopy
terminals other than the system console terminal.
Many commercial
applications using video display terminals are forms or menu driven.
The
standard RSTS/E keyboard monitors do not, and perhaps cannot, take
advantage of video terminal features.

Change the command set
RSTS/E itself has a very limited command set that is shared by its various
keyboard monitors. BASIC-PLUS has a somewhat fuller set of commands, but
some of these are not relevant to someone not programming in BASIC-PLUS.
DCL provides a rich command set, but it might not be appropriate for your
system. Extending or changing the command set may be done through the use
of CCL commands, but another way is to write a keyboard monitor.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
Package Notes
o

Seq 21.1.2 N

2 of 4

Many users of RSTS/E systems are non-programmers and they do not need
access to the full capabilities of RSTS/E. Limiting what these users can
do may actually help them. They do not have to learn commands which are
irrelevant to their use of the system, and they are protected from typing
commands by accident that would cause something to happen that they did
not expect.

Next, let us review some guidelines for writing keyboard monitors.
o

Open a channel for terminal 1/0
All standard RSTS/E keyboard monitors use channel 0 for terminal 1/0
because channel 0 is ahrays open except when the job is detached.
However, if a keyboard monitor is to use special terminal modes, such as
echo control mode, open "KB: II on a channel other than 0 so that you can
use those modes.

Prompt for command input
The" Ready" message is a prompt. So is a dot or a special character such
as ">,, or "$". So is a form on a screen. It is just a way to let the user
know the keyboard monitor is ready for input. You may choose to have a
different prompt, depending on whether the job is logged in or logged out.
BASIC~PLUS prompts a logged~out job with II Bye" .
If you use a form to
prompt, you should display a different form when the job is logged out, to
let the other users know that they can log into the system using that
terminal.

Wait for a command line
After prompting the user, wait for a command line from the keyboard.
Execute a .READ or GET instruction, depending on the language. If you are
coding in MACRO-1', you can put a value of -1 in the XRTIME word of the
XRB, so that terminal service will flag the job as being in keyboard
monitor wait state (displayed as "A C" by SYSTAT). However, you cannot do
the same in BASIC-PLUS, which does not a11o\;I negative WAIT times.

Convert the command line to upper case
(If
you
At least convert the command part of the line to upper case.
like, you may choose to convert to lower case.) At any rate, convert to
one case before processing. Your users should be free to type their
commands in either case and achieve the same results.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 21.1.2 N

RSX Emulator and utilities Package
Package Notes

3 of 4

Check for abbreviations
The ability to abbreviate commands is not mandatory (BASIC-PLUS does not
have it). but your users will love you for it. Each RSTS/E CCL command
can be abbreviated to some minimum number of characters, usually two or
three, when that command is added to the system. Any number of characters
from the minimum to the full length of the command can be typed as the
command. If you process your own commands this way. your users won't have
to learn separate rules for your commands and for CCL commands.

Let CCL do part of your work
Getting a command line executed as a CCL command line is easy, especially
in BASIC-PLUS (V7.2). However, you may want to impose some restrictions,
rather than allowing every user to execute any CCL command.
This is
entirely governed by considerations specific to your system.

RUN programs
Implementing a RUN command is also easy in BASIC-PLUS, by using the CHAIN
statement.
If you can code in MACRO-11. the RUN command is not difficult
in MACRO-11 either. However, consider whether you want to give your users
the full gamut of all executable programs on the system.

The rest is up to you
After CCL commands and RUN, not many standard system commands are left.
You mayor may not need ASSIGN and DEASSIGN commands. You do need a BYE
or LOGOUT command, but these are normally CCL commands already.
You
really have a free hand in designing your command set.

Lastly, observe the following precautions.
o

Be careful with privileges
It would be unusual for a keyboard monitor to require privileges. Thus, a
keyboard monitor is normally non-privileged. If you do make it privileged
for any reason, drop privileges temporarily upon entry to the program,
regain privileges only long enough to execute privileged functions, and
drop privileges again as soon as you can.

Distinguish between logged-in and logged-out jobs
Remember that logged-out jobs are always privileged,
When the job is
logged out, you don I t want to process commands the same way as when the
job is logged in. In fact, a keyboard monitor normally does not want to

RSTS/E V7. 2 Maintenance Notebook., June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
Package Notes

Seq 21.1.2 N

4 of 4

process commands from a logged-out job at all. For this reason, the
"feature" patch to the RSX run-time system does not allow the "menu"
program to be called unless the job is logged in.
o

Be careful with terminal types
If your keyboard monitor is specifically written to handle video terminals
with special characteristics, make sure other terminals on the system,
such as hardcopy terminals, will still work. One way to achieve this is
to include a very simple keyboard monitor mechanism in your keyboard
monitor for such terminals. Another approach is to always invoke another
keyboard monitor for such terminals (switch to another run-time system or
run (CHAIN to) another program).

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 21.3.1 F

RSX Emulator and utilities Package
RSX.RTS

1 of 2

MAKING TASK IMAGES NON-SWAPPABLE - RSX.RTS FEATURE PATCH
Sometimes a situation exists where it would be desirable to lock a job in
memory so that it would not be swapped out between run bursts. The RSTS/E
Programming Manual describes the BASIC-PLUS SYS call which locks a job in
memory.
This article describes how task images may be made non-swappable
through the use of a Task Builder switch.
CAUTION
Locking jobs in memory may cause fragmentation of user space and
is normally not recommended. Use of the capability described in
this article may cause severe system performance degradation,
and may even lock out ALL other jobs on your system.
The Task Builder (TKB) switch "ICP" indicates a "checkpointable" or swappable
task or job.
This is the default for all .TSK files built by TKB. By
specifying "I-CP" for the task output file, e.g.,
TKB TASKI-CP,MAP=OBJ
the resulting task image will be marked as non-swappable. When the task is
run, if the patch described below is installed in the run-time system, the job
will be locked for the duration of its execution. The job will be unlocked
when the task terminates and II Ready" (or an equivalent prompt) is printed.
The following patch applies only to the RSX.RTS distributed with V7.2, and
does not apply to any other run-time system. Thus, the only task images which
can be locked in memory are those built to run under the RSX run-time system.
This excludes all task images built using the HISEG option.
PROCEDURE:
1.

This is a feature patch to the RSX run-time system only.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? RSX.RTS

can

installed

using

(RSX run-time system name)

the

PATCH

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
RSX.RTS
3.

Seq 21.3.1 F
2 of 2

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0,1JRSX.RTS
File found in account [0,1J

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.
4.

The patch is as follows:
Base address? .. NSW
Offset address? 0
Offset Old
Base
?????? 000000 000240
?????? 000002 013700

New?
? .SET
? AC

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

(RSX run-time system name)

system

(RSX run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 21.3.2 F

RSTS/E V7.2
RSX Emulator and Utilities Package
RSX.RTS
DISA~LING

1 of 2

POST-MORTEM DUMPS FOR CTRL/C ABORTS - RSX.RTS FEATURE PATCH

The Post-Mortem Dump capability of the RSX run-time system is enabled for task
images built with the Task Builder IPM switch. (See the RSTS/E Task Builder
Manual.) When such a task is executed, a post-mortem dump file is created if
the task is aborted for any reason. Thus, the error condition which caused
the task to abort may be analyzed through examination of the saved job image.
Strictly speaking, typing CTRL/C to terminate the execution of a task is to
abort it. For example, the program might be in an infinite loop, and, unless
CTRL/C were typed, the program would continue to execute indefinitely.
In
such a case, a post-mortem dump caused by typing CTRL/C may reveal what the
program was doing over and over again.
However, it may not always be
desirable to generate a dump at the typing of CTRL/C, while at the same time a
dump is desired for other kinds of aborts. This article describes a feature
patch to the RSX run-time system to disable the generation of post-mortem
dumps when CTRL/C is typed to abort any task.
PROCEDURE:
1.

This is a feature patch to the RSX run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? RSX.RTS

can

installed

the

PATCH

(RSX run-time system name)

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [0,lJRSX.RTS
File found in account [0,1J

using

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 21.3.2 F

RSTS/E V7.2
RSX Emulator and utilities Package
RSX.RTS
4.

The patch is as follows:
Base address? .. CCPM
Offset address? 0
Offset Old
Base
?????? 000000 000404
?????? 000002 123727

2 of 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 ADDed, or if it is your system default run-time system, execute the
following commands:
RUN $UTILTY(cr>
(UTILTY's header line>
HUNLOAD RSX(cr>
HEXIT(cr>

(RSX run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run-time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY(cr>
(UTILTY's header line>
HLOAD RSX/STAY/ADDR:nnn(cr>
HEXIT<cr>
Ready

system

(RSX run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
RSX.RTS

Seq 21.3.3 F
1 of 3

CHANGE KEYBOARD MONITOR PROMPT - RSX.RTS FEATURE PATCH
The Keyboard Monitor in the RSX run-time system prompts with a "greater-than"
sign (">") when it is ready to accept a command from the terminal. This
prompt is analogous to the" Ready" message of BASIC-PLUS, or the II II (dot)
printed by the RT11 run-time system. In RSTS/E V7.2. it is possible to make
the RSX run-time system the system default run-time system.
There are
advantages to doing this. However, one side effect, which may be considered
undesirable by some users, is that the familiar "Ready" message is not printed
unless the job is using BASIC-PLUS as its private default run-time system.
The procedure described below will change the Keyboard Moni tor prompt of the
RSX run-time system from ">,, to n<CR><LF>Ready<CR><LF><LF>" (logged in) and to
"<CR><LF>Bye<CR><LF>(LF>" (logged out). It also changes the RSX run-time
system to behave like BASIC-PLUS in the following ways:
1.

Typing an empty line does not result in another prompt.

Line Feed is echoed immediately after typing Carriage Return.

Typing CTRL/Z results in the n?End of file on device" error message.

PROCEDURE:
1.

This is a feature patch to the RSX run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? RSX.RTS

can

installed

the

PATCH

(RSX run-time system name)

This patch can be installed manually using ONLPAT,
program;

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

using

the

on-line

patching

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

This patch is contained in a patch file appearing in patch ki t version Ii A"
or later.

RSTS/E V1.2 Maintenance Notebook, June 1982

Seq 21. 3. 3 F

RSTS/E V1.2
RSX Emulator and utilities Package
RSX.RTS

2 of 3

The patch is as follows:
Base address? • • RDY
Offset address? 2
Base
Offset Old
?????? 000002 0000f2J1
?????? f2J00004 001000
?????? 00f2J0f2J6 0f2Jf2J016
?????? f2J00010 000000
?????? 00f2Jf2J12 000000
?????? 000014 000000
?????? 000f2J16 00f2J000
?????? f2J00020 000000
Offset address? ~Z
Base address? • .BYE
Offset address? 2
Offset Old
Base
?????? 0000f2J2 f2J00001
?????? 000004 001000
?????? 000006 000016
?????? 000010 000000
?????? 000f2J12 000000
?????? f2J00014 000000
?????? 000016 000000
Offset address? ~Z
Base address? •• RPT
Offset address? Gf>
Base
Offset Old
?????? f2J00000 012116
?????? 0000f2J2 ??????
?????? 000004 000201
Offset address? ~Z
Base address? • .RMOD
Offset address? Of>
Offset Old
Base
?????? 000000 0f2J1000
?????? 000002 016646
Offset address? ~Z
Base address? • .EOF
Offset address? Of>
Base
Offset Old
?????? 000000 000240
?????? f2J00002 000240
?????? f2J00004 000207

New?
? 1f2J.
? f2J
? 5015
? "RE+20000
? "AD+20f2J40
? 'Y+6440
? 5f2J12
( CTRL/Z for new offset)
? ~Z
( CTRLlZ for new base)
New?
? 8.
? 0
? 5f2J15
? "BY+20000
? 'E+6440
? 5012
(CTRLlZ for new offset)
? ~Z
( CTRLlZ for new base)
New?
? NOP
? NOP
? ~Z

( CTRLlZ for new offset)
(CTRLI Z for new base)

New?
? 0
? ~Z

New?
? 4137
? .. ERMS
? ~C

( CTRLlZ for new offset)
( CTRLlZ for new base)

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

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
RSX.RTS

Seq 21.3.3 F
3 of 3

(RSX run-time system name)

system

(RSX run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 21.3,4 F

RSX Emulator and utilities Package
RSX,RTS

1 of 2

CHANGE PROGRAM NAME OF KEYBOARD MONITOR - RSX.RTS FEATURE PATCH
The Keyboard Monitor in the RSX run-time system sets up a II program name" of
", .. MeR" (~1onitor Console Routine) when it is waiting for a command to be
typed at a terminal. By comparsion, BASIC-PLUS sets up a program name of
"NONAME", and the RTll run-time system set up the name" RT11". This name is
displayed by SYSTAT, or by typing CTRL/T (if the feature is included on the
system). Some users may prefer to change the " ... MCR" name to the familiar
II NONAME" , or
to some other name of their choice.
The procedure described below will change the program name of the RSX Keyboard
Monitor to II NONAMEIi . Any other six-character alphanumeric (or RAD50) name may
be sub sti tuted .
PROCEDURE:
1.

This is a feature patch to the RSX run-time system.

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? RSX.RTS

can

installed

using

the

PATCH

(RSX run-time system name)

This patch can be installed manually using ONLPAT,
program:

the

on-line

patching

RUN $ONLPAT

Command File Name? <cr>
File to patch? [0,lJRSX.RTS
File found in account [0,lJ

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

This patch is contained in a patch file appearing in patch kit version II A"
or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
RSX.RTS

2 of 2

The patch is as follows:
Base address? .. NAM
Offset address? <If>
Base
Offset Old
?????? 00012100 131574
17??17 000002 050712
?17??? 000004 0000130

Seq 21.3.4 F

New?
? %NON
? %AME
? ... C

(up-arrowl C to exit;CTRLlC for INIT)

(RSX run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run~time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
HLOAD RSX/STAY/ADDR:nnn<cr)
IIEXIT<cr)
Ready

system

(RSX run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
RSX.RTS

Seq 21. 3.5 F
1 of 3

INVOKING A MENU PROGRAM - RSX.RTS FEATURE PATCH
PROBLEM:
Some installations may elect for certain users to return to a menu program,
instead of one of the standard RSTS/E Keyboard Monitors such as BASIC-PLUS.
SOLUTION:
The following feature patch to the RSX run-time system will change its
keyboard monitor such that it invokes a program called "MENU" in account
[1,10] instead of issuing its normal ">,, prompt.
"MENU" must be compiled
(i.e •• executable).
If a specific file type is required, include it in the
following patch. Otherwise, the effect of the patch will be equivalent to
typing "RUN [1,10]MENU" to the keyboard monitor.
The first portion of the patch determines the filename specification of the
menu program to be invoked.
Any valid RSTS/E filename specification,
including device, PPN, filename, and file type (up to 26 characters) may be
patched in. The filename string begins at Base" •• MENU", Offset 0. Two ASCII
characters per word may be patched in, using the quote (") prefix.
The second portion of the patch determines the line number at which the
program is to be started. Be sure to include the decimal point (".") after
the line number value so that it is interpreted as a decimal number.
If the menu program cannot be run for any reason, the RSX run-time system will
default to its normal keyboard monitor.
PROCEDURE:
1.

This is a feature patch to the RSX run-time system. It may be installed
in any RSX run-time system. Alternatively, you may install it in a new
run-time system created from the RSX run-time system. For example,
RUN $PIP.SAV<cr>
*SY:[0,1]MENU.RTS/MO:16=SY:[0,1]RSX.RTS<cr>

*"Z
Ready

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
RSX.RTS
2.

2 of 3

The patch described in Step 4 below
option of INIT.SYS:
Option: PATCH
File to patch? RSX.RTS

Seq 21.3.5 F

can

installed

using

the

PATCH

(RSX run-time system name)

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

the

on-line

patching

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

This patch is contained in a patch file appearing in patch kit version "A"
or later.
NOTE
The patch file for this patch requires manual editing to
include installation specific parameters before it can be
successfully installed. Specifically, change [1,10]MENU to
the desired account and program name.
4.

The patch is as follows:
Base address? .. MENU
Offset address? 0
Base
Offset Old
?????? 000000 020040
?????? 000002 020040
?????? 000004 020040
?????? 000006 020040
?????? 000010 020040
?????? 000012 020040
Offset address? "z
Base address? .. LINE
Offset address? 0
Base
Offset Old
?????? 000000 000000
?????? 000002 ??????

New?
? "[ 1
? ", 1
? "0 ]
? "ME
? "NU
? "z

New?
? 0.
? "c

(File specification
(of menu program)

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

(Line number to start at)
(up-arrow/C to exit;CTRL/C for INIT)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
RSX.RTS
5.

Seq 21.3.5 F

3 of 3

(RSX run-time system name)

Ready
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.
If, in addition to being previously ADDed, the run-time
ADDed with the ISTAY switch, also reload it as follows:
RUN $UTILTY<cr>
<UTILTY's header line>
IILOAD RSX/STAY/ADDR:nnn<cr>
IIEXIT<cr>
Ready

system

(RSX run-time system name)

had

been

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
CRF.TSK

Seq 21.13.1 N
1 of 2

USING THE RSX CRF UTILITY
An RSX CRF.TSK utility is included on the RSTS distribution kit as an
unsupported product.
It is not, therefore, copied from the distribution by
This program will create cross reference
any of the build procedures.
listings from the binary cross reference (.CRF) files optionally produced by
the RSX task builder (TKB) and 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:
CRF
CREATED BY MACRO ON 15-JUL-79 AT 06 :02
SYMBOL CROSS REFERENCE
SYMBOL VALUE
REFERENCES
CR
000015
114-180
=
FF
114-180
= 000014
HT
000011
114-180
=
LF
000012
114-180
=
L$$IST = ******
1-1
1-2
2-53
RSTS
000001
114-39
=
R$$11M = 000000
114-38
SPA
000040
114-180
=
VT
000013
114-180
=
******
V1145
4-157
=
$$$VER = 034066
115-1
113-2

PAGE
CREF

07.065

4-182

3-1

Task Builder output:
CRF

CREATED BY

TKB

ON 15-JUL-79 AT 06:23

GLOBAL CROSS REFERENCE

PAGE
CREF

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

II DIRSYM

CRFIN

II FCSGBL

II DIRSYM
/I DIRSYM
II DIRSYM
/I DIRSYM
II ERR
II ERR

FIP
FIP

07.065

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RSX Emulator and utilities Package
CRF.TSK

Se q 21. 13 • 1 N
2 of 2

More details on the CRF output can be found in the RSX-11 utilities Procedures
Manual.
To request that MAC or TKB produce a binary cross reference file, the /CR
switch must be specified 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 CCL if installed. When
run using the RUN command, CRF will prompt with II CRF)" . Typing the CTRLlZ
combination 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 II@II) 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 V7e2 Maintenance Notebook, June

1982

RSTS/E V7. 2

Seq 22. 1 • 1 N

RT-l1 Emulator and utilities Package
Package Notes

1 of 1

USE OF UNDERSCORE IN RT-l1 EMULATOR UTILITIES
RSTS/E allows the use of the underscore (II II) 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-l1 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-l1 emulator, file specifications given to a utility are scanned
using the RT-l1 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-l1 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
speci fied in RT-l1 file description blocks.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
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
feature which can be linked with user-written run-time systems.

unsupported

To use RTSODT with run-time systems that are assembled and linked under the
RTll run-time system, execute the following commands:
RUN $LBR.TSK<cr)
LBR)RTSODT.OBJ=LB:SYSLIB/EX:RTSODT<cr)
LBR)"Z
Ready
RUN $PIP.SAV<cr)
*RTSODT.OBJ=RTSODT.OBJ/RMS:FB<cr)
*"Z
Ready
You may now include RTSODT.OBJ in the list of input
For example:

files

during

the

LINK.

RUN $LINK<cr)
*RT110D/Z,RT110D/W,RT110D=RT11/X/H:U177776/U:U4000/C< cr)
*UERR.STB,URTSODT<cr)
*PATCH<cr)
*"Z
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 V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RT-l1 Emulator and utilities Package
HOOK.SAV

Seq 22.5.1 N
1

of 5

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 SYSGEN, 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":
RUN $UTILTY<cr>
<UTILTY's header line>
HMOUNT xxn:packid/PRIVATE<cr>
I('Z

Ready
Copy INIT.SYS from your system disk to the output device:
RUN $PIP.SAV<cr>
*xxn:[0,lJ*.*:SY0:[0,lJINIT.SYS<cr>
*"Z

Ready
Then, run HOOK.SAV:
RUN $HOOK.SAV<cr>
*xxn:[0.1JINIT.SYS<cr>
Hook complete
*"Z
Ready
Creating a bootable RSTS/E DOS-format Magnetic Tape
Mount a scratch magnetic tape on a tape drive.
the tape before using it.) Then, run HOOK.SAV:
RUN $HOOK.SAV<cr>
*xxn:[0.1JINIT.SYS[/D[:n.]],SY0:[0,1]INIT.SYS<cr)
Hook complete
wAZ

(Note that HOOK.SAV will zero

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RT-11 Emulator and utilities Package
HOOK.SAV

Seq 22.5.1 N
2 of 5

Ready
NOTES
1.

Magnetic tape density:
follows:

ID:800.
ID
ID: 1600.
ID: 1600

Specify Ii/D:n" after the "output"

dev:filnam,

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

Note:
o ID:800 (no dot) is an illegal specification
o If ID is not specified, the drive's current settings are used.
o HOOK will assign the tape drive to you, in DOS format, at the
density that you specify (or do not specify).
2.

Normally. HOOK finds the bootstraps for disks and magnetic tapes in
SY0:[0.1JINIT.SYS.
If,
as
may happen on a development machine,
[0,lJINIT.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 must meet the following criteria:
o It must reside on a mounted disk
o It must be a SAV-format SIL with a symbol table
o It must have the global symbols "BOOTS" and "MBOOTS" defined for the
start of the disk and magnetic tape boots, respectively.
o The bootstraps must be in the standard RSTS/E format, 400(8) bytes
for each disk bootstrap, and 1000(8) bytes for each magnetic tape
bootstrap.
o In short, the bootstrap file should look like INIT.SYS.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 22.5.1 N

RT-l1 Emulator and utilities Package

HOOK.SAV

3 of 5

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 [0.1JMTBOOT.SYS. If
the tape is written at 1600 BPI, the name of the first file will be
[0,lJMSBOOT.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
tape, the default name INIT.SYS is used, with the current PPN.
words, if you are logged in under [123,1] and specify

magnetic
In other

MT0:/D:800. ,[0,lJFOO.FOO
the files on the tape will be "[0,lJMTBOOT.SYS" and n[123,1]INIT.SYS".
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. If the directory looks unusual, it is
not a bootable RSTS/E tape.
5.

The following might be useful information.
standard command lines:
DK0:[0,lJINIT.SYS
Load and execute [0,l]INIT.SYS when DK0: is booted.

MM1:[0,lJINIT.SYSID:1600,DR0:[0,lJINIT.SYS
Load and execute MM1:[0,lJINIT.SYS when MM1: is booted; copy the
file to be executed from DR1:[0,l]INIT.SYS; set the density to
1600 BPI.
Non-standard command lines:
DB3:[0,lJINIT.SYS,,[4,4]NEWINI.SYS
Load and execute [0,lJINIT.SYS when
bootstrap from [4,4]NEWINI.SYS.

DB3:

MM0:,[0,1]INIT.SYS <not recommended)
Load and execute a file called
[0,1 ]I NIT .SYS.

INIT.SYS that was copied from

booted;

get

the

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 22.5.1 N

RSTS/E V7.2
RT-l1 Emulator and utilities Package
HOOK.SAV
6.

4 of 5

Possible Errors:
?Can't open disk NFS
Someone else is using the disk
privileged.

HOOKed,

you

are

not

?Can't open [0,1JSY0:INIT.SYS
You must be privileged to run HOOK.SAV
?Directory error
The output disk is not a valid RSTS/E file-structured disk.
?File high limit too large
The file to be loaded by the bootstrap program is too large.
?Error reading boot block
An 1/0 error occurred while reading the disk to be HOOKed;
be off-line.
?Error writing boot block
An 1/0 error occurred while writing the
disk may be write-locked.

bootstrap

it may

program;

the

?Error reading pack ID
An 1/0 error occurred while reading the disk to be HOOKed.
?Error reading INIT.SYS
An 1/0 error occurred while reading INIT.SYS.
?Explicit unit number required
The device name specified must include an explicit unit number.
?Ill cmd?
HOOK.SAV could not interpret the specified command line.
?Illegal density
The density that you specified cannot be used on this tape drive.
?Illegal overlay number in INIT
You are using an obsolete version of INIT.SYS.
?INIT.SYS is not a SAV format SIL
You are using an obsolete version of INIT.SYS.
?Not a boatable device
HOOK.SAV cannot write a bootstrap for that device.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
RT-l1 Emulator and utilities Package
HOOK.SAV

Seq 22.5.1 N

5 of 5

?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 the magnetic tape.
?UFD open failure
An 1/0 error occurred.

RSTS/E V7.2 Maintenance Notebook. June 1982

RSTS/E V7.2
RT-11 Emulator and utilities Package
PIP,SAV

Se q 22. 13 . 1 F
1 of 1

SETTING INEWFILE AS A DEFAULT PIP.SAV OPTION - PIP.SAV FEATURE PATCH
PROBLEM:
When transferring a disk file to a new disk file, PIP transfers the creation
date and time, and last access date of the existing file to the newly created
file. This may be undesirable in some environments where files are backed up
by creation or access dates.
SOLUTION:
This problem may be solved on a per-command basis by using the INEWFILE
option.
However, if it is deemed that this operation is desired as the
default, the following PIP patch may be applied.
If this patch is applied INEWFILE will be the default operation. To transfer
a file and retain all accounting information the IRETAIN switch may be used on
a per-command basis to override the new default.
PROCEDURE:
1.

This is a feature patch to PIP.SAV.

The patch described in Step 4 below can NOT be installed using
option of INIT.SYS.

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [1,2]PIP.SAV
File found in account [1,2J

the

on-line

the

PATCH

patching

(RETURN for manual patch installation)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.
4.

The patch is as follows:
Base address? .. NEWF
Offset address? 0
Base
Offset Old
?????? 000000 001037
?????? 000002 005767

New?
? (Q&377)+BR
?

"'c

(up-arrowl C to exit)

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 22.13.2 F

RSTS/E V7. 2
RT-l1 Emulator and utilities Package
PIP.SAV

1 of 1

TRANSFERRING FILES BY DATE OF LAST ACCESS - PIP.SAV FEATURE PATCH
PROBLEM:
PIP allows file operations selectively by creation date through the use of a
number of switches (i.e .• ITODAY, ISINCE, IUNTIL, etc.). In some instances it
would be desirable to have such switches key off of the last access date.
SOLUTION:
Two new switches have been added to PIP to allow specifying either creation
date (/CREATION) or date of last access (/DLA). The default operation is to
key off of the creation date.
The following patch will set the defaul t
operation to key all date selections off of the date of last access.
PROCEDURE:
1.

This is a feature patch to PIP.SAV.

The patch described in Step 4 below CANNOT be installed using the INIT.SYS
PATCH option.

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [l,2JPIP.SAV
File found in account [1,2J

the

on-line

patching

(RETURN for manual patch installation)

The patch is also contained in a patch file appearing in patch kit version
"Ail or later.

The patch is as follows:
Base address? ,.DLAC
Offset address? 0
Offset Old
Base
?????? 000000 001002
?????? 000002 016700

New?
? (Q&377)+BR
? "c
(up-arrow/C to exit)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2

Seq 22. 13.3 F

RT-ll Emulator and utilities Package
PIP.SAV

1 of 1

REQUIRING VOLUME 1.0. SPECIFICATIONS WITH ANSI MAGNETIC TAPES
- PIP.SAV FEATURE PATCH
PROBLEM:
When using PIP.SAV to write multi-volume ANSI format magnetic tapes, a volume
10 may be specified when mounting a tape. The default action for PIP is to
check the volume 1.0. against that of the tape being mounted, and if the two
do not match to reject the mounted tape. In some environments it might be
desirable to force the specification of the volume 1.0. to insure maximum tape
security.
SOLUTION:
The following patch will reject the mounting of an ANSI format
if no volume 1.0. is specified.

magnetic

tape

PROCEDURE:
1.

This is a feature patch to PIP.SAV.

The patch described in Step 4 below can NOT be installed using
option of INIT.SYS.

This patch can be installed manually using ONLPAT.
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [1.2JPIP.SAV
File found in account [l,2J

the

on-line

the

PATCH

patching

(RETURN for manual patch installation)

The patch is also contained in a patch file appearing in patch kit version
"A" or later,
4,

The patch is as follows:
Base address? ,.VIDS
Offset address? 0
Base
Offset Old
?????? 000000 000403
?????? 000002 032704

New?
? NOP
?

(up~arrowl C to

ex it)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RT-11 Emulator and utilities Package
PIP.SAV

Seq 22. 13.4 F
1 of 1

SETTING ILOG AS A DEFAULT PIP.SAV OPTION - PIP.SAV FEATURE PATCH
PROBLEM:
In some environments it is desirable to have the ILOG option with PIP.SAV
for all transactions.
NOTE

set

Certain control files for older products which use PIP.SAV may
not run with this optional feature patch installed.
SOLUTION:
The following PIP.SAV feature patch will set the ILOG option for every PIP.SAV
command which allows the use of ILOG. Note that the INOLOG switch may be used
to suppress the logging for a particular operation.
PROCEDURE:
1.

This is a feature patch to PIP.SAV.

The patch described in Step 4 below can NOT be installed using
option of INIT.SYS.

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [1,2JPIP.SAV
File found in account [1,2J

the

on-line

the

PATCH

patching

(RETURN for manual patch installation)

The patch is also contained in a patch file appearing in patch kit version
"An or later.
4.

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

New?
? 100000
? AC

(up-arrowl C to exit)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RT-11 Emulator and utilities Package
PIP.SAV

Seq 22.13.5 F
1 of 1

MAKING IERASE IMPLY IDELETE - PIP.SAV FEATURE PATCH
PROBLEM:
Some users may want to make the IERASE switch imply IDELETE.
SOLUTION:
The patching procedure detailed below will cause the IERASE
IDELETE.

switch

imply

This is a feature patch to PIP.SAV.

The patch described in Step 4 below can NOT be installed using
option of INIT.SYS.

the

PATCH

This patch can be installed manually using ONLPAT,
program:

PROCEDURE:

RUN $ONLPAT
Command File Name? <cr>
File to patch? [1,2JPIP.SAV
File found in account [1,2J

the

on-line

patching

(RETURN for manual patch installation)

This patch is contained in a patch file appearing in patch kit version "A"
or later.
4.

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

? 10001

? AC

(up-arrow/C to exit)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTSIE V7. 2
RT-l1 Emulator and utilities Package
PIP.SAV

Seq 22.13.6 F
1 of 1

CHANGING THE MAXIMUM ALLOWABLE MAGNETIC TAPE BLOCKING SIZE
- PIP.SAV FEATURE PATCH
PROBLEM:
The current maximum allowable blocking size that PIP permits on magnetic tape
is 4096. Some installations may want to change this to 8192. to allow better
usage of magnetic tape.
SOLUTION:
The procedure described below shows how this can be accomplished.
NOTE
Unless the CCL 'lSI' switch is used to increase PIP's si ze or
the procedure described in article Seq 22.1.3 N is used to
increase the default load size, PIP will not allow larger
blocksizes because of lack of buffer space,
This can be
overcome by changing PIP's size to 20K words.
PROCEDURE:
1.

This is a feature patch to PIP.SAV.

The patch described in Step 4 below can NOT be installed using
option of INIT.SYS.

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [1,2JPIP.SAV
File found in account [l,2J

the

on~line

the

PATCH

patching

(RETURN for manual patch installation)

This patch is contained in a patch file appearing in patch kit version II A"
or later.
4.

The patch is as follows:
Base address? .. BSHI
Offset address? 0
Base
Offset Old
?????? 000000 010000
?????? 000002 003004

New?
? 8192.

? AC

(up-arrow/C to exit)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RT-11 Emulator and utilities Package
SAVRES.SAV

Seq 22.19.' F
1 of 2

CHANGE SAYRES DEFAULT DENSITY TO 1600 BPI - SAVRES.SAV FEATURE PATCH
PROBLEM:
SAYRES, as released, defaults to the lowest density (of 800 BPI and 1600 BPI)
allowed by a given tape drive (normally 800 BPI) for all tape I/O. It may be
desirable at some installations to have SAYRES default to the highest density
allowed by a given tape drive for more compact storage of data. This is
especially true if all drives on the system support 1600 BPI and the problem
described below is not applicable.
CAUTION
If the tape drive being used has a TM02 formatter, the hardware
bootstrap of a 1600 BPI tape will not be possible.
(You can
determine the formatter type by using the HARDWR LIST suboption
of INIT,) Therefore, if it is desirable for SAYRES to create
tapes which are bootable on such a drive it is recommended that
this patch not be installed. Normally. TU16 and TU45 drives use
a TM02 formatter, TE16 and TU77 drives do not.
SOLUTION:
The following feature patch will cause SAYRES to default to the highest
density allowed by a given tape drive for all tape I/O. This default can be
overridden by attaching the /DENSITY:800 switch to the device specification.
Refer also to article Seq 1.1.1 F, which supplies a similar patch for the
SAYRES option of INIT.
PROCEDURE:
1.

This is a feature patch to SAVRES.SAV.

The patch described in Step 4 below can NOT be installed using
option of INIT.SYS.

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [1,2JSAVRES.SAV
File found in account [1.2J

the

on-line

the

PATCH

patching

(RETURN for manual patch installation)

RSTS/E V7.2 Maintenance Notebook, June 1982

Seq 22.19.1 F

RSTS/E V7.2
RT-11 Emulator and utilities Package
SAVRES.SAV

2 of 2

The patch is also contained in a patch file appearing in patch kit version
"A" or later.
4.

The patch is as follows:
Base address? DIACTL
Offset address? 310
Offset Old
Base
?????? 000310 030070
?????? 000312 177460
?????? 000314 033061
?????? 000316 030060
?????? 000320 000377
?????? 000322 001440
?????? 000324 003100
?????? 000326 000000
Offset address? "'z
Base address? SAVCTL
Offset address? 42
Offset Old
Base
?????? 000042 030070
?????? 000044 177460
?????? 000046 033061
?????? 000050 030060
?????? 000052 000377
?????? 000054 001440
?????? 000056 003100
?????? 000060 000000
Offset address? "'z
Base address? RESCTL
Offset address? 30
Offset Old
Base
?????? 000030 030070
?????? 000032 177460
?????? 000034 033061
?????? 000036 030060
?????? 000040 000377
?????? 000042 001440
?????? 000044 003100
?????? 000046 000000

New?
? "16
? "00
? 034377
? <If>
? <If>
? 1600.
? 800.
? "'z

New?
? "16
? "00
? 034377
? <If>
? <If>
? 1600.
? 800.
? "'c

(no change; verify only)
(no change; verify only)
( CTRLlZ for new offset)
(CTRLI Z for new base)

(no change; verify only)
(no change; verify only)
(CTRLI Z for new offset)
( CTRLlZ for new base)

(no change; verify only)
(no change; verify onl y)
( up-arrow/ C to ex it)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2
RT-11 Emulator and utilities Package
SAVRES.SAV

Seq 22.19.2 F
1 of 2

MAKING INOERROR THE DEFAULT - SAVRES.SAV FEATURE PATCH
PROBLEM:
The INOERROR switch indicates that SAYRES should
conditions:
1.
2.

3.
4.

abort

under

the

following

A contiguous file is made non-contiguous
A placed file is "unplaced"
A bad comparison occurs
An unexpected bad block is encountered on the input RSTS/E disk
in a SAVE or IMAGE operation

Some installations, however, may always
circumstances.

want

SAYRES

abort

under

these

SOLUTION:
The following feature patch will make INOERROR, rather than IERROR, the
default in SAVRES.SAV.
Note that the user may override the default for a
particular operation by specifying IERROR. Refer also to article Seq 1.1.2 F,
which supplies a similar patch for the SAYRES option of INIT.
PROCEDURE:
1.

This is a feature patch to SAVRES.SAV.

The patch described in Step 4 below can NOT be installed using
option of INIT.SYS.

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [1,2]SAVRES.SAV
File found in account [1,2]

the

on-line

the

PATCH

patching

(RETURN for manual patch installation)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7.2

Seq 22.19.2 F

RT-11 Emulator and utilities Package
SAVRES.SAV

2 of 2

The patch is as follows:
Base address? .• NOER
Offset address? 2
Base
Offset Old
?????? 000002 000010
?????? 000004 ??????
?????? 000006 ??????
?????? 000010 ??????
?????? 000012 000004
?????? 000014 ??????

New?
? 4
? <If>
? <If>
? <If>
? 10
? "'c

(no change)
(no change)
(no change)
(up-arrowl C to exit)

RSTS/E V7.2 Maintenance Notebook, June 1982

RSTS/E V7. 2
RT-11 Emulator and utilities Package
SAVRES.SAV

Seq 22.19.3 F
1 of 1

MAKING INOSTATS THE DEFAULT - SAVRES.SAV FEATURE PATCH
PROBLEM:
SAVRES always prints a summary report after completing a transfer unless the
INOSTATS (no statistics) switch is specified.
Certain installations may
prefer that this report NOT be printed unless specifically requested.
SOLUTION:
The following feature patch will make INOSTATS, rather than ISTATS, the
default in SAVRES.SAV.
Note that the user may override this default for a
particular operation by specifying ISTATS. Refer also to article Seq 1.1.3 F,
which supplies a similar patch for the SAVRES option of INIT.
PROCEDURE:
1.

This is a feature patch to SAVRES.SAV.

The patch described in Step 4 below can NOT be installed using
option of INIT.SYS.

This patch can be installed manually using ONLPAT,
program:
RUN $ONLPAT
Command File Name? <cr>
File to patch? [1,2JSAVRES.SAV
File found in account [1,2J

the

on-line

the

PATCH

patching

(RETURN for manual patch installation)

The patch is also contained in a patch file appearing in patch kit version
"A" or later.
4.

The patch is as follows:
Base address? .. NOST
Offset address? 2
Offset Old
Base
?????? 000002 000040
?????? 000004 ??????
?????? 000006 ??????
?????? 000010 ??????
?????? 000012 000020
?????? 000014 ??????

New?
? 20
? <If>
? <If>
? <If>
? 40
? "c

(no change)
(no change)
(no change)
(up-arrowl C to exit)

RSTS/E V7.2 Maintenance Notebook, June 1982
SPDs and Option Bulletins

6.g

6.1

Page 6-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, a sample of which is shown below:
SPD 13.1.20
This number appears on the first page of the SPD bulletin, at the far right
hand side of the PRODUCT NAME: line.
Note that the last part of the SPD number is the revision level, with 0
assigned for original issues of SPDs.

being

RSTS/E V7.2 Maintenance Notebook, June 1982
SPDs and Option Bulletins
6.2

Page 6-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 release notes is provided as a convenient place to file these bulletins.
There is no filing scheme for option bulletins.

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/o Digital's local subsidary
or approved distributor

Internal orders should be placed through the Software Distribution Center (SDC), 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 V7.2 Maintenance Notebook

AA-L997B-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
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 ____________________________________________________________________
City _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ___ State _______ ZiporCode ________
Country

I
I
I
i
I
I

-------Do Not Tear - Fold Here and Tape _______________________________ ~ ____ .J
t

II IIII
•

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

ATIN: Commercial Engineering Publications MK1-2/H3
DIGITAL EQUIPMENT CORPORATION
CONTINENTAL BOULEVARD
MERRIMACK, N.H. 03054

No Postage
Necessary
if Mailed in the
United States

I
I

I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
!
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
i

- - - - - - - Do Not Teal' . Fold Here and Tape - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - j

I
i
I
I
I
I
I
I
I
I
I
I
I

Q.)

1:5=
l'ti

ICi
IQI)
I §

1<
I ....
I

;::I

Ie,.)

I
i
I
I
I
i
I
I
I
I
I
I
I
i
I

DIGITAL EQUIPMENT CORPORATION

Printed in U.S.A.