Digital PDFs

AA-KW28A-TC

November 1987

64 pages

Original

2.3MB

Document:	RSTS/E Release Notes
Order Number:	AA-KW28A-TC
Revision:	0
Pages:	64
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsts_e/V09/1_General_Information_and_Installation/AA-KW28A-TC_RSTS_E_V9.5_Release_Notes_Nov87.pdf

OCR Text

RSTS/E
Release Notes
Order No. AA-KW28A-TC

November 1987

These Release Notes describe new features of the
RSTS/E system and explain the differences between this
version 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

V9.5

SOFTWARE VERSION:

RSTS/E

V9.5

digital equipment corporation, maynard, massachusetts

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

~D~DDmDTM
DEC
DECmail
DECmate
DECnet
DECsystem-10
DECSYSTEM-20
DECtape
DECUS
DECwriter

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

RSTS
RSX
RT
UNIBUS
VAX
VMS
VT
Work Processor
WPS-PLUS

RSTS/E V9.5 Release Notes
CONTENTS
1

1.1
1 .1.1
1.1.2
1.2
1.2.1
1.2.2
1.2.3
1.2.4
1.3
1.3.1
1.3.2
1.4
1.5
1.5.1
1.5.2
1.5.3
2
2.1
2.1 . 1
2.1 . 2
2.2
2.3
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4 . .5
2.5
2.6
2.7
2.8
2.8.1
2.8.2
2.8.3
2.8.4
2.8.5
2.8.6
2.8.7
2.8.8
2.8.9
2.8.10
2.8.11
2.9

New Features of RSTS/E V9.5
New Hardware Support . . .
VT 320

.
.

. .... 1
. . . . . 1
...

RA82
. ..
........
Monitor
. . . . ..
. ......
Future Changes to Terminal Service .
. .
Terminal Service . . . . .
.........
Extended Cluster Size Support
. . . . . . . . .
Fast-Mapping Facility . . . . . . . . . . .
Programming considerations .
.......

2
2
2
3
3
4
4

DeL

•

SHOW QUOTA Command . . . . . . . .
New INSTALL Qualifier Argument . .

•

.
.

. . 7
. . 7

BACKUP

•

••

•

••••••••••••

Task Builder (TKB) . . . . . . . . . . . . . . . . 9
. . . . . . . . . . . . • 9
New RNDSEG Option
New Switches . . . . . . . .
.....
10
New Error Messages .
. . . . . . . . .
11
Differences Between v9.5 and v9.4 . . . . . .
12
Installation . . . . .
.........
12
Building CUSPs From The SOURCE Logical Package 12
Corrections
. . . . . . ..
...
13
Start-up Procedures
. . . . . . . . . . . . . . 14
Initialization Code (INIT.SYS) . . . . .
14
Corrections
. . . . . . . . . . . . . . . . 15
Monitor
.. . . . . . . .
. . .
16
Corrections
. . . . . .
. . .
16
EMT Logging Correction .
. . . . . . . . . 16
Terminal Service Corrections. . . . . . . . . 17
Set Terminal Characteristics Part I
. . . . . 17
Device Drivers . . . . . . . . . . . . . . . . 17
MS Tape Driver Corrections
. . . . . . . 17
XEDVR Enhancements
..........
18
L,OGIN . . . . . . . . .
......
18
Error Logging Package
. . . . .
19
Corrections
. . .
. . . . .
21
Floating Library Facility . . . . . . • . . . .
21
DeL
. . . . . . . . •.
..........
22
DCL Expression Handler .
. . . . .
22
DCL Logfiles . . . . . .
. . . . . . .
22
DCL Symbol Table Management
. . . . . . . . .
22
ASSIGN command . . . . . . . .
.•..
23
BACKUP command . . . . .
.....
23
BASIC command . . . . . . . . . . . . . .
24
/CONFIRM qualifier
. . . . . . . . . . . . . 24
CREATE/ACCOUNT Command . . . . . . . .
25
INITIALIZE command . . .
...
25
ON severity THEN command
. . . . . . . . . 25
WRITE command . . .
. . . . . . . . .
25
Help Files . . . . . . . . . . . . . . . . . . .
26
iii

RSTS/E V9.5 Release Notes

2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10.5
2.10.6
2.10.7
2.10.8
2.10.9
2.10.10
2.10.11
2.10.12
2.10.13
2.11
2.11.1
2.11.2

2.11.3
2.11.4
2.11.5
2.11.6
2.11.7
2.12
2.12.1
2.12.2
2.13
2.13.1
2.13.2
3
3.1
4
4.1

4.1 . 1

DCL
Commonly Used System Programs (CUSPs)
.. .
DSKINT
.............. .
Enhancements . . . . . . . . . . . .
Corrections
. . . . .
LOGIN.TSK . . . . . . .
SHUTUP.TSK .
. ...... .
LOGOUT.TSK .
. ........ .
ODT.TSK . . . . . . . . . . . . . . .
ONLCLN Enhancements
HOOK Enhancements
SAVRES
...
PIP
Corrections
. . . . ..
.......
OPSER BATCH PACKAGE
. . . . . . . . . . . .
Print/Batch Services (PBS) . . . . . . . . .
Corrections
. . . . . . . . . . . . . . .
SYSTAT

•

••

.
.
.
.

••••••••••

Unsupported utilities
. ..
. ..... .
MACRO-II V5.5 (MACRO.SAV and MAC.TSK)
.. .
New Features . . . . . . . . . . . . . . . . .
Additional Conditionals
. . . ..
. ..
Hexadecimal Support . . . . . . . .
Extensions and Bug Fixes . . . . . . . . .
XOR Flagged with z . . . . . .
.. .
.SBTTL Line 80 Characters
...... .
Limit of 254 Psects in Symbol Table . . . .
New and Changed Error Messages . . . . . . .
Permanent Direct Assignments Made Re~lly
Pe rmanen t
. . . . . . . . • . . . . . . .
Clarification of \ Operator . . . . . . . . .
.IRPC Now Handles Argument of 124 Characters.
AR with Null Argument . . . . . . . . . . . .
Space No Longer Needed Between Macro Name and
Argument List
. . . . ..
....... .
RMS -11

RMS-ll ACCESS METHODS
. ..
...
Corrections
. . .
RMS-ll UTILITIES . . . . .
Corrections
. . . . . . . . . . . .
Layered Products . . . . . . . . . . . . . . .
DECmail-ll V3.0 . . . . . . . . . . . . . .
Updates on RSTS/E V9.5 . . . . . . . . .
Corrections
. . . . . . . . . . . . . . .
DECne tiE
............. .
NCP Enhancements . . . .
. . . . .
Documentation Changes in RSTS/E V9.5 .
Corrections
. . . . . . . . . . . . . . . .
Known Problems and Restrictions with RSTS/E V9.5
Recommendations and Restrictions for Extended
Cluster-Size Disks .
. . . . . . . . ..
Wasted Space . . . . . . . . .
.....
iv

.
.
.
.

26
27
27
27
27
27
28
28
28
28
28
29
29
29
30
31
31
32
32
32
32
32
32
33
33
33
33
34
34
34
35
35
35
35
35
35
36
36
37
37
37
39
40
40
41
41
42
42
42

RSTS/E V9.5 Release Notes
4.1.2
4.2
4.2.1
4.2.2
4.2.3
4.3
4.4
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.6
4.6.1
4.6.2
4.6. 3
4.6.4
4.6.5
4.6.6
4.6.7
4.6.8
4.7
4.8
4.9
4.9.1
4.9.2

BACKUP strategy . . . . . . . . . . . . .
Installation . . .
........
..
Boot from TU10 . . . . . . . . . . .
..
Booting Magnetic Tape
. . . . . . . . . . .
Flag Files .
..............
DEUNA Ethernet Driver
... . . . . . . . . .
Initialization Code (INIT.SYS) .
. ..
Monitor . . . . . . . . . . . . . . . . . .
DB and DR Disk Drivers . . . . . . . .
MSCP Disk Driver . . . . . . . . . . . . . .
Virtual Disk as Part of the Public structure
TMSCP Tape Driver
.. . . . . . . . . . .
Terminal Service . . . . . . . . . . . . . .
Commonly Used System Programs (CUSPs)
.. .
ANALYS Package . . • . .
.... .
DSKSEK

•

••

.
.
.
.
.
.
.
.
.

•••••.•••

PIP

•

••

•

••••••••

•

••

•••

Supporting Disks with Unit Numbers Greater Than
9 .••••.•
•••••••••.•••
Log File Corruption . . . .
Print/Batch Services (PBS) .
RSX and RMS Tasks
RMS -11 . . . . . . . . . . . .
Layered Products .
DECmail-ll V3.0
DECnet/E . . .
NFT and FAL

42
42
42
43
43
43
43
44
44
44
45
45
46
46
46
46
47
47
47
48
49
49
49
49
50
50
51
51

RSTS/E V9.S Release Notes
Preface
The RSTS/E V9.S Release Notes describe new features in RSTS/E for this
release as well as differences between this and the previous release,
RSTS/E V9.4.
The procedure to install a new RSTS/E V9.S system or to upgrade an
existing RSTS/E system to V9.S follows the same general process
developed for V9.0.
Because of the V9.0 changes to the installation process, users of
earlier versions of RSTS/E should read the RSTS/E System Installation
and Update Guide prior to attempting an installation of RSTS/E V9.S.
If you are installing a new RSTS/E V9.S system, refer to PART I of the
RSTS/E System Installation and Update Guide.
If you are upgrading a pre-V9.0 svstem to V9.S, refer to PART II of
the RST'S/E System Installation and Update Guide.
If you are updating a RSTS/E V9.0 or later system to V9.S, refer to
PART IV of the RSTS/E System Installation and Update Guide.
In addition, users and programmers familiar with RSTS/E V9.4 should
read these notes to learn about changes and new features in RSTS/E
V9.S.
The V9.S Release Notes are divided into four sections:
1.
2.
3.
4.

RSTS/E v9.S New Features
Differences Between RSTS/E V9.S and RSTS/E V9.4
RSTS/E V9.S Documentation Changes
Known Problems and Restrictions with RSTS/E V9.S

NOTE
If you last used a version of RSTS/E older than V9.4,
you should read the release notes for any intermediate
versions.

vii

RSTS/E V9.5 Release Notes
New Features
1

1.1

New Features of RSTS/E V9.S

New Hardware Support

1.1.1

VT320

The VT320 is a 24 line, low cost, conversational text-only terminal
featuring VT220 compatibility.
Its features are:
o

Designed to provide high quality human interface and long
term reliability at low cost

25th line status display can be used to display local state
indicators, or be written from host

Level 3 terminal

Supports Terminal State Interrogation (TSI)

Supports 8-bit Architecture

The printer port is bidirectional and supports the 8-bit
architecture

