Digital PDFs

AA-5246H-TC

November 1990

156 pages

Original

17MB

Document:	RSTS/E V10.0 Release Notes
Order Number:	AA-5246H-TC
Revision:	0
Pages:	156
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsts_e/V10/AA-5246H-TC_RSTS_E_V10.0_Release_Notes_Nov1990.pdf

OCR Text

RSTS/E Version 10.0 Release Notes
Order Number: AA-5246H-TC

(

RSTS/E Version 10.0 Release Notes
Order Number: AA-5246H-TC

November 1990
These Release Notes describe new features of the RSTS/E Version 10.0 system and explain
the differences between this release and previous versions of RSTS/E. System managers and
system maintainers should read this document prior to system installation.

Operating System and Version: RSTS/E Vi 0.0
Software Version:

(

digital equipment corporation
maynard, massachusetts

RSTS/E V10.0

November 1990
The information in this document is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation
assumes no responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may only be used
or copied in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment not supplied
by Digital Equipment Corporation or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1 )(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013.

© Digital Equipment Corporation 1990. All rights reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document requests
the user's critical evaluation to assist in preparing future documentation. The following are
trademarks of Digital Equipment Corporation:
ALL-IN-1
DATATRIEVE-11
DEC/CMS
DECdx
DEC/FMS-11
DECmail
DECnet
DECnetiE
DECSA
DECserver
DECsystem-10
DECSYSTEM-20
DECUS
DECworld
DELUA
DEQNA

DEUNA
DIBOl
EDT
FMS-11
lAS
LA
LN01
Micro/RSX
OS/8
PDP
PDP-11
PDT
Q-BUS
RMS-11
RSTS

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

~DmDDmDm

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

(

Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1
1.1

New Features
NewHardwa~Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Higher performance PDP-11/93, 11/94 Processors .............. .
RA70 and RA90 Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LA324 Desktop Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1
1-1
1-2
1-2

New Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1
Command Line Editing and Command Recall ................. .
1.2.1.1
Command Line Editing ........................ .
1.2.1.2
Command Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.3
System Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4
Terminal Attributes ........................... .
1.2.1.5
Command Recall Buffers ....................... .
1.2.1.6
Terminal OPEN Modes ........................ .
1.2.1.7
Command Line Editing and Recall Keys ............ .
1.2.1.8
Editing Multiline Commands ..................... .
SET HOST Behavior ......................... .
1.2.1.9
1.2.1.10
Software/Hardware Terminal Setup ................ .
1.2.2
Echo On Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.1
Program ming Considerations .................... .
1.2.2.1.1
Use of Terminal Input Buffers .................. .
1.2.2.1.2
Conditional Reads ......................... .
Host Initiated LAT Connections ........................... .
1.2.3
1.2.3.1
lAT Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3.2
New Commands for Host Initiated lAT Connections .... .
1.2.3.3
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
lAT Queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3.4
1.2.3.5
Programming Considerations .................... .
Dial-out Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3.6
Extended logicals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4
1.2.4.1
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator/Message Services (OMS) ........................ .
1.2.5
Installing OMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.5.1
1.2.5.2
OPSER Compatibility ......................... .
1.2.5.3
New DCl Commands For OMS .................. .
1.2.6
New File Attribute Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Job Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.7
lOGIN User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.8
1.2.9
New OPER Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.10
Improved lOGIN Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3
1-3
1-3
1-3
1-4
1-5
1-5
1-6
1-7
1-8
1-9
1-10
1-10
1-11
1-11
1-12
1-12
1-13
1-13
1-13
1-15
1-16
1-17
1-17
1-18
1-18
1-19
1-20
1-20
1-20
1-21
1-22
1-22
1-23

1.1.1
1.1.2
1.1.3
1.2

(

iii

1.2.11

1.2.12
1.2.13
1.2.14
1.2.15

Chapter 2
2.1
2.2

New DCL Commands and Qualifiers . . . . . . . . . . . . . . . . . . . . . . . .
1.2.11.1
New F$ENVIRONMENT Function . . . . . . . . . . . . . . . . . .
New ASSIGN/PORT Command . . . . . . . . . . . . . . . . . . .
1.2.11.2
New CREATE/PORT Command . . . . . . . . . . . . . . . . . . .
1.2.11.3
New BACKUP/IMAGE Command . . . . . . . . . . . . . . . . . .
1.2.11.4
New BACKUP/COPY Command . . . . . . . . . . . . . . . . . . .
1.2.11.5
New BACKUP Verify-Only Operation ............... .
1.2.11.6
New /INITIALIZE Arguments for BACKUP and
1.2.11.7
RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator-Assisted BACKUP and RESTORE .......... .
1.2.11.8
1.2.11.9
New /REPLACE=QUERY and /QUERY Options ....... .
1.2.11.10 New DEASSIGN/PORT Command ................ .
1.2.11.11 New DELETE/PORT Command . . . . . . . . . . . . . . . . . . .
1.2.11.12 New FILE_UTILITY Overlay . . . . . . . . . . . . . . . . . . . . . .
1.2.11.13 New /NOTIFY Qualifier for PRINT and SUBMIT ....... .
1.2.11.14 New /[NO]OUTPUT Qualifier . . . . . . . . . . . . . . . . . . . . .
1.2.11.15 New RECALL Command . . . . . . . . . . . . . . . . . . . . . . . .
1.2.11.16 New REPLY Command . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.11.17 New SET FILE Qualifiers . . . . . . . . . . . . . . . . . . . . . . .
1.2.11.18 New SET OPERATOR_SERVICES Command ........ .
1.2.11.19 New SET PORT Command . . . . . . . . . . . . . . . . . . . . . .
1.2.11.20 New SET TERMINAL Qualifiers . . . . . . . . . . . . . . . . . . .
1.2.11.21 New SHOW ACCOUNT/FULL Fields. '.' ............ .
1.2.11.22 New SHOW ENTRY Status: FORMS_WAIT .......... .
1.2.11.23 New SHOW ENTRY Qualifier . . . . . . . . . . . . . . . . . . . . .
1.2.11.24 New SHOW OPERATOR_SERVICES Command ....... .
1.2.11.25 New SHOW PORT Command . . . . . . . . . . . . . . . . . . . .
1.2.11.26 New SHOW REQUEST Command ................ .
1.2.11.27 New START/OPERATOR_SERVICES Command ....... .
1.2.11.28 New STOP/OPERATOR_SERVICES Command ....... .
1.2.11.29 New CC Command . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.11.30 New COPY /TRANSFER_MODE Qualifier ........... .
New RSX Directive - MSDS$ . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Easier BASIC-PLUS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
New CUSP Resident Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New SORT/MERGE Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support for OMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
START.COM File Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accounts for Optional Packages . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1
2-3
2-3

Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Temporary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Larger Record I/O for Libraries and Regions . . . . . . . . . . . . . . . . . .
Larger Magtape Recordsizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New Local Object Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS Driver Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYS Call Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.6.1
.LOGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.6.2
.READA and .wRITA . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.6.3
.ULOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.6.3.1
UU.ASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.6.3.2
UU.DAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.6.3.3
UU.DEA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2--4
2--4
2--4
2--4
2--4

2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6

1-28
1-29
1-29
1-30
1-30
1-30
1-30
1-30
1-31
1-32
1-32
1-32
1-32
1-33
1-33
1-33
1-33
1-34
1-34
1-34
1-34
1-34
1-34
1-35
1-35
1-35
1-35
1-36

Differences Between V10.0 and V9.7

2.2.1
2.2.2
2.2.3
2.3

1-23
1-23
1-26
1-26
1-26
1-27
1-28

2--4

2-5
2-5
2-5
2-5
2-5
2-6
2-6
2-6

2.3.6.4
2.3.6.5
2.3.6.6
2.3.6.7
2.3.6.8
2.3.6.9
2.3.6.10
2.3.6.11
2.3.6.12
2.3.6.13
2.3.6.14

2.4

2.5

2.6

DCl
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.4.6
2.4.7
2.4.8
2.4.9
2.4.10
2.4.11
2.4.12
2.4.13
2.4.14
2.4.15
2.4.16
2.4.17
2.4.18
2.4.19
2.4.20
2.4.21
2.4.22
2.4.23
2.4.24
2.4.25
2.4.26
2.4.27

UU.ATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.CHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.CNV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.FCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.FIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.L1N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.SLN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.SWP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.TB3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UU.TRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ALLOCATE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASSIGN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE/ACCOUNT Command . . . . . . . . . . . . . . . . . . . . . . . . . . .
DEASSIGN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DEFiNE/COMMAND/SYSTEM Command . . . . . . . . . . . . . . . . . . . . .
DIRECTORY Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HELP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INITIAliZE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INQUIRE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LINK Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOAD/OVERLAY Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MOUNT/REBUILD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRINT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REQUEST Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET ACCOUNT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET JOB/PRIVILEGE Command . . . . . . . . . . . . . . . . . . . . . . . . . .
SET NODE/LAT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET SYSTEM Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET TERMINAL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW ACCOUNT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW DEVICE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW JOB/PRIVILEGES Command . . . . . . . . . . . . . . . . . . . . . . . .
SHOW LOGICALS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW SYSTEM Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW TERMINAL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SUBMIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOAD/OVERLAY Command . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-6
2-6
2-6
2-6
2-7
2-7
2-7
2-7
2-7

2-8
2-8
2-8
2-8
2-9
2-9
2-9
2-9
2-9
2-10
2-10
2-10
2-10
2-10
2-11
2-11
2-11
2-11
2-11

2-12
2-12

2-12
2-13

2-13
2-13
2-13

2-14
2-14
2-14

2-14

BACKUP/RESTORE Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.1
Larger Block Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.2
Larger Buffer Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.3
Improved Exit Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.4
Pre-extended Disk Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.5
Temporary Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOGIN Datemme Attribute Updated . . . . . . . . . . . . . . . . . . . . . . . .
2.5.6
2.5.7
TUNE Privilege No Longer Required . . . . . . . . . . . . . . . . . . . . . . . .
2.5.8
INSTAL Privilege No Longer Required . . . . . . . . . . . . . . . . . . . . . . .

2-14

Print/Batch Services (PBS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW ENTRY Display Format . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.1
2.6.2
Automatic File Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.3
New User Request Packet Field . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.4
Batch Exit Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.5
PBS Operator Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-16

2-14
2-15
2-15
2-15

2-15
2-16
2-16

2-16

2-17

2-17
2-17
2-17

2-18

2.7

Commonly Used System Programs (CUSPs) ........................ .
2.7.1
ANALYS .......................................... .
DIRECT .......................................... .
2.7.2
DSKCVT ......................................... .
2.7.3
DSKINT .......................................... .
2.7.4
DSKSEK ......................................... .
2.7.5
Error Package ...................................... .
2.7.6
LOGIN ........................................... .
2.7.7
LOGOUT ......................................... .
2.7.8
ODT ............................................ .
2.7.9
ONLCLN ......................................... .
2.7.10
OPSER Package .................................... .
2.7.11
PIP.SAV ....................................... , .. .
2.7.12
REORDR ......................................... .
2.7.13
SHUTUP ......................................... .
2.7.14

2-18
2-19
2-19
2-19
2-19
2-19
2-19
2-20
2-20
2-20
2-21
2-21
2-21
2-22
2-22

2.8

BASIC-PLUS .............................................. .
2.8.1
BASIC-PLUS Debugging ............................... .
2.8.2
Extended Logicals Support ............................. .
2.8.2.1
ASSIGN Command .......................... .
DEASSIGN Command ........................ .
2.8.2.2
HELLO and BYE Commands .................... ~ ....... .
2.8.3
Old-Format SEND/RECEIVE Calls ........................ .
2.8.4

2-22
2-22
2-22
2-23
2-23
2-23
2-23

2.9

RSX-11

2-24

2.10

RT-11

2.11

RMS-11
2.11.1
2.11.2
2.11.3

Chapter 3

2-24

RMS-11 Macro Library ................................ .
RMS-11 Access Methods .............................. .
RMS-11 Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-24
2-24
2-24
2-25

Documentation Changes

3.1

New RSTSIE Version 10.0 Internals and Data Structures Manual

3-1

3.2

Revised Manuals , .......................................... .

3-1

3.3

New Documentation Binders ................................... .

3-2

3.4

Documentation Additions ..................................... .
3.4.1
Maintenance Notebook ................................ .
System Directives Manual .............................. .
3.4.2
3.4.3
Programming Manual ................................. .

3-2
3-2
3-7
3-7

Chapter 4

................................................... .

Layered Products

4.1

DATATRIEVE-11 ............................................ .
4.1.1
Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2
4-2
4-3

4.2

DECdx ................................................... .

4-3

4.3

DECmail-11 ............................................... .

4-3

DECnet/E ...........................................•......
4.4.1
Changes ......................................... .
4.4.1 .1
Utility Library Changes ........................ .
4.4.1 .2
Database Format Changes ..................... .
4.4.1.3
NFT/FAL ................................. .
4.4.2
Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.1
File Access Listener (FAL) Utility ................. .
4.4.2.2
Network File Transfer (NFT) Program .............. .
Installation and Update ........................ .
4.4.2.3

4-3
4-4
4-4
4-4
4-4

4.5

DIBOL ................................................... .

4-6

4.6

FORTRAN-77 .............................................. .

4-7

4.7

WPS-PLUS/RSTS V1.1 ........................................ .

4-7

4.4

(
\

Chapter 5

(

4-5
4-5
4-6
4-6

Corrections

5.1

Installation ................................................ .

5--1

5.2

INIT.SYS ................................................. .

5--2

5.3

Monitor .................................................. .
5.3.1
DEQNAlDELQA Device Driver ........................... .

5--2
5-4

5.4

DCL
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
5.4.8
5.4.9
5.4.10
5.4.11
5.4.12

5-4
5-4
5--5
5--5
5--5
5--5
5--5
5--5

CREATE/ACCOUNT Command .......................... .
GOSUB Command ................................... .
INITIALIZE Command ................................. .
MOUNT Command ................................... .
REMOVE/OVERLAY .................................. .
SET NODE/LAT/ACCESS=DIALUP ........................ .
SET PASSWORD ................................... .
SET TERMINAL Command ............................. .
SHOW DEVICE Command ............................. .
SHOW NODE/LAT ................................... .
SHOW QUOTA Command .............................. .
lime Format ....................................... .

5--6
5--6
5--6
5--7
5--7

5.5

BACKUP/RESTORE Package ................................... .

5--7

5.6

Print/Batch Services (PBS) .................................... .

5--8

5.7

Commonly Used System Programs (CUSPs) ........................ .
5.7.1
ANALYS .......................................... .
5.7.2
DSKSEK ......................................... .
5.7.3
MEMORY ......................................... .
5.7.4
OPSER .......................................... .
5.7.5
PIP ............................................. .
RECOVR.COM ..................................... .
5.7.6
SYSTAT .......................................... .
5.7.7
ODT ............................................ .
5.7.8

5--8
5--8
5--9
5--9
5--9
5--9
5--9
5--9
5--10

5.8

RMS-11
5.8.1
5.8.2

5--10
5--10
5--10

RMS-11 Access Methods .............................. .
RMS-11 Remote Access Methods ......................... .

vii

Chapter 6

Restrictions

6.1

Small Memory Systems

6-1

6.2

Installation ................................................ .

6-2

6.3

INIT.SVS ................................................. .

6-3

6.4

Monitor .................................................. .
6.4.1
Escape Sequences in Prompts ........................... .
6.4.2
UU.ATR Directive .................................... .

6-3
6-3
6-4

6.5

DCl
6.5.1
6:5.2
6.5.3
6.5.4
6.5.5
6.5.6
6.5.7
6.5.8
6.5.9
6.5.10

6-4
6-4
6-5

6.6

6-5
6-5
6-6
6-6
6-6
6-6
6-6

6-7
6-7
6-7
6-7
6-7
6-7

BACKUP/RESTORE Package ................................... .
6.6.1
AFTER File Selection ................................. .
BACKUP/COPY Command ............................. .
6.6.2
6.6.3
BACKUP/IMAGE Command ............................. .
6.6.3.1
HOOK Failure .............................. .
6.6.3.2
Initialization Errors ........................... .
6.6.4
BEFORE File Selection ................................ .
6.6.5
/MODIFIED Times ................................... .
RESTORE Command ................................. .
6.6.6
6.6.6.1
Error Recovery Handling ....................... .
6.6.6.2
Restoring VMS Savesets ....................... .

6-9
6-9
6-9
6-10
6-10

6.7

Print/Batch Services (PBS) .................................... .

6-10

6.8

Operator/Message Services Package ............................. .

6-11

6.9

Commonly Used System Programs (CUSPs) ........................ .
6.9.1
BPCREF ......................................... .
COPY ........................................... .
6.9.2
ODT ............................................ .
6.9.3
RUNOFF ......................................... .
6.9.4
6.9.5
PIP ............................................. .

6-11
6-11
6-11
6-11
6-11
6-12

6.10

RSX

6-12

6.11

RMS-11

6.11.1

viii

DCl Command Parsing ............................... .
DCl Error Handling .................................. .
F$ENVIRONMENT ................................... .
Language Compiler Commands .......................... .
lOGIN Command ................................... .
MOUNT/NOSHAREABlE Restriction ....................... .
/OUTPUT Qualifier ................................... .
RETURN Command .................................. .
SET TERMINAL Restrictions ............................ .
System Command Error Messages ........................ .

RMS-11 Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-8

6-12
6-12

Index

(

Tables

1-1
1-2

OMS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

F$ENVIRONMENT Items and Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-13
1-20
1-24

4-1

Layered Products Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1

New LAT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

(

(
\

Preface
The RSTS/E ~rsion 10.0 Release Notes describe new RSTSIE features for this
release, as well as differences between this and the previous release, RSTSIE
V9.7.
The procedure to install a new RSTSIE VIO.O system or to upgrade an existing
RSTSIE system to VIO.O follows the same general process developed for V9.0 and
later systems.
Because of the changes to the installation process starting with V9.0, users of
earlier versions of RSTSIE should read the RSTS / E System Installation and
Update Guide prior to attempting an installation of RSTSIE VIO.O.
If you are installing a new RSTSIE VIO.O system, refer to Part 1 of the RSTS / E
System Installation and Update Guide.
If you are upgrading a pre-V9.0 system to VIO.O, refer to Part 2 of the RSTS / E
System Installation and Update Guide.
If you are updating a RSTSIE V9.0 or later system to VIO.O, refer to Part 4 of the
RSTS / E System Installation and Update Guide.

In addition, users and programmers familiar with RSTSIE V9.7 should read these
notes to learn about changes and new features in RSTSIE VIO.O. The RSTS / E
Version 10.0 Release Notes are divided into the following chapters:
Chapter 1

New Features

Chapter 2

Differences Between VIO.O and V9.7

Chapter 3

Documentation Changes

Chapter 4

Layered Products

Chapter 5

Corrections

Chapter 6

Restrictions

NOTE

If you last used a version of RSTSIE prior to V9. 7, you should also read

the RSTS / E V9.x Release Notes for any intermediate versions.
Unless otherwise noted, all numeric values specified in these notes are decimal.

Chapter 1

New Features
This chapter describes the new features provided with RSTSIE V10.0.

1.1 New Hardware Support
This section describes any new PDP-11 hardware supported by RSTSIE V10.0.

1.1.1

Higher performance PDP-11/93, 11/94 Processors
The 11/93 and 11/94 are Digital's newest PDP-11 processors. These processors
fonn the basis for the highest perfonnance PDP-11 systems available. The 11/93
is used in Q-bus systems while the 11/94 is used in UNIBUS systems. Both
processors are available in either 2 megabyte or 4 megabyte onboard memory
configurations. These processors do not require a separate memory cache, since
the onboard memory enables the CPU to make all memory access at the same
high speed that a cache would offer.
Both processors are based on the proven DCJ11 and FPJ11 CMOS Processor
architecture. They provide more features than their older counterparts (the
11/73, 11/83 and 11184) while preserving the same fonn and fit for backward
compatibility. These new processors provide improved perfonnance (using 70 ns
cycle time memory), 7 additional serial lines (for a total of 8 DL11 compatible
serial lines), and an expanded setup menu and boot ROM (with 8K bytes of
customizable boot EEPROM). With the memory and serial lines all contained on
the CPU module, systems will require less power and backplane space. The 11/93
and 11/94 processors also include a battery operated time of year (TOY) clock.
Support for the 11/93 and 11/94 processors was previously announced for RSTSIE
V9.7 and required that patches 1.1.16F and 3.1.12F be installed. V10.0 adds full
parity memory support as well as support for the TOY clock. When booted, INIT
will detennine the system date and time from the TOY clock, so no one needs to
enter the date and time.
See the August 1990 RSTS / E Software Dispatch for additional infonnation on
these new PDP-11 processors.
NOTE

(

When you first start the KDJ11-E, the TOY clock will probably be set
to the wrong time for your timezone. Since RSTSIE uses the value in
the TOY clock to set the system time, Digital recommends that you set
the clock to the correct local time before you bootstrap your RSTSIE
medium. Please refer to the KDJJJ-E User's Guide for instructions on
how to do this.

New Features

1-1

1.1.2

RA70 and RA90 Disks
RSTSIE V10.0 supports RA70 and RA90 disks. Support for both disks was
announced in the December 1989 RSTS / E Software Dispatch.
RA70 disks are high-performance 5-1/4 inch, 280 megabyte drives. The RA70
can be housed in the B213-A Q-bus expansion cabinet, the SA550 storage array,
the SA650 storage array, or the SA705 removable storage array. Up to two RA70
drives can be housed in the B213-A for Q-bus systems. Up to eight drives can
be configured in the storage array cabinets for connection to either Q-bus or
UNIBUS systems. The SA550 allows for a combination of RA82 and RA70 drives
in the same cabinet. The SA650 allows for a combination of RA90 and RA70
drives in the same cabinet. The SA705 storage array allows only removable
RA70-RK drives.
RA90 disks are high-performance 1.2 gigabyte drives. Two RA90 drives can be
configured in a 10.5 inch high portion of a standard rack - the same physical
space as one RA81. Up to six drives can be configured in the RA90-C/FIHIJ
cabinet. Up to eight drives can be configured in the SA600 storage array, or the
SA650 storage array cabinet for connection to either Q-bus or UNIBUS systems.
The RA90, with a device cluster size of 64, is the largest capacity disk currently
supported by RSTSIE.
Both disks feature static dual porting like other DSA family disks. The RA70
and RA90 drives connect to Q-bus systems using the KDA50 controller, and to
UNIBUS systems using the UDA50 controller. RSTSIE suppbrts a maximum
of two UDA50IKDA50 type controllers. Each controller can be configured for a
maximum of four drives in any combination ofRA60, RA70, RA80, RA81, RA82,
or RA90 disks. Where multiple systems are configured, larger numbers of drives
can be configured to share the same storage array cabinet while being cabled to
different systems.

1.1.3

LA324 Desktop Printer
RSTSIE V10.0 includes support for the LA324 desktop printer. The LA324 is a
wide-carriage 24-wire impact dot matrix printer that replaces the DEC LA120
and LA210. It has the following features:
•

Barcode printing capability

•

Sixel character set support

•

Bold, slant, underline, overline, double underline, strike-through, subscripting, and superscripting printing support

•

Draft or letter-quality modes

•

Serial and parallel interface

•

Color printing capability with color ribbon

•

Handling for cut sheets, fanfold paper, envelopes, labels, multipart forms

•

Demand document operation which assures no wasted paper

•

Paper parking feature which allows you to use single sheets without removing
fanfold paper

Use the DCL command SET TERMINAUDEVICE-TYPE=LA324 to set default
characteristics for the LA324 printer.

1-2

New Features

1.2 New Software Featu res
(

This section describes the new software features included with RSTSIE V10.O.

1.2.1

Command Line Editing and Command Recall
RSTSIE V10.O supports Command Line Editing and Command Recall. These two
features significantly improve productivity by reducing the amount of keystrokes
required to enter commands or correct typing errors. Because these features are
implemented in the RSTSIE monitor, they are available almost everywhere in the
system: at the DCL command level, within other keyboard monitors, and at the
application program level.

1.2.1.1

Command Line Editing

In previous versions of RSTSIE the only two line editing functions were:
•

The Delete or Rubout key to delete the previously typed character (to the left
of the cursor)

•

CtrllU to delete the entire line

This made it difficult to correct errors discovered near the beginning of a command; you could either delete all characters back to the character to be corrected,
or delete the line and re-enter it. There was no way to move the cursor within
the line to make corrections.

V10.O makes such editing much easier by adding several new line editing functions. You can now:
• Move the cursor left or right one character
• Move the cursor to the beginning or end of the line
• Delete the previous word
• Delete to the beginning of the line
• Insert a new character at the cursor position
• Overstrike (replace) an existing character at the cursor position
These new functions reduce the amount of typing required to correct errors or,
when coupled with the new Command Recall feature, modify and re-execute
already entered commands.
1.2.1.2

Command Recall

V10.O provides a related feature called Command Recall. This feature allows you
to recall your most recently entered commands or program input lines. Command
Recall extends line editing even more, since it allows you to recall and change
commands or program lines after they have already been entered and executed.
This saves significant time in re-entering the same command (such as editing
the same file multiple times) or correcting a command that did not execute as
expected.
RSTSIE provides three separate Command Recall buffers: one for DCL commands, one for commands entered in other keyboard monitors, and a third for
program input. If there is not enough room in a recall buffer to store the current
command, then one or more of the oldest commands in the buffer are erased to
make room for the new one. Section 1.2.1.5 describes the use of these buffers in
greater detail.

New Features

1-3

Use the standard Up Arrow and Down Arrow terminal keys to move backward or
forward in the current recall buffer. (For terminals that do not have arrow keys,
use CtrllB and CtrllN.)
A new DCL command, RECALL, is provided to manage your DeL Command
Recall buffer. Use the RECALL command to:
• Display all of your saved commands
• Erase aU of your saved commands
.. Recall a saved command by index number
• Recall a saved command by text
See Section 1.2.11.15 for more details on the RECALL command.
1.2.1.3

System Changes

To accommodate the new Command Line Editing and Recall features, the fonowing changes have been made to the system:
..

By default, the Escape Sequence terminal attribute is now enabled.
Previously, all terminals were initialized with the Escape Sequence attribute
disabled.
The Escape Sequence attribute must be enabled to anow Command Line
Editing and Command Recall via the terminal's arrow keys within a program.
The Escape Sequence setting is ignored when commands are read by DCL or
other keyboard monitors.

Several control characters now have different meanings. These keys are
described in Section 1.2.1.7. Of special interest are the following:
Ctrl/D - When line editing is enabled, CtrllD moves the cursor backwards (left) one character. Otherwise, CtrllD continues to act as it did in
previous versions.
CtrllH (BACKSPACE) - When line editing is enabled, CtrllH moves the
cursor to the beginning of the line. Otherwise, CtrllH continues to act as
the BACKSPACE character.
CtrllJ (LINE FEED) - When line editing is enabled, CtrllJ deletes the
word to the left of the cursor. Otherwise, CtrllJ continues to act as the
LINE FEED character.
CtrllU - When line editing is enabled, CtrllU deletes from the beginning
of the line to the cursor; characters from the cursor to the end of the line
are shifted to the beginning of the line. Otherwise, CtrllU acts as before:
it erases the entire line, echoes AU, and repositions the cursor at the start
of the next line.

1-4

New Features

Many changes have been made to the terminal Device Data Block (DDB).
These changes are documented in Chapter 13 of the new RSTS / E ViO
Internals and Data Structures Manual.
The locations of the terminal input buffer (TTINPT) and the echo control
(typeahead) buffer (TTINEC) have been exchanged. See Section 1.2.2.1.1 for
more information about this change.

1.2.1.4

Terminal Attributes

The Command Line Editing and Command Recall features are available on
all terminals capable of processing and displaying ANSI escape sequences those terminals with the ANSI terminal attribute. Command Line Editing is
automatically disabled on terminals set to NOANSI. Command Recall is still
available on terminals set NOANSI, but recalled commands are displayed on the
next line instead of the current line.

(

Two new terminal attributes control the availability of Command Line Editing
and Command Recall: LINE_EDITING and RECALL. These new attributes
control their functions only within an application or program; they do not apply
to commands entered at DCL or other keyboard monitors.
Command Line Editing and Command Recall are always available at the DCL
level, regardless of the LINE_EDITING and RECALL terminal attributes. They
are also available within most other keyboard monitors, unless the keyboard
monitor opens the terminal in a mode that forces the feature to be disabled,
for example, opening the terminal in binary mode. This is discussed further in
Section 1.2.1.6.
The following additional terminal attributes control how characters typed within
a line (where the cursor is not positioned at the end of the line) should be handled:
•

OVERSTRIKE mode - indicates that each new character should replace
(overstrike) the character positioned at the cursor.

•

INSERT mode - indicates that each new character should be inserted at the
current cursor position; characters to the right of the cursor are shifted right
one character to make room for the new character.

By default, terminals are initialized with OVERSTRIKE in effect. The terminal's
editing mode is in effect each time you begin editing a line. You can also type
CtrllA at any time to switch back and forth between INSERT and OVERSTRIKE
mode until you end the line with a delimiter.
All of these new terminal attributes are controlled using new SET TERMINAL
qualifiers, as described in Section 1.2.11.20.
1.2.1.5

Command Recall Buffers

RSTS/E VlO.O distinguishes the following three kinds of commands for purposes
of Command Recall:
•

DCL commands -

commands entered at the DCL prompt

•

Other keyboard monitor commands - commands or lines entered at other
keyboard monitors, such as BASIC-PLUS or RT-11

•

Program commands -lines entered in response to a program or application

The RSTS/E monitor maintains a separate recall buffer for each of the three
command types. Each job on the system is assigned its own set of buffers in a
new area of memory called thejob header. See Section 1.2.7 for more information
about job headers.

(

Since each recall buffer is limited in size, only a certain number of commands can
be stored and maintained. As newer commands are entered, the oldest commands
in the buffer are deleted. Unlike the recall buffer on VMS, the recall buffers on
RSTS/E are not limited to only 20 commands. Instead, RSTS/E will maintain as

New Features

1-5

many commands as will fit in the buffer. The actual number of commands saved
depends on the size of the buffer and the length of each command saved.
DCL commands are stored in their own recall buffer until you log out or
specifically erase them with the RECALLIERASE command. You can use the
RECALL/ALL command to list all of the commands available in the DCL recall
buffer, or the RECALL command to recall a specific command either by index
number or text. See Section 1.2.11.15 for more information on the new RECALL
command.
If you switch from DCL to another keyboard monitor, either with the SET

JOBIKEYBOARD_MONITOR command or the SWITCH system command (CCL),
RSTSIE creates a second recall buffer. All commands entered at this level are
stored and maintained separately from your DCL commands. Once you return to
the DCL command level, all of the commands entered at the keyboard monitor
level are erased and the DCL recall buffer is reactivated. This feature is especially useful for users who must occasionally switch to another keyboard monitor,
such as BASIC-PLUS, to perform a task not accessible from DCL, for example, compiling a BASIC-PLUS program. The separate buffer prevents non-DCL
commands from being stored in DCUs recall buffer.
A third recall buffer is provided for program input. Whenever a program initially
prompts for input from the terminal, the monitor creates a third-level recall
buffer. Lines entered at the program level are automatically saved and may be
recalled without any special coding on the part of the program. Program lines
will continue to be stored across program chains and CCLs until you return to
DCL or another keyboard monitor. At that time, the program's recall buffer is
erased and the DCL or other keyboard monitor's recall buffer is reactivated.
1.2.1.6

Terminal OPEN Modes

Certain programs, such as EDT and DECmail-11, use the terminal's arrow keys
or other control characters for their own purposes. Some keyboard monitors may
do the same. To allow these applications to continue operating as before, RSTSIE
will automatically disable Command Line Editing and Command Recall if a
program or keyboard monitor opens the terminal in any of the following modes:
• BINARY or ODT (MODE 1%)
• TECO (MODE 2%)
• ECHO CONTROL (MODE 8%)
In addition, the monitor will disable Command Line Editing and Command Recall
in any applications that use FMS.
Note that while in ESCAPE SEQUENCE mode (mode 256), Command Line
Editing and Command Recall are only available using control characters. The
arrow keys and function keys are available for the application's use.
For all other terminal open modes, the availability of Command Line Editing and
Command Recall is dependent on the LINE_EDITING and RECALL terminal
attributes.
Some programs that do not open the terminal in a mode that. automatically
disables Command Line Editing or Recall can still disable one or both functions
by issuing the Set Terminal Characteristics SYS call to tum off the
LINE_EDITING and RECALL attributes. Such programs should save the initial
state of these attributes and then restore them upon exit. See the RSTS IE V10.O
Programming Manual for further details.

1-6

New Features

1.2.1.7

Command Line Editing and Recall Keys

With only one exception, all Command Line Editing and Recall keys are identical
to those defined on VMS. The one exception is that RSTSIE defines the CtrllN key
to recall the next (more recent) command in the recall buffer. VMS has no such
control key defined. CtrllN has the same effect as the Down Arrow key. RSTSIE
provides the CtrllN key to complement the CtrllB (Recall Previous Command)
key, so that you can move backward and forward in the recall buffer while the
terminal is open in Escape Sequence mode (mode 256).
The following is a list of the special Command Line Editing and Command Recall
keys. The online help topic Keys and the RSTS / E User's Guide also contain
information about the use of these keys.
•

Left Arrow or CtrllD -

Cursor Left

Moves the cursor left, or backward, one character position in the command
line. If the cursor is already at the beginning of the command line, the key is
ignored.
•

Right Arrow or CtrllF -

Cursor Right

Moves the cursor right, or forward, one character position in the command
line. If the cursor is already at the end of the command line, the key is
ignored.
•

Ctrl/H (BACKSPACE) or F12 - Beginning of Line
Moves the cursor to the beginning of the command line. If the cursor is
already at the beginning of the command line, the key is ignored.

•

CtrllE -

End of Line

Moves the cursor to the end of the command line. If the cursor is already at
the end of the command line, the key is ignored.
•

CtrllA or F14 - Toggle OVERSTRIKEIINSERT Mode
Toggles between OVERSTRIKE mode and INSERT mode. When you enter or
recall a command, the initial mode is determined by your terminal's INSERT
or OVERSTRIKE attribute. The mode remains in effect until you press CtrllA
to switch modes, or press a line delimiter to end the command. Once you
press a line delimiter, the mode reverts back to the default indicated by the
terminal attribute.
When in OVERSTRIKE mode, each new character you type replaces the
character positioned under the cursor. When in INSERT mode, each new
character you type causes all characters from the cursor to the end of the line
to be shifted right one character to make room for the new character.

•

CtrllJ (LINE FEED) or F13 -

Delete Word

Deletes the word to the left of the cursor. If the cursor is already at the start
of the line, then the key is ignored.
Deleting a word will do the following:
•

Delete any consecutive spaces and tabs immediately to the left of the
cursor.

•

Delete any consecutive alphanumeric characters [A-Z, a-z, 0-9] immediately to the left of the cursor.

•

If no characters are deleted, then delete a single, nonalphanumeric,
character.

New Features

1-7

•

Ctrl/U -

Delete Line

Erases all characters from the beginning of the line to the cursor. Remaining
characters are shifted left to the beginning of the line.
On multiline commands, Ctrl/U will only delete the portion of the command
from the cursor to the left margin.
Ctrl/U behaves the same, whether Command Line Editing is enabled or not.
If the terminal is set to HARDCOPY, AU will be displayed and the remaining

portion of the command will be displayed on the next line, similar to earlier
versions of RSTSIE.
•

Ctr1JR -

Redisplay Line

Redisplays the current command line without changing the cursor position.
On multiline commands, the cursor will be moved to the left hand margin,
and spaces will be displayed until the cursor lines up under the start of the
command. For example, if you type a command which wraps onto a second
line and press Ctr1JR, the display - before and after - would look like this
(vertical lines indicate terminal margins):
AFTER "R

BEFORE "R
IPROMPT> Command wraps here I
land continues on 2nd line. I

IPROMPT> Command wraps herel
I
Command wraps here I
land continues on 2nd line. I

Unlike VMS, RSTSIE does not know the current command's prompt, so it
cannot re-display the prompt with the command when Ctr1JR is pressed.
•

Up Arrow or CtrllB - Recall Previous Command
Moves backward one command in the recall buffer, making the next previous
or earlier command entered the current command; any characters on the
current line are discarded. The cursor is positioned at the end of the recalled
command, regardless of the position of the cursor previous to the recall. Press
Return to execute the command or use one of the line editing keys to change
it.
If there are no more commands to recall, pressing the Up Arrow key erases

the current command and does not recall a command.
•

Down Arrow or CtrllN - Recall Next Command
Moves forward one command in the recall buffer, making the next or most
recently entered command the current command.
If there are no more commands to recall, pressing the Down Arrow key erases

the current command and does not recall a command.
1.2.1.8

Editing Multiline Commands

The following rules apply when editing multiline commands:
•

You can only move the cursor left or right or delete characters on the last
line of a multiline command. You cannot move the cursor from the last line
to a previous line of the command unless you first delete all of the characters
on the last line and delete the last character from the previous line (thereby
making the previous line the last line of the command).
If the cursor is positioned at the first character of the last line and you press

the LEFT ARROW or CtrllD key to move the cursor left (to the last character
of the previous line), then the key is ignored and the cursor does not move.
1-8

New Features

•

Pressing CtrllU when the cursor is positioned on the last line of a multiline
command line only erases characters to the beginning of that line, not to the
beginning of the entire command. As always, any characters from the cursor
to the end of that line are shifted left to the beginning of the line.

•

Similarly, pressing BACKSPACE or CtrllH when the cursor is positioned on
the last line of a multiline command only moves the cursor to the beginning
of that line, not to the beginning of the first line.

•

If you press LINE FEED or Ctrl/J to delete the word to the left of the cursor
and that word extends back to the previous line of a multiline command
(the word is split across two lines), then only those characters back to the
beginning of the current line are deleted. The remainder of the word at the
end of the previous line is not deleted.

Because of these limitations, you should try to avoid entering multiline commands
whenever possible. In some cases you can use DCL command abbreviations or
redefine frequently used long DCL command/qualifier strings to reduce the length
of your command. You can also redefine your terminal width to 132 columns (on
terminals that support the extended width feature) to allow for longer commands
on a single line.
1.2.1.9

SET HOST Behavior

When you use SET HOST to connect to a remote system (using the NET utility),
commands that you enter on your local system are sent to the remote system for
processing. There are two character transfer modes available during a network
connection: NORMAL mode and ODT mode. These modes are selected by typing
CtrllP (followed by Return if the current mode is normal mode) and entering
either ODT or NORMAL. The default is normal mode; characters are echoed by
the local system but the command is not sent to the remote system until a line
delimiter is entered. ODT mode instructs the NET program to open the local
terminal in binary mode, causing all characters to be echoed and sent to the
remote system as they are typed. NORMAL mode is the preferred mode as it
reduces network overhead for each character typed.
If LINE_EDITING and RECALL are enabled on the local system, then these
functions will also work when connected to a remote system, depending on the
SET HOST transfer mode in effect. If the connection is operating in ODT mode,
then the monitor will send all characters, including line editing and recall control
characters and escape sequences, to the remote system. If line editing and recall
are enabled on the remote system as well, assuming that the remote system is
running RSTSIE V10.0 or an operating system that supports such functions, then
those functions will be performed by the remote system. Otherwise, the special
characters will be processed according to the rules for the remote system.
If the SET HOST connection is operating in NORMAL mode and the
LINE_EDITING and RECALL terminal attributes are enabled, then the monitor
on the local system handles all line editing and recall functions, treating all
characters typed as data to the NET program. This means that, regardless of
your current level at the remote system, DCL, Keyboard Monitor, or Program,
all commands that you enter will be maintained in your local system's program
recall buffer.

This behavior effectively gives you full command line editing and recall on any
remote system that you connect to. However, some applications on the remote
system may assign functions to keys defined in V10.0 as Command Line Editing
or Command Recall function keys. For example, DECmail-ll defines the Right
Arrow key as Read Next Message and the Left Arrow key as Read Previous
Message. Because DECmail-ll opens the terminal in escape sequence mode,
New Features

1-9

the system automatically disables Command Line Editing (see Section 1.2.1.6),
thereby giving DECmail-ll full control of the left and right arrow keys. If you
attempt to run DECmail-ll on a remote system while in NORMAL transfer
mode and with LINE_EDITING enabled, the left and right arrow keys will be
intercepted and processed by your local system as line editing keys, effectively
blocking their use by DECmail-ll on the remote system. Because there are now
many more special editing keys defined than in previous versions of RSTSIE, you
may encounter more remote applications that do not correctly process certain
special keys.
There are two ways to overcome these problems. The easiest is to switch to
ODT mode while connected to the remote system. Doing so opens your terminal
in binary mode, thereby disabling local Command Line Editing and Command
Recall, and allowing any special line editing and recall keys to be passed to the
remote system. Alternatively, you can use the SET TERMINAL command to
disable Command Line Editing (INOLINE_EDITING) and/or Command Recall
(INORECALL) prior to issuing the SET HOST command to connect to the remote
system.
Note that this does not represent an actual change in behavior compared to
earlier RSTSIE versions. Prior to V10.O, arrow keys and other special function
keys did not work across a network connection unless you switched to ODT
transfer mode.
Thus, the behavior is different, but consistent in relation to your local system.
Since all commands are read by the NET program, they are stored and recalled
as program-level commands.
1.2.1.10

Software/Hardware Terminal Setup
If the [NO]EIGHT_BIT software terminal characteristic is different from the

hardware setting, the arrow keys will not work for edit or recall commands.
Pressing an arrow key generates either a 7 -bit or an 8-bit escape sequence,
depending on the terminal's hardware setting. The RSTSIE operating system receives and transmits either 7-bit or 8-bit escape sequences based on the terminal's
software setting. If these two settings do not match, then the arrow keys will not
behave as expected.
Other mismatches, such as different speeds or parity settings, can also cause
unpredictable results.
Use the SET TERMINAL command to ensure that the software settings match
the hardware characteristics of your terminal.

1.2.2

Echo On Read
A new feature of V10.O is Echo On Read. Echo On Read is the processing and
echoing of characters typed on a terminal only when a read occurs. In versions
of RSTSIE prior to V10.O, characters were processed and echoed as soon as you
typed them, even if no read was pending. In some instances, these typeahead
characters would be processed incorrectly. For example, if you begin typing your
password before LOGIN issues its Password: prompt, the characters you type
are echoed, since the terminal is not yet set to NOECHO mode. Another example
is the processing of escape sequences when starting the EDT text editor. On
startup, EDT disables the terminal's Escape Sequence attribute. However, if
you type ahead while EDT is starting up, and your terminal is set to Escape
Sequence, the characters you type will not be processed correctly; they will be

1-10

New Features

,---

processed based on your terminal's current settings and open modes rather than
those established at the time of the read.
Echo On Read solves all of these problems, and more. With the addition of
Command Line Editing and Recall, the position of the cursor on the command
line becomes more important than before. Without Echo On Read, the position of
the cursor with respect to the characters output to the terminal becomes erratic
and unpredictable. Consider the case of typing ahead while a DIRECTORY
command is being executed. The typeahead characters are echoed interspersed
with the directory listing characters, and editing the line becomes virtually
impossible. In such cases, you would need to type Ctrl/R to redisplay your
current command so you know where on the command line the cursor is located.
Echo On Read solves this problem as well.
As of V10.0, characters are stored in the typeahead buffer - but not processed
or echoed - if there is no outstanding read request. When a read is issued,
any characters in the type ahead buffer - up to the first line delimiter - are
processed. This ensures that any typeahead characters are processed based on
the correct terminal open mode, terminal characteristics, etc.
Echo On Read is compatible with the way VMS character processing is handled.
Special interrupt characters (for example Ctrllr and CtrllC) will continue to be
processed immediately, regardless of whether or not a read is outstanding.
Echo On Read in V10.0 has a very different look and feel than previous versions
of RSTSIE. Most noticeable is the lack of any visual cues when you type ahead
(since typeahead characters are no longer echoed until a read occurs). Some
inexperienced users may conclude that their terminal or the system is not
functioning properly. Users should be encouraged to type Ctrltr to see that their
terminal and the system are still operating.
1.2.2.1

Programming Considerations
There have been several changes to the system to support the new Echo On
Read feature. Echo On Read was designed and implemented in such a way as to
not require any changes to existing RSTSIE applications. Nonetheless, certain
applications that were designed to take advantage of the now obsolete Immediate
Echo feature may be affected.

The following sections discuss certain aspects of Echo On Read as it relates to
new or existing RSTSIE programs.
1.2.2.1.1

Use of Terminal Input Buffers
To better assist programs that examine the input buffer to determine if any

characters were typed at the terminal, RSTSIE V10.0 has exchanged the terminal input buffer (TTINPT) and the echo control or typeahead buffer (TTINEC)
locations. These buffers, each three words long, have simply switched locations.
The reason for this change is so that programs which examine the input buffer
via the UU.FCB directive to determine if any terminal characters were typed
since the last .READ will continue to work properly.
The UU.FCB system directive allows you to examine the first 14 words of the
terminal's DDB. This directive can be used only on a terminal which the program
currently has open. The most common use of this directive is to compare the
input start pointer with the end pointer to see if any characters were typed. With
Echo On Read, characters are not stored in the input buffer unless a read is
pending. Since you cannot issue a UU.FCB directive and a .READ directive at
the same time, the input buffer will never contain any characters. By exchanging

New Features

1-11

the locations of the input buffer and typeahead buffer, such programs will now be
examining the typeahead buffer, which win contain all characters typed since the
last .READ directive was satisfied.
Programs which use this method of detecting terminal input will continue to work
without modification. However, programs which scan other user's terminals for
input may require modification to change the buffer's address. The input and
typeahead buffers are no longer at the same address as they were prior to V10.0.
See Chapter 13 of the RSTS / E V10 Internals and Data Structures Manual for
more information about the layout and contents of the terminal DDB.
1.2.2.1.2

Conditional Reads

Conditional reads (terminal reads which include the RECORD 8192% modifier)
are one exception to the Echo On Read feature. Conditional reads are used when
an application does not want to stall waiting for terminal input. When issued,
the monitor returns data to the program only if a line of data (a line which has
been terminated with a delimiter) is available. Otherwise, the monitor returns an
error to the program.
It is assumed that programs which use the conditional read feature expect that
characters will still be echoed while the program continues doing other tasks
between conditional reads. Echo On Read would cause terminal input in these
cases to be fragmented, with only full lines echoed whenever a conditional read
results in data returned. This would be unacceptable for many applications that
use conditional terminal reads.

To avoid this problem, RSTSIE will, upon receipt of a conditional read request,
begin echoing and processing characters as they are typed, similar to typeahead
behavior prior to V10.0. Echoing of typeahead characters will stop when the next
line delimiter is typed. Typeahead echoing is re-enabled each time a conditional
read is issued, up to the next line delimiter.
To cancel this special conditional read state without issuing another read, close
the terminal's open channel. This clears the special read pending state, indicating
that typeahead characters should no longer be echoed immediately. Once the flag
is cleared, typeahead characters win be echoed on the next .READ from the
terminal.

1.2.3

Host Initiated lAT Connections
Host initiated LAT connections are now supported in RSTSIE V10.0. This feature
provides you with the ability to establish a connection from a RSTS system to
a remote device, such as a printer, modem or terminal, attached to an Ethernet
terminal server. For example, if you connect an LN03 printer to your server,
and set the proper characteristics of the remote port on the server according
to the guidelines described in the documentation for the server, users on any
RSTS system on the Ethernet could print files on that device. Host initiated LAT
connections allow you to distribute some of your resources over the entire local
area network rather than restricting them to individual local systems.
In general, terminals connected to terminal servers can now be used like any
other terminals on your system, including multiterminal service and other
special-purpose terminal uses. Once the steps to define and set up a local LAT
terminal are completed (generally as part of system startup), you can use LAT
terminals as you would any other terminals.

1-12

New Features

The remaining sections describe how to set up and use local LAT terminals on
your system.
1.2.3.1

LAT Ports

LAT ports are different than most terminals on your system since they are not
physically connected to the system using terminal interfaces. Instead, RSTSIE
connects LAT ports to terminal server ports using Ethernet hardware and software.
LAT ports are like pseudo-keyboards and other dynamic keyboards in that they
are not assigned a unique keyboard unit number until they are created. Dynamic
keyboards are numbered sequentially, starting with the first available keyboard
unit number greater than the maximum physical (static) keyboard unit number.
Like other dynamic keyboards on RSTSIE, LAT ports can be referenced using
standard keyboard syntax, for example, KB45:, or device controller syntax,
such as KBI3:. The controller designator I is used to identify LAT ports. When
creating a LAT port, you can either specify the number of the port you want to
create, or let the system pick the next available number.
1.2.3.2

New Commands for Host Initiated LAT Connections

Table 1-1 lists all of the new DCL commands provided to support local LAT ports
for use in host-initiated LAT connections. See Section 1.2.11 or use the HELP
command for a complete description of these commands.
Table 1-1:

1.2.3.3

New LAT Commands

Command

Description

ASSIGNIPORT

Assigns or reassigns a LAT port to a remote port andJor service
on a terminal server

CREATEIPORT

Logically creates a LAT port

DEASSIGNIPORT

Deassigns a LAT port from a remote port and/or service on a
terminal server

DELETEIPORT

Logically deletes a LAT port

SET PORT

Modifies the characteristics of a LAT port

SHOW PORT

Displays the characteristics of a LAT port

Getting Started

Before you can begin using host initiated LAT connections, you must first create
a local LAT terminal port and then assign it to a remote port and/or service on
a terminal server. To create a local LAT terminal port, issue the DCL command
CREATEIPORT. For example, the following command creates a LAT port using
dynamic keyboard line KBIO: (KB47: in the example):
$ CREATE/PORT _KBIO:
Port KB47:
created

If desired, you can also assign the LAT port to a remote port and/or service

on the terminal server at the the same time you create the LAT port. Use the
/TERMINAL_SERVER qualifier to specify the name of the server to use; the
/REMOTE_PORT qualifier to specify the name of the remote port on the server
that the device is connected to; and/or the /SERVICE qualifier to specify the
service on the server you want to use.

New Features

1-13

For example, the following command creates a LAT port using keyboard KB47:
and assigns it to port PORT_72 on terminal server LAT890:
$ CREATE/PORT KB47: /TERMINAL SERVER=LAT890 /REMOTE PORT=PORT 72 /SERVICE=PRINT
Port KB47:
created
Port KB47:
assigned with queueing to terminal-server LAT890
remote-service PRINT
remote-port
PORT 72

Similarly, the following command creates a LAT port using dynamic keyboard line
KBIO: and assigns it to any port on terminal server LAT890 offering the service
named LN03:
$ CREATE/PORT/TERMINAL_SERVER=LAT890/SERVICE=LN03 KBIO:
Port KB47:
created
Port KB47:
assigned with queueing to terminal-server LAT890
remote-service LN03

You can specify the name of the port to create using standard keyboard syntax (KEn:) or controller syntax (KEIn: for dynamic keyboards), or simply let
the system select the next available dynamic keyboard number to use (the
CREATEIPORT command displays the designator of the keyboard used to create
the LAT port). In cases where you have applications that must reference a LAT
port via a specific device designator (such as PBS print servers) you must be careful to ensure that the LAT port is created using the correct keyboard or controller
syntax designator. Otherwise, the desired port may be unavailable or already
assigned to another job or function. This problem is best avoided by creating
all necessary LAT ports in the START. COM system startup command file before
other users or jobs can create them.
NOTE

When adding commands to your START.COM file to create LAT ports
for use as print servers in PBS, before you start PBS, you must create
the required LAT ports. PBS expects any local LAT ports defined as
print servers to have already been created when it initializes its print
servers at startup.
Once the LAT port is created, you can set the characteristics of the port using the
SET TERMINAL command as you would for any standard terminal. By default,
a newly created LAT port has the settings of a hardcopy terminal. For example,
if port KB60: is assigned to a port on a terminal server which has an LN03
printer connected to it, you would issue the following command to set the port's
characteristics to that of an LN03:
$ SET TERMINAL/DEVICE=LN03/PERMANENT KB60:

A LAT port must be assigned to a terminal server port or service before it can be
used. If you do not assign a LAT port to a terminal server at the time the port
is created, or you want to reassign the port to a different terminal server, port or
service, use the ASSIGNIPORT command. For example, the following command
assigns LAT port KB47: to port PORT_72 on terminal server LAT890:
$ ASSIGN/PORT/REMOTE PORT=PORT 72 KB47: LAT890
Port KB47:
assigned with queueing to terminal-server LAT890
remote-port
PORT 72

1-14

New Features

Use the SET PORT command to set individual LAT port characteristics, such
as queueing (see next section). For example, the following command disables
queueing of all connection requests onLAT port KB47::
$ SET PORT/NOQUEUED KB47:
Port KB47: not queued

You can also use the SET PORT command to assign a port to a different remote
port and/or service on a terminal server, similar to the ASSIGNIPORT command.
For example, the followng command changes the service on LAT port KBIO: to
PRINT_SERVICE and disassociates any remote port name from the LAT port:
$ SET PORT/SERVICE=PRINT SERVICE/NOREMOTE PORT KBIO
Port KB9:
characteristics set as requested
Port KB9:
assigned with queueing to terminal-server SERV 1
remote-service PRINT SERVICE

Once a LAT port is created, it can be deleted by using the DELETEIPORT
command. For example, the following command deletes LAT port KB47::
$ DELETE/PORT KB47
Port KB47: deleted

If a session is active when this command is issued, the port is not deleted until

the session is finished. The session can be aborted and the port immediately
deleted by specifying the IABORT qualifier when issuing the DELETEIPORT
command.
You can also use the DEASSIGNIPORT command to deassign a LAT port from
a terminal server port and/or service. For example, the following command
deassigns LAT port KB47: from its current remote port and/or service on a
terminal server:
$ DEASSIGN/PORT KB47:
Port KB47: deassigned

Note that the DEASSIGNIPORT command is generally unnecessary since you
can use the ASSIGNIPORT command to assign a LAT port to a different server,
remote port, or service without first deassigning it.
1.2.3.4

LAT Queueing

One of the capabilities offered by some terminal servers is the ability to place
host initiated requests that cannot immediately be processed on a queue. This
will occur when the remote port is busy with another request. When the remote
port becomes available, the server notifies the requesting host node that the
connection can now be established. On RSTSIE, local LAT ports are created with
queued access as the default. You can change the port's setting to noqueued
access by including the /NOQUEUED qualifier on the CREATEIPORT command
when the port is created, or the ASSIGNIPORT or SET PORT commands after the
port is created. If you set the local LAT port to noqueued access, then the server
will reject the connection request if the remote port is not currently available.
Likewise, you can change the port's setting to queued access by including the
IQUEUED qualifier on the same commands.
NOTE

Not all terminal servers provide queueing. Refer to the server's documentation to determine whether or not this feature is available.

New Features

1-15

1.2.3.5

Programming Considerations

Existing applications that perform terminal I/O will generally work without
modification. Some applications may require changes, depending on how they
were designed to open terminals and perform terminal 1/0.
For local LAT ports, the request to initiate a connection takes place when the
port is first assigned or opened. Because the connection request can be delayed
for a period of time, the assign or open request always completes immediately,
even though the connection is not yet established. If the connection is established
when the first write request for the terminal is issued, then the write completes
normally. However, if the connection is still not established when the program
issues a write request for the terminal, the action taken depends on the type of
write operation:
•

All except NOSTALL writes:
If a normal write request (all except NOSTALL writes) is issued and the

connection is still not completed, then the user's job is stalled in a TT state
until one of the following conditions occur:
The connection is established, at which time the write request is processed.
The connection is rejected or times out, in which case the error ?I/O to
detached keyboard is returned.
•

NOSTALL writes:
If the write request is a NOSTALL write, then the user's job is not stalled

and one of the following events will occur:
The connection has been established, in which case the write request is
processed.
The connection request is still being processed, in which case the error
?Device not available is returned immediately.
The connection is rejected or times out, in which case the error ?I/O to
detached keyboard is returned immediately.
Note that an application issuing NOSTALL writes can, if it receives the
?Device not available error, simply reissue the write request until the
connection is established.
Some application programs may need to be modified to handle these types of
conditions specific to host initiated LAT ports.
A new SYS call, Return Local LAT Port Status, allows application programs
to find out the current status of the port. In addition, the SYS call will also
return the queue position if the request has been queued, and reject reason
code if the request was rejected. With this SYS call, application programs can
continually reissue the call after assigning or opening the port waiting for the
establishment or rejection of the connection before attempting any I/O. This
provides the application program with the flexibility of doing other tasks while
waiting for the connection to be established. See the RSTS / E Programming
Manual for further details on this SYS call.

1-16

New Features

1.2.3.6

Dial-out Modems

Applications written for dial-out modem access should work without modifications. To use this feature, first:
•

Connect the modem to a port on the server following the guidelines detailed
in your 'Ierminal Server's User Manual.

•

Create the local LAT port on a RSTS system using the CREATEIPORT
command, and assign it to the remote port and/or service on the server using
the ASSIGNIPORT command.

•

Set the characteristics of the newly created port via the SET TERMINAL
command as you would any static terminal line, except for the DIALUP characteristic. Because the server is connected directly to the modem, the server,
not RSTS, handles all necessary modem signals. Therefore the /DIALUP
characteristic should not be set. An error is issued if you attempt to set the
/DIALUP characteristic on any LAT port.
NOTE

If a user logs in from a terminal connected to a terminal server

modem, RSTSIE will correctly recognize the user's access type as
DIALUP. This occurs because the server includes information with
its connection request indicating that the connection is through a
modem.
See Section 2.4.17 for details on the new SET NODEILAT qualifier
IACCESS for handling LAT connections from terminal servers that
do not adhere to this standard.
Once the steps outlined above have been taken, the port is ready to be used.
No further action is required.

1.2.4

Extended Logicals
The following significant enhancements have been made to extend the use of
system and user logicals in V10.0:

•

Longer Logicals
Previously, user logical names were limited to 6 characters while system
logical names could be up to 9 characters long. As ofV10.0, both system and
user logical names can be up to 15 characters in length. Extended logical
names provide for more meaningful mnemonics when defining logicals.

•

More User Logicals
Previously, users could only define a maximum of three logicals, (four if no
account PPNs were included in any logical definition). In V10.0, users can
define significantly more logicals. A 1K-word buffer is provided for each job to
store a user's logical definitions. The actual number of user logicals that can
be defined depends on the length of each logical name defined. Typically, as
many as 100 logicals can now be defined for each job on the system.

•

Extended Logical Name Characters
Previously, user logical names could consist of only alphanumeric characters.
System logical names also allow the use of a dollar sign character within the
name. In V10.0, both user and system logicals allow the underscore character
C) as well. The underscore character makes it easy to separate words within
a logical name, such as MY_DISK or TEST_FILES$. Since underscores at the
New Features

1-17

start of a device specification prevent logical translation, they are not allowed
as the first character of a logical name.
NOTE

The dollar sign character ($) is only permitted in system logical
names. This allows a system logical to be defined in such a way
that it cannot be overridden by a user logical with the same name.
As before, system and user logicals are used to reference a device, an account, or
both. User logicals can be defined to override a system logical; RSTS/E scans the
user logical table before the system logical table when looking up a logical name.
The DCL command ASSIGN is used to define user logicals, while the command
ASSIGN/SYSTEM is used to define system logicals.
1.2.4.1

Compatibility

Previously, each job's user logicals were stored in a small region of the job's
address space, usually referred to as the job's low core. This area was of fixed
length, and could not be extended. In VIO.O, a buffer is reserved in the job
header region to store user logical assignments. Note that this change does not
reduce the size of virtual memory space available to programs. (See Section 1.2.7
for more information about job headers.)
Very few applications assign, deassign or list logicals directly. Most simply
accept and use logical names as part of file specs to open files or devices on the
system. Such applications will continue to work as before. Applications that do
manipulate logicals directly may require modifications. Of particular interest is
the new List User Logicals SYS call that provides a way to list all user logicals
and their definitions. See the RSTS / E Programming Manual for further details.
Although the monitor no longer stores logicals in the user low core logical area,
the monitor will continue to search that area when translating or deassigning
logicals. Logicals stored in areas other than the new job header logical area may
con:fl.ict with existing logicals, leading to unpredictable results.
Changes and enhancements have been made to several monitor directives to
support the new extended logicals in V10.0. These changes are summarized in
Section 2.3.6.

1.2.5

Operator/Message Services (OMS)
The Operator/Message Services (OMS) package represents a significant enhancement to the overall management of RSTSIE systems. Combined with the
PrintlBatch Services (PBS) package, OMS functionally replaces the OPSER
package.
OMS provides more powerful capabilities and an easier-to-use command interface
than its OPSER predecessor. OMS provides these general system functions:

Operator Messages and Requests
Users issue the REQUEST command to send messages to operators. Users
can also include the /REPLY qualifier to indicate that a reply is needed.
REQUEST/REPLY causes the user's job to be stalled until an operator replies
(via the new REPLY command) to the request or aborts the request, or the
user types Ctrl/C to cancel the request. The REQUESTIREPLY command can
be used to ask an operator to mount a disk or tape, change printer forms, or
to simply carryon a dialogue with an operator. See Section 2.4.14 for more
information about changes to the REQUEST command for V10.O.

1-18

New Features

•

Operator Terminals
A new SET TERMINAL qualifier, /OPERATOR_SERVICES, is provided to
enable a terminal to receive operator messages, requests or both. Unlike
the OPSER package, which only allowed one terminal to display operator
information, OMS allows any number of terminals, either logged-in or
logged-out, to act as operator terminals.
Operators can include a SET TERMINAL/OPERATOR_SERVICES command
in their LOGIN.COM files to begin receiving OMS messages and/or requests
whenever and wherever they log into the system.

•

System Messages
OMS receives event information, such as LOGIN attempts or printer offline
notices, from various system programs and broadcasts the messages to all
defined opera tor terminals.
A program interface to OMS is provided so that user programs can send
messages, requests or other commands to the OMS facility.

•

Message Logging
If requested to do so, OMS also records all messages, requests and replies

to requests in a specially-formatted OMS log file. A new command, SHOW
REQUESTS, allows you to examine entries in the OMS log file. Extensive
selection qualifiers are provided to allow you to display log file entries based
on the following:
• Request type (!REPLY)
• Facility name (lFACILITY)
• Date and time (/BEFORE and /SINCE)
• Job number (lJOB)
• User account (IUSER)
• Terminal number (/TERMINAL)
• Message text (/TEXT and !EXACT)

•

Disk/Tape Mount Support
The REQUEST command's !REPLY qualifier accepts an optional DCL symbol
name argument. For example, the following command causes the operator's
reply to be stored in the global symbol DISK_NAME for further processing:
$ REQUEST/REPLY=DISK_NAME/GLOBAL

You can use this feature within a Batch or DCL command procedure to
perform operator-assisted disk or tape mounting.

•

BACKUP and RESTORE Support
OMS provides support for mounting disks or tapes as part of a BACKUP
or RESTORE operation. This allows backups and restores to be performed
under Batch, since requests for mounting additional disk or tape volumes are
issued as operator requests instead of user prompts.

For complete details on how to use the new OMS facility, refer to the RSTS / E
System Manager's Guide.
1.2.5.1

Installing OMS

OMS is an optional package on RSTS!E, and is installed similar to other RSTS!E
packages. Because OMS provides systemwide operator services, Digital recommends that you always install and use OMS on your system.
See Section 2.2 for further details on how to install OMS.
New Features

1-19

1.2.5.2

OPSER Compatibility

While OMS is functionally compatible with the older OPSER package, it operates
and interfaces with the rest of the system quite differently.
If desired, you can operate OMS and OPSER concurrently. Note that all RSTSIE

system programs that previously sent messages to OPSER, such as LOGIN and
LOGOUT, now communicate with OMS instead.
User programs that send messages to OPSER must be modified to communicate with OMS. Refer to the LOGIN.BAS source program located in the V10.0
SOURCES package to see how to send messages to OMS from a BASIC-PLUS
program.
1.2.5.3

New DCl Commands For OMS

The OMS package introduces several new DCL commands for use by users
and operators. Table 1-2 lists these new commands. See the RSTS / E System
Manager's Guide, the RSTS / E User's Guide, or use the HELP command for a
complete description of these commands.
Table 1-2:

1.2.6

OMS Commands

Command

Description

SET OPERATOR_SERVICES

Changes the current settings of the OMS
package

SET TERMINAIJOPERATOR_SEVICES

Defines a terminal as an Operator terminal,
allowing it to receive messages and/or requests

SHOW OPERATOR_SERVICES

Displays the current status and settings of the
OMS package

START/OPERATOR_SERVICES

Starts the OperatorlMessage Services package

STOP/OPERATOR_SERVICES

Shuts down the OperatorlMessage Services
package

Request-Related Command

Description

Replies to or aborts a pending request, and
stores the reply in the OMS Log file

REQUEST

Broadcasts a message or request to all operators and operator terminals on the system,
and records the message or request in the
OMS Log file

SHOW REQUEST

Displays messages, requests and replies to
requests stored in the current OMS Log file or
an archived OMS Log file

New File Attribute Flags
RSTSIE V10.0 supports two new file attribute flags: [NO]IGNORE and
[NO]BACKUP. Both flags are used by the BACKUP command.
NOTE

These file attributes are not used by the new BACKUPIIMAGE and
BACKUP/COPY commands.

1-20

New Features

:---

The [NO]IGNORE flag indicates whether BACKUP will ignore this file during
a BACKUP operation. Use this flag for files that should always be excluded
from your everyday backup operations. Once a file is set to IGNORE, you do not
need to use the /EXCLUDE qualifier to exclude the file from a backup operation.
The default for all files is NOIGNORE, except for temporary files, that is, those
created with the CRTFQ monitor directive.
The [NO]BACKUP flag indicates how BACKUP should treat the data portion
of a file. If NO BACKUP is set, the file's attributes (name, type, size, and so
forth) will be included in the backup operation, but the file's actual data will
not. A RESTORE operation will restore such a file to its original size, although
its contents will be random. Assign the NOBACKUP attribute to files whose
contents are highly volatile, such as the system swap files. The default for all
files is BACKUP.
Both attribute flags are maintained and displayed like any other RSTS/E file
attributes. Section 1.2.11.17 describes how to use the SET FILE command to
enable or disable these new file attributes.
The [NO]BACKUP file flag has the same meaning as on VMS. The [NO]IGNORE
file flag is specific to RSTS/E; it has no corresponding attribute on VMS.

1.2.7 Job Headers
RSTS/E V10.0 makes use of a new in-memory job structure called ajob header for
maintaining each user's logical definitions and previously entered commands or
program data for use by the new Command Recall feature. RSTS/E treats each
job's header as a logical extension of the job, swapping both the job and its header
in and out of memory as necessary. The new job header has no impact on a job's
virtual address space, and is transparent to the job itself.
Each job running on RSTS/E V10.0 requires an additional 2K-word region of
memory for its job header. As a result, the minimum SWAPMAX value for V10.0
is 34K-words, and the maximum is 66K-words, an increase of 2K-words over
the SWAPMAX range defined for V9.7. If you are already using a SWAPMAX
value larger than 32, then you will need to increase your system's SWAPMAX by
2K-words to account for the new job headers.
When you install V10.0, INIT.SYS will automatically rebuild the SWAP.SYS
file to support the larger SWAPMAX minimum. On I & D space systems with
SWAPMAX already defined to a value larger than 32, you can change the size of
SWAPMAX during installation to reflect the 2K-word increase for job headers.
To increase the size of the SWAP1.SYS swap file, answer YES to the installation
prompt:
Do you want _SYO:SWAP1.SYS created (at xxxx blocks)? <yes>

The installation procedure will create the SWAP1.SYS file at the correct size to
support the same number of jobs at the new SWAPMAX size.
Use the INSTALL/SWAPFILE command to recreate the SWAP1.SYS file on a disk
other than the system disk, or to recreate any other swap files (SWAPO.SYS or
SWAP3.SYS) on your system.
See Task 1, Phase 5 of the RSTS / E System Installation and Update Guide for
further information on creating swap files on your system.

New Features

1-21

1.2.8

LOGIN User Names
LOGIN has been enhanced to allow logging in using a (system) logical name
instead of a PPN. You can now respond to LOGIN's User: prompt with a system
logical name (without a trailing colon). The logical name specified must be a
system logical that translates into a valid PPN. If the logical definition also
includes a device, the device must be _SY: or _SYO:.
If the specified logical name is not translatable, translates to an invalid PPN,
or translates to a device other than _SY: or _SYO:, then LOGIN.TSK win still
prompt for a password and then display its ?Invalid entry - try again message.
Like any system logical, those defined for use in LOGIN can also be used in a file
specification. For example, the system logical name SMITH, defined as [10,30],
can be used in response to LOGIN's User: prompt to log into account [10,30], and
can also be used to reference a file in the [10,30] account on the public structure,
such as SMITH:FILES.DAT. The combination of these two uses of a system logical
can, in many cases, reduce or eliminate the need to know the actual PPN of a
user's account.
You may want to define system logicals for all of the interactive accounts on your
system, so that all users can log in using their own user names, similar to VMS.
Note that system logicals use space in XBUF, so you may need to increase the
size of XBUF to provide room for the additional system logicals. Also be aware
that a large number of system logicals may degrade system performance.
In cases where you cannot define system logicals for all users on your system,
you may still want to define logicals for certain accounts that are logged into
frequently or by many users. For example, you could define a system logical
DEMO for a special demonstration account on your system, so that users could
log into the account by entering the user name DEMO, without needing to know
the account's actual PPN.

1.2.9

New OPER Privilege
The new privilege, OPER (operator), has been added in VIO.O to control various
operator functions in the new Operator/M:essage Services (OMS) package. With
OPER privilege, a user can do the following:
.. Start, stop and modify the OMS package
Receive new operator messages and requests
• Reply to pending requests
0& Display previous operator messages and requests

See Section 1.2.5 for details on the new OMS package.
Since OPER is a new privilege, the VIO.O installation procedure allows you to
assign the new privilege to one or more accounts on the system. See Section 2.2
for further details.
The OPER privilege is supported like all other RSTSIE privileges. All monitor
directives, DeL commands, and programs that manipulate or display privileges
have been updated to include the OPER privilege.

1-22

New Features

1.2.10 Improved lOGIN Performance
Changes have been made to LOGIN.TSK and LOGIN.COM to reduce the time
required to log in to a RSTSIE V10.0 system. The actual time saved is dependent
on system load but should be visible to most users.
The following enhancements were made to improve overall LOGIN performance:
•

LOGIN.TSK now looks up various files previously looked up via the
F$SEARCH function by the system LOGIN.COM procedure. LOGIN.TSK
passes information about these files to the [0,1]LOGIN.COM procedure via
new bit flags in the P6 parameter.

•

Because of the change described above, the system LOGIN. COM procedure
has been greatly simplified. The P1-P5 parameters retain their same meanings as before but are, in some cases, superseded by bit flags in the new P6
parameter. Existing LOGIN. COM procedures that rely on those parameters
will continue to work without change. Read the [0,1]LOGIN.COM file listing
for an explanation ofthe parameters used by LOGIN.COM.

•

Some of the actions performed by LOGIN after a user entered his or her
password are now performed before the Password: prompt. While this does
not actually improve overall LOGIN time, it shortens the perceived LOGIN
time by reducing the delay between a user's password response and the DCL
$ prompt.
NOTE

Note that using a pre-V10.0 [0,1]LOGIN.COM file with V10.0 may
degrade overall login performance.
If you upgrade an existing RSTSIE system to Version 10.0, then the

latest system-wide LOGIN.COM file installs as [0,1]LOGIN.00L.
You must manually replace your existing [0,1]LOGIN.COM file with
the newest one to gain the performance benefits described. Be sure
[0,1]LOGIN.COM has a protection code of <104> and a run-time system
of DCL whenever you replace an existing [0,1]LOGIN.COM file.
Use the following DCL command to ensure that [0,1]LOGIN.COM has
the correct protection code and run-time system assigned:
SET FILE/PROTECTION=104/RUNTlME=DCL [O,l]LOGIN.COM

1.2.11

New DCl Commands and Qualifiers
This section describes new commands, qualifiers or features that have been added
to DCL for V10.0.

1.2.11.1

New F$ENVIRONMENT Function

A new function, F$ENVIRONMENT, has been added to DCL for V10.0. This function, compatible with the VMS function of the same name, provides a way for a
DCL command procedure to get information about the current DCL environment.
The format of the F$ENVIRONMENT function is:
value

=F$ENVmONMENT(item)

New Features

1-23

where value is the value returned by the function, and item is a string keyword
which defines the type of infonnation to be returned by the function. The function
can be used in symbol assignments or within a DCL expression and follows the
same rules as other DCL functions.
Table 1-3 lists each F$ENVIRONMENT item and its corresponding value.
Table 1-3:

F$ENVIRONMENT Items and Values

Item

Value Returned

CAPTIVE

Returns the string TRUE if the user's job is running in a
captive account, or FALSE otherwise.

CONTROL

When issued from a command procedure, returns the string
C if SET CONTROL=C is in effect, or the null string if SET
NOCONTROL=C is in effect.
When issued interactively, CONTROL always returns the null
string.

DATA

When issued from a command procedure, returns a string
indicating the current DATA setting. Possible values are:
DATA
DATAlEND_OF_DATA=c
NODATA
DATAlEND_OF_DATA=c (c = end-of-data character) is returned only if an end-of-data character other than $ is in
effect.
When issued interactively, DATA always returns the null
string.

DEFAULT

Returns as a string the user's current (logged-in) account
(PPN) in the form [proj,prog].

DEPTH

Returns as an integer the current command procedure depth
level. When issued interactively, DEPTH always returns O.
When issued from a command procedure, the DEPTH value
returned is one greater than the level of the procedure that
called it. Note: When issued from a batch job, DEPTH always
returns 2 or greater.

ECHO

Returns a string indicating the current ECHO setting. Possible
values are:
ECHO
NOECHOIWARNING
NOECHOINOWARNING
Returns as an integer the number of DCL channels currently
available, after taking into account any channels already in
use.t

INTERACTIVE

Returns the string TRUE if the current job's access mode is
INTERACTNE, or FALSE otherwise.
Returns as a string the specification of the currently open log
file, or a null string if no log file is open.

tDCL channels are used for the @ command (one per command procedure), the OPEN command (one
per open file), and the F$SEARCH function when used with a wildcard filespec argument (one per
command procedure).

(continued on next page)

1-24

New Features

I--~-

Table 1-3 (Cont.):

F$ENVIRONMENT Items and Values

Item

Value Returned

LOGFILE_PROMPT

Returns as a string the current DCL prompt displayed when a
log file is open. LOGFILE_PROMPT returns the same string
value as the DCL reserved symbol $LOGFILE_PROMPT.

MAX_DEPTH

Returns as an integer the maximum number of DCL command
procedures that can be nested, without regard to any DCL
channels currently in use. t

NOCONTROL

When issued from a command procedure, returns the string C
if SET NOCONTROL=C is in effect, or the null string if SET
CONTROL=C is in effect.
When issued interactively, NOCONTROL always returns the
null string.
When issued from a command procedure, returns the string
TRUE if an ON CONTROL_C THEN ... command is in
effect, or FALSE otherwise. When issued interactively, ON_
CONTROL_C always returns the string FALSE.
When issued from a command procedure, returns a string
indicating the severity level of the current ON <severity>
THEN command. Possible values are:
NONE (SET NOON)
WARNING (ON WARNING THEN ... )
ERROR (ON ERROR THEN ... )
SEVERE_ERROR (ON SEVERE_ERROR THEN ... )
When issued interactively, ON_SEVERITY returns the string
NONE.

PROCEDURE

Returns as a string the file specification of the command
procedure currently executing.
When issued interactively, PROCEDURE returns the null
string.

PROMPT

Returns as a string the currently defined DCL prompt string.
PROMPT returns the same string value as the DCL reserved
symbol $PROMPT.

PROTECTION

Returns as an integer the user's default file protection code. If
no default protection code has been specified, PROTECTION
returns the system default protection code 60.
Returns the string TRUE if log file time stamps are currently
enabled, or FALSE otherwise. If a log file is not currently
active, then TIME_STAMP returns the string FALSE.

VERIFY

Returns a string indicating the current VERIFY setting.
Possible values are:
VERIFY
VERIFYIDEBUG
NOVERIFY

New Features

1-25

Many of the item values returned by F$ENVIRONMENT are designed to make it
easy for a command procedure to save a current DCL setting and then restore it
later. For example:
$ DATA_SAVE = F$ENVIRONMENT ("DATA")
$
SET NODATA

$ SET 'DATA SAVE'

For further details about the F$ENVIRONMENT function, see Chapter 3 of the
RSTS / E Quick Reference Guide.
1.2.11.2

New ASSIGN/PORT Command

The ASSIGNIPORT command assigns a local LAT port on the RSTSIE node to a
port and/or service on a remote terminal server. You must first create a local port
with the CREATEIPORT command before you can assign it to a terminal server.
See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the ASSIGNIPORT command.
1.2.11.3

New CREATE/PORT Command

The CREATEIPORT command logically creates a local LAT port on the RSTSIE
node. Only application ports can be created. The CREATEIPORT command
can also be used to assign the new port to a terminal server, a remote service,
and/or a remote port, and to specify whether or not connections will be queued.
CREATEIPORT can also be used to assign a system logical or a user logical name
to the new port.
See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the CREATEIPORT command.
1.2.11.4

New BACKUP/IMAGE Command

BACKUPIIMAGE is a new feature that allows the asynchronous copying of a
file structured RSTSIE disk to another disk. You can use this feature to perform
disk-to-disk backups or to copy a disk's data to a newer disk as part of upgrading
your hardware.
BACKUPIIMAGE copies all accounts and files from the input disk to the output
disk. It functions similarly to the SAVRES IMAGE option, although it operates at
the file level of the disk instead of the cluster level. As a result, BACKUPIIMAGE
does not require that the input and output disks be the same size and type; you
can copy all of the accounts and files from any size disk to any other size disk
provided, of course, that the output disk is large enough to hold all of the data
from the source disk.
BACKUPIIMAGE uses the same asynchronous file copying technique used
by the standard BACKUP command. As a result, BACKUPIIMAGE is very
fast. For example, on an 11/83 system using a /BLOCK_SIZE value of 24576,
BACKUPIIMAGE can transfer all of the accounts and files from one RD54 disk to
another (approximately 293,000 blocks) in 23 minutes, an average transfer rate of
6.5 megabytes per minute.

1-26

N~w Features

,----

The following example illustrates how you would use the BACKUPIIMAGE
command to copy all of the data on SY: to DUl:
$ BACKUP/IMAGE SY: DU1:/INITIALIZE=(ERASE,NOEXERCISE,CLUSTERSIZE=8) /BUFFER SIZE=MAXIMUM /BLOCK SIZE=MAXIMUM /VERIFY
Please mount image output volume:
Press RETURN when ready:
This disk pack appears to be a RSTS/E formatted
disk with the following characteristics:
Pack ID :
Pack Cluster Size
Pack is currently

IMAGE
8

Private,
Update access on writes,
Level: 1.2

Proceed (Y or N)? Y
Writing accounts to image volume
Account
0, 2] written to volume 1
Account
0, 3] written to volume 1

Writing placed files to image volume
File [ 0,
1]RSTS96.SIL written to volume 1
File [ 0,
1]RSTS97.SIL written to volume 1

Writing non-placed files to image volume
File [ 0,
l]CONFIG.SYS written to volume 1
File [ 0,
l]TEST .DCL written to volume 1

Hooking the output volume
Account [ 0,
1] verified against volume 1
File [ 0,
1]RSTS96.SIL verified against volume 1
File [ 0,
1]RSTS97.SIL verified against volume 1
%Verification failure for file data for file [0,1]SWAP1.SYS
File [ 0,
1]SWAP1 .SYS verified against volume 1

Please dismount image output volume
$

See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the BACKUPIIMAGE command.
1.2.11.5

New BACKUP/COPY Command

A new BACKUP/COPY command has been added to allow you to copy
files, accounts or volumes from one disk to another using the BACKUP facility. BACKUP/COPY is a superset of the BACKUPIIMAGE command:
BACKUPIIMAGE provides disk-to-disk full volume copying, while BACKUP/COPY
lets you copy less than a full volume from one disk to another.
BACKUP/COPY is particularly useful when copying large amounts of data from
one disk to another, or from one account to another. BACKUP/COPY offers higher
performance than the standard COPY command (PIP), because of BACKUP's use
of asynchronous I/O. As with the BACKUp, BACKUPIIMAGE and RESTORE

New Features

1-27

commands, BACKUP/COPY may degrade overall system performance to achieve
its own high transfer rate.
For example, to transfer all of the files in the HELP$ account [0,2] on the system
disk to account [0,2] on the private disk _DU1:, use the command:
$ BACKUP/COPY HELP$:*.*

DU1:

BACKUP/COPY will create the [0,2] account on _DU1:, and then transfer aU of
the files from HELP$ on the system disk to the new account on DU1:.
See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the BACKUP/COPY command.
1.2.11.6

New BACKUP Verify-Only Operation

The !VERIFY qualifier to the BACKUP command now accepts the argument
=ONLY to perform a VERIFY operation on an existing backup set. Previously
you could only perform a VERIFY operation as part of a BACKUP or RESTORE
operation.
You can use the BACKUPNERIFY=ONLY command to determine which files
and/or accounts on a disk have changed since it was last backed up.
You can also use this feature to eliminate unnecessary rewinds and file searches
when creating multiple backup sets on magtape. By delaying the VERIFY
operation until all Backup sets have been created, you can avoid having to rewind
the tape and skipping over other Backup sets.
You can use BACKUPIIMAGEIVERIFY=ONLY to verify that two disks are the
same. You must do the BACKUP operation twice, first from disk A to disk B,
then from disk B to disk A. One operation verifies that all the accounts and files
on disk A are on disk B; the other, that all the accounts and files on disk B are on
disk A.
In some cases, you may get some verification errors with the account attributes
for [1,1] and [1,2] because DSKINT may have created those accounts and preextended them.
The actual order of files may be different on the two disks without causing any
verification errors. The boot block is not verified. Also, if the two disks have
different cluster sizes then some account or file attributes may not verify correctly.
1.2.11.7

New /INITIAUZE Arguments for BACKUP and RESTORE

The /INITIALIZE qualifier, as part of the BACKUP or RESTORE commands,
or in response to those command's volume mount prompts, will now accept the
following new argmnents:
=[NOJQUERY
=[NO]ERASE
=[NO]EXERCISE
=EXERCISE=n (n = 1, 2, or 3)
=CLUSTERSIZE=n Cn = 1, 2, 4, 8, 16, 32, or 64)
This will anow you to have more control over the initializing of disks as part of
a BACKUP or RESTORE operation, and will often eliminate having to perform
these operations separately.
These arguments have the same meaning and use as the INITIALIZE command
qualifiers by the same name. See the RSTS / E System Manager's Guide for more
details.

1-28

New Features

1.2.11.8

Operator-Assisted BACKUP and RESTORE

The BACKUPIRESTORE package now provides the /ASSIST qualifier to allow
operators to answer volume mount prompts during a BACKUP, RESTORE,
BACKUPIlMAGE, or BACKUP/COPY operation. The /ASSIST qualifier requires
that the new Operator Message Services (OMS) facility is installed and running.
This feature provides a powerful extension to the BACKUPIRESTORE package,
as it now allows for Backup and Restore operations to run under Batch, with the
assistance of a system operator to mount volumes as required.
The default is INOASSIST. If you want to perform a BACKUP or RESTORE
operation within a DCL command procedure running under Batch, be sure to
specify /ASSIST to request operator assistance.
/ASSIST causes the normal volume mount prompt to be sent to OMS as an
operator request. An operator replies to the volume mount request using the
REPLY command. An operator can reply in any of the following ways:
•

REPLY/ABORT terminates the operation, similar to typing Ctrl/Z in response
to the mount prompt.

•

REPLY/TO with text. If text is included with the reply, then the text is
taken as the response to the mount prompt. An operator can reply with any
valid response text to the prompt. For example, the following reply mounts
the (next) backup volume on disk _DMO:, and initializes it using several
initialization options:
$ REPLY/TO=317 "_DMO:/INIT=(NOERASE,NOEXERCISE,CLUSTERSIZE=16)"

•

1.2.11.9

REPLY/TO with no text. If no text is included with the reply, then the volume
mount default is taken, the same as if the user had pressed Return to the
mount prompt.

New /REPLACE=QUERY and /QUERY Options

By default, the RESTORE command prompts you before replacing any file it
encounters on the output disk. Similarly, the /QUERY qualifier in the BACKUP
and RESTORE commands prompts you for each file to select. Respond YES or
NO to these prompts to indicate your choice for the file displayed.
In some instances, your response to these prompts is always the same, all YES or
all NO. This can happen, for example, if you forget to include the IRE PLACE or
INOREPLACE qualifier with RESTORE, causing the default IREPLACE=QUERY
to force prompting for each possible file replacement encountered. In other cases,
your response may become the same - all YES or all NO - after responding to
a particular file prompt.
Rather than requiring you to answer each prompt, BACKUP now accepts an
optional/ALL qualifier with your YES or NO reply. /ALL means apply this
response to all future queries, thereby eliminating any further prompting. In the
case of IREPLACE=QUERY, YES/ALL causes all remaining files to be replaced,
while NO/ALL causes all remaining existing files to be skipped. In the case of
/QUERY, YES/ALL causes all remaining files to be selected, while NO/ALL causes
all remaining files to be skipped.

New Features

1-29

1.2.11.10

New DEASSIGN/PORT Command

The DEASSIGNIPORT command deassigns a local LAT port on the RSTSIE
node from the remote terminal server to which it was assigned. Issuing the
DEASSIGNIPORT command for a local port which has an active session will have
no effect on that session.
See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the DEASSIGNIPORT command.
1.2.11.11

New DELETE/PORT Command

The DELETEIPORT command logically deletes a local LAT port on the RSTSIE
node. If there is an active connection on the port when the DELETEIPORT
command is issued, the port is marked for deletion, then deleted when the
connection is over.
See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the DELETEIPORT command.
1.2.11.12

New FILE_UTILITY Overlay

The UU.FIL monitor directive is now heavily used in most file operations. To
improve file performance, a new overlay called FILE_UTILITY can be loaded
and unloaded from memory using the DCL commands LOAD/OVERLAY and
UNLOAD/OVERLAY.
1.2.11.13

New /NOTIFY Qualifier for PRINT and SUBMIT

The I[NO]NOTIFY qualifier has been added to the PRINT and SUBMIT commands. Print or Batch entries created with the !NOTIFY qualifier will cause
PBS to broadcast messages when there is a change to the entry's status. PBS
will broadcast these messages to an terminals logged in under the entry's owner
(PPN). Messages will be broadcast when:
• The entry starts .
.. The entry completes .
.. The queue deletes the entry.
Ii> The print server processing a print entry goes offline.
By default, entries are created with INONOTIFY.
1.2.11.14

New /[NO]OUTPUT Qualifier

The I[NO]OUTPUT qualifier has been added to most of the DCL SHOW commands (a few already supported it). This provides an easy way to direct the
output of a SHOW command to a file or print device. The INOOUTPUT format
is convenient for checking a command for errors or warnings (typically within a
command procedure); it suppresses all SHOW output, displaying only warning
and error messages.
The following DCL SHOW commands now accept the /[NO]OUTPUT qualifier:
.. SHOW CACHE
.. SHOW COMMAND/SYSTEM
.. SHOW DEVICE
.. SHOW ENTRY
.. SHOW FILE/SYSTEM
ill SHOW JOBIPRIVILEGE
.. SHOW LOGICAL
1-30

New Features

• SHOW PRINTER
• SHOW PORT
• SHOW QUEUE
• SHOW QUOTA
• SHOW SERVER
• SHOW SYSTEM
• SHOW TERMINAL
The following DCL SHOW commands, which already supported /OUTPUT, have
been extended to support the NO prefix. Additionally, these commands no longer
require a filename argument. If no filename is specified, then the information is
displayed on the terminal (as if the qualifier had not been included).
• SHOW ACCOUNTS
• SHOW BUFFERS
• SHOW COUNTERSILAT
• SHOW DEVICES/ALLOCATED
• SHOW DISKS
• SHOW FILES/OPEN
• SHOW JOBS
• SHOW LIBRARIES
• SHOW MEMORY
• SHOW NODEILAT
• SHOW RECEIVERS
• SHOW RUNTIME_SYSTEMS
• SHOW SESSIONS/LAT
• SHOW SERVICEILAT
• SHOW TERMINAL_SERVERSILAT
• SHOW USERS
The following DCL SHOW commands do not support the /[NO]OUTPUT qualifier.
If necessary, use the OPENILOG_FILE command to create a log file for saving
the output of these commands:
• SHOW DATE
• SHOW DAYTIME
• SHOW SYMBOLS
• SHOW TIME
The following commands support the /OUTPUT qualifier to allow output to a file,
but they do not support the NO prefix:
• DIFFERENCES
• DIRECTORY
• EDIT
• HELP
1.2.11.15

New RECALL Command

The RECALL command is used to:
•

List all of the commands in the recall buffer (RECALL/ALL).

•

Erase all of the commands in the recall buffer (RECALLIERASE).

•

Recall a command by its index number (RECALL n). For example, RECALL
1 recalls the most recently entered command.

•

Recall a specific command by its leading text (RECALL string). For example,
RECALL PRINT recalls the most recently entered PRINT command.

New Features

1-31

See the RSTS/E V10.O User's Guide or use the online HELP command for
complete details on use and format of the RECALL command.
1.2.11.16

New REPLY Command

The REPLY command is used by an operator to answer a pending request. The
operator can complete the request, abort the request, or answer the request while
keeping the request pending.
The REPLY command also supports the following VMS-compatible qualifiers:
•

/ENABLE
REPLYIENABLE enables your terminal as an operator terminal for your
current timesharing session, and displays any pending operator requests on
your terminal.

•

/DISABLE
REPLY/DISABLE disables your terminal as an operator terminal. If your
terminal was previously set as a permanent operator terminal (by issuing the
command SET TERMINAL/OPERATORIPERMANENT), then the terminal
will become an operator terminal again as soon as you log off.

•

/STATUS
REPLY/STATUS displays the status of your terminal as an operator terminal,
and displays any pending requests. If the terminal is not set to receive
REQUESTIREPLY messages, then pending requests will not be displayed.

See the RSTS / E System Manager's Guide or the online HELP topic REPLY for
more information.
1.2.11.17

New SET FILE Qualifiers

The SET FILE command now accepts the I[NO]IGNORE and I[NO]BACKUP
qualifiers. These file attributes are used exclusively by the BACKUP command
to ignore certain files during a backup operation, or to backup only a file's attributes (not its data). See Section 1.2.6 for more information about these new file
attributes.
NOTE

These file attributes only apply to the BACKUP command, not to the
BACKUPIIMAGE or BACKUP/COPY commands.
1.2.11.18

New SET OPERATOR_SERVICES Command

The SET OPERATOR_SERVICES command is used to change the current settings of the Operator/Message Services (OMS) package. See the RSTS / E System
Manager's Guide or the online HELP topic SET OPERATOR_SERVICES for more
information.
1.2.11.19

New SET PORT Command

The SET PORT command sets the characteristics of a LAT port on a RSTSIE
node.
See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the SET PORT command.

1-32

New Features

1.2.11.20

New SET TERMINAL Qualifiers

Several new qualifiers and associated terminal attributes have been added to
support Command Line Editing, Command Recall and the Operator/Message
Services package:
•

/INSERT
Puts the terminal in INSERT mode, making it the default mode when you
begin editing a line.

•

/[NO]LINE_EDITING
Enables or disables Command Line Editing at the program level.

•

/OPERATOR_SERVICES
Indicates that the terminal should receive operator messages (MESSAGES),
operator requests (REQUESTS), both or neither.

•

/OVERSTRIKE
Puts the terminal in OVERSTRIKE mode, making it the default mode when
you begin editing a line.

•

/[NO]RECALL
Enables or disables command line recall at the program level.

All of the above qualifiers can be specified with the /PERMANENT qualifier to
maintain the attribute's setting when the terminal is not in use. You must have
HWCTL privilege to specify /PERMANENT.
See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the SET TERMINAL command.
1.2.11.21

New SHOW ACCOUNT/FULL Fields

The SHOW ACCOUNTIFULL display now contains two new fields: UFD Size and
UFD Used. UFD Size is the size of the account's directory in clusters. The value
can range from 1 to 7 clusters, with the minimwn being the value specified with
the /SIZE qualifier on the CREATE/ACCOUNT command when the account was
created.
The UFD Used field shows what percentage of the account's directory space
is currently in use. The performance of file operations within an account will
degrade as the used percentage approaches 100 percent.
1.2.11.22

New SHOW ENTRY Status: FORMS_WAIT

A new status has been added to the SHOW ENTRY display. FORMS_WAIT
indicates that a Print or Batch entry cannot be started because its associated
form is not currently installed on any print server assigned to the entry's queue.
This new status keyword makes it easier to identify entries that require a forms
change.
1.2.11.23

New SHOW ENTRY Qualifier

A new qualifier, /STATUS, has been added to the SHOW ENTRY command to
allow you to select entries for display based on their current status.
The /STATUS qualifier accepts one or more status keyword argwnents. If you
specify multiple status keywords, then SHOW ENTRY displays those entries with
any of the specified status.
New Features

1-33

See the RSTS / E User's Guide or use the HELP command for further information
about the new /STATUS qualifier.
1.2.11.24

New SHOW OPERATOR_SERVICES Command

The SHOW OPERATOR_SERVICES command displays the current status and
settings of the Operator/Message Services (OMS) package. See the RSTS / E
System Manager's Guide or the online HELP topic SHOW OPERATOR_
SERVICES for more information.
1.2.11.25

New SHOW PORT Command

The SHOW PORT command displays the characteristics of LAT ports on the
RSTSIE node. By default, both interactive and application ports are displayed.
The information shown includes the local port name, the port type (either interactive or application), the queued setting, the terminal server name, the remote
service (if specified), the remote port (if specified), and the connection status.
If the port is not assigned to a terminal server, then only the local port name and
type are displayed. If the port is assigned but not yet connected, the requested

terminal server, remote service, and remote port are shown. If the port is waiting
to connect, the connection status In Progress is shown. If the connection is
queued, then the queue position is also displayed. If the port is connected, the
terminal server, the remote service and the remote port to which it is actually
connected are shown, and the job number is displayed.
See Chapter 8 in the RSTS / E System Manager's Guide for more information
about the SHOW PORT command.
1.2.11.26

New SHOW REQUEST Command

The SHOW REQUEST command displays messages and requests stored in the
Operator/Message Services (OMS) work file. You can select messages or requests
for display based on a variety of selection criteria (for example, ID number, date,
job or terminal number, or facility name). See the RSTS / E System Manager's
Guide or the online HELP topic SHOW REQUEST for more information.
1.2.11.27

New START/OPERATOR_SERVICES Command

The START/OPERATOR_SERVICES command starts the Operator/Message
Services (OMS) package. See the RSTS / E System Manager's Guide or the online
HELP topic START/OPERATOR_SERVICES for more information.
1.2.11.28

New STOP/OPERATOR_SERVICES Command

The STOP/OPERATOR_SERVICES command shuts down the Operator/Message
Services (OMS) package. See the RSTS / E System Manager's Guide or the online
HELP topic STOP/OPERATOR_SERVICES for more information.
1.2.11.29

New CC Command

The CC command invokes the PDP-ll C compiler if it is installed. See the Guide
to PDP-ll C for information.

1-34 New Features

1.2.11.30

New COPY ITRANSFER_MODE Qualifier

The COPY command now supports a new qualifier, !TRANSFER_MODE, to
specify which transfer mode - block or record - should be used to copy the file
to a remote node.
If the !TRANSFER_MODE qualifier is not specified, then the COpy command

determines the most appropriate mode to use in transferring the file.
This qualifier only applies to network file copy operations. DCL displays an error
if you include the qualifier with a local file copy command (no node name included
in either the input or output file specifications).
For further details on network transfer modes, see Section 4.4.1.3.

1.2.12 New RSX Directive -

MSDS$

The RSX directive Map Supervisor D-Space (MSDS$) allows a task to change the
mapping of its supervisor mode D-space APRs. This directive can also provide
information about the current mapping of the task's supervisor mode D-space
APRs or about a library's current mode.
For further information on using the MSDS$ directive, see the RSTS / E System
Directives Manual.

1.2.13

Easier BASIC-PLUS Installation
The installation and update of BASIC-PLUS run-time systems have been made
easier in VIO.O If there are existing BASIC-PLUS run-time systems in SY:[O,l],
then the BASIC-PLUS installation procedure will ask you if you want to update
those run-time systems. If you do, then no further questions will be asked to
update those run-time systems.
When you are creating new BASIC-PLUS run-time systems, you can use an
existing BASIC-PLUS run-time system as a template, similar to the template
feature used to build RSTSIE monitor SILs.
You can also create more than one BASIC-PLUS run-time system during the
installation process.
See the RSTS / E Installation and Update Guide for further details.

1.2.14 New CUSP Resident Library
The original CSPLIB.LIB resident library, first included with RSTSIE V9.0 and
used by many of the RSTSIE CUSPs, was built using BASIC-PLUS-2 V2.3. It was
also shipped with the modules required for users to link their own applications
against it.
For RSTSIE VIO.O, there is a new CUSP resident library called CSPIOO.LIB. This
library is built against BASIC-PLUS-2 V2.6. All of the RSTSIE CUSPs included
with VIO.O that previously used the CSPLIB library have been rebuilt to use the
new CSPIOO.LIB library.
The old CSPLIB.LIB resident library is no longer required by any of the RSTSIE
VIO.O CUSPs, but is still included with RSTSIE VlO.O for any existing user
programs that are linked against it. The SYSINI.COM procedure installs both
CSPIOO.LIB and CSPLIB.LIB during system startup. The START.COM file
includes a REMOVEILIBRARY command, which has been commented out, to
New Features

1-35

remove the CSPLIB.LIB library. If you do not need the CSPLIB.LIB resident
library on your system, then delete the exclamation point character from in front
of the command to remove the library during start up.
The support modules to link applications agaim'1t CRPUB .LTB nrp no lnnr;er
provided; only the support modules to link against CSPIOO.LIB are included
with RSTS/E VIO.O. Any new user programs that wish to make use of the
CSPIOO.LIB library win have to be compiled using BASIC-PLUS-2 V2.B. Digital
recommends that you do this; the CSPLIB.LIB library may not be included with
future versions of RSTSIE.

1.2.15

New SORT/MERGE Release
RSTSIE VIO.O includes a new release of SORTIMERGE, SORTIMERGE V3.1.
V3.1 is primarily a maintenance release, but includes substantially revised documentation. Refer to the SORTIMERGE documentation for complete information
on installing and using SORTIMERGE V3.1.

1-36

New Features

Chapter 2

Differences Between V10.0 and V9.7
This chapter describes the differences between RSTSIE VIO.O and RSTSIE V9.7.
For differences in layered products running on RSTSIE, see Chapter 4.

2.1

System Name
The edit level part of the system version number is now a single alphabetic
character instead of a 2-digit number, for example, VIO.O-L instead ofVI0.0-12.
This change was necessary to provide room for the extra digit in the RSTSIE
version number.

2.2 Installation
The following changes and enhancements have been made to the RSTSIE
installation procedure for VIO.O:
•

Larger SWAPMAX Range
The installation procedure has been changed to support the increased size
of SWAPMAX (see Section 1.2.7). The new SWAPMAX range is 34K to 66K
words. "

•

Improved Flag File Handling
The installation procedure uses a new key for its flag files. The key now
includes an edit level (baselevel) identifier along with the version number.

•

Improved Multivolume Handling
The installation procedure now handles multivolume media (such as 800
BPI magtapes and RL02 disks) more efficiently than before. The installation
procedure will now prompt you to mount only those volumes required for the
package(s) being installed.
This improvement translates into reduced installation time, especially when
selectively restoring packages from a multivolume kit.
For RSTSIE VIO.O, the RL02 and 800 BPI magtape installation media contain
two volumes each; all other media types contain only one volume each. If you
install a package that begins on a volume other than the currently mounted
one, or if the package you are installing spans more than one volume, you will
see a mount message similar to the following:
Please mount volume 2 on MMO:
Press RETURN to continue

Differences Between V10.0 and V9.7

2-1

Mount the volume indicated and press RETURN to continue the installation.
NOTE

You must still mount. the first volume ofyonr infltnllat.ion kit when
doing an installation or upgrade. Since no RSTSIE VI0.0 media
requires more than two volumes, the change described above does
not reduce the number of volumes you must mount. The main
benefit of this change is the installation time savings resulting from
not having to process all of the backup sets on a volume to locate a
given package's backup file.
•

Command Line Editing and Command Recall
If you are performing an installation or an update on an ANSI Scope terminal
(VT100, VT200 series, or VT300 series), then you can make full use of
the new Command Line Editing and Command Recall features during the
installation.

•

Template Monitor Default
Previously, when you were updating your system, the default for the Use
template monitor? prompt was N because you were running under the
SYSGEN monitor. Now, when you are running under the SYSGEN monitor,
the update procedure will attempt to find the monitor you last installed on
your system. If it finds a monitor other than SYSGEN.SIL, then the default
for the Use template monitor? prompt will be Y, and that monitor's name
will become the default for the Template monitor's name? prompt.

•

BASIC-PLUS DEBUG Support
The debugging feature of BASIC-PLUS, previously implemented by applying
the feature patch described in Article 4.10.1 of the RSTS IE V9.0 Maintenance
Notebook, is now a fully supported option of BASIC-PLUS and can be selected
as a standard option during installation.
The BASIC-PLUS installation procedure will now ask a new configuration
question Debug? If you answer YES to this question, then the BASIC-PLUS
runtime-system created will include debugging support. Refer to Article
4.11.1 of the RSTSIE Vl0.0 Maintenance Notebook for further details on how
to use the BASIC-PLUS debugging option.
Note that including the Debug option will increase the size of your BASICPLUS runtime-system, and, depending on the other options selected, may
cause it to grow larger than 16K words. Refer to the RSTS IE System
Installation and Update Guide for guidelines on configuring the various
BASIC-PLUS options.

•

Old-Style SENDIRECEIVE Support
The so-called old-format SENDIRECEIVE SYS() functions have been obsolete
and their use discouraged for several releases. In VI0.0, these SYS()
functions have been removed from BASIC-PLUS to make room for other code.
Users needing to include the old-format code can do so by answering y to the
Old-style SEND/RECEIVE? prompt during BASIC-PLUS installation.
Note that including the old-format SENDIRECEIVE SYS() functions in a
BASIC-PLUS run-time system may increase its size above the standard 16K
limit. In such cases, you may need to remove other options to reduce the size
under the 16K limit.

2-2

Differences Between V10.0 and V9.7

1-'--

Digital recommends that you modify any programs that make use of the
old-format SENDIRECEIVE SYS() functions to use the newer-format
SENDIRECEIVE functions. See Chapter 8 of the RSTS / E Programming
Manual for further information.

2.2.1

Support for OMS
OMS is a new installation package for RSTSIE VI0.0. It is installed similarly to
other optional system packages (like PBS). It is recommended that you install
OMS as a standard component on your system as it provides system services for
logging system events and communicating with operators. If you wish, you can
continue using the OPSER package concurrent with OMS.
If you are updating a V9.x system and the OMS package is installed for the

first time, you will be asked which accounts to assign the new OPER privilege.
Answer this question with the account or list of accounts, separated by commas,
to which you want to assign the OPER privilege. Wildcard accounts are accepted.
You will not be asked this question if you are installing a new RSTSIE VI0.0
system, because account [1,2] on the system disk will already have the OPER
privilege.
NOTE

Initially, only the startup job on your system, the one created when
timesharing is started, will have the OPER privilege (the startup job
is always assigned all privileges). Assign the OPER privilege to any
accounts you want to be able to issue privileged operator commands or
perform operator functions with the OMS package.

2.2.2

START.COM File Changes
A new START.COM file is included with VI0.0. The file contains new commands
to:
• Start the new OperatorfMessage Services (OMS) package
• Define _KBO: as an Operator Terminal
• Send a message to OMS when START.COM is completed
• Load the new FILE_UTILITY monitor overlay
• Create and assign host-initiated LAT ports
If you are updating a RSTSIE V9.x system, be sure to copy these new commands

from [O,I]START.OOL into your existing START.COM file.
The commands to create and assign host-initiated LAT ports and to load the
FILE_UTILITY overlay are optional and have been commented out. Remove the
exclamation points from in front of these commands if you want to provide LAT
ports or load the FILE_UTILITY overlay during startup.
NOTE

Differences Between V10.0 and V9.7

2-3

Be aware that the commands to start up OMS are not commented out in
START. COM. If you decide not to install OMS on your system, remove or
comment out these commands to avoid generating errors during system startup.

2.2.3

Accounts for Optional Packages
Prior to RSTSIE V10.0, the RSTSIE installation procedure created accounts for all
the RSTSIE optional packages, even those you did not select to install.
In V10.0, the installation procedure only creates accounts for the optional
packages you select.

2.3 Monitor
This section describes changes to the RSTSIE monitor for V10.0.

2.3.1

Creating Temporary Files
When the CRTFQ (create temporary file) function is used, the new IGNORE
attribute is set for the file. This causes those files created by the CRTFQ function
to be automatically excluded from any BACKUP operations.

2.3.2

Larger Record 1/0 for Libraries and Regions
In previous versions of RSTSIE, when 110 was done to or from a library or a
dynamic region, the entire buffer had to be mapped when the I/O operation was
started. This sometimes limited the amount of data that could be read or written
in a single 110 operation.
Beginning with VlO.O, when doing I/O to or from a library or dynamic region,
only the first word of the buffer need be mapped. The end address of the buffer
must be within the bounds of the same library or region as the starting address,
but does not have to be mapped. As a result, programs may now be able to read
or write larger buffers in a single I/O operation.

2.3.3

Larger Magtape Recordsizes
RSTSIE V10.0 supports a new open mode (1024%) for ANSI magtape opens. This
mode can be specified to use larger magtape recordsizes. When this mode is used
and the recordsize value specified is 0, then the record size value is set equal to
the specified blocksize value.
The BACKUPIRESTORE facility uses this new feature to extend its maximum
magtape block size.
See the RSTS IE Programming Manual for further details.

2.3.4

New Local Object Type
A new single-instance Local Object Type, value 11, has been defined for use by
the Operator/Message Services package.

2-4

Differences Between V10.0 and V9.7

2.3.5

MS Driver Changes
The driver for MS magtapes (TSll, TS05, TU80) has been changed in RSTSIE
VI0.0 to ignore records Jess than 14 bytes long when reading from tape. This was
done to prevent the MS driver from accidentally interpreting random noise on the
tape as a data record.
Note that the driver has never allowed records of less than 14 bytes to be written
to tape.

2.3.6

SYS Call Changes
This section describes all of the SYS calls and monitor directives that have been
changed for V10.0. See the RSTS / E Programming Manual and the RSTS / E
System Directives Manual for complete details.

2.3.6.1

.LOGS

The .LOGS directive, Check for Logical Device Name, has been enhanced to
support up to 15-character logical names. Logical names are now passed as
five RAD50 words instead of three. The name is still passed beginning at offset
XRLEN of the XRB.
In addition, three new logical and RAD50 translation subfunctions have been
added to the .LOGS directive.
See the RSTS / E System Directives Manual for further details on the .LOGS
directive.
2.3.6.2

.READA and .WRITA

In RSTSIE V10.0, the .READA (asynchronous read) and .WRITA (asynchronous
write) directives no longer require TUNE privilege. If a program does not have
TUNE privilege enabled, then it can only issue one .READA or .WRITA directive at a time. The monitor returns the error INUSE if a program without
TUNE privilege issues an additional .READA or .WRITA directive while the first
.READA or .WRITA directive has not yet completed.
Multiple .READA or .WRITA directives can still be issued from a job with TUNE
privilege, as in previous versions. See the RSTS / E System Directives Manual or
the RSTS / E Programming Manual for details.
Asynchronous I/O completions preempt the runburst of the current job if the
current job has a priority below -64 or if the job issuing the asynchronous 110 has
a priority above +64.
2.3.6.3

.ULOG

The .ULOG directive provides a mechanism for calling the three FIP functions
UU.ASS, UU.DEA and UU.DAL without calling FIP directly or invoking any
overlays. Changes to each of .ULOG's three subfunctions are summarized in the
sections that follow. See the RSTS / E System Directives Manual or the RSTS / E
Programming Manual for details.

Differences Between V10.0 and V9.7

2-5

2.3.6.3.1

UU.ASS

The UU.ASS directive, Assign User Logical, has been changed to support extended logicals. An additional subfunction to list user logicals by index number
has also been added. See Chapter 3 of the RSTS / E System Directives Manual.
2.3.6.3.2

UU.DAL

The UU.DAL directive, Deallocate All Devices and Deassign User Logicals, has
been enhanced to support extended logicals and provide a way to deassign user
logicals without deallocating devices. See Chapter 3 of the RSTS / E System
Directives Manual.
2.3.6.3.3

UU.DEA

The UU.DEA directive, Deallocate A Device or Deassign A User Logical, has been
enhanced to support extended logicals. See Chapter 3 of the RSTS / E System
Directives Manual.
2.3.6.4

UU.ATR

The UU.ATR Write Account Attributes directive now pennits updating of an
account's date and time of last interactive and noninteractive login field~ provided
they are currently null. If either field already contains a non-null value, then the
field cannot be changed, as in previous versions.
This change allows BACKUPIIMAGE and RESTORE to correctly restore an
account's date and time of last interactive and noninteractive login, so long as the
account was just created or was never logged in to.
See the RSTS / E System Directives Manual or the RSTS / E Programming Manual
for details.
2.3.6.5

UU.CHK

The UU.CHK directive now supports the new OPER privilege. Use UU.CHK
to determine if a user has the OPER privilege enabled, or to map the OPER
privilege keyword to or from its bit position in a privilege mask. See the RSTS / E
System Directives Manual or the RSTS / E Programming Manual for details.
2.3.6.6

UU.CNV

The date and time conversion Sys call (used by TIME$() in BASIC-PLUS) now
only recognizes time values in the range 0 to 2047, the low-order 12 bits of the
time word. The high-order three bits are now ignored. Note that RSTSIE time
values represent minutes until midnight, and should be in the range 0 to 1440.
See the RSTS / E System Directives Manual or the RSTS / E Programming Manual
for details.
2.3.6.7

UU.FCB

The following changes have been made to the UU.FCB directive:
•

2-6

The tenninal DDB (device data block) layout and contents have changed for
V10.0. As a result, the UU.FCB directive, subcode 0, will return different
data for a terminal open on a specified channel. See the RSTS/E VI0.0
Internals and Data Structures Manual for further infonnation about tenninal
DDBs.

Differences Between V10.0 and V9.7

•

The data returned by UU.FCB subcode 1 now includes the device name,
filename and filetype of the file open on the channel specified. This allows
a calling program to get information about the file opened on the specified
channel.
The file's device name is returned in the standard device offsets FQDEV and
FQDEVN. The file's PPN, name and type (in that order) are returned in four
consecutive words starting at offset FQNAM1+2.

See the RSTS / E System Directives Manual or the RSTS / E Programming Manual
for details.
2.3.6.8

UU.FIL

The following changes have been made to the UU.FIL directive:
•

The UU.FIL directive has been enhanced to support setting and clearing the
new [NO]BACKUP and [NO]IGNORE file attribute flags. These flags are
described in Section 1.2.6.

•

When requested, the UU.FIL directive could set the DLAlDLW of a file if the
file was currently closed, but not if it was opened. This is now available as an
option, and the DLAlDLW can now be set whether the file is opened or closed.

See the RSTS / E System Directives Manual or the RSTS / E Programming Manual
for details.
2.3.6.9

UU.JOB

The UU.JOB (Create Job) directive now updates the noninteractive date/time
of last login when spawning a logged-in job. See the RSTS / E System Directives
Manual or the RSTS / E Programming Manual for details.
2.3.6.10

UU.LlN

The UU.LIN (LOGIN) directive now records both the interactive and noninteractive date and time of last login. It also updates the date and time of last
interactive login for logins at a physical terminal or pseudo keyboard, and updates the date and time of last noninteractive login for Batch or Network Server
logins.
See the RSTS / E System Directives Manual or the RSTS / E Programming Manual
for details.
2.3.6.11

UU.SLN

The UU.SLN directive has been enhanced to support extended logicals up to
15 characters long. See the RSTS / E System Directives Manual or the RSTS / E
Programming Manual for details.
2.3.6.12

UU.SWP

The UU.SWP (Remove System File) directive now returns an indicator if no overlay or error file was added, allowing the calling program to determine whether
the call actually removed the requested file. See the RSTS / E System Directives
Manual or the RSTS / E Programming Manual for details.

Differences Between V10.0 and V9.7

2-7

2.3.6.13

UU. TB3

The system's hardware configuration word now contains a bit which indicates
whether or not the system includes FIS hardware. See the RSTS / E S.'Ystem
Directives Manual or the RSTS / E Programming Manual for details on how to
access this new bit.
2.3.6.14

UU.TRM

New terminal attributes bits are now defined to control:
• Line editing (LINE_EDITING)
• Command recall (RECALL)
• Line editing mode (INSERT or OVERSTRIKE)
• Operator requests (OPERATOR=REQUESTS)
• Operator messages (OPERATOR=MESSAGES)
Note that the new LINE_EDITING and RECALL attributes only control those
features within a program.
All of the new terminal attribute bits have permanent and temporary settings.
Use the SET TERMINAL command to enable or disable the new attributes, and
the SHOW TERMINAUFULL command to display their cUrrent state. See the
RSTS / E User's Guide or use the online HELP command for more information on
the use of these commands to manage the new attributes.
See the RSTS / E Programming Manual for information on how to set, clear, or
read these new terminal attributes within a program.

2.4 Del
This section describes changes to the DCL run-time system and its associated
commands and services for V10.O.

2.4.1

ALLOCATE Command
The ALLOCATE command now accepts the qualifier I[NO]QUEUED when
allocating a terminal defined as a local LAT port. This qualifier temporarily sets
or clears the queueing characteristic on the local LAT port you are allocating.
This queued setting remains in effect only until you deallocate the device.
The ![NO]QUEUED qualifier is only valid if the device being allocated is a local
LAT port.
If IQUEUED is specified, connections initiated by this local LAT port to a terminal

server will be placed on the server's queue if the server supports queueing and
the remote port is currently busy. If INOQUEUED is specified, connections will
not be queued and will fail if the remote port is busy.
Use the SHOW PORT command to display the port's connection status and
queued setting status. If the port is set IQUEUED, and the server is busy, a
connection status of In Progress and the connection's position in the queue will be
shown.
If this qualifier is not specified, the queued setting that was specified when the

port was created or assigned will be used.

2-8

Differences Between V10.0 and V9.7

2.4.2

ASSIGN Command
The following qualifiers have been added to the DCL ASSIGN command for
VIO.O:
•

/uSER
The /uSER qualifier indicates a user logical assignment.
This qualifier is provided primarily for completeness; if you do not specify
/uSER or /SYSTEM, then the command assigns a user logical, as it did
previously. You can include the /uSER qualifier in DCL command procedures
to explicitly state the type of logical assignment you are making.

•

/[NO]REPLACE[=QUERY]
The /[NO]REPLACE[=QUERY] qualifier is now available for assigning user
logicals.

2.4.3

CREATE/ACCOUNT Command
The CREATE/ACCOUNT command now supports the OPER and NOOPER
keywords as arguments to the !PRIVILEGES qualifier.

2.4.4

DEASSIGN Command
The DEASSIGN command now accepts the /USER qualifier to indicate a user
logical deassignment.
This qualifier is provided primarily for completeness; if you do not specify IUSER
or /SYSTEM, then the command deassigns a user logical, as it did previously. You
can include the IUSER qualifier in DCL command procedures to explicitly state
the type of logical deassignment you are making.
Both DEASSIGN/uSER and DEASSIGN/SYSTEM display the %Logical not
found warning message if the logical name you specify is not assigned. In
previous versions, DEASSIGN/SYSTEM displayed an error message.

2.4.5

DEFINE/COMMAND/SYSTEM Command
The DEFINE/COMMAND/SYSTEM command now accepts the
/[NO]REPLACE=QUERY qualifier to control replacing system commands that
already exist. The qualifier works the same as the /[NO]REPLACE=QUERY
qualifier for other DCL commands such as COpy and RENAME. The default is
INOREPLACE, as in previous versions.
See the RSTS / E System Manager's Guide for details.

2.4.6

DIRECTORY Command
The DIRECTORY command has been updated for VIO.O to show the status of
the new [NO]IGNORE and [NO]BACKUP file attributes when a /FULL listing is
requested.
In addition, the DIRECTORY/FULL display now includes each file's open count.

Differences Between V10.0 and V9.7

2-9

2.4.7

HELP Files
All HELP files have been updated to reflect new DCL commands or qualifiers or
additions to existing DCL commands. The following other changes are noted:

2.4.8

•

The new topics Command Recall and Line Editing have been added to provide
help for the new Command Line Editing and Command Recall features.

•

The topic Keys has been revised to include the new key definitions related to
Command Line Editing and Command Recall.

•

The RA70 and RA90 disks have been added to the Advanced Disks topic, and
the (unsupported) RP02 and RP03 disks have been removed.

INITIALIZE Command
•

The INITIALIZE command for disks now sets the new IGNORE file attribute
for the files [O,l]BADB.SYS and [O,l]SATT.SYS. This excludes these files from
BACKUP operations.

•

In previous versions, INITIALIZE would fail with a ?DSKINT allocation failure
error if you attempted to initialize a virtual disk smaller than 16 blocks.
While a virtual disk this small is legal, it can only be used as a
non-file-structured disk; it cannot be initialized because it is too small to hold
a minimal RSTS/E file structure.
For V10.0, if you attempt to initialize the virtual disk smaller than 16 blocks,
INITIALIZE will display the following more useful error message:
?Disk too small to be RSTS file-structured

2.4.9

INQUIRE Command
If you specify INQUIREtrIMEOUT and the command times out, DCL deletes any

characters typed up to the point of timeout.

2.4.10

LINK Command
The DCL LINK command has been enhanced to add the following qualifiers in
support of PDP-11 C for RSTS/E:
•

ICC
Indicates object files created by the PDP-11 C compiler

•

/STACK=n
Specifies the size of the executable program's stack space, in words. The
/STACK qualifier corresponds to the STACK=n option in TKB. See the
RSTS / E Task Builder Reference Manual for further details.

2.4.11

LOAD/OVERLAY Command
The LOAD/OVERLAY command now supports the overlay keyword FILE_UTILITY.
See Section 1.2.11.12 for more details.

2-10

Differences Between V10.0 and V9.7

2.4.12

MOUNT/REBUILD Command
Error checking in the MOUNT/REBUILD command has been improved. The
clustersizes of [O,l]BADB.SYS and [O,l]SATT.SYS are now verified t.o ensure that
they are the same as the pack clustersize.

2.4.13

PRINT Command
The I[NO]NOTIFY qualifier has been added. See Section 1.2.11.13 for further
details.

2.4.14

REQUEST Command
The REQUEST command has been changed for V10.0 to communicate with the
new Operator/Message Services (OMS) package. REQUEST now allows you to
send requests that require a reply from an operator.
When you include the new /REPLY qualifier with your request, your job is stalled
until one of the following events occur:

• An operator replies to your request.
• An operator terminates your request.
• You type CtrllC to terminate your request.
You can also include the !TIME_OUT qualifier with /REPLY to specify the
maximum time (in minutes) that the command will wait for a reply. If no
response is received in the specified time, then the request is terminated. This is
especially useful when issuing REQUEST/REPLY commands within a Batch job.
Note that the REQUEST command no longer communicates with the OPSER
package. If you issue a REQUEST command and OMS is not running, then the
following error is displayed:
?Operator/Message Services not running

Users who want the REQUEST command to continue dispatching to the OPSER
package can redefine the command (in their LOGIN. COM file) as:
$ REQ-UEST == "CCL PLEASE"

See the RSTS / E User's Guide or the online HELP topic REQUEST for more
information about the REQUEST command.

2.4.15

SET ACCOUNT Command
The SET ACCOUNT command now accepts the keywords OPER and NOOPER as
arguments to the !PRIVILEGES qualifier.

2.4.16

SET JOB/PRIVILEGE Command
The SET JOB!PRIVILEGE command now accepts the keywords OPER and
NOOPER.

Differences Between V10.0 and V9.7

2-11

2.4.17

SET NODE/LAT Command
The SET NODEILAT command now accepts the qualifier IACCESS to specify
whether connections via the terminal server should be treated as LOCAL or
DIALUP.
Most terminal servers send the host system their proper access type when a
connection is established. However, not all terminal servers do so. For example,
DECnetIDOS LAT connections do not currently supply an access type when a
connection is made from an MS-DOS system. In such cases, RSTSIE by default
treats the connection as DIALUP for security.
The new IACCESS qualifier lets the system manager decide how such terminal
server connections should be treated by the system.
Note that this qualifier only determines the access type for terminal servers that
do not supply an access type. If a terminal server does include an access type
with its connection, RSTSIE will ignore any IACCESS setting and use the access
type supplied by the server instead.
CAUTION

Setting the access type to LOCAL for a terminal server that provides
access to the system via dialup lines could compromise security. For
example, if your system normally requires a system password for
DIALUP access, and you have ACCESS=LOCAL in effect, then any
user dialing into your system through a terminal server that does not
supply its own access type will be able to log in without entering the
system password.

2.4.18

SET SYSTEM Command
The ISWAP_MAXIMUM qualifier argument range has been increased by two,
from the current 32K to 64K words to 34K to 66K words, to account for the new
job header region described in Section 1.2.7.

2.4.19

SET TERMINAL Command
The following changes have been made to the SET TERMINAL command for
VIO.O:
•

•

SET TERMINAL no longer allows the qualifiers /HOST_SYNC and
IRESUME=ANY to be used together. These qualifiers now conflict. A
terminal that has the HOST_SYNC attribute enabled cannot be set to
RESUME=ANY and vice versa.
SET TERMINAL no longer allows the qualifiers IAUTOBAUD and
IANSWERBACK to be used together. These qualifiers now conflict. A

terminal that has AUTO BAUD enabled cannot be set to ANSWERBACK and
vice versa.

2-12

•

The SET TERMINAVDEVICE=terminal_type command no longer affects the
terminal's ESCAPE_SEQUENCE attribute. Previously, all device macros set
the terminal to NOESCAPE_SEQUENCE.

•

The SET TERMINAL qualifier /BUFFER_QUOTA, used to change a terminal's character buffer quota, now requires the !PERMANENT qualifier. This
limits control of a terminal's buffer quota to users with HWCTL privilege.

Differences Between V10.0 and V9.7

2.4.20

•

The tenninal input buffer quota range has been changed. Previously, a
tenninal's buffer quota could be set from a minimum of 180 characters to
7650 characters. The new buffer quota range is 168 to 7140 characters.

•

Several new qualifiers have been added to SET TERMINAL t.o enable and
disable the new tenninal attributes defined in V10.0. See Section 1.2.11.20
for more infonnation on the new tenninal attributes.

SHOW ACCOUNT Command
The SHOW ACCOUNT command now lists the OPER privilege (if enabled) in its
/FULL display.
Also, the /FULL display includes two new fields: UFD size and UFD used. See
Section 1.2.11.21 for more details.

2.4.21

SHOW DEVICE Command
The SHOW DEVICE command now properly reports disks that were disabled by
INIT during system startup.

2.4.22

SHOW JOB/PRIVILEGES Command
The SHOW JOBIPRIVILEGES command now lists the OPER privilege (if
enabled).

2.4.23

SHOW LOGICALS Command
The following changes have been made to the SHOW LOGICALS command for
V10.0:
•

By default, the SHOW LOGICALS command now displays both user and
system logicals. Previously, it displayed only user logicals.

•

The /uSER qualifier has been added to display only user logicals. Use
/SYSTEM as before to display only system logicals.

•

If you specify a logical name parameter that contains no wildcard characters,
SHOW LOGICALS will display only those logicals (user or system) that
exactly match the name given. Previously, SHOW LOGICALS displayed all
logicals that matched the parameter up to the number of characters entered.
This change was made to make the SHOW LOGICALS command more
consistent with the DIRECTORY command and other DCL SHOW commands.
For example, in V9.7 and earlier, the following command displayed alllogicals
beginning with the character W:
$ SHOW LOGICALS W

In V10.0, only the system or user logical named W is displayed. You must
now include wildcard characters (? or *) in the logical name parameter to
select multiple logicals for display, such as W* to display alllogicals that
begin with W.

Differences Between V10.0 and V9.7

2-13

2.4.24

SHOW SYSTEM Command
When changes are made, the SHOW SYSTEM command now displays a threecolumn listing of the changes that take effect at rebooting.

2.4.25

SHOW TERMINAL Command
In a SHOW TERMINALIFULL listing, the new terminal attributes listed in
Section 1.2.11.20 are included (in alphabetical order) in the list of terminal
attributes.
In addition, since Command Line Editing requires that the terminal be set to
ANSI, SHOW TERMINAL includes the following status message at the end of its
display if LINE_EDITING and NOANSI are in effect:
Line Editing is not available (No ANSI)

2.4.26

SUBMIT Command
The I[NO]NOTIFY qualifier has been added to the SUBMIT command. See
Section 1.2.11.13 for further details.

2.4.27

UNLOAD/OVERLAY Command
The UNLOAD/OVERLAY command now supports the overlay keyword
FILE_UTILITY. See Section 1.2.11.12 for more details.

2.5 BACKUP/RESTORE Package
Besides the new BACKUPIIMAGE and BACKUP/COPY commands, several other
changes and enhancements have been made to the BACKUPIRESTORE facility
forV10.0:

2.5.1

Larger Block Sizes
BACKUPIRESTORE can now read and write backup sets with block sizes up to
28,672 bytes. The /BLOCK_SIZE qualifier now accepts arguments in the range
2048 to 28672. The default /BLOC~SIZE value for tapes has been increased to
16384 for the BACKUP command. For disks, the default /BLOCK_SIZE value is
28672 for the BACKUP command. The default /BLOCK_SIZE value for the new
BACKUPIIMAGE and BACKUP/COPY commands is 28672 (the maximum).
Larger block sizes provides the following key benefits:
Reduced backup set size on both disks and tapes. Fewer block headers (data
written at the beginning of each block) are required when using larger block
sizes and reduced backup set size on tape.
Larger block sizes means fewer interrecord gaps on the tape so more data can
be stored on a given tape.
Improved overall BACKUPIRESTORE performance. Larger block sizes
reduces the CPU overhead required to manage blocks within a backup set.

2-14

Differences Between V10.0 and V9.7

Improved VMS BACKUP compatibility. Backup sets created on VMS with
larger block sizes (8192 is the default block size for tape backup sets on VMS)
can now be successfully restored on RSTSIE.
Note that specifying a larger /BLOCK_SIZE value may require more memory
(dynamic region) to complete the operation, as described below.
NOTE

When creating a backup set that will be restored on an earlier version
of RSTSIE (pre-V10.0), be sure to specify a /BLOCK_SIZE value less
than or equal to the maximum value pennitted by that version. For
example, if you create a magtape backup set to be restored on a V9.7
system, specify IBLOCK_SIZE=4080 (the maximum magtape block size
allowed in V9.7).

2.5.2

Larger Buffer Sizes
The maximum /BUFFER_SIZE value has been increased from 127 to 255. The
default is the minimum memory required to support the block size of the backup
set.
Specifying a larger buffer size will reduce the total time required to complete a
backup or restore operation and will also improve overall system perfonnance
during the operation.

2.5.3

Improved Exit Status
BACKUP now exits with status SUCCESS only if it successfully completes its
operation and issues the final dismount message. BACKUP exits with status
ERROR if the backup or restore operation is not completed, for example, if you
type CtrllZ at the prompt for next disk or tape volume, or type CtrllC during an
in-progress operation.
This change also improves the RSTSIE installation process. For example, prior
to V10.0, if you mounted the wrong distribution media in response to a volume
prompt (as part of a RESTORE operation), but then mounted the correct volume,
the RESTORE operation would complete successfully but the installation itself
would fail because RESTORE exited with an error. Now, the installation would
proceed because RESTORE would exit with status SUCCESS, even though an
error was generated during the volume mounting phase of the RESTORE.

2.5.4

Pre-extended Disk Files
During file transfers to sman, slow disks such as the RX50 and RX33, files will
be pre-extended on creation, then truncated to their proper size after the data
is transferred. This saves time by eliminating the disk seeks associated with
extending the files in small steps.

2.5.5

Temporary Privileges
BACKUP.TSK now requires temporary privileges. Therefore, the V10.0 installation procedure will set the protection code of the file [O,1]BACKUP.TSK to <232>.

Differences Between V10.0 and V9.7

2-15

2.5.6

LOGIN Date/Time Attribute Updated
BACKUP win now update an account's date/time of last interactive and noninteractive login, provided the account being restored on the target disk (via the
RESTORE, BACKUPIIMAGE or BACKUP/COPY command) is a newly created
account and has not been logged into before.
If the account being restored on the target disk already exists and has been

logged into, then the target account's current date/time oflast login information
is not changed.

2.5.7

TUNE Privilege No longer Required
The BACKUP and RESTORE commands no longer require TUNE privilege.
Users without TUNE privilege can now execute these commands as well as the
new BACKUPIIMAGE and BACKUP/COPY commands, but will not achieve
the same high level of performance as those with TUNE privilege. Also, users
without TUNE privilege cannot specify the /BUFFER_SIZE qualifier; instead, the
minimum buffer size required for the backup set's block size is used.
BACKUPIRESTORE originally required TUNE privilege because it uses asynchronous I/O to perform all of its disk and tape 110. The monitor required TUNE
privilege to execute the .READA and .WRITA (asynchronous) 110 directives.
In VIO.O, the monitor permits asynchronous I/O calls from jobs without TUNE
privilege, but restricts those calls to only one read/write request at a time. See
Section 2.3.6.2 for further details on this monitor change.

2.5.8

INSTAL Privilege No longer Required
If a user does not have INSTAL privilege, and the system's DYNAMIC_REGION_
LIMIT is set lower than the /BUFFER_SIZE value required, BACKUPIRESTORE
will automatically reduce the /BLOCK_SIZE and /BUFFER_SIZE values to the
maximum allowed by the DYNAMIC_REGION_LIMIT. BACKUPIRESTORE
displays an informational message. For example:
Not enough free memory, block size reduced to 4098
Dynamic region size is 5K-words

If the system's DYNAMIC_REGION_LIMIT value is too small to support the
minimum buffer size required, BACKUPIRESTORE displays the following error
message and exits:
?Not enough free memory to create dynamic region

See the RSTS / E System Manager's Guide for more information about the SET
SYSTEM command's !DYNAMIC_REGION_LIMIT qualifier.

2.6 Print/Batch Services (PBS)
Several enhancements have been made to the PrintlBatch Services (PBS) package
for VI0.0, as explained in the next few sections. See also Section 1.2.11.13.

2-16

Differences Between Vi 0.0 and V9.7

2.6.1

SHOW ENTRY Display Format
The format of the SHOW ENTRY brief and full displays has been changed to
use column headings instead of field keywords, so that more infonnat.ion can be
displayed on the first line of each entry's display. With this change, it is no longer
necessary to specify /FULL to display a print entry's form name.
This change, coupled with the new /STATUS qualifier and FORMS_WAIT entry
status, lets you quickly find entries that are waiting for a forms change, and see
which forms are required.
Also, the SHOW ENTRY full display format now displays !NOTIFY if the request
was created with the !NOTIFY qualifier.

2.6.2

Automatic File Compression
Previously, PBS compressed its workfile only at start up. PBS now performs
automatic compression of its work file, PBS$:PBS.SYS. Compression occurs
periodically, based on the number of PRINT or BATCH entries deleted from the
file since the last compression. Entries are deleted as they are completed, or
when they are explicitly deleted with a DELETEIENTRY command.
If you issue a PRINT or SUBMIT command while PBS is compressing its workfile,
you may receive a (Waiting for acknowledgment ... ) message, indicating that PBS
has not yet received your request. In most instances, PBS will respond to a
PRINT or BATCH request in less than one minute.
With the addition of this feature, it is no longer necessary to periodically stop and
restart PBS as described in article 15.1.4 of the August 1987 Software Dispatch.

2.6.3

New User Request Packet Field
A new I[NO]NOTIFY field has been added to the User Request Packet interface
for PBS. See Chapter 10 of the RSTS / E Programming Manual for further
information.

2.6.4

Batch Exit Status
Two changes have been made to the PBS Batch Processor in V10.0 that provide
better control over error handling within a batch job:
•

Batch jobs now exit with the same status as the exit status of the job's
COM file, instead of the most severe status detected by the monitor during
execution.
For example, consider the following COM file executed in a batch job:
$ Set NoOn
$ -Write 0 "?This is an error line"
$ ::::Exit 1

Disable error handling
! Force status ERROR
! Exit with status success

Prior to V10.0, this batch job would exit with status ERROR, even though
the COM file itself exited with status SUCCESS. This happened because the
monitor returned ERROR as the most severe status seen during execution of
the batch job.

Differences Between V10.0 and V9.7

2-17

•

Batch jobs that execute multiple COM files will now exit whenever any of the
job's COM files exit with a status of ERROR or SEVERE_ERROR. Prior to
V10.0, all of the COM files included in the batch job would execute, even if
one of them exited with status ERROR or SEVERE_ERROR.
For example, consider the following COM files included in a batch job:
$! FILEL COM
$ Write a "?This is an error line"
$ _Stop

Force exit status of ERROR
This command is never reached

$!FILE2.COM
$ Write a "Processing FILE2.COM"
$ -Exit

Say we got here
All done

Prior to V10.0, if the above COM files were submitted with the following command, then the FILE2.COM file would be executed, even though FILE1.COM
exited with status ERROR:
$ SUBMIT FILE1,FILE2

In V10.0, the batch job exits immediately after the FILE1.COM file completes.
FILE2.COM is not executed.
I~-~

2.6.5

PBS Operator Messages
PBS has been enhanced to send messages to the new OperatorlMessage Services
(OMS) package to notify operators of various events of interest. PBS will send a
message to OMS when any of the following events occur:
•

A Print or Batch entry starts.

•

A Print or Batch entry completes.

•

A Print or Batch entry is deleted.

•

A print server goes off line while processing an entry.

•

When one or more Print entries are waiting for a forms change (entries with
status FORMS_WAIT; see Section 1.2.11.22).

For entries requiring a forms change, PBS will send a message to OMS the
first time it finds an entry in a FORMS_WAIT state. PBS will continue sending
reminder messages at increasing intervals, from once every 30 minutes to once
every six hours, until there are no more entries waiting for a forms change.
PBS sends its messages to OMS with the facility name PBS. If messages are
being saved in the OMS work file, you can display all messages sent from PBS by
issuing the following command:
$ SHOW REQUESTS/NOREPLY/FACILITY=PBS

2.7 Commonly Used System Programs (CUSPs)
This section describes CUSPs that have been changed for V10.0.

2-1 B

Differences Between V10.0 and V9.7

2.7.1

ANALYS
The following enhancements have been made to the ANALYS program for V10.0:

2.7.2

•

The special flag characters! (LAT) and * (dialup) have been appended to the
appropriate keyboards in the job status display.

•

The system up-time display is now compatible with that used by SYSTAT.

•

Locked block information is now included in the open files display.

•

ANALYS now produces a list of devices similar to that created by the DCL
SHOW DEVICE command.

•

ANALYS now displays information about the use of cache, similar to that
created by the DCL SHOW CACHE command.

DIRECT
Directory listings that include the symbolic attributes now also display the new
[NO]IGNORE and [NO]BACKUP file attributes.

2.7.3

DSKCVT
The DSKCVT program has been updated to support the new OPER privilege:

2.7.4

•

You must have OPER privilege enabled to run the DSKCVT program,
otherwise DSKCVT displays an error message and exits.

•

When assigning privileges to accounts, DSKCVT assigns the new OPER
privilege to all [1,*] accounts.

DSKINT
•

The DSKINT program has been modified to set the IGNORE file flag for the
[O,l]BADB.SYS and [O,l]SATT.SYS files created during disk initialization.

•

If you attempt to initialize the virtual disk smaller than 16 blocks, DSKINT

will display the following error message:
?Disk too small to be RSTS file-structured

2.7.5

DSKSEK
The DSKSEK program has been updated for V10.0 to support RA90 disks.

2.7.6

Error Package
The Error package has been enhanced for V10.0 to include support for RA70 and
RA90 disks.

Differences Between V10.0 and V9.7

2-19

2.7.7

LOGIN now displays both the date and time of last interactive and last
noninteractive logins. All local, dialup and SET HOST logins update the date
and time of last interactive login. Batch and network server logins update the
date and time of last noninteractive login.

•

LOGIN now accepts a system logical name in response to its User: prompt,
allowing users to log in by name. See Section 1.2.8 for further details.

•

LOGIN performance has been improved by moving some of the LOGIN tasks
from the system login command file [O,l]LOGIN.COM into LOGIN.TSK. See
Section 1.2.10 for further details.

•

LOGIN now sends its messages to OMS instead of OPSER. If OMS is not
running, LOGIN broadcasts its messages to _KBO: (the system console).
If messages are being logged in the OMS Log file, you can display messages

from LOGIN by issuing the following command:
$ SHOW REQUEST/NOREPLY/FACILITY=LOGIN

2.7.8

LOGOUT
LOGOUT now sends messages to OMS instead of OPSER. If OMS is not running,
LOGOUT broadcasts its messages to _KBO: (the system console).
If messages are being logged in the OMS Log file, you can display messages from

LOGOUT by issuing the following command:
$ SHOW REQUEST/NOREPLY/FACILITY=LOGOUT

2.7.9

ODT
Several enhancements have been made to the ODT program residing in the
AUXLIB$: account. The program is now built using BASIC-PLUS-2, and has a
.TSK extension.
In previous releases, a user could get write access to memory or files by using
LINE FEED as the delimiter. In V10.0, in addition to the LINE FEED key (or
CtrIlJ), you can use a new switch, I[NO]WRITE, to specifically request read-write
access or read-only access. Including the !WRITE switch in the command has the
same effect as terminating the command with LINE FEED. Pressing Return to
end the command has the same effect as INOWRITE. The switch, when present,
always overrides the command terminator.
The type of access granted is displayed in an informational message, for instance
Access is READ WRITE. Occasionaly you may request write access, but for some
reason can not be granted this access. In this case, you first receive a warning
message giving the reason for the restricted access, followed by a second message,
Access is READ ONLY.

You can also type HELP at the File<MEMORY>? prompt to get an overview of the
options available at the main prompt. If you happen to have a file called HELP
(with no extension) in your account and you wish to work on that file, simply
include the period (.) in the file name to signify the file HELP. as distinct from
the HELP command.

2-20

Differences Between V10.0 and V9.7

2.7.10

ONLCLN
The clustersizes of [0,1]BADB.SYS and [0,1]SATT.SYS are now verified to ensure
that they match the pack clustersize.

2.7.11

OPSER Package
Two new OPSER commands are included with V10.0 to disable features that
were previously disabled via feature patches in VS.O and earlier. These feature
patches, 14.6.1 and 14.10.1, were removed in V9.0.
•

QUMRUN feature patch 14.6.1, Disabling Job with different form name
waiting message, has been replaced by the OPSER command NOFORMS_
WAIT. By default, forms waiting messages are broadcast to the Operator
Services Console. Issue the NOFORMS_WAIT command to disable the forms
waiting message. Issue the command FORMS_WAIT to reactivate the forms
waiting message.

•

SPLRUN feature patch 14.10.1, Eliminating extra form feeds on special
forms, has been replaced by the OPSER command NOFORM_FEED. By
default, two form feeds are printed at the beginning of each print job. Issue
the NOFORM_FEED command to eliminate one of the form feeds. Issue the
command FORM_FEED to reactivate the extra form feed.

If you plan to use these new commands, include them in the OPSER startup

section of the system START. COM file. However, you can also issue these
commands once OPSER has started (and detached), by issuing them as a
qualifiers to the PLEASE utility. For example:
$ PLEASE/NOFORMS_WAIT
COMMAND SENT TO 'OPSER'
Forms Waiting messages DISABLED
$

2.7.12

PIP.SAV
The following enhancements have been made to PIP for V10.0:
•

A new directory listing switch !MDELETE is now available to display files
that are marked for deletion. The switch can be abbreviated to !MD.

•

All file attributes are now preserved when a file is copied from disk to
disk. This includes all caching flags, the NODELETABLE flag, and the new
[NO]IGNORE and [NO]BACKUP flags.

•

The ILI:S directory option now includes the new [NO]IGNORE and
[NO]BACKUP file attributes in the directory listing.

•

The ILI:S directory option now displays each file's open count in the directory
listing.

Differences Between V10.0 and V9.7

2-21

2.7.13

REORDR
The REORDR utility has been enhanced to allow sorting of directories by filename
or filetype. Directories sorted by filename will have their fileR ordered nlphnbetically by filename (primary key), then filetype (secondary key). Directories sorted
by filetype will have their files ordered alphabetically by filetype (primary key),
then filename (secondary key). Like other REORDR sort options, you can sort by
filename or filetype in either forward or reverse order.
When viewing a directory sorted by REORDR, be aware that files added to the
directory since it was last sorted may be out of order.
See the RSTS / E System Manager's Guide for details.

2.7.14

SHUTUP
SHUTUP now includes a shutdown phase for OMS. If OMS is running, SHUTUP
issues an implicit STOP/OPERATOR_SERVICES/ABORT command to shut down
OMS. Any pending requests are deleted as part of the OMS shutdown phase.
;---

2.8 BASIC-PLUS
This section describes the changes that have been made to the BASIC-PLUS
run-time system for V10.0.

2.8.1

BASIC-PLUS Debugging
The debugging feature of BASIC-PLUS, previously implemented by applying the
feature patch described in article 4.10.1 of the RSTS / E Maintenance Notebook,
is now a fully supported option and can be selected as a standard BASIC-PLUS
option during installation. See Section 2.2 for details on how to select this option
during installation.
When you select BASIC-PLUS debugging, the debug commands TRACE,
UNTRACE, BREAK, UNBREAK, and DUMP become reserved keywords, and
conflict with variables of the same name. Programs built against a version of
BASIC-PLUS that does not include debugging can continue using the above
keywords as variable names.
NOTE

Digital recommends you avoid the use of the debugging keywords as
variable names, to avoid possible conflicts when using a version of
BASIC-PLUS that includes the debugging option.

2.8.2

Extended Logicals Support
The BASIC-PLUS ASSIGN and DEASSIGN keyboard monitor commands have
been enhanced to support the extended user logicals available in V10.0. See
Section 1.2.4 for details on the new extended logicals feature.
To provide this support, BASIC-PLUS now recognizes spaces as delimiters in
these commands. Support for extended logicals is only available in EXTEND
mode.

2-22

Differences Between V10.0 and V9.7

The following sections describe the changes to the BASIC-PLUS ASSIGN and
DEASSIGN commands in more detail.

2.8.2.1

ASSIGN Command

A command such as ASSIGN DL3:[1,2] LOGICALNAME will now be recognized
as an assignment of an extended VlO.O logical. The rules that BASIC-PLUS uses
to determine an extended logical assignment are:
•

The string between the first and second space must not contain a filename.

•

The string following the second space must contain only characters valid in a
logical name.

Thus, a command such as ASSIGN DL3:[1,3]FOO BAR will produce an error
in VIO.O. In earlier releases, spaces were ignored and this command assigned
account DL3:[1,3] the logical name FOOBAR.
Commands such as ASSIGN MMO: and ASSIGN <40> continue to work as in
previous releases.
Note that a command such as ASSIGN DL3:[1,2]LOGICALNAME does not create
an extended logical, because there are no spaces beween the account name and
the logical name. BASIC-PLUS treats it the same as in earlier releases; the
monitor truncates the logical name to LOGICA and assigns it to DL3:[1,2], as it
did previously.

2.8.2.2

DEASSIGN Command

A command such as DEASSIGN LOGICALNAME will now be recognized as a
deassignment of an extended VIO.O logical. The rules that BASIC-PLUS uses to
determine an extended logical deassignment are:
•

All embedded spaces are ignored.

•

All characters in the logical name must be valid for a logical name.

Commands such as DEASSIGN MMO: or DEASSIGN <40> continue to work as
in earlier releases.

2.8.3

HELLO and BYE Commands
In earlier releases, the HELLO and BYE commands were parsed and handled by
the BASIC-PLUS run-time system. They have been removed from BASIC-PLUS
to make room for other code in VIO.O.
The standard HELLO and BYE commands can still be available from BASICPLUS, by installing them as system commands (CCLs).

2.8.4

Old-Format SEND/RECEIVE Calls
The so-called old-format SENDIRECEIVE SYS( ) functions, of the form:
SYS (CHR$ (6%)

+ CHR$ (18%) + ...

)

have been obsolete and their use discouraged for several releases. In VIO.O, these
SYS() functions have been removed from BASIC-PLUS to make room for other
code.

Differences Between V10.0 and V9.7

2-23

Users needing to include the old-format code can do so by answering Y to the
Old-style SEND/RECEIVE? prompt during BASIC-PLUS installation.

Note that including the old-format SENDIRECElVE SYS() functions in a
BASIC-PLUS run-time system may increase its size ahove the Rtandrml 10K
limit. In such cases, you may need to remove other options to reduce the size
under the 16K limit.
Digital recommends that you modify any programs that make use of the
old-format SENDIRECEIVE SYS() functions to use the newer-format
SENDIRECElVE functions. See Chapter 8 of the RSTS / E Programming Manual
for further information.

2.9 RSX-11
The RSX object library SYSLIB.OLB has been updated to include the PDP-ll C
impure area vector and region mapping support for FORTRAN-77. This change
was required to support PDP-ll C programming for the RSX environment under
RSTSIE.

The fonowing changes have been made to the RT-ll run-time system and its
associated utilities for V10.0:

2.11

LINK.SAV has been updated to the latest version of RT-ll, V5.4.

LIBR.SAV has also been updated to the latest version of RT-ll, V5.4.

The RT-ll object library [1,2]SYSLIB.OBJ has been modified to include all of
the standard RT-ll modules, along with the existing RSTS-specific modules.

RMS-11
This section describes changes that have been made to RMS-ll and its associated
utilities for V10.0.

2.11.1

RMS-11 Macro library
The RMS-ll Macro Library (RMSMAC.MLB) has been modified to add the
definition NB$NOD to the NAM$BT macro. This definition is relevant to
$PARSE operations, signifying the presence of a node in the file specification.

2.11.2

RMSm11 Access Methods
The module ROXPFN in the RMSLBB.OLB and RMS libraries has been enhanced
to allow extension of a contiguous relative or indexed file by marking the file
noncontiguous. This is especially important for improved handling of indexed
files. In the past, if a $PUT resulted in a complex bucket split, it was possible
for RMS-ll to use all available blocks in the file before completing the $PUT. The
file would then be inconsistent in its indexed structure. To signal the incomplete
state of the file, RMS-ll would breakpoint. Now, RMS-ll win mark the file
noncontiguous and extend it as necessary to complete the $PUT operation.

2-24

Differences Between Vi 0.0 and V9.7

Be aware that, once an indexed file is marked noncontiguous, RMS-ll performance on the file may degrade.
NOTE

When an RMS-ll program aborts or the system crashes during a
$PUT or $UPDATE operation, the file should be reloaded to ensure
data consistency on subsequent keyed or RFA access. Otherwise data
inconsistency problems may surface at a later time.
The CLOSE operation now accepts a negative channel number. If a negative
channel number is passed, RMS performs a reset close (CALFIP RSTFQ)
function, similar to BASIC-PLUS. This causes the file to be closed without
performing any of the normal clean-up operations, such as marking a tentative
file permanent.

2.11.3

RMS-11 Utilities
The RMSDSP, RMSDEF, RMSBCK, and RMSRST utilities have been modified
to parse file specifications in a manner more consistent with RSTS/E DCL
standards. As a result, these utilities now properly handle the standard RSTS
file specifications.

Differences Between V10.0 and V9.7

2-25

Chapter 3

Documentation Changes

3.1

New RSTSIE Version 10.0 Internals and Data Structures
Manual
RSTSIE Version 10.0 includes a new manual as part of its standard documentation, the RSTS/E Version 10.0 Internals and Data Structures Manual. This
significant addition to the RSTSIE documentation set provides technical information about the internal data structures and operation of the RSTSIE operating
system. This manual will prove invaluable to RSTSIE technical support people,
system programmers, or those with an interest in the inner workings of RSTSIE.

3.2 Revised Manuals
V10.0 includes new versions of the most commonly used manuals in the RSTSIE
documentation set. The following manuals have been revised for V10.0:

• RSTS / E Documentation Directory
• RSTS / E Maintenance Notebook
• RSTS/E Programming Manual
• RSTS / E Quick Reference Guide
• RSTS / E Release Notes
• RSTS / E System Directives Manual
• RSTS / E System Installation and Update Guide
• RSTS / E System Manager's Guide
• RSTS / E System User's Guide
• RSTS / E Task Builder Reference Manual
• PDP-ll SORT/MERGE User's Guide
The following RSTS/E manuals have not been revised for V10.0:

• BASIC-PLUS Language Manual
• EDT Editor Manual
• EDT Quick Reference Guide
• lAS / RSX-ll ODT Reference Manual
• Introduction to BASIC
• Introduction to the EDT Editor
• RSTS / E Guide to Writing Command Procedures
• PDP-II MACRO-ll Language Reference Manual
• RSTS / E Programmer's Utilities Manual
• RSTS/E RMS-ll: An Introduction
• RSTS / E RMS-ll MACRO Programmer's Guide
• RSTS/E RMS-ll User's Guide
• RSTS / E RMS-ll Utilities Manual
• RSTS / E RTll Utilities Manual
Documentation Changes

3-1

• RSTS/E RUNOFF User's Guide
• PDP-ll TEeO User's Guide
• RSTS / E Utilities Reference Manual

3.3 New Documentation Binders
New binders and dividers are also included with V10.0 to give your RSTSIE
documentation set a new look. The traditional RSTSIE Chinese Red binder color
has been replaced with the Digital standard grey.
If you have purchased a complete RSTSIE V10.0 Distribution Kit, then your kit

includes all RSTSIE manuals, binders, dividers and spines. Follow the directions
provided with your documentation to assemble your manuals into their proper
binders.
If you have purchased a RSTSIE V10.0 Update Kit, meaning you are upgrading

an existing version of RSTSIE, then your kit includes new binders and only those
manuals that have been revised for V10.0. Follow the directions provided with
your V10.0 documentation to combine your existing (unrevised) manuals with the
new manuals into the new binders. See Section 3.2 for a list of those manuals
being revised and those unchanged in V10.0.

3.4 Documentation Additions
This section describes information not presently included in the RSTSIE V10.0 or
related products' documentation set.

3.4.1

Maintenance Notebook
The following pages replace article 0.1.1 in the RSTS/E Maintenance Notebook
for VlO.O. Please remove the old version of article 0.1.1 and replace it with this
one.

3-2

Documentation Changes

I~-

Seq. No. 0.1.1 N

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

This article is an updated list of all soitware components included with RSTS/E VIO.O. The
information in this article supersedes the information in Appendix C of the RSTS j E System
Installation and Update Guide.
Neither Appendix C nor this article includes optional layered product components or temporary modules created during installation. Modules belonging to an optional package included
with RSTS/E will only be present if you choose to install that package on your system.
Listed with each module is its standard protection code and its expected location on your
system. Note that file protection codes play a critical role in the overall security of your
system. You should not change the protection code of any file included with RSTS/E unless
directed to do so. Changing a file's protection code to a different value may compromise
security or cause the program to fail in unpredictable ways.
An asterisk ( *) after the file name indicates that the file has RMS attributes.

RSTS/E V10.0 Maintenance Notebook

Seq. No. 0.1.1 N

System Files
Name .Typ
BAnB .SYS
INIT .SYS
BACKUP.TSK
DCL
.RTS
PKG002.MSG
CONFIG.SYS
SWAP .SYS
RT11 .RTS
CSP100.LIB
REMESC.TSK
NETCHK.TSK
UPDATE. COM
SYSINLCOM
CSPHLP.COM
LPRES .COM
CHECK .COM
CSPLNG.COM
MONBLD.COM
INSPKG.COM
DELLOG.COM
CSP1 .HLP
LP
. HLP
LP1
.HLP
. HLP
LP2
MICRO .HLP
BEGIN .COM
LP
. COM
SWAP1 .SYS
LOGIN .COM
BASIC .RTS

Size
Prot
8 P < 63>
618CP < 60>
141C <232>
114C <232>
7C < 40>
1CP < 60>
136CP < 63>
20C < 60>
41C < 60>
13C <124>
13C <124>
3C <124>
8C <124>
9C <104>
13C <104>
3C <104>
24C <104>
15C <104>
14C <104>
4C <104>
1C <104>
1C <104>
1C <104>
1C <104>
2
< 60>
28C <104>
23C <104>
3264CPL< 60>
5C <104>
69C < 60>

Name .Typ
SATT .SYS
ERR
. ERR
SYSGEN.SIL
PKG001.MSG
RSX
.RTS
GETSYS.TSK
CRASH .SYS
ODT
.SYS
CSPLIB.LIB
SYSDIE.TSK
INSTAL.COM
COPYUP.COM
RECOVR.COM
SETPAS.COM
LISTER.COM
MONITR.COM
ASSLOG.COM
VOLCHK.COM
NETDEL.COM
CSP
. HLP
CSP2 . HLP
LPX
. HLP
LPX1 . HLP
CSPLST.DAT
CSPRES.COM
CSP
. COM
MAIN .COM
RSTS .SIL
START .COM

Total of 6438 blocks in 59 files in

Size
Prot
14CP < 63>
16CP < 40>
681CP < 60>
8C < 40>
6C < 60>
55C <124>
123CP < 63>
14
< 60>
41C < 60>
36C <124>
3C <124>
2C <124>
12C <124>
2C <104>
8C <104>
16C <104>
13C <104>
4C <104>
9C <104>
2C <104>
2C <104>
1C <104>
1C <104>
2C <104>
17C <104>
35C <104>
22C <104>
672C L< 60>
21C <124>

SY: [0,1]

Help Package
Name .Typ
DCALLO.HLP
DCASSI.HLP
DCASQU.HLP
DCATTA.HLP
DCBASLHLP
DCBDIR.HLP
DCBP2 .HLP
DCBYE .HLP
DCCCL .HLP
DCCLLG.HLP
DCCOPY.HLP
DCCREA.HLP
DCCRVI.HLP
DCDEAL.HLP
DCDEPO.HLP
DCDSQU.HLP
DCDEFI.HLP
DCDEVI.HLP
DCDFCS.HLP
DCDIFF.HLP
DCDISM.HLP
DCDLCM.HLP
DCDLEN.HLP
DCDLRQ.HLP
DCDLSV.HLP
DCDMMT.HLP
DCDPSY.HLP

Size
7
7

2
4
3

20
3
3
3
2

23
8

6
2
3
3
1
3

11
5
1
1
3

10
2
3

Prot
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

Name .Typ
DCAPPE.HLP
DCASPO.HLP
DCAT . HLP
DCBACK.HLP
DCBCOP.HLP
DCBlMA.HLP
DCBROA.HLP
DCLCCC.HLP
DCCLOS.HLP
DCCLQU.HLP
DCCRAC.HLP
DCCRPO.HLP
DCDAPO.HLP
DCDEAS.HLP
DCDETA.HLP
DCDSSY.HLP
DCDELE.HLP
DCDFCM.HLP
DCDIBO.HLP
DCDIRE.HLP
DCDLAC.HLP
DCDLCS.HLP
DCDLQU.HLP
DCDLSB.HLP
DCDMDK.HLP
DCDUMP.HLP
DCEDIT.HLP

RSTS/E V10.0 Maintenance Notebook

Size
8
6
3

35
29
22
5
33
2
2

18
13
2
3
4
1

11
1
2

11
8
2
2
3
3
1
9

Prot
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

SY: [0,2]

Seq. No. 0.1.1 N

DCEOD .HLP
DCFOFO.HLP
DCFORT.HLP
DCGOSU.HLP
DCHANG.HLP
DCIF • HLP
DCINER.HLP
DCINIQ.HLP
DCINMT.HLP
DCINQU.HLP
DCINST.HLP
DCINSW.HLP
DCLOAD.HLP
DCLOID.HLP
DCLOOV.HLP
DCMOUN.HLP
DCMTMT.HLP
DCONCC.HLP
DCOPLG.HLP
DCPRIN.HLP
DCRECA.HLP
DCREJO.HLP
DCREMO.HLP
DCRERU.HLP
DCREQU.HLP
DCREST.HLP
DCRPLY.HLP
DCSET .HLP
DCSECA.HLP
DCSEDA.HLP
DCSEDV.HLP
DCSEEN.HLP
DCSEHO.HLP
DCSELG.HLP
DCSEND.HLP
DCSENO.HLP
DCSEON.HLP
DCSEPA.HLP
DCSEPO.HLP
DCSEPT.HLP
DCSESV.HLP
DCSETE.HLP
DCSEVE.HLP
DCSHAL.HLP
DCSHCA.HLP
DCSHCS.HLP
DCSHDK.HLP
DCSHDV.HLP
DCSHFI.HLP
DCSHFS.HLP
DCSHLB.HLP
DCSHLS.HLP
DCSHNT.HLP
DCSHOW.HLP
DCSHPR.HLP
DCSHQU.HLP
DCSHRQ.HLP
DCSHRV.HLP
DCSHSV.HLP
DCSHTE.HLP
DCSHUS.HLP
DCSTOP.HLP
DCSTQM.HLP
DCSPOS.HLP
DCSPQM.HLP

3
3

2
5
2
4
6

22
6
8
2

11
1
3
4
1
5
5

10
21
10
3
2

2
8

36
7
3
8
4
2
9

3
2
3
2
1
3
8
4
9

47
3
3
7
2
6
3
1
5
2
1
1
3
2

12
13
2

14
10
9

3
7

4
4

< 40>
< 40>
< 40>

< 40>
< 40>

< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

< 40>

< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

DCEXIT.HLP
DCFORC.HLP
DCF77 .HLP
DCGOTO.HLP
DCHELP.HLP
DCINDK.HLP
DCINIT.HLP
DCINLI.HLP
DCINOV.HLP
DCINRU.HLP
DCINSV.HLP
DCLINK.HLP
DCLOGI.HLP
DCLOGO.HLP
DCMACR.HLP
DCMTDK.HLP
DCON . HLP
DCOPEN.HLP
DCOPQU.HLP
DCREAD.HLP
DCREER.HLP
DCRELI.HLP
DCREOV.HLP
DCRENA.HLP
DCRESW.HLP
DCRETU.HLP
DCRUN .HLP
DCSEAC.HLP
DCSECO.HLP
DCSEDT.HLP
DCSEEC.HLP
DCSEFI.HLP
DCSEJO.HLP
DCSENC.HLP
DCSEJ;'IE.HLP
DCSENV.HLP
DCSEOS.HLP
DCSEPN.HLP
DCSEPR.HLP
DCSEQU.HLP
DCSESY.HLP
DCSETI.HLP
DCSHAC.HLP
DCSHBU.HLP
DCSHCM.HLP
DCSHDA.HLP
DCSHDT.HLP
DCSHEN.HLP
DCSHFO.HLP
DCSHJO.HLP
DCSHLO.HLP
DCSHMY.HLP
DCSHOS.HLP
DCSHPO.HLP
DCSHPV.HLP
DCSHQT.HLP
DCSHRT.HLP
DCSHSB.HLP
DCSHSY.HLP
DCSHTI.HLP
DCSTAR.HLP
DCSTOS.HLP
DCSTQU.HLP
DCSPQU.HLP
DCSPSV.HLP

3
5
3
3
5

15
2

< 40>
< 40>

< 40>
< 40>
< 40>
< 40>
< 40>

< 40>
< 40>

11
13

< 40>
< 40>

5
6
5
2

< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

10
9

10
2
5
2
2
2

12
2
5
4

14
1
2
3
B

6
2
3
2
2
9
9

13
19
2

10
3
1
1
1

13
2
5
5
2
3

7
2
3
2
2
2
1
2
7
2
3
7

< 40>

< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

RSTS/E V10.0 Maintenance Notebook 3

Seq. No. 0.1.1 N

DCSTSV.HLP
DCTYPE.HLP
DCUNLI.HLP
DCUNOV.HLP
DCWRIT.HLP
ADVANC.HLP
BPCOMM.HLP
BPFUNC.HLP
BPSTAT.HLP
COMREC.HLP
CTRLT .HLP
DCL
. HLP
DIRECT. HLP
DISKS .HLP
ERRDIS.HLP
EXPRES.HLP
FIT
. HLP
FORMS .HLP
HELP .TSK
KEYS . HLP
LEVELS.HLP
MAGTAP.HLP
PASSWD.HLP
PROGRM.HLP
PIPDIR.HLP
PLEHLP.HLP
PLEQUE.HLP
QUEHLP.HLP
QUOTAS.HLP
RT11 • HLP
SERVRS.HLP
SYSHLP.HLP
TIMES .HLP
TECOFL.HLP
TYPHLP.HLP
VTEDKP.HLP
DCSHOD.HLP
DCCRSV.HLP
DCSHVL.HLP
DCSHCO.HLP
DCSTLA.HLP
DCCRSL.HLP
DCSHSL.HLP
DCSHCL.HLP
DCSHSS.HLP
DCWAIT.HLP
DCLMGE.HLP

a
a
3
3
6

20
12
14
19

a
a
2
4

15
7

6
11
1a
29C
14
6
12
10
2
3
6
4

a
11
13
7

22
7
6
3
6
1
1
1
1
2
2
2
4
3
4

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

DCSUBM.HLP
DCUNID.HLP
DCUNLO.HLP
DCUNRU.HLP
ACCNTS.HLP
BPCHLP.HLP
BPCREF.HLP
BPHELP.HLP
COPHLP.HLP
COPY . HLP
DATES .HLP
DCMAIL.HLP
DIRHLP.HLP
ENTRYS.HLP
ERRHLP.HLP
FILES .HLP
FITHLP.HLP
FUNCTN.HLP
HELP . HLP
LABELS.HLP
LINEED.HLP
OPERAT.HLP
PRIVS .HLP
PIPHLP.HLP
PIPSAV.HLP
PLEBAT.HLP
PLESPL.HLP
QUEUES.HLP
RSX
. HLP
RUNTIM.HLP
SYMBOL.HLP
TERMNL.HLP
TECHLP.HLP
TECOMD.HLP

20
2

Size
97C
15C
52C
82C
59C

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

2
2

30
4
6
2
4
3
7
3
4

11
7

19
11
31

a
4
7
7

12
31
31
4
6

20
3
9

14
4
5

12
12

UTLH~P.HLP

VTEHLP.HLP
DCSEOD.HLP
DCSEVL.HLP
DCDESV.HLP
DCSENL.HLP
DCSHNL.HLP
DCSESL.HLP
DCDESL.HLP
DCSHTL.HLP
DCSPLA.HLP
DCLSRT.HLP

Total of 1935 blocks in 277 files in

1
1
1
7
2
2
2
2
2

~'~-

SY: [0,2]

Error Logging Package
Name .Typ
ERRDAT.FIL
ERRINT.TSK
ERRDIS.TSK
ANALYS.TSK
ANALY2.TSK

Size
67C
laC
44C
5ac
71C

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

Name .Typ
MSCPER.FIL
ERRCPY.TSK
ERRDET.TSK
ANALY1.TSK
ANALY3.TSK

Total of 563 blocks in 10 files in

RSTS/E V10.0 Maintenance Notebook

SY: [0,3]

Seq. No. 0.1.1 N

Update Package
Name .Typ
PA0401.006
PA0401.001
PA0401.003
PA0401.005
PA0304.002
PATCH .DAT
CPATCH.TSK
UTILTY.TSK

Size
1
2
1
1
2
1
24C
48C

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

Name .Typ
PA0411.003
PA0401.002
PA0401.004
PA0304.001
PATCH .BAK
BUILD .TSK
AUTOED.TSK

Total of 173 blocks in 15 files in

Size
1
1
1
3
1
59C
27C

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

SY: [0,4]

Size
21C
21C
28C
26C

Prot
<124>
<124>
<124>
<124>

SY: [0,5]

S.ize
409C
2

Prot
<232>
< 40>

SY: [0,6]

Size
51C
30C
61C
37C
51C
52C

Prot
<252>
<252>
<252>
<252>
<252>
<252>

SY: [0,7]

Size
12C
89C
87C
90C
80C
93C
87C

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

SY: [0,8]

SY: [0,4]

Device Testing Package
Name .Typ
DSKSEK.TSK
LPEXER.TSK
CPEXER.TSK
KBEXER.TSK

Size
18C
14C
28C
17C

Prot
<124>
<124>
<124>
<124>

Name .Typ
DSKEXR.TSK
DXEXER.TSK
CPUTST.TSK
MTEXER.TSK

Total of 173 blocks in 8 files in

SY: [0,5]

PrintlBatch Services Package
Name .Typ
PBS
.TSK
PBSERR.ERR
PBS
.SYS*

Size
196C
57
32

Prot
<232>
< 40>
<188>

Name .Typ
PBSMGR.TSK
FORMS .SYS

Total of 696 blocks in 5 files in

SY: [0,6]

File Restore Package
Name .Typ
BACKUP.HLP
BACLST.TSK
BACDIR.TSK
BACLAB.TSK
BACCOM.TSK
BACENT.TSK
BACKUP.PRM

Size
12
55C
56C
45C
47C
41C
5

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

Name .Typ
RESTOR.TSK
BACCON.TSK
BACMNT.TSK
BACDSK.TSK
BACLOD.TSK
BACFRM.TSK

Total of 543 blocks in 13 files in

SY: [0,7]

OPSER-based Spooling Package
Name .Typ
CHARS .QUE
QUEMAN.TSK
OPSER .TSK
SPOOL .TSK
SPLRUN.TSK
BATIDL.TSK
BATRUN.TSK
PLEASE.TSK

Size
2
61C
51C
83C
90C
79C
88C
40C

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

Name .Typ
BATCH .DCD
QUMRUN.TSK
OPSRUN.TSK
SPLIDL.TSK
BATCH .TSK
BATDEC.TSK
QUE
.TSK

Total of 1032 blocks in 15 files in

SY: [0,8]

RSTS/E V10.0 Maintenance Notebook 5

Seq. No. 0.1.1 N

Unsupported Utility Package
Name .Typ
DSKDMP.BAS
QSTATS.B2S
BPDA .BAS
LQSTAT.BAS
MEMORY. BAS
CONNEC.BAS
DIALER. DOC
RSTSFL.OBJ*
RSTSFL.DOC
MEMORY.TSK
B2CREF.TSK
B2CREF.DOC
RNO
.RNO
RNOBLD.ODL
COMND . MAC
ERMSG . MAC
HYPHEN.MAC
PINDX . MAC
RNFIO . MAC
RUNOFF.MAC
EMS
.COM
DSKDMP.TSK
CONNEC.TSK
EMTCPY.TSK
QSTATS.TSK
SRCCOM. SAV

Size
19
59
59
19
15
46
63
42
2
13C
113C
2
85
2
7
10
54
9
9
71

lac
29C
38C
24C
17C

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

Name .Typ
STATUS.B2S
DSKPEK.OBJ*
DSKDMP.HLP
QSTATS.DOC
FLOAT . BAS
DIALER.BAS
EMTCPY.BAS
RSTSFL.OLB*
RSTSFL.HLP
FLOAT .TSK
B2CREF.HLP
RNO
.TSK
RNOBLD.CMD
RNPRE . MAC
CMTAB . MAC
FMTCM . MAC
INDEX . MAC
RNCMD . MAC
RNORSX.MAC
START . MAC
DUMP .SAV
BPDA .TSK
DIALER.TSK
STATUS.TSK
LQSTAT.TSK

Total of 1666 blocks in 51 files in

Size
92
1
26
32
19
85

10/;
102C
6
21C
12
72C
6

Prot
< 60>
< 60>
< 40>
< 60>
<: 60>

SY: [0,9]

< 60>
< 60>

< 60>

10C
37C
44C
56C
22C

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

Size
169C
133C
179C
20C
15C
10C
18C
7C
3

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

SY: [0,10]

Prot
< 40>
< 40>

SY: [0,11]

11
26
11
22
5

SY: [0,9]

RMS·ll Package
Name .Typ
RMSBCK.TSK
RMSDEF.TSK
RMSCNV.TSK
RMSIFL.TSK
RMSLBA.LIB
RMSLBC.LIB
RMSLBE.LIB
DAPRES.LIB
RMSRES.TSK*
RESLIB.OOL

Size
149C
134C
215C
141C
18C
14C
14C
43C
18
0

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

Name .Typ
RMSR~T.TSK

RMSDSP.TSK
RMSDES.TSK
RMSRES.LIB
RMSLBB.LIB
RMSLBD.LIB
RMSLBF.LIB
DAPENV.LIB
RMSRES.STB*

Total of 1300 blocks in 19 files in

SY: [0,10]

EDT Package
Nan,e .Typ
EDT52 .DOC
EDT200.DOC
EDT
.TSK

Size
3
4
238C

Prot
< 40>
< 40>
<104>

Name .Typ
EDTI00.DOC
EDTKIT.DOC

Total of 287 blocks in 5 files in

RSTS/E V10.0 Maintenance Notebook

SY: [0,11]

Size
3
39

Seq. No. 0.1.1 N

SYSGEN Components and BASIC-PLUS Package
Name .Typ
MONITR.CMD
RSXRTS.CMD
CHECK .MAC
KBDEF .MAC
CRA
.OBJ
MCP
.OBJ
OPN
.OBJ
KVR
.OBJ
XTR
.OBJ
EM2
.OBJ
GRD
.OBJ
FIPLRG.OBJ
NOD
.OBJ
DLPORT.OBJ
VHPORT.OBJ
PDVVEC.OBJ
KBD
.OBJ
KIN
.OBJ
SES
.OBJ
TRN
.OBJ
EVL
.OBJ
UNA
.OBJ
OVRLRG.OBJ
OVLHD .OBJ
DEFALT.STB
SYSGEN.SAV
BPLGEN.TSK
MA2
.OBJ
MA2F .OBJ
MA4F .OBJ
XL2
.OBJ
XL2F .OBJ
XL4F .OBJ
XT2I .OBJ
XT4
.OBJ
SF
.OBJ
PU
.OBJ
SN
.OBJ
VE
.OBJ
LA
.OBJ
M18
.OBJ

Size
2
1

22
44
8
3
3
3

2
3
3
2
4
2
2
1
4
3
2
3
2
4
4
1

1
104C
42C
16
14
16
3

2
2
3
3
6
5

2
2

10
1

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 40>
< 60>
<124>
<124>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>

Name .Typ
RJ2780.CMD
HOOK .SAV
TBL
. MAC
RSTS .OBJ
DSK
.OBJ
BBR
.OBJ
XVR
.OBJ
.OBJ
MVR
EMT
.OBJ
GEN
.OBJ
RSX
.OBJ
FMS
.OBJ
DHPORT.OBJ
DZPORT.OBJ
PKPORT.OBJ
TERCLS.OBJ
KBX
.OBJ
LAT
.OBJ
NSP
.OBJ
RDM
.OBJ
DMP
.OBJ
QNA
.OBJ
OV2
.OBJ
DEFALT.SAV
BUFCHK.TSK
BASIC .CMD
RTS
.OBJ
MA2I .OBJ
MA4
.OBJ
MA4D .OBJ
XL2I .OBJ
XL4
.OBJ
XT2
.OBJ
XT2F .OBJ
XT4F .OBJ
IO
.OBJ
MX
.OBJ
DBG
.OBJ
DI
.OBJ
LAD
.OBJ
BASIC .COM

Total of 1864 blocks in 82 files in

Size
25
28C
120
1076
5
3

2
3
3
3

2
3
2
2
4

15
2
3

2
2
4
2
4C
21C
1
74
14
19

14
3

3
2
2
6
8
2
1

10
2C

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

SY: [0,12]

RSTS/E V10.0 Maintenance Notebook

Seq. No. 0.1.1 N

TECO Package
Name .Typ
TECO .RTS
TYPE .TEC
VTEDIT.DOC
TECO .DOC
TECKBM.TEC
SEARCH.TEC
FMTMAC.TEC
TYPE .TES
FMTMAC.TES
TECKBM.TES
SEARCH.TES
TECOLB.OBJ
SCREEN.OBJ
SCROLL.OBJ
CRTRUB.MAC

Size
48C
7C
119
995
3C
5C
1C
17
9
3
9
68
15
4
65

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

Name .Typ
TECO .TEC
VTEDIT.TEC
TECORN.DOC
TECO .INI
LOCAL .TEC
.TEC
SQU
TECO .TES
VTEDIT.TES
TECOIN.TES
LOCAL .TES
SQU
.TES
GEXIT .OBJ
SCRINS.OBJ
CRTRUB.OBJ

Total of 1641 blocks in 29 files in

Size
10C
24C
108
8
3C
10C
28
34
18
3
15
3
4
5

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

SY:[0,13]

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

SY: [0,14]

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
<104>

SY: [0,15]

Prot
60>
60>
60>
60>
60>

SY:[0,17]

SY: [0,13]

Auxiliary Library Package
Name .Typ
ODT
.TSK
QUOLST.TSK
GRIPE .TSK
FIT
.TSK
BPCREF.TSK
RUNOFF.TSK

Size
38C
50C
17C
60C
25C
59C

Prot
<104>
<232>
<232>
<232>
<104>
<104>

Name .Typ
COPY .TSK
TALK .TSK
DISPLY.TSK
PMDUMP.TSK
BPCRF1.TSK
DSKCVT.TSK

Total of 519 blocks in 12 files in

Size
25C
12C
72C
52C
SIC
58C

SY: [0,14]

SORTIMERGE Package
Name .Typ
V96BUG.FIX
SRTUTL.ODL
MGEUTL.ODL
MGESHR.OLB
SRTUTL.CMD*
SRTUTL.TSK*
SRTTRN.TSK

Size
1
12
10
201
4
389C
103C

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
<104>
<104>

Name .Typ
SRTL;rB.OLB
MGELIB.OLB
SRTSHR.OLB
RELEAS.NOT
MGEUTL.CMD*
MGEUTL.TSK*

Total of 1739 blocks in 13 files in

Size
216
196
220
15
4
368C

SY: [0,15]

SOURCE Package
Name .Typ
ATPK . BAS
DISPLY.B2S
DSPMUL.MAC
LOGIN .BAS
SHUTUP.BAS

Size
97
199
4
91
155

<
<
<
<
<

Prot
60>
60>
60>
60>
60>

Name .Typ
DIRECT.BAS
DISPLY.COM
HELP . BAS
LOGOUT.BAS
SYSTAT.B2S

Total of 964 blocks in 10 files in

RSTS/E V10.0 Maintenance Notebook

Size
100
2
101
33
182

SY:[0,17]

<
<
<
<
<

Seq. No. 0.1.1 N

EDT Build Package
Name .Typ
EDTLIB.OLB
EDTR1 .ODL
EDTR2 .ODL
EDTR3 .ODL
EDTR4 .ODL
EDTR5 .ODL

Size
378
28
32
32
32
32

<
<
<
<
<
<

Prot
60>
60>
60>
60>
60>
60>

Name
EDTR1
EDTR2
EDTR3
EDTR4
EDTR5

Total of 539 blocks in 11 files in

.Typ
.CMD
.CMD
.CMD
.CMD
.CMD

Size
1
1
1
1
1

Prot
60>
60>
60>
60>
60>

SY: [0,18]

Size
87C

Prot
<232>

SY: [0,20]

Size
34C
271
2
2
222
9
12
3
4
2
2
6
39
142
8
223
216
11
10
16

Prot
< 60>
< 40>
< 40>
< 40>
< 40>
< 60>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

SY: [1,1]

<
<
<
<
<

SY: [0,18]

OMS Package
Name .Typ
.TSK
OMS

Size
38C

Prot
<252>

Name .Typ
OMSMGR.TSK

Total of 125 blocks in 2 files in

SY: [0,20]

Program Development Libraries
Name .Typ
CSP100.STB*
SYSLIB.OLB*
BP2
.LNK
.LNK*
F77
RMSMAC . MLB *
RMSDAP.OLB*
RMS11 .ODL*
RMS11S.0DL*
RMS11X.ODL*
RMSRLX.ODL
DAP11X.ODL*
DAPSLX.ODL*
RMSRES.STB*
DAPRES. STB*
RMS
.OOL
ODTID .OBJ*
DCLC81.HLP
MGELIB.OLB
SRTREC.ODL
MGEREC.ODL
STMGRC.ODL

Size
8C
280
3
3
189
102
85
3
5
2
5
2
3
2
0
13
1
197
11
9
15

Prot
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 60>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

Name .Typ
CSP100.TSK*
RSXMAC . SML *
C81
.LNK
RSX11 .LNK*
RMSLIB.OLB*
RMSFUN.OBJ*
RORMS1.MAC*
RMS12S.0DL*
RMS12X.ODL*
RMSSLX.ODL*
DAPRLX.ODL*
RMSRES.TSK*
DAPRES.TSK*
RMSDES.HLP*
ODT
.OBJ*
EDTHEL.HLP*
SRTLIB.OLB
SRTFIL.ODL
MGEFIL.ODL
STMGFL.ODL

Total of 2172 blocks in 41 files in

SY: [1,1]

RSTS/E V10.0 Maintenance Notebook 9

Seq. No. 0.1.1 N

System Library Package
Name .Typ
GETSYS.TMP
DSKINT.TSK
ACTMGR.TSK
DCLAUX.TSK
PIP
.SAV
CREF .SAV
LIBR .SAV
ONLPAT.SAV
KERNEL.MAC
VEROOL.SYS
SYSGEN. COM
SYSLIB.OBJ
LOGOUT.TSK
SYSTAT.TSK
SWITCH.TSK
SYSMAC.SML
TERMGR.TSK
PAT
.SAV
MAKSIL.TSK
STK
.TSK
.TSK
LBR
CRF
.TSK
RSX
.OOL
BUILD .TSK
CPATCH.TSK
PLEASE.TSK
SMRES .CMD
INSTAL. LOG

Size
1
1l0C
300C
54C
61C
6C
28C
71C
162
0
24
73
22C
63C
llC
46
138C
llC
52C
221C
66C
47C
0
5C
5C
5C
1
66

Prot
< 60>
<232>
<232>
<232>
<232>
<104>
<104>
<104>
< 60>
< 60>
< 60>
< 40>
<232>
<232>
<232>
< 40>
<232>
<104>
<104>
<104>
<104>
<104>
< 60>
<124>
<124>
<232>
< 60>
< 60>

N8me .Typ
UTLMGR.TSK
ONLCLN.TSK
SHUTUP.TSK
SILUS .SAV
MACRO .SAV
LINK .SAV
ERR
.STB
COMMON.MAC
DCLUTL.TSK
CONFIG.MAC
GLOBAL.COM
LOGIN .TSK
DIRECT.TSK
FILCOM.TSK
ATPK .TSK
SAVRES.SAV
LATMGR.TSK
REORDR.TSK
TKB
.TSK
MAC
.TSK
PAT
.TSK
PRELIN.TSK
UTILTY.TSK
AUTOED.TSK
QUE
.TSK
BPLGEN.COM
SRTUTL.MAP*

Total of 3629 blocks in 55 files in

10 RSTS/E V10.0 Maintenance Notebook

Size
316C
111C
72C
40C
63C
57C
3
39
26C
5
1
46C
58C
48C
30C
209C
104C
86C
221C
100C
55C
46C
5C
5C
5C
3
226

SY: [1,2]

Prot
<232>
<232>
<232>
<104>
<104>
<104>
< 40>
< 40>
<232>
< 60>
< 60>
<232>
<232>
<104>
<232>
<124>
<232>
<232>
<104>
<104>
<104>
<232>
<124>
<124>
<232>
< 60>
< 60>

SY: [1,2]

,~~

Article 3.4.1 in the RSTSjE Maintenance Notebook for V10.0 contains an
incorrect base address. Please remove the old version of article 3.4.1 and replace
it with this one.

Documentation Changes 3.....3.

3-4

Documentation Changes

Seq. No. 3.4.1 F

Changing Special LOGIN Terminal -

Terminal Service Feature Patch

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

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

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

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

(RETURN for installed monitor SIL)

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

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

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

RSTS/E V10.0 Maintenance Notebook

Seq. No. 3.4.1 F

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

RSTS/E V10.O Maintenance Notebook

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

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

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

The Component. Subcomponent section of the RSTS / E Maintenance Notebook
for V10.0 accidentally left out subcomponent numbers for package corrections.
To correct this problem, please remove pages 3 through 10 of the RSTS / E
Maintenance Notebook and replace them with the following eight pages.

DocumentationChanges

3-5

3-6

Documentation Changes

2 Component.Subcomponent Assignments

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

RSTSIE MONITOR
0.0
0.1
0.2

RSTS/E V10.0 General Notes

1.0
1.1
1.2
1.3

Initialization

2.0
2.1
2.2
2.3

System Installation and Update

3.0
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.14
3.15

Executive

4.0
4.1
4.2

BASIC-PLUS

System Notes
System Management Guidelines

INIT.SYS Corrections
INIT.SYS Program Notes
INIT.SYS Restrictions

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

Monitor Corrections
Monitor Notes
Monitor Restrictions
Terminal Service Corrections
Terminal Service Notes
Terminal Service Restrictions
File Processor Corrections
File Processor Notes
File Processor Restrictions
Device Driver Corrections
Device Driver Notes
Device Driver Restrictions
FMS Monitor Corrections
FMS Monitor Notes
FMS Monitor Restrictions

BASIC-PLUS Corrections
BASIC-PLUS Notes

RSTS/E V10.0 Maintenance Notebook 3

4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11

BASIC-PLUS Restrictions
Programming Hints
Math Packages
Matrix Functions
PRINT-USING
Record I/O
Virtual Core
String Arithmetic
Optional BASIC-PLUS Features

5.0

(Reserved)

6.0
6.1
6.2
6.3

System Files

7.0
7.1
7.2
7.3

DECnetlE Monitor Package V4.1

System Files Notes
System Files Restrictions
System Files Corrections

DECnetlE Monitor Corrections
Package Notes
Package Restrictions

RSTSIE UTILITIES
8.0
8.1
8.2
8.3

Help Package (HELP$)

9.0
9.1
9.2
9.3

TECO Package (TECO$)

10.0
10.1
10.2
10.3

System Library ($)

11.0
11.1
11.2
11.3

Auxiliary Library (AUXLlB$)

Package Notes
Package Restrictions
Package Corrections

Library Notes
Library Restrictions
Library Corrections

Package Notes
Package Restrictions
Package Corrections

RSTS/E V10.0 Maintenance Notebook

12.0
12.1
12.2
12.3

Error Logging Package (ERROR$)

13.0

RESTOR Package (RESTOR$)

13.1
13.2
13.3

Package Notes
Package Restrictions
Package Corrections

14.0
14.1
14.2
14.3

Operator Services and Spooling Package (OPSER$)

15.0
15.1

Print/Batch Services Package (PBS$)

15.2
15.3

Package Notes
Package Restrictions
Package Corrections

16.0
16.1
16.2
16.3

Unsupported Package (UNSUPP$)

17.0

Layered Product Update Package (UPDATE$)

Package Notes
Package Restrictions
Package Corrections

17.1

Package Notes

17.2
17.3

Package Restrictions

18.0
18.1
18.2
18.3

Package Corrections
Device Test Package (TEST$)
Package Notes
Package Restrictions
Package Corrections

19.0
19.1
19.2
19.3

Operator/Message Services Package (OMS$)

20.0

CUSP Source Package (SOURCE$)

20.1
20.2

Package Notes
Package Restrictions
Package Corrections

Package Notes
Package Restrictions

RSTS/E V10.0 Maintenance Notebook 5

20.3
21.0

Package Corrections
SORT/MERGE V3.0 (SORT$)

21.1

Package Notes

21.2

Package Restrictions

21.3

Package Corrections

22.0

RMS·11 V2.0 (RMS$)

22.1

Package Notes

22.2

Package Restrictions

22.3

Package Corrections

23.0

EDT V3.0 (EDT$)

23.1

Package Notes

23.2

Package Restrictions

23.3

Package Corrections

24.0

(Reserved)

25.0

(Reserved)

RSTSIE DOCUMENTATION
26.0

Documentation

26.1

RSTS/E Documentation Directory

AA·2642H· TC

26.2

RSTS/E V10.0 Release Notes

AA·5246H·TC

26.3

RSTS/E V10.0 Maintenance Notebook

AA·L997E·TC

26.4

RSTS/E System Installation and Update Guide

AA·2669K· TC

26.5

RSTS/E System Manager's Guide

AA·2762H·TC

26.6

RSTS/E System User's Guide

AA·EZ12B· TC

26.7

RSTS/E Guide to Writing Command Procedures

AA·CF03A·TC

26.8

RSTS/E Utilities Reference Manual

AA·EZ11A·TC

26.9

Introduction to the EDT Editor

AA·K443A·TC

26.10

PDp·11 SORT/MERGE User's Guide

AA·CI67B·TC

26.11

RSTS/E RUNOFF User's Guide

AA·3337B· TC

26.12

EDT Editor Manual

AA·M476A·TK

26.13

RSTS/E Task Builder Reference Manual

AA·5072D·TC

26.14

RSTS/E Programmer's Utilities Manual

AA-D749A-TC

RSTS/E Programmer's Utilities Manual Update 1

AD-D749A·T1

RSTS/E Programmer's Utilities Manual Update 2

AD-D749A-T2

26.15

RSTS/E RT11 Utilities Manual

AA-M213A-TC

26.16

PDP·11 TECO User's Guide

AA-K420B-TC

26.17

BASIC-PLUS Language Manual

AA-2623D-TC

RSTS/E V10.0 Maintenance Notebook

26.18

RSTS/E Programming Manual

AA-EZ09B-TC

26.19

RSTS/E System Directives Manual

AA-EZ1 OB-TC

26.20

IAS/RSX-11 ODT Reference Manual

AA-M507A-TC

26.21

PDP-11 MACRO-11 language Reference Manual

AA-KX10A-TC

PDP-11 MACRO-11 language Reference Manual Update

AD-KX1 08A-T1

26.22

RSTS/E RMS-11 MACRO Programmer's Guide

AA-P507A-TC

26.23

RSTS/E RMS-11: An Introduction

AA-P508A-TC

26.24

RSTS/E RMS-11 User's Guide

AA-P510A-TC

26.25

RSTS/E RMS-11 Utilities Manual

AA-P509A-TC

26.26

RSTS/E Quick Reference Guide

AA-EZ13C-TC

26.27

Introduction to BASIC

AA-0155B-TK

26.28

EDT Quick Reference Guide

AA-M477A-TK

26.29

RSTS/E Vi 0.0 Internals and Data Structures Manual

AA-PB60A-TC

RUN-TIME SYSTEMS SUPPORT
27.0

DCl Run-time System and Utilities

27.1

Package Notes

27.2

Package Restrictions

27.3

Package Corrections

28.0

RSX-11 Emulator and Utilities

28.1

Package Notes

28.2

Package Restrictions

28.3

Package Corrections

29.0

RT-11 Emulator and Utilities

29.1

Package Notes

29.2

Package Restrictions

29.3

Package Corrections

30.0

(Reserved)

OPTIONAL SOFTWARE
31.0

DECnetiE Utilities V4.1 (DECNET$)

31.1

Package Notes

31.2

Package Restrictions

31.3

Package Corrections

32.0
32.1

DECnetiE V4.1 Documentation
DECnetiE V4.1 Release Notes

AA-M269D-TC

RSTS/E Vi 0.0 Maintenance Notebook

32.2

DECnetlE V4.1 System Manager's Guide

32.3

DECnetlE V4.0 Network Programming in BASIC-PLUS

32.4

DECnetlE V4.0 Network Programming in MACRO

32.S

DECnetlE V4.0 Network Programming in FORTRAN

32.6

DECnetlE V4.0 Network Programming in COBOL

32.7

DECnetlE V4.0 Guide to User Utilities

AA-HS04C-TC

32.8

DECnetlE V4.0 Network Installation and Update Guide

AA-K714C-TC

AA-HSOSD-TC

and BASIC-PLUS-2

33.0

PDP-11 C V1.0

33.1

Package Notes

33.2

Package Restrictions

33.3

Package Corrections

34.0

WPS-PLUS/RSTS V1.1

34.1

Package Notes

34.2

Package Restrictions

34.3

Package Corrections

3S.0

(Reserved)

36.0

DECmail-11 V3.1

36.1

Package Notes

36.2

Package Restrictions

36.3

Package Corrections

37.0

(Reserved)

to
44.0
4S.0

DECdx/RSTS V1.0

4S.1

Package Notes

4S.2

Package Restrictions

4S.3

Package Corrections

46.0

(Reserved)

47.0

(Reserved)

48.0

BASIC-PLUS-2 V2.6

48.1

Package Notes

48.2

Package Restrictions

48.3

Package Corrections

RSTS/E V10.0 Maintenance Notebook

49.0
49.1

DATATRIEVE-11 V3.3A
Package Notes

49.2

Package Restrictions

49.3

Package Corrections

50.0

(Reserved)

to
54.0
55.0

FORTRAN IV V2.8

55.1

Package Notes

55.2

Package Restrictions

55.3

Package Corrections

56.0

COBOL-81 V3.0

56.1

Package Notes

56.2

Package Restrictions

56.3

Package Corrections

57.0

FORTRAN-77 VS.4

57.1

Package Notes

57.2

Package Restrictions

57.3

Package Corrections

58.0

PDP-11 Symbolic Debugger V2.1

58.1

Package Notes

58.2

Package Restrictions

58.3

Package Corrections

59.0

(Reserved)

60.0

(Reserved)

61.0

(Reserved)

62.0

PLXY-11 V1.3

62.1

Package Notes

62.2

Package Restrictions

62.3

Package Corrections

63.0

(Reserved)

to
67.0

RSTS/E V10.0.Maintenance Notebook

68.0
68.1

MENU-11 V2.0
Package Notes

68.2

Package Restrictions

68.3

Package Corrections

(Reserved)

69.0
to

72.0

73.0
73.1
73.2
73.3

DIBOL V6.1
Package Notes
Package Restrictions
Package Corrections

(Reserved)

74.0
to

89.0
90.0
90.1

User Assigned Components - For Development Use
Package Notes

90.2

Package Restrictions

90.3

Package Corrections

91.0

User Assigned Components - For User Use

to
99.0

RSTS/E V10.0 Maintenance Notebook

3.4.2

System Directives Manual
On page 3-146 of the RSTS / E System Directives Manual, the fifth paragraph,
beginning "The octal value," should have the string FIRQB+FQMODE in front of
it in the left-hand column.

3.4.3

Programming Manual
The page references in tables 8-1 through 8-4 of the RSTS / E Programming
Manual for V10.0 are incorrect. To correct this problem, please remove pages 8-3
through 8-12 of the RSTS / E Programming Manual and replace them with the
following ten pages.

Documentation Changes

3-7

3-8

Documentation Changes

In Tables 8-1 through 8-4, the Relevant Privileges column lists the privileges
associated with each SYS call. A user who attempts to can a SYS function
without sufficient privilege receives the error ?I1legal SYS() usage (ERR=18)
or the error ?Protection violation (ERR=10). To avoid repetition, this chapter
describes error 18 for calls only if it has a meaning different from nonprivileged
attempts to use the call.

Table 8-1:

SYS System Function Calls (by Function Code)

Function
Code(F)

Function Name

Relevant
Privileges

Cancel CtrllO effect on terminal

None

Enter tape mode on terminal

None

8-11
8-12

2
3

Enable echoing on terminal

None

8-12

Disable echoing on terminal

None

Page

4
5

Enable ODT submode on terminal

None

8-13
8-14

Exit with no prompt message

None

8-15

SYS call to the file processor

See individual
FIP call

8-15

Get core common string

None

8-15

Put core common string

None

8-16

Exit and clear program

None

8-16

Reserved for special implementations

Cancel all type ahead

None

8-17

Return information on last opened file

None

8-18

Reserved for special implementations

Execute CCL command

Execute access
to file

8-19

Table 8-2:

SYS System Function Calls (by Function Name)

Function Name

Function
Code(F)

Relevant
Privileges

Page

Cancel all type ahead

None

8-17

Cancel CtrllO effect on terminal

None

8-11

Disable echoing on terminal

None

8-13

Enable echoing on terminal

None

Enable ODT submode on terminal

None

8-12
8-14

Enter tape mode on terminal

None

8-12

Execute CCL command

1
14

Execute access
to file

8-19

Exit and clear program

None

8-16

Exit with no prompt message

None

8-15

Get core common string

None

8-15

Put core common string

None

8-16

(continued on next page)

SYS System Function Calls

8-3

Table 8-2 (Cont.):

SYS System Function Calls (by Function Name)

Function Name

Function
Code(F)

Reserved for special implementations

Return information on last opened file
SYS call to the file processor

Relevant
Privileges

Page

None

8-18

See individual
FIP call

8-15

Table 8-3:

FIP SYS Calls (by Subfunction Code)

Function
Code(FO)

Function Name

Relevant Privileges

Page

-29

Get monitor tables - part III

None

8-35

-28

Spooling (Obsolete, use PBS request)

Read access
Write access

8-37

-27

Snap shot dump

SYSIO

8-41

-26

File utility functions

Read access
Write access
DATES
TUNE
SYSIO

8-41

-25

Read/write file attributes

Read access
Write access

8-47

-25

Read pack attributes

DEVICE

8-49

-25

Read/write account attributes

GACNT
WACNT

8-50

-25

Delete account attributes

GACNT
WACNT

8-54

-24

Add/delete CCL command

INSTAL

8-55

-23

Terminating file name string scan

None

8-27

-22

Set special run priority

TUNE

8-57

-21

Drop/regain (temporary) privileges

None

8-57

-20

Locklunlockjob in memory

TUNE

8-59

-19

Set number of logins

SWCTL

8-60

-18

Add run-time system

INSTAL

8-61

-18

Remove run-time system

INSTAL

8-63

-18

Unload run-time system

INSTAL

8-64

-18

Add resident library

INSTAL

8-65

-18

Remove resident library

INSTAL

8-68

-18

Unload resident library

INSTAL

8-69

-18

Create dynamic region

INSTAL

8-69

(continued on next page)

8-4

SYS System Function Calls

Table 8-3 (Cont.):

FIP SYS Calls (by Subfunction Code)

Function
Code(FO)

Function Name

Relevant Privileges

Page

-18

CreatelDelete virtual disk

INSTAL
HWCFG

8-71

-17

Name run-time system

Write access

8-73

-16

Shut down system

SHUTUP

8-73

-15

Accounting dump

GACNT
WACNT

8-74

-14

Change system date/time

DATES

8-75

-13

Change priority/run burst/job size

TUNE

8-76

-12

Get monitor tables - part II

None

8-77

-11

Change file backup statistics

DATES

8-79

-10

File name string scan

None

8-27

-9

Hang up a dataset

HWCTL

8-81

-8

Get open channel statistics

None

8-81

-7

Enable CtrllC trap

None

8-83

-6

Poke memory

SYSMOD

8-85

-5

Broadcast to terminal

SEND

8-86

-4

Force input to terminal

SYSIO

8-87

-3

Get monitor tables - part I

None

8-88

-2

Disable logins

SWCTL

8-89

-1

Enable logins

SWCTL

8-90

Create user account (new format)

GACNT
WACNT

8-90

Create user account (old format)

GACNT
WACNT

8-93

Delete user account

GACNT
WACNT

8-96

MOUNT
HWCFG

8-97

Reserved

Disk pack status

None

8-101

Verify password

DEVICE
GACNT
WACNT

8-101

Logout

EXQTA
WACNT

8-104

Attach

GACNT
WACNT

8-106

Reattach

DEVICE

8-107

Swap Console

None

8-109

Detach

JOBCTL

8-110

(continued on next page)

SYS System Function Calls

6-5

Table 8-3 (Cont.):
Function
Code(FO)

FIP SYS Calls (by Subfunction Code)

Function Name

Relevant Privileges

Page

Change quota (old fonnat)/expiration date/password GACNT
(old fonnat)
WACNT

8-111

Change quota (new fonnat)/expiration
date/password (old fonnat)

GACNT
WACNT

8-114

Set password (new fonnat)

GACNT
WACNT

8-115

Kill job

JOBCTL

8-116

Disable tenninal

HWCTL

8-117

Return error messages

None

8-118

Allocate/reallocate device

DEVICE
HWCTL

8-119

Assign user logical

None

8-121

List user logical names

None

8-122

Deallocate a device or deassign user logical

None

8-123

Deallocate all devices

None

8-124

Zero a device

DEVICE
Create/rename access to
account

8-125

Read/read and reset accounting data

GACNT
WACNT

8-127

Directory lookup on index

DEVICE
Read or execute access

8-133

Special magnetic tape directory lookup

DEVICE

8-135

Set tenninal characteristics - part I

HWCFG

8-140

Set tenninal characteristics - part II

HWCFG

8-148

Disk directory lookup on file name

DEVICE
Read or execute access

8-137

Disk wildcard directory lookup

DEVICE
Read or execute access

8-138

I,~-

Obsolete (use function code 22)

Enable/disable disk caching

TUNE

8-154

Convert date and time

None

8-156

Add new logical names

INSTAL

8-158

Remove logical names

INSTAL

8-160

Change disk logical name

INSTAL

8-161

List logical names

None

8-162

Message send/receive

JOBCTL
SEND
SWCFG
SWCTL
SYSIO

8-162

Send local data message with privileges

SEND

Ch. 10

(continued on next page)

8-6

SYS System Function Calls

Table 8-3 (Cont.):

FIP SYS Calls (by Subfunction Code)

Function
Code(FO)

Function Name

Relevant Privileges

Page

Send PrintlBatch Services request

None

Ch. 10

Create and delete a local LAT port

SWCTL

8-165

Assign, deassign, and set local LAT ports

SWCFG

8-167

Return LAT port characteristics

None

8-173

Add system files

Write access
INSTAL

8-177

Remove system files

Write access
INSTAL

8-180

List system files

None

8-181

Create ajob

Execute access
EXQTA
JOBCTL
TUNE
WACNT

8-182

Wildcard PPN lookup

DEVICE

8-188

Return job status

JOBCTL
TUNE

8-189

Reserved

Set/clear current privileges

None

8-191

Read current privileges

None

8-191

StalllUnstall system

HWCTL

8-193

Reserved

Third-party privilege check

None

8-194

Check file access rights

None

8-195

Convert privilege name to mask

None

8-196

Convert privilege mask to name

None

8-197

Open next disk file

DEVICE
Read access
Write access
DATES

8-198

Set device characteristics

HWGFG
HWCTL

8-200

Set line printer characteristics

HWCFG

8-203

Set system defaults

HWCFG
SWCFG

8-205

Load monitor overlay code and return status/remove monitor overlay code

SWCFG

8-206

PEEK function

RDMEM
SYSMOD

8-210

SYS System Function Calls

8-7

Table 8-4:

FIP SYS Calls (by Function Name)

Function Name

Function
Code(FO)

Accounting dump

Relevant Privileges

Page

-15

GACNT
WACNT

8-74

Add/delete CCL command

-24

INSTAL

8-55

Add new logical names

INSTAL

8-158

Add system files

Write access
INSTAL

8-177

Add resident library

-18

INSTAL

8-65

Add run-time system

-18

INSTAL

8-61

Allocate/reallocate device

DEVICE
HWCTL

8-119

Assign a local LAT port

SWCFG

8-167

Assign user logical

None

8-121

Attach

GACNT
WACNT

8-106

Broadcast to terminal

-5

SEND

8-86

Change disk logical name

INSTAL

8-161

Change file backup statistics

-11

DATES

8-79

GACNT
WACNT

8-114

Change priority/run burst/job size

-13

TUNE

8-76

Change system dateltime

-14

DATES

8-75

Check file access rights

Change quota/expiration date/password

None

8-195

Convert date and time

None

8-156

Convert privilege mask to name

None

8-197

Convert privilege name to mask

None

8-196

Create ajob

Execute access
EXQTA
JOBCTL
TUNE
WAC NT

8-182

Create dynamic region

-18

INSTAL

8-69

Create a local LAT port

SWCTL

8-165

Create user account (new format)

GACNT
WACNT

8-90

Create user account (old format)

GACNT
WACNT

8-93

Deallocate all devices

None

8-124

Deallocate a device or deassign user logical

None

8-123

Deassign a local LAT port

SWCFG

8-169

Delete account attributes

-25

GACNT
WAC NT

8-54

Delete a local LAT port

SWCTL

8-166

(continued on next page)

8-8

SYS System Function Calls

Table 8-4 (Cont.):

FIP SYS Calls (by Function Name)

Function Name

Function
Code(FO)

Relevant Privileges

Page

Delete user account

GACNT
WACNT

8-96

Detach

JOBCTL

8-110

Directory lookup on index

DEVICE
Read or execute access

8-133

Disable logins

-2

SWCTL

8-89

Disable terminal

HWCTL

8-117

Disk directory lookup on file name

DEVICE
Read or execute access

8-137

Disk pack status

MOUNT
HWCFG

8-97

Disk wildcard directory lookup

DEVICE
Read or execute access

8-138

Drop/regain (temporary) privileges

-21

None

8-57

Enable CtrllC trap

-7

None

8-83

Enable logins

-1

SWCTL

8-90

Enable/disable disk caching

TUNE

8-154

File name string scan

-10

None

8-27

File utility functions

-26

Read access
Write access
DATES
TUNE
SYSIO

8-41

Force input to terminal

-4

SYSIO

8-87

Get monitor tables - part I

-3

None

8-88

Get monitor tables - part II

-12

None

8-77

Get monitor tables - part III

-29

None

8-35

Get open channel statistics

-8

None

8-81

Hang up a dataset

-9

HWCTL

8-81

Kill job

JOBCTL

8-116

Return local LAT port characteristics

None

8-173

List logical names

None

8-162

List user logical names

None

8-122

List system files

None

8-181

Load monitor overlay code and return status

SWCFG

8-206

Lock/unlock job in memory

-20

TUNE

8-59

None

8-101

Logout

EXQTA
WACNT

8-104

(continued on next page)

SYS System Function Calls

8-9

Table 8-4 (Cont.):

FIP SYS Calls (by Function Name)

Fllnction Name

Function
Code(FO)

Message send/receive

Name run-time system

-17

Write access

8-73

Open next disk file

DEVICE
Read access
Write access
DATES

8-198

RDMEM
SYSMOD

8-210

PEEK function

Relevant Privileges

Page

JOBCTL
SEND
SWCFG
SWCTL
SYSIO

8-162

Poke memory

-6

SYSMOD

8-85

Read current privileges

None

8-191

Read pack attributes

-25

DEVICE

8-49

Read/read and reset accounting data

GACNT
WACNT

8-127

Read/write account attributes

-25

GACNT
WACNT

8-50

Read/write file attributes

-25

Read access
Write access

8-47

Reattach

DEVICE

8-107

Remove logical names

INSTAL

8-160

Remove monitor overlay code

SWCFG

8-206

Remove resident library

-18

INSTAL

8-68

Remove run-time system

-18

INSTAL

8-63

Remove system files

Write access
INSTAL

8-180

Return error m.essages

None

8-118

Return job status

JOBCTL
TUNE

8-189

Send local data message with privileges

SEND

Ch. 10

Send PrintlBatch Services request

None

Ch. 10

Set/clear current privileges

None

8-191

Set device characteristics

HWCFG
HWCTL

8-200

Set local LAT port characteristics

SWCFG

8-167

Set line printer characteristics

HWCFG

8-203

Set system defaults

HWCFG
SWCFG

8-205

Set number of logins

-19

SWCTL

8-60

GACNT
WACNT

8-115

Set password

(continued on next page)

8-10

SYS System Function Calls

l~-

Table 8-4 (Cont.):

FIP SYS Calls (by Function Name)

Function Name

Function
Code(FO)

Relevant Privileges

Page

Set special run priority

-22

TUNE

8-57

Set terminal characteristics - part I

HWCFG

8-140

Set terminal characteristics - part II

HWCFG

8-148

Shut down system

-16

SHUTUP

8-73

Snap shot dump

-27

SYSIO

8-41

Special magnetic tape directory lookup

DEVICE

8-135

Spooling (obsolete: use PBS request)

-28

Read access
Write access

8-37

StalllUnstall system

HWCTL

8-193

Swap Console

None

8-109

Terminating file name string scan

-23

None

8-27

Third-party privilege check

None

8-194

Unload resident library

-18

INSTAL

8-69

Unload run-time system

-18

INSTAL

8-64

Verify password

DEVICE
GACNT
WACNT

8-101

Wildcard PPN lookup

DEVICE

8-188

Zero a device

DEVICE
Create/rename access to
account

8-125

8.1.2

Cancel Ctri/O Effect on Terminal
Data Passed
Bytes

Meaning

CHR$(O%), the cancel CtrllO code.

CHR$(N%), where N% is the number (between 0 and 12) of the channel on
which the system executes the call. If you do not specify this byte, the call uses
channelO.

CHR$(K%), where K% is the number (between 0 and 127) of the keyboard
assigned but not open by the job. This follows the multiterminal service rule.
The keyboard is the slave terminal under control of a master terminal open on
the channel you specify in byte 2.
If you do not specify this byte, the keyboard affected is the one open on the
channel you specify in byte 2.

Data Returned
The target string is equivalent to the passed string.

Privileges Required
None.

Cancel Ctrl/O, F=O

8-11

Discussion
This call cancels the effect of a CtrllO typed at the specified terminal. The
call selects the terminal open on the channel number you pass in byte 2. (The
terminal must be open on that channel.) If you use a slave terminal, byte 2 must
be a nonzero channel number on which the master terminal is open; byte 3 must
contain the keyboard number of the slave terminal. See the RSTS / E System
User's Guide for a description of CtrllO.

8.1.3

Enter Tape Mode on Terminal
Data Passed
Bytes

Meaning

CHR$(l%), the enter tape mode code.

CHR$(N%), where N% is the number (between 0 and 12) of the channel on
which the system executes the call. If you do not specify this byte, the call uses
channelO.

Data Returned
The target string is equivalent to the passed string.

Privileges Required
None

Discussion
This call is specifically for use with ASR33 terminals that have a low-speed paper
tape reader. The call disables echoing on the terminal and places the terminal
in tape mode so that a program can be read into the system from the low-speed
reader.
The action of this call is the same as that of the TAPE command (see the BASICPLUS Language Manual). The call selects the terminal open on the channel
number you pass in byte 2. (The terminal must be open on that channel.) If you
use a slave terminal, byte 2 must be a nonzero channel number on which the
master terminal is open; byte 3 must contain the keyboard number of the slave
terminal.
Note that CtrllC cancels tape mode.

8.1.4

Enable Echoing on Terminal
Data Passed

8-12

Bytes

Meaning

CHR$(2%), the enable echoing code.

Enable Echoing, F=2

Chapter 4

Layered Products

This chapter describes the differences between V10.O and V9.7, and the
restrictions and corrections to RSTS/E layered products for V10.O. See the
RSTS / E System Installation and Update Guide or the Layered Product's
Installation Guide for instructions on how to update the software.
Table 4-1 lists all ofthe layered products supported on RSTS/E V10.O and the
method for installing each one.
NOTE

Future versions of the layered products that currently use
@[O,l]INSTALL may be changed to use Auto-Install. See the
Layered Product's Installation Guide for more details.
Table 4-1:

Layered Products Installation

Layered Product

Installation method

COBOL-81IRSTS/E

Auto-Install

DATATRIEVE-ll

Auto-Install

DECdxlRSTS

RUN$BUILD

DECmail-ll for RSTS/E

@[O,l]INSTALL

DECnetJE

@[O,l]INSTALL

mBOL for RSTS/E

@[O,l]INSTALL

FMS-llIRSTS

@[O,l]INSTALL

FORTRAN IVIRSTS/E

@[O,l]INSTALL

MENU-l1/RSTS

RUN $BUILD

PDP-ll BASIC-PLUS-2

@[O,l]INSTALL

PDP-ll C for RSTSIE

Auto-Install

PDP-ll FORTRAN-77IRSTS/E

Auto-Install

PDP-ll Symbolic Debugger

@[O,l]INSTALL

PLXY-llIRSTS

RUN $BUILD
@[O,l]INSTALL

WPS-PLUSIRSTS

Layered Products 4-1

4.1

DATATRIEVE-11
This section lists the corrections and restrictions for DATATRIEVE-ll V3.3.

4.1.1

Corrections
The following DATATRIEVE-ll problems have been corrected via updates
included with the RSTSIE V10.O software:
•

DATATRIEVE-ll could not accept an ACL password on the command
READY domain (*). This problem was caused by corruption of the password
data in the DDMF after being received from the remote host.

•

When using the lexical functions in an endless loop, the error message Pool
Space Exhausted was received. This was because space was not released back
to pool once the function was completed.

•

When an attempt was made to CtrllC out of a PRINT statement or SHOW
operation, DTR-ll displayed the error INTERNAL DATATRIEVE ERROR,
RECOVERING. This problem only occured when DTR-ll was built with
Supervisor Mode RMS.

•

Changes were made to the task size of the DDMF, because of a problem that
happened if you have installed DTR-ll without using Supervisor Mode RMS.
When running REMDTR or the DDMF task you received an error message
and your network link was rejected.

•

DTR-ll now recognizes the QUERY.INI file if it is renamed in a different
location other than SY:, or if it is assigned to a logical name. Also if the
dictionary name and location are renamed, moved to different locations other
than SY:, or assigned to logical names, and the default .INI file is not found,
DTR-ll searches for a system .INI file.

•

The error message [BBad Record address in RAE now reads correctly.

•

In some cases, the Report Writer printed AT BOTTOM OF PAGE twice.

•

When you issued multiple consecutive PRINT ON statements,
DATATRIEVE-ll displayed the following error:
Timeout loop counter has been exhausted
INTERNAL DATATRIEVE ERROR
SEVERE ERROR -- CANNOT CONTINUE

This problem has been fixed.
NOTE
To apply updates to DATATRIEVE-ll V3.3 you must install

DATATRIEVE-ll using the standard Auto-Install procedure.
Before you begin the DATATRIEVE-ll update, be sure to delete
DTRUPD.DON from PATCH$:. This file may be left over from a previous DATATRIEVE update; the presence of this file indicates that the
update is done.

4-2

Layered Products

4.1.2

Restrictions
DATATRIEVE-ll has the following restrictions:
•

Printing a date field together with another field does not give the correct
printout. To get a correct printout just using the PRINT command (that
is, not using the Report Writer), rename the other field, as in the following
example:
DECLARE FOO PIC X(ll) .
FOR CURRENT BEGIN
FOO=DATE-FIELD
PRINT NAME-FIELD, FOO I "TESTING"
END

•

When you use the Report Writer, explicitly specify the columns to print at, for
example:
REPORT CURRENT
PRINT NAME_FIELD,COL 30, DATE_FIELD, COL 41, "TESTING"
END REPORT

It is not important where you place DATE_FIELD, but you must place the
text string 11 columns after DATE_FIELD if you want the text string to
appear directly after it.

4.2 DECdx
DECdx has the following restrictions:
•

When you install DECdx, the installation control file attempts to print the
DECdx Release Notes in SY:[1,2]DDXRLS.RST. It uses the OPSER package
to print these notes. If OPSER is not running when you install DECdx, an
error occurs and the installation aborts. As a workaround, you can start the
OPSER package before installating DECdx, or simply ignore the error; by
that point, DECdx has been properly installed.

•

When you run DECdx, you must set up your terminal to emulate a VT52. On
a DECmate, you can do this by selecting the SO menu and entering TM 52.

•

When you run DECdx, you must set the terminal type attribute to VT52
and turn off the terminal attribute ESCAPE_SEQUENCE. Use the DCL
commands SET TERMINALNT52 and SET TERMINALINOESCAPE.

4.3 DECmail-11
DECmail-11 help file updates used to have RMS attributes. This caused some
help topics in DECmail-11 to display extraneous text. RSTSIE VIO.O contains
updated help files without RMS attributes.

4.4 DECnet/E
This section describes the changes and corrections that have been made to
DECnetIE V4.1.

Layered ProdUcts

4-3

4.4.1

Changes
This section describes changes that have been made to DECnetlE for VIO.O.

4.4.1.1

Utility Library Changes

All of the DECnet utilities that previously used the CSPLIB resident library are
replaced on the RSTSIE VIO.O kit to use the new CSPIOO library.
4.4.1.2

Database Format Changes

The format of the files [O,l]NETPRM.SYS and [O,l]NSPO.SYS has changed for
VIO.O. New installations and updates of DECnetlE will automatically update
these files to the new format. This update will allow future versions of DECnetlE
to support additional network devices.
The RSTSIE VlO.O monitor will support both the old and new file formats. This
will allow any currently installed version of DECnet/E to continue working with
RSTSIE VIO.O.
Optimizations have also been made to the RSTSIE VIO.O monitor which may
result in slightly faster node lookup with both the old and new formats.
New versions of DECNET$:NCP.TSK and DECNET$:EVTLOG.TSK, included on
the RSTSIE VIO.O kit as part of the DECnetlE update package, will only run with
the new database format.
4.4.1.3

NFT/FAL

The following changes and enhancements have been made to the NFT and FAL
utilities in DECnet/E:
•

Default Transfer Mode
Previously, NFT by default transferred files in record mode. This sometimes
resulted in slower file transfers or errors when transferring binary files
without RMS attributes. Users could include the IBL switch to direct NFT to
use block mode instead.
NFT now automatically selects the most suitable mode - record or block for transferring files to other nodes. This provides increased performance
for most file transfers, and avoids the RMS errors Record too big and Illegal
Record Format.
NFT will use block mode to transfer a file if:

4-4

•

The operation involves only remote RSTSIE nodes running the current
version of RSTSIE.

•

An APPEND operation is not requested, either via the APPEND command
or a COPY command that implies concatenation, such as OUT = A,B.

•

A Record mode switch is not included in the command. This includes the
Variable (NA) and Native (INA) switches as well as the new Record (IRE)
switch (see below).

•

The RSTSIE nodes are not running the current release, but the operation
does not involve wildcard input.

Layered Products

NOTE

The DCL COPY command invokes NFT to perfonn network file
copy operations. Therefore, this feature applies to the DCL COpy
command as well. See also Section 1.2.11.30.
NFT's logging message now includes the transfer mode used. For example:
FILE01.BAR copied to RSTS::FILE01.BAR in block mode

•

New !RECORD Switch
To allow explicit selection of the file transfer mode (block or record), NFT
now recognizes the !RECORD switch, as well as the existing !BLOCK switch.
Previously, NFT always transferred files in record mode, unless !BLOCK
was specified. Now that NFT by default selects the best transfer mode, the
!RECORD switch is provided to allow users to override the default action.

•

DELETE Command Mode Changes
NFT now uses block mode whenever possible when deleting remote files, thus
avoiding failures on attempts to delete RMS Sequential Undefined files.

•

TYPE Command Mode Changes
NFT now uses record mode whenever possible when typing remote files, thus
avoiding cases where implied carriage control is ignored, or where indexed file
prologue blocks are displayed.

•

Help Files
NFT HELP has been updated to include all of the transfer mode changes
described in this section.

4.4.2 Corrections
This section describes problems that have been corrected in DECnetIE and its
utilities in V10.0.
4.4.2.1

File Access Listener (FAL) Utility

•

FAL has been modified to correctly report date/time of file creation. This
allows VMS programs to remotely access RSTSIE files using the /SINCE and
!BEFORE date qualifiers.

•

FAL has been modified to correctly handle wildcarding in block mode.
Previously, when a certain ordering of files existed in the user's directory,
NFT would report the error ER$RSZ and the remote FAL would hang.

•

If a program running on another system uses DECnetlE to create an indexed file on a RSTSIE system, and if the last 110 operation to the file is an
$UPDATE or keyed $PUT using a duplicate key, then the file is deleted when
it is closed. This only happens if the program creates the remote file; if the
program accesses a file that was already there, the problem does not occur.
The patch to correct this problem, described in article 31.5.2 of the November
1990 RSTS / E Software Dispatch, is no longer required and should not be
applied.

Layered Products

4-5

4.4.2.2

4.4.2.3

Network File Transfer (NFT) Program

•

NFT has been corrected to handle double precision file sizes when perlonning
directory operations.

•

NFT will now log local deletes when the command includes the /LOG switch.

•

NFT will now correctly identify a Sequential Undefined file (with embedded carriage control) on directory operations, rather than reporting it as a
nonattributed file.

Installation and Update

The DECnetiE Installation and Update procedure did not correctly handle the
selection of the resident library fonns of NFT and FAL. The procedure installed
the non-RMS library fonn of NFT and FAL, even though the user elected to
install the RMS libraries. The procedure will now install the RMS library fonn of
NFT and FAL whenever the user installs the RMS libraries.

4.5 DIBOL
RSTSIE VIO.O contains the following changes for RSTSIE DIBOL V6.1:
•

Online release notes are provided which document the changes made to
RSTSIE DIBOL. Reinstall RSTSIE DIBOL V6.I on RSTSIE VIO.O to update
the DIBOL software.

•

Prior to RSTSIE VIO.O, if you specified the I[NO]OPTIMIZE and I[NO]DEBUG
qualifiers together on the DCL DIBOL command, the qualifier you specified
first was ignored. This has been fixed in RSTSIE VIO.O.

•

DIBOL programs that cluster the RMS and DIBOL resident libraries and also
use I & D splitting and overlaying may fail with Reserved Instruction Trap,
Odd Address Trap or Memory Management errors.
The problem is caused by an incorrect mapping of the RMS library. It occurs
when a tenninal or data file is opened. To avoid this problem, avoid clustering
RMS with DIBOL. If you are currently using DCL to build the program, the
following command creates a clustered library program:
LINK/DIBOL/CODE=DATA/STRUCTURE

Modify the command as follows:
LINK/DIBOL/CODE=DATA/RMS=SUPER/STRUCTURE

This maps the RMS library through supervisor mode.
If you are using a TKB command file, and your .CMD file contains a cluster
option, for example:
CLSTR = DBCOTS,FDVRES,RMSRES:RO

Modify the .CMD file, substituting the following:
CLSTR = DBCOTS,FDVRES:RO
RESSUP = RMS$:RMSRES/SV:O

In addition, you need to modify your .CMD file or .ODL file to include the
supervisor mode version of the RMS Autoload module. If you currently
reference RMSLIB/LB:ROAUTL, substitute RMSLIB/LB:ROAUTS. If your
.ODL file references the RSTSIE ODL file LB:RMSRLX, then substitute
LB:RMSSLX.
4-6

Layered Products

Using this workaround does not increase the size of the DIBOL program; in
fact it reduces it. Also, performance is slightly better with supervisor mode
RMS library than when clustering the RMS library.

4.6 FORTRAN-77
The update file for FORTRAN-77, PATCH$:F77.DOC, had incorrect RMS
attributes on the RSTS/E V9.7 kit. This file is corrected in RSTS/E V10.O.

4.7 WPS-PLUS/RSTS V1.1
The following WPS-PLUSIRSTS problems have been corrected via updates
included with the RSTS/E V10.O software:
Under certain conditions, Sort Processing exceeded its stack limits. When this
happened, RSTS reported a Memory Management error, displayed a register
dump and issued the fatal error message ??Program lost-sorry. For example:
??Memory management trap
000000 144540 000016 000014 000022 000032 177776 144644 174001
??Program lost-sorry

When this error occurred Sort processing stopped and WPS-PLUS returned to the
Main Menu.
This problem is corrected via updates to the following files:
- WPS$:WPLSRT.TSK
- WPS$:WPLSRT.LIB
- WPS$:WPSMES.MSG
- WPS$:WPSVER.DAT
Upon completion of this update, the WPS-PLUSIRSTS version will be Vl.l.l.
The changes in this update disable the WPS-PLUSIRSTS automatic release
notes feature. This was done to save disk space, since this feature automatically
placed a copy of the WPS-PLUSIRSTS release notes in each account initialized
for WPS-PLUS.
The only effect of this change is that the release notes no longer appear as a WPS
docwnent in a newly created account. The change does not affect current users of
WPS-PLUSIRSTS Vl.l unless they decide to create new WPS-PLUS accounts.
If you apply this update as part of a first-time installation of WPS-PLUSIRSTS
V1.1, the release notes document mentioned in Chapter 2, "Verifying the
Installation," ofthe WPS-PLUS/RSTS Installation manual does not exist.
To get a copy of the release notes, invoke WPS. Create a new docwnent called

Release_Notes. When the ruler appears, type Gold G. At the Title: prompt type
_WPS$:RELNOT.WPL and press RETURN twice. This puts a copy of the release
notes into your account.
If you are a first-time installer of WPS-PLUSIRSTS, you may want all your users

to get a copy of the WPS-PLUSIRSTS release notes. To do this, edit the file
WPS$:WPSVER.DAT and remove the exclamation point, !, at the beginning of the
second and third lines in the file. Do this before initializing any WPS-PLUSIRSTS
accounts and before any user invokes WPS-PLUS.

Layered Products

4-7

Chapter 5

Corrections

This chapter describes problems that have been corrected in RSTS/E V10.0. Some
of the problems described were corrected in earlier RSTSIE versions by patches
published in the RSTS / E Software Dispatch. Such articles, where noted, are no
longer required and should not be applied to V10.0. For corrections to layered
products running on RSTSIE, see Chapter 4.

5.1

Installation
The following corrections have been made to the installation procedures:
•

In V9.7, if you answered NO to the installation prompt Are you ready to
and then assigned a package logical name to a nonstandard
location (device and/or account), the installation ignored the assignment and
used the package's standard location instead.
proceed?

This problem was described in article 2.2.1 of the November 1989 RSTS / E
Software Dispatch.
•

The RSTSIE V9.7 online installation procedure incorrectly displayed an error
message at the conclusion of building a new monitor SIL.
This problem was described in article 2.2.2 of the January 1990 RSTS / E
Software Dispatch.

•

Previously, if you mounted the wrong volume in response to a volume mount
prompt during installation, the installion would abort with an error even
though you corrected the error by mounting the proper volume. This problem
occurred because the BACKUPIRESTORE package did not exit with status
SUCCESS even though the volume mount operation completed successfully.
The BACKUPIRESTORE package now exits with the correct exit status.

•

Previously, when doing an online monitor installation to a target disk, the
installation procedure did not copy all of the necessary monitor modules to
the target disk. This problem has been corrected.

•

Prior to V10.0, if you selected the prebuilt monitor, the installation procedure
would create a SWAP1.SYS swap file large enough to hold 20 jobs even though
the monitor could only support a maximum of 10 jobs. The installation
procedure now creates a 10-job SWAP1.SYS file.

•

In V9.7, if you installed Monitor ODT, the file SYO:[0,1]ODT.SYS is set
NODELETABLE. This caused a ?Protection violation error when you
updated your RSTS/E system. In RSTS/E V10.0, the file _SYO:[0,1]ODT.SYS
is set to DELETEABLE before it is replaced during an upgrade.

Corrections

5-1

•

Before RSTSIE V10.0, if you typed a question mark (?) in response to the
Do you want _SYo: [0,1] SWAP1. SYS created (at n blocks)? prompt, the
installation procedure redisplayed the What size would you like SWAPMAX to
be? prompt after displaying its help text. This has been fixed to display the
proper prompt.

•

Previously, if you were doing a target installation using an ANSI Scope
terminal, some messages would not be readable, and some disk initialization
prompts would overwrite each other. These problems have been fixed in
RSTSIE VlO.O.

•

Online help is now available at the following prompt:
You may now transfer the layered product update components from the
Installation kit.
Do you wish to do the transfer?

The display prior to the Product updates to transfer prompt has been
changed to include ALL, NOprod [, ..• ] as options. The help message for this
prompt has been updated to show that prod [, ... ] is a valid response for
transferring multiple layered products.
•

When you updated your system to RSTSIE V9.7, you could not have the
RSTSIE Installation kit on a different device than the one you used to boot
your RSTSIE Installation kit. For V10.0, you can use a different device.

5.2 INIT.SYS
•

In certain cases, systems with multiple DHll multiplexers crashed during
system startup. The patch to correct this problem, described in article 1.1.14
of the RSTS / E Software Dispatch, is no longer required and should not be
applied.

•

Systems with DEQNAlDELQA Ethernet devices assigned vector addresses
of 400 8 or greater sometimes crashed during system startup. The patch to
correct this problem, described in article 1.1.15 of the RSTS / E Software
Dispatch, is no longer required and should not be applied.

•

Certain unexpected hardware errors on RQDX controllers (for RD53/54 type
disks) sometimes caused INIT to hang. This happened during the DSKINT
option or while rebuilding the disk after a system crash. This problem has
been corrected in V10.0. INIT will now print an error message and retry the
operation.

5.3 Monitor

5-2

Corrections

•

In some circumstances, the job number cell of the Job Data Block was
corrupted, causing the system to crash. The patch to correct this problem,
described in article 3.1.9 of the September 1989 RSTS / E Software Dispatch,
is no longer required and should not be applied.

•

If the input buffer quota was reached willIe processing C1 control characters,
the system could crash. This problem was corrected by a patch in the August
1989 RSTS / E Software Dispatch, sequence number 3.3.23. This patch is no
longer needed and should not be applied.

•

If a tenninal was set to RESUME=ANY and the tenninal was stalled,

extraneous characters were displayed in place of the next character to
be displayed. This problem was corrected by a patch in the August 1989
RSTS / E Software Dispatch, sequence number 3.3.24. This patch is no longer
needed and should not be applied.
•

Under certain conditions, a user's LOGIN.COM procedure could loop infinitely
trying to exit. The patch to correct this problem, described in article 3.3.25
of the January 1990 RSTS / E Software Dispatch, is no longer required and
should not be applied.

•

Previously, the STATUS command in the KMCUT program (included with
the HP 2780/3780 and 3271 PE products available from DECUS) could crash
the system or cause other random system errors. The patch to correct this
problem, described in article 3.5.17 of the October 1989 RSTS / E Software
Dispatch, is no longer required and should not be applied.

•

Under certain conditions, use of asynchronous 110 to extend a disk file could
cause the file to grow excessively, exhausting all the remaining free space on
the disk. The patch to correct this problem, described in article 3.5.18 of the
December 1989 RSTS / E Software Dispatch, is no longer required and should
not be applied.

•

Some applications that used RMS in Supervisor mode did not act properly
when CtrllC was typed. This problem was corrected by a patch in the
November 1989 RSTS/E Software Dispatch, sequence number 3.1.10. This
patch is no longer needed and should not be applied.

•

Issuing the Swap Console command when the console was a dynamic
keyboard, as for LAT lines, could cause the system to crash. The patch to
correct this problem, described in article 3.5.20 of the August 1990 RSTS / E
Software Dispatch, is no longer required and should not be applied.

•

Tenninal lines set to DIALUP and AUTOBAUD might fail to autobaud
correctly. The patch to correct this problem, described in article 3.3.28 of the
August 1990 RSTS / E Software Dispatch, is no longer required and should
not be applied.

•

If a detached job tried to reattach to a keyboard line that had pending input,

the system might crash. The patch to correct this problem, described in
article 3.3.29 of the August 1990 RSTS / E Software Dispatch, is no longer
required and should not be applied.
•

Spawning a logged-in job on a static keyboard that has pending input could
cause the system to crash. The patch to correct this problem, described in
article 3.3.27 of the April 1990 RSTS / E Software Dispatch, is no longer
required and should not be applied.

•

Setting a port on a tenninal server to NOAUTOPROMPT to prevent the
automatic starting of LOGIN could corrupt memory allocated to XBUF. The
patch to correct this problem, described in article 3.3.26 of the March 1990
RSTS / E Software Dispatch, is no longer required and should not be applied.

•

Detaching, reattaching, or swapping console from a dynamic keyboard could
crash the system if that keyboard was opened on another channel at the time
of the detach. The patch to correct this problem, described in article 3.5.19 of
the May 1990 RSTS / E Software Dispatch, is no longer required and should
not be applied.

Corrections

5-3

•

Prior to V10.0, if a program used the UU.ATT directive to reattach to a
detached terminal without deassigning the console or closing its I/O channels,
the terminal open modes, delimiter mask, and input buffer were cleared.
Since the terminal was still owned by the detached job, these terminal
attributes should not have been cleared. The patch to correct this problem,
described in Article 3.5.20 of the November 1990 RSTS / E Software Dispatch,
is no longer required and should not be applied.

•

Prior to V10.0, if a program issued a conditional SLEEP of 0 seconds, the
monitor erroneously caused the program to sleep for 32768 seconds. The
RSTS / E Programming Manual discusses this in the section SLEEP and
Conditional SLEEP Statements, in the chapter "System Programming Hints."
It describes the format of a conditional sleep statement as SLEEP expression
+ 32767% + 1%, where expression is defined as the number of seconds to stop
execution. Thus, a sleep value of 0% + 32767% + 1% should cause the program
to sleep for 0 seconds, not 32768 seconds. This problem has been corrected in
VlO.O.

5.3.1

DEQNA/DELQA Device Driver
•

In previous versions of RSTSIE, the Ethernet SYSID message, sent periodically by the operating system to identify itself to other network nodes, had an
invalid value in one of its fields. This has been corrected in V10.0.

•

An inconsistency existed in the error handling for the .SPEC call which loads
Ethernet multicast addresses. This problem allowed invalid addresses passed
to the monitor to exist in the internal data structures maintained for the
driver. This has been corrected in V10.0.

5.4 Del
This section describes problems that have been corrected in the DCL run-time
system or its associated commands and services in V10.0.

5.4.1

CREATE/ACCOUNT Command
The CREATE/ACCOUNT command has the following corrections:
•

In previous versions of RSTSIE, if you attempted to create an account on
a disk that was not mounted you received the misleading error message
?Invalid DEV: [P, PN] specification. The CREATE/ACCOUNT command
now displays the error message ?Disk pack is not mounted.

•

If you issue a command of the form CREATE/ACCOUNT disk:{ppnl and
the disk you specify is physically dismounted (that is, spun down), but
not logically dismounted, you now receive the error message ?Device not
available. Previously, the error message displayed was ?Disk RDS level 0.0
not allowed.

•

5-4

Corrections

The CREATE/ACCOUNT command now clears the privileges and name on
accounts created using a template account on an RDS level 1.1 disk. The
privileges default to None and the account name defaults to (no name). If
the /PRIVILEGES or /NAME qualifier is used in addition to the /TEMPLATE
qualifier, then the characteristics you specifiy are applied instead of the
defaults.

Previously, the privileges were set to match those of the account you were
logged into, the name defaulted to <no name>, and the INAME qualifier was
ignored.

5.4.2

GOSUB Command
Previously, if a GOSUB command in a DCL command procedure included a
continuation line, the subroutine referenced by the GOSUB command was
executed multiple times. For example, the following command would cause the
subroutine GET_ARG to execute twice:
$ IF Pl .EQS. "" THEN GOSUB GET ARG

This has been corrected in RSTSIE V10.0 to execute the subroutine only once.

5.4.3

INITIALIZE Command
Prior to RSTSIE V10.0, the INITIALIZE command sometimes failed with the
error ?Protection violation even though you had the necessary privileges
(WRTNFS and RDNFS) to initialize a disk. This problem has been corrected in
V10.0. Users with WRTNFS and RDNFS privileges are authorized to initialize a
disk, as stated in the documentation.

5.4.4

MOUNT Command
The MOUNT qualifier INOSHAREABLE only accepted the keyword INOSHARE.
The qualifier now accepts the full keyword INOSHAREABLE.

5.4.5

REMOVE/OVERLAY
The REMOVE/OVERLAY command now displayes the error message ?Overlay
file not installed if there is no OVR.SYS file in use. Previously, the message
displayed was Overlay file removed.

5.4.6

SET NODE/LAT/ACCESS=DIALUP
The SET NODE/LAT/ACCESS=DIALUP command now displays the error
message ? SWCFG pr i vilege required if you do not have this privilege. Previously,
SET NODE displayed the message ?Protection violation at line 1.

5.4.7

SET PASSWORD
Previously, if you issued the SET PASSWORD command with a wildcard PPN (for
example, [10,*]) to change the password of multiple accounts, and you specified a
password longer than six characters, SET PASSWORD sometimes truncated the
password to six characters for NOLOOKUP accounts, even though NOLOOKUP
accounts can support passwords up to 14 characters.

Corrections

5-5

This problem occurred if SET PASSWORD encountered a LOOKUP account,
requiring it to truncate the password to six characters. If SET PASSWORD then
encountered any NOLOOKUP accounts, it assigned them the truncated password
instead of the original (non-truncated) password.
In V10.0, the SET PASSWORD command correctly assigns the specified password
to all accounts. If an account is LOOKUP, then SET PASSWORD truncates
the password as necessary to a maximum of six characters. For NOLOOKUP
account, SET PASSWORD assigns the specified password, up to a maximum of 14
characters.

5.4.8

SET TERMINAL Command
Several corrections have been made to the SET TERMINAL command for V10.0:

5.4.9

•

Previously, you could specify /HOST_SYNC for a terminal with the attribute
RESUME=ANY, or /RESUME=ANY for a terminal with HOST_SYNC. These
attributes conflict. In V10.0, a terminal that has the HOST_SYNC attribute
enabled cannot be set to RESUME=ANY, and vice versa.

•

Also, you could previously specify IAUTOBAUD for a terminal with
ANSWERBACK, or vice versa. These attributes conflict. In V10.0, a
terminal that has AUTOBAUD enabled cannot be set to ANSWERBACK, and
vice versa.

•

Previously, the SET TERMINAL command did not require !PERMANENT if
the /BUFFER_QUOTA qualifier was specified. This allowed users without
HWCTL privilege to change their terminal's buffer quota. In V10.0, the
SET TERMINAL command requires !PERMANENT, and therefore HWCTL
privilege, to specify /BUFFER_QUOTA.

•

The terminal input buffer quota range allowed in V9.6 and V9.7 was incorrect.
Previously, a terminal's buffer quota range was 180 to 7650 characters. The
buffer quota range in V10.0 is 168 to 7140 characters.

•

The SET TERMINALIDELIMITER command now disallows eight-bit characters as private delimiters and displays the error message ?Invalid private
delimiter. Previously, eight-bit characters were not trapped, the sign bit
was stripped from the argument, and the wrong character was set up as the
private delimiter.

•

The SET TERMINALIINQUIRE command now clears any private delimiters
you have set. Previously, if you had a private delimiter set, this command
failed, displaying the error message ?Terminal type could not be determined.

SHOW DEVICE Command
The SHOW DEVICE command now displays Disabled by INIT instead of
Restricted when this is a device's actual status. The command SHOW DEVICE
SY: now displays information about the system disk. In previous versions no
information was displayed.

5.4.10

SHOW NODE/LAT
The SHOW NODEILAT command now displays the setting of the IACCESS
qualifier.

5-6 Corrections

5.4.11

SHOW QUOTA Command
Previously, the SHOW QUOTA command displayed an error if your account had
a default protection set. This has been corrected in VIO.O. A1so, if you specify a
nonexistent account or an account that you do not have the privileges to access,
earlier versions of RSTS/E displayed quota information for your own account.
In V10.0, the SHOW QUOTA command displays an error message under these
circumstances.

5.4.12

Time Format
DCL now correctly interprets 12:00 PM as noon, not midnight, in all DCL
commands.

5.5 BACKUP/RESTORE Package
Several problems have been corrected in the BACKUPIRESTORE Package for
V10.0:
•

BACKUP/DIRECTORY incorrectly displayed protection codes with 512 added
to the actual protection code for files marked NODELETEABLE.

•

BACKUP/DIRECTORY did not display an error if the /DIRECTORY qualifier
was not specified immediately following the BACKUP command. Because
BACKUP/DIRECTORY is a single command, the /DIRECTORY qualifier
must always appear immediately after the BACKUP verb, similar to the
RESTORE/DIRECTORY command.

•

During RESTORE of a backup set created with a group size other than 10, if
an error occurred reading the first block of the backup set, BACKUP did not
restore all the backup set data correctly and sometimes exited prematurely
with a ??Memory management trap error. V10.0 BACKUP correctly recovers
data after an error reading the first block of the backup set.

•

During BACKUP of a large number of O-length files, BACKUP sometimes
hung in a sleep state indefinitely and failed to finish the BACKUP. V10.0
BACKUP performs BACKUP on any number of O-length or NOBACKUP files.

•

BACKUP/DIRECTORY did not correctly report pack cluster sizes larger
than 16 when listing pack attributes. If the disk was initialized with a pack
clustersize larger than 16, BACKUP always displayed the cluster size as 16.
BACKUP/DIRECTORY now reports the correct clustersize.

•

If the last group of data blocks was smaller than the group size, BACKUP

did not write an XOR block to the backup set after completing all the data
for the backup set. That meant that, if there was an error reading any block
in the last group, RESTORE was unable to recover the data for that block
and also failed to restore the data in any subsequent block in the last group.
V10.0 BACKUP writes a final XOR block at the end of every backup set and
recovers data from any bad block in the last group.
•

If the user did not have the appropriate WACNT or GACNT privilege,

RESTORE returned the error ?Illegal SYS () usage when it tried to create
an account other than the user's account. It also returned a ?Protection
violation error for each account attribute it tried to update, even though
it was unable to create the account in the first place. BACKUP now gives
the error ?Protection violation if it can't create the account, and will
not try to update the account attributes afterward. Note that RESTORE,
Corrections

5-7

BACKUPIIMAGE, and BACKUP/COPY give the following errors if the user
does not have the required WACNT or GACNT privilege even if the account
already exists:
?Error creating directory [PPN]
?Protection violation

•

If BACKUP recovered the data in the last data block of a backup set using
its XOR block, BACKUP could hang in an infinite sleep state. This has been
corrected for VIO.O.

•

Under some circumstances, BACKUP entered an infinite sleep state waiting
for streaming tapes to start on the last of their data blocks. VIO.O BACKUP
makes sure streaming tapes start properly on their last blocks.

•

Previously, if you specified /CREATED=BEFORE=date, then BACKUP selected
all files created on or before the date you specified, rather than only those
files created before that date. The same behavior occurred if you specified
/MODIFIED=BEFORE=date.

This problem has been corrected for VIO.O. BACKUP will now select only
those files created (lCREATED) or modified (!MODIFIED) before the date you
specify.

5.6 Print/Batch Services (~BS)
The PrintlBatch Services (PBS) package now sends a carriage return instead of
a null character to a print device on a keyboard server when the print device is
first opened. Some LP devices connected to keyboard lines (via a serial to parallel
converter) will echo null characters as spaces which skews the output to the
printer.
The PBS package will still send null characters to keyboard print servers for two
reasons:
•

The FILL characteristic for the keyboard line is non-zero.

•

There are null characters in the file being printed and the print server is set
to /CONTROLS.

5.7 Commonly Used System Programs (CUSPs)
This section describes problems that have been corrected in various CUSPs in
VIO.O.

5.7.1

5-8

ANALYS

Corrections

•

ANALYS incorrectly displayed virtual disk memory above l024K as being
locked out.

•

The number of buffers covered by the SESQ and XMTQ annotations were
incorrect. ANALYS has been changed to report their correct size.

5.7.2

DSKSEK
Previously, DSKSEK sometimes failed on certain disk types.

5.7.3

MEMORY
MEMORY incorrectly displayed virtual disk memory above 1024K as being locked
out.

5.7.4

OPSER
An OPSER Batch job sometimes failed when run under an account with detached
jobs. This has been corrected so that batch jobs will always respond with Return
to the LOGIN prompt Job number to attach to?, meaning the batch job will not
attach to any detached jobs running in the same account.

5.7.5

5.7.6

PIP
•

PIP incorrectly handled page sizes when copying large files (greater than
32,767 blocks) to the line printer.

•

A ?TRAP TO 4 error sometimes occurred when copying a file to a dismounted
disk.

•

PIP issued an incorrect error message if wildcards were included in the input
specification of a disk copy command and the disk was not mounted.

RECOVR.COM
The [O,I]RECOVR.COM recovery procedure creates a special recovery version of
the file [O,I]SYSINI.COM. This version of [O,I]SYSINI.COM displays the message
You may now proceed to recover your system by using the RESTORE command.

In V9.7, the recovery version of [O,I]SYSINI.COM tried to delete itself upon
completion. This was done so that the standard version of SYSINI.COM could be
restored later. However, the DELETE command failed, displaying Message text
not available.

In RSTS/E VI0.0, the file [O,I]RECOVR.COM no longer includes a DELETE
command in the special recovery version of [O,I]SYSINI.COM, eliminating the
DELETE error that occurred in V9.7. However, you must now ensure that the
special recovery version of [O,I]SYSINI.COM is replaced by the standard version
of [O,I]SYSINI.COM when you restore your system. See Chapter 16 of the
RSTS / E System Manager's Guide for instructions on recovering your system
disk.

5.7.7

SYSTAT
SYSTAT incorrectly displayed virtual disk memory above 1024K as being locked
out.

Corrections

5-9

5.7.8

OOT
Previously, ODT stayed in a run state when accessing RA82 and RA90 disks in
non-file-structured mode. Although this problem still exists for RA90 disks, it has
been corrected for RA82 disks.

5.8 RMS-11
This section describes problems that have been corrected in RMS-ll and its
utilities in V10.O.

5.8.1

RMS-11 Access Methods
The modules RORSET and R1CONP in the RMSLIB.OLB and the RMS libraries
have been changed to correct remote $CONNECT operations so that the User
Buffer address is copied to the Record Buffer address as a preparation for locate
mode. This behavior is now consistent with the local RMS-ll $CONNECT
operation.
The module ROOPFL in the RMSLIB.OLB and the RMS libraries has been
changed to remove an earlier correction that interpreted a RSTSIE native stream
file as having implied carriage control. While this achieved some compatibility
with VMS, it introduced a RSTSIE incompatibility, specifically, RT-ll map files
after a network copy had incorrect carriage control.

5.8.2

RMS-11 Remote Access Methods
The module RONFRT in RMSDAP. OLB and the DAPRES library has been
corrected to handle records larger than 510 bytes when the file's Maximwn
Record Size (MRS) equals zero. At time of file creation, an MRS of zero indicates
that RMS should never consider a record too large for insertion in the file.

5-10

Corrections

Chapter 6

Restrictions

This chapter describes known problems and restrictions in RSTSIE VIO.O. Some
of the restrictions decribed in this chapter are under investigation and may
be resolved in a future release of RSTSIE. For restrictions on layered products
running on RSTSIE, see Chapter 4.

6.1

Small Memory Systems
RSTSIE VIO.O contains several changes that may impact systems that have a
limited amount of memory, such as the PDP-1l/34 (limited to a maximum of 124K
words of memory). The following VIO.O changes increase the amount of memory
required during timesharing:
•

Additional code added to the VIO.O executive can increase the size of your
monitor up to 3K words.

•

The new Job Header data structure increases each job's maximum memory
(SWAP MAX) by 2K words.

•

The RESTORE command, when used to restore backup sets created with a
large block size (up to 28K bytes in VIO.O), requires a larger dynamic region
for its buffers.

RSTSIE requires that there be enough memory to hold the installed monitor,
XBUF (minimum 3K words), and at least one job at the defined SWAP MAX
(34K words for non-I & D space systems). Additional memory is also required (as
needed) for other run-time systems, resident libraries and dynamic regions.
Depending on their hardware and software configurations, some small-memory
systems may not be able to use all of the features available in RSTSIE. Such
systems may encounter problems installing or using VIO.O because of the
increased memory usage. These problems can exhibit themselves in a variety of
ways:
•

INIT will not start timesharing if there is not sufficient user memory to
support one job at the defined SWAP MAX size.

•

The VIO.O installation may fail when restoring files from the Installation kit
if there is insufficient memory for the RESTORE command's dynamic region
(a 9K word region is required).

•

Installation of resident libraries or run-time systems may fail if there is not
enough available memory to hold them.

•

BACKUP and RESTORE operations may fail if there is insufficient memory
for the required dynamic region.

Restrictions

6-1

The following guidelines are suggested to help deal with insufficient memory
problems on small memory systems:

1. Do not configure optional hardware or software in the monitor that is
not required. Use the INIT HARDWARE DISABLE option to di~nble nny
hardware included but not used on your system.
2.

Create a second minimum configuration monitor that can be used whenever
additional user memory is required. Use the SET SYSTEMIMONITOR_NAME
command and reboot the system to switch between monitors.

3. If using DECnetiE, do not include network routing support unless required.
Routing code adds several K words of code to the monitor.
4.

DECnetiE code is automatically included in the installed monitor at startup
if the nodes database file is present (SYO:[O,l]NETPRM.SYS). Rename the
nodes database file and reboot the system to eliminate the DECnetiE code
from the installed monitor at startup. DECnetiE adds up to 13K words to the
installed monitor.

5. Reduce the number of small buffers configured in your monitor. Only do this
if your system statistics indicate a consistently large number of available
small buffers (more than 200).
6. Reduce XBUF to its minimum required value (3K words). Note that reducing
the size of XBUF may reduce overall performance because of less directory
and data caching.
7.

Do not allocate memory for the virtual disk (DVO:).

8. Avoid installing run-time systems and resident libraries that are not required.

6.2 Installation
The following restrictions apply to the RSTS/E installation procedure:
•

If you install V10.0 onto a multi-disk public structure, then the monitor .SIL,
[O,l]LOGIN.COM, [O,l]START.COM, and the BASIC-PLUS run-time system
file(s) may be installed on a public disk other than SYO:. If the monitor .SIL
and [O,l]START.COM files are not installed on SYO:, then you will not be able
to successfully start your new system.

The workaround is to manually copy these files to the system disk, once
installation is complete. The following example shows such a copy operation:
$ COpy _SY:[O,l]RSTS.SIL SYO: [O,l]RSTS.SIL
$ COpy _SY:[O,l]START.COM _SYO: [0, 1] START. COM

•

During installation, the SORTIMERGE installation program lists the defaults
that it uses, then asks you whether these defaults are acceptable. If you are
using a video terminal, part of this list may scroll off of the screen before the
question is asked, thus making it impossible to tell whether or not all of the
defaults are correct.
To prevent this, either install SORTIMERGE using a hardcopy terminal or

use the Hold Screen key to freeze and release the screen as you read the list
of defaults.
•

6-2

Restrictions

If you press Ctrl/C and abort a target installation, the system logical
PATCH$: may still be assigned to the target disk and not restored to
its original assignment. This can cause problems during or after target
installation, since the logical may not refer to its expected location.

To avoid this, reassign the logical manually after a target disk installation.
•

During installation, if you specify that the installation kit is on a device other
than the default device, then you cannot answer NO to any of the Are you
ready to proceed? prompts. If you do answer YES to any of the prompt.s and
then proceed, the installation will try to use the default device instead of the
device you specified.

6.3 INIT.SYS
An unnecessary error message prints when an 800 BPI magnetic tape on a TE16
subsystem that uses a TM02 formatter is booted from the Option: prompt of
INIT.SYS. For example:
MMO Error

MTCS1
144270

MTWC
000000

MTFC
001007

MTCS2
000100

MTDS
154640

MTER
102100

MTTC
102300

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

6.4 Monitor
This section describes the known problems and restrictions for the RSTSIE
monitor.

6.4.1

Escape Sequences in Prompts
When performing command line editing, the monitor relies heavily on the
position of the cursor after a prompt has been issued. If the DCL prompt or
program prompt contains an escape sequence, the monitor is unable to compute
the position of the cursor.
If your prompt contains an escape sequence, your command may be displayed

incorrectly when deleting characters in the middle of the command line. Your
command may also shift to the left, clearing part of the prompt, when you type
CtrllR to redisplay the command. After you type CtrllR, although the line may
not be aligned with the prompt, line editing will behave correctly.
One suggested workaround is to include a RETURN character (without a LINE
FEED) to reset the position after the escape sequences. For example, if your DCL
prompt ensures your terminal is in VT220 mode, you might have your prompt
defined as follows:
$ SET PROMPT F$CHR(27)+" [62;O'"'pCOMMAND> "

In this situation, command line editing would not work properly as described
above. However, this can be solved by adding a RETURN in the prompt right
before the COMMAND> string, as follows:
$ SET PROMPT F$CHR(27)+"[62;0""p"+F$CHR(13)+"COMMAND> "

Restrictions

6-3

6.4.2

UU.ATR Directive
When you issue the Write Account Attributes form of the UU.ATR directive to
update the disk and detached job quota information, the new quot.as maint.ained
on disk for that PPN are updated immediately. However, if the account has users
logged into it or open files, then the in-memory copy of this data is not updated.
This presents two problems:

1. The new quotas do not take effect until all users have logged out of the
account and all files open in the account have been closed.
2. Issuing the SHOW ACCOUNTIFULL command shows the old quota values
for the logged-out and logged-in disk quotas rather than the new values. This
is because the monitor returns the in-memory copy of this data whenever it
is available, which is the case when users are logged into the account or the
account has open files.
If you use the DCL command SET ACCOUNT or the UU.CHU directive to change

the quotas, then you will not encounter this problem. The SET ACCOUNT
command uses the UU.CHU directive which changes both the disk and in-memory
copy of the quotas.
BACKUPIRESTORE, on the other hand, uses the UU.ATR directive when
updating the accounting data. If an account being updated has any users logged
into it or any open files, the current in-memory quotas are still enforced and
displayed by the SHOW ACCOUNT command.

6.5 Del
This section describes known problems and restrictions in the DCL run-time
system and associated commands and utilities.

6.5.1

DCl Command Parsing
In certain rare cases, DCL may interprete a null DCL command as an @ command without a parameter, causing it to prompt for a command file. This can
occur if SET VERIFY is in effect and DCL executes the @ command to start a
command procedure, and the first line in the command file is of the form $_ or
$_!comment. In such cases, DCL mistakenly displays the prompt Command File:,
as if the @ command was issued without a file parameter.
If this condition occurs in a batch or command procedure, DCL will satisfy the
Command File: prompt with CtrllZ and the command procedure will continue
normally. If the condition occurs interactively (very rare), you must type CtrIlZ to
exit the extraneous prompt.

To avoid this condition, do not prefix comment lines with the underscore character. In general, you should only use the underscore prefix to prevent automatic
symbol substituion on DCL command keywords that represent valid DCL symbols. Special DCL characters like @ and ! cannot be redefined as valid DCL
symbols.

6-4

Restrictions

6.5.2

DCl Error Handling
If you specify an ON severity THEN _GOTO label command in a .COM file, and

the label is not defined in your .COM file, then if an error occurs, DCL redisplays
- as part of its error message - the command line that caused the error, rather
than the ON severity THEN _GOTO label command that contained the undefined
label.

6.5.3

F$ENVIRONMENT
The following restrictions apply to the DCL function F$ENVIRONMENT in
VIO.O:
•

If you execute the function F$ENVIRONMENT("LOG_FILE") with a log file

open, DCL inserts an extra <CR><LF> into the log file immediately before
the F$ENVIRONMENT function call. Terminal output is not affected. For
example, the following command:
$ _WRITE 0 "Log file = ", F$ENVIRONMENT ("LOG_FILE")

will appear in the log file as the following entry:
Log file =
_DU1:[lO,lO]TEST.LOG

As a workaround, you can assign the function's value to a DCL symbol before
displaying the desired result. For example:
$ LOG FILE = F$ENVIRONMENT("LOG FILE")
$ _WRITE 0 "Log file = ",LOG_FILE

While this does not eliminate the extra <CR><LF> in the log file, it does
avoid splitting any WRITE 0 text.
•

If you execute the function F$ENVIRONMENT("LOG_FILE") with a log file

open, the log file closes and then reopens (in APPEND mode). This causes
the log file to expand by one block each time the F$ENVIRONMENT("LOG_
FILE") function is invoked.
The suggested workaround to this problem is to avoid excessive calls to the
F$ENVIRONMENT("LOG_FILE") function. As illustrated above, you can
assign the function value to a DCL symbol if you need to refer to it more than
once.

6.5.4

language Compiler Commands
If you issue the DCL language compiler commands COBOL, DIBOL,

FORTRANIF77 or MACRO, DCL returns a ?Protection violation error if
the source file is on a disk that is mounted read-only and you do not specify the
/OBJECT= qualifier. The workaround is to copy the source file to the system disk,
or remount the source disk write-enabled.

Restrictions

6-5

6.5.5

LOGIN Command
The V10.O feature that allows you log in using a system logical name instead
of a PPN is not available with the DCL LOGIN command. That. is, you cannot.
issue the command LOGIN SMITH if you are already logged in. This is because the
DCL LOGIN command only accepts a PPN parameter, even though the LOGIN
program itself can accept either a PPN or a logical name.
If the system command HELLO is defined on your system, then you can issue

the command HELLO SMITH to log into the account pointed to by the logical name
SMITH.

6.5.6

MOUNT/NOSHAREABLE Restriction
If you try to mount a disk and assign ownership of it to another job by using the

MOUNT/NOSHAREABLE=job-number command, you get an ?Account or device
in use error message, followed by a register dump, and then possibly another
error message. RSTSIE mounts the disk and assigns the requested job, but the
disk is restricted. (This will be shown as a status of Lck in a SHOW DISKS
display).
The workaround is to ignore these errors, and then to use the SET
DEVICE/NORESTRICT command to unrestrict the disk if needed.

6.5.7

IOUTPUT Qualifier
For certain DCL commands, if you specify /OUTPUT=disk.file and disk.file
already exists, then the command's output will be appended to the existing file
rather than replacing it.
This applies to all DCL commands processed by the SYSTAT program, given in
the following list:
• SHOW BUFFERS
• SHOW DISKS
• SHOW JOBS
• SHOW LIBRARIES
• SHOW MEMORY
• SHOW RUNTIME_SYSTEMS
• SHOW USERS

6.5.8

RETURN Command
If the DCL command RETURN is executed with SET VERIFY in effect, DCL

echoes the GOSUB command line that called the subroutine. The problem does
not occur if SET NOVERIFY is in effect. The extraneous GOSUB command is
echoed - at your terminal or in a batch log file-but is not executed.

6.5.9

SET TERMINAL Restrictions
If you use the command SET TERMINAL/AUTOBAUD to change the autobaud

characteristic of a terminal which is connected to RSTSIE via LAT or DECnetlE,
the IAUTOBAUD qualifier is ignored and the terminal's attribute is not changed.
No error message is displayed, even though the IAUTOBAUD qualifier is invalid
under these conditions.
6-6

Restrictions

If you use the command SET TERMINAL/SPEED=(input-rate,output-rate) to
change the baud rate of a terminal whose speed is not settable, the qualifier
is ignored and the terminal's attribute is not changed. No error message is
displayed, even though the terminal may not support different input and output
baud rates.

6.5.10

System Command Error Messages
If DCL displays the error ?Can' t find file or account in response to a system
command (CCL), DCL's arrow may not be pointing to the part of the command
that caused the error.

6.6 BACKUP/RESTORE Package
This section describes known restrictions in the RSTS/E BACKUPIRESTORE
package.

6.6.1

AFTER File Selection
BACKUP interprets the keyword AFTER to mean "on or after" the date/time
specified, similar to the DIRECTORY command's /SINCE qualifier. This may
cause more files to be selected than expected. For example, if you issue the
following command, you might expect BACKUP to only select files with a creation
date later (newer) than 20-Jun-90:
$ BACKUP/CREATED=AFTER=20-JUN-90 *.* BACKUP.BCK

Instead, BACKUP will select all files created on or after 20-JUN-90.
If you include both a date and time value with AFTER, then BACKUP will select
all files created on or after the specified date/time.

6.6.2

BACKUP/COPY Command
BACKUP/COPY, like RESTORE, always places output files in NEW FILES LAST
(NFL) order so that they will be in the same order with respect to each other
as they were on the input disk. If the output disk is initialized as NEW FILES
FIRST (NFF), the files are still created in NFL order.

6.6.3

BACKUP/IMAGE Command
This section describes known restrictions for the new BACKUPIIMAGE command.

6.6.3.1

HOOK Failure

BACKUPIlMAGE will fail to HOOK the output disk if:
•

The output disk is dismounted when BACKUPIlMAGE is run

•

The output disk is mounted INOSHAREABLE

•

IINITIALIZE is specified in the BACKUP command line

Under any of these conditions, HOOK displays the error ?Can't open
[0, 1] SYO: INIT. SYS, then BACKUPIlMAGE displays the error %Unable to hook
output volume.

Restrictions

6-7

This happens because, when the output disk is not mounted, BACKUPIIMAGE
mounts it /NOSHAREABLE to protect it from access during the backup operation.
BACKUPllMAGE runs HOOK at a pseudo keyboard from a spawned job, and
HOOK fails because it cannot reach the /NOSHAREABLE disk. If you mount
the disk /SHAREABLE first and specify llNITIALIZE, then BACKUP/IMAGE
dismounts the disk to do the initialization and then remounts it /NOSHAREABLE
for the backup, which causes the same result for HOOK.
To allow BACKUPllMAGE to HOOK the output disk, mount it /NOSHAREABLE

before running BACKUPllMAGE, and do not specify IINITIALIZE in the
BACKUPllMAGE command line.
If the HOOK fails, you can still HOOK the output disk after BACKUPllMAGE

has completed by running SYSGEN$:HOOK. At HOOK's prompt, type:
dey: [O,l]INIT.SYS"dev: [O,l]INIT.SYS

where dev: is the output disk device name.
NOTE

BACKUPllMAGE will try to HOOK the output disk only if:

6.6.3.2

•

It copies [O,l]INIT.sYS to the output disk, and

•

The input disk is hooked.

Initialization Errors

BACKUPllMAGEIINITIALIZE initializes the output disk with a clustersize
of zero by default, which tells DSKINT to use the device clustersize as the
pack clustersize. In some cases, this may cause errors during backup or verification. If you want BACKUP to use a clustersize other than zero, use the
IINITIALIZE=CLUSTER_SIZE=nn qualifier.
Possible errors are:
•

A directory attribute verification error for each directory on the disk. These
happen because the directory attribute that contains the total allocation is
different on disks with different cluster sizes.
NOTE

Even on disks with the same cluster size, you may get two directory
attribute verification errors for each of the accounts [1,1] and [1,2]
if DSKINT was used to create those accounts on the source disk.
This happens because DSKINT places the date/time attributes
before the disk quota attribute, while BACKUP places the disk
quota attribute before the date/time attributes. BACKUP compares
attributes by looking them up by index on each disk, and therefore
will get a compare error on each attribute because the ordering is
different.
•

If a directory on a source disk with a larger clustersize contains a large

enough number of files, then the target directory on the disk with a smaller
clustersize may not be able to hold all the files, resulting in a ?No room for
user on device error for each file that does not fit into that directory, and
resulting in the files not being copied to the output disk.

6-8

Restrictions

6.6.4

BEFORE File Selection
If you specify both a date and a time value with the BEFORE keyword argument,

BACKUP interprets BEFORE to mean "on or before" the date/time specified. For
example, if you issue the following command, then BACKUP will select any file it
encounters with the creation date/time 20-JUN-90 11:50 PM:
$ BACKUP/CREATED=BEFORE=20-JUN-90:11:50PM *.* BACKUP.BCK
(It will, of course, also select all files with an earlier creation date/time.)

If you include a date but no time value with the BEFORE keyword, then

BACKUP selects only those files with a creation date earlier than the date
specified.

6.6.5

IMODIFIED Times
RSTSIE maintains for each file a creation date, creation time and modification
(access) date, but no modification time.
BACKUP allows you to specify a time value for the !MODIFIED qualifier, since
BACKUP can select files from VMS savesets that include modification times for
VMS files. Because there is no modification time for RSTSIE files, BACKUP
assumes a modification time of 00:00 - the earliest time of day - for the file's
modification date.
This can produce unexpected results when you include a time value with the
!MODIFIED qualifier. For example, if you include the following qualifier, then
you might expect BACKUP to select only those files with a modification date/time
on or after 16-Jun-90 10:00 AM:
/MODIFIED=AFTER=16-JUN-90:10:00AM

However, since all RSTSIE files are treated as having a modification time of 00:00
(start of day), BACKUP does not select any files modified on 16-Jun-90; only files
modified on 17-Jun-90 or later are selected.
Similarly, if you specified the following qualifier, then BACKUP will select all files
modified on or before 16-JUN-90 00:00 (start of day):
/MODIFIED=BEFORE=16-JUN-90:00:00

Since BACKUP considers all RSTSIE files as having a modification time of 00:00,
BACKUP selects all files modified on 16-Jun-90 instead of only those files created
on or before 16-Jun-90 00:00.
To avoid these problems, do not specify a time value with !MODIFIED when

backing up or restoring RSTSIE files.

6.6.6

RESTORE Command
This section describes known restrictions for the RESTORE command.

Restrictions

6-9

6.6.6.1

Error Recovery Handling

When BACKUP restores a backup set and encounters an error reading a block, it
tries to recover the data. Example errors:
%CRC error detected for block
?Error reading backup set
?Data error on device

If the recovery procedure is successful, BACKUP simply continues with the

restore operation without issuing any message to indicate that the recovery
was successful. However, if the recovery is not successful, BACKUP issues the
following message:
?Unable to recover part of Backup set

It may follow this with other error messages about missing data or attributes for

a specific file.
NOTE

Because BACKUP has no way of knowing the contents of an unrecoverable bad block in the backup set, parts of files or entire files may be
lost with no error messages displaying the name of the lost file(s).
6.6.6.2

Restoring VMS Savesets

The following restrictions apply to restoring files from savesets created on VMS:
•

Some VMS savesets restored on RSTSIE may produce the error message
?Invalid record length in Backup set - record skipped one or more times.
This is because VMS BACKUP uses a data structure within its savesets
that RSTSIE does not recognize. These error messages have no effect on the
validity of the restored data and may be ignored.

•

Some files transferred from RSTSIE to VMS, then backed up to a VMS saveset
and restored with RSTSIE BACKUP, may cause the error ?Some file data
in file [PPN] FILENAME may be missing. This is caused by the fact that a file
can be created at a larger size on VMS than it was originally on RSTSIE,
even though only the original number of disk blocks contain valid file data.
VMS BACKUP then puts the larger size in the save set attribute record that
describes the file, but copies only the smaller number of valid file data blocks
to the saveset.
When the file is restored to RSTSIE it is created at the larger size specified in
the file attribute record, but there is only enough data in the saveset to fill up
the original smaller size. This causes BACKUP to note the discrepancy and
print the above error. The restored file is bigger than the original file, but the
USED:m:n attribute provides the correct original size information to other
RSTSIE operations. The file data is complete and correct, and the error may
be ignored.

6.7 Print/Batch Services (PBS)
Under certain conditions, some PrintlBatch Services (PBS) commands may fail
with the error message ?Packet error -1600.
The conditions that cause this error are rare, generally requiring multiple users
to issue PRINT or SUBMIT commands at the same time that PBS wraps the
sequence number around from 9999 to 1. Should this error occur, simply reissue
the command that triggered the error.
6-10

Restrictions

6.8 Operator/Message Services Package
The ISINCE qualifier of the SHOW REQUESTS command defaults to 12:00AM if
no time is specified with the qualifier. The RSTS / E System Manager)s Guide and
the online help text incorrectly state that the time defaults to 11:59PM.

6.9 Commonly Used System Programs (CUSPs)
This section describes known problems and restrictions in various RSTSIE
CUSPs.

6.9.1

BPCREF
The BPCREF program accepts the IQUE qualifier to queue its output file for
printing under the OPSER print facility. Queueing is accomplished by chaining
to the QUE program.
BPCREF continues to rely on the OPSER package for queueing its cross reference
file for printing if requested. It does not use the newer PrintlBatch Services
(PBS) package. If you need to use the print queueing capability of BPCREF, then
you must continue running the OPSER print package (you can use both PBS and
OPSER concurrently). Alternatively, you can use the DCL PRINT command to
queue the cross reference file for printing after the BPCREF completes.

6.9.2

COPY
The COpy program, located in AUXLIB$, may abort with the error ?Maximum
memory exceeded if you attempt to copy or verify a magtape with too large a block

size. This is not a new restriction, but may now occur due to the introduction of
larger block sizes in BACKUP and the monitor.

6.9.3

ODT
ODT.TSK hangs if you use it to access an RA90 disk non-file-structured. If you
have the problem, type CtrllC to exit ODT. ODT.TSK works correctly in filestructured mode, when used to access the contents of individual files on RA90
disks.

6.9.4

RUNOFF
The RUNOFF program accepts the IQUE qualifier to queue its output file for
printing under the OPSER print facility. Queueing is accomplished by chaining
to the QUE program.
RUNOFF continues to rely on the OPSER package for print queueing if requested. It does not use the newer PrintlBatch Services (PBS) package. If you
need to use the print queueing capability of RUNOFF, then you must continue
running the OPSER print package (you can use both PBS and OPSER concurrently). Alternatively, you can use the DCL PRINT command to queue the
RUNOFF output file for printing after RUNOFF completes.

Restrictions

6-11

6.9.5

PIP
Because of buffersize limitations, PIP cannot copy or read magtape backup sets
created by BACKUP with a /BLOCK_SIZE value of 4096 or larger. If you need to
copy or read a magtape backup set with PIp, create it with a IBLOCK_SIZE value
of 4080 or less.

6.10 RSX
The RSX-ll LBR utility does not support the new extended logicals. Only logical
names of six characters or less are valid in LBR.

6.11

RMS-11

6.11.1

•

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

•

Keyed access on a remote indexed file will incorrectly report a Record Not
Found error when the target record's key size is described as zero on a key
whose datatype is non-string. This is documented as a correct way to pass a
non string key, but currently works correctly only for local operations.

RMS-11 Utilities
The RMS-ll utilities RMSDSP, RMSDEF, RMSBCK, and RMSRST do not support
underscores in logical names.

6-12

Restrictions

Index
A
Access methods, RMS-11, 2-24
AllOCATE command, 2-8
ANAlYS system program, 2-19,5-8
ANSI Scope terminals, 2-2
Answerback, 2-12
APRs, 1-35
ASSIGN/PORT command, 1-26
ASSIGN command, 2-9, 2-23
/ASSIST qualifier, BACKUP/RESTORE package, 1-29
Asynchronous 110, 2-16,5-3
Autobaud, 2-12
/AUTOBAUD qualifier, SET TERMINAL command, EH>
Automatic file compression, PBS, 2-17

B
Backspace key, 1-7
BACKUP/COPY command, 1-27, 6-7
BACKUP/IMAGE command, 1-26, 6-7
BACKUP/RESTORE command, 2-14
BACKUP/RESTORE package, 1-29, 5-1, 5-7, 6-7
BACKUPIVERIFY=ONlY command, 1-28
BACKUP command, 1-20
BACKUP file attribute, 2-9, 2-19
flag, 1-20
/BACKUP qualifier, SET FilE command, 1-32
BACKUP qualifiers, S-8, 6-7, 6-9
/CREATED, 6-9
/MODIFIED, 6-9
Backup set size
Disks, 2-14
Tapes, 2-14
BASIC-PLUS, 2-2 to 2-3, 2-22 to 2-24
DEBUG, 2-2
Debugging feature, 2-22
Extended logicals support, 2-22
installation, 1-35, 6-2
Batch Exit Status, PBS, 2-17
Batch Processor, PBS, 2-17
BPCREF system program, 6-11
BYE command, 2-23

c
CC command, 1-34
COBOL compiler command, 6-5
Command line editing, 1-3, 1-6,1-33,2-2,6-3
keys, 1-7
SET HOST, 1-9
SET TERMINAL, 1-10

Command parsing, DCl, 6-4
Command recall, 1-3, 1-6, 2-2
buffers, 1-5
keys, 1-7
Conditional read, 1-12
COPY command, !TRANSFER_MODE qualifier, 1-35
COpy utility, 6-11
CREATE/ACCOUNT command, 2-9
CREATE/ACCOUNT Command, S-4
CREATE/PORT command, 1-26
CSPLlB.LlB resident library, 1-35
Ctrl/A, 1-7
Ctrl/B, 1-8
Ctrl/C, 1-11
Ctrl/D, 1-4, 1-7
Ctrl/E, 1-7
Ctrl/F, 1-7
Ctrl/H, 1-4, 1-7
Ctrl/J, 1-4, 1-7
Ctrl/N, 1-8
Ctrl/R, 1-8, 1-11
Ctrl!T, 1-11
Ctrl/U, 1-4, 1-7
CUSP resident library, 1-35
CUSPs, 2-18 to 2-22, 6-11
Corrections, 5-8

o
Database format
DECnetlE, 4-4
DATATRIEVE-11, 4-2
DCJ11 CMOS processor, 1-1
DCl, corrections, S-4
DCl command parsing, 6-4
DCl commands, 2-8 to 2-18
system commands, 6-7
DCl error handling, 6-5
DEASSIGN/PORT command, 1-30
DEASSIGN command, 2-9, 2-23
DEBUG for BASIC-PLUS, 2-2
Debugging, BASIC-PLUS, 2-22
/DEBUG qualifier, 4-6
DECdx, 4-3
DECmail-11, 4-3
DECnetlE, 4-3
Database format, 4-4
File Access Listener (FAl) utility, 4-4, 4-5
Insta"ation and update, 4-6
libraries, 4-4
Network File Transfer (NFT) program, 4-6

Index-1

DECneVE (Cont.)
Network File Transfer(NFT) utility, 4-4
DEFINE/COMMAND/SYSTEM command 2-9
DELETE/PORT command, 1-30
'
Delete Line function, 1-7
DELQA device driver, 5-4
DEQNA device driver, 5-4
Device driver
DELQA, 5-4
DEQNA, 5-4
DH11 multiplexer, 5-2
Dial-out modems, 1-17
DIBOL, 4-6
DIBOL compiler command, 6-5
DIRECTORY command, 2-9
DIRECT system program, 2-19
Disks
Backup set size, 2-14
multi-disk installations, 6-2
public structure installations, 6-2
Documentation Directory, 3-1
Dollar sign character, 1-18
Down Arrow key, 1-8
DSKCVT system program, 2-19
DSKINT system program, 2-19
DSKSEK system program, 2-19,5-9
Dynamic keyboards, 1-13

E
Echo
immeditate, 1-11
Echo On read, 1-10
Editing, command line, 1-3,2-2,6-3
End of Line function, 1-7
Error handling, DCL, 6-5
Error package, 2-19
Escape Sequence terminal attribute, 1-4,1-10,2-12
Ethernet, 5-2, 5-4
Extended logicals, 1-17,2-22

F
F$ENVIRONMENT function, 1-23, 6-5
FAL utility, 4-4,4-5
File Access Listener utility, see FAL utility
File attribute flags
BACKUP, 1-20
IGNORE, 1-20
FILE_UTILITY overlay, 1-30
Format, database, 4-4
FORMS_WAIT status, 1-33
FORTRAN/F77compiler command, 6-5
FORTRAN-77, 4-7
FPJ11 CMOS processor, 1-1

G
GOSUB command, 5-5

H
Hardware support, 1-1 to 1-2
HELLO command, 2-23
HELP files, 2-10
HOOK, 6-7
Host-initiated LAT connections, 1-12, 1-13

Index-2

I & D space, 4-6, 6-1
1& D Space, 1-21
IGNORE file attribute, 2-9,2-19
flag, 1-20
/IGNORE qualifier, SET FILE command, 1-32
Immediate echo, 1-11
INIT.SYS file, 5-2, 6-3
Initialization, 6-3
INITIALIZE command, 2-10,5-5
/INITIALIZE qualifier
BACKUP, 1-28
RESTORE, 1-28
INQUIRE command, 2-10
INSERT mode terminal attribute, 1-5
toggle, 1-7
/INSERT qualifier, SET TERMINAL command, 1-33
Installation, 2-1 to 2-4, 6-2
accounts and options, 2-4
corrections, 5-1
Installing OMS, 1-19
Internals and Data Structures Manual, 3-1

J
Job Data Block, 5-2
Job header, 1-5,1-18,1-21,6-1
Job quotas, 6-4

K
Keyboards, dynamic, 1-13

L
LA324 printer, 1-2
Language compiler commands, 6-5
LAT, 1-26,2-12,2-19
host-initiated connections, 1-12,1-13
ports, 1-13, 1-26, 1-30, 1-32, 1-34
Ports, 2-8
LAT queueing, 1-15
Left Arrow key, 1-7
Libraries
CXSP100, 4-4
DECneVE, 4-4
Line editing, 1-3, 1-33, 2-2, 6-3
LINE FEED function, 1-7
/LlNE_EDITING qualifier, SET TERMINAL command,
1-33
LINE_EDITING terminal attribute, 1-5
LINK command, 2-10
List User Logicals SYS call, 1-18
LOAD/OVERLAY command, 2-10
Logging In, 1-22, 6-6
Logical names, 6-12
Logicals
extended, 1-17,2-22
RMS-11, 6-12
system, 2-13
user, 1-17, 2-13
LOGIN.COM file, 1-23, 2-20, 5-3, 6-2
LOGIN command, 1-22
LOGIN Command, 6-6
LOGIN system program, 2-20
LOGOUT system program, 2-20

M
(

MACRO compiler command, 6-5
Macro library, RMS-11, 2-24
Maintenance Notebook, 3-1, 3-2
MEMORY system program, 5-9
Modems, 1-17
Monitor, 2-4 to 2-8
corrections, 5-2
installation, 6-2
restrictions, 6-3
MOUNT/NOSHAREABLE, 6-6
MOUNT/REBUILD command, 2-11
MOUNT command, 5-5
MOUNT Command, 6-6
MSDS$ directive, 1-35
Multiline commands, editing, 1-8
Multiplexer, DH11, 5-2
Multivolume handling, 2-1

N
Network File Transfer program, DECnetlE, see NFT
Network File Transfer utility, see NFT utility
NFT program, 4-6
NFT utility, 4-4
NOECHO mode terminal attribute, 1-10
/NOTIFY qualifier, PRINT command, 1-30
/NOTIFY qualifier, SUBMIT command, 1-30

o
ODT, 5-10
ODT.TSK system program, 6-11
ODT system program, 2-20
Old format, SEND/RECEIVE functions, 2-2, 2-23
OMS, 1-18,1-22,1-33,1-34,2-3,2-11,2-18,
2-20,6-11
Installing, 1-19
ONLCLN system program, 2-21
OPEN mode, 1-6
Operator/Message Services, 1-18
Operator Message Services
See also OMS
/OPERATOR_SERVICES qualifier, SET TERMINAL
command, 1-33
OPER privilege, 1-22,2-3,2-11,2-19
OPSER package, 1-20, 2-3, 2-20, 2-21, 5-9
/OPTIMIZE qualifier, 4-6
/OUTPUT Qualifier, 6-6
/OUTPUT qualifier, SHOW command, 1-30
OVERSTRIKE mode terminal attribute, 1-5
toggle, 1-7
/OVERSTRIKE qualifier, SET TERMINAL command,
1-33

p
PBS, 1-18,1-30,2-16 to 2-18
Automatic file compression, 2-17
Batch Processor, 2-17
Corrections, 5-8
Restrictions, 6-10
User request packets, 2-17
PDP-11/34, 6-1
PDP-11/93 processor, 1-1
PDP-11/94 processor, 1-1

PDP-11 SORT/MERGE User's Guide, 3-1
PIP.SAV, 2-21
PIP system program, 2-21,5-9,6-12
Ports, LAT, 1-13, 1-26, 1-32,2-8
PrintlBatch Services, 1-18,2-16 to 2-18
See also PBS
PRINT command, 1-30,2-11
Printer, LA324 , 1-2
Privileges
OPER, 1-22
Programming Manual, 3-1,3-7

Q
Q-bus, 1-1, 1-2
/QUERY qualifier, RESTORE command, 1-29
Queueing, LAT, 1-15
Quick Reference Guide, 3-1
Quotas, 6-4

R
RA70 disks, 1-2
RA90 disks, 1-2
.READA directive, 2-16
.READ directive, 1-11
conditional, 1-12
Reattaching terminals, 5-4
Recall, command, 1-3
RECALL command, 1-6, 1-31
Recall Next Command function, 1-8
Recall Previous Command function, 1-8
/RECALL qualifier, SET TERMINAL command, 1-33
RECALL terminal attribute, 1-5
RECOVR.COM procedure, 5-9
Redisplay Line function, 1-8
REMOVE/OVERLAY command, 5-5
REORDR system program, 2-22
/REPLACE=QUERY qualifier, RESTORE command,
1-29
REPLY command, 1-32
REQUEST command, 2-11
Resident libraries, 1-35
RESTORE command, 1-29,6-9,6-10
RESTORE Command, 6-10
Restoring VMS savesets, 6-1 0
RETURN command, 6-6
Return Local LAT Port Status SYS call, 1-16
Right Arrow key, 1-7
RL02 disks, 2-1
RMS-11, 2-24 to 2-25, 4-2, 4-6, 6-12
Access methods, 2-24
Macro library, 2-24
Utilities, 2-25
RMS-11, corrections, 5-10
RMSBCK utility, 2-25,6-12
RMSDEF utility, 2-25,6-12
RMSDSP utility, 2-25,6-12
RMSMAC.MLB file, 2-24
RMSRST utility, 2-25, 6-12
RSX-11, 2-24
Restrictions, 6-12
RSX directives
MSDS$, 1-35
RT-11 , 2-24
RUNOFF system program, 6-11

Index-3

SA550 storage array, 1-2
SA650 storage array, 1-2
SA705 storage array, 1-2
SEND/RECEIVE fUnctions, old format, 2-2, 2-23
SET ACCOUNT command, 2-11,6-4
SET FILE qualifiers
/BACKUP, 1-32
/IGNORE, 1-32
SET HOST
command line editing, 1-9
SET JOB/PRIVILEGE command, 2-11
SET NODE/LAT/ACCESS=DIALUP command, 5--5
SET NODE/LAT command, 2-12
SET OPERATOR_SERVICES command, 1-32
SET PASSWORD command, 5--5
SET PORT command, 1-32
SET SYSTEM command, 2-12
SET TERMINAL command, 1-33,2-12,5--6,6--6
command line editing, 1-10
SET TERMINAL qualifiers, 1-33
/DELIMITER, 5-6
/INQUIRE, 5--6
/INSERT, 1-33
/LlNE_EDITING, 1-33
/OPERATOR_SERVICES, 1-33
/OVERSTRIKE, 1-33
/RECALL, 1-33
SHOW ACCOUNT/FULL display, 1-33
SHOW ACCOUNT command, 2-13, 6-4
SHOW command, /OUTPUT qualifier, 1-30
SHOW DEVICE command, 2-13,5--6
SHOW ENTRY command, 1-33
SHOW ENTRY display, 1-33, 2-17
SHOW JOB/PRIVILAGES command, 2-13
SHOW LOGICALS command, 2-13
SHOW NODEILAT command, 5--6
SHOW OPERATOR_SERVICES command, 1-34
SHOW PORT command, 1-34
SHOW QUOTA command, 5--7
SHOW REQUEST command, 1-34
SHUTUP system program, 2-22
SLEEP statement, 5-4
Small-memory systems, 6-1
Software features, new, 1-3 to 1-36
SORT/MERGE
installation, 6-2
SORT/MERGE utility, 1-36, 6-2
/SPEED qualifier, SET TERMINAL command, 6--6
START.COM file, 2-3
START/OPERATOR_SERVICES command, 1-34
/STATUS qualifier, SHOW ENTRY command, 1-33
STOP/OPERATOR_SERVICES command, 1-34
SUBMIT command, 1-30, 2-14
Supervisor mode, 1-35
SWAPMAX range, 2-1
SYS call
List User Logicals, 1-18
Return Local LAT Port Status, 1-16
SYSTAT system program, 5--9
System commands, 6-7
System Directives Manual, 3--1, 3--7
System Installation and Update Guide, 3-1
System Manager's Guide, 3-1
System name, 2-1
System User's Guide, 3-1

Tapes
Backup set size, 2-14
TaskBuilder Reference Manual. 3-1
Terminal attribute, 2-14
Terminal attributes, 1-5
Escape Sequence, 1-10
INSERT mode, 1-5
LINE_EDITING, 1-5
NOECHO mode, 1-10
OVERSTRIKE mode, 1-5
RECALL, 1-5
Terminal input buffers, 1-11
Terminal OPEN modes, 1-B
Terminals
reattaching, 5-4
Time format, correction, 5-7
Time of year clock, 1-1
TOY clock, 1-1
/TRANSFER_MODE qualifier, COpy command, 1-35
TUNE privilege, 2-16
Typeahead, 1-10

index-4

u
Underscore character, 1-17,6-12
UNIBUS, 1-1,1-2
UNLOAD/OVERLAY command, 2-14
Up Arrow key, 1--8
User logicals, 1-17,2-13
User request packets, PBS, 2-17
Utilities
RMS-11, 2--25
UU.ATR directive, 6-4
UU.ATI directive, 5-4
UU.CHU directive, 6-4
UU.FCB directive, 1-11
UU.FIL directive, 1-30

v
VT100 terminals, 2-2
VT200 terminals, 2-2
VT300 terminals, 2-2

w
Wildcard characters, 2-13
WPS-PLUS/RSTS, 4--7
.wRITA directive, 2-16

How to Order Additional Documentation

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

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

Telephone and Direct Mail Orders
Your Location

Call

Contact

Continental USA,
Alaska, or Hawaii

800-DIGITAL

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

Puerto Rico

809-754-7575

Local Digital subsidiary

Canada

800-267-6215

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

International

Local Digital subsidiary or
approved distributor

Internal 1

USASSB Order Processing - WMOlE15
or
U.S. Area Software Supply Business
Digital Equipment Corporation
Westminster, Massachusetts 01473

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

Reader's Comments

RSTS/E Version 10.0 Release Notes
AA-5246H-Te

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

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

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

I would like to see morelless

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

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

N amelI'itle

Dept.
Date

Company
Mailing Address
Phone

Do Not Tear - Fold Here and Tape - - -

- - -

- -

-"I

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

~DmDDmDTM

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

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

III II , , , II, II ! , , , I, I, ,I, ,II, III 1.1 II I, ,I, ,,I, III ,,,I
________

Do Not Tear - Fold Here - - - - _ - - _ - _ - _ _ _ _ _ _ _ _ _ _ _ _ _ ,

Reader's Comments

RSTS/E Version 10.0 Release Notes

AA-5246H-TC

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

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

I would like to see more/less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

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

N ame!I'itle

)

Dept.

Company

Date

Mailing Address
Phone

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

- - -

- - - - - - -

- --,

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

~DmDDmDTM

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

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

1111111111111111111111111111111111111111111111111111
_ _ _ _ _ _ _ _

Do Not Tear - Fold Here _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ , I

- - - - - - - - - - - - - - - -- - -

Printed in U.S.A.