DEC423 local direct connect

Set-up option allows Compose Key to be disabled

The DCL command SET TERMINAL/INQUIRE properly sets the software
characteristics of this new terminal.
The SET TERMINAL command qualifier /DEVICE_TYPE now accepts the
keyword argument VT320.
The SHOW TERMINAL command displays the new terminal type VT320.
The terminal type code for the VT320 is 50.

RSTS/E V9.5 Release Notes
New Features
1.1.2

RA82

The RA82 is the newest member of the Digital storage Architecture.
is a 625 megabyte disk drive that connects to the UDA50 or KDA50
series controller.

1.2

Monitor

1.2.1

Future Changes to Terminal Service

Several changes will be made in the next version of RSTS/E that will
impact terminal service.
These changes are required to enable
additional enhancements to the terminal driver~
The first of these
changes involves several features which are currently optional.
The
following features will be automatically included in all systems in
the next version of RSTS/E:
Multi-Terminal Service
Echo control
Control/T support
Multiple private delimiters
Since the default has been to include these features in every monitor,
we believe that there will be no impact on most sites.
For sites that
previously did not include any of these features, the size of the
monitor will be increased by IK word.
For sites that selected some,
but not all of these features, the inc:rease will be less than 1K word,
and may not have any impact at all.
In addition, the terminal service device driver will no longer need to
be assembled during the installation procedure.
This will result in a
small reduction in the time required to build a monitor (the exact
reduction will depend on the CPU being used).
Due to assembly no
longer being needed at installation time, the source for terminal
service will not be distributed on the binary kit.
Customers who
require sources to the terminal driver will need to purchase the
source kit for the release after V9.5.
Order numbers for the source
kit are:
QR430-EM
QR430-FR

1600 BPI media
Fiche

RSTS/E V9.S Release Notes
New Features

1.2.2

Terminal Service

The terminal driver has been modified to send a BELL character to the
terminal when the speed of a line set to auto-baud has been detected.
This will make users on systems with slow response times aware that
the speed has been determined and no further carriage returns are
required.

1.2.3

Extended Cluster Size Support

The monitor has been modified to allow access to a disk with a cluster
size of 32 or 64.
This allows RSTS/E to use a disk as a single volume
containing up to 4,096,000 blocks. RSTS/E now supports these disks as
data or system disk devices.
See section 4.1 for recommendations and
restrictions on using extended cluster-size disks. An extended
cluster-size disk is still considered a Level 1.2 disk, as the
directory structure has not changed.
However, an extended
cluster-size disk created by a RSTS/E V9.S or later system will not be
usable on previous versions of RSTS/E because its cluster size was not
valid. Any attempt to "MOUNT" an extended cluster-size disk under a
previous version will result in the following error:
"?Disk pack mount error"
Note that when using extended cluster-size disks with device cluster
sizes greater than 16 (RA82), the default buffer size to access the
disk in cluster mode will be larger than other disks.
This may cause
user programs to receive a "?Maximum memory exceeded" error when using
cluster mode I/O on the extended disks.
This is not the case for
small disks initialized with pack cluster sizes greater than 16, but
only for disks with device cluster sizes greater than 16.
Since RSTS uses an MFD/GFD/UFD cluster size of 16 on disks with a pack
cluster size greater than 16, a user program that accesses directory
structures directly might have to be modified. Any program that does
calculations of the MFD/GFD/UFD cluster size divided by the pack
cluster size to obtain a cluster ratio will have to be modified, as
this ratio will be less than 1.
If a cluster ratio is obtained that
is less than 1, the program should set it to 1.
Extended cluster-size disks are supported everywhere except in SAVRES.
See section 2.10.8 for more details on SAVRES and extended
cluster-size disks.

RSTS/E V9.5 Release Notes
New Features
1.2.4

Fast-Mapping Facility

A new mapping facility has been added as an alternative to the MAPFQ
subfunction of the .PLAS directive, providing greatly enhanced
performance and compatibility with the fast-mapping facility of
RSX-IIM-PLUS. Applications that are dependent on re-mapping of
libraries in the normal course of execution could see significant
speed improvements.
However, the fast-mapping facility has the following restrictions:
1.

Only the offset to the map field (FQSlZE) and, optionally,
the length to the map field (FQBUFL), may be modified by the
fast-mapping facility.

The interface to the fast-mapping facility is designed for
speed, not for ease of programming. Debugging a task using
fast-mapping may be more difficult than using the .PLAS
directive.
Specifically, protecting the operating system and
its data structures is the only validation of parameters that
is done.

The interface uses the PDP-II lOT instruction.
Tasks may use
lOT for internal communications and other functions, but
tasks that use fast-mapping cannot use the lOT instruction
for any purpose other than fast-mapping.

The interface uses registers for passing parameters rather
than using a FlRQB, a savings of significant instructions
over the .PLAS directive.
This means that the MACRO-II
programmer must be careful about register usage when using
fast-mapping.

These restrictions (particularly number 2) should not deter the use of
fast-mapping in high performance applications.
However, we recommend
that you first get the application running with the .PLAS directive,
varying only the FQSlZE and FQBUFL fields, and then replace the
directive with fast-mapping.
See section 1.5 of these notes for information about TKB and Fast Map.
Programming considerations
Before issuing a fast-mapping call, the task must create and map the
window by using the Create Address Window (CRAFQ) and MAPFQ
subfunctions of the .PLAS directive.
'rhe FlRQB+12(octal) in the CRAFQ
directive must be at least as large as the largest FQBUFL to be
requested in fast-mapping.

RSTS/E V9.5 Release Notes
New Features
Three parameters are required for the fast-mapping call.
The first
parameter is the base APR times 10 (octal) plus the I/D space flag (0=
I-space and 100 (octal)= D-space).
NOTE
Resident libraries are always mapped in both I and D
space on RSTS.
However, programs should not rely on
this continuing, and should specify the proper space
instead.
The second parameter is the offset field to map from the start of the
library to the base of the window.
The third parameter is an optional
length to map.
If the length to map is given, the high bit of the
first parameter (the APR times 10 (octal» must be set.
The following is a table of first parameter values:
Space

Base APR

If No Length Given

User-I
User-I
User-I
User-I
User-I
User-I
User-I
User-I

0
1
2
3
4
5
6
7

APR 1-0 cannot be changed
000010
100010
000020
100020
000030
100030
000040
100040
000050
100050
000060
100060
000070
100070

User-D
User-D
User-D
User-D
User-D
User-D
User-D
User-D

0
1
2
3
4
5
6
7

APR D-O cannot be changed .
000110
100110
000120
100120
100130
000130
100140
000140
000150
100150
100160
000160
000170
100170

with Length Given

The offset field (second parameter) is specified in 32-word slivers,
in the same way it would be for the FQSIZE value in the MAPFQ
subfunction of the .PLAS directive, and has the same meaning.
If the length to map (FQBUFL) is not specified (high bit a 0) the
length is assumed to be FIRQB+12(octal) from the last CRAFQ directive
executed.
If it is specified (high bit set), then that length is
mapped unless the value is zero.
If it is zero, then either the CRAFQ
size (FIRQB+12(octal»
or the size of the library minus the offset
size, whichever is smaller, is used.
R2 on return will contain the
length mapped in slivers.
This handling is identical to that for
FQBUFL in the .PLAS directive.

RSTS/E V9.5 Release Notes
New Features
Note the difference between the RSTS and RSX versions in that User D
space must remain mapped to user's low core (APRO) at all times in
RSTS. RSX does not have such a restriction.
Note that the speed of fast-mapping is affected by the parameter
values. Not specifying the length to map is the fastest and
specifying a length equal to zero is the slowest. The improvement
over the .PLAS directive is in the range of six to twelve times
faster. The amount of improvement depends on the amount of re-mapping
done by the task.
Calling Sequence
RO
Rl
R2

parameter 1
parameter 2
parameter 3

see table above
offset field
optional length specification

Returned data
RO

status

R2 length mapped
Rl & R3

IS.SUC if successful
IE. ITS or IE.ALG if failure
if successful length actually mapped in slivers
indeterminate

Programming examples:
1) Changing only window offset in I space:
MOV
MOV

#40,RO
#200,Rl

lOT
TST
BMI

RO
ERROR

iwindow at APR 4 in I-space
ioffset from base of library is 4K words
i200 slivers * 32 words/sliver
iR2 is not needed
iissue fast map call
isuccessful?
ino

2) Changing window offset and actual length specified:
MOV
MOV
MOV

#100150,RO
#lOO,Rl
#500,R2

lOT
TST
BMI

RO
ERROR

iwindow at APR 5 in D-space
ioffset 2K words from library base
ispecified len9th = 10K words
ithis will use APR's 5,6 & 7
iissue fast map call
isuccessful?
ino

RSTS/E V9.S Release Notes
New Features
3) Changing window offset and defaulted length specified:
CLR
CLR

#IOOl40,RO
RI
R2

lOT
TST
BMI
MOV

RO
ERROR
R2,MAPLEN

iwindow base at APR 4 in D-space
ioffset=O, window begins at library base
iforce calculation to FIRQB+12(octal) or
;remaining size of library
;issue fast map call
;successful?
ino
iCOPY of size actually mapped, in slivers

In the above text and examples the term "LIBRARY" means a resident
library or dynamic data region.

1.3
1.3.1

DeL

SHOW QUOTA Command

A SHOW QUOTA command has been added to DCL.

The format is:

$ SHOW QUOTA

The SHOW QUOTA command displays disk quotas for all mounted disks for
the account currently in use.
See the DCL help files for more
information.

1.3.2

New INSTALL Qualifier Argument

A new INSTALL qualifier argument has been defined to allow
installation of unrestricted floating libraries.
The new qualifier
argument is used as follows:
INSTALL/LIBRARY/NOAD[DRESS]=UNRE[STRICTED] name.lib
Refer to section 2.7 for a description of unrestricted floating
libraries.
The method of installing size-restricted floating libraries is as
follows:
INSTALL/LIBRARY/NOAD[DRESS=RESTRICTED] name. lib

RSTS/E V9.5 Release Notes
New Features
1.4

BACKUP

RSTS/E V9.5 provides a new feature for BACKUP to list files within
BACKUP savesets.
The syntax is as follows:
$ BACKUP/DIRECTORY dev:[p,pn]filnam.typ
- or $ RESTORE/DIRECTORY dev:[p,pn]filnam.typ
For example:
$.backup/dir x:savset
please mount volume 1 of Backup set SAVSET.BCK
Where can this volume be located'? <DRO:>
Account Name
.Typ Size
Prot Accessed
Date
[195,0
]MYDCL .COM
4
< 60> 04-0ct-85 04-0ct-85
[195,0
]LOGOUT.COM
1C
<124> 04-0ct-85 04-0ct-85
[195,0
] ERROR .COM
1
< 60> 04-0ct-85 04-0ct-85
[195,0
1
]DONE
.TXT
< 60> 04-0ct-85 04-0ct-85
[195,0
]JOB2
.COM
1
< 60> 04-0ct-85 04-0ct-85
[195,0
]LOGIN2.COM
1
< 60> 04-0ct-85 04-0ct-85
[195,0
]SPWNJ2.LOG
9
< 60> 09-Jun-87 09-Jun-87
[195,0
]ASSEM .COM
2
< 60> 19-Jun-87 19-Jun-87
[195,0
]LOGIN .BAK
2
< 60> 14-Jul-87 14-Jul-87
Please dismount volume 1 of Backup set SAVSET.BCK

Time
Clu RTS
04:06 PM
4 DCL
04:06 PM
4 DCL
04:06 PM
4 DCL
04:06 PM
4 ... RSX
04:06 PM
4 DCL
04:06 PM
4 DCL
03:16 PM
4 DCL
12:19 PM
4 DCL
09:30 AM
4 DCL

$.backup/dir/full x:savst3
Please mount volume 1 of Backup set SAVST3.BCK
Where can this volume be located'? <DRO:>
[ 0,10]RMSBCK.TSK
Size:
92/92
Run time system: RSX
Created:
04-0ct-85 03:29 PM
Last accessed:
04-0ct-85
Protection:
<104>
(Executable, Owner:RWE, Group:E, World:E)
Organization: Sequential
Attributes:
Clustersize= 16, Contiguous
Record format:
Fixed length
Record attributes:
None

RSTS/E v9.5 Release Notes
New Features
0,10]RMSRSTnTSK
Size:
110/110
Run time system: RSX
Created:
04-0ct-85 03:29 PM
Last accessed:
04-0ct-85
Protection:
<232> (Privileged, Executable, Owner:RWE, Group:E, World:E
Organization: Sequential
Attributes:
Clustersize= 16, Contiguous
Record format:
Fixed length
Record attributes:
None
O,lO]RMSDEF.TSK
Size:
77/77
Run time system: RSX
Created:
04-0ct-85 03:29 PM
Last accessed:
04-0ct-85
Protection:
<104>
(Executable, Owner:RWE, Group:E, World:E)
Organization: Sequential
Attributes:
.Clustersize= 16, Contiguous
Record format:
Fixed length
Record attributes:
None
Record attributes:
None
Please dismount volume 1 of Backup set SAVST3.BCK
Two additional new qualifiers that may be specified only with
/DIRECTORY are /BRIEF and /FULL.
The /BRIEF qualifier is the default
and is similar to the DCL full directory format (minus file
attributes).
The /FULL qualifier is optional and gives information
for each file on multiple lines, similar to the VMS DIRECTORY/FULL
command.
The qualifier /OUTPUT has been added to the BACKUP and RESTORE
commands and is a synonym for /LIST_FILE.
Qualifiers to select files, such as /SELECT, /EXCLUDE, etc., can be
used with /DIRECTORY.
The DCL help fi.les for BACKUP and RESTORE now include the additional
qualifiers /BRlEF, /FULL, /DIRECTORY, and /OUTPUT.

1.5
1.5.1

Task Builder (TKB)
New RNDSEG Option

You use the RNDSEG option to cause TKB to round the size of a named
segment up to the nearest APR boundary while building a resident
library.

RSTS/E V9.S Release Notes
New Features
Syntax:
RNDSEG=seg-name
seg-name:
The 1- to 6-character Radix-50 name of the segment.
Default:
None
Notes:

The RNDSEG option operates only during a library build.
Attempting to use the option while building any other form of
task will result in the following diagnostic error message:
TKB -- *DIAG* - Library build not requested - ignoring option
RNDSEG=SEGl

If you attempt to specify a nonexistent segment name, the
following diagnostic error will be generated and the build
will continue:
TKB -- *DIAG* - Segment not found to address round
RNDSEG=NOSEG

1.5.2

New Switches
/FM
The /FM qualifier tells TKB to set the proper bits in the
task header to enable the fast-mapping feature of the
executive.
The following command line shows the proper placement of the
/FM switch:
TKB>file.tsk/FM,,=file.obj
The default is fast-mapping disabled (/-FM).

RSTS/E V9.S Release Notes
New Features

/SB
The /SB qualifier causes the task to be built with the slow
mode of the Task Builder.
The following command line shows the proper placement of the
/SB switch:
TKB>file.tsk/SB,,=file.obj
NOTE
The slow task builder STK.TSK will be removed in a
future release of RSTS/E.
The default in TKB is /-SB.

1.5.3

The default in STK is /SB.

New Error Messages

CLUSTER LIBRARY ELEMENT, element-name, IS NOT RESIDENT OVERLAID
This message occurs when the listed cluster element has been built
without memory-resident overlays.
This kind of element cannot be used
as a cluster library element.
Cluster libraries 2-6 must be
memory-resident and overlaid.
INCOMPATIBLE OTS MODULE
This message occurs when the OTS (Overlay Run-Time System) module
requested by TKB has not been found.
The OTS modules are part of the
system library.
This error occurs if you are using an incompatible
version of the system library (SYSLIB.OLB).

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
2

2.1
2.1.1

Differences Between V9.S and V9.4

Installation
Building CUSPs From The SOURCE Logical Package

Section 2.11.1 of the RSTS/E V9.0 Release Notes lists those sources
included with RSTS/E, and describes how to install them on your
system.
To create executable programs from these sources, you must have
BASIC-PLUS-2 available on your system.
To ensure that these programs
are created correctly, you must compil,e the sources with the following
BASIC-PLUS-2 attributes in effect:
Data type
REAL
Real size
SINGLE
Integer size
WORD
Scale factor
0
Variant
0
Chain with line #
Once you have compiled a source module, use the DCL LINK command or
run the Task Builder (RUN $TKB) to create the executable program.
The following example illustrates how to correctly build the LOGIN
program located in the SOURCE$:
account.
It assumes that your
BASIC-PLUS-2 compiler is installed with the defaults shown above:
$ BASIC/BP2
PDP-II BASIC-PLUS-2 V2.3-00
BASIC2
OLD SOURCE$:LOGIN.BAS
BASIC2
COMPILE
LOGIN
11:55 AM

24-May-86

BASIC2
EXIT

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
$ RUN $TKB
TKB>LOGIN.TSK=LOGIN.OBJ,LB:BP20TS/LB
TKB>/
Enter Options:
TKB>UNITS=13
TKB>ASG=SY:5:6:7:8:9:l0:ll:l2
TKB>EXTTSK=512
TKB>LIBR=CSPLIB:RO
TKB>//
$ COPY/REPL/PROT=232 LOGIN.TSK SYO:$LOGIN.TSK
[File LOGIN .TSK copied to [1,2]LOGIN .TSK]
$ DELETE LOGIN.OBJ,LOGIN.TSK
LOGIN .OBJ deleted
LOGIN .TSK deleted
The TKB "LIBR=CSPLIB:RO" option causes the resultant task to use the
CSPLIB resident library, reducing the overall memory requirements of
CUSPs running on your system. All of the components included in the
SOURCE package, except for SHUTUP.BAS, should be task-built using the
CSPLIB resident library.
SHUTUP.TSK cannot be built with any resident
libraries because it removes all resident libraries when shutting down
the system. Remove the TKB "LIBR=CSPLIB:RO" option when task-building
SHUTUP.BAS.
Be sure to assign the proper protection code to any CUSP program that
you create.
See Article 0.1.1 of the RSTS/E Maintenance Notebook
(June 1985) for a complete list of the software components included
with RSTS/E and their associated locations and protection codes.
Note that DIGITAL does not support any CUSPs that have been modified.
If you encounter problems with a CUSP that you have modified, please
confirm that the problem occurs with the standard supplied CUSP before
submitting an SPR.
If you have suggestions or ideas that might
improve any of the CUSPs on RSTS, please submit a priority 5
(suggestion) SPR.

"2.1.2

Corrections

The following problems have been fixed in the installation procedure:
o

Prior to RSTS/E V9.5, the installation procedure would abort
if it was restarted with the installation tape not at BOT.
In RSTS/E V9.5, the installation procedure ensures that the
installation tape is rewound before proceeding.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4

2.2

When configuring the monitor, the SYSGEN program would not
use the template monitor's configuration for the number of
DHVll lines to enable as the default.
RSTS/E V9.5 uses the
template monitor's DHVll configuration as the default.

SYSGEN was giving erroneous and variable prompts at the
"template monitor's name" question. When you pressed. the
return key at the <??> prompt, the default would change to
<?>. This problem has been corrected.

Prior to RSTS/E V9.5, you were not able to install the SORT
package if you said "YES" to I&D space tasks and the
currently installed monitor still had a swap max of 32K.
You
would get a "?Not enough available memory" error when the
installation procedure tried to run the I&D space version of
MAC.TSK or TKB.TSK.
In RSTS/E V9.5, the SORT package
includes the non-I&D space version of MAC.TSK and TKB.TSK and
the installation procedure uses these tasks instead of the
ones in the system library.
These tasks are deleted by the
installation procedure after SORT has been successfully
installed.

start-up Procedures

Two changes have been made to the START.COM file.
If you are updating
a V9.* system, this file will be restored to [0,1] with the filename
START.095.
Compare the differences between this file and your
START.COM file and make the appropriate changes to your file.

2.3

The EDT resident library is now installed using the new
/NOADDRESS=UNRESTRICTED qualifier on the INSTALL/LIBRARY
command.

The comments about using the /LOCK qualifier when running
ERRINT have been removed.
Using the /LOCK qualifier can
cause memory fragmentation and possible system lock-up.

Initialization Code (INIT.SYS)

INIT has been modified to allow access to extended cluster-size disks:
o

The DSKINT option has been modified to allow initializing
extended cluster-size disks. A disk initialized with a pack
cluster size of 32 or 64 will require MFO, GFO, and UFO
14

RSTS/E V9.5 Release Notes
Differences Between V9~5 and V9.4
cluster sizes of 16. See section 4.1 for recommendations and
restrictions on using extended cluster-size disks.
o

The COpy option has been enhanced to allow copying system
files to a disk with a cluster size greater than 16.

REFRESH has been modified to allow file manipulation on
extended disks, as well as rebuilding them off-line.

The SAVRES option of INIT has been modified and does not
allow access to disks with a cluster size of 32 or 64.
If
this is attempted, the following error message is displayed:
"SAVRES cannot be used with disks of clustersize greater than 16"
The operation will then be aborted and a new command prompt
issued.

corrections
o

In previous versions of RSTS/E, if you booted INIT.SYS from a
device that was connected to a non-primary controller (that
is, a controller that is not at the primary CSR address),
INIT would display the message "Warning - Booted device is at
a non-standard CSR address" but would still allow you to
proceed normally.
If you then attempted to start a monitor
SIL using the non-primary controller as the system disk
controller p the system would sometimes crash during start-up.
In V9.5, INIT.SYS has been enhanced in two ways to remedy
that problem.
First, if INIT sees that it has been booted
from a non-primary controller, it displays an expanded
warning message which reads:
Warning - Booted device is at a non-standard CSR address
You must use the CSR suboption of the HARDWR option to
set the CSR address before timesharing can be started.
Second, INIT will not allow timesharing to be started until
the CSR option has been used to identify the non-primary
controller's address to INIT.

INIT.SYS now looks at the attributes for account SYO:[1,2]
before attempting system start-up to ensure that it is a USER
account that is set to be INTERACTIVE.
If either of these
conditions is not met, an error message is displayed and
start-up is aborted.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9a4
Note that account [1,2] is automatically set up correctly on
disks that are initialized as SYSTEM disks.
o

A problem existed in previous versions of RSTS/E with the
INSTAL option of INIT.SYS. If the INSTAL option was used to
install a monitor, and the installation process aborted or
was stopped for any reason, invalid information was left in
the configuration tables but INIT still thought that a SIL
was currently installed. If you then attempted to start
timesharing, several random error messages would display and
the start-up would abort.
This problem has been fixed in V9.5. If an INSTAL aborts (or
is aborted) during certain critical phases, the currently
installed monitor is deinstalled and the message "Please
install a valid monitor SIL" is displayed. You must correct
the cause of the abort, if necessary, and then install a
valid SIL before timesharing can be started.

2.4
2.4.1

In versions of RSTS/E since V9.3, the PARITY suboption of
DEFAULT would cause an "Unexpected trap through 4" error if
the system had more than 1920K words of memory. This problem
has been fixed for v9.5.

Monitor
Corrections

Previously, the system would crash when dismounting a disk volume, if
the drive had been hardware write-protected after being mounted as a
Read/Write device, and a user then att·empted to delete an account from
the disk. This problem has been corrected in V9.5.

2.4.2

EMT Logging Correction

A problem existed in the EMT Logger Receive Call where random data was
being returned in bytes 3 through 40, rather than the information
described on pages G-5 and G-6 of the RSTS/E Programming Manual. This
problem has been corrected in V9.5.

RSTS/E v9.S Release Notes
Differences Between V9.S and V9.4

2.4.3

Terminal Service Corrections
o

A problem existed in V9.4 where opening a log file with the
/TIMESTAMP qualifier would cause a time stamp to be written
after each character written to the logfile.
This problem
also caused multiple time stamps to be written at the end of
a logfile produced by PBS. A dispatch article (Seq.
3.3.14M) published in the September Software Dispatch
provides a correction to the problem for V9.4.
This problem
has been corrected for V9.S.

In V9Q3 and V9.4, a problem existed where C1 control
characters 129 through 132 were not converted to co control
characters, when not using Transparent Controls Mode (Mode
16384%), as in previous versions of RSTS/E.
This problem has
been corrected in V9.S.

A problem in terminal service existed where the last record
was not read from certain files when issuing the DCL READ
command.
This problem occurred when reading files with
implied carriage control attributes, but was dependent upon
where the record was situated in the file.
Problems
generally occurred when the last byte of a record was the
last byte of a block.
This problem has been fixed in V9.S.

2.4.4

Set Terminal Characteristics Part I

A problem existed in the UU.TRM Part I directive where issuing the
call to permanently enable/disable CTRL/R and CTRL/T would have no
effect.
This problem has been fixed in V9.S.

2.4.5

Device Drivers

MS Tape Driver Corrections
o

The job hang experienced when using new tapes in TK2S drives
has been fixed in V9.S.

On ANSI tapes that were created by methods other than the DCL
COpy command or the PIP system utility, the block count field
of the ANSI EOF1 trailer record for a file would contain an
incorrect count if any soft tape errors occurred while
writing that file.
This problem has been fixed for V9.S.

1, 7

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
XEDVR Enhancements
The device driver for the DEUNA and DELUA devices has been enhanced in
several minor ways for V9.5.
Sites using this driver are likely to
notice a reduction in superfluous errors being logged by the driver,
and may notice that some changes have been made to Circuit Counter
computations, correcting the Bytes Sent and Bytes Received fields in
the circuit counters.

2.5

An announcement message now prints when a user logs in~
before any prompting begins.
This feature is similar to the
SYS$ANNOUNCE logical on VMS systems.
The message is placed
in the file [O,l]LOGIN.TXT and must be a Stream-ASCII file,
similar to [1,2]NOTICE.TXT.
This file can be created,
edited, or removed by the system manager or anyone with
sufficient privileges to change files in [0,1].
NOTE
Do not put escape sequences in
[O,l]LOGIN.TXT.
They will not be displayed
properly.
Also, we recommend that you place this file,
along with LOGIN.COM, at the beginning of the
[0,1] directory for better performance.
You
can use the command:
PIP [0,1]/MO:1536=[0,1]LOGIN.TXT/LO

The [O,l]LOGIN.COM file has been changed to use the GOSUB and
RETURN commands that were introduced in RSTS/E V9.4.
If you
are updating a V9.* system, then this file will be restored
to [0,1] with the filename LOGIN.095.
Compare the
differences between this file and your LOGIN. COM file and
make the appropriate changes to your file.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
NOTE
If you do change [O,l]LOGIN.COM, we recommend
that you place the file at the beginning of
the [0,1] directory for better performance.
You can use the command:
PIP [0,1]/MO:1536=[0,1]LOGIN.COM/LO

2.6

Error Logging Package

The following enhancements have been made to the error logging
package:
o

The ability to recall a prompt.
By typing "",, at any of the prompts, you can recall the
previous prompt.
For example:
Input File <ERROR$:ERRLOG.FIL)? <CR>
Output File <KB:ERRDIS.OUT>? <CR>
He[lp], Ba[d blocks], Su[mmary], Fu[ll] Report or Ze[ro]
File <Summary>? "
output File <KB:ERRDIS.OUT>? ...
Input File <ERROR$:ERRLOG.FIL>? "
Input File <ERROR$:ERRLOG.FIL>?

The ability to handle AM/PM format times.
You can now enter times in AM/PM format as well as 24-hour
format.
For example, either of these times are now
acceptable to ERRDIS:
Starting Time <First Error>? 23:17
or
Starting Time <First Error>? 11:17 PM

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
o

The ability to handle numeric date formats, and the YESTERDAY
and TODAY keywords.
In addition to the alphanumeric date format (dd-mmm-yy), you
can now enter a date in the numeric date format (yy.mm.dd).
In this format, yy is the year in the range 70 to 99, mm ii
the month in the range 01 to 12, and dd is the day in the
range 01 to 31.
For example, you can enter the date August
5, 1987 as follows:
Starting Date <First Error>? 87.08.05
In addition to the above-mentioned formats, you can also use
the keywords YESTERDAY and TODAY.
For example:
Starting Date <First Error>? YESTERDAY

Selective zeroing option.
You now have the option of zeroing the entire file or just a
specific error type without first receiving a Summary Report.
When you type "ZE" at the selection prompt, you will be
prompted to zero the entire error file (ALL, which is the
default), or only a specific error type, indicated by a
two-letter code (i.e., KT, DU, OM).
The following example
demonstrates this new feature:
He[lp], Ba[d blocks], Su[mmary], Fu[ll] Report or Ze[ro]
File <Summary>? ZE
Zero Which Error Type <All>? <CR>
Completion results in a zeroed error file and returns you to
the "Input File <ERRLOG.FIL>?" prompt.
He[lp], Ba[d blocks], Su[mmary], Fu[ll] Report or Ze[ro]
File <Summary>? ZE
Zero Which Error Type <All>? KT
Completion results in all KT errors being zeroed from the
error file and returns you to the "Input File <ERRLOG.FIL>?"
prompt.
Previously, you could ask to see errors of a specific type,
and still have the option of zeroing the entire error file.
Now if you ask to see all errors, you can zero the entire
error file.
If you ask to see errors of a specific type, you
can only zero errors of that type.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
The following examples show this change:
Input File <ERROR$:ERRLOG.FIL>? <CR>
Output File <KB:ERRDIS.OUT>? <CR>
He[lp], Ba[d blocks], Su[mmary], Fu[ll] Report or Ze[ro]
File <Summary>? FU
Specific Error Type <All>? <CR>
Starting Date <First Error>? <CR>
Ending Date <Last Error>? <CR>
Zero Error File upon completion (Yes/No) <No>?
Input File <ERROR$:ERRLOG.FIL>? <CR>
Output File <KB:ERRDIS.OUT>? <CR>
He[lp], Ba[d blocks], Su[mmary], Fu[ll] Report or Ze[ro]
File <Summary>? FU
Specific Error Type <All>? KT
Starting Date <First Error>? <CR>
Ending Date <Last Error>? <CR>
Zero KT Errors upon completion (Yes/No) <No>?

Corrections
error display program ERRDET.TSK would sometimes abort with a
DI?Subscript out of range" error if a corrupted error log packet was
encountered while displaying a FULL report of MSCP or TMSCP errors.
This problem has been fixed for V9.5.
~rhe

2.7

Floating Library Facility

Prior to RSTS/E V9.5, there were two classes of resident libraries:
fixed address (added with INSTALL/ADDRESS) and floating address (added
with INSTALL/NOADDRESS) libraries.
There are no programming
restrictions associated with fixed address libraries, but you must
have physical memory available for each individual fixed address
library added to the system.
Floating libraries, on the other hand,
have significant programming restrictions (documented in the RSTS/E
Programming Manual), but do not require available physical memory over
that of the memory needed for user jobs.
In V9.5, a new type of resident library, the unrestricted floating
library, has been added to RSTS/E.
The old floating libraries are now
referred to as restricted floating libraries.

RSTS/E V9.S Release Notes
Differences Between V9.S and V9.4
The major advantage with this new class is in memory utilization~ as
long as there is adequate memory for the largest floating library
installed on the system, the user can have any number of floating
libraries installed and is free to us~ them in any order, one at a
time.
These libraries will overlay each other probably using the same
physical memory.
It is now possible to have the sum total of library
sizes greater than the total physical memory in the system.
The only difference between unrestricted floating libraries and fixed
libraries is that a user program can only map one floating library at
a time.
It is not valid to map to more than one unrestricted floating
library, nor is it valid to map to a restricted and an unrestricted
floating library.
It is valid to map any number of fixed libraries in
combination with the single floating library.
To install the new class of floating library a new DCL qualifier has
been added.
The installation command is as follows:
INSTALL/LIBRARY/NOADDRESS=UNRESTRICTEI> name.lib

2.8
2.8.1

DeL
DeL Expression Handler

previously, at the interactive level, if a label was specified
followed by a non-string assignment statement (i.e., an assignment
that did not use the := or :== format}, string assignment was
performed.
This problem has been fixed in V9.S.

2.8.2

DeL Logfiles

under certain conditions, the carriage return and line feed characters
were omitted from logfiles.
This occurred if the last character of an
RMS error message was the last character of a block in a logfile.
This problem has been fixed in v9.S.

2.8.3

DeL Symbol Table Management

Several problems were fixed in the symbol table management routines.
These problems generally occurred when the symbol table was at or near
its size limit. A dispatch article (20.1.7) published in the
September Software Dispatch provides a correction to these problems
for pre-V9.S systems.

RSTS/E V9.S Release Notes
Differences Between V9.S and V9.4
2.8.4

,1\SSIGN command

Previously, when using the ASSIGN command, if you specified a user
logical name ending with a dollar sign ($), and the device to which
the logical name was being assigned did not contain a PPN, the "$"
would be treated as part of the device name.
For example, the
command:
$ ASSIGN DRO: DISK$:
resulted in the assignment of of DISK:

to DRO:[l,2].

In V9.S, the error U?Invalid user logical name" is reported if the
logical name contains a dollar sign.
Dollar signs are only valid in
system logical names.

2.8.5

BACKUP command
o

The range :for the /GROUP_SIZE qualifier has been changed to 0
to 100 to be compatible with the VMS BACKUP command. A value
of 0 is equivalent to /NOGROUP SIZE, indicating no XOR blocks
will be written to the backup Iile.

Default Buffersize for MS and MU Device Types
The default buffersize for MS and MU devices
from 3 to 5S.
This change will allow the MS
drivers to stream data to the TUBO, TUBl and
change will reduce the time it takes to back
these devices.

has been changed
and MU device
TKSO.
This
up disks to

We do not recommend that you lower the buffersize below 20
when writing savesets to the TKSO. Also, using the qualifier
/BUFFER_SIZE=MAX is not recommended for streaming or
non-streaming tape drives.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
2.8.6

BASIC command

Support has been added for BASIC-PLUS-2 V2.4 (BP2) command lines.
Previously the BASIC command would only allow you to switch into a
BASIC environment. Now when using BP2 (the default), you can issue a
complete BASIC-PLUS-2 command directly from DeL.
The command line
format is as follows:
$ BASIC [commandline]

commandline

= { [/qualifiers] [[@]file-name[/qualifiers]] }

qualifiers =
/[NO]BUILD
/[NO]CHAIN
/[NO]CROSS[:[NO]KEYWORDS]
/[NO]DEBUG
/[NO]FLAG[:[NO]DECLINING]
/[NO]LINES
/[NO]LIST[ :lst-file]
/[NO]MACRO[ :mac-file]
/[NO]OBJECT[ :obj-file]
/SCALE:int-const
/VARIANT:int-const
/[NO]WARNINGS
Example:
$ BASIC/BP2/LIST foo.b2s/0BJECT:foo.out
$ BASIC/Bad_Qual/LIST file
BASIc/~ad_Qual/LIST file

BASIC -- Illegal Qualifier

2.8.7

/CONFIRM qualifier

The /CONFIRM qualifier has been added to many DCL commands, and is
synonymous with /QUERY.
This change has been added to be more
compatible with other operating systems that use /CONFIRM.
The
commands which accept the /CONFIRM qualifier are:
APPEND
COpy
DELETE

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
RENAME
SET PROTECTION
TYPE

2.8.8

CREATE/ACCOUNT Command

Prior to RSTS/E V9.5, the CREATE/ACCOUNT command would print the
newly-created account's UFD cluster numbers only when the /POSITION
qualifier was specified together with the /SIZE qualifier.
Now, the
UFD cluster numbers are displayed regardless of the /POSITION
qualifier.

2.8.9

INITIALIZE command

The /MFD CLUSTER SIZE and /CLUSTER SIZE qualifiers now accept only
integer arguments that are a power-of two.
If an integer is specified
which is in the valid range for that qualifier but is not a power of
two, the DCL error message "?Number not a power of 2" displays.
The /CLUSTER SIZE qualifier to the INITIALIZE command has been
modified to accept arguments in the range 1 to 64.
For more detailed
information on this difference see section 2.3 of these notes.

2.8.10

ON severity THEN command

When sW'itching back and forth from DCL to another run-time system, DCL
would occasionally ignore warnings, errors, and severe errors, and not
take the ON severity THEN condition.
Upon entry back into DCL, DCL
now gets the most severe error since it was last entered, and acts
upon the severity condition if ON severity THEN is in effect.

2.8.11

WRITE command

Previously, DCL could fail with "??Program failure in DCL" if an
attempt was made to write to a data file that was opened with the
OPEN/WRITE command and the currently allocated symbol table memory was
near full.
A dispatch article (20.1.8) published in the October
Software Dispatch provides a correction to this problem for pre-V9.5
systems.
This problem has been fixed for V9.5.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
2.9

Help Files

The following list represents all of the technical changes made to the
RSTS/E help files for V9.5:

DeL
APPEND command
/CONFIRM and /NOCONFIRM have been added to APPEND.
BACKUP command
New qualifiers (/BRIEF /DIRECTORY /FULL /OUTPUT) have been
added to the subtopics list.
/ACCOUNT_DATA replaces /NOACCOUNT_DATA as the default.
BASIC PLUS command
This command no longer appears in the master list, but is a
subtopic of the BASIC keyword.
COpy command
/CONFIRM and /NOCONFIRM have been added to COpy.
DELETE command
/CONFIRM and /NOCONFIRM have been added to DELETE.
INSTAL /LIBRARY command
/NOADDRESS=RESTRICTED and /NOADDRESS=UNRESTRICTED have been
added to subtopics list.
RENAME command
/CONFIRM and /NOCONFIRM qualifiers have been added to
subtopics list.
RESTORE command
New qualifiers (/BRIEF /DIRE:CTORY /FULL /OUTPUT) have been
added to the subtopics list.
SET PROTECTION command
/CONFIRM and /NOCONFIRM qualifiers have been added to the
subtopics list.
26

RSTS/E V9.S Release Notes
Differences Between V9.S and v9.4
SHOW QUOTA command
This is a new command in V9.S.
TYPE command
/CONFIRM and /NOCONFIRM qualifiers have been added to the
subtopics list.

2.10

Commonly Used System Programs (CUSPs)

2.10.1

DSKINT

EnhancE~men t s

DSKINT has been modified to allow initializing a disk with a pack
cluster size of 32 or 64. An extended disk requiring a device cluster
size of 32 or 64 is also allowed. When initializing a disk with a
pack cluster size of 32 or 64, DSKINT uses MFD, GFD, and UFD cluster
sizes of 16.
Corrections
Previous versions of DSKINT would sometimes fail with spurious error
messages.
This problem has been corrected in V9.S.

2.10.2

The following problems have been fixed in LOGIN.TSK:
()

Prior to RSTS/E V9.S, if you did not have the appropriate
GACNT or WACNT privilege, you could not attach to a detached
job that was running out of another account.
You would
always get a "?Failure to attach to job" message and be
logged-out.
NOw, if you don't have the appropriate
privilege, LOGIN prompts you for the password.
If the
password is correct, you will be attached to the job.
If it
is incorrect, you will be logged back into your account.

Prior to RSTS/E V9.S, LOGIN would not allow you to attach to
a detached job whose job number was greater than the current
job maximum.
This has been fixed for RSTS/E V9.S.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
o

SHUTUP.TSK

2.10.3

2.10.4

Prior to RSTS/E V9.5, if you attempted to log into another
account and you exceeded your disk quota on a disk whose unit
number was greater than 9, LOGIN would display the disk
number incorrectly. This has been fixed for RSTS/E V9.5.

SHUTUP.BAS, the source to SHUTUP.TSK, is now included in the
System Program package, SOURCES. It can be retrieved from
the RSTS/E distribution kit with the command "@[O,l]INSTALL
SYSTEM PROGRAM SOURCES". See section 2.1.1 of these notes
for information on rebuilding SHUTUP.BAS.

Prior to V9.5, it was possible to get illegal system usage
errors when running SHUTUP. This condition has been
corrected.

LOGOUT.TSK

Prior to RSTS/E V9.5, LOGOUT would not terminate the message it
broadcasts to KBO: with a <CR><LF> sequence; it would leave the
cursor at the end of the message. For RSTS/E V9.5, LOGOUT will append
a <CR><LF> sequence to the end of the message.

2.10.5

ODT.TSK

Prior to RSTS/E V9.5, the ODT.TSK program did not have the arithmetic
precision it needed to access addresse's above 400000(8). For RSTS/E
V9.5~ ODT.TSK now uses double-precision.

2.10.6

ONLCLN Enhancements

ONLCLN and MOUNT have been modified to support disks with cluster
sizes greater than 16.

2.10.7

HOOK Enhancements

HOOK has been modified to allow HOOKing an extended cluster-size disk.
28

RSTS/E V9.S Release Notes
Differences Between V9.S and V9.4

2.10.8

SAVRES

SAVRES has been modified to display an error message if you attempt to
use it on extended cluster-size disks (disks with a pack cluster size
greater than 16).
If you attempt this, SAVRES displays the following
error message:
"SAVRES cannot be used with disks of clustersize greater than 16"
The operation will then be aborted, and a new command prompt issued.

2.10.9

PIP

The PIP /RENAME command now checks the input and output DEVICE and PPN
to make sure they match before attempting to rename a file.
A PIP
/RENAME command will be legal if the OUTPUT device and PPN match the
input DEVICE and PPN.
If an input DEVICE or PPN is specified, then a
matching output DEVICE or PPN must also be specified.
If an output DEVICE or PPN does not match the input DEVICE and PPN,
you will get one of two new error messages:
?Output/Input device mismatch on RENAME
or
?Output/Input PPN mismatch on RENAME
NOTE
Under DCL, no output device is required because DCL
supplies a "." if the device is not specified.

corrections
The following PIP problems have been fixed for V9.S:
o

If you changed both the name and protection code of a file
with the RENAME command, the confirmation message would
incorrectly say that the new file name was renamed to the new
file name, rather than that the old file name was renamed to
the new file name.
PIP now gives the correct message.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
o

A PIP/ZE of an account with protected files would not delete
the files and would not notify the user that there were files
left.
PIP now notifies the user if there are any undeleted
files after a /ZE command.

PIP incorrectly printed the Fixed Control Field in RMS VFC
files with no Carriage Control or Implied Carriage Control.
PIP now suppresses printing of the Fixed Control Field.

The restriction that caused the error "?Illegal RMS
organization" when attempting to transfer RMS INDEXED or
RELATIVE files from disk to tape, has been lifted.
The
original problem of infinite looping, which the restriction
was meant to prevent, has been fixed by allowing PIP to
handle record sizes greater than 4095.
NOTE
You can only copy RMS files to ANSI magtape.
See section 4.6.5 of these notes for
additional information.

2.10.10

OPSER BATCH PACKAGE

BATC~ jobs since V9.0 have run under the RTll run-time system, and
have not executed LOGIN.TSK.
That represents two incompatibilities
with OPSER BATCH prior to V9.0.
Therefore, OPSER BATCH has been
changed in two ways:

Every BATCH job will now execute [O,l]LOGIN.COM before
executing the .CTL file.

After the spawned job executes the LOGIN.COM files, BATRUN
sets the job's keyboard monitor (KBM) according to the
following conditions:

+---------------+------------.-----+-------------+-----------+
I $JOB followed I Job's KBM after I Is RSX.RTS
I Job's KBM I
by "/DCL"?
I
LOGIN. COM ?
I installed? I set to? I

+---------------+------------.-----+-------------+-----------+
YES
NO
NO
NO

N/A
DCL
DCL
NOT DCL

N/A
NO
YES
N/A

DCL
RTll
I
RSX
I No change

I
I

+---------------+-----------------+-------------+-----------+
30

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
Everything works as before, except that you can now have
OPSER BATCH jobs run under any installed keyboard monitor by
altering your LOGIN.COM files appropriately.

2.10.11

print/Batch Services (PBS)

Corrections
The following problems have been fixed for V9.5:
o

PBS now waits for characters in system buffers to be sent to
a keyboard device before a job is completed.
previously, a
job was completed as soon as the system had buffered all the
requests, occasionally resulting in some output being lost
when the system was shut down.

Print servers for keyboard devices that do not exist in the
monitor now display properly.
Previously, these devices
would display with names like "KBl28:", or "KBl92:".
This problem usually occurred when a print server had been
defined on a keyboard line, and then the controller had been
replaced with a different type.
These devices now display in device controller syntax, and
can be modified using that name.

PBSMGR would go into an infinite loop if the last line of
PBS$:FORMS.SYS ended with the continuation character.
PBSMGR
now displays the error message "?Error in 'forms definition
file".

Simulated form servers would occasionally cause PBS to stop
in the middle of a print job, or hibernate, stopping all
jobs.

If a batch job completed at exactly 10 seconds into any
minute, then the time-stamps at the end of the log-file
displayed the time as "xx:xx:OlO" instead of "xx:xx:lO".

PBS was incorrectly deciding which print servers understand a
real backspace character, causing backspaces to be simulated
on keyboard servers, and to do the wrong thing for line
printer servers.
PBS now handles backspaces correctly for
all print servers.

RSTS/E V9.S Release Notes
Differences Between V9.S and V9.4
o

2.10.12

If the SET TIME command was used to set the time past
midnight, PBS would not start jobs scheduled to run on that
day.
PBS now realizes when the date has changed and will
start any pending jobs that are able to run.

SYSTAT

Prior to V9.S, SYSTAT allowed improper' qualifiers to the /W:
switch.
Now, only a valid device is allowed in conjunction with the /Vi1:
switch.

2.10.13

Unsupported Utilities

Prior to RSTS/E V9.S, the files RSTSFL.OBJ, RSTSFL.OLB, and DSKPEK.OBJ
in UNSUPP$:
have not been usable because they did not have any RMS
attributes.
For RSTS/E V9.S, these files will be restored to UNSUPP$:
with their RMS attributes.

2.11

MACRO-II VS.S (MACRO.SAV and MAC.TSK)

2.11.1

New Features

Additional Conditionals
Two new conditionals have been added, .IF PI and .IF P2.
If PI tests
true, the assembler is in pass 1.
If P2 tests true, the assembler is
in pass 2.
Hexadecimal Support
Hexadecimal support has been added to MACRO-ll VS.S.
consists of:
o

AX for temporary radix change

.RADIX 16 for permanent radix change

.ENABL HEX for hexadecimal listings

The support

RSTS/E V9.5 Release Notes
Differences Between v9.5 and V9.4
You use ~x in the same way as you use
the linE~
.WORD

~B,

~D,

or AO.

For example, in

6+'" XIA

MACRO-II would treat the quantity lA as a two-digit hexadecimal
number, but evaluate the 6 in the current radix .
. RADIX 16 works in the same manner as .RADIX 2, .RADIX 8, or .RADIX
10 . . Rl~DIX 16 sets the default radix to 16, so that all numbers are
assumed to be hex.
The .EN1~BL HEX directive does not affect assembly of the source, but
it does change the listing format.
All addresses and the contents of
locations are listed as hexadecimal values.
NOTE
RESTRICTION: All hexadecimal values used with ~X and
.RADIX 16 must begin with a digit, which can be O.
For example, the hexadecimal value F3 must be written
as OF3.
Otherwise, MACRO-II assumes the item is a
symbolic name, not a hexadecimal number.

2.11.2

Extensions and Bug Fixes

XOR Flagged with Z
XOR is one of the class of instructions that operates differently in
certain addressing modes on different processors.
These uses of the
XOR instruction are now flagged with Z in the assembly listing .
• SBTTL Line 80 Characters
A .SBTTL line can now be 80 characters long.
Limit of 254 Psects in Symbol Table
You can now have more than 254 psects in your program; however, only
the first 254 appear in the symbol table.

RSTS/E V9.S Release Notes
Differences Between V9.S and V9.4
New and Changed Error Messages
In previous versions of MACRO-II for RT-II, the error message
"?MACRO--F--I/O error on workfile" could be caused either by a
legitimate I/O error or by running out of room in the workfile!.
These
two error conditions have been separated, and the error message
"Workfile space exceeded" added for the case of running out of room.
(The RSX version (MAC.TSK) of MACRO-II does not have this error,
because it can increase the size of its workfile dynamically.)
with all versions of MACRO-II, if your program requires workfile space
of greater than 400 8 blocks, you will get the error message
"?MACRO--F--Storage limit exceeded (64K)" (MACRO.SAV), or "MP~C
storage limit exceeded (64K)" (MAC.TSK).
This limit cannot be
increased.
Additional internal checks have been added to MACRO-II to help ensure
proper operation.
If an unexpected condition is detected, MACRO-II
now reports the error "?MACRO--F--Internal error" (MACRO.SAV), or "MAC
--- Internal error" (MAC.TSK).
If you get this error, please submit
an SPR to DIGITAL along with a method of duplicating the problem.

2.11.3

Permanent Direct Assignments Made Really Permanent

In previous versions of MACRO-II, it was possible to change the value
of a symbol that was assigned a value using the -.
operator, even
though values assigned with -.
are supposed to be permanent.
It
could be done like this:
SYMBOL=: 100
SYMBOL= SYMBOL
SYMBOL= 40

;Define permanent symbol
;Set permanent symbol to its current value
;Now its value can be changed

MACRO-II now retains a symbol's permanent attribute in all cases.

2.11.4

Clarification of \

Operator

The \ operator cannot be used with a forward reference; the symbol on
which it is used must already be defined.
In addition, the \ operator
cannot be used with a relocatable symbol.

RSTS/E V9.S Release Notes
Differences Between V9.5 and V9.4
2.11.5

.IRPC Now Handles Argument of 124 Characters

Previous versions of MACRO-II could not handle an .IRPC argument of
more than 96 characters. In MACRO-II V5.5, the limit has been
increased to 124 characters.

2.11.6

AR With Null Argument

If you use ~R with a null argument (~R followed by a <RET», the AR
produces a word of zeros, as though it had been followed by three
spaces.

2.11.7

Space No Longer Needed Between Macro Name and Argument List

You no longer need a space or tab between a macro name and an argument
list in angle brackets. For example, if BUILD is a macro name, the
line
BUILD<A,B,C>
is now valid.
had to be:

In previous versions of MACRO-II, the line would have

BUILD <A,B,C>

2.12

RMS-11

2.12.1

RMS-ll ACCESS METHODS

Corrections

Several changes have been made to correct problems relating to RMS-ll
terminal I/O.
o

RMS-ll reported a non-attributed stream file as having
embedded carriage control. Thus, a program which attempted
to copy the file to the terminal would not set up the

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
terminal correctly.
This would result in records being
output without any end-of-record carriage control.
To
correct this behavior, these files are now reported as
implied carriage control files by RMS-ll.
The correction was
in ROOPFL in RMSLIB.OLB as well as the resident library.
o

2.12.2

RMS-ll did not correctly handle $PUT to a terminal where the
record length exceeded 128. bytes.
Due to incorrect logic
carriage returns were inserted after each record fragment.
This caused inappropriate overprinting.
This correction was
in RIPUNR in RMSLIB.OLB and the resident libraries.

RMS-l1 UTILITIES

Corrections
o

RMSIFL failed to correctly report exit status when errors
occurred while loading a file with more than one alternate
key.
Once the first alternate key had been loaded without
errors, internal exit status was set to success.
Any errors
on subsequent keys were not reflected in the task's final
exit status.
This could cause command files or batch jobs to
function incorrectly.
Now, all errors are correctly reported
in the exit status.

Previously, RMSDES handled default devices incorrectly when
the GET and SAVE commands were issued.
The default device is
initialized by TKB to the device from which RMSDES is run.
If a HELP command was issued, the default device was reset to
LB:.
The CREATE command reset the default device to the file
specification passed with that 'command, or to SY:
if no
explicit device was present in the design buffer.
The GET
and SAVE commands used whichever of these defaults occurred
most recently.
NOw, GET and SAVE assume SY:
as the default
device.

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4

2.13

Layered Products

2.13.1

DECmail-ll V3.0

Updates on RSTS/E V9.S
Transfe]~ the DECmail-ll V3.0 update
during the system upgrade to V9.5.
Installation and Update Guide, Part
more information about transferring

components to the PATCH account
Refer to the RSTS/E System
IV:, Phase:3, Task:4, page 178 for
updates for Layered Products.

If you do not transfer DECmail-ll updates during the system upgrade,
you will need to mount your RSTS/E Installation media during the
DECmail--ll update.
The RSTS/E Layered Product Update Procedure will
transfer the DECmail-ll updates.
Requirements for this update:
Privileges:
Refer to the DECmail-ll Installation and System Manager's
Guide for information about the privileges needed.
Programs:
SY:[1,2]LBR.TSK
SY:[1,2]TKB.TSK
SY:[1,2]MAKSIL.TSK
Disk space:
1000 blocks for uP9ate files in PATCH$:
5350 blocks for update work files in WORK$:
NOTE
The 5350 blocks of disk space in WORK$:
will
be returned to the system as free space after
the update has completed.
1350 blocks for updated tasks in MAIL$:

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
NOTE
The blocks for the tasks in MAIL$: should be
contiguous for optimum performance.
The total number of free blocks needed to do this update is
7700 of which 1350 blocks should be contiguous.
In order to
reduce the need for disk space the MAIL update procedure
deletes files as soon as they are no longer needed.
NOTE
Use of DECmail-ll during the update may cause
unpredictable errors to occur.
Updating your DECmail-ll V3.0 software can be accomplished by invoking
the RSTS/E software update procedure. The following is an example of
a DECmail-11 update.
$ @[O,I]UPDATE LAYEREDPRODUCT MAIL
Deleting all global symbols
Patch account <PATCH$:> :
The following will be updated:
MAIL
Proceed?

<yes>

Please enter the name and unit number of the disk to which you
want to update the software. This disk should be physically
mounted and write-enabled.
Target disk?

<SY:> :

Assigning system logicals

RSTS/E V9.5 Release Notes
Differences Between V9.5 and V9.4
01-Dec-86 09:49 AM
01-Dec-86 09:49 AM
please mount the MAIL Library media and enter the name and unit
number of the device.
Valid device types are:
'MM', 'MS', 'MT',
, MU', , ])M ' 0 r ' DL '
MAIL Library device?

<MMO:> DLO:

The update procedure will complete without user intervention from
this point.
UPDATE. LOG is a log file of this update procedure,
created in your account, and should be checked for possible
update errors.
Disregard multiply defined symbol errors during
the task rebuild phase.
The upd4~te should take between 3 and 4.5 hours, depending on your
CPU and system disk~
Corrections
The following problems have been fixed in this update:
o

Files printed within DECmail-ll with the PRINT FILE command
were deleted after being printed.

Date and time values specified to the /AFTER qualifier were
ignored when sending a message using the /EDIT qualifier, or
if AUTO EDIT was enabled.

The From:
and Subject:
fields get cleared out when sending
a message with /EDIT or AUTO EDIT enabled.

Batch Mail messages having To:
and CC:
lines greater than
255 characters would result in a "?Line too long" error and
abort MAILQ.

Entering PRINT<return> with no current message aborts MAIL
with an "?Arguments don't match" error.

DECmail-ll displays "?Integer error" when sending a message
greater than 64 blocks in length via Message Router.

MAILQ aborts with "?No room for user on device" when it
encounters zero free blocks.
MAILQ will now wait for blocks
to become available before re-attempting the delivery.

Users would sometimes receive multiple copies of the same
mail message when sent via Batch Mail.

RSTS/E V9.S Release Notes
Differences Between V9.S and V9.4
o

Entering "NI" at the Send Menu replaces the CC:
field with
the To:
field contents, if a CC:
line had been entered.

Files having records with trailing carriage returns, such as
RNa and DSR files, do not print correctly when sent to users
on other nodes.

Users intermittently receive messages with an incorrect To:
field when sent via Batch Mail.

DECmail-ll would abort with a Maximum Memory Exceeded error
when attempting to send or FETCH Message Router mail to a
large number of users.

Two errors which caused Batch Mail to send duplicate messages
were corrected.

Mail would not be delivered to a user who had exceeded logged
out quota.

The SELECT keyword was not properly cleared after
unsuccessful SEARCH commands.

2.13.2

DECnet/E

NCP Enhancements
The DECnet/E Network Management Program (NCP.TSK) has been
enhanced to provide more concise information when displaying
CIRCUIT SUMMARY details for Ethernet circuits.
In previous
releases, the command SHOW CIRCUIT UNA-O SUMMARY would display
all known adjacent nodes when the Executor node was a router.
Now, the complete display is only available when issuing the SHOW
CIRCUIT UNA-O STATUS command; on routing nodes, the SHOW CIRCUIT
SUMMARY will only display adjacency information about the routing
nodes that exist on the circuit.

RSTS/E V9.5 Release Notes
Documentation Changes
3

Documentation Changes in RSTS/E V9.S

The documentation for RSTS/E V9.5 consists of these Release
Notes.

3.1

Co:crections

The following documentation errors will be corrected in a future
version of RSTS/E:
o

In the RSTS/E System Directives Manual on page 3-131, the
second paragraph states in part "Unless data passed and
returned show specific values for the XRB, it should be all
zeros."
The following statement will help to clarify how you should
handle FIRQB and XRB:
When using SEND/RECEIVE calls, you must clear both FIRQB and
XRB, even if XRB is not used.

In the RSTS/E Programming Manual on page 9-3, the description
of the confirmation data received in byte 3 for a system call
to PBS is incorrect.
The data returned in byte 3 is
CHR~? (255%) .

In the RSTS/E Programming Manual on page 9-22, the
documentation for the /COPIES field is incorrect.
Byte 1
should be CHR$(131%) not CHR$(13%).

RSTS/E V9.S Release Notes
Known Problems and Restrictions
4

4.1
4.1.1

Known Problems and Restriction£ with RSTS/E v9.S

Recommendations and Restrictions for Extended Cluster-Size
Disks
wasted Space

Extended cluster-size disks are recommended for use when a small
number of large files needs to be placed on a single volume.
These disks are NOT recommended for use as system disks, or as
disks holding large numbers of accounts.
Because the directories
contained on these disks use cluster size 16, and the pack
cluster size is 32 or 64, there will be some wasted space in each
directory. With a pack cluster size of 32, there will be 16
wasted blocks per directory cluster (a maximum of 7*16 = 112
blocks per account); with a pack cluster size of 64, there will
be 48 wasted blocks per directory cluster (a maximum of 7*32 =
224 blocks per account).
If the number of accounts on an
extended cluster-size disk is kept to a minimum, then the
percentage of wasted space will be a very small percentage of
total space available on the disk. As the number of accounts
grow, the actual amount, and percentage amount of wasted space
increases.
For this reason, DIGITAL recommends that these disks
be used for limited numbers of accounts, and for large data
files.

4.1.2

BACKUP strategy

Extended cluster-size disks must be backed up using the BACKUP
program (or the DCL BACKUP command).
SAVRES cannot be used to
save, or make image copies of extended cluster-size disks.

4.2
4.2.1

Installation
Boot from TU10

RSTS/E 9.S cannot be booted from the 'Option:' BOOT command on a
TUID magnetic tape drive.
The tape can be booted on this drive
using a hardware boot ROM.

RSTSjE V9.5 Release Notes
Known Problems and Restrictions
4.2.2

Booting Magnetic Tape

Magnetic tape distributions of RSTSjE or any bootable recovery
tapes of RSTSjE must be booted from unit zero.
This problem
affects MM and MT drives.
This problem will be corrected in a
future release of RSTSjE.

4.2.3

Flag Files

The installation or update of RSTSjE leaves several zero length
flag files (files used by the installation procedure to determine
what parts of the installation have been completed) in various
system accounts after installation.
Deleting any of these files may cause unpredictable results.
particular, deleting the flag file [1,2]VER095.SYS may cause
certain layered product installations and updates to fail.

4.3

DEUNA Ethernet Driver

Under some conditions, it is possible to hang a user job in an XE
state when attempting a transmit command to a DELUA controller
which was initialized successfully during system start up, but
which was subsequently rendered inoperable due to a simple
failure such as cable removal.
The command SET DEVICE
XEO:jDISABLE frees up the job to continue normal processing.
The
DELUA should be disabled until such time as the cabling is
repaired.

4.4
o

Initialization Code (INIT.SYS)
If your installed monitor has a Virtual Disk defined (DV:),
and you START a monitor that has no Virtual Disk defined, and
then START your original monitor containing the Virtual Disk
again, you will get "?Device unavailable" errors when you
attempt to use the Virtual Disk.
The workaround is to use the DEFALT option of INIT.SYS to
remove and then redefine the Virtual Disk for your original
monitor.

RSTS/E V9.5 Release Notes
Known Problems and Restrictions
o

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 MTWC
MTFC
MTCS2 MTDS
MTER
MTTC
144270 000000 001007 000100 154640 102100 102300

The error message you receive may be different. This message
prints as a result of the density autosizing process that
occurs on TMQ2 formatters, and does not represent a true
hardware error.
o

While pattern checking MSCP disks during off-line INIT using
the DSKINT option, an unexpected error message may be
displayed by DSKINT of the form:

o Error
000003
DSKINT will continue to run to completion and the error can
be safely ignored. If your INIT has been booted from a
magnetic tape device, a magtape error showing no errors
occurred might appear instead of the error described above.
As before, the occurrence of this error may be safely
ignored. This problem will be corrected in a future release
of RSTS/E.

4.5
4.5.1

Monitor

DB and DR Disk Drivers

The DB and DR disk drivers may count or log errors for the wrong
disk unit if there is heavy DB/DR disk activity and an attempt is
made to mount a unit that is spun down or off-line.
This problem will corrected in a future release of RSTS/E.

4.5.2

MSCP Disk Driver

On systems having multiple UDA50-A MSCP controllers, a system
crash may result if disk unit numbers are swapped between two
drives on different UDA50-A controllers during timesharing.
The preferred workaround is to only swap drive numbers when
timesharing is not up. The best method is to shut the system

RSTS/E V9.5 Release Notes
Known Problems and Restrictions
down, and swap the unit numbers when the "Start timesharing"
prompt appears. After swapping the unit numbers, reboot the
system disk and restart timesharing.

4.5.3

Virtual Disk as Part of the Public structure

We do not recommend that the Virtual Disk be made part of the
public structure as a read/write disk. When creating a file on
the public structure, the File Processor selects the disk on the
public structure with the most free space.
Data files and
programs will be lost if they are placed on the Virtual Disk and
the system is shut down or crashes. We recommend that if you
plan to use or are currently using the Virtual Disk as part of
the public structure, you mount it as a read-only disk.
This
will prevent files from being created inadvertently on the
Virtual Disk and potentially lost.
NOTE
In a future release, RSTS/E development is
planning to restrict the mounting of the Virtual
Disk to read-only when it is mounted as a public
disk.

4.5.4

TMSCP Tape Driver

If your system contains only one TMSCP tape drive (TU8l or TK50),
it must be set up as unit O.
If you have two drives and unit 0
does not work, you must make the working drive unit 0 and
disconnE~ct the non-working drive.
This restriction will be fixed
in a future release of RSTS/E.
NOTE
The controller number must also match the drive
number.
For example:
Valid
Name

Address Vector Comments

MUO:
MUl:

174500
160504

P350
P354

TU81
TK50

units: O(TU81)
units: 1(TK50)

RSTS/E V9.5 Release Notes
Known Problems and Restricti~ns
Invalid

4.5.5

Name

Address vector Comments

MUO:
MU1:

174500
160504

P350
P354

TU81
TK50

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

Terminal Service

If you have included multi-terminal service support in your
monitor, then the terminal driver will not allow a job to
conditionally sleep if there is any pending output on any slave
terminal.
These checks are done even if the job is currently not
using the multi-terminal service feature.
This has created a
problem with the Print/Batch Services package.
Under certain
circumstances, the Print/Batch Services package will go into a
steady run state, locking out jobs that have a lower priority.
These circumstances are:
1.

A print job has been started for a keyboard server on a
dial-up line that is not connected or has lost carrier.

Another print job starts on another keyboard server.

PBS will enter a steady RUN state until the job finishes on the
second print server, or the dial-up connection is established.
This will be fixed in a future release of RSTS/E.

4.6
4.6.1

Commonly Used System Programs (CUSPs)
ANALYS package

In the monitor dump section of the ANALYS report, the "virtual
disk" area of the Memory Layout is incorrectly shown as "locked
out".
This will be fixed in a future release of RSTS/E.

4.6.2

DSKSEK

The disk exercise utility DSKSEK has not been modified to support
large cluster-size disks.
Therefore, if you have a disk which
has a cluster size greater than 16 you must use the DSKEXR

RSTS/E V9.S Release Notes
Known Problems and Restrictions
utility to exercise the disk.
a future release of RSTS/E.

4.6.3

This restriction will be lifted in

The LOGIN and LOGOUT programs control when to drop the carrier on
a dial-up linee
If you access the system from a captive account
over a dial-up line and the command procedure you are running
aborts abnormally, the carrier will not be dropped.
A workaround
to this problem is to trap all possible errors within the command
procedure and exit by using the LOGOUT command.

4.6.4

ODT.TSK

ODT.TSK will not display addresses greater than 177777(8)
correctly.
It accesses the correct location and displays the
contents of the address correctly.
It is just the display of the
address that is incorrect.

4.6.5

PIP

The following problems have been reported and will remain as
restrictions for V9.5, while they are being investigated for
resolution in a future release:
o

PIP cannot access files that are on a tape created on an RTl1
system.
This problem will be fixed in a future release of
RSTS/E.

There is a restriction using the Open Next directive with PIP
when copying files "into themselves".
If you are copying
files "into themselves" on the system disk initialized as NFL
(New Files Last), and you specify that disk's device name
differently on the input and output side of the command line,
PIP will continue copying files in an endless loop; it will
not properly detect the last file in the directory.
Under
such circumstances, you must type CTRL/C to terminate the
operation.
For example, if your system disk is DUI:
and
you issue the command:
$ PIP _SY:[1,2]=_DU1:[l,2]*.*/LOG

PIP will loop endlessly copying files.

RSTS/E v9.5 Release Notes
Known Problems and Restrictions
To prevent this, do not specify a device name for the system
disk, or, specify the same device name on both the input and
output side of the PIP command line (_SY: = SY:,
_SYO: = _SYO:,
DU1:
_DU1:, etc.).
o

If you try to copy a file with certain attributes to magtape,
PIP encounters a memory management trap and exits.
The
attributes are:
RMS Sequential, fixed length records of 512
bytes, maximum record length 512, records do NOT span blocks.
This will be fixed in a future release.

Prior to V9.5, PIP would not attempt to copy RMS Relative or
RMS Indexed files to magtape because of a known bug in the
code.
The bug has been fixed, and we have lifted this
restriction (see section 2.10.9 of these notes).
However, it
is only valid to copy RMS files TO ANSI MAGTAPE.
PIP will
allow you to copy RMS files to DOS magtape, but if you do,
the files' attributes will be lost, and the files will be
unusable.
In a future release we will implement safeguards
to prevent inadvertent copying of untranslatable RMS files to
DOS magtape.

4.6.6

Supporting Disks with unit Numbers Greater Than 9

The following utilities will not correctly print the disk name
and unit number in error messages, for disks with unit numbers
greater than 9:
LINK.SAV
LIBR.SAV
MACRO.SAV
For example, if the source file TESTOl does not exist on DU15:
$ run $macro
*DU15:TEST01=DU15:TESTOl
?MACRO-F-File not found DVE:TEST01.MAC
DU15:TEST01=DU15:TESTOl
This problem will be fixed in a future release of RSTS/E.

RSTSjE V9.5 Release Notes
Known Problems and Restrictions
4.6.7

Log File Corruption

If the disk on which a DCL or BATCH log file is being written
becomes full, then as space becomes available the resultant log
file may contain one or two ending blocks of random data.

4.6.8

Print/Batch Services (PBS)

PBS will sometimes process pending entries after the queue
manager has received the message telling it to shut down.
The
problem is related to the number of active servers assigned to
the active queue when the shutdown message is received.
This
will be corrected in a future release of RSTSjE.

4.7

RSX and RMS Tasks

Typically you are allowed to omit one or both of the PPN
(project,programmer number) fields when specifying a file or
account.
You are also able to use logical names longer than 6
characters, and logical names containing dollar signs.
The
following is a list of RSX and RMS tasks which do NOT allow you
to specify one or more of these features.
Task
Name
-------

TKB
MAC
PAT
LBR

Handles Logical
names longer than
6 characters

-----------------

RMSDEF
RMSDSP

Handles Logical
names containing
dollar ( $ ) signs

Handles omitted
field(s) in PPN

----------------

---------------

YES
YES
Cannot Handle
Cannot Handle

YES
YES
YES
YES

Cannot
Cannot
Cannot
Cannot

Handle
Handle
Handle
Handle

YES
YES

Cannot Handle
Cannot Handle

4.8

RMS-ll

RMS-ll does not correctly parse an underscored device.
effect is to ignore the underscore.

Remote access to indexed files will not work correctly when a
keyed $GET is attempted with a non-string key and a keysize
of zero.
This is documented as a correct way to pass a

The

RSTS/E V9.5 Release Notes
Known Problems and Restrictions
non-string key and works correctly for local operations.
This problem will be fixed in a future release of RSTS/E.

4.9

Layered Products

4.9.1

DECmai1-11 v3.0

The following restrictions apply to DECmail-ll V3.0 on RSTS/E
V9.5:
o

Sending a message via combined MROUTER and MRGATE pathways is
not valid.
For example, To:
MROUTER::MRGATE::FAGEN or To:
MRGATE::MROUTER::BECKER.
The workaround is to choose one method of delivery or the
other (Message Router or normal DECmail-ll).
If the addressee is an ALL-IN-l user, send the message to
node::Al::username.
If the addressee is a VAX DECmail user, send to
node::DECMAIL::name.
If you wish to send a message to another DECmail- 11 user
via Message Router, send to node::MROUTER::username.
Otherwise, let DECmail-ll handle the delivery by not
using any alternate delivery mode keywords (MRGATE,
MROUTER, DECMAIL, or AI) in the address.

SET TERM/WIDTH=132 does not set the terminal hardware to wide
screen mode.
It only sets the software column count that
determines where to wrap the header fields when reading a
message.

RSTS/E V9.5 Release Notes
Known Problems and Restrictions
4.9.2

DECnet/E

The NCP command to SET EXECUTOR SEGMENT BUFFER SIZE <n>does
not work when the EXECUTOR STATE: is ON.
The command should
fail with an appropriate error, but instead it appears to
succeed without taking any action.
This will be corrected in
a future release of RSTS/E.

When attempting to issue a command such as SHOW NODE <number>
COUNTERS and the node <number> isn't in your volatile
database, NCP will report that the node does not exist, even
though you may have an active link to it.
The workaround is
to ensure that all of the nodes you normally access are
defined in your volatile parameter file.
This will be
corrected in a future release of RSTS/E.

DECnet/E will not successfully create a network parameter
file for networks of greater than twenty-six thousand nodes.
In order to successfully create a node database (NETPRM.SYS),
you must specify a Maximum Nodes value smaller than 26,000.
This is a restriction to the current release of DECnet/E and
may be lifted in any future release or update.

When you SET HOST from RSTS/E to some versions of VMS,
1099in9 off the VMS system may cause the following message to
display:
%Logical link failure to remote node xxxxxx
NSF reason code = 0
Control returned to node xxxxxx
This error message is triggered by the receipt of an
unexpected message from the VMS node during disconnect. When
the message displays, no actual error has occurred and the
user session is not otherwise affected.

NFT and FAL
o

NFT and FAL do not preserve correct protection codes when
creating files.
Protection codes for the output file are
computed by adding together the default system protection
code and the codes for executable (64.), sensitive (128.), or
executable and privileged (64.+128.) as set on the input
file.

RSTS/E V9.5 Release Notes
Known Problems and Restrictions
o

NFT and FAL do not correctly report the size of extremely
large files in directory operations. Where the value exceeds
65565, it requires more than 16 bits to be represented. The
extra bits are ignored, therefore, the value is
misrepresented. This will be fixed in a future release of
RSTS/E.

NFT does not correctly handle the block mode switch during a
wildcard copy operation. The effect is that the switch is
ignored after the first copy is performed. This will be
fixed in a future release of RSTS/E.

t-IOW TO ORDER ADDITIONAL DOCUMENTATION
DIRECT TELEPHONE ORDERS
In Continental USA
and Puerto Rico
call 800-258-171 0

In Canada
call 800-267-6215

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

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

DIRECT MAIL ORDERS (Canada)
DIGITAL EQUIPMENT OF CANADA LTD.
100 Herzberg Road
P.O. Box 13000,
Kanata, Ontario, Canada K2K 2A6
Attn: DECDIRECT OPERATIONS

ELECTRONIC ORDERING
Dial BOO-DEC-DEMO with any VT100 or VT200
compatible terminal and a 1200/2400 baud modem.
If you need assistance, call BOO-DEC-INFO.

INTERNATIONAL
DIGITAL EQUIPMENT CORPORATION
P&SG Business Manager
c/o Digital's local subsidiary
or approved distributor

Iinternal orders should be placed through the Software Distribution Center (SOC),
Digital Equipment Corporation, Westminster, Massachusetts 01473-0471
* Any prepaid order from P~erto Rico must be placed

with the Local Digital Subsidiary:
809-754-7575

Fleader's Comments

RSTS/E
Release Notes
AA-KW28A-TC

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

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

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

I would like to see morelless

Wbat I like best about this manual is

Wbat 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 lam using Version _ _ _ of the software this manual describes.

NamefI'itle
Company

Dept.
Date

Mailing Address
Phone ._________________

t
I
I

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

111111

No Postage
Necessary
If MaIled In the
UnIted S~ates

BUSINESS REF-L Y MAIL
FIRST CLASS PERMIT NO 33 MAYNARD MASS
POSTAGE WILL BE PAID BY ADDRESSEE

ATTN: Office Systems Documentation MK01-2/E02
DIGITAL EQUIPMENT CORPORATION
Continental Boulevard
Merrimack N. H. 03054

111 ••••• 11.11 •••• 1.1 •• 1•• 11.1 •• 1.1 •• 1.1 •••• 11.11.1 •• 1
- - - - - -Do Not Tear· Fold Here and Tape - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -, - - - - -