Digital PDFs

AD-FD06A-B7

April 1986

239 pages

Original

8.5MB

Document:	The Software Dispatch RSX RSX-11M/S RSX-11M-PLUS Micro/RSX April 1986
Order Number:	AD-FD06A-B7
Revision:	0
Pages:	239
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/Software_Dispatch/RSX_Software_Dispatch_198604.pdf

OCR Text

RSX
RSX-11M/ S
RSX-11 M-PLUS
Micro/ RSX
April 1986

A -

The Software Dispatch
RSX

RSX-11M/S
RSX-11 M-PLUS
Micro/RSX
April 1986
AD-FD06A-B7

•

'
,.

~n~nomn

ware

RSX SOFTWARE DISPATCH
Published by
Corporate Administrative Systems Group, Software Services
Dlgltal Equipment Corporation
129 Parker St. (PK02/E49)
Maynard, MA 01754
The RSX Software Dispatch complements the Software Dispatch Reviews for RSX-11 M/S, RSX11 M-PLUS and Micro/RSX. New and revised Software Product Descriptions, programming notes,
software problems and solutions, and documentation corrections are published here. Much of the
material is developed from Software Performance Report (SPR) answers significant to the general
audience and is printed here to supplement the maintenance notebook (established by the Software Dispatch Review).

..
•

PRODUCTS SUPPORTED In the RSX SOFTWARE DISPATCH
BASIC-PLUS-2
COBOL, PDP-11
COBOL-81/RSX
CORAL 66, PDP-11
DATATRIEVE-11
DBMS-11
DECnet-11M
DECnet-11M-PLUS
DECnet-11S
DECnet/SNA Gateway Products
DPM
DPM-PLUS Software
DT07-11M

FMS-11/RSX
FORTRAN IV/VAX to RSX
FORTRAN-77/RSX, PDP-11
FORTRAN-77 DEBUG, PDP-11
LSP-11
MUX200/RSX-IAS
PASCAL/RSX, PDP-11
RGL/11
RPG II, PDP-11
RSX MDE/T-11
RSX-11M
RSX-11S
RSX-11 M-PLUS

RSX-11/3271 Protocol Emulator
RSX-11M 2780/3780 Emulator
RSX-11 M/FORTRAN Enhancement
Pkg. for MINC
RSX-11M/FORTRAN Real-Time Pkg.
for MINC
RSX-11M/SNA Protocol Emulator
RTEM-11
SORT-11
SSP-11
UN1004/RSX

DISTRIBUTION
The RSX Software Dispatch is directed to one software contact for each software product. No
mailing will be made to addresses without a software contact name. Address change requests
should be sent to the nearest DIGITAL field office. Include the new address and malling label from
the most recently received publication.
Software binary and sources are provided under licenses only. The standard Terms and Conditions, OEM Agreements, and/or Quantity Discount Agreement contain the licenses for all binaries
other than DECsystem-10.
Barbara Scollan, Editor
Copyright© Digital Equipment Corporation 1986. All Rights Reserved.

The material in this document is for information purposes only. Digital
believes the information in this publication is accurate as of its publication
date: such information is subject to change without notice. Digital is not
responsible for any inadvertent errors. Comments on the contents of this
publication should be directed to your local Digital Field Office.

..
DEC
DEC US

DECnet
DECsystem-1 O
DECSYSTEM-20
DECwriter

The following are trademarks of Digital Equipment Corporation
DIBOL
EDUsystem
IAS
MASS BUS

PDP
PDT
RSTS

RSX
RT
ULTRIX
UNIBUS
VAX
VMS
VT

(

RSX Software Dispatch, April 1986

TABLE or CONTENTS

Sequence No.
PRODUCT AVAILABILITY DATES

RSX-UM V4.1

•

INDIRECT
PROBLEMS WITH LOCAL SYMBOLS IN GLOBAL NAME FORMAT

VMR
UNABLE TO BOOT TRUNCATED RXOl SYSTEM

2 0 2.5 0 2 M

LPP
LPP LOOPS ON NEGATIVE RECORD LENGTH

TltB
TltB

CORRUPTING VIRTUAL MEMORY UNDER RARE CONDITIONS

RMs-u v2.o
10 0 7 0 1 0 3 M

INDEX FILE CORRUPTION IN ALTERNATE KEY PATH

PDP-11 SYMBOLIC DEBUGGER v2.o
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER VERSION 2 0 0

RSX-llM V4 0 l CUMULATIVE INDEX

(
RSX-UM V4.2

•

(

AUTOCONFIGURE
ACF MAY NOT CORRECTLY SET UP DV 0 NUC IN CONFIG 0 DAT FOR RS03/4s

1.1 0 1 0 3 M

IRS
NEW •TASK IMAGE I/O ERROR• MESSAGE FOR DEVICES
SCHEDULING OF SHUFFLER MAY CRASH SYSTEM

2.2.2.1 M
2.2.2.2 M

35
36

INDIRECT
ESCAPE RESPONSE TO .ASKS DEFINES SYMBOL AS LOGICAL
ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES
CORRUPTED BEGIN-END BLOCK POINTERS IN LOCAL SYMBOL TABLE

20 2 0 3 0 9 M
2.2.3.10 M
2 0 2 0 3 0 11 M

37
38
40

CONTROL FILES
ERLRPT-F-MODLOASYM UNDEFINED SYMBOL IN MODULE TO BE LOADED

3.3.s.s M

•

Sequence No.

Page

LPP LOOPS ON NEGATIVE RECORD LENGTH

40 10 5 0 1 M

PIP
DELETING PILES, JO DOES NOT ALWAYS WORK PROPERLY

5.1.12 0 1 M

BRO
POTENTIAL PROBLEM WHEN FIRST PILE RESTORED IS CONTIGUOUS

5 0 1 0 17 0 11 M

TASK BUILDER
TKB SWITCH /CL DOES NOT WORK
MULTIPLE REFERENCES TO 0 PSECT IN SEGMENT CAUSE TKB TO ABORT

5.3.0.1 M
5.3.0.2 M

49
50

TASK WITH LARGE NUMBER OP LUNs HANGS IN ODT

5.5.1.1 M

HELP
HELP /OUT:TTNN: <PARAMETER> DOES NOT WORK

5 0 7 0 10 1 N

DCL
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @PILESPEC• DOES NOT WORK

6.1.0.5 M
6.1.0.6 M

55
56

LPP

•

ODT

PDP-11 SYMBOLIC DEBUGGER v2.o
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER VERSION 2.0

RSX-llM V4.2 CUMULATIVE INDEX

61
RSX-118 V4 0 l

VMR
UNABLE TO BOOT TRUNCATED RXOl SYSTEM

RSX-llS V4 0 l CUMULATIVE INDEX

RSX-US V4 0 2
11SGEN2
11SGEN2 PROBLEMS

RSX-llS V4 0 2 CUMULATIVE INDEX

RSX-11M-PLUS V2 0 l
INDIRECT
PROBLEMS WITH LOCAL SYMBOLS IN GLOBAL NAME FORMAT

(

Sequence No.
VllR

•

SET /NOTYPEAHEAD CAUSES CRASH

SAV
SAV CRASHES WHEN SYSTEM DISK IS A DUAL-ACCESS DEVICE

LPP
LPP LOOPS ON NEGATIVE RECORD LENGTH

4.1.5.6 M

TKB CORRUPTING VIRTUAL MEMORY UNDER RARE CONDITIONS

RllS-11 V2. 0
INDEX FILE CORRUPTION IN ALTERNATE KEY PATH

PDP-11 SYMBOLIC DEBUGGER v2.o

ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER VERSION 2.0

RSX-llM-PLUS V2.1 CUMULATIVE INDEX

RSX-llM-PLUS V3.0
SYSGEN
AUTOCONFIGURE DOES NOT PASS MULTIPLE T(MSCP) INFO TO SYSGEN

1.1.0 0 1 M

111

AUTOCONFIGURE
ACF MAY NOT CORRECTLY SET UP DV.NUC IN CONFIG.DAT FOR RS03/4s

1.1.1 0 1 M

113

DIRECTIVES
GSSW$ CRASHES SYSTEMS WITH NO SWITCH REGISTER

20 1 0 1 0 2 R

115

LOADR
DRIVER WITH A CLOCK BLOCK IN THE CTB CRASHES THE SYSTEM

20 10 5 0 1 M

117

•

INTERNAL CMOS
ASN COMMANDS WITH NULL LOGICALS CAUSE SYSTEM CRASH

2.2.1 0 2 M

119

•

INS
NEW •TASK IMAGE I/O ERROR• MESSAGE FOR DEVICES

20 20 20 1 M

121

ICP
.ASK DOES NOT WORK AS DOCUMENTED WITH <ESC> RESPONSE

2 0 2 0 3 0 10 M

123

(

Sequence No.

Pape

INDIRECT
ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES
CORRUPTED BEGIN-END BLOCK POINTERS IN LOCAL SYMBOL TABLE

2.2.3.11 M
2.2.3.12 M

124
126

SAV
SAV DOES NOT SIZE MEMORY CORRECTLY ON UNIBUS SYSTEMS
SAV CRASHES WHEN SYSTEM DISK IS A DUAL-ACCESS DEVICE

2.2.6.3 M
2.2.6.4 M

127
128

BPR
BPR GIVES CRYPTIC ERROR MESSAGE WHEN FILE IS DELETED

4.1.1.1 M

129

LPP
LPP LOOPS ON NEGATIVE RECORD LENGTH

4.1 0 5.1 M

131

BRO
BRO ON SYSTEMS WITHOUT ACCOUNTING: GARBAGE IN USER NAME

4.2 0 2.1 N

133

PIP
DELETING FILE, JO DOES NOT ALWAYS WORK PROPERLY

5.1.12.1 M

135

BRU
BRU--MISLEADING ERROR MESSAGE/ACTION FOR UNMOUNTED TAPES

5.1 0 17.10 N

137

TASK BUILDER
TKB SWITCH /CL DOES NOT WORK
MULTIPLE REFERENCES TO .PSECT IN SEGMENT CAUSE TKB TO ABORT

5.3.0.1 M
5.3.0.2 M

139
140

OD'!'
TASK WITH LARGE NUMBER OF LUNs HANGS IN OD'!'

5.s.1.1 M

141

HELP
HELP /OUT1TTNN: <PARAMETER> DOES NOT WORK

5.7.1 0 1 N

143

PllD/SNAP
PMD SNAPSHOT FOR I/D SHNAPSBOT DUMPS I-SPACE AND NOT D-SPACE

5.7.3 0 1 M

145

DCL
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @FILESPEC• DOES NOT WORK

6.1.0.2 M
6.1.0.3 M

147
148

•
PDP-11 SYMBOLIC DEBUGGER v2.o
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER VERSION 2.0
RSX-11M-PLUS V3 0 0 CUMULATIVE INDEX

17.1 0 1.1 N

149
153

•

Sequence No.

Micro/RSX Vt. O
llicro/RSX v1.o COllULATIVE INDEX

159

llicro/RSX V3. O

•
•

(

INTERNAL CllDS
ASN COMMANDS WITH NULL LOGICALS CAUSE SYSTBM CRASH

2.2.1.1 M

163

INS
NEW •TASK IMAGE I/O ERROR• MESSAGE FOR DEVICES

2.2.2.1 M

165

INDIRECT
ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES
CORRUPTED BEGIN-BND BLOCK POINTERS IN LOCAL SYMBOL TABLB

2.2 0 3.8 M
2.2.3.9 M

167
169

BPR
BPR GIVES CRYPTIC BRROR MESSAGE WHBN FILE IS DBLBTED

4.1.1 0 1 M

171

LPP
LPP LOOPS ON NEGATIVE RECORD LENGTH

40 1 0 5 0 1 M

173

TASJC BUILDER
MULTIPLE REFERENCES TO .PSECT IN SEGMENT CAUSE TKB TO ABORT
TKB SWITCH /CL DOBS NOT WORK

50 30 00 1 M
5.3.0.2 M

175
176

DCL
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @FILESPEC• DOES NOT WORK

6.1.0.2 M
6.1.0.3 M

177
178

Micro/RSX V3.0 CUMULATIVE INDEX

179

SOFTWARE PRODUCT DESCRIPTIONS (SPDa)
SOFTWARE PERFORMANCE REPORT (SPR) SUBMISSIONS
SUGGESTIONS FOR SUBMITTING TAPES WITH SPRa
SOFTWARE PROBLEMS OR ENHANCEMENTS
DIGITAL SOFTWARE LICENSING
DIGITAL EQUIPMENT COMPUTER USERS SOCIETY (DECUS)

183
219
220
221
223
225

•

PRODUCT AVAILABILITY DATES - RSX

APRIL 1986

The following list contains date and version of the latest release of
supported software products. Customers who are in warranty or have a
software product service agreement during the month the product became
available, are eligible to receive the new release. Eligible customers
who have not received the new release should contact their local
DIGITAL office.

PRODUCT

(

BASIC-PLUS-2 for RSX-llM
and RSX-llM-PLUS,PDP-11
COBOL,PDP-11
COBOL-81/RSX
DATATRIEVE-11
DBMS-11
DECdx/RSX
DECmail-11 for RSX-llM-PLUS
and Micro/RSX
DECnet Router Server
DECnet-UM
DECnet-llM-PLUS
DECnet-US
DECnet/SNA Gateway Products
DPM
DPM-PLUS SOFTWARE
FORTRAN IV/RSX
FORTRAN-77 DEBUG/RSX,PDP-11
FORTRAN-77/RSX,PDP-ll
LSP-ll
MicroPower/Pascal-RSX
PASCAL/RSX,PDP-11
RGL/11
RPG II, PDP- ll
RSX MDE/T-11
RSX-11 2780/3780 Emulator
RSX-11 PSI/M
RSX-11 PSI/M-PLUS
RSX-11/3271 Protocol
Emulator
RSX-1 lM
RSX-llM V4.l UPDATE
RSX-llM/FORTRAN Enhancement
Pkg. for MING
RSX-UM/FORTRAN Real-Time
Pkg. for MING

VERSION

AVAILABLE

2.3
4.4
2.3 SPD ONLY
3 .1
2.1
1.0
2.0

JUN 85
MAY 82
NOV 85
SEP 84
JAN 83
NOV 84
AUG 84

1. 1 SPD ONLY
4.0
2.0
4.0
1. 2
4.1
1. 1
2.6
1.0
5.0 SPD ONLY
1. 2 DOC ONLY
2.0
1.2
1.1 DOC ONLY
8.8
1.0
4.1
2.0
2.0
3.0

OCT 85
MAR 84
MAR 84
MAR 84
JAN 85
AUG 82
AUG 82
JUN 83
OCT 83
JAN 86
JAN 86
AUG 85
JAN 86
JAN 86
JUL 83
DEC 82
JUL 82
MAR 84
MAR 84
JAN 83

4.2
A
1. 3

JAN 86
JAN 86
JAN 86

1. 2

JAN 86

PRODUCT AVAILABILITY DATES - RSX (cont'd)

PRODUCT
RSX-1 lM-PLUS
RSX-llM-PLUS DECgraph-11
RSX-llM-PLUS DECtype
RSX-llM-PLUS DIBOL
RSX-llM-PLUS V2.l UPDATE
RSX-llS
RSX-llS V4.l UPDATE
RTEM-11
SORT/MERGE,PDP-11
SPM-llM
SPM-llM-PLUS
SSP-11

VERSION
3.0
1.2
3.0
1.1
A
4.2
A
2.0
3.0
2.1
2.1
1.3 DOC ONLY

AVAILABLE
JAN 86
NOV 84
FEB 84
NOV 84
JAN 86
JAN 86
JAN 86
MAR 84
JUN 84
JUL 84
JUL 84
JAN 86

•

...

RSX-11M V4.1

•

RSX Software Dispatch, April 1986

RSX- llM V4 .1
MCR
INDIRECT
•

Seq. No. 2.2.3.15 M
1 of 2

*Supersedes RSX-llM V4.l November 1985 Software Dispatch Seq. No. 2.2.3.15 M*
PROBLEMS WITH LOCAL SYMBOLS IN GLOBAL NAME FORMAT
PROBLEM
STATEMENT:

(

The Indirect Command Processor allows definitions of global and local symbols
with the same name to exist on the same level. Also, it allows the individual
deletion of local symbols when they assume the global naming convention. This
is contradictory to the documentation.
The following command files demonstrate the problem:
A.CMD

.SETS $A "Howdie"
.SETS $B "Doodie"
@A2
.IFNDF $A .STOP
.IF $B NE 2 .STOP
.ERASE SYMBOL $B
.IF $B NE "Doodle" .STOP
.ERASE SYMBOL $B
.EXIT

local symbol $A
local symbol $B
ensure we are back on the correct level
this $B is global from A2.CMD
erases $B from global table
this $B is local from A.CMD
erases $B from local table

A2.CMD
.ENABLE GLOBAL
.SETN $B 2
.EXIT

enable global symbol processing
global symbol $B

RESPONSE:

(

The Indirect Command Processor and the documentation are consistent in
allowing global and local symbols with the same name to exist on the same
level. Using local symbol names beginning with the dollar sign ($) is not
recommended because of potential confusion with global symbols but is
permitted by Indirect. If global and local symbols with the same name exist
at a level, and reference is made to that symbol name, the global symbol takes
precedence over the local one for assignments, comparisons, etc.
3

RSX Software Dispatch, April 1986

Seq. No. 2.2.3.15 M

RSX-llM V4.l
MCR
INDIRECT

2 of 2

•
The implementation of Indirect does allow the .ERASE SYMBOL to affect local
symbols if their name begins with the dollar sign, contrary to the documented
restriction that only
global
symbols
may
be
individually
erased.
Investigation of this problem shows that the restriction can be removed
without adverse impact.
Its removal would also eliminate the apparent
advantages of naming local symbols with dollar signs.
RSX-llM Version 4.2 Update C will include a change which removes this
restriction. Specifically, the .ERASE SYMBOL directive will be able to erase
individual global or local symbols. If two symbols with the same name, one
global and one local, exist for the level on which the .ERASE SYMBOL is being
executed, the global symbol will take precedence and be erased.

l
4

(

RSX Software Dispatch, April 1986

RSX-llM V4.1
MCR

Seq. No. 2.2.s.2 M

VMR

1 of 1

UNABLE TO BOOT TRUNCATED RXOl SYSTEM (SPR 11-81002 RC)
PROBLEM
STATEMENT:
Saving a system image file of 494 blocks or greater on
unusable system.

RXOl

produces

RESPONSE:
This problem is caused because of a discrepancy between the code to truncate a
system saved on an RXOl and the RXOl bootstrap driver. The bootstrap for an
RXOl attempts to read a block and then checks to see if it is beyond the end
of the system image.
This causes a problem when the entire disk is used,
since there is no extra block to mark the end of the system image.
In this
case, the controller is forced to attempt to read a block beyond the end of
the disk, causing the bootstrap to hang.
The workaround is to restrict your system to 492 blocks or less.
This problem is corrected in RSX-llM/S Version 4.2 Update C.

(
5

•·

RSX Software Dispatch, April 1986

RSX-llM V4.l
BATCH/QUEUE MGR
LPP

Seq. No. 4.1.5.6 M
1 of 1

•
LPP LOOPS ON NEGATIVE RECORD LENGTH (SPR 11-78038 RDH)
PROBLEM
STATEMENT:

(

LPP loops when printing a file containing a
length.

record

with

negative

record

RESPONSE:
PRT issues a GET$S directive to read each record from the file being
Two types of invalid record length may result from this operation:
1.

Actual record length exceeds limit established
specified in F.URBD

for

the

printed.

device

and

In this case, File Control Services (FCS) transfers as many bytes as
will fit in the user buffer and returns the error code IE.REG. FCS
updates F.RCNM to point at the next record.
2.

Actual record length is negative.
FCS returns the error code IE.REG. No bytes are transferred to the
user buffer. Also, FCS does not update F.RCNM to the next record,
since it cannot determine its starting point because of the negative
record length.
On receiving the IE.REG error code, PRT assumes that it resulted from
the former case and proceeds to print the truncated record. If the
error had resulted from the latter situation, PRT prints the contents
of the user buffer (the preceding line) and requests the next record,
thereby, looping until the entry is deleted from the queue.

RSX-llM Version 4.2 Update C includes a correction for this problem.
Specifically, PRT will test for negative record length and abort with an error
message if one occurs.

RSX Software Dispatch, April 1986

Seq. No. S.3.1.12 M

RSX-llM V4.l
TASK BUILDER
TKB

1 of 1

TKB CORRUPTING VIRTUAL MEMORY UNDER RARE CONDITIONS (SPR 11-82336 LP)
PROBLEM
STATEMENT:
TKBFSL odd address traps while trying to build the user's task, which links to
FCSFSL.
The task also links to a resident common, and the user observes
certain P-sect is removed from the common, the task will build.

that

when

RESPONSE:

Incorrectly, TKB was treating resident library symbol references as symbol
definitions.
When the symbol was from a supervisor-mode library this bug
would also cause TKB to corrupt virtual memory. However, because of the way
TKB uses virtual memory, this corruption would lead to problems if, and only
if, two events occurred:
1.

The symbol table entry for the supervisor-mode library symbol
reference was allocated to exactly the last seven words of a virtual
memory page.

The number of virtual memory page searches exceeded 64K.

Your task, when built with the FSL version of TKB, just happened to meet these
two very rare conditions, and, thus, TKB failed. The bug which caused this
problem is corrected in RSX-llM Version 4.2 Update c.
Since the slightest change in the virtual-memory requirements of your task
would allow TKB to succeed, your task would build when you removed a P-sect
from the resident common.

(
9

•

(

RSX Software Dispatch, April 1986

Seq. 10.7.1.3 M

RMs-11 v2.o
for RSX-llM V4.1

1 of 6
*Supersedes RSX-llM V4.1 September 1985 Software Dispatch Seq. No. 10.7.1.3 M*

•
INDEX FILE CORRUPTION IN ALTERNATE KEY PATH
PROBLEM:
There is a problem updating INDEX files with variable-length records.
If an attempt is made to update an existing variable-length record, a bad RRV
is created in the alternate key path if the following conditions are true:

The record size is increased.

Either a new alternate key
changed.

As a result of the increased record size, a bucket split occurs. (If
unaware of whether a bucket split occurs, assume that condition 3 is
true.)

introduced

existing

one

If an attempt is now made to GET this record by alternate key, RMS will return
the error ER$RRV (Bad Internal Pointer).

(

SOLUTION:
The patching procedure detailed below corrects the above problem.
In
cases, the files should be reloaded to correct the alternate key path.

all

RESPONSE:
This problem has been fixed and will be released in
meantime, the following procedure will fix the
post-Update E system.

(
11

RSX-llM
problem

In the
V4.2.
on the current

RSX Software Dispatch, April 1986

RMs-11 v2.o
for RSX-llM V4. l

Seq. 10. 7. 1. 3 M
2 of 6

"
NOTE

•

The program prompts with an underscore, so input begins after
that.
In all instances, make a copy of the file being
modified in case a mistake occurs.

1. If RMSRES.TSK (the full function library)
into the user's account and invoke ZAP.
(you)
(you)

ZAP)RMSRES.TSK
113 : 10 10 4 ;Or
=0,674/(CR)

(ZAP)

113:0,000674/ 000054

(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)

(CR)
ll3:0,000676/ 000566
(CR)
ll3:0,000700/ 116446
(CR)
Tl3:0,0001021 000024
(CR)
Tl3 :o ,000104/ 132765

(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(ZAP)
(you)

0, 700/(CR)
113 :o ,ooo 700 I 116446
4 767(CR)
-/(CR)
ll3:0 ,000702/ 000024
6626(CR)
0, 700/(CR)
113:0,000700/ 004767
(CR)
ll3:0,000702/ 006626
113:17636;lr(CR)

is used, copy it from LB:[l,l]

comment: set relocation register for R3IUDR
comment: begin prior to the location to be
patched to confirm that you are in
the correct place
comment: verify that these values are the same
on your system

comment: now specify the patch location

comment: now verify that you succeeded
comment: SUCCESS
comment: set relocation register to start of
patch space. The contents of all
locations
opened at this point
should be ZEROS.

•

(

RSX Software Dispatch, April 1986

RMS-11 V2.0
for RSX-llM V4.l

Seq. 10. 7 .1. 3 M
3 of 6

•

(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)

1,0/(CR)
ll3:1,000000/ 000000
11646<CR)
<CR)
ll3:1,000002/ 000000
116466(CR)
-<CR)
ll3:1,000004/ 000000
24(CR)
-(CR)
ll3: 1,00000 6/ 000000
2(CR)
-<CR)
T13 : 1 ,oooo 10 I 000000
1402(CR)
-(CR)
ll3:1,000012/ 000000

(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)

62716(CR)
-<CR>
ll3:1,000014/ 000000
106(CR)
-<CR)
ll3: 1,000016/ 000000
207(CR)
,O/<CR)

(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)

113:1,000000/ 11646
(CR)
ll3:1,000002/ 116466
(CR)
ll3:1,000004/ 000024
<CR)
T13: 1 ,00000 6/ 00000 2
(CR)
ll3:1,000010/ 001402
(CR)

comment: Start inserting new code at
this point

comment: verify that the new code was
correctly inserted

(
13

RSX Software Dispatch, April 1986

RMs-11 v2.o

Seq. 10 • 7. 1 • 3 M

for RSX-llM V4.l
4 of 6

(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)

113:1,000012/ 062716
(CR)
113:1,000014/ 000106
(CR)
ll3: 1,000016/ 000207

•

comment: exit from ZAP

Now copy the corrected RMSRES.TSK into LB:[l,l] and reinstall it.
NOTE
Tasks built against RMSRES do not have to be rebuilt to
include this correction.
Instead, INStall the corrected
resident library. However, the resident library cannot be
REMoved until all tasks installed against it are removed. It
may be easier to simply reboot.
The standard start-up
procedure can then install it.
Check to ensure that the
libraries are indeed installed via that procedure.
2. If RMSLIB.OLB is used to build RMS disk-overlaid or nonoverlaid tasks:
A. Extract the appropriate module from the object library.
$ LBR R3IUDR.OLD=LB:[l,l]RMSLIB.OLB/EX:R3IUDR
B. Create a file R3IUDR.PAT containing:
.TITLE
• IDENT
.PSECT

R3IUDR
/0222CMA/
R3IUDR,I

$$$

$$$+700
CALL
PATCH
.PSECT PATCH
R$IRP = 24

(

RSX Software Dispatch, April 1986

RMs-11 v2.o

Seq. 10. 7 .1. 3 M

for RSX-llM V4.l
5 of 6

•
•

PATCH:

2$:

MOV
MOVB
BEQ
ADD
RETURN
.END

(SP),-(SP)
R$IRP(R4),2(SP)
2$
#106,(SP)

C. Assemble the patch.
) MAC R3IUDR.PAT
D. Apply the patch using the PAT utility.
) PAT R3IUDR.NEW=R3IUDR.OLD/CS:022614,R3IUDR.OBJ/CS:013501

E. Replace into the library.
) LBR LB:[l,l]RMSLIB.OLB/RP=R3IUDR.NEW
3. If RMSLIB.OLB is
done by the user):

(

used

to build the RMS resident library (this is rarely

A. Extract the appropriate module from the object library.
$ LBR R3IUDL.OLD=LB:[l,l]RMSLIB.OLB/EX:R3IUDL
B. Create a file R3IUDR.PAT containing:
.TITLE
.!DENT
.PSECT

R3IUDL
/0222CMA/
R3IUDR,I

$$$ =

• = $$$+700

(

CALL
PATCH
.PSECT PATCH
R$IRP = 24

RSX Software Dispatch, April 1986

RMs-11 v2.o

Seq • 10 • 7. 1 • 3 M

for RSX-llM V4.1
6 of 6

PATCH:

2$:

MOV
MOVB

(SP),-(SP)
R$IRP(R4) ,2(SP)

BEQ
ADD
RETURN
.END

2$
1110 6, (SP)

•

c. Assemble the patch.
) MAC R3IUDL.PAT
D. Apply the patch using the PAT utiiity.
) PAT R3IUDL.NEW=R3IUDL.OLD/CS:025534,R3IUDL.OBJ/CS:013473
E. Replace into the library.
) LBR LB:[l,l]RMSLIB.OLB/RP/-EP=R3IUDL.NEW
Rebuild any applications that are not built against RMSRES.

(

RSX Software Dispatch, April 1986

Seq. 17.1.1.1 N

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM V4.l

1 of 3

ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER VERSION 2.0
PRODUCT DESCRIPTION
Introduction
The PDP-11 Symbolic Debugger Version 2.0 is designed to help users find logic
and programming errors in successfully compiled and linked programs that do
not run correctly. Version 2.0, an extension of PDP-11 FORTRAN-77 DEBUG
Version
1.0, includes support for FORTRAN-77, COBOL-81, and MACR0-11.
Capabilities have also been added to PDP-11 FORTRAN-77 DEBUG Version 1.0 to
make it more powerful. Support is provided for debugging tasks built with land D-space, on systems where both the hardware and operating system support
this feature, for example, RSTS/E V9.0 or higher, RSX-llM-PLUS V2.l or higher,
Micro/RSTS V2.0, and Micro/RSX V3.0.

The debugger is designed as two tasks, a kernel and a background task.
The
kernel is linked in with user programs. The kernel is either overlaid to
occupy less than 4 kilobytes (KB) of user program space, or nonoverlaid to
occupy about 5 KB. The default is an overlaid debugger kernel which can be
used with all user programs (overlaid, cotrees, resident libraries, etc.),
except those user programs that do manual overlay loading. The kernel
communicates with the larger background task, which provides the debugger's
main functionality.
Operating Systems/Installation
The debugger runs on the following versions of DIGITAL's operating systems:
o

VAX-11 RSX Version 2.0 or higher

RSX-llM Version 4.1 or higher

RSX-llM-PLUS Version 2.1 or higher

Professional Host Tool Kit Version 2.0 or
Version 2.0 or higher

RSTS/E Version 9.2 or higher

(

higher

and

PRO/Tool

Kit

RSX Software Dispatch, April 1986

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM V4.l

Seq • 17 • 1 • 1 • 1 N
2 of 3

Micro/RSX Version 3.0 or higher

Micro/RSTS Version 2.0 or higher

On each supported operating system, the debugger is installed using an
automatic installation procedure.
Installation will vary from system to
system. The PDP-11 Symbolic Debugger Version 2.0 on VAX/VMS, Micro/RSX,
Professional
Host
Tool Kit/VMS, RSTS/E, and Micro/RSTS use operating
system-supplied installation procedures. The PDP-11 Symbolic Debugger Version
2.0 on RSX-llM/M-PLUS, P/OS, and Professional Host Tool Kit/RSX use an
installation procedure supplied with the kit.
Documentation
The debugger documentation set has been completely revised.
of the new manuals.

Below is

PDP-11 Symbolic Debugger User's Guide

PDP-11 Symbolic Debugger Installation Guide

PDP-11 Symbolic Debugger Quick Reference

PDP-11 Symbolic Debugger Information for FORTRAN-77 Users

PDP-11 Symbolic Debugger Information for COBOL-81 Users

PDP-11 Symbolic Debugger Information for MACR0-11 Users

list

Availability
The PDP-11 Symbolic Debugger Version 2.0 was expected to be available from the
Software Distribution Center (SDC) in March.
RELEASE NOTES
The Release Notes for the PDP-11 Symbolic Debugger Version 2.0 are distributed
on line as part of the kit. These Release Notes describe known problems and
restrictions in the PDP-11 Symbolic Debugger Version 2.0. Workarounds for the
problems have been provided, whenever possible, to lessen their impact.

(

RSX Software Dispatch, April 1986

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM V4.1

Seq. 17.1.1.1 N
3 of 3

Accessing the On-Line Release Notes
The Installation Guide contains procedures for obtaining copies of the on-line
Release Notes.
The following paragraphs contain the correct commands and
procedures to obtain the on-line Release Notes.
In the Installation Guide, page 5-3, "Installation on the Professional,"
PIP and FLX commands given to copy the Release Notes are incorrect.
correct commands are:

the
The

FOR DISK USERS
) BRU/NOI/UFD/NEW/MOU indev:[l,5]DBGREL.DOC outdev:
FOR TAPE USERS
) BRU/BAC:DBGREL/REW/NOI/UFD/NEW indev:

outdev:

Replace indev with the device on which your distribution medium is allocated
and mounted, replace outdev with the destination device. The Release Notes
are copied to [1,5] and named DBGREL.DOC.

(
19

(
RSX-11M V4.1
CUMULATIVE INDEX
APRIL 1986
This is a complete listing of all articles for RSX-11M V4.1 and layered products. Missing sequence
numbers may pertain to problems unique to other versions of the same product or other major operating
systems.
IMPORTANT I
unassigned articles are indicated:

UNASSIGNED.

Flags are currently being installed for all articles.

The flags and definitions are as follows.

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

Optional Feature Patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the 1duration of the current
release and will be incorporated with any future release, unless otherwise stated.

R = Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as part
of the normal release cycle.
N = Note. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.
sequence

Mon/Yr

SYSGEN
SYSGEN
SYSTEM GENERATION COMMAND FILE CHANGES FOR UPDATE C

1.1.0.1 M

Jun 84

COMMAND FILES
SYSGEN SETS UP INCORRECT CONTROL FUNCTION BITS FOR CO:
SGNKLAB EXITS WITH UNDEFINED SYMBOL ERRORS
TWO LOADABLE IPS CAUSE UNDEFINED SYMBOLS IN EXEC
SYSGEN PHASE 1 ASKS QUESTIONS THAT SHOULD NOT BE ASKED
RSX-llM SYSGEN SUPPORT FOR UPDATE D
AUTOCONFIGURE HANGS ON 128KW SYSTEMS

1.1.1.1 F
1.1.1.2 M
1.1.1.3 M
1.1.1.4 R
1.1.1.s M
1.1.1.6 N

oec 83
oec 83
Mar 84
Mar 84
Jun 84
Jun 84

UPDATE
COMPRSLIB.CMD CANNOT BE FOUND DURING UPDATE

1.1.3.1 M

Mar 85

Component

c
,

RSX-11M V4.1

(
21

COllponent

sequence

Mon/Yr

EXECUTIVE
MISC ROUTINES
22-BIT SYS RUNNING WITH 128KW MEMORY CRASHES ON VIRGIN BOOT

2.1.6.1 M

NOV 83

MCR
MCR
ALLOW • • r • COMMENTS AFTER •ENABLE DATA TO BE PASSED
DCL HELP COMMAND PASSES COMMENT STRING TO MCR

2.2.0.1 M
2.2.0.2 N

Aug 84
Jul 85

.
...

INTERNAL CMDS
ASN PPNN:• DOES NOT GIVE SYNTAX ERROR
SET /HOLD DOES NOT WORK ON VT100 TERMINAL
SCHEDULING OF SHUFFLER MAY CRASH SYSTEM

2.2.1.1 M
2.2.1.2 N
2.2.2.1 M

Jun 85
Dec 85
Mar 86

INDIRECT
INDIRECT GIVES INVERTED OUTCOME OF .IFLOA OR .IFNLOA
SEVERAL PROBLEMS WITH INDIRECT
DUDRV MCR UNLOAD SHOULD NOT BE DONE
.TESTFILE DOES NOT WORK ON A MODULE WITHIN A LIBRARY
INDIRECT MAY CONFUSE IDENTICAL LABELS
MULTIPLE PARAMETERS TO .ENABLE /.DISABLE
ALLOW•,• COMMENTS ON .SETO AND .SETO
.CHAIN LOSES CONTEXT
F.FFBY FIELD OF <FILATR> LIST SHOULD BE A WORD
FINAL DELIMITER NOT INCLUDED IN LAST SYMBOL
<FILSPC> IS SOMETIMES CORRUPTED
ICP FORMAT CONTROL RIGHT/LEFT JUSTIFY DOESN'T WORK
RESTRICTION ON .TEST WITH LOWERCASE CHARACTERS
INVALID CHARACTERS IN SUBSTITUTION SYMBOL NAMES
PROBLEMS WITH LOCAL SYMBOLS IN GLOBAL NAME FORMAT
.EXIT DIRECTIVE WITHIN BEGIN-END BLOCK
INDIRECT COMMAND .SETT <ERSEEN> LEAVES IT FALSE
24-HOUR MAXIMUM FOR .DELAY DIRECTIVE
DEFAULT RADIX FOR INDIRECT SUBSTITUTION FORMAT CONTROL

2.2.3.1 M
2.2.3.2 M
2.2.3.3 R
2.2.3.4 M
2.2.3.5 R
2.2.3.6 M
2.2.3.7 M
2.2.3.8 M
2.2.3.9 M
2.2.3.10 M
2.2.3.11 M
2.2.3.12 N
2.2.3.13 R
2.2.3.14 M
2.2.3.15 M
2.2.3.16 M
2.2.3.17 M
2.2.3.18 M
2.2.3.19 M

NOV 83
Mar 84
Apr 84
Apr 84
Apr 84
JUn 84
Jul 84
JUl 84
Aug 84
Aug 84
Mar 85
Mar 85
oct 85
NOV 85*
Apr 86
NOV 85*
NOV 85*
Jan 86
Feb 86

2.2.5.1 M
2.2.s.2 M

Aug 85
Apr 86

2.2.6.l N
2.2.6.2 M
2.2.6.3 N

Mar 84
JUn 85
JUl 85

UHL
UNLOADING A DRIVER MAY CRASH THE SYSTEM

2.2.7.1 M

Jan 84

DRIVERS
DRDRV, DUDRV, DYDRV
BUG IN DRDRV ECC CODE
DU DRIVER INHIBITS TERMINAL TIMEOUTS
PROBLEMS WITH DUDRV
RX02 SUPPORT FOR 22 BIT OBUS SYSTEMS

3.1.1.2 M
3.1.1.3 M
3.1.1.4 M
3.1.1.5 M

Dec

VMR
VMR DOES NOT HANDLE DEVICES ON A VAXcluster CORRECTLY
UNABLE TO BOOT TRUNCATED RX01 SYSTEM
BOO
BOOT HANGS ON COPY OF A SYSTEM SAVED ON DIFFERENT CONTROLLER
PDP-11/44 RUNS SLOWER AFTER SYSTEM IS SAVED
SOFTWARE BOOT MAY GIVE INCORRECT MEMORY SIZE

83
Dec 83
Dec 83
Jan 84

Oollponent

sequence

Mon/Yr

SUPPORT FOR DOUBLE SIDED FLOPPY
ON MULTIPLE FORKS7 DO NOT ALWAYS BUFFER DATA INTO DYCOM
TEMP GETS MULTIPLY DEFINED WITH TWO CONTROLLERS
RSX SLOWS DOWN ON Micro/PDP-11

3.1.1.6 N
3.1.1.7 M
3.1.1.8 M
3.1.1.9 M

Mar 84
Apr 84
oec 84
Jul 85

FDX-TTDRV
SLAVED TERMINAL DIFFERENCE IN NEW RELEASE
REMOTE LINE HANGS UP WHILE CHANGING CHARACTERISTICS
CRDRV READ CHECK ERROR SENDS BAD CARD TO USER
TC.EPA AND TC.PAR CANNOT BE SET FOR DHll
ABORTING DHVll CURRENT OUTPUT DISABLES TERMINAL I/O

3.1.3.1 F
3.1.3.2 M
3.1.3.3 R
3.1.3.4 M
3.1.3.5 M

oec 83

FIX RCL, MOVE LABEL, ADD DOCUMENTATION
PATCH HB034 CAUSES SYSTEM CRASHES

3.1.4.1 M
3.1.4.2 M

Mar 84
Mar 84

XODRV
XODRV CRASHES SYSTEM IF CANCEL I/O IS USED WITH READ

3.1.5.1 M

Jun 85

CODRV
CONSOLE DRIVER MAY CRASH SYSTEM DURING LOW POOL CONDITIONS

3.1.6.1 M

Mar 84

FCS .EXTND AND TRUNCATION

3.2.1.1 N

Jan 84

MTAACP/Fl lMSG
MOUNT REPORTS WRONG ERROR FOR OFFLINE TAPE
MTAACP HANGS/CRASHES SYSTEM

3.2.3.1 M
3.2.3.2 M

Jan 84
JUD 84

ERROR LOGGING
CFL
CORRECTION FOR CFL NOT GIVEN IN UPDATE C

3.3.1.1 N

oct 85

FILE READ ERROR ON RP03'S
LBN BAD FOR RL01/RL02 DISKS FROM ERRLOG

3.3.4.1 M
3.3.4.2 M

oec 83
Mar 84

CONTROL FILES
V4.1 RPT ABORTS ON RASO ERROR

3.3.5.1 N

Jan 84

OUE /EN:xxx/FI:l/DEL DOESN'T DELETE THE FILE FROM THE JOB
STOP:AB DELETES FILES INSTEAD OF PUTTING THEM IN HELD STATE
()MG DOESN'T STOP SPOOLED LINE PRINTER PROPERLY
QUEUE /EN:xxxx ERROR MESSAGE INCONSISTENT
QUEUE PRODUCES ERROR ON ASSIGN OF QUEUE WITH 1 OR 2 CHARS
OUE HANGS IF UFO [1,7) IS NOT PRESENT

4.1.3.1 M
4.1.3.2 N
4.1.3.3 N
4.1.3.4 M
4.1.3.5 M
4.1.3.6 N

NOV 83
NOV 83
Jan 84
Apr 84
Apr 84
Apr 85

OUE/PRI
LPP INCORRECTLY DELETES FILE BY FILE ID

4.1.4.1 M

Jan 85

Mar 84
Jul 84
Mar 85
Mar 85

LADRV

FILE SYSTEM

res

RPT

BATCH/OUEUE MGR
()MG

(

component

sequence

Mon/Yr

LPP
IF USER WRITTEN DEL CHECK ROUTINE USED PRI/DE DOESN'T DELETE
PROBLEM WITH SIMULATED FORMS AND FORMFEEDS
LA100 DEVICE SUPPORT ADDED TO DESPOOLER HAS 2 PROBLEMS
FILE WITH AN ILLEGAL RECORD SIZE WILL HANG IN OUEUE
NLO SHOULD NOT BE SPOOLABLE
LPP LOOPS ON NEGATIVE RECORD LENGTH

4.1.5.1 N
4.1.5.2 N
4.1.5.3 M
4.1.5.4 M
4.1.5.5 M
4.1.5.6 M

NOV

MULTI-USER TASK
SHUTUP
SHUTUP INCORRECTLY TESTS FOR TASK IMAGE CHECKPOINT SPACE

4.2.5.1 M

Jun 84

UTILITIES
DMP
ANSI MAGTAPES AND DMP

5.1.5.1 R

Jan 84

FLX
ENDLESS •DEVICE HANDLER MISSING• MESSAGES FROM FLX
FLX ABORTS ON COMMAND FOLLOWING •ILLEGAL SWITCH• MESSAGE
FLX DOES ONT SUPPORT DU:

5.1.1.1 M
5.1.1.2 M
5.1.1.3 M

Jan 84
Jan 84
Jan 84

INI
INI CANNOT USE /INDEX=END SWITCH WITH LAST TRACK DEVICES

5.1.8.1 M

Sep 85

MOU
MOUNT X:/FOR/ACP=UNIOUE CRASHES SYSTEM

5.1.10.1 N

Jan 84

PIP
DELETING FILES,70 DOES NOT ALWAYS WORK PROPERLY

5.1.12.1 M

Feb 86

BRU
ERRORS OCCUR ON MULTI-DISK RESTORE TO MOUNTED DISK
BRU INCORRECTLY HANDLES EXTENSION HEADERS AND 32 1 000 FILES
BRU /VER ABORTS ON THIRD TAPE WITH LARGE MULTIHEADER FILES
BRU ABORTS WITH I/O ERROR -10 ON RESTORES
BRU ERROR RECOVERY DURING A BACKUP TO TAPE
IMPROPER ERROR RECOVERY DURING A DISK-TO-TAPE BACKUP
BRU /IMAGE:RESTORE TO A MOUNTED DISK IGNORES /BACKUP~SET
BRU DOESN'T VERIFY ALL TAPES IN A BACKUP SET BEFORE STOPPING
BRU /BAD:MANUAL DOES NOT WORK AS DOCUMENTED
CANNOT DO SELECTIVE BACKUP/RESTORE WITH BRUSYS V3 0 0

5.1.11.1 M
5.1.11.2 M
5.1.11.3 M
5.1.17.4 M
5.1.11.5 M
5.1.17.6 M
5.1.11.1 R
5.1.11.8 N
5.1.17.9 M
5.1.17.10 M

oec 83
Jul 84
Apr 85
Apr 85
May 85
May 85
Jun 85
JUl 85
Sep 85
Feb 86

SYSTEM LIBRARIES
It-SERIES
A/D IS NOT ENABLED IF NO KW-11 IN SYSTEM

5.2.5.1 M

Apr 84

MISC SYSLIB
SYSLIB MODULE $CBASG DROPS MSD

5.2.6ol N

Feb 85

TASK BUILDER
TKB
TKB DOESN'T PROPERLY CK FOR MEM RES O'LAYED CLUSTER ELEMENT

5.3.1.1 M

NOV 83

83
Jan 84
Mar 84
Apr 84
Apr 84
Apr 86

(

Component

sequence

Mon/yr

TKB •vsECT' OPTION DOES NOT WORK CORRECTLY
TKB DOES NOT CORRECTLY SET FORTRAN TASK APR BITMAP
TKB ODD ADDRESS TRAPS WHEN BUILDING LARGE I/D TASK
READ ONLY AND READ WRITE CLUSTERING
NOTES REGARDING CLUSTER LIBRARY USE
TKB OFTEN CREATES MULTIPLE AUTOLOAD VECTORS FOR SAME SYMBOL
TKB CAN'T LINK SHARED REGIONS TOGETHER IF USING SYS PARTITION
FORTRAN-77 APR BITMAP IS INCORRECT
MULTIPLE REFERENCES TO .PSECT IN SEGMENT CAUSES TKB TO ABORT
TKB SWITCHES /LI AND /CO DO NOT WORK AS DOCUMENTED
TKB CORRUPTING VIRTUAL MEMORY UNDER RARE CONDITIONS

5.3.1.2 M
5.3.1.3 M
5.3.1.4 M
5.3.1.5 R
5.3.1.6 M
5.3.1.7 M
5.3.1.8 M
5.3.1.9 M
5.3.1.10 M
5.3.1.11 N
5.3.1.12 M

83
Jan 84
Mar 84
Mar 84
JUn 84
Aug 84
oct 84
oec 84
oct 85
NOV 85
Apr 86
NOV

FTB PRINTS GARBLED SYMBOL NAME AND MODULE NAME

NOV

STK CANNOT BUILD LARGE HEAVILY O'LAYED TASK CORRECTLY

Mar 84

DEBUGGING AIDS
ODT
TASK WITH LARGE NUMBER OF LUNS HANGS IN ODT

5.5.1.1 M

Jan 86

MISC SYS TASKS
HELP
HELP KEYWORDS DO NOT ACCEPT DEVICE NUMBERS HIGHER THAN 7
HELP /OUTtTTNN: <PARAMETER> DOES NOT WORK

5.7.1.1 M
5.7.1.2 N

Jul 84
Feb 86

CDA
CDA ODD ADDRESS TRAP ON ADDRESS OUT OF RANGE
CDA DOES NOT DISPLAY ALL I/O PACKETS
CDA /MEMSIZ SWITCH EXTENDS FILE TOO FAR
CDA DOES NOT OUTPUT LAST WORD OF ERRLOG BUFFERS
CDA DOES NOT ALLOW MS: TO FINISH REWINDING

5.7.2.1 M
5.7.2.2 M
5.7.2.3 M
5.7.2.4 M
5.1.2.5 M

Apr 84
JUn 84
Jul 85
Jul 85
Jul 85

RMDEMO
RMDEMO IN/OUT STATISTICS INCORRECT
RUNNING RMD FROM CLOCK QUEUE DOES NOT WORK CORRECTLY
FMD DOES NOT SHOW PARTITIONS BELOW 32K

5.7.5.1 M
5.7.5.2 M
5.7.5.3 M

Jan 84
Apr 84
Apr 85

TDX
TDX PROBLEMS FIXED IN UPDATE C
CATCHALL.CMD MISSING FROM DISTIRBUTION KITS
CVT DOES NOT WORK FROM A COMMAND FILE
FLYING INDIRECT OPTION OFTEN FAILS

5.7.7.1 M
5.7.7.2 M
5.7.7.3 M
5.7.7.4 M

Jan 84
Mar 84
Apr 84
JUn 84

RCT
RCT PROBLEMS

5.7.15.l M

oec 83

DCL
DCL
VARIOUS SYNTAX PROBLEMS IN DCL FIXED IN UPDATE B
/NO JOURNAL DOESN'T WORK FOR DCL EDIT/EDT
DCL 'STOP/ABORT' COMMAND FAILS WITH 'STOP WHAT?' MESSAGE

6.1.0.1 M
6.1.0.2 M
6.1.0.3 M

NOV

NOV 83

83
oec 83

COllponent

sequence

Mon/Yr

RMSCNV / PD SWITCH TAXES ASCII 0 TO 7 AS OCTAL NUMBER
LINK COMMAND DELETES INTERMEDIATE FILE TOO SOON
DCL FORTRAN COMMAND LISTING SWITCHES DO NOT WORK
DCL ALLOWS MULTIPLE INVOCATIONS OF AT.
DCL FIXES TO STOP/OUEUE/MANAGER/ABORT NOT ON UPDATE B KITS
DCL DOES NOT ACCEPT BAC @ @FILESPBC SYNTAX
VARIOUS DCL PROBLEMS FIXED IN UPDATE C
NEW DCL COMMANDS FOR DECNET/SNA SUPPORT
DCL DOES NOT ALWAYS DETECT A FILE SPEC ERROR
DCL PROBLEMS WITH NETWORK NODE SPECIFICATIONS
•MOUNT/DENS•800 DD1• TRANSLATES TO MOU DD1/DENS•800.
SET DEVICE /SYSTEM AND DCL COBOL/Cll PROBLEMS
DCL/ATT/OUT-FILESPEC DOES NOT PLACE OUTPUT IN FILESPEC
DCL SE DE ABBREVIATION AMBIGUOUS
DCL LINK /OPTION:FILESPEC NOT ACCEPTED AS VALID SYNTAX
DCL DELETE [*,*] FILESPEC DOESN'T WORK FOR UPDATE C
•ocL LIBRARY/CREATE LIBRARYSPEC• PROMPTS FOR INPUT MODULES
DCL SUBMIT/NOPRINT DOES NOT WORK CORRECTLY WITH UPDATE D
DCL FORTRAN/NOF77 SHOULD NOT ALSO REOUIRE /F77
•1• AT BEGINNING OF OUOTED STRING IS STILL TREATED AS COMMENT
ADD /[NO]WARNINGS QUALIFIER TO DCL PRINT AND SUBMIT COMMANDS
CREATE/DIR/ALL-NUN. DOES NOT TRANSLATE DECIMAL POINT
PURGE/KEEP1N/NOLOG FILE TRANSLATES TO PIP/SB•FILE/PU1N
RUN /DELAY1N DOES NOT WORK WITH THE /STATUS1TASK QUALIFIER
DCL START/PRINTER LPNt/PAGE:N DOES NOT WORK
DCL CONVERTS CERTAIN SPECIAL CHARACTERS INCORRECTLY
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @FILESPEC• DOES NOT WORK

6.1.0.4 N
6.1.0.5 M
6.1.0.6 M
6.1.0.7 M
6.1.0.8 N
6.1.0.9 M
6.1.0.10 M
6.1.0.11 M
6.1.0.12 M
6.1.0.13 M
6.1.0.14 M
6.1.0.15 M
6.1.0.16 M
6.1.0.17 M
6.1.0.18 M
6.1.0.19 M
6.1.0.20 M
6.1.0.21 M
6.1.0.22 M
6,1.0.23 M
6.1.0.24 M
6.1.0.25 M
6.1.0.26 N
6.1.0.27 N
6.1.0.28 N
6olo0o29 N
6.1.0.30 M
6.1.0.31 M

oec 83
Jan 84
Jan 84
Jan 84
JUn 84
Mar 84
Apr 84
JUn 84
JUn 84
Jun 84
Aug 84
Aug 84
Aug 84
NOV 84
NOV 84
oec 84
Jan 85
Jan 85
Jan 85
Jan 85
Jan 85
Mar 85
JUn 85
JUl 85
JUl 85
Jul 85
Jan 86
Jan 86

DOCUMENTATION
SYSGEN GUIDE
PIP COMMAND LINE FOR COPYING llM TARGET SYSTEM IS INCORRECT

7.1.19.1 N

May 85

MINI RBF
THE DCL COMMAND DIRECTORY/PRINTER DOES NOT WORK ON RSX-llM

7.1.28.1 R

oec 84

10.6.2.1 N

May 84

10.7.lol N
10.7.1.2 N
10.7.1,3 M
10.7.1.4 M

Aug 84
Feb 85
Apr 86
sep 85

SORT/MERGE V3.0
PACPGE NOTES
ANNOUNCING PDP-11 SORT/MERGE V3 • 0
as-11 v2.o
SUMMARY OF RMS-11 MODIFICATIONS SINCE DISTRIBUTION ON RSX-llM
SUMMARY OF RMS-11 MODIFICATIONS ON RSX-llM FOR UPDATE E
INDEX FILE CORRUPTION IN ALTERNATE KEY PATH
CORRUPTION IN VERY LARGE FILES

(

COllponent

sequence

llOD/!l"

10.8.2.2 N
10.8.2.3 N
10.8.2.4 N
10.8.2.s N
10.8.2.6 N
10.8.2.1 N
10.8.2.8 N
10.8.2.9 N
10.8.2.10 N
10.8.2.11 N
10.8.2.12 N
10.8.2.13 N
10.8.2.14 N
10.8.2.1s N
10.8.2.16 N

NOV 83
NOV 83
NOV 83
NOV 83
NOV 83

10.8.3.1 N

oec 84

10.14.4.26 M
10.14.4.27 M
10.14.4.28 M
10.14.4.29 M

Jun 83
JUD 83
JUD 83
JUD 83

10.15.1.1 N
10.15.1.2 N
10.15.1.3 M
10.15.1.4 M

oec 83
oec 83
oec 83

10.17.1.1 M

May 84

10.18.1.1 N

JUD 83

DECDet-11M/S VJ.1

RSX DECnet PROGRAMMER'S REFERENCE MANUAL CORRECTIONS
RSX DECnet SYSTEM MANAGER'S GUIDE CORRECTION
PROPER SYSLIB.OLB FOR NETGEN
TIPS ON SUBMITTING A DECnet SPR
DOCUMENTATION CORRECTION FOR RSX-11S SYSTEMS
ERRORS IN THE DECnet SYSTEM MANAGER'S GUIDE
INCORRECT FORMAT FOR NCP SHOW MODULE X25-PROTOCOL
THE MICROFICHE FOR RSX DECnet 3.1/1.1 IS NO LONGER RESTRICTED
PROBLEMS DOWN-LINE LOADING OVERLAYS VIA DECnet
HOW TO WRITE A NETWORK SPR
DECnet-llM/S PROBLEMS FIXED ON RSX-11M/S LAYERED UPDATE A
DECnet AUTOPATCH MAY NOT APPLY ALL PATCHES
DOWN-LINE LOADING OVER THE DMVll GIVES WRONG TRIBUTARY ADDRESS
DECnet-llM/S PROBLEMS FIXED ON RSX-llM LAYERED UPDATE B
DECnet-11M/S PROBLEMS PIXED ON RSX-11M LAYERED UPDATE C

NOV 83
NOV 83
NOV 83
NOV 83
Nov 83

Aug 83
NOV 83
NOV 83
NOV 83
Apr 84

DECnet-11M/S V4.0
DECnet-11M PROBLEMS PIXED ON RSX-11M LAYERED UPDATE E

DATATRIEVB-11 V2 • 4
XEYED OR BOOLEAN
ODICT MAY NOT CREATE A OUERY DICTIONARY
CHANGES TO SUPPORT RMS v2.o
REOUIRED PATCHES FOR DATATRIEVE-11

DATATRIEVB-11 V3.0
ANNOUNCING DATATRIEVE-11 VERSION 3
NEW DATA DICTIONARY FOR VERSION 3
PROBLEM WITH REDEFINES
RSM v2.o CHANGE TO DATATRIEVE-11 VJ.O

Feb 84

PMS-11/RSX v1.o
PDV

PMS TERMINAL SUPPORT PATCHES

BASIC-PLOS-2 V2.1

(

PACltAGE NOTES
PDP-11 BASIC-PLUS-2 V2.1 NOW AVAILABLE

sequence

Mon/Yr

10.19.1.1

Apr 84

10.20.1.1 N

D8C

PDP-11 CORAL 66 V4.0
GENERAL
ANNOUNCEMENT OF PDP-11 CORAL 66 V4.0
PROCEDURE FOR INSTALLATION OF PATCHES ON PDP-11 CORAL 66 V4.0

11.5.1.1 N
11.5.1.2 N

Apr 84
Apr 84

COMPILER
ARRAY INDEX INCORRECTLY COMPUTED SOMETIMES
ERROR IN FLOATING p0INT OPTIMIZATION
'UNION' OPERATOR CAN CAUSE COMPILER TO ABORT
DIVISION BY ONE CAN GENERATE INCORRECT CODE
OBJECT CODE PRINT CAN CAUSE PRINTER FORMAT ERRORS
ABNORMAL TERMINATION OF COMPILER IF SOURCE TOO BIG
ARRAY PARAMETERS CAN CAUSE ERROR 189

11.5.2.1 M
11.5.2.2 M
11.5.2.3 M
11.5.2.4 M
11.5.2.5 M
11.5.2.6 M
11.5.2.1 M

Apr 84
Apr 84
Apr 84
Apr 84
Apr 84
Apr 84
Apr 84

12.1.1.1 N

Jun 83

14.1.1.1 N

NOV

15.1.lol N

Jan 84

Component
BASIC-PLUS-2 V2e2
PACXAGE·NOTES
BASIC-PLUS-2 V2.2 TO SHIP IN MARCH

BASIC-PLUS-2 V2.3
PROBLEM WITH PRINT USING

PDP-11 CORAL 66 V4.0

COBOL-81 v2.o
PACKAGE NOTES
ANNOUNCING COBOL-81 VERSION 2.0

PDP-11 RPG II V8 • 8
ANNOUNCEMENT OF PDP-11 RPG II vs.a

RGL/11 Vl.1

THE COLOR OF A GRAPH'S LABELS AND TITLES IS NOT CONTROLLED
BY THE CURRENT WRITING COLOR

FORTRAN IV/RSX V2.6
OTS
LIST-DIRECTED READ

D8C

(

CO.ponent

sequence

Mon/Yr'

17.l.l.l N

Apr 86

PDP-11 SYMBOLIC DEBUGGER V2.0
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER v2.o

(
29

RSX-11M V4.2

(

RSX Software Dispatch, April 1986

Seq. No. 1.1.1.3 M

RSX-llM V4.2
SYSGEN
AUTOCONFIGURE

1 of 1

ACF MAY NOT CORRECTLY SET UP DV.NUC IN CONFIG.DAT FOR RS03/4s
(SPR 11-00211X CS)
PROBLEM
STATEMENT:

(

Autoconfigure (ACF) may not correctly set up DV.NUC in the CONFIG.DAT file for
RS03/4 devices.

RESPONSE:
This problem occurs if the RS03/4 device does not have the
register implemented, as allowed by the MASSBUS specification.

Serial

Number

If the RS03/4 Serial Number register is not implemented, the Autoconfigure
logic does not handle it as an exception condition and incorrectly sets up
DV.NUC in the device configuration file, CONFIG.DAT.
A user, under this condition and performing a SYSGEN, finds that the ACO SHOW
operation aborts abnormally.
The user must then restart the SYSGEN, not
include the Autoconfiguration process, and manually provide SYSGEN with the
hardware configuration information.
This problem is corrected in RSX-llM Version 4.2 Update C.

(
33

(

RSX Software Dispatch, April 1986

Seq. No. 2.2.2.1 M

RSX- llM V4. 2
MCR
INS

1 of 1

NEW "TASK IMAGE I/O ERROR" MESSAGE FOR DEVICES (SPR ll--00207X RC)
•

PROBLEM
STATEMENT:
INS aborts with the message "SYNTAX ERROR" for certain I/O errors returned
the driver.

RESPONSE:
For those I/O errors other than device off line, no pool, device not in
system, device not mounted, parse error, and file privilege violation, which
are currently reported explicitly, we have changed the message to read:
"Task image I/O error"
This problem is corrected in RSX-llM Version 4.2 Update C.

(
35

RSX Software Dispatch, April 1986

Seq. No. 2.2.2.2 M

RSX-llM V4.2
MCR
INS

1 of 1

SCHEDULING OF SHUFFLER MAY CRASH SYSTEM (SPR ll-00212X KF)

•
PROBLEM
STATEMENT:
Scheduling the Shuffler may crash the system if the Shuffler is not
memory.

fixed

RESPONSE:
If the Shuffler is not fixed in memory and is requested by the system, the
$RQSCH pointer into the Active Task List (ATL) can get redirected to the task
control block (TCB) of the Shuffler even though it is not in the ATL. This
can cause the system to attempt to activate the Shuffler. If the Shuffler is
not yet loaded in memory, the system looks to the next task in the ATL to make
the current task. Since the Shuffler is not in the ATL, the link word may not
be a valid TCB address. At this point, the system will most likely attempt to
access an odd address and crash.
This problem is corrected by calling an alternate entry to the Executive
request routine when the Shuffler is requested by the system. This alternate
entry checks if the task is active before possibly resetting the $RQSCH
pointer.
If the task is not active, which is the case of the unfixed
Shuffler, $RQSCH will be redirected only after the task is loaded and placed
in the ATL.
This problem is corrected in RSX-llM Version 4.2 Update B. Although this
situation has been corrected, to avoid other problems with the Shuffler, we
suggest that a separate partition be created for the Shuffler, and the task be
fixed in memory.

RSX Software Dispatch, April 1986

RSX-11M V4.2
MCR
INDIRECT

Seq. No. 2.2.3.9 M
1 of 1

ESCAPE RESPONSE TO .ASKS DEFINES SYMBOL AS LOGICAL (SPR 11-00206X RDH)
PROBLEM
STATEMENT:
When an ".ASKS ssssss txt-string" directive is responded to with the ESCAPE
key, the symbol "ssssss" is defined as logical and set true. A subsequent use
of "ssssss" as a string variable (as in another .ASKS directive) results in
a "Redefining symbol to different type" error message.
RESPONSE:
A change was made to Indirect in RSX-llM Version 4.2 to implement setting
symbol "ssssss" true when an ".ASK ssssss txt-string" directive is answered
with the ESCAPE key, thereby, complying with the documentation. In making the
change, the internal variable SYMTYP was used to test if "ssssss" is a logical
symbol. Variable SYMTP should have been used instead.
The following command line sequence will provide a workaround, where the .TEST
immediately precedes the .ASKS line •
• TEST ssssss
.ASKS ssssss txt-string
It establishes a valid context for SYMTYP such that the succeeding .ASKS will
not arbitrarily make "ssssss" a logical symbol.
RSX-llM Version 4.2 Update B includes a correction for this problem.

(
37

RSX Software Dispatch, April 1986

Seq. No. 2.2.3.10 M

RSX-UM V4.2
MCR
INDIRECT

1 of 2

ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES (SPR ll-00213X RDH)
PROBLEM
STATEMENT:
The Indirect Command Processor allows definitions of global and local symbols
with the same name to exist on the same level. Also, it allows the individual
deletion of local symbols when they assume the global naming convention. This
is contradictory to the documentation.
The following command files demonstrate the problem:
A.CMD
.SETS $A "Howdie"
.SETS $B "Doodie"
@A2
.IFNDF $A .STOP
.IF $B NE 2 .STOP
.ERASE SYMBOL $B
.IF $B NE "Doodle" .STOP
.ERASE SYMBOL $B
.EXIT

local symbol $A
local symbol $B
ensure we are back on the correct level
this $B is global from A2.CMD
erases $B from global table
this $B is local from A.CMD
erases $B from local table

A2.CMD
.ENABLE GLOBAL
.SETN $B 2
.EXIT

enable global symbol processing
global symbol $B

RESPONSE:

RSX Software Dispatch, April 1986

Seq. No. 2.2.3.10 M

RSX-llM V4.2
MCR
INDIRECT

2 of 2

The implementation of Indirect does allow the .ERASE SYMBOL to affect local
symbols if their name begins with the dollar sign, contrary to the documented
restriction that only
global
symbols
may
be
individually
erased.
Investigation of this problem shows that the restriction can be removed
without adverse impact.
Its removal would also eliminate the apparent
advantages of naming local symbols with dollar signs.
RSX-llM Version 4.2 Update C includes a change which removes this restriction.
Specifically, the .ERASE SYMBOL directive will be able to erase individual
global or local symbols. If two symbols with the same name, one global and
one local, exist for the level on which the .ERASE SYMBOL is being executed,
the global symbol will take precedence and be erased.

(
39

RSX Software Dispatch, April 1986

RSX-llM V4.2
MCR
INDIRECT

Seq. No. 2.2.3.11 M
1 of 1

CORRUPTED BEGIN-END BLOCK POINTERS IN LOCAL SYMBOL TABLE (SPR ll--00214X RDH)
PROBLEM
STATEMENT:
Both .SETS assignments to local string symbols and .ERASE LOCAL directives can
cause memory protect violations or Illegal Nesting errors when executed from
within Begin-End blocks or from files invoked with the /LO switch.
RESPONSE:
Begin-End blocking context, which is stored in the Local Symbol Table as
special frames, includes pointers to the start of the next-higher symbol
block. The pointers are not correctly maintained when a .SETS is executed on
a string symbol that is outside the current Begin-End block but still within
the current Local Symbol Table range, for example, a local symbol defined at a
higher level of Begin-End block.
If the .SETS changes the length of the
string, a Memory Protect violation may occur when the task exits.
In a similar manner, execution of the .ERASE LOCAL directive from the
beginning block level of a file which was invoked with the /LO switch will
corrupt the Begin-End block pointers, resulting in an Illegal Nesting error.
These failures can be avoided by:
1.

Do not modify higher-level local string symbols from within Begin-End
blocks.
If you need to implement this functionality, define the
string symbol as global.

Do not execute the .ERASE LOCAL directive from the highest block
level of a file which has been invoked with a /LO switch. Defining
the symbols as global and erasing them with the .ERASE SYMBOL xxxx
directive provides an alternative implementation.

RSX-llM Version 4.2 Update C includes corrections for these problems.

(

RSX Software Dispatch, April 1986

Seq. No. 3.3.s.s M

RSX-llM V4.2
ERROR LOGGING
CONTROL FILES

1 of 1

ERLRPT-F-MODLOASYM UNDEFINED SYMBOL IN MODULE TO BE LOADED (SPR 11-00208X GM)

.
PROBLEM
STATEMENT:
RPT aborted, while analyzing TKSO errors, with the following error message:
"ERLRPT-F-MODLOASYM, Undefined symbol in module to be loaded"
RESPONSE:
One of the control file modules that analyzes the MSCP device's information
message has undefined symbols in it. This causes RPT to abort with the above
error message.
This problem is corrected in RSX-llM Version 4.2 Update B.

(
41

RSX Software Dispatch, April 1986

RSX-llM V4.2
BATCH/QUEUE MGR
LPP

Seq. No. 4.1.s.1 M
1 of 1

LPP LOOPS ON NEGATIVE RECORD LENGTH (SPR ll-00210X RDH)
PROBLEM
STATEMENT:
LPP loops when printing a file containing a
length.

record

with

negative

record

RESPONSE:
PRT issues a GET$S directive to read each record from the file being
Two types of invalid record length may result from this operation:
1.

Actual record length exceeds limit established
specified in F.URBD

for

the

printed.

device

and

In this case, File Control Services (FCS) transfers as many bytes as
will fit in the user buffer and returns the error code IE.RBG. FCS
updates F.RCNM to point at the next record.
2.

Actual record length is negative.
FCS returns the error code IE.RBG. No bytes are transferred to the
user buffer.
Also, FCS does not update F.RCNM to the next record,
since it cannot determine its starting point because of the negative
record length.
On receiving the IE.RBG error code, PRT assumes that it resulted from
the former case and proceeds to print the truncated record. If the
error had resulted from the latter situation, PRT prints the contents
of the user buffer (the preceding line) and requests the next record,
thereby, looping until the entry is deleted from the queue.

RSX-llM Version 4.2 Update C includes a correction for this problem.
Specifically, PRT will test for negative record length and abort with an error
message if one occurs.

(
43

RSX Software Dispatch, April 1986

Seq. No. S.1.12.1 M

RSX-llM V4.2
UTILITIES
PIP

1 of 1

DELETING FILES, ;O DOES NOT ALWAYS WORK PROPERLY (SPR ll-0020SX JG)
PROBLEM
STATEMENT:
Deleting files and using wildcards for the member number in the UFD and a
zero for the version number, causes the latest version number of the file from
the first UFD to remain sticky for all files in all other UFDs.
RESPONSE:
This problem has been corrected so that the latest version of the file is
found in each UFD, and not just the first UFD. The correction for this
problem is in RSX-llM Version 4.2 Update B.

(
45

(

RSX Software Dispatch, April 1986

Seq. No. 5.1.17.11 M

RSX-llM V4.2
UTILITIES
BRU

1 of 1

POTENTIAL PROBLEM WHEN FIRST FILE RESTORED IS CONTIGUOUS (SPR ll--00204X SIR)
PROBLEM
STATEMENT:
A potential problem was discovered in BRU under RSX-llM V4.2, which could
cause the contiguous file attribute not to be set for the first file restored.
RESPONSE:
This problem is caused by the duplicate use of a single flag to indicate two
different conditions. In the extremely unlikely event that both of these
conditions occur, the first, and only the first, file created on the output
disk of a copy or restore operation will not have the contiguous file
attribute set, even if this attribute were set for the original input file.
However, the output file is created contiguously.
Using PIP with the /CO switch to copy the file contiguously will correct
problem, should it ever occur.
This problem is corrected in RSX-llM Version 4.2 Update B.

(
47

this

RSX Software Dispatch, April 1986

RSX-11M V4. 2
TASK BUILDER
TASK BUILDER

Seq. No. 5.3.0.1 M
1 of 1

TKB SWITCH /CL DOES NOT WORK (SPR 11-00112P DR)

•
PROBLEM
STATEMENT:
When a task built with the TKB switch /CL is installed, it does not end up
marked as such. The following command displays the task status where "xxxxxx"
is the name of a task. This task should have the CLI status displayed but
does not.
MCR TAL xxxxxx
RESPONSE:
When the TKB switch /CL was implemented, the original task flag word did
not have any bits available. A second task flag word was added to the task
label block. Although the task build command line is properly parsed and the
internal representations updated, the process of setting the new task flag
word contained an error.
The INS
status.

switch

/CLI=YES

can

used as a workaround to force the desired

The task flag word is correctly set in RSX-llM Version 4.2 Update B.

(
49

RSX Software Dispatch, April 1986

RSX-llM V4.2
TASK BUILDER
TASK BUILDER

Seq. No. 5.3.0.2 M
1 of 1

MULTIPLE REFERENCES TO .PSECT IN SEGMENT CAUSE TKB TO ABORT (SPR ll-00202X DR)

•
PROBLEM
STATEMENT:
Multiple references in a single segment to a .PSECT specified in an ODL file
cause TKB to behave unpredictably, including aborting because of an odd
address trap.
A multiple reference may inadvertently be created when
tailoring an ODL file by combining segments. The following is an artificially
simple example:
.PSECT
.PSECT
.ROOT

X
Y
X- X- Y- Y

.END
RESPONSE:
TKB, upon detecting the multiple occurrence, improperly skips over inserting
the .PSECT
into the segment's section list, resulting in an extra word being
popped off the stack.
Since specifying a .PSECT more than once serves no function, the
workaround is to remove all multiple references from the ODL files.
Multiple occurrences will be allowed by being
ignored) in RSX-llM Version 4.2 Update B.

properly

handled

obvious

(that

is,

RSX Software Dispatch, April 1986

Seq. No. S.S.1.1 M

RSX-llM V4.2
DEBUGGING AIDS
ODT

1 of 1

tASK WITH LARGE NUMBER OF LUNs HANGS IN ODT (SPR ll-00201X LP)

•
PROBLEM
STATEMENT:
The user's I/D task works when built non-I/D, but crashes when built I/D. The
task, which uses a large number of LUNs (110), hangs immediately when built
with ODT.
RESPONSE:
When a task is built with ODT, two additional LUNs are included for ODT.
ODT
was incorrectly using the first of these LUNs as an event flag number to issue
QIOs to the terminal. This error caused the task to hang in ODT because the
ODT LUN number (111) was higher than the any of the legal event flag numbers
(0-96). This error will be corrected in RSX-llM Version 4.2 Update B.
As a workaround, when using ODT, specify fewer LUNs with the TKB UNITS option.
Also, avoid using event flag numbers in the task, which coincide with the ODT
LUNs.

(
51

(

RSX Software Dispatch, April 1986

Seq. No. S.7.1.l N

RSX-llM V4.2
MISC SYS TASKS
HELP

1 of 1

HELP /OUT:TTNN: <PARAMETER) DOES NOT WORK (SPR ll--00174X JF)
PROBLEM
STATEMENT:

(

The command HELP/OUT:TTnn:
parameter is ignored.

(parameter)

does

not

work

expected.

The

RESPONSE:
There is a problem with the way HELP parses file specifications for the /OUT
and /FIL switches. If just a device is specified without a file name and
it is followed by another parameter, HELP treats the next parameter as the
file name.
As a workaround, provide a file name after the device name, or add another
switch after the device name. For example, HELP/OUT:TTnn:/MCR (parameter).
This problem is corrected in RSX-llM Version 4.2 Update B.

(
53

•

(

RSX Software Dispatch, April 1986

RSX-llM V4. 2
DCL
DCL

Seq. No. 6.1.0.s M
1 of 1

DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED (SPR 11-00193X JJA)

•
PROBLEM
STATEMENT:
The DCL LINK/OPTION command does not work as documented. The RSX-llM V4.1
Command Language Manual, page 6-74, specifies that there are three ways of
supplying options to the /OPTION qualifier:
1.

Supply a file specification of a file
options, i.e., LINK/OPTION:filespec.

Respond to the options prompt.
Example:

which

contains

the

list

LINK/OPTION
Option? optl
Option? opt2
Option? opt3
Option? (CR/LF)

List the options on the
LINK/OPTION:optl,opt2,opt3.

command

line separated by commas, i.e.,

However, the third format, where the options are listed on
line, separated by commas, does not work.

the

same

command

RESPONSE:
This problem results from an error in the parsing code for the DCL LINK
command.
It has been corrected. The correction will appear in RSX-llM
Version 4.2 Update B.
For now, use one of the formats which
Manual, and invoke TKB directly.

work,

(
55

refer

the Task Builder

RSX Software Dispatch, April 1986

Seq. No. 6.1.0.6 M

RSX-11M V4.2
DCL
DCL

1 of 1

DCL "LIBRARY @FILESPEC" DOES NOT WORK (SPR 11-00196X JJA)

•
STATEMENT:
The DCL command "LIBRARY @filespec" does not work.
RESPONSE:
It is currently documented that a user may perform operations with the DCL
LIBRARY command in one of two ways. A user may either specify the operation
with associated qualifiers directly on the command line or supply the LIBRARY
command with a file that contains the intended operations, i.e., DCL LIBRARY
@filespec. Currently, however, the latter format does not work.
This is corrected in RSX-llM Version 4.2 Update B.
For now, to circumvent the problem, the user
LBR will then accept a file containing the
LBR @filespec.

may invoke the MCR LBR command.
intended operations, i.e., MCR

(

RSX Software Dispatch, April 1986

Seq. 17.1.1.1 N

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM V4.2

1 of 3
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER VERSION 2.0

•
PRODUCT DESCRIPTION

(

Introduction
The PDP-11 Symbolic Debugger Version 2.0 is designed to help users find logic
and programming errors in successfully compiled and linked programs that do
not run correctly. Version 2.0, an extension of PDP-11 FORTRAN-77 DEBUG
Version
1.0, includes support for FORTRAN-77, COBOL-81, and MACR0-11.
Capabilities have also been added to PDP-11 FORTRAN-77 DEBUG Version 1.0 to
make it more powerful. Support is provided for debugging tasks built with land D-space, on systems where both the hardware and operating system support
this feature, for example, RSTS/E V9.0 or higher, RSX-llM-PLUS V2.l or higher,
Micro/RSTS V2.0, and Micro/RSX V3.0.
The debugger is designed as two tasks, a kernel and a background task.
The
kernel is linked in with user programs. The kernel is either overlaid to
occupy less than 4 kilobytes (KB) of user program space, or nonoverlaid to
occupy about 5 KB. The default is an overlaid debugger kernel which can be
used with all user programs (overlaid, cotrees, resident libraries, etc.),
except those user programs that do manual overlay loading. The kernel
communicates with the larger background task, which provides the debugger's
main functionality.
Operating Systems/Installation
The debugger runs on the following versions of DIGITAL's operating systems:

(

VAX-11 RSX Version 2.0 or higher

RSX-llM Version 4.1 or higher

RSX-llM-PLUS Version 2.1 or higher

Professional Host Tool Kit Version 2.0 or
Version 2.0 or higher

RSTS/E Version 9.2 or higher

higher

and

PRO/Tool

Kit

RSX Software Dispatch, April 1986

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-UM V4.2

Seq. 17.1.1.1 N
2 of 3

Micro/RSX Version 3.0 or higher

Micro/RSTS Version 2.0 or higher

•

Below is

PDP-11 Symbolic Debugger User's Guide

PDP-11 Symbolic Debugger Installation Guide

PDP-11 Symbolic Debugger Quick Reference

PDP-11 Symbolic Debugger Information for FORTRAN-77 Users

PDP-11 Symbolic Debugger Information for COBOL-81 Users

PDP-11 Symbolic Debugger Information for MACR0-11 Users

list

RSX Software Dispatch, April 1986

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM V4.2

Seq. 17.1.1.1 N
3 of 3

the
The

FOR DISK USERS

> BRU/NOI/UFD/NEW/MOU indev:[l,5]DBGREL.DOC outdev:
FOR TAPE USERS
) BRU/BAC:DBGREL/REW/NOI/UFD/NEW indev:

outdev:

Replace indev with the device on which your distribution medium is allocated
and mounted, replace outdev with the destination device. The Release Notes
are copied to [1,5] and named DBGREL.DOC.

(

(
59

RSX-UM V4.2
CUMULATIVE INDEX
APRIL 1986

This is a complete listing of all articles for RSX-llM V4.2 and layered products. Missing sequence
n1111bers •ay pertain to probleas unique to other versions of the same product or other major operating
syst•••·
IMPORTANT I
Unassigned articles are indicated:

UNASSIGNED.

Flags are currently being installed for all articles.

The flags and definitions are as follows.

M • Mandatory Patch. These patches correct errors in the software product. All users are required to
apply these patches to maintain consistent •user level• unless the accompanying article specifies
otherwise.
F • 0ptional Feature Patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the duration of the current
release and will be incorporated with any future release, unless otherwise stated.
R = Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as part
of the normal release cycle.
N = Note. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.
* = Articles appeared in the RSX Software Dispatch Review, September 1985.
Component

Sequence

Mon/Yr

1.1.1.1 R*
1.1.1.2 N

Sep 85
Nov 85

RSX-UM V4.2
SYSGEN
COMMAND PILES
SYSGEN PHASE 1 ASKS QUESTIONS THAT SHOULD NOT BE ASKED
TK50 FAILS TO INTERRUPT WHEN ACF IS RUN ON PDP-11/84
AUTOCONFIGURE
ACF MAY NOT CORRECTLY SET UP DV 0 NUC IN CONFIG 0 DAT FOR RS03/4s

Apr 86

EXECUTIVE
MISC ROUTINES
$QRMVT ROUTINE SHOULD NOT BE USED FOR GENERAL CASE DEQUEUING

Jan 86

(
61

Component

Sequence

Mon/Yr

2.2.2.1 M
2.2.2.2 M

Apr 86
Apr 86

2.2.3.1 R*
2.2.3.2 M
2.2.3.3 M

.!!£!.
INS
NEW •TASK IMAGE I/O ERROR• MESSAGE FOR DEVICES
SCHEDULING OF SHUFFLER MAY CRASH SYSTEM
INDIRECT, ICO, ICM, ICP
INDIRECT CAN CONFUSE IDENTICAL LABELS
FILE NAME AND SUBSTITUTION ERRORS IN INDIRECT
INDIRECT PROBLEMS CORRECTED IN UPDATE B
24-HOUR MAXIMUM FOR .DELAY DIRECTIVE
INVALID CHARACTERS IN SUBSTITUTION SYMBOL NAMES
INDIRECT COMMAND .SETT <ERSEEN> LEAVES IT FALSE
0 EXIT DIRECTIVE WITHIN BEGIN-END BLOCK
ERROR IN EXECUTION ON @/LB:MODULE FROM DCL OR MCR
ESCAPE RESPONSE TO .ASKS DEFINES SYMBOL AS LOGICAL
ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES
CORRUPTED BEGIN-END BLOCK POINTERS IN LOCAL SYMBOL TABLE

20 20 3 0 5 M
2.2.3.6 M
2.2.3. 7 M
2.2.3.8 M
20 2 0 3 0 9 M
2.2.3.10 M
2 0 2 0 3 0 11 M

Sep 85
Jan 86
Feb 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Apr 86
Apr 86
Apr 86

SAV/BOO
BOOT HANGS ON COPY OF A SYSTEM SAVED ON DIFFERENT CONTROLLER
SAV DOES NOT SIZE MEMORY CORRECTLY ON UNIBUS SYSTEMS
SAVE DOES NOT SIZE MEMORY ABOVE 1920 kW ON 0-BUS SYSTEMS

2.2.6.l N*
2.2.6.2 M
2.2.6.3 M

Sep 85
Feb 86
Feb 86

DRIVERS
DYDRV, DODRV, DRDRV, DDDRV, DLDRV
SUPPORT FOR DOUBLE-SIDED FLOPPY
DDDRV TIMES OUT WHILE COPYING LARGE FILES
DLDRV's ERROR RECOVERY SHOULD MAKE COMPLETE DRIVE-STATUS CHECK

3.1.1.1 M*
3.1.1.2 M
3.1.1.3 M

Sep 85
Mar 86
Mar 86

MUDRV
MUDRV DOES NOT SUPPORT MULTIPLE-DENSITY TAPE DRIVES
SYSTEM CRASHES WITH MUDRV/PUCOM MAPPED

3.1.2.1 M
3.1.2.2 M

Mar 86
Mar 86

FDX-TTDRV
DRIVER DOUBLE FORK CAUSES SYSTEM CRASH ON 0-BUS SYSTEM
VARIOUS TTDRV PROBLEMS

3.1.3.1 N
3.1.3.2 M

Feb 86
Mar 86

XEDRV
VARIOUS XEDRV PROBLEMS

3 0 1 0 5.1 M

Mar 86

ERROR LOGGING
CONTROL FILES
RPT DOES NOT RECOGNIZE USER-WRITTEN MODULES
UPDATE ERROR-CODE TABLE IN MSCP60 0 CNF
END MESSAGE PACKETS FOR MU ARE NOT ANALYZED PROPERLY
ERROR LOG MESSAGE PACKETS FOR TK50 ARE NOT ANALYZED PROPERLY
ERLRPT-F-MODLOASYM UNDEFINED SYMBOL IN MODULE TO BE LOADED

2.2.1.• M

.
3.3.5.1 M
3 0 3.5 0 2 M
3.3.5.3 M
3.3.5.4 M
3.3.5.5 M

Mar 86
Mar 86
Mar 86
Mar 86
Apr 86

BATCH/OUEUE MGR
QMG

STICKINESS IS LOST IN FILE EXTENSION IF FILES DO NOT EXIST

Mar 86

Component

Sequence

Mon/Yr

LPP
LPP LOOPS ON NEGATIVE RECORD LENGTH

40 10 50 1 M

Apr 86

DMP
ANSI MAGTAPES AND DMP

5.1.5.1 R*

Sep 85

UTILITIES
MOU
MOUNT DOES NOT WAIT FOR RA80/81 TO SPIN DOWN!

5 0 1 0 10 0 1 M

Mar 86

PIP
DELETING FILES, 10 DOES NOT ALWAYS WORK PROPERLY

5 0 1 0 12 0 1 M

Apr 86

BRU
BRU 9 NO FILES FOUND• PROBLEM CORRECTED
BRU ENDS WITH MEMORY PROTECTION VIOLATION DURING RESTORES
BRU INDICATES OUTPUT DISK IS TOO FRAGMENTED DURING VERIFY
BRU MAY FAIL ON THE VERIFY PASS OF A BACKUP OPERATION
BRU REPORTS I/O STATUS OF -255
BRU REPORTS ERRORS ABOUT FILES THAT DO NOT EXIST
BRU USES WRONG IMAGE FILE FOR RESTORE/COMPARE
BRU DOES NOT RECOVER PROPERLY FROM TAPE-LABEL ERRORS
ABNORMAL TERMINATION DURING THE VERIFY PASS OF A RESTORE
BRU REPORTS ATTACH FAILED AS SECOND FATAL ERROR
POTENTIAL PROBLEM WHEN FIRST FILE RESTORED IS CONTIGUOUS

5 0 1 0 17 0 1 M
5.1.11.2 N
5.1.11.3 N
5.1.11.4 N
5.1.11.5 N
5.1.11.6 N
5.1.11.1 N
5.1.11.8 M
5.1.11.9 M
5.1.11.10 N
5.1.17 0 11 M

Dec 85
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Apr 86

SYSTEM LIBRARIES
CSI
CSI$1 AND CSI$2 MEMORY PROTECT

5 0 20 60 1 M

Mar 86

TASK BUILDER
TASK BUILDER
TKB SWITCH /CL DOES NOT WORK
MULTIPLE REFERENCES TO PSECT IN SEGMENT CAUSE TKB TO ABORT

5 0 3 0 00 1 M
5 0 30 00 2 M

Apr 86
Apr 86

TKB
TKB OPENED AND CLOSED THE COMMAND FILE FOR EACH OPTION
I/D TASK LINKED TO LIBRARY AND COMMON DOES NOT BUILD

5.3.1.1 N
5 0 3 0 10 2 M

Nov 85

TASK WITH LARGE NUMBER OF LUNs HANGS IN ODT

5.5.1.1 M

Apr 86

DCL
DCL
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @FILESPEC• DOES NOT WORK

6.1.0.5 M
60 10 00 6 M

Apr 86
Apr 86

MISC SYS TASKS
HELP
HELP /OUT:TTNN: <PARAMETER> DOES NOT WORK

5 0 7 0 10 1 N

Apr 86

Feb 86

DEBUGGING AIDS
ODT

Component

Sequence

Mon/Yr

MPT/DTE
MPT FAILS TO FUNCTION PROPERLY

Mar 86

RCT
RCT DOES NOT REPLACE ALL BAD BLOCKS

Feb 86

DCL
DCL
CORRECT PRINTERPORTS PROBLEM AND ADD DEVICE NEGATIONS
RUN/STATUS:COMMAND DOES NOT MAP CORRECTLY
/LOG QUALIFIER SHOULD BE /LOGFILE ON SUBMIT COMMAND
DCL LINK DOES NOT WORK CORRECTLY IN SET DEBUG/EXECUTE MODE
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @FILESPEC• DOES NOT WORK

6.1.0.1 M
6.1.0.2 M
6.1.0.3 M
6.1.0.4 M
6.1.0.5 M
6.1.0.6 M

Feb 86
Feb 86
Feb 86
Mar 86
Apr 86
Apr 86

10.5.1.1 N*

Sep 85

RSX-11 2780/3780 PROTOCOL EMULATOR V4.1
CONDITIONS FOR AUTOMATIC SIGN ON

BASIC-PLUS-2 V2.3
PROBLEM WITH PRINT USING

Dec

FORTRAN IV/RSX V2.6
OTS
LIST-DIRECTED READ
PDP-11 SYMBOLIC DEBUGGER v2.o
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER v2.o

Apr 86

RSX-115 V4.1

RSX Software Dispatch, April 1986

RSX-llS V4.l
MCR

Seq. No. 2.2.s.1 M
1 of 1

VMR

UNABLE TO BOOT TRUNCATED RXOl SYSTEM (SPR ll-S81002 RC)
PROBLEM
STATEMENT:
Saving a system image file of 494 blocks or greater on
unusable system.

RXOl

produces

(
67

(
RSX-HS V4.1
CUMULATIVE INDEX
APRIL 1986

This is a COllplete listing of all articles for RSX-11S V4.1 and layered products. Missing sequence
n1111bers may pertain to probl. .s unique to other versions of the same product or other major operating
systems.
IMPORTANT I
unassigned articles are indicated1

UNASSIGNED.

Flags are currently being installed for all articles.

The flags and definitions are as follows.

M = Mandatory patch. These patches correct errors in the software product. All users are required to
apply these patches to maintain consistent •user level" unless the accompanying article specifies
otherwise.
F = Optional Feature Patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the duration of the current
release and will be incorporated with any future release, unless otherwise stated.
R = Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as part
of the normal release cycle.
N = NOte. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.
Component

sequence

Mon/Yr

EXECUTIVE
MISC ROUTINES
22-BIT SYS RUNNING WITH 128KW MEMORY CRASHES ON VIRGIN BOOT

2.1.6.1 M

NOV

MCR
BASIC MCR
REMOVE OF UNFIXED TASK ON 11S WILL CAUSE SYSTEM HANG

2.2.4.1 M

Apr 84

UNABLE TO BOOT TRUNCATED RXOl SYSTEM

2.2.5.1 M

Apr 86

MISC SYS TASKS
OTL
OTL RAS SEVERAL PROBLEMS
OTL DOES NOT SET UP WINDOW BLOCKS PROPERLY
OTL WILL NOT WORK WITH VIRTUAL ARRAY TASKS

5.1.8.1 M
5.7.8.2 M
5.7.8.3 M

Apr 84

RSX-HS V4.1

VMR

84
Feb 85

DSC

Collponent

Sequence

Mon/Yr

10080202 N
10.8.2.3 N
10.8.2.4 N
10.8.2.s N
10.80206 N
10.8.2.7 N
10.8.2.s N
10.8.2.9 N
10.8.2.10 N
10.8.2.11 N
10.8.2.12 N
10.8.2.13 N
10.8.2.14 N
10.8.2.1s N
10.8.2.16 N

NOY 83
NOV 83
NOY 83
NOY 83
NOY 83
NOY 83
NOY 83
NOV 83
NOY 83
NOY 83
Aug 83
NOV 83
NOY 83
NOY 83

10.8.3.1 N
10.8.3.2 N

Dec 84
Mar 85

DECnet-llM/S V3.1
RSX DECNET PROGRAMMER'S REFERENCE MANUAL CORRECTIONS
RSX DECNET SYSTEM MANAGER'S GUIDE CORRECTION
PROPER SYSLIB.OLB FOR NETGEN
TIPS ON SUBMITTING A DECNET SPR
DOCUMENTATION CORRECTION FOR RSX-llS SYSTEMS
ERRORS IN THE DECNET SYSTEM MANAGER'S GUIDE
INCORRECT FOR.MAT FOR NeP SHew MODULE X25 PROTOCOL
THE MICROFICHE FOR RSX DECNET 3.1/1.1 IS NO LONGER RESTRICTED
PROBLEMS DOWN-LINE LOADING OVERLAYS VIA DECNET
HOW TO WRITE A NETWORK SPR
DECNET-llM/S PROBLEMS PIXED ON RSX-llM/S LAYERED UPDATE A
DECNET AUTOPATCH MAY NOT APPLY ALL PATCHES
DOWN-LINE LOADING OVER THE DMVll GIVES WRONG TRIBUTARY ADDRESS
DECNET-llM/S PROBLEMS PIXED ON RSX-11M LAYERED UPDATE B
DECNET-llM/S PROBLEMS PIXED ON RSX-llM LAYERED UPDATE C

Apr 84

DECnet-llM/S V4o0
DECnet-llM PROBLEMS PIXED ON RSX-llS LAYERED UPDATE E
PERFORMING A DECnet-llS V4.0 NETGEN ON A VMS V4.0 HOST

RSX-115 V4.2

RSX Software Dispatch, April 1986

RSX-llS V4.2
SYS GEN
11SGEN2

Seq. No. 1.1.6.2 M
1 of 1

11SGEN2 PROBLEMS (SPR ll-00180X MR)
PROBLEM
STATEMENT:
1.

The llSGEN2 command procedure issues the command SET
VAX/VMS host, and VAX-11 RSX MCR gives an error message.

The 11SGEN2 VMR example fails to show that a partition should be
created for DY COM and the common should be installed when the DY
driver is built loadable.

NOON

RESPONSE:
1.

SET NOON is not a legal VAX-11 RSX MCR command.
This erroneous
command will be removed from 11SGEN2 in RSX-llS Version 4.2 Update B.

The missing example for installing DYCOM will be added to llSGEN2
RSX-llS Version 4.2 Update B.

(
73

RSX-HS V4.2
CUMULATIVE INDEX
APRIL 1986

This is a c0111plete listing of all articles for RSX-llS v4.2 and layered products. Missing sequence
nuabers •ay pertain to proble•s unique to other versions of the same product or other •ajor operating
syste•s.
IllPORTANTI
unassigned articles are indicated:

UNASSIGNED.

Flags are currently being installed for all articles.

The flags and definitions are as follows.

M • Mandatory patch. These patches correct errors in the software product. All users are required to
apply these patches to maintain consistent •user level• unless the accompanying article specifies
otherwise.
P m Optional Feature patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the duration of the current
release and will be incorporated with any future release, unless otherwise stated.
R ~ Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as part
of the normal release cycle.
N • NOte. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.
COllponent

sequence

Mon/Yr

SYSGEN
11SGEN2
11SGEN2 RETURNS •cOMMAND PILE OPEN ERROR•
11SGEN2 PROBLEMS

1.1.6.1 M
1.1.6.2 M

Peb 86
Apr 86

DRIVERS
MUDRV
MUDRV DOES NOT SUPPORT MULTIPLE-DENSITY TAPE DRIVES
SYSTEM CRASHES WITH MUDRV/PUCOM MAPPED

3.1.2.1 M
3.1.2.2 M

Mar 86
Mar 86

UTILITIES
BRU
BRU •No PILES POUND• PROBLEM CORRECTED

5.1.17.1 M

oec 85

RSX-HS V4.2

(
75

COllponent

seguence

Mon/Yr

SYSTEM LIBRARIES
CSI
CSI$1 AND CSI$2 MEMORY PROTECT

So2o6o1 M

Mar 86

MISC SYS TASKS
RCT
RCT DOES NO!l' REPLACE ALL liAD BLOCKS

s.1.1s.1 M

Peb 86

RSX-11M-PLUS V2.1

RSX Software Dispatch, April 1986

(
Seq • No • 2. 2. 3. 20 M

RSX-llM-PLUS V2.l
MCR
INDIRECT

1 of 2

*Supersedes RSX-llM-PLUS V2.l November 1985 Software Dispatch Seq. 2.2.3.20 M*
PROBLEMS WITH LOCAL SYMBOLS IN GLOBAL NAME FORMAT (SPR ll-P00215X RDH)
PROBLEM
STATEMENT:
The Indirect Command Processor allows definitions of global and local symbols
with the same name to exist on the same level. Also, it allows the individual
deletion of local symbols when they assume the global naming convention. This
is contradictory to the documentation.
The following command files demonstrate the problem:
A.CMD

(

.SETS $A "Howdie"
.SETS $B "Doodie"
@A2
• IFNDF $A .STOP
.IF $B NE 2 .STOP
.ERASE SYMBOL $B
• IF $B NE "Doodle" .STOP
.ERASE SYMBOL $B
.EXIT

local symbol $A
local symbol $B
ensure we are back on the correct level
this $B is global from A2.CMD
erases $B from global table
this $B is local from A.CMD
erases $B from local table

A2.CMD

-----.ENABLE GLOBAL
.SETN $B 2
.EXIT

enable global symbol processing
global symbol $B

RESPONSE:

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V2.l
MCR
INDIRECT

Seq. No. 2.2.3.20 M
2 of 2

The implementation of Indirect does allow the .~RASE SYMBOL to affect local
symbols if their name begins with the dollar sign, contrary to the documented
restriction

that

only

gl ohal

symbols

may

individual 1 y

erased.

Investigation of this problem shows that the restriction can be removed
without adverse impact.
Its removal would also eliminate the apparent
advantages of naming local symbols with dollar signs.
RSX-llM-PLUS Version 3.0 Update C and the next release of Micro/RSX will
include a change which removes this restriction. Specifically, the .ERASE
SYMBOL directive will be able to erase individual global or local symbols.
If two symbols with the same name, one global and one local, exist for the
level on which the .ERASE SYMBOL is being executed, the global symbol will
take precedence and be erased.

(

RSX Software Dispatch, April 1986

Seq. No. 2.2.5.4 M

RSX-llM-PLUS V2.1
MCR
VMR

1 of 1

SET /NOTYPEAHEAD CAUSES CRASH (SPR 11-00109P JF)
PROBLEM
STATEMENT:
A non-I/D RSX-llM-PLUS system with a DHU/DHV terminal controller and the no
typeahead characteristic set in VMR crashes after bringing on line the
fourth DHU/DHV line.
RESPONSE:
The size of the typeahead buffer cannot be changed in a non-I/D system.
When
VMR processes the SET /NOTYPEAHEAD command, it does not check to see if the
system is I/D or not, and it always sets the size of the typeahead buffer to
one.
This is correct for an I/D system, but not for a non-I/D system. VMR
should not change the size of the typeahead buffer on a non-I/D system.
This
eventually causes the system to crash when the terminals are brought on line.
As a workaround, set the no typeahead characteristic in MCR instead of VMR and
then SAVe the system.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update c.

(
81

RSX Software Dispatch, April 1986

Seq. No. 2.2.6.5 M

RSX-llM-PLUS V2.l
MCR
SAV

1 of 1

SAV CRASHES WHEN SYSTEM DISK IS A DUAL-ACCESS DEVICE (SPR 11-83266 KF)
PROBLEM
STATEMENT:
When SAVing a virgin system following system generation, the system crashes
with an odd address trap. The system device is dual access between two RH
controllers.
RESPONSE:
The system crash occurs when trying to access the second RH controller of your
system disk.
When SAV brings the system down, it sets the system device and
its controllers off line. The system device is necessarily on line.
One of
its controllers must also be on line for the system to work. In the case of a
dual-access device, the second controller does not have to be on line
or physically in the system. SAV fails to check the controller to see if it
is there before it accesses its control and status register (CSR) address in
memory. Since the controller is not there in this case, accessing this
location causes the system to crash. Since the system has been generated with
XDT, when the XDT prompt appears on the console, typing G will make the system
proceed as if nothing were wrong. The crash does not corrupt the system in
any way.

This problem is corrected in RSX-llM-PLUS Version 3.0 Update C.
Until
then, when SAVing your system, type G to the XDT prompt, and your system will
start up. This problem will not occur if the second RH controller is
installed properly. Check the switches on the controller to be sure they are
set for the correct CSR address.

(
83

RSX Software Dispatch, April 1986

RSX-llM-PLUS V2.l
BATCH/QUEUE MGR
LPP

Seq. No. 4.1.5.6 M
1 of 1

LPP LOOPS ON NEGATIVE RECORD LENGTH (SPR ll-P78038 RDH)

•

PROBLEM
STATEMENT:
LPP loops when printing a file containing
length.

record

with

negative record

RESPONSE:
PRT issues a GET$S directive to read each record from the file being
Two types of invalid record length may result from this operation:
1.

Actual record length exceeds limit established
specified in F.URBD.

for

the

printed.

device

and

In this case, File Control Services (FCS) transfers as many bytes as
will fit in the user buffer and returns the error code IE.RBG. FCS
updates F.RCNM to point at the next record.
2.

Actual record length is negative.
FCS returns the error code IE.RBG. No bytes are transferred to the
user buffer. Also, FCS does not update F.RCNM to the next record,
since it cannot determine its starting point because of the negative
record length.
On receiving the IE.RBG error code, PRT assumes that it resulted from
the former case and proceeds to print the truncated record. If the
error had resulted from the latter situation, PRT prints the contents
of the user buffer (the preceding line) and requests the next record,
thereby, looping until the entry is deleted from the queue.

RSX-llM-PLUS Version 3.0 Update C and the next release of
Micro/RSX will
include
a correction for this problem. Specifically, PRT will test for
negative record length and abort with an error message if one occurs.

(
85

•
•

(

RSX Software Dispatch, April 1986

Seq. No. S.3.1.11 M

RSX-llM-PLUS V2.l
TASK BUILDER
TKB

1 of 1

TKB CORRUPTING VIRTUAL MEMORY UNDER RARE CONDITIONS (SPR ll-P82336 LP)
PROBLEM
STATEMENT:
TKBFSL odd address traps while trying to build the user's task, which links to
FCSFSL.
The task also links to a resident common, and the user observes
certain P-sect is removed from the common, the task will build.

that

when

RESPONSE:
Incorrectly, TKB was treating resident library symbol references as symbol
definitions.
When the symbol was from a supervisor-mode library this bug
would also cause TKB to corrupt virtual memory. However, because of the way
TKB uses virtual memory, this corruption would lead to problems if, and only
if, two events occurred:
1.

The symbol table entry for the supervisor-mode library symbol
reference was allocated to exactly the last seven words of a virtual
memory page.

The number of virtual memory page searches exceeded 64K.

Your task, when built with the FSL version of TKB, just happened to meet these
two very rare conditions, and, thus, TKB failed. The bug which caused this
problem will be corrected in RSX-llM-PLUS Version 3.0 Update C and the
next release of Micro/RSX.
Since the slightest change in the virtual-memory requirements of your task
would allow TKB to succeed, your task would build when you removed a P-sect
from the resident common. This also means that TKB, TKBRES, and TKBFSL in
V3.0 and VJ.OB will work with your task because modifications made to TKB
itself for the new release have changed virtual memory requirements.

(
87

RSX Software Dispatch, April 1986

RMs-11 v2.o
for RSX-llM-PLUS V2.l

Seq. 10.7.1.3 M
1 of 6

*Supersedes RSX-llM-PLUS V2.l September 1985 Software Dispatch Seq 10.7.1.3 M*
INDEX FILE CORRUPTION IN ALTERNATE KEY PATH
PROBLEM:

There is a problem updating INDEX files with variable-length records.
If an attempt is made to update an existing variable-length record, a bad RRV
is created in the alternate key path if the following conditions are true:
o

The record size is increased.

Either a new alternate key
changed.

As a result of the increased record size, a bucket split occurs. (If
unaware of whether a bucket split occurs, assume that condition 3 is
true.)

introduced

existing

one

If an attempt is now made to GET this record by alternate key, RMS will return
the error ER$RRV (Bad Internal Pointer).
SOLUTION:
The patching procedure detailed below corrects the above problem.
In
cases, the files should be reloaded to correct the alternate key path.

all

RESPONSE:
This problem has been fixed and will be released in RSX-llM-PLUS V3.0. In the
meantime, the following procedure will fix the problem on the current
post-Update E system (select the appropriate procedure).

(
89

RSX Software Dispatch, April 1986

RMs-11 v2.o
for RSX-llM-PLUS V2.l

Seq. 10 • 7. 1. 3 M
2 of 6

NOTE
The program prompts with an underscore, so input begins after
that.
In all instances, make a copy of the file being
modified in case a mistake occurs.

1. If RMSRES.TSK (the resident library) is used, copy RMSLBF.TSK from
LB:[l,l] and invoke ZAP.
(you)
(you)

ZAP)RMSLBF.TSK
2:50104;0r
0, 674/(CR)

(ZAP)

2:0,000674/ 000054

(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(ZAP)

(CR)
2:0,000676/ 000566
<CR>
2:o ,ooo 700 I 116446
(CR)
2:0,000702/ 000024
(CR)
2:0 ,000704/ 132765

(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(ZAP)
(you)

0, 700/(CR)
2 :O ,ooo 700 I 11644 6
4 767<CR>
-/(CR)
2:0,000702/ 000024
6626(CR)
O, 700/(CR)
2:0,000700/ 004767
(CR)
2:0 ,000702/ 006626
_2: 57636;1 r(CR)

(ZAP)

connnent: set relocation register for R3IUDR
comment: come in a few locations before, to
confirm that you are in the correct
place
comment: verify that these values are the same
on your system.

comment: now come back to make the change

comment: now verify that you succeeded
comment: SUCCESS
•.

comment: set relocation register to start of
patch space. The contents of all
locations
opened at this point
should be ZEROS.

RSX Software Dispatch, April 1986

RMs-11 v2.o

Seq. 10 • 7. 1. 3 M

for RSX-llM-PLUS V2.1
3 of 6

(

(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)
(ZAP)

1,0/<CR)
2:1,000000/ 000000
11646(CR)
(CR)
2:1,000002/ 000000
116466<CR>
-<CR)
2:1,000004/ 000000
24<CR>
-<CR)
2: 1 ,00000 6/ 000000
2(CR)
-<CR)
2:1,000010/ 000000
1402(CR)
-<CR)
2: 1,000012/ 000000

(you)
(you)
(ZAP)
(you)
(you)
(ZAP)
(you)
(you)

62716<CR>
-<CR)
2:1,000014/ 000000
106(CR)
-<CR)
2:1,000016/ 000000
- 207<CR>
1,0/(CR)

(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)
(ZAP)
(you)

comment: start inserting new code at
this point

comment: now verify that the new code was
put in correctly

2: 1,000000/ 11646
<CR)
2: 1,000002/ 116466
<CR>
2: 1 , 000004 I 0000 24
(CR)
2: 1,00000 6/ 00000 2
<CR>
2: 1,000010 I oo 1402
<CR>
2:1,000012/ 062716
<CR>
2:1,000014/ 000106
<CR>
2: 1,000016/ 00020 7
x

comment: exit from ZAP

RSX Software Dispatch, April 1986

RMs-11 v2.o

Seq. 10. 7 .1. 3 M

for RSX-llM-PLUS V2.1

4 of 6

Now copy the corrected RMSLBF.TSK into LB:[l,1].
Next, to remo1re the old RMSLBF.'fSK and install the new RMSLBF.'fSK. 'fhis
requires removing all tasks installed against RMSLBF. Once this is done,
RMSLBF can be removed by issuing the following command:
REM/REG RMSLBF
Now install the the new one by issuing:
INS LB:[l,l]RMSLBF/PAR=GEN/READ
Now reinstall all the tasks.
If unable to remove RMSLBF, it may be easier to reboot the system.
Since
RMSLBF has already been copied into the account where the standard start-up
procedure looks for it, the system will come up with the newly installed
version. However, check your start-up procedure to confirm this.
NOTE
Tasks built against RMSRES will not
include this correction.

have

rebuilt

2. If RMSLIB.OLB is used to build RMS disk-overlaid or nonoverlaid tasks:
A. Extract the appropriate module from the object library.
$ LBR R3IUDR.OLD=LB:[l,l]RMSLIB.OLB/EX:R3IUDR
B. Create a file R3IUDR.PAT containing:
.TITLE
.!DENT
.PSECT

R3IUDR
/0222CMA/
R3IUDR,I

$$$ =
= $$$+700

RSX Software Dispatch, April 1986

Seq. 10. 7 .1. 3 M

RMS-11 V2.0
for RSX-llM-PLUS V2.l

5 of 6

CALL
.PSECT
R$IRP

PATCH
PATCH
24

MOV
MOVB
BEQ
ADD
RETURN
.END

(SP),-(SP)
R$IRP(R4),2(SP)
2$
11106,(SP)

PATCH:

2$:

C. Assemble the patch.
) MAC R3IUDR.PAT
D. Apply the patch using the PAT utility.
) PAT R3IUDR.NEW=R3IUDR.OLD/CS:022614,R3IUDR.OBJ/CS:013501
E. Replace into the library.
) LBR LB:[l,l]RMSLIB.OLB/RP=R3IUDR.NEW
3. If RMSLIB.OLB is used to build the RMS resident library satellites (this is
rarely done by the user):
A. Extract the appropriate module from the object library.
$ LBR R3IUDL.OLD=LB:[l,l]RMSLIB.OLB/EX:R3IUDL
B. Create a file R3IUDR.PAT containing:
.TITLE

R3IUDL

.IDENT
.PSECT

/0222CMA/
R3IUDR,I

$$$ =

(

• = $$$+ 700

RSX Software Dispatch, April 1986

RMs-11 v2.o

Seq • 10 • 7 • 1 • 3 M

for RSX-llM-PLUS V2.l
6 of 6

CALL
.PSECT

PATCH
PATCH

PATCH:

2$:

MOV
(SP),-(SP)
MOVB
R$IRP(R4),2(SP)
BEQ
2$
ADD
1110 6, (SP)
RETURN
.END

C. Assemble the patch.
) MAC R3IUDL.PAT
D. Apply the patch using the PAT utility.
) PAT R3IUDL.NEW=R3IUDL.OLD/CS:025534,R3IUDL.OBJ/CS:Ol3473
E. Replace into the library.
) LBR LB:[l,l]RMSLIB.OLB/RP/-EP=R3IUDL.NEW
Rebuild any applications that are not built against RMSRES.

RSX Software Dispatch, April 1986

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM-PLUS V2.l

Seq. 18.1.1.1 N
1 of 3

ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER VERSiON 2.0
PRODUCT DESCRIPTION
Introduction
The PDP-11 Symbolic Debugger Version 2.0 is designed to help users find logic
and programming errors in successfully compiled and linked programs that do
not run correctly. Version 2.0, an extension of PDP-11 FORTRAN-77 DEBUG
Version
1.0, includes support for FORTRAN-77, COBOL-81, and MACR0-11.
Capabilities have also been added to PDP-11 FORTRAN-77 DEBUG Version 1.0 to
make it more powerful. Support is provided for debugging tasks built with !and D-space, on systems where both the hardware and operating system support
this feature, for example, RSTS/E V9.0 or higher, RSX-llM-PLUS V2.l or higher,
Micro/RSTS v2.o, and Micro/RSX V3.0.
The debugger is designed as two tasks, a kernel and a background task.
The
kernel is linked in with user programs. The kernel is either overlaid to
occupy less than 4 kilobytes (KB) of user program space, or nonoverlaid to
occupy about 5 KB. The default is an overlaid debugger kernel which can be
used with all user programs (overlaid, cotrees, resident libraries, etc.),
except those user programs that do manual overlay loading. The kernel
communicates with the larger background task, which provides the debugger's
main functionality.
Operating Systems/Installation
The debugger runs on the following versions of DIGITAL's operating systems:

(

VAX-11 RSX Version 2.0 or higher

RSX-llM Version 4.1 or higher

RSX-llM-PLUS Version 2.1 or higher

Professional Host Tool Kit Version 2.0 or
Version 2.0 or higher

RSTS/E Version 9.2 or higher

higher

and

PRO/Tool

Kit

RSX Software Dispatch, April 1986

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM-PLUS V2.l

Seq. 18.1.1.1 N
2 of 3

Micro/RSX Version 3.0 or higher

Micro/RSTS Version 2.0 or higher

Below is

PDP-11 Symbolic Debugger User's Guide

PDP-11 Symbolic Debugger Installation Guide

PDP-11 Symbolic Debugger Quick Reference

PDP-11 Symbolic Debugger Information for FORTRAN-77 Users

PDP-11 Symbolic Debugger Information for COBOL-81 Users

PDP-11 Symbolic Debugger Information for MACR0-11 Users

list

RSX Software Dispatch, April 1986

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM-PLUS V2.l

Seq. 18.1.1.1 N
3 of 3

the
The

FOR DISK USERS

> BRU/NOI/UFD/NEW/MOU indev:[l,5]DBGREL.DOC outdev:
FOR TAPE USERS

> BRU/BAC:DBGREL/REW/NOI/UFD/NEW indev:

outdev:

Replace indev with the device on which your distribution medium is allocated
and mounted, replace outdev with the destination device. The Release Notes
are copied to [1,5] and named DBGREL.DOC.

(
97

•·

RSX-llM-PLUS V2.l
CUMULATIVE INDEX
APRIL 1986

This is a complete listing of all articles for RSX-llM-PLUS v2.1 and layered products. Missing
sequence nuabers may pertain to problems unique to other versions of the saae product or other aajor
operating ayateas.

...

IMpORTANTI
unassigned articles are indicated:

UNASSIGNED.

Flags are currently being installed for all articles.

The flags and definitions are as follows.

M = Mandatory patch. These patches correct errors in the software product. All users are required to
apply these patches to maintain consistent •user level• unless the accompanying article specifies
otherwise.
F = Qptional Feature patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the duration of the current
release and will be incorporated with any future release, unless otherwise stated.
R = Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as part
of the normal release cycle.
N = Note. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.

coaponent

Sequence

Mon/yr

1.1.1.1 F
1.1.1.2 M
1.1.1.3 M
1.1.1.4 M
1.1.1.s M
1.1.1.6 M
1.1.1.1 M
1.1.1.8 M
1.1.1.9 M
1.1.1.10 N
1.1.1.11 M

oec 83
oec 83
oec 83
Mar 84
Apr 84
JUD 84
Jun 84
JUD 84
JUD 84
JUD 84
Jun 85

RSX-llM-PLUS V2.l

(

SYSGEN
COMMAND FILES
SYSGEN SETS UP INCORRECT CONTROL FUNCTION BITS FOR CO:
SGNKLAB EXITS WITH UNDEFINED SYMBOL ERRORS
DUDRV GETS TASK BUILD ERROR IF TWO CONTROLLERS
SYSGEN DOES NOT HANDLE OVERFLOW CORRECTLY
AUTOCONFIGURE DOES NOT SKIP CONTROLLER IDS, G, I, O, AND 0
DHUll SUPPORT, DHVll CHANGE
IMPROVE TEST FOR CORRECTLY INSTALLED KIT
CHANGE TO SPM-11 TEXT
SYSGEN ON A VAX/VMS HOST
STARTUP HANDLES DAPRES INCORRECTLY ON RL02
CRASH MESSAGE DISPLAYS PHYSICAL, NOT LOGICAL, UNIT NUMBER

Component

Sequence

Mon/Yr

EXECUTIVE
DIRECTIVES
$IODON DOES NOT CHECK FOR s.KRB~o
GSSW$ CRASHED SYSTEMS WITHOUT SWITCH REGISTER

2.1.1.1 M
2.1.1.2 R

Jul 85
Jan 86

LOADR
LOADR MAY CRASH SYSTEM WHEN LOADING I- AND D-SPACE TASKS
DRIVER WITH A CLOCK BLK IN THE CTB CRASHES THE SYSTEM

2.1.5.1 F
2.1.5.2 M

Aug 85
Feb 86

MISC ROUTINES
PROBLEMS SPAWNING TASKS
INVALID CACHE PARITY ERROR REGISTERS GIVEN TO ERRLOG
PARITY ERROR ON BLOCK BOUNDARY CAUSES FIXER TO BANG
BARD/SOFTWARE LIMIT OFFSETS IN ERRLOG DEV UCB ARE REVERSED
CANNOT PROPERLY CRASH TO MM; DEVICE ON PDP-11/24

2.1.6.2 M
2.1.6.3 M
2.1.6.4 M
2.1.6.5 N

JUl 84
Jul 84
Aug 84
Apr 85

MCR
MCR
ALLOW •.1• COMMENTS AFTER 0 ENABLE DATA TO BE PASSED
OCL HELP COMMAND PASSES COMMENT STRING TO MCR

2.2.0.1 M
2.2.0.2 N

Aug 84
Jul 85

INTERNAL CMDS
DISK OPT FAIRNESS COUNT DISPLAY IS SOMETIMES WRONG
ASN PPNN:= DOES NOT GIVE SYNTAX ERROR
SET /CLI COMMAND FAILS IN NONPRIVILEGED BATCH JOB
SET /HOLD DOES NOT WORK ON VT100 TERMINAL

2.2.1.1 N
2.2.1.2 M
2.2.1.3 N
2.2.1.4 N

Feb 85
Jun 85
Jun 85
oec 85

INS
INS FAILS TO INSTALL LARGE TASKS WITH VIRTUAL ARRAYS
INS DOES NOT CORRECTLY CHECK ADDRESS BOUNDS FOR I/D TASK
INS INCORRECTLY CALCULATES D-ROOT OFFSET
INSTALL FAILS UNEXPECTEDLY PROCESSING $XXX
INS ERROR WITH SOME TASKS LINKED TO CLUSTER
INS FAILS TO INSTALL CERTAIN I/D TASKS
SYSTEM CRASH RUNNING /ID/MU TASK WITH EMPTY RO,D PORTION

2.2.2.1 M
2.2.2.2 M
2.2.2.3 M
2.2.2.4 M
2.2.2.5 M
2.2.2.6 M
2.2.2.7 M

83
83
Jan 84
Mar 84
Jul 84
NOV 84
May 85

INDIRECT
INDIRECT GIVES INVERTED OUTCOME OF .IFLOA OR .IFNLOA
SEVERAL PROBLEMS WITH INDIRECT
ICM FORMAT CONTROL FOR RIGHT/LEFT JUSTIFY DOES NOT WORK
.TESTFILE DOES NOT WORK ON A MODULE WITHIN A LIBRARY
INDIRECT MAY CONFUSE IDENTICAL LABELS
LBR LOOKS FOR INDINDEX IN WRONG UIC
MULTIPLE PARAMETERS TO .ENABLE /.DISABLE
ALLOW •1• COMMENTS ON 0 SETO AND 0 SETD
.CHAIN LOSES CONTEXT
F.FFBY FIELD OF <FILATR> LIST SHOULD BE A WORD
FINAL DELIMITER NOT INCLUDED IN LAST SYMBOL
INDIRECT FAILS AFTER UPDATE D
<FILSPC> IS SOMETIMES CORRUPTED
ICP FORMAT CONTROL RIGHT/LEFT JUSTIFY DOESN'T WORK
, A DEFINES A AS •1,2•

2.2.3.1 M
2.2.3.2 M
2.2.3o3 M
2.2.3.4 M
2.2.3.5 R
2.2.3.6 M
2.2.3.7 M
2.2.3.8 M
2.2.3.9 M
2.2.3.10 M
2.2.3.11 M
2.2.3.12 M
2.2.3.13 M
2.2.3.14 N
2.2.3.15 R

NOV 83
Mar 84
Mar 84
Apr 84
Apr 84
JUn 84
Jun 84
Jul 84
Jul 84
Aug 84
Aug 84
Feb 85
Mar 85
Mar 85
Aug 85

100

Jan 84

Dec

(

Component

sequence

Mon/Yr

TIMING PROBLEM WITH .XOT AND .WAIT FROM OCL TERMINAL
RESTRICTION ON .TEST WITH LOWERCASE CHARACTERS
PRO HOST TOOL KIT INSTALLATION PROCEDURE BROKE
INVALID CHARACTERS IN SUBSTITUTION SYMBOL NAMES
PROBLEMS WITH LOCAL SYMBOLS IN GLOBAL NAME FORMAT
.EXIT DIRECTIVE WITHIN BEGIN-END BLOCK
INDIRECT COMMAND 0 SETT <ERSEEN> LEAVES IT FALSE
24-HOUR MAXIMUM FOR .DELAY DIRECTIVE
DEFAULT RADIX FOR INDIRECT SUBSTITUTION FORMAT CONTROL
ERROR IN EXECUTION OF @/LB:MODULE FROM MCR OR COMMAND FILE

2.2.3.16 R
2.2.3.17 R
2.2.3.18 M
2.2.3.19 M
2.2.3.20 M
2.2.3.21 M
2.2.3.22 M
2.2.3.23 M
2.2.3.24 M
2.2.3.25 M

Sep 85
oct 85
oct 85
NOV 85
Apr 86
NOV 85
NOV 85
Jan 86
Feb 86
Mar 86

BASIC MCR
CO: DCB CORRUPTION IF COT NOT ACTIVE

2.2.4.1 M

Mar 84

VMR
VMR DOES NOT CHECK FOR OTHER COPIES OF A MULTIUSER TASK
VMR CANNOT INSTALL SOME I/D TASKS
SECPOL PERCENTAGE WRONG FOR LARGE SECONDARY POOL
SET /NOTYPEAHEAD CAUSES CRASH

2.2.5.1 M
2.2.5.2 M
2.2.5.3 M
2.2.5.4 M

Mar 84
Aug 84
Sep 84
Apr 86

SAV/BOO
SAV HANGS IF SYSTEM IMAGE TOO LARGE
SAV SIZES A MAXIMUM MEMORY CONFIGURATION INCORRECTLY
BOOT HANGS ON COPY OF A SYSTEM SAVED ON DIFFERENT CONTROLLER
MEMORY IS NOT SIZED CORRECTLY ON AN 11/44 WITH 4 MB OF MEMORY
SAV CRASHES WHEN SYSTEM DISK IS A DUAL-ACCESS DEVICE

2.2.6.1 M
2.2.6.2 M
2.2.6.3 M
2.2.6.4 M
2.2.6.5 M

Jan 84
Mar 84
Mar 84
Feb 86
Apr 86

3.1.1.2 M
3.1.1.3 M
3.1.1.4 M
3.1.1.5 M
3.1.1.6 M
3.1.1.7 M

oec 83
Jan 84
Mar 84
Apr 84
Jun 84
Jul 85

3.1.3.1 F
3.1.3.2 M
3.1.3.3 M
3.1.3.4 M
3.1.3.5 M
3.1.3.6 N

oec 83
Mar 84
Sep 84
Mar 85
Mar 85
Mar 85

FIX RCL, MOVE LABEL, ADD DOCUMENTATION
PATCH HB034 CAUSES SYSTEM CRASHES

3.1.4.1 M
3.1.4.2 M

Mar 84
Mar 84

CODRV
CONSOLE DRIVER MAY CRASH SYSTEM DURING LOW POOL CONDITIONS

3.1.6.1 M

Mar 84

DRIVERS

DUDRV, DYDRV
DU DRIVER INHIBITS TERMINAL TIMEOUTS
RX02 SUPPORT FOR 22 BIT QBUS SYSTEMS
DO MULTIPLE FORKS, DO NOT ALWAYS BUFFER DATA INTO DYCOM
DUDRV MODIFICATIONS :ERROR RECOVERY, UNIT FAIRNESS
WHEN POWER IS OFF OF RX02, ANY I/O TO RX02 WILL CRASH
RSX SLOWS DOWN ON Micro/PDP-11

FDX-TTDRV
SLAVED TERMINAL DIFFERENCE IN NEW RELEASE
REMOTE LINE HANGS UP WHILE CHANGING CHARACTERISTICS
SYSTEM CRASHES IF DMll-BB DEV SYSGENNED BUT NOT INSTALLED
TC.EPA AND TC.PAR CANNOT BE SET FOR DHll
ABORTING DHVll CURRENT OUTPUT DISABLES TERMINAL I/O
DTR IS NOT ASSERTED UNTIL RING IS DETECTED

LADRV

('
101

sequence

Mon/tr

FCS .EXTND AND TRUNCATION

3.2.1.1 N

Jan 84

MTAACP/FllMSG
MOUNT REPORTS WRONG ERROR FOR OFFLINE TAPE
MT.AACP BANGS/CRASHES SYSTEM

3.2.3.1 M
3.2.3.2 M

Jan 84

Collponent

FILE SYSTEM

FCS

ERROR LOGGING
RPT
FILE READ ERROR ON RP038
LBN BAD FOR RL01/RL02 DISKS FROM ERRLOG

JUn 84

...
)

0 3 0 4 0 1

oac 83

Mar 84

COllTROL FILES
V2o1 RPT ABORTS ON RASO ERROR

3.3.5.1 N

Jan 84

BATCH/QUEUE MGR
BPR
BATCH PROCESSOR EXITS WREN JOB ABORTED
BPR GIVES CRYPTIC ERROR MSG. WHEN FILE IS EDITED AND PURGED

4.1.1.1 M
4.1.1.2 M

Sep 84
Mar 86

STOP:AB DELETES FILES INSTEAD OF PUTTING THEM IN HELD STATE
QMG DOESN'T STOP SPOOLED LINE PRINTER PROPERLY
QUEUE /EN:xxxx ERROR MESSAGE INCONSISTENT
QUEUE PRODUCES ERROR ON ASSIGN OF QUEUE WITH 1 OR 2 CHARS
QUE /EN:NNN/BO ABORTS AN ACTIVE BATCH JOB
SUBMIT /[NO]TR COMMAND PRODUCES ERROR MESSAGE
QUE HANGS IF UFO [1,7) IS NOT PRESENT

4.1.3.1 N
4.1.3 .2 N
4.1.3.3 M
4.1.3.4 M
4.1.3.5 M
4.1.3.6 M
4.1.3.7 N

NOV 83
Jan 84
Apr 84
Apr 84
JUD 84
Sep 84
Apr 85

OUB/PRI
BATCH JOBS COPIED FROM PRIVATE DISK TO LB:[l,7] NOT DELETED
SHOW QUEUE SOMETIMES BANGS
LPP INCORRECTLY DELETES FILE BY FILE ID

4.1.4.1 M
4.1.4.2 M
4.1.4.3 M

sep 84
oec 84
Jan 85

LPP
IF USER WRITTEN DEL CHECK ROUTINE USED PRI/DE DOESN'T DELETE
PROBLEM WITH SIMULATED FORMS AND FORMFEEDS
LA100 DEVICE SUPPORT ADDED TO DESPOOLER BAS 2 PROBLEMS
FILE WITH AN ILLEGAL RECORD SIZE WILL BANG IN QUEUE
NLO SHOULD NOT BE SPOOLABLE
LPP LOOPS ON NEGATIVE RECORD LENGTH

4.1.5.1 N
4.1.5.2 N
4.1.5.3 M
4.1.5.4 M
4.1.5.5 M
4.1.5.6 M

NOV 83

QllG

Jan 84
Mar 84
Apr 84
Apr 84
Apr 86

•

MULTIUSER TASK

BYB
BYE SOMETIMES REPORTS WRONG CPU TIME USED

NOV 84

SBUTUP
SHUT UPP ODD ADDRESS TRAPS IF FIRST CHAR OF DEVICE NAME IS ODD

4o2e5ol M

Mar 84

l
102

Component

sequence

Mon/Yr

ACCOUNTING
ACCOUNTING
START/ACC WITH NL: TRANSACTION FILE CRASHES THE SYSTEM
ACCOUNTING NOT STARTED CORRECTLY

4.3.0.1 R
4.3.1.1 M

Jan 84
Mar 84

SHADOW RECORDING
SHADOW RECORDING
SHADOW RECORDING DOESN'T WORK ON SINGLE SCB CONTROLLERS

4.4.0.1 R

Apr 84

SHADOW RECORDING WORKS ON DU: DEVICES

4.4.1.1 N

Jun 85

UTILITIES
CRP
CRF EXITS IF A SYMBOL IS REFERENCED TOO MANY TIMES

5.1.3.1 M

Jan 84

DMP
ANSI MAGTAPES AND DMP

5.1.5.1 R

Jan 84

PLX
ENDLESS •DEVICE HANDLER MISSING• MESSAGES FROM FLX
FLX ABORTS ON COMMAND FOLLOWING •ILLEGAL SWITCH• MESSAGE
FLX DOES NOT SUPPORT DU:

5.1.7.1 M
5.1.7.2 M
5.1.7.3 M

Jan 84
Jan 84
Jan 84

INI
INI CANNOT USE /INDEXzEND SWITCH WITH LAST TRACK DEVICES

5.1.8.1 M

Sep 85

MOU
MOUNT X:/FOR/ACP•UNIOUE CRASHES SYSTEM
BOOTING DU SYSTEM DISK CAUSES EXTRA MESSAGE

5.1.10.1 N
5.1.10.2 M

Jan 84
May 85

PIP
DELETING FILES, JO DOES NOT ALWAYS WORK PROPERLY

5.1.12.1 M

Feb 86

BRU
ERRORS OCCUR ON MULTI-DISK RESTORE TO MOUNTED DISK
BRU INCORRECTLY HANDLES EXTENSION HEADERS AND 32,000 FILES
BRU /VER ABORTS ON THIRD TAPE WITH LARGE MULTIHEADER FILES
BRU ABORTS WITH I/O ERROR -10 ON RESTORES
BRU ERROR RECOVERY DURING A BACKUP TO TAPE
IMPROPER ERROR RECOVERY DURING A DISK-TO-TAPE BACKUP
BRU /IMAGE1RESTORE TO A MOUNTED DISK IGNORES /BACKUP__SET
BRU DOESN'T VERIFY ALL TAPES IN A BACKUP SET BEFORE STOPPING
BRU /BAD:MANUAL DOES NOT WORK AS DOCUMENTED
CANNOT DO SELECTIVE BACKUP/RESTORE WITH BRUSYS V3.0
BRU--MISLEADING ERROR MESSAGE/ACTION FOR UNMOUNTED TAPES

5.1.11.1 M
5.1.11.2 M
5.1.11.3 M
5.1.17.4 M
5.1.11.5 M
5.1.11.6 M
5.1.17.7 R
5.1.11.8 N
5.1.17.9 M
5.1.17.10 M
5.1.17.11 N

oec 83

PMT
RK07 GETS •DEVICE NOT READY• WHEN BEING FORMATTED

5.1.18.1 N

SHA

(
103

Jul 84
Apr 85
Apr 85
May 85
May 85

Jun 85
JUl 85
Sep 85
Feb 86
Feb 86

Aug 85

Component

sequence

Mon/Yr

SYSTEM LIBRARIES
IC-SERIES
A/D IS NOT ENABLED IF NO KW-11 IN SYSTEM

5.2.5.1 M

Apr 84

MISC SYSLIB
SYSLIB MODULE $CBASG DROPS MSD

5.2.6.1 N

Feb 85

TASK BUILDER
TKB
SEVERAL M-PLUS TKB PROBLEMS
TKB •vsECT' OPTION DOES NOT WORK CORRECTLY
TKB FAILS TO BUILD TASK WHICH IS 1 WORD LARGER
READ ONLY AND READ WRITE CLUSTERING
TKB CANNOT BUILD I/D TASK W/24K I-SPACE & VSECTS W/COMMON
NOTES REGARDING CLUSTER LIBRARY USE
TKB OFTEN CREATES MULTIPLE AUTOLOAD VECTORS FOR SAME SYMBOL
TKB CAN'T LINK SHARED REGIONS TOGETHER IF USING SYS PARTITION
MULTIPLE REFERENCES TO .PSECT IN SEGMENT CAUSES TKB TO ABORT
TKB SWITCHES /LI AND /CO DO NOT WORK AS DOCUMENTED
TKB CORRUPTING VIRTUAL MEMORY UNDER RARE CONDITIONS

5.3.1.1 M
5.3.1.2 M
5.3.1.3 N
5.3.1.4 R
5.3.1.5 M
5.3.1.6 M
5.3.1.7 M
5.3.1.8 M
5.3.1.9 M
5.3.1.10 N
5.3.1.11 M

NOV 83
NOV 83
Jan 84
Mar 84
Mar 84
JUn 84
Aug 84
oct 84
oct 85
NOV 85
Apr 86

FTB
FTB PRINTS GARBLED SYMBOL NAME AND MODULE NAME

5.3.2.1 M

NOV 83

STK CANNOT BUILD LARGE HEAVILY O'LAYED TASK CORRECTLY

5.3.3.1 M

Mar 84

5.5.1.1. M

Jan 86

DEBUGGING AIDS
ODT

TASK WITH LARGE NUMBER OF LUNS HANGS IN ODT
EDITORS
SLP
SLPRll DOESN'T REPORT EXIT STATUS ON CHECKSUM FAILURE

oec 83

MISC SYS TASKS
HELP
HELP KEYWORDS DO NOT ACCEPT DEVICE NUMBERS HIGHER THAN 7
HELP /OUT:TTNN: <PARAMETER> DOES NOT WORK

5.1.1.1 M
5.1.1.2 N

Apr 84
Feb 86

CDA
CDA ODD ADDRESS TRAP ON ADDRESS OUT OF RANGE
CDA /DENS SWITCH GIVES SYNTAX ERROR
CDA /MEMSIZ SWITCH EXTENDS FILE TOO FAR
CDA DOES NOT OUTPUT LAST WORD OF ERRLOG BUFFERS
CDA DOES NOT ALLOW MS: TO FINISH REWINDING
CDA DOES NOT DISPLAY L.ICB FOR CONTROLLER TABLE BLOCKS

5.1.2.1 M
5.1.2.2 M
5.1.2.3 M
5.1.2.4 M
5.1.2.5 M
5.7.2.6 M

Apr 84
Aug 84
Jul 85
JUl 85
JUl 85
Feb 86

RM DEMO
RMDEMO IN/OUT STATISTICS INCORRECT
AVERAGES ON S PAGE CLOBBERED WHEN SWITCH TO COMMAND PAGE
RUNNING RMD FROM CLOCK QUEUE DOES NOT WORK CORRECTLY
UPDATE C OF RMDEMO I/O PAGE MAY CAUSE SYSTEM CRASH

5.7.5.1 M
5.7.5.2 M
5.7.5.3 M
5.7.5.4 M

Jan 84
Jan 84
Apr 84
oct 84

104

(

Component

Sequence

Mon/yr

RMD DOES NOT SHOW PARTITIONS BELOW 32K
RMD I/O HARD/SOFT ERROR LIMITS ARE REVERSED

5.7.5.5 M
5.7.5.6 N

Apr 85
Jul 85

TDX
TDX PROBLEMS FIXED IN UPDATE C
CVT DOES NOT WORK FROM A COMMAND FILE
FLYING INDIRECT DOES NOT WORK WHEN SY: CHANGES

5.7.7.1 M
5.7.7.2 M
5.7.7.3 M

Jan 84
Apr 84
Jun 84

COT
COT. 00 ABORTS WITH ODD ADDRESS TRAP

5.7.14.1 N

Jun 84

RCT
RCT PROBLEMS

5.7.15.1 M

oec 83

DCL
DCL
VARIOUS SYNTAX PROBLEMS IN DCL FIXED IN UPDATE B
/NOJOURNAL DOESN'T WORK FOR DCL EDIT/EDT
DCL 'STOP/ABORT' COMMAND FAILS WITH 'STOP WHAT?' MESSAGE
RMSCNV / PD SWITCH TAKES ASCII 0 TO 7 AS OCTAL NUMBER
LINK COMMAND DELETES INTERMEDIATE FILE TOO SOON
DCL FORTRAN COMMAND LISTING SWITCHES DO NOT WORK
VARIOUS PROBLEMS IN DCL FIXED IN UPDATE C
DCL INCORRECTLY TRANSLATES STOP/QUEUE/MANAGER/ABORT
DCL DOES NOT ACCEPT BAC @FILESPEC SYNTAX
NEW DCL COMMANDS FOR DECNET SNA SUPPORT
DCL DOES NOT ALWAYS DETECT A FILE SPEC ERROR
DCL PROBLEMS WITH NETWORK NODE SPECIFICATIONS
SET DEVICE/SYSTEM AND DCL COBOI./CLI PROBLEMS
•MOUNT/DENS=800 DD:• TRANSLATES TO MOU DD:/DENS=800.
DCI./ATT/OUT=FILESPEC DOES NOT PLACE OUTPUT IN FILESPEC
DCL SE DE ABBREVIATION AMBIGUOUS
DCL LINK /OPTION:FILESPEC NOT ACCEPTED AS VALID SYNTAX
DCL DELETE [*,*) FILESPEC DOESN'T WORK FOR UPDATE C
"DCL LIBRARY/CREATE LIBRARYSPEC• PROMPTS FOR INPUT MODULES
DCL SUBMIT/NOPRINT DOES NOT WORK CORRECTLY WITH UPDATE D
DCL FORTRAN/NOF77 SHOULD NOT ALSO REQUIRE /F77
•1• AT BEGINNING OF QUOTED STRING IS STILL TREATED AS COMMENT
ADD /[NO)WARNINGS QUALIFIER TO DCL PRINT AND SUBMIT COMMANDS
CREATE/DIR/ALL=NUM. DOES NOT TRANSLATE DECIMAL POINT
CERTAIN DCL SUBMIT QUALIFIERS DO NOT WORK WITH UPDATE D
DCL DOES NOT WORK AS A CATCHALL FOR MCR
SET ACCOUNTING DOES NOT WORK IN DCL
PURGE/KEEP:N/NOLOG FILE TRANSLATES TO PIP/SB•FILE/PU:N
RUN /DELAY:N DOES NOT WORK WITH THE /STATUS:TASK QUALIFIER
DCL START/PRINTER LPN:/PAGE:N DOES NOT WORK
DCL CONVERTS CERTAIN SPECIAL CHARACTERS INCORRECTLY
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @FILESPEC• DOES NOT WORK

6.1.0.1 M
6.1.0.2 M
6.1.0.3 M
6.1.0.4 N
6.1.0.5 M
6.1.0.6 M
6.1.0.7 M
6.1.0.8 M
6.1.0.9 M
6.1.0.10 M
6.1.0.11 M
6.1.0.12 M
6.1.0.13 M
6.1.0.14 M
6.1.0.15 M
6.1.0.16 M
6.1.0.17 M
6.1.0.18 M
6.1.0.19 M
6.1.0.20 M
6.1.0.21 M
6.1.0.22 M
6.1.0.23 M
6.1.0.24 N
6.1.0.25 M
6.1.0.26 N
6.1.0.27 N
6.1.0.28 N
6.1.0.29 N
6.1.0.30 N
6.1.0.31 N
6.1.0.32 M
6.1.0.33 M

83
83
oec 83
oec 83
Jan 84
Jan 84
Mar 84
Mar 84
Mar 84
JUn 84
Jun 84
JUn 84
Jul 84
Aug 84
Aug 84
NOV 84
NOV 84
oec 84
Jan 85
Jan 85
Jan 85
Jan 85
Jan 85
Mar 85
Apr 85
Jun 85
Jun 85
JUn 85
Jul 85
Jul 85
Jul 85
Jan 86
Jan 86

(
105

NOV
NOV

Component

Sequence

Mon/Yr

10.5.4.1 N

oec 85

PDP-11 FORTRAN-77/RSX V5.0
UNFORMATTED SEQUENTIAL WRITE ERRORS AFTER APPLYING UPDATE E

SORT/MERGE V3 • 0
PACKAGE NOTES
ANNOUNCING PDP-11 SORT/MERGE V3.0

May 84
RMs-11 v2.o

SUMMARY OF RMS-11 MODIFICATIONS SINCE DISTRIBUTION ON RSX-llM-PLUS
SUMMARY OF RMS-11 MODIFICATIONS ON RSX-llM-PLUS FOR UPDATE E
INDEX FILE CORRUPTION IN ALTERNATE KEY PATH
CORRUPTION IN VERY LARGE FILES

10.7.1.1 N
10.7.1.2 N
10.7.1.3 M
10.7.1.4 M

Aug 84
Feb 85

10.8.2.2 N
10.0.2.3 N
10.0.2.4
10.0.2.5 N
10.0.2.6 N
10.0.2.1 N
10.0.2.8 N
10.0.2.9 N
10.8.2.10 N
10.8.2.11 N
10.0.2.12 N
10.8.2.n N

NOV 83
NOV 83

APr 86
Sep 85

DEcnet-llM-PLUS Vl.1
RSX DECnet PROGRAMMER'S REFERENCE MANUAL CORRECTIONS
RSX DECNET SYSTEM MANAGER'S GUIDE CORRECTION
UNASSIGNED
TIPS ON SUBMITTING A DECnet SPR
INCORRECT FORMAT FOR NCP SHOW MODULE X25-PROTOCOL
THE MICROFICHE FOR RSX DECnet 3.1/1.1 IS NO LONGER RESTRICTED
DLX TASKS MUST NOT HAVE EXTERNAL HEADERS
HOW TO WRITE A NETWORK SPR
DECnet-llM-PLUS PROBLEMS FIXED ON RSX-llM-PLUS LAYERED UPDATE A
DECnet AUTOPATCH MAY NOT APPLY ALL PATCHES
DECnet-llM-PLUS PROBLEMS FIXED ON RSX-llM-PLUS LAYERED UPDATE B
DECnet-llM-PLUS PROBLEMS FIXED ON RSX-llM-PLUS LAYERED UPDATE C

xxx xx
NOV 83
Nov 83
NOV 83
NOV 83
NOV 83
NOV 83
NOV 83
NOV 83
Mar 84

DEcnet-llM-PLUS v2.o
DEcnet-llM-PLUS PROBLEMS FIXED ON RSX-llM-PLUS LAYERED UPDATE E
PERFORMING A DECnet-llS V4.0 NETGEN ON A VMS V4.0 HOST
FAL ABORTS WITH ·T-bit trap or BPT. ERROR

10.8.3.1 N
10.8.3.2 N
10.8.3.3 N

oec 84
oec 84
Jul 85

10.14.4.26 M
10.14.4.27 M
10.14.4.28 M
10.14.4.29 M

Jun 83
JUn 83
Jun 83
JUn 83

10.15.1.1 N
10.15.1.2 N
10.15.1.3 M
10.15.1.4 M

oec 83
oec 83
oec 83
Feb 84

DATATRIEVE-11 V2.4
KEYED OR BOOLEAN
QDICT MAY NOT CREATE A QUERY DICTIONARY
CHANGES TO SUPPORT RMS v2.o
REQUIRED PATCHES FOR DATATRIEVE-11
DATATRIEVE-11 V3.0
ANNOUNCING DATATRIEVE-11 VERSION 3
NEW DATA DICTIONARY FOR VERSION 3
PROBLEM WITH REDEFINES
RMS v2.o CHANGE TO DATATRIEVE-11 V3.0

106

OOllponent

sequence

Mon/tr

ns-11/RSX v1.o

PDV
FMS TERMINAL SUPPORT PATCHES

May 84

BASIC-PLUS-2 V2.1

•

PACUGI ROTBS
PDP-11 BASIC-PLUS-2 V2.1 NOW AVAILABLE

JUD 83

BASIC-PLUS-2 V2.2
PACUGI llOTIS
BASIC-PLUS-2 V2.2 TO SHIP IN MARCH

Apr

10.20.1.1 N

l)eC

PDP-11 CORAL 66 V4.0
GIRIRAL
ANNOUNCEMENT OF PDP-11 CORAL 66 V4.0
PROCEDURE POR INSTALLATION OP PATCBBS ON PDP-11 CORAL 66 V4.0

11.S.1.1 N
11.S.1.2 N

APr 84
APr 84

COllPILER
ARRAY INDBX INCORRECTLY COMPUTED SOMETIMES
ERROR IN FLOATING POINT OPTIMIZATION
'UNION' OPERATOR CAN CAUSE COMPILER TO ABORT
DIVISION BY ONE CAN GENERATE INCORRECT CODE
OBJECT CODE PRINT CAN CAUSE PRINTER FORMAT ERRORS
ABNORMAL TERMINATION OP COMPILER IP SOURCE TOO BIG
ARRAY PARAMETERS CAN CAUSE ERROR 189

11.S.2.1 M
11.S.2.2 M
11.S.2.3 M
11.S.2.4 M
11.s.2.s M
11.S.2.6 M
11.S.2.7 M

APr 84
APr 84
A.pr 84
APr 84
.Apr 84
APr 84
.Apr 84

BASIC-PLUS-2 V2.3
PROBLEM WITH PRINT USING
PDP-11 CORAL V4.0

coeo1.-u v2.o
PACUGE llOTIS
ANNOUNCING COBOL-81 VERSION 2.0

Jun 83

•
SPll-1111-PLUS V2e1
GDBRAL NOTES
ANNOUNCING SPM-11M-PLUS VERSION 2.1

sep 84
PDP-11 llPG II V8 • 8

(

ANNOUNCEMENT OP PDP-11 RPG II vs.a

14.1.1.1 N

107

NOV 83

Component

sequence

Mon/Yr

RSX-llM-PLUS DIBOL Vl.O
DOCUMENTATION
CORRECTION NOTE TO DIBOL-83 LANGUAGE REFERENCE MANUAL

15ololol M

Jul 84

16ololol N

oec 85

FORTRAN IV/RSX V2 06
OTS
LIST-DIRECTED READ

•

DEClllail-11 V2 • 0
GENERAL NOTES
ANNOUNCING DEOnail-11 v2.o FOR RSX-llM-PLUS v2.1

17.1.1.1 N

Sep 84

18.1.1.1 N

Apr 86

PDP-11 SYMBOLIC DEBUGGER v2.o
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER v2.o

108

RSX-11 M-PLUS V3.0

•

109

•

RSX Software Dispatch, April 1986

Seq. No. 1.1.0.l M

RSX-llM-PLUS V3.0
SYSGEN
SYS GEN

1 of 1

AUTOCONFIGURE DOES NOT PASS MULTIPLE T(MSCP) INFO TO SYSGEN (SPR ll-00191X GNL)
PROBLEM
STATEMENT:
If a system has multiple MSCP/TMSCP controllers, Autoconfigure does not pass
this information to SYSGEN. During a SYSGEN, if a user selects Autoconfigure
and wants more than one MSCP/TMSCP controller generated in, it is necessary to
override Autoconfigure results and manually enter the information, which has
potential for getting erroneous CSRs and vectors in the system for those
devices.
RESPONSE:
The information for multiple (T)MSCP controllers, those at the floating CSRs,
was not previously recorded in the Autoconfigure data file CONFIG.DAT.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update B.

(
111

•

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
SYS GEN
AUTOCONFIGURE

Seq. No. 1.1.1.l M
1 of 1

ACF MAY NOT CORRECTLY SET UP DV.NUC IN CONFIG.DAT FOR RS03/4s
(SPR 11-P00211X CS)
PROBLEM
STATEMENT:

(

Autoconfigure (ACF) may not correctly set up DV.NUC in the CONFIG.DAT file for
RS03/4 devices.
RESPONSE:
This problem occurs if the RS03/4 device does not have the
register implemented, as allowed by the MASSBUS specification.

Serial

Number

(
113

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
EXECUTIVE
DIRECTIVES

Seq. No. 2.1.1.2 R
1 of 1

GSSW$ CRASHES SYSTEMS WITH NO SWITCH REGISTER (SPR ll-00194X LBM)
PROBLEM
STATEMENT:
The GSSW$ directive (get sense switches) on PDP-11/73 and PDP-11/84 processors
crashes the system.
RESPONSE:
In the past, when all RSX systems required a customized SYSGEN, Executives
generated for processors without switch registers did not include support for
the GSSW$ directive. Also, some hardware implementations returned some more
or less meaningful value, even if there was no switch register, instead of
trapping with a Q-bus or UNIBUS time-out error.
With the elimination of customized SYSGENs (for user friendliness), the GSSW$
directive code may now be included in Executives running on systems without
switch registers. Some of these systems respond with a Q-bus or UNIBUS
time-out error to references addressing the nonexistent switch register. The
Executive quite rightly interprets the resulting trap in system state as being
indicative
of a software fault (in this case, attempting to address
nonexistent hardware), and crashes the system. In fact, issuing the GSSW$
directive on hardware without a switch register should not cause a system
crash. The GSSW$ directive code will be enhanced in a future update to
preclude this from happening. In the meantime, the obvious workaround is to
refrain from issuing the GSSW$ directive on hardware having no switch
register.

(
115

(

RSX Software Dispatch, April 1986

Seq. No. 2.1.s.1 M

RSX-llM-PLUS V3.0
EXECUTIVE
LOADR

1 of 1

DRIVER WITH A CLOCK BLOCK IN THE CTB CRASHES THE SYSTEM (SPR 11--00192X GM)
PROBLEM
STATEMENT:
When reloaded, a user-written driver with a clock block in the CTB crashes the
system.

f
RESPONSE:
The above problem is the result of an error in the module LDFIN.MAC, where the
pointer to clock queue block is set incorrectly.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update B.
please avoid setting the clock block in the CTB.

(
117

Until

then,

(

RSX Software Dispatch, April 1986

Seq. No. 2.2.1.2 M

RSX-llM-PLUS V3.0
MCR
INTERNAL CMDS

1 of 1

ASN COMMANDS WITH NULL LOGICALS CAUSE SYSTEM CRASH (SPR 11-00217X JK)
PROBLEM
STATEMENT:
The MCR ASN command causes a system crash if the logical
consists of a blank node name or blank device name.

name

being assigned

RESPONSE:
Since the ASN command strips off one or two colons from a logical name before
an assignment, the following commands will result in a null logical name and
cause an odd address system crash within the third directive connnon:
ASN eqv=:
ASN eqv=::
This problem is corrected in RSX-llM-PLUS Version 3.0 Update C.

(
119

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
MCR
INS

Seq. No. 2.2.2.1 M
1 of 1

NEW "TASK IMAGE I/O ERROR" MESSAGE FOR DEVICES (SPR 11-P00207X RC)
PROBLEM
STATEMENT:
INS aborts with the message "SYNTAX ERROR" for certain I/O errors returned
the driver.

(
121

..
...

(

RSX Software Dispatch, April 1986

Seq. No. 2.2.3.10 M

RSX-llM-PLUS V3.0
MCR
ICP

1 of 1

.ASK DOES NOT WORK AS DOCUMENTED WITH (ESC) RESPONSE (SPR 11-00200X LP)
PROBLEM
STATEMENT:
Entering <ESC) in response to an .ASK directive only sets the special logical
symbol <ESCAPE) to true. According to the RSX-llM-PLUS V3.0 MCR Operation~
Manual, pages 4-24 and 4-33, the logical symbol specified in the .ASK
directive should also be set to true.
RESPONSE:
The .ASK directive will be corrected in the next release so that it sets both
the specified logical symbol and the special logical symbol (ESCAPE) to true
when an <ESC) is entered.

(
123

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
MCR
INDIRECT

Seq. No. 2.2.3.11 M
1 of 2

ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES (SPR ll-P00213X RDH)
PROBLEM
STATEMENT:
The Indirect Command Processor allows definitions of global and local symbols
with the same name to exist on the same level. Also, it allows the individual
deletion of local symbols when they assume the global naming convention. This
is contradictory to the documentation.
The following command files demonstrate the problem:
A.CMD
.SETS $A "Howdie"
.SETS $B "Doodie"
@A2
.IFNDF $A .STOP
.IF $B NE 2 .STOP
.ERASE SYMBOL $B
.IF $B NE "Doodle" .STOP
.ERASE SYMBOL $B
.EXIT

local symbol $A
local symbol $B
ensure we are back on the correct level
this $B is global from A2.CMD
erases $B from global table
this $B is local from A.CMD
erases $B from local table

A2.CMD
.ENABLE GLOBAL
.SETN $B 2
.EXIT

enable global symbol processing
global symbol $B

RESPONSE:
The Indirect Command Processor and the documentation are consistent in
allowing global and local symbols with the same name to exist on the same
level. Using local symbol names beginning with the dollar sign ($) is not
recommended because of potential confusion with global symbols but is
permitted by Indirect. If global and local symbols with the same name exist
at a level, and reference is made to that symbol name, the global symbol takes
precedence over the local one for assignments, comparisons, etc.

124

....

(

RSX Software Dispatch, April 1986

Seq. No. 2.2.3.11 M

RSX-llM-PLUS V3.0
MCR
INDIRECT

2 of 2

The implementation of Indirect does allow the .ERASE SYMBOL to affect local
symbols if their name begins with the dollar sign, contrary to the documented
restriction that only
global
symbols
may
be
individually
erased.
Investigation of this problem shows that the restriction can be removed
without adverse impact.
Its removal would also eliminate the apparent
advantages of naming local symbols with dollar signs.
RSX-llM-PLUS Version 3.0 Update C includes a change which removes this
restriction. Specifically, the .ERASE SYMBOL directive will be able to erase
individual global or local symbols. If two symbols with the same name, one
global and one local, exist for the level on which the .ERASE SYMBOL is being
executed, the global symbol will take precedence and be erased.

(
125

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
MCR
INDIRECT

Seq. No. 2.2.3.12 M
I of 1

CORRUPTED BEGIN-END BLOCK POINTERS IN LOCAL SYMBOL TABLE (SPR ll-P00214X RDH)
PROBLEM
STATEMENT:
Both .SETS assignments to local string symbols and .ERASE LOCAL directives can
cause memory protect violations or Illegal Nesting errors when executed from
within Begin-End blocks or from files invoked with the /LO switch.
RESPONSE:
Begin-End blocking context, which is stored in the Local Symbol Table as
special frames, includes pointers to the start of the next-higher symbol
block. The pointers are not correctly maintained when a .SETS is executed on
a string symbol that is outside the current Begin-End block but still within
the current Local Symbol Table range, for example, a local symbol defined at a
higher level of Begin-End block.
If the .SETS changes the length of the
string, a Memory Protect violation may occur when the task exits.
In a similar manner, execution of the .ERASE LOCAL directive from the
beginning block level of a file which was invoked with the /LO switch will
corrupt the Begin-End block pointers, resulting in an Illegal Nesting error.
These failures can be avoided by:
1.

Do not modify higher-level local string symbols from within Begin-End
blocks.
If you need to implement this functionality, define the
string symbol as global.

RSX-llM-PLUS Version 3.0 Update C includes corrections for these problems.

'
126

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
MCR
SAV

Seq. No. 2.2.6.3 M
1 of 1

SAV DOES NOT SIZE MEMORY CORRECTLY ON UNIBUS SYSTEMS (SPR ll-P00199X KF)
PROBLEM
STATEMENT:
SAV does not size memory correctly on
memory.

UNIBUS

systems

with

megabytes

RESPONSE:
UNIBUS systems experience this problem when they have between 1920kW and
2048kW (4 MB) of main memory. The UNIBUS Map maps addresses between 1920kW
and 2044kW back to main memory, leaving the top 4kW for the I/O page.
Please
refer to Figure 6-26, page 162, of the PDP-11 Processor Handbook. When SAV
sizes memory, it clears memory until it traps because of nonexistent memory.
In this case, SAV does not discover nonexistent memory at the UNIBUS addresses
because the UMRs point back to low memory.
Therefore, low memory ends up
being cleared. The system will crash when it tries to start backup. Notice,
because of the UNIBUS, SAV is correct in sizing memory to 1920kW, even though
there are up to 4 megabytes of main memory in the system.

This problem is corrected in RSX-llM-PLUS Version 3.0 Update B. Until
then, size the system image file so it is even and not divisible by 4. This
causes SAV to start on the correct boundary when sizing memory. In this way,
SAV will not attempt to access the UNIBUS addresses, therefore, low memory
will not be cleared.

(
127

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
MCR
SAV

Seq. No. 2.2.6.4 M
1 of 1

SAV CRASHES WHEN SYSTEM DISK IS A DUAL-ACCESS DEVICE (SPR ll-00216X KF)
PROBLEM
STATEMENT:
When SAVing a virgin system following system generation, the system crashes
with an odd address trap. The system device is dual access between two RH
controllers.
RESPONSE:
The system crash occurs when trying to access the second RH controller of your
system disk.
When SAV brings the system down, it sets the system device and
its controllers off line. The system device is necessarily on line.
One of
its controllers must also be on line for the system to work. In the case of a
dual-access device, the second controller does not have to be on line
or physically in the system. SAV fails to check the controller to see if it
is there before it accesses its control and status register (CSR) address in
memory. Since the controller is not there in this case, accessing this
location causes the system to crash. Since the system has been generated with
XDT, when the XDT prompt appears on the console, typing G will make the system
proceed as if nothing were wrong. The crash does not corrupt the system in
any way.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update c. Until then,
when SAVing your system, type G to the XDT prompt and your system will
start up. This problem will not occur if the second RH controller is
installed properly. Check the switches on the controller to be sure they are
set for the correct CSR address.

128

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
BATCH/QUEUE MGR
BPR

Seq. No. 4.1.1.1 M
1 of 1

BPR GIVES CRYPTIC ERROR MESSAGE WHEN FILE IS DELETED (SPR 11-00198X DR)
PROBLEM
STATEMENT:
An ambiguous and incomplete error message is produced by the
under the following conditions:
BPR

*FATAL*- I/O error

BPR

*FATAL*- Job was aborted via CLI

BPR

*DIAG*- I/O error

batch

The messages are cryptic because the batch job exits fatally when
find the original batch file.

processor

BPR

cannot

RESPONSE:
The batch processor is doing two processes wrong. First, internally, it is
not handling the error at the proper severity level. This is why the second
error message is produced. Secondly, it tries to close a batch file that was
never open; thus, the second I/O error. This happens because the internal
flags were not being used correctly for this condition.
These problems will be corrected in RSX-llM-PLUS Version 3.0 Update C.
error message which will be produced is:
BPR -- *FATAL*- I/O error -- file not found

(
129

The

....

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
BATCH/QUEUE MGR
LPP

Seq. No. 4.1.5.1 M
1 of 1

LPP LOOPS ON NEGATIVE RECORD LENGTH (SPR ll-P00210X RDH)
PROBLEM
STATEMENT:
LPP loops when printing a file containing a
length.

record

with

negative

record

RESPONSE:
PRT issues a GET$S directive to read each record from the file being
Two types of invalid record length may result from this operation:
1.

Actual record length exceeds limit established
specified in F.URBD.

for

the

printed.

device

and

In this case, File Control Services (FCS) transfers as many bytes as
will fit in the user buffer and returns the error code IE.RBG. FCS
updates F.RCNM to point at the next record.
2.

Actual record length is negative.
FCS returns the error code IE.RBG. No bytes are transferred to the
user buffer. Also, FCS does not update F.RCNM to the next record,
since it cannot determine its starting point because of the negative
record length.
On receiving the IE.RBG error code, PRT assumes that it resulted from
the former case and proceeds to print the truncated record. If the
error had resulted from the latter situation, PRT prints the contents
of the user buffer (the preceding line) and requests the next record,
thereby, looping until the entry is deleted from the queue.

RSX-llM-PLUS Version 3.0 Update C includes a correction for this problem.
Specifically, PRT will test for negative record length and abort with an error
message if one occurs.

(
131

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
MULTI-USER TASK
BRO

Seq. No. 4.2.2.1 N
1 of 1

BRO ON SYSTEMS WITHOUT ACCOUNTING: GARBAGE IN USER NAME (SPR 11-00175X JF)
PROBLEM
STATEMENT:
Broadcast on a system without resource accounting puts
name.

garbage

the

user

RESPONSE:
Broadcast relies on assembly-time conditionals to determine the presence of
resource accounting in the system. This is incorrect because broadcast is not
assembled during SYSGEN. It must be changed to check for the presence of
resource accounting at run time.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update B.

(
133

...

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
UTILITIES
PIP

Seq. No. 5.1.12.1 M
1 of 1

DELETING FILE, ;0 DOES NOT ALWAYS WORK PROPERLY (SPR ll-00195X JG)
PROBLEM
STATEMENT:
Deleting files and using wildcards for the member number in the UFD and a
zero for the version number, causes the latest version number of the file from
the first UFD to remain sticky for all files in all other UFDs.
RESPONSE:
This problem has been corrected so that the latest version of the file is
found in each UFD, and not just the first UFD. The correction for this
problem is in RSX-llM-PLUS Version 3.0 Update B.

(
135

•

(

RSX Software Dispatch, April 1986

(
Seq. No. 5.1.17.10 N

RSX-llM-PLUS V3.0
UTILITIES
BRU

l of 2

BRU--MISLEADING ERROR MESSAGE/ACTION FOR UNMOUNTED TAPES (SPR ll-00190X SIR)
PROBLEM
STATEMENT:

(

When attempting a BACKUP/RESTORE operation to/from a tape that has not been
mounted, BRU issues a warning message, physically dismounts the tape from the
drive, and requests another tape. Any attempts to remount the tape are futile
because BRU will persistently dismount it. The only solution is to abort BRU,
mount the tape foreign, and run BRU again.
There are two problems with this.
First, BRU can be aborted only by a
privileged terminal. Secondly, if the terminal from which BRU was initiated
is in a remote location, the user is forced to walk to the tape drive to
remount the tape on the drive.
RESPONSE:
The message BRU displays when the tape is not mounted depends upon the
operation being performed. Attempts to back up to an unmounted tape result in
the messages:
BRU
*WARNING* -- Tape label error
I/O error code -16
BRU -- Mount another tape
Attempts to restore from an unmounted tape result in the messages:
BRU -- *WARNING*
I/O error code -16

Tape label error

BRU -- *WARNING* -- Volume not a backup tape
BRU -- Mount another tape
We recognize these messages can be misleading, and the action taken by BRU
under these circumstances is inappropriate. The reason for this is that BRU
does not check the mount status of the devices involved in BACKUP or RESTORE
operations before it begins the operation. Some types of read errors and any
errors which occur while writing the tape are treated as recoverable.

(
137

RSX Software Dispatch, April 1986

Seq. No. 5.1.17.10 N

RSX-llM-PLUS V3.0
UTILITIES
BRU

2 of 2

Obviously, this behavior is not appropriate when the errors are caused by the
fact that the tape is not mounted.
The best solution we can offer at this time is to avoid this user error;
tapes involved in any BACKUP or RESTORE operation must always be mounted
foreign. After the error has been made, the only way to correct it is to
abort BRU, remount the tape, mount the tape foreign, and run BRU again.
Enhancements to BRU are being considered for a future release of RSX-llM-PLUS,
which would enable it to issue a more appropriate error message and take a
more reasonable action when a device is not mounted properly.

138

(

RSX Software Dispatch, April 1986

Seq. No. 5.3.0.l M

RSX-llM-PLUS V3.0
TASK BUILDER
TASK BUILDER

1 of 1

TKB SWITCH /CL DOES NOT WORK (SPR ll-P00112P DR)
PROBLEM
STATEMENT:
When a task built with the TKB switch /CL is installed, it does not end up
marked as such. The following command displays the task status where "xxxxxx"
is the name of a task. This task should have the CLI status displayed but
does not.
MCR TAL xxxxxx
RESPONSE:
When the TKB switch /CL was implemented, the original task flag word did
not have any bits available. A second task flag word was added to the task
label block. Although the task build command line is properly parsed and the
internal representations updated, the process of setting the new task flag
word contained an error.
The INS switch
status.

/CLI=YES

can

used

a workaround to force the desired

The task flag word is correctly set in RSX-llM-PLUS Version 3.0 Update B.

(
139

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
TASK BUILDER
TASK BUILDER

Seq. No. 5.3.0.2 M
1 of 1

MULTIPLE REFERENCES TO .PSECT IN SEGMENT CAUSE TKB TO ABORT
(SPR ll-P00202X DR)
PROBLEM
STATEMENT:
Multiple references in a single segment to a .PSECT specified in an ODL file
cause TKB to behave unpredictably, including aborting because of an odd
address trap.
A multiple reference may inadvertently be created when
tailoring an ODL file by combining segments. The following is an artificially
simple example:
.PSECT
.PSECT
.ROOT
.END

X
Y
X- X- Y- Y

RESPONSE:
TKB, upon detecting the multiple occurrence, improperly skips over inserting
the .PSECT into the segment's section list, resulting in an extra word being
popped off the stack.
Since specifying a .PSECT more than once serves no function, the
workaround is to remove all multiple references from the ODL files.
Multiple occurrences will be allowed by being
ignored) in RSX-llM-PLUS Version 3.0 Update B.

properly

handled

obvious

(that

is,

l
140

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
DEBUGGING AIDS
ODT

Seq. No. S.S.1.1 M
1 of 1

TASK WITH LARGE NUMBER OF LUNs HANGS IN ODT (SPR ll-P00201X LP)
PROBLEM
STATEMENT:
The user's I/D task works when built non-I/D, but crashes when built I/D. The
task, which uses a large number of LUNs (110), hangs immediately when built
with ODT.
RESPONSE:
When a task is built with ODT, two additional LUNs are included for ODT.
ODT
was incorrectly using the first of these LUNs as an event flag number to issue
QIOs to the terminal. This error caused the task to hang in ODT because the
ODT LUN number (111) was higher than the any of the legal event flag numbers
(0-96). This error will be corrected in RSX-llM-PLUS Version 3.0 Update B.
As a workaround, when using ODT, specify fewer LUNs with the TKB UNITS option.
Also, avoid using event flag numbers in the task, which coincide with the ODT
LUNs.

(
141

(

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
MISC SYS TASKS
HELP

Seq. No. 5.7.1.1 N
1 of 1

HELP /OUT:TTNN: (PARAMETER) DOES NOT WORK (SPR 11-P00174X JF)
PROBLEM
STATEMENT:
The command HELP/OUT:TTnn:
parameter is ignored.

(parameter)

does

not

work

expected.

The

(
143

(

RSX Software Dispatch, April 1986

Seq. No. 5.7.3.1 M

RSX-llM-PLUS V3.0
MISC SYS TASKS
PMD/SNAP

1 of 1

PMD SNAPSHOT FOR I/D SNAPSHOT DUMPS I-SPACE AND NOT D-SPACE (SPR ll-00203X NH)
PROBLEM
STATEMENT:
PMD snapshot for I/D stack dumps the I-space and not the D-space.
RESPONSE:
We have determined that there is a problem concerning PMD snapshot and the
space that it dumps.
The problem resides in PMD.MAC. It fails to check
IDFLAG for the proper area to dump before calling DUMP3, which dumps the
stack.
However, this is done before the module DUMP4 is called by PMD.
Therefore, the correct partition is identified.
This problem will be corrected in a future update or release.

(
145

RSX Software Dispatch, April 1986

Seq. No. 6.1.0.2 M

RSX-llM-PLUS V3.0
DCL
DCL

1 of 1

DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED (SPR ll-P00193X JJA)
PROBLEM
STATEMENT:
The DCL LINK/OPTION command does not work as documented. The RSX-llM-PLUS
V2.l Command Language Manual, page 6-74, specifies that there are three ways
of supplying options to the /OPTION qualifier:
1.

Supply a file specification of a file
options, i.e., LINK/OPTION:filespec.

Respond to the options prompt.
Example:

c
3.

which

contains

the

list

LINK/OPTION
Option? optl
Option? opt2
Option? opt3
Option? (CR/LF)

List the options on the
LINK/OPTION:optl,opt2,opt3.

command

line separated by commas, i.e.,

However, the third format, where the options are listed on
line, separated by commas, does not work.

the

same

command

RESPONSE:
This problem results from an error in the parsing code for the DCL LINK
command. It has been corrected. The correction will appear in RSX-llM-PLUS
Version 3.0 Update B.
For now, use one of the formats which
Manual, and invoke TKB directly.

work,

(
147

refer

the Task Builder

RSX Software Dispatch, April 1986

RSX-llM-PLUS V3.0
DCL
DCL

Seq. No. 6.1.0. 3 M
1 of 1

DCL "LIBRARY @FILESPEC" DOES NOT WORK (SPR ll-P00196X JJA)
PROBLEM
STATEMENT:
The DCL command "LIBRARY @filespec" does not work.
RESPONSE:
It is currently documented that a user may perform operations with the DCL
LIBRARY command in one of two ways. A user may specify the operation with
associated qualifiers directly on the command line or supply the LIBRARY
command with a file that contains the intended operations, i.e., DCL LIBRARY
@filespec. Currently, however, the latter format does not work.
This is corrected in RSX-llM-PLUS Version 3.0 Update B.
To circumvent the problem, the user may invoke the MCR LBR command.
then accept a file containing the intended operations, i.e.,
@filespec.

148

LBR will
MCR LBR

(

RSX Software Dispatch, April 1986

Seq. 17.1.1.l N

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM-PLUS V3.0

1 of 3
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER VERSION 2.0
PRODUCT DESCRIPTION
Introduction
The PDP-11 Symbolic Debugger Version 2.0 is designed to help users find logic
and programming errors in successfully compiled and linked programs that do
not run correctly. Version 2.0, an extension of PDP-11 FORTRAN-77 DEBUG
Version
1.0, includes support for FORTRAN-77, COBOL-81, and MACR0-11.
Capabilities have also been added to PDP-11 FORTRAN-77 DEBUG Version 1.0 to
make it more powerful. Support is provided for debugging tasks built with rand D-space, on systems where both the hardware and operating system support
this feature, for example, RSTS/E V9.0 or higher, RSX-llM-PLUS V2.l or higher,
Micro/RSTS v2.o, and Micro/RSX V3.0.
The debugger is designed as two tasks, a kernel and a background task.
The
kernel is linked in with user programs. The kernel is either overlaid to
occupy less than 4 kilobytes (KB) of user program space, or nonoverlaid to
occupy about 5 KB. The default is an overlaid debugger kernel which can be
used with all user programs (overlaid, cotrees, resident libraries, etc.),
except those user programs that do manual overlay loading. The kernel
communicates with the larger background task, which provides the debugger's
main functionality.
Operating Systems/Installation
The debugger runs on the following versions of DIGITAL's operating systems:

(

VAX-11 RSX Version 2.0 or higher

RSX-llM Version 4.1 or higher

RSX-llM-PLUS Version 2.1 or higher

Professional Host Tool Kit Version 2.0 or
Version 2.0 or higher

RSTS/E Version 9.2 or higher

149

higher

and

PRO/Tool

Kit

RSX Software Dispatch, April I986

Seq • I 7. I • I • I N

PDP-II SYMBOLIC DEBUGGER v2.o
for RSX-IIM-PLUS V3.0

2 of 3

Micro/RSX Version 3.0 or higher

Micro/RSTS Version 2.0 or higher

On each supported operating system, the debugger is installed using an
automatic installation procedure.
Installation will vary from system to
system. The PDP-II Symbolic Debugger Version 2.0 on VAX/VMS, Micro/RSX,
Professional
Host
Tool Kit/VMS, RSTS/E, and Micro/RSTS use operating
system-supplied installation procedures. The PDP-II Symbolic Debugger Version
2.0 on RSX-IIM/M-PLUS, P/OS, and Professional Host Tool Kit/RSX use an
installation procedure supplied with the kit.
Documentation
The debugger documentation set has been completely revised.
of the new manuals.

Below is

PDP-II Symbolic Debugger User's Guide

PDP-II Symbolic Debugger Installation Guide

PDP-II Symbolic Debugger Quick Reference

PDP-II Symbolic Debugger Information for FORTRAN-77 Users

PDP-II Symbolic Debugger Information for COBOL-8I Users

PDP-II Symbolic Debugger Information for MACRO-II Users

list

Availability
The PDP-II Symbolic Debugger Version 2.0 was expected to be available from the
Software Distribution Center (SDC) in March.
RELEASE NOTES
The Release Notes for the PDP-II Symbolic Debugger Version 2.0 are distributed
on line as part of the kit. These Release Notes describe known problems and
restrictions in the PDP-II Symbolic Debugger Version 2.0. Workarounds for the
problems have been provided, whenever possible, to lessen their impact.

150

RSX Software Dispatch, April 1986

PDP-11 SYMBOLIC DEBUGGER v2.o
for RSX-llM-PLUS V3.0

Seq. 17.1.1.1 N
3 of 3

In the Installation Guide, page 5-3, "Installation on the Professional,"
PIP and FLX commands given to copy the Release Notes are incorrect.
correct commands are:

the
The

FOR DISK USERS
) BRU/NOI/UFD/NEW/MOU indev:[l,5]DBGREL.DOC outdev:
FOR TAPE USERS
) BRU/BAC:DBGREL/REW/NOI/UFD/NEW indev:

outdev:

Replace indev with the device on which your distribution medium is allocated
and mounted, replace outdev with the destination device. The Release Notes
are copied to [1,5] and named DBGREL.DOC.

(
151

.
... .

(

RSX-11M-PLUS V3.0
CUMULATIVE INDEX
APRIL 1986

•

This is a complete listing of all articles for RSX-11M-PLUS V3.0 and layered products. Missing
sequence nu•bers may pertain to problems unique to other versions of the same product or other major
operating systems.
IMPORTANT I
Unassigned articles are indicated:

UNASSIGNED.

Flags are currently being installed for all articles.
M

The flags and definitions are as follows.

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

F = 0ptional Feature Patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the duration of the current
release and will be incorporated with any future release, unless otherwise stated.
R • Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as part
of the normal release cycle.
N = Note. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.

* = Articles appeared in the RSX-llM-PLUS V3.0 Software Dispatch Review, August 1985.

Component

Sequence

Mon/Yr

1.1.0 0 1 M

Apr 86

RSX-llM-PLUS V3 0 0
SYSGEN
SYSGEN
AUTOCONFIGURE DOES NOT PASS MULTIPLE T(MSCP) INFO TO SYSGEN
AUTOCONFIGURE
ACF MAY NOT CORRECTLY SET UP DV 0 NUC IN CONFIG 0 DAT FOR RS03/4s

(

DISTRIB KITS
DAPRES NOT PROPERLY INSTALLED

Apr 86

1.1.2 0 1 M

153

Feb 86

Component

Sequence

EXECUTIVE
EXECUTIVE
DISK CACHE FLUSH PARTIAL BLOCK WRITES TO SUPPORT RTEM-11
DIRECTIVES
FAST MAP FACILITY HAS ADDITIONAL RESTRICTION AND ERROR CODE
GSSW$ CRASHES SYSTEMS WITH NO SWITCH REGISTER

Mon/Yr

Mar 86

20 10 1 0 1 M
2 0 1.1.2 R

Mar 86
Apr 86

LOADR
DRIVER WITH A CLOCK BLOCK IN THE CTB CRASHES THE SYSTEM

Apr 86

MISC ROUTINES
CERTAIN CALLS TO $QRMVT SHOULD BE CHANGED TO $QRMVA

Jan 86

!!£!..
INTERNAL CMDS
CBD NEEDS TO KNOW ABOUT NEW REGION CHARACTERISTICS
ASN COMMANDS WITH NULL LOGICALS CAUSE SYSTEM CRASH

2.2.1.1 M
2.2.1.2 M

Jan 86
Apr 86

INS
NEW •TASK IMAGE I/O ERROR• MESSAGE FOR DEVICES

20 2 0 20 1 M

Apr 86

INDIRECT, ICO, ICM, ICP
INDIRECT EXITS WITHOUT WARNING ON I/O ERROR
LOGICAL NAME AND SUBSTITUTION ERRORS IN INDIRECT
INDIRECT PROBLEMS CORRECTED IN UPDATE B
SPECIAL SYMBOL <UIC> SOMETIMES ERRONEOUS IN NAMED MODE
24-HOUR MAXIMUM FOR .DELAY DIRECTIVE
INVALID CHARACTERS IN SUBSTITUTION SYMBOL NAMES
INDIRECT COMMAND .SETT <ERSEEN> LEAVES IT FALSE
0 EXIT DIRECTIVE WITHIN BEGIN-END BLOCK
ERROR IN EXECUTION OF @/LB:MODULE FROM DCL OR MCR
.ASK DOES NOT WORK AS DOCUMENTED WITH <ESC> RESPONSE
ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES
CORRUPTED BEGIN-END BLOCK POINTERS IN LOCAL SYMBOL TABLE

2.2.3.1 M
2.2.3.2 M
2.2.3.3 M
2.2.3.4 M
2.2.3.S M
2.2.3.6 M
2.2.3.7 M
2.2.3.8 M
2.2.3.9 M
2.2.3.10 M
2.2.3.11 M
2 0 2 0 3 0 12 M

Jan 86
Jan 86
Feb 86
Feb 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Apr 86
Apr 86
Apr 86

SAV/BOO
SAV DOES NOT SIZE MEMORY ABOVE 1920 kW ON 0-BUS SYSTEMS
SAV'd/BOOTED 11/70 SYSTEMS DO NOT CORRECTLY IDENTIFY RHlls
SAV DOES NOT SIZE MEMORY CORRECTLY ON UNIBUS SYSTEMS
SAV CRASHES WHEN SYSTEM DISK IS DUAL-ACCESS DEVICE

2.2.6.l M
2.2.6.2 M
20 2 0 6 0 3 M
2.2.6.4 M

Feb 86
Mar 86
Apr 86
Apr 86

DRIVERS
DYDRV
RX02 SUPPORT FOR 22-BIT 0-BUS SYSTEMS
DLDRV's ERROR RECOVERY SHOULD MAKE COMPLETE DRIVE-STATUS CHECK
DDDRV TIMES OUT WHILE COPYING LARGE FILES

3.1.1.1 M
3.1.1.2 M
3.1.1.3 M

Aug 85
Mar 86
Mar 86

MUDRV
MUDRV DOES NOT SUPPORT MULTIPLE-DENSITY TAPE DRIVES
SYSTEM CRASHES WITH MUDRV/PUCOM MAPPED

3.1.2.1 M
3.1.2.2 M

Mar 86
Mar 86

154

Component

Sequence

Mon/Yr

FDX-TTDRV
DRIVER DOUBLE FORK CAUSES SYSTEM CRASH ON 0-BUS SYSTEM
VARIOUS TTDRV PROBLEMS

3 0 10 3 0 1 N

30 10 3 0 2 M

Feb 86
Mar 86

3 0 10 5 0 1 M

Mar 86

30 30 50 1 M

XEDRV
VARIOUS XEDRV PROBLEMS

•

ERROR LOGGING
CONTROL FILES
UPDATE ERROR-CODE TABLE IN MSCP60 0 CNF
END MESSAGE PACKETS FOR MU ARE NOT ANALYZED PROPERLY
ERROR LOG MESSAGE PACKETS FOR TK50 ARE NOT ANALYZED PROPERLY

30 30 50 3 M

Mar 86
Mar 86
Mar 86

BATCH/QUEUE MGR
BPR
BPR GIVES CRYPTIC ERROR MESSAGE WHEN FILE IS DELETED

4 l l l M

Apr 86

40 1 0 3 0 1 M
4 0 1 0 3.2 M

Mar 86
Mar 86

40 10 5 0 1 M

Apr 86

BRO
BRO ON SYSTEMS WITHOUT ACCOUNTING: GARBAGE IN USER NAME

40 2 0 2 0 1 N

Apr 86

UTILITIES
MOU
MOUNT DOES NOT WAIT FOR RA80/81 TO SPIN DOWN!

5 0 1 0 10 0 1 M

Mar 86

PIP
DELETING FILE, 10 DOES NOT ALWAYS WORK PROPERLY

5.1.12 0 1 M

Apr 86

QMG
INCORRECT ERROR MESSAGE IF DEVICE IS INVALID
STICKINESS IS LOST IN FILE EXTENSION IF FILES DO NOT EXIST
LPP
LPP LOOPS ON NEGATIVE RECORD LENGTH

30 30 50 2 M

MULTI-USER TASK

BRU
BRU "NO FILES FOUND" PROBLEM CORRECTED

5.1.11.1 M
5.1.11.2 N
5.1.17.3 N
5.1.17.4 N
5.1.11.5 N
5.1.11.6 N
5.1.11.1 N

Dec 85

BRU ENDS WITH MEMORY PROTECTION VIOLATION DURING RESTORES
BRU INDICATES OUTPUT DISK IS TOO FRAGMENTED DURING VERIFY
BRU MAY FAIL ON THE VERIFY PASS OF A BACKUP OPERATION
BRU REPORTS ATTACH FAILED AS SECOND FATAL ERROR
BRU REPORTS I/O STATUS OF -255
BRU REPORTS ERRORS ABOUT FILES THAT DO NOT EXIST
BRU USES WRONG IMAGE FILE FOR RESTORE/COMPARE
BRU DOES NOT RECOVER PROPERLY FROM TAPE-LABEL ERRORS
BRU--MISLEADING ERROR MESSAGE/ACTION FOR UNMOUNTED TAPES

5.1.11.8 N
5.1.11.9 M
5 0 1 0 17.10 N

Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Apr 86

SYSTEM LIBRARIES
CSI
CSI$1 AND CSI$2 MEMORY PROTECT

50 20 60 1 M

Mar 86

(
155

CO•ponent

Sequence

Mon/Yr

TASK BUILDER
TASK BUILDER
TKB SWITCH /CL DOES NOT WORK
MULTIPLE REFERENCES TO 0 PSECT IN SEGMENT CAUSE TKB TO ABORT

5.3.0.1 M
5.3.0.2 M

Apr 86
Apr 86

TKB
NOTES REGARDING CLUSTER LIBRARY USE
TKB OPENED AND CLOSED THE COMMAND FILE FOR EACH OPTION
I/D TASK LINKED TO LIBRARY AND COMMON DOES NOT BUILD

5.3.1.1 M
5.3.1.2 N
5.3.1.3 M

Aug 85
Nov 85
Feb 86

..
~

DEBUGGING AIDS
ODT

TASK WITH LARGE NUMBER OF LUNs HANGS IN ODT

5.5.1.1 M

MISC SYS TASKS
HELP
HELP /OUT:TTNN: <PARAMETER> DOES NOT WORK

Apr 86

PMD/SNAP
PMD SNAPSHOT FOR I/D SNAPSHOT DUMPS I-SPACE AND NOT D-SPACE

5 0 70 3 0 1 M

Apr 86

RCT
RCT DOES NOT REPLACE ALL BAD BLOCKS

5.7.15.1 M

Feb 86

6.1.0.1 M
60 10 00 2 M
6 0 10 0 0 3 M

Mar 86
Apr 86
Apr 86

10 0 5 0 1 0 1 N

Aug 85

10 0 20.1.1 N

Dec 85

DCL
DCL

DCL LINK DOES NOT WORK CORRECTLY IN SET DEBUG/EXECUTE MODE
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @FILESPEC• DOES NOT WORK

RSX-11 2780/3780 PROTOCOL EMULATOR V4 0 l
CONDITIONS FOR AUTOMATIC SIGN ON

BASIC-PLUS-2 V2.3
PROBLEM WITH PRINT USING

FORTRAN IV/RSX V2 0 6
OTS
LIST-DIRECTED READ

Dec 85

PDP-11 SYMBOLIC DEBUGGER v2.o
ANNOUNCING THE PDP-11 SYMBOLIC DEBUGGER v2.o

Apr 86

156

Micro/RSX V1.0

157

.•

(
Micro/RSX v1.o
CUMULATIVE INDEX
APRIL 1986

This is a complete listing of all articles for Micro/RSX v1.o and layered products. Missing sequence
nuabers may pertain to problems unique to other versions of the same product or other major operating
systems.
IMPORTANT I
unassigned articles are indicated:

UNASSIGNED.

Flags are currently being installed for all articles.

The flags and definitions are as follows.

M = Mandatory patch. These patches correct errors in the software product. All users are required to
apply these patches to maintain consistent •user level" unless the accompanying article specifies
otherwise.
F = oPtional Feature patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the duration of the current
release and will be incorporated with any future release, unless otherwise stated.
R = Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as part
of the normal release cycle.
N = NOte. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.

Component

sequence

Mon/yr

15.1.1.1 M

Aug 84

17.lolol N

Sep 84

Micro/RSX DIBOL v1.o
DOCUMENTATION
CORRECTION NOTE TO DIBOL-83 LANGUAGE REFERENCE MANUAL

DEOaail-11 v2.o
GENERAL NOTES
ANNOUNCING DEOnail-11 v2.o FOR Micro/RSX

(
159

Micro/RSX V3.0

161

RSX Software Dispatch, April 1986

Seq. No. 2.2.1.1 M

Micro/RSX V3.0
MCR
INTERNAL CMDS

1 of 1

ASN COMMANDS WITH NULL LOGICALS CAUSE SYSTEM CRASH (SPR ll-X00217X JK)

PROBLEM
STATEMENT:
The MCR ASN command causes a system crash if the logical name
consists of a blank node name or blank device name.

being

assigned

RESPONSE:
Since the ASN command strips off one or two colons from a logical name before
an assignment, the following commands will result in a null logical name and
cause an odd address system crash within the third directive common:
ASN eqv=:
ASN eqv=::
This problem will be corrected in the next release of Micro/RSX.

(
163

(

RSX Software Dispatch, April 1986

Seq. No. 2.2.2.1 M

Micro/RSX V3.0
MCR
INS

1 of 1

NEW "TASK IMAGE I/ 0 ERROR" MESSAGE FOR DEVICES ( SPR 11-XOO 20 7X RC)
PROBLEM
STATEMENT:
INS aborts with the message "SYNTAX ERROR" for certain 1/0 errors returned
the driver.

c
RESPONSE:
For those 1/0 errors other than device off line, no pool, device not in
system, device not mounted, parse error, and file privilege violation, which
are currently reported explicitly, we have changed the message to read:
"Task image 1/0 error"
This problem Will be corrected in the next release of Micro/RSX.

(
165

RSX Software Dispatch, April 1986

(
Micro/RSX V3.0
MCR
INDIRECT

Seq. No. 2.2.3.8 M
1 of 2

ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES (SPR ll-X.00213X RDH)

PROBLEM
STATEMENT:
The Indirect Command Processor allows definitions of global and local symbols
with the same name to exist on the same level. Also, it allows the individual
deletion of local symbols when they assume the global naming convention. This
is contradictory to the documentation.
The following command files demonstrate the problem:
A.CMD
.SETS $A "Howdie"
.SETS $B "Doodie"
@A2
.IFNDF $A .STOP
.IF $B NE 2 .STOP
.ERASE SYMBOL $B
.IF $B NE "Doodle" .STOP
.ERASE SYMBOL $B
.EXIT

local symbol $A
local symbol $B
ensure we are back on the correct level
this $B is global from A2.CMD
erases $B from global table
this $B is local from A.CMD
erases $B from local table

A2.CMD
.ENABLE GLOBAL
.SETN $B 2
.EXIT

enable global symbol processing
global symbol $B

(
167

RSX Software Dispatch, April 1986

Micro/RSX V3.0
MCR
INDIRECT

Seq. No. 2.2.3.8 M
2 of 2

The implementation of Indirect does allow the .ERASE SYMBOL to affect local
symbols if their name begins with the dollar sign, contrary to the documented
restriction that only
global
symbols
may
be
individually
erased.
Investigation of this problem shows that the restriction can be removed
without adverse impact.
Its removal would also eliminate the apparent
advantages of naming local symbols with dollar signs.
The next release
of
Micro/RSX includes a change which removes this
restriction. Specifically, the .ERASE SYMBOL directive will be able to erase
individual global or local symbols. If two symbols with the same name, one
global and one local, exist for the level on which the .ERASE SYMBOL is being
executed, the global symbol will take precedence and be erased.

168

RSX Software Dispatch, April 1986

Seq. No. 2.2.3.9 M

Micro/RSX V3.0
MCR
INDIRECT

1 of 1

CORRUPTED BEGIN-END BLOCK POINTERS IN LOCAL SYMBOL TABLE (SPR ll-X00214X RDH)
PROBLEM
STATEMENT:
Both .SETS assignments to local string symbols and .ERASE LOCAL directives can
cause memory protect violations or Illegal Nesting errors when executed from
within Begin-End blocks or from files invoked with the /LO switch.
RESPONSE:
Begin-End blocking context, which is stored in the Local Symbol Table as
special frames, includes pointers to the start of the next-higher symbol
block. The pointers are not correctly maintained when a .SETS is executed on
a string symbol that is outside the current Begin-End block but still within
the current Local Symbol Table range, for example, a local symbol defined at a
higher level of Begin-End block.
If the .SETS changes the length of the
string, a Memory Protect violation may occur when the task exits.
In a similar manner, execution of the .ERASE LOCAL directive from the
beginning block level of a file which was invoked with the /LO switch will
corrupt the Begin-End block pointers, resulting in an Illegal Nesting error.
These failures can be avoided by:

Do not modify higher-level local string symbols from within Begin-End
blocks.
If you need to implement this functionality, define the
string symbol as global.

Do not execute the .ERASE LOCAL

directive from the highest block
level of a file which has been invoked with a /LO switch. Defining
the symbols as global and erasing them with the .ERASE SYMBOL xxxx
directive provides an alternative implementation.

The next release of Micro/RSX will include corrections for these problems.

(
169

•

{

RSX Software Dispatch, April 1986

Micro/RSX V3.0
BATCH/QUEUE MGR
BPR

Seq. No. 4.1.1.1 M
1 of 1

BPR GIVES CRYPTIC ERROR MESSAGE WHEN FILE IS DELETED (SPR ll-X00198X DR)
PROBLEM
STATEMENT:
An ambiguous and incomplete error message is produced by the
under the following conditions:
BPR

*FATAL*- I/O error

BPR

*FATAL*- Job was aborted via CLI

BPR

*DIAG*- I/O error

batch

The messages are cryptic because the batch job exits fatally when
find the original batch file.

processor

BPR

cannot

RESPONSE:
The batch processor is doing two processes wrong. First, internally, it is
not handling the error at the proper severity level. This is why the second
error message is produced. Secondly, it tries to close a batch file that was
never open; thus, the second I/O error. This happens because the internal
flags were not being used correctly for this condition.
These problems will be corrected in the next release of Micro/RSX.
message which will be produced is:
BPR -- *FATAL*- I/O error -- file not found

•

(
171

The error

(

RSX Software Dispatch, April 1986

Seq. No. 4.1.s.1 M

Micro/RSX V3.0
BATCH/QUEUE MGR

1 of 1

LPP

LPP LOOPS ON NEGATIVE RECORD LENGTH (SPR 11-X00210X RDH)
PROBLEM
STATEMENT:
LPP loops when printing a file containing a
length.

record

with

negative

record

RESPONSE:
PRT issues a GET$S directive to read each record from the file being
Two types of invalid record length may result from this operation:
1.

Actual record length exceeds limit established
specified in F.URBD

for

the

printed.

device

and

In this case, File Control Services (FCS) transfers as many bytes as
will fit in the user buffer and returns the error code IE.RBG. FCS
updates F.RCNM to point at the next record.
2.

Actual record length is negative.
FCS returns the error code IE.RBG. No bytes are transferred to the
user buffer. Also, FCS does not update F.RCNM to the next record,
since it cannot determine its starting point due to the negative
record length.
On receiving the IE.RBG error code, PRT assumes that it resulted from
the former case and proceeds to print the truncated record. If the
error had resulted from the latter situation, PRT prints the contents
of the user buffer (the preceding line) and requests the next record,
thereby, looping until the entry is deleted from the queue •

•

The next release of Micro/RSX will include a correction for this problem.
Specifically, PRT will test for negative record length and abort with an error
message if one occurs.

(
173

•

(

RSX Software Dispatch, April 1986

Micro/RSX V3.0
TASK BUILDER
TASK BUILDER

Seq. No. 5.3.0.1 M
1 of 1

MULTIPLE REFERENCES TO .PSECT IN SEGMENT CAUSE TKB TO ABORT
(SPR 11-X.00202X DR)
PROBLEM
STATEMENT:
Multiple references in a single segment to a .PSECT specified in an ODL file
cause TKB to behave unpredictably, including aborting because of an odd
address trap.
A multiple reference may inadvertently be created when
tailoring an ODL file by combining segments. The following is an artificially
simple example:
.PSECT
.PSECT
.ROOT
.END

x
y

X- X- Y- Y

•

(
175

properly

handled

obvious

(that

is,

RSX Software Dispatch, April 1986

Micro/RSX V3.0
TASK BUILDER
TASK BUILDER

Seq. No. 5.3.0.2 M
1 of 1

TKB SWITCH /CL DOES NOT WORK (SPR 11-X00112P DR)
PROBLEM
STATEMENT:
When a task built with the TKB switch /CL is installed, it does not end up
marked as such. The following command displays the task status where "xxxxxx"
is the name of a task. This task should have the CLI status displayed but
does not.
MCR TAL xxxxxx
RESPONSE:
When the TKB switch /CL was implemented, the original task flag word did
not have any bits available. A second task flag word was added to the task
label block. Although the task build command line is properly parsed and the
internal representations updated, the process of setting the new task flag
word contained an error.
The INS switch /CLI=YES can be used as
status.

workaround

force

the

desired

The task flag word will be correctly set in the next release of Micro/RSX.

176

(

RSX Software Dispatch, April 1986

Seq. No. 6.1.0.2 M

Micro/RSX V3.0
DCL
DCL

1 of 1

DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED (SPR 11-X00193X JJA)
PROBLEM
STATEMENT:
The DCL LINK/OPTION command does not work as documented. For Micro/RSX, it is
specified that there are three ways of supplying options to the /OPTION
qualifier:
1.

Supply a file specification of a file
options, i.e., LINK/OPTION:filespec.

Respond to the options prompt.
Example:

which

contains

the

list

LINK/ OPTION
Opt ion? opt 1
Option? opt2
Option? opt3
Option? (CR/LF)

List the options on the
LINK/OPTION:optl,opt2,opt3.

command

line separated by commas, i.e.,

However, the third format, where the options are listed on
line, separated by commas, does not work.

the

same

command

RESPONSE:
This problem results from an error in the parsing code for the DCL LINK
command.
It has been corrected. The correction will appear in the next
release of Micro/RSX •

•
For now, use one of the formats which
Manual, and invoke TKB directly.

work,

(
177

refer

the Task Builder

RSX Software Dispatch, April 1986

Seq. No. 6.1.0.3 M

Micro/RSX V3.0
DCL
DCL

1 of 1

DCL "LIBRARY @FILESPEC" DOES NOT WORK (SPR 11-X00196X JJA)
PROBLEM
STATEMENT:
The DCL command "LIBRARY @filespec" does not work.
RESPONSE:
It is currently documented that a user may perform oper~tions with the DCL
LIBRARY command in one of two ways. A user may either specify the operation
with associated qualifiers directly on the command line or supply the LIBRARY
command with a file that contains the intended operations, i.e., DCL LIBRARY
@filespec. Currently, however, the latter format does not work.
The problem will remain a
next release.

restriction of Micro/RSX until it is fixed in our

•

178

(

Micro/RSX V3.0
CUMULATIVE INDEX
APRIL 1986

This is a complete listing of all articles for Micro/RSX V3.0 and layered products. Missing sequence
nuabers may pertain to problems unique to other versions of the same product or other aajor operating
sys teas.
IMPORTANT I
Unassigned articles are indicated:

UNASSIGNED.

Flags are currently being installed for all articles.

The flags and definitions are as follows.

0ptional Feature Patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the duration of the current
release and will be incorporated with any future release, unless otherwise stated.

R = Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as par
of the normal release cycle.
N = Note. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.

Sequence

Component

Mon/Yr

Micro/RSX V3.0
SYSGEN
DISTRIB KITS
DAPRES NOT PROPERLY INSTALLED

•

(

Feb 86

EXECUTIVE
EXECUTIVE
DISK CACHE FLUSH PARTIAL BLOCK WRITES TO SUPPORT RTEM-11

2.1.0.1 M

Mar 86

DIRECTIVES
FAST MAP FACILITY HAS ADDITIONAL RESTRICTION AND ERROR CODE
ERROR IN EXECUTION OF @/LB:MODULE FROM DCL

2.1.1.1 M
2.1.1.2 M

Mar 86
Mar 86

MCR
INTERNAL CMDS
ASN COMMANDS WITH NULL LOGICALS CAUSE SYSTEM CRASH

179

Apr 86

Component

Sequence

Mon/Yr

YINS
NEW "TASK IMAGE I/O ERROR" MESSAGE FOR DEVICES

20 2 0 2 0 1 M

Apr 86

INDIRECT, ICQ, ICM, ICP
LOGICAL NAME AND SUBSTITUTION ERRORS IN INDIRECT
INDIRECT PROBLEMS IDENTIFIED ON Micro/RSX V3.0
SPECIAL SYMBOL <UIC> SOMETIMES ERRONEOUS IN NAMED MODE
INVALID CHARACTERS IN SUBSTITUTION SYMBOL NAMES
24-HOUR MAXIMUM FOR 0 DELAY DIRECTIVE
INDIRECT COMMAND .SETT <ERSEEN> LEAVES IT FALSE
.EXIT DIRECTIVE WITHIN BEGIN-END BLOCK
ERASING LOCAL SYMBOLS WITH DOLLAR-SIGN NAMES
CORRUPTED BEGIN-END BLOCK POINTERS IN LOCAL SYMBOL TABLE

2.2.3.1 M
2.2.3.2 M
2.2.3.3 M
2.2.3.4 M
2.2.3.5 M
2.2.3.6 M
2.2.3. 7 M
2.2.3.8 M
2.2.3.9 M

Jan 86
Feb 86
Feb 86
Mar 86
Mar 86
Mar 86
Mar 86
Apr 86
Apr 86

DRIVERS
DDDRV
DDDRV TIMES OUT WHILE COPYING LARGE FILES

Mar 86

DLDRV
DLDRV's ERROR RECOVERY SHOULD MAKE COMPLETE DRIVE-STATUS CHECK

Mar 86

MUDRV
MUDRV DOES NOT SUPPORT MULTIPLE-DENSITY TAPE DRIVES
SYSTEM CRASHES WITH MUDRV/PUCOM MAPPED

3 0 1 0 20 1 M
3 0 1 0 2.2 M

Mar 86
Mar 86

ERROR LOGGING
CONTROL FILES
END MESSAGE PACKETS FOR MU ARE NOT ANALYZED PROPERLY
ERROR LOG MESSAGE PACKETS FOR TK50 ARE NOT ANALYZED PROPERLY

30 30 50 1 M
3 0 3 0 5.2 M

Mar 86
Mar 86

BATCH/QUEUE MGR
BPR
BPR GIVES CRYPTIC ERROR MESSAGE WHEN FILE IS DELETED

Apr 86

LPP
LPP LOOPS ON NEGATIVE RECORD LENGTH

4 0 1 0 5.1 M

Apr 86

UTILITIES
BRU
BRU--MISLEADING ERROR MESSAGE/ACTION FOR UNMOUNTED TAPES
BRU ENDS WITH MEMORY PROTECTION VIOLATION DURING RESTORES
BRU INDICATES OUTPUT DISK IS TOO FRAGMENTED DURING VERIFY
BRU MAY FAIL ON THE VERIFY PASS OF A BACKUP OPERATION
BRU REPORTS ATTACH FAILED AS SECOND FATAL ERROR
BRU REPORTS I/O STATUS OF -255
BRU REPORTS ERRORS ABOUT FILES THAT DO NOT EXIST
BRU USES WRONG IMAGE FILE FOR RESTORE/COMPARE
BRU DOES NOT RECOVER PROPERLY FROM TAPE-LABEL ERRORS

5.1.11.1 N
5.1.11.2 N
5.1.11.3 N
5.1.17.4 N
5.1.11.5 N
5.1.17.6 N
5.1.11.1 N
5.1.11.0 N
5.1.17.9 M

Feb 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86

SYSTEM LIBRARIES
CSI
CSI$1 AND CSI$2 MEMORY PROTECT

1l,
5 0 20 6 0 1 M

180

Mar 86

(

Coaponent

Sequence

Mon/Yr

TASK BUILDER
TASK BUILDER
MULTIPLE REFERENCES TO .PSECT IN SEGMENT CAUSE TKB TO ABORT
TKB SWITCH /CL DOES NOT WORK

50 30 00 1 M
5 0 3 0 00 2 M

Apr 86

MISC SYS TASKS
RCT
RCT DOES NOT REPLACE ALL BAD BLOCKS

s.1.1s.1 M

Feb 86

6 0 10 0 0 1 M

Mar 86

Apr 86

DCL
DCL LINK DOES NOT WORK CORRECTLY IN SET DEBUG/EXECUTE MODE
DCL LINK/OPTION DOES NOT FUNCTION AS DOCUMENTED
DCL •LIBRARY @FILESPEC• DOES NOT WORK
DOCUMENTATION
DOCUMENTATION
DOC.ERROR IN CREATING AN OPTIONAL SOFTWARE TAPE KIT

c
•

(
181

6 0 10 0 0 2 M

Apr 86

60 10 00 3 M

Apr 86

Jan 86

Software Product Descriptions (SPDs)

(

Below is a list of the revised SPDs which appear on the following
pages:

•

10 .42.03
10 .43.03
14.18.06
18.04.01
18.07.02
30 .43.02

RSX-11 PSI/M, Version 2.1
RSX-11 PSI/M-PLUS, Version 2.1
PDP-11 PASCAL/RSX, Version 1.2
Micro/RSX FORTRAN-77, Version 5.0
Micro/RSX PDP-11 PASCAL, Version 1.2
DECserver 100 Terminal Server, Version 1.1

(

•

(
183

...

(

Software
Product
Description
PRODUCT NAME:

RSX-11 PSl/M, Version 2.1

SPO 10.42.03

Packetnet Syatem lnt9tf8ce
by the network; no facility is offered in the software product
whereby a terminal locally connected to an RSX-11 M system can act as a network terminal to other systems connected to the network.

DESCRIPTION

RSX-11 PSl/M allows a suitably configured RSX-11 M system to connect to Packet Switching Data Networks
(PSDNs) conforming to the CCITT recommendation X.25
(June 1980). Using RSX-11 PSl/M, the system may function as packet-mode Data Terminal Equipment (DTE) on
the PSDN. The software product supports access to the
facilities offered by X.25 communication for RSX-11 M user
programs written in MACR0-11, FORTRAN IV, and FORTRAN IV-PLUS. RSX-11 PSl/M supports task-to-task and
remote terminal communications via the X.25 network.

Operation of remote X.29 terminals appears similar to that
of terminals locally connected to the RSX-11 M system;
application programs need not be aware that access to the
terminal is via the RSX-11 PSl/M software. However, applications that bypass operating system control mechanisms
such as LOGON/LOGOFF may not function as expected.
There may also be restrictions imposed by the network

itself.

RSX-11 PSl/M can coexist with, or operate as a layered
product under DECnet-11 M to allow use of DECnet facilities over X.25 PSDNs, as well as point-to-point connections such as private leased lines or switched telephone
networks. For details please refer to the DECnet-11 M SPD
(SPD 10.66.xx).

The interface presented to an application program using a
remote X.29 terminal is compatible with that to a local terminal, except for those facilities where adequate support is
not provided by the network; for example. the support provided by the PAD for data forwarding upon input of an
escape sequence is not compatible with that required by
DIGITAL standard software. This means that FMS and
some of the screen editors may not function as expected
unless the PAD is set up in a cost-ineffective way. Additional facilities are provided which allow a program to manipulate the terminal parameters maintained by the PAD.

THlr·to-r..1r Communlc•tlon
For intertask communication, application programs use
RSX-11 M executive calls to use the X.25 functions, including setting up and breaking connections, transmitting and
receiving data. sending and receiving interrupt messages
and resetting virtual circuits. This interface. in addition to
CCITT X.25 level 3 functions, provides translation of symbolic DTE addresses. transfer of calls between tasks, and
splitting and recombination of messages which are longer
than the packet size selected for the circuit. National extensions not part of the international recommendations are not
provided. RSX-11 PSl/M does not include, for example, file
transfer, file access, or task addressing.

Vlrtu•I Circuits
RSX-11 PSl/M offers communications over both Permanent and Switched Virtual Circuits (PVCs and SVCs), the
maximum total number of virtual circuits supported being
255, subject to memory availability. The maximum number
of remote terminals supported is 140. Note, however. that
each remote terminal uses a virtual circuit. Up to two physical connections can be made to the PSDN.

Une Discipline
The communications discipline used is the CCITT recommendation X.25. Specifically, the product supports V.24
(EIA • RS232) and CCITT V.35 at the hardware level, the
symmetric LAPB variant of the X.25 frame level protocol,
and the X.25 packet level protocol over point-to-point, 4wire, synchronous, full-<:luplex lines. An RSX-11 M system
configured with PSI appears as a packet-mode DTE. Operation as Data Circuit Terminating Equipment (DCE) is not
supported.

access.
Remote Tennln•I Communlc•tlon•

RSX· 11 PSl/M supports access by remote terminals (character-mode DTEs) according to CCITT recommendations
X.3, X.28 and X.29. Terminals are supported in 'Remote
X.29 Terminal' mode in which code conversions between
ASCII and the actual code used by the terminal are performed by the network. Note that terminals are connected
via a Packet Assembly Disassembly (PAD) facility provided

Networlc M•n•gemenf

A Network Control Program and Configuration File Editor
are provided for the control of the operation of the X.25 soft-

October 1985

softWare
(
185

AE-N141D-TC

RllM 1 PSl/M, Venlon 2.1

SPD 10.42.03

ware. This Includes lollClng and unloaclng the software,
defining the lines, specification of addressing information
for Incoming calls and access to error counters and other
maintenln08 functions. This Interface provides a subset of
the DIGITAL Networl< Archlteeture specification for Net-

work Management.

SVCs and other network facilltles and their support must
be prepared jointly by the customer and DIGITAL.
MINIMUM HARDWARE REQUIRED
Any valid RSX-11 M system configuration with:
Memory Requirements

Conrmunlcdona
RSX-11 PSl/M suppons two types of communications interface as presented In the table below. They differ in many
respects, particularty in their effect on CPU utlHzation. The
table shows rated bandwidth for each device type used at
maximum configuration for that device. Bandwidth is
defined as the total number of bits per second full duplex
(Input and output), including protOCOI overtlead, being handled by the RSX-11 PSl/M software. Maximum Line Speed
Is defined as the maximum number of bits per second per
hardware device that Is supported by the software. Therefore, the following algorithm may be used in determining
valid configurations:

• A minimum of 20K words additional memory for resident
RSX-11 PSl/M software and data storage. This includes
sufficient memory for basic X.25 operation for 8 virtual
circuits. Additional memory· is required for optional features and additional circuits; for example, each additional virtual circuit will require approximately 250
words.
• A minimum of 9K words additional memory for the RSX11 PSl/M X.29 software if Remote Terminals are supported

• A minimum of 26K words of additional memory to
dynamically load the RSX-11 PSl/M software

RSX Pool Requirements

• Character Interrupt Devices - With the DUP11, CPU
cycles are required for X.25 packet and frame level protocol processing, and also for each character sent and
received

• A minimum of 60 words plus 1Owords for each network
task - for basic X.25 operation

• The KMS11-8 and KMS11-P are medium-speed Direct
Memory Access (OMA) communications controllers.
The KMS11-80/E is an 8-llne multiplexer of which 2
lines are supported. The KMS11-PX/Y is a single-line
device. Character transmission and reception and the
X.25 frame level protocol (LAPB) processing is executed in microcode by the KMS11 communications controller. The PDP-11 CPU processes only the X.25
packet level protocol.

Table 1
Dntce

Type

BD/E

llulmum Mulmum
LIM lpHd Number ot Bllndwldlll
Supporl9d Supporl9d Supporl9d
(Kblta/-)
Linn
(Kblta/-)

4.8

2
2

19.2

38.4
19.2
78.8

OMA

19.2

78.8

OMA

84.0

128.0

OUP11
Character
OPV11
Character
KMS11OMA
KMS11-

Mulmum

9.8

• An additional 22 words for each Remote Terminal
Operation with DECnet-11 M

• Operation of X.25 virtual circuits under DECnet-11M
incurs extra memory requirements. (Please consult the
DECnet-11 M SPD (SPO 10.66.xx) for further details.)
Disk Space

• A maximum of 25,000 blocks of disk space is required
for Network Generation, of which approximately 5000
blocks must be on a disk that Is available throughout the
generation process and wm subSequently be used for
RSX-11 PSl/M operation.

Processors
• POP-11 /23-PLUS, POP-11 /24, POP-11 /44, or POP-11 /
70 central processors with one of the following communications devices supporting one (1) line:
•
•
•
•

PX
KMS11-

DUP11-DA low-speed synchronous interface
DPV11-DA low-speed sychronous Interface
KMS11-BD/E medium-speed synchronous interface
KMS11-PX{Y medium-speed synchronous interface

Note:

Note: This table describes the physical hardware configurations supported by RSX-11 PSl/M. It should be
noted that the attachment of such devices as A/0
converters and timesharing terminals can reduce
the maximum number of lines or bandwidth that
can be supported.

For PTT certification purposes, the combination of
any KMS11-B controller hardware and X.25 level 2
microcode (which is supplied as part of RSX-11
PSl/M product) is known as the KMX11.

GROWTH CONSIDERATIONS
The minimum hardware requirements for any future version
of this product may be different from the minimum hardware requirements for the current version.
OPTIONAL HARDWARE

PREREQUISITE SUPPORT PLAN
A Network Profile and Customer Support Plan covering all
the intended network nodes, their usage of PVCs and

A communications interface and/or additional line. The
product supports up to two (2) DUP11 s or one (1) KMS 11
line together with one (1) OUP11.

(
186

(

SPD 10.42.03

RSX·11 PSl/M, Venlon 2.1

For networlc• and eountry c:ombllNlllon• other lhan
thou lleted In Table 2 under WARRANTY LIMITATIONS

PREREQUISITE SOFTWARE
RSX·11 M Operating System
Refer to the RSX-11 M Optional Software Cross Reference
Table (SPO 20.99.xx) for the required vsslorl.

OPTIONAL SOFTWARE

THIS PRODUCT IS PROVIDED "AS IS" WITHOUT ANY
WARRANTY OF ANY KIND EITHER EXPRESS OR
IMPLIED.
WARRANTY LIMITATIONS

DECnet-11M

DIGITAL has designed or adapted this software product to
operate on the networks in the associated countries listed
in Table 2.

FORTRAN IV/RSX
FORTRAN-n/RSX

While this software may function correctly with other

SOFTWARE WARRANTY
For networtce llet9d In Table 2 under WARRANTY UMI·
TATIONS when operated In tM aaaoclated country ae

packet-switching networks, DIGITAL cannot offer its standard warranty for this software unless it has been tested
with such networks and found acceptable to DIGITAL.

ehown

Table 2

Warranty for this software product is provided by DIGITAL
with the purchase of a license for the product. There is no
addittOnal charge. This software product is warranted to
conform to the Software Product Description (SPO). This
means that DIGITAL wiR remedy any nonconformance
when it Is reported to DIGITAL by the customer during the
warranty period.
The warranty period Is ninety (90) days. It begins when the
software is installed or thirty (30) days after delivery to the
end user, whichever occurs first and expires ninety (90)
days later. All warranty related support for this software wiH
end 180 days after release of the subsequent vsslorl.

Warranty is provided in the country of purchase. DIGITAL
will provide a service location which will accept reporting (In
a format prescribed by DIGITAL) of a nonconformance
problem caused when using the licensed software under
normal conditions as defined by the SPD. DIGITAL wiU remedy a nonconformance problem in the current unaltered
release of the licensed software by issuing correc:tion information such as: correc:tion documentation, corrected code,
or notice of availability of corrected code; or a restriction or
a bypass. The customer will be responsible for the
preparation and submission of the problem report to the service location.
Warranty Excluelon

DIGITAL DOES NOT WARRANT THAT THE SOFTWARE
LICENSED TO CUSTOMER SHALL BE ERROR FREE,
THAT THE SOFTWARE SHALL OPERATE WITH ANY
HARDWARE AND SOFTWARE OTHER THAN AS SPECIFIED IN THIS SPD, THAT THE SOFTWARE SHALL SATISFY CUSTOMER'S OWN SPECIFIC REQUIREMENTS,
OR THAT COPIES OF THE SOFTWARE OTHER THAN
THOSE PROVIDED OR AUTHORIZED BY DIGITAL
SHALL CONFORM TO THE SPD.
DIGITAL MAKES NO WARRANTIES WITH RESPECT TO
THE FITNESS AND OPERABILITY OF MODIFICATIONS
NOT MADE BY DIGITAL.
IF THE SOFTWARE FAILS TO FUNCTION FOR REASONS STATED ABOVE, THE CUSTOMER'S WARRANTY
WILL BE INVALIDATED AND ALL SERVICE CALLS WILL
BE BILLABLE AT THE PREVAILING PER CALL RATES.

(
187

Hetwmc·epeclflc DIGITAL lnmlled
documentation
Included

and Supportad

yea
yea

yes
yes

yea
yes
yea
yes
yea
yea

yes
yes
yea
yea
yes
yea

Oatapac (Cenada)
Oatex-P (West Germany)
PSS (United ~)
Telllnet (Unitad States)
Telepec (Switzertand)
Transpac (France)
Tymnet (Unitad States)
Pacnet (Taiwan)

Since the introduction of this software, other conflg1.ntions
may have been tested. Please contact your local DIGITAL
office for up-to-date information regarding listed configurations.
INSTALLATION

Cuetomer Responlllbllltl. .

Before installation of the software, the customer must:
•

Previously have installed all requisite software and hardware including terminals.

•

Obtain, install and demonstrate as operational any
modems and other equipment and facilities necessary
to interface to DIGITAL's communication equipment.

•

Demonstrate equivalency of operation for modems
other than Bell 208A, 208B, 209, 212A synchronous
moderns or in Europe, PTT approved modems.

•

Make available for a reasonable period of time, as mutually agreed by DIGITAL and the customer, all hardware,
communication facilities and terminals that are to be
used during installation.

•

For multi-node networks, designate one adjacent node
to verify installation/connectivity.

•

The X.25 network verification portion of this product's
installation requires that the customer subscribe to the
Open User Group and to at least one Switched Virtual

SPD 10.42.03

ASX·11 PSl/M, Yenlon2.1

Circuit. Systems with exclusively Permanent Virtual Circuits or Closed User Group membership require specially negotiated arrangements for DIGITAL instalation
of this product.
Delays caused by any failure to meet the responsibilities
will be charged at the then prevailing rate for time and materials.
For thoH networka Hated In Table 2 under WARRANTY
LIMITATIONS
DIGITAL requires that a customer's first purchase of this
software product include DIGITAL Installation Services.
These services provide for installation of the software product by an experienced DIGITAL Software Specialist.
For subsequent purchases of this product only experienced customers should attempt installation. DIGITAL recommends that all other customers purchase DIGITAL's
Installation Services.
DIGITAL's Installation Services can be purchased as a sep.
arate service.
Courteay lnatallatlon Service
This software product will be installed by DIGITAL at no
additional charge if you purchase it concurrent with a
Startup Service Package that includes installation service.
Both the operating system and this product must be
installed concurrently.
For network• other than those Hated in Table 2 under
WARRANTY LIMITATIONS
This software product can be installed by the customer
using the step-by-step documentation available for this
product.
ORDERING INFORMATION
Single-Use licensed software is furnished under the licensing provisions of DIGITAL's Standard Terms and Conditions of Sale, which provide in part that the software and
any part thereof may be used on only the single CPU on
which the software is first installed, and may be copied, in
whole or in part (with the proper inclusion of DIGITAL's
copyright notice and any proprietary notices on the software) for use on such CPU.
You will need a separate license for each CPU on which
you will be using the software product (except as otherwise
specified by DIGITAL). Then you will select the Materials
and Service Options you need to utilize the product effectively. IF YOU ARE ALREADY FAMILIAR WITH THESE
OPTIONS, YOU MAY OBTAIN THE ORDERING INFORMATION DIRECTLY FROM THE SOFTWARE OPTIONS
CHART. In most cases, you will want to review the following descriptions to determine what options you require.
LICENSE OPTIONS
Single-Use License Option

The Single-Use License is your right to use the software
product on a single CPU and it includes your 90 day warranty.

•

Single-Use License Option, and

• Distribution and Documentation Option

The license gives you the right to use the software on a
single CPU and the Distribution and Documentation Option
provides the machine-readable software and related documentation.
To use this software product on additional CPUs, you must
purchase for each CPU as a minimum:
• Single-Use License Option
In addition to the right to use, the license gives you the onetime right to copy the software from your original CPU
installation to the additional CPU. Therefore, the Distribution and Documentation Option is not required, but
optional.
MATERIALS AND SERVICE OPTIONS
Distribution and Documentation Option

The Distribution and Documentation option provides the
machine-readable software in binary form and the basic
documentation. You must have, or order, a Single-Use
License to obtain this option. You will need this option to
install the software for the first time. When revised versions
of this software product become available, they may also
be obtained by purchasing this option again.
If you prefer to receive automatic distribution of revised versions for this product, you must purchase a Software Product Service Agreement.
Software Revialon Right-To.Copy Option
The Right-To.copy Option allows a customer with multiple
CPUs to copy a revised version of a software product from
one CPU to another. Each CPU must be licensed for that
product. You first install the revised software on one CPU;
then you can make copies for additional CPUs by purchasing the Right-To-Copy Option for each additional CPU.
If you prefer to automatically obtain the right-to-copy, you
must purchase a Service Right-tO..COpy for each additional
CPU; this is a service added to a Software Product Service
Agreement.
Documentation-Only Option
You can obtain one copy of the basic documentation by
purchasing the Documentation-Only Option.
Installation Service Option
DIGITAL's Installation Service is provided by a DIGITAL
Software Specialist and accelerates your productive use of
this product. For more information on what is included in
this service, please obtain the appropriate Service Description from your local DIGITAL office.
Installation Service will be provided at no additional charge
(Courtesy Installation) under the conditions described in the
Installation section above.
Consult Table 2 under WARRANTY LIMITATIONS for a list
of networks and countries where this service is available.

For your first installation of this software product you must
purchase as a minimum:

188

(

RSX-11 PSl/M, Venlon2.1

SPD 10.42.03

Softw•re Product Service Agreemenla

DIGITAL offers licensed customers annual Software Product Service Agreements to maintain their software:
DECsupport s.rvtc:e is the most comprehensive level of
service offering critical problem on-site assistance and
scheduled preventative maintenance. You receive telephone support that gives you timely answers and solves
most software problems. In addition, you get revised versions of the software and documentation, and system
newsletters or dispatches.
BASIC Service is ideal for customers who have a staff
whose experience and expertise enables them to analyze
and communicate a software problem to DIGITAL remote
support centers. You receive telephone support that gives
you timely answers and solves most software problems. In
addition, you get revised versions of the software and documentation, and system newsletters or dispatches.

(

Self·M81nt9n•nc• Service is designed for customers who
require revised versions of the software and documentation from DIGITAL. In addition, you get system newsletters
or dispatches and may submit software performance questions.
All agreements are available to licensed DIGITAL customers on an annual, contractual basis. Service coverage is
extended to the DIGITAL Engineering Certified networks (in
the specified countries) listed in Table 2.
A variety of service options may be added to an existing
Software Product Service Agreement, such as service for
multiple-like systems. Contact your DIGITAL representative for additional information and ordering details.
The Prerequisite Software, as specified by this SPD, must

have the equivalent level Software Product Service.

(
189

For more information on what is included In these agreements, please obtain the appropriate Service Description
from your local DIGITAL office.
Trmlnlng From Educdonlll Servicff
To ensure customer success with DIGITAL products, Educational Services sells training for the installation, maintenance and/or management of DIGITAL software. Course
formats vary from seminars to packaged training materials
that include self-paced instruction and computer-based
instruction to traditional lecture/labs at DIGITAL's worldwide Training Centers.
For a complete listing of course schedules and prices, refer
to the DIGEST, Educational Services' quarterly publication.
For curriculum-specific information, training recommendations and assistance in planning training programs, please
contact your Educational Services Representative.

ProfeuiONll Sottw•re Services
DIGITAL Software Specialists are available on a per-<:811 or
resident contract basis to help in all phases of software
development or implementation. Specialists are available to
serve as technical consultants, decision support consultants or business systems analysts. Resources are avail·
able to:
• Supplement your programming staff
• Assume project management responsibility
• Develop software
• Augment a system start-up service package with tailored services to meet specific needs
Contact your DIGITAL representative for additional information and ordering details.

SPO 10.42.03

RSX-11 PSl/M, Version 2.1
SOFTWARE OPTIONS CHART

The distribution Media Codes used in the Software Options Chart are described below. You specify the desired Media COde
at the end of the Order Number, e.g., QJD91-HD • binaries on 9-track 800 BPI Magtape (NAZI).
D •
H M •

9-track 800 BPI Magtape (NAZI)
RL02 Disk Cartridge
9-track 1600 BPI Magtape (PE)

NOTE:

V • RK07 Disk Cartridge
Z = No hardware dependency

The av.llabillty of theM softwant product options and services may vary by country. Customers should contact their local DIGITAL oftlce for Information on availability
ORDER
NUMBER

OPTIONS

LICENSE OPTIONS: A LICENSE IS REQUIRED FOR EACH CPU.
Single-Use License

QJD91-UZ

MATERIALS AND SERVICE OPTIONS:
Distribution and Documentation Option

QJD91-HD
QJD91-HH
QJD91·HM
QJD91-HV

Software Revision Right-To-Copy Option

QJD91-HZ

Documentation Only Option

QJD91·GZ

Installation Service Option

QJD91-ID
QJD91-IH
QJD91-IM
QJD91-IV

DECsupport Service

QJD91-9D
QJD91-9H
QJD91-9M
QJD91-9V

Basic Service

QJD91-8D
QJD91-8H
QJD91-8M
QJ191-8V

Self-Maintenance Service

QJD92-3D
QJD92-3H
QJD92-3M
QJD92-3V

190

...

(

Software
Product
Description
PRODUCT NAME:

RSX-11 PSl/M·PLUS, Venton 2.1

SPD 10.43.03

Packetnet System Interface
DESCRIPTION
RSX-11 PSl/M-PLUS allows a suitably configured RSX11 M-PLUS system to connect to Packet Switching Data
Networ1ts (PSDNs) conforming to the CCITT recommendation X.25 (June 1980). Using RSX· 11 PSl/M-PLUS, the ~ys
tem may function as packet-mode Data Terminal
Equipment (DTE) on the PSDN. The software product supports access to the facilities offered by X.25 communication for RSX-11 M-PLUS user programs written in MACR011, FORTRAN IV, and FORTRAN IV-PLUS. RSX-11 PSI/
M-PLUS supports task-to-task and remote terminal communications via the X.25 networ1t.
RSX-11 PSl/M-PLUS can coexist with, or operate as a layered product under DECnet-11 M-PLUS to allow use of
DECnet facilities over X.25 PSDNs, as well as point-topoint connections such as private leased lines or switched
telephone networks. For details please refer to the DECnet11 M-PLUS SPD (SPD 10.66.xx).

Talk·to-Talk Communication
For intertask communication. application programs use
RSX-11 M-PLUS executive calls to use the X.25 functions,
including setting up and breaking connections. transmitting
and receiving data, sending and receiving interrupt messages and resetting virtual circuits. This interface, in addition to CCITT X.25 level 3 functions, provides translation of
symbolic DTE addresses. transfer of calls between tasks,
and splitting and recombination of messages. wh~ ~ longer than the packet size ~acted for the arcuit. Na~al
extensions not part of the international recommendations
are not provided. RSX-11 PSl/M-PLUS does not include,
for example, file transfer, file access, or task addressing.

When using this interface an application program can communicate with complementary software on any other system (packet-mode DTE) connected to the network
(DIGITAL or non-DIGITAL). This interface conforms to the
DIGITAL Network Architecture specification for X.25
access.
Remote Terminal Communication•
RSX-11 PSl/M-PLUS supports access by remote terminals
(character-mode DTEs) according to CCITT recommendations X.3, X.28 and X.29. Terminals are supported in
'Remote X.29 Terminal' mode in which code conversions
between ASCII and the actual code used by the terminal
are performed by the network. Note that terminals are con-

nected via a Packet Assembly Disassembly (PAD) facility
provided by the networ1t; no faciHty is offered in the software product whereby a terminal locally connected to an
RSX-11M-PLUS system can act as a network terminal to
other systems connected to the network.
Operation of remote X.29 terminals appears similar to that
of terminals locally connected to the RSX-11M-PLUS system; application programs need not be aware that access
to the terminal is via the RSX-11 PSl/M-PLUS software.
However, applications that bypass operating system control mechanisms such as LOGON/LOGOFF may not function as expected. There may also be restrictions imposed
by the network itself.
The interface presented to an application program using a
remote X.29 terminal is compatible with that to a local terminal, except for those facilities where adequate support is
not provided by the network; for example, the support provided by the PAD for data forwarding upon Input of an
escape sequence is not compatible with that required by
DIGITAL standard software. This means that FMS and
some of the screen editorS may not function as expected
unless the PAD is set up in a cost-ineffective way. Additional facilities are provided which allow a program to manipulate the terminal parameters maintained by the PAD.
Virtual Circuits

RSX-11 PSl/M-PLUS offers communications over both Permanent and Switched Virtual Circuits (PVCs and SVCS),
the maximum total number of virtual circuits supported
being 255, subject to memory availability. The maximum
number of remote terminals supported is 140. Note, however, that each remote terminal uses a virtual circuit. Up to
two physical connections can be made to the PSDN.
Line Dltclpllne

The communications discipline used is the CCITT recommendation X.25. Specifically, the product supports V.24
(EIA - RS232) and CCITT V.35 at the hardware level, the
symmetric LAPB variant of the X.25 frame level protocol,
and the X.25 packet level protocol over point-to-point, 4wire, synchronous. full-duplex lines. An RSX-11 M-PLUS
system configured with PSI appears as a packet-mode
DTE. Operation as Data Circuit Terminating Equipment
(DCE) is not supported.
Netwotlr Management

A Network Control Program and Configuration File Editor

October 1115

soft Ware
(
191

AE·N142D-TC

Rllc-11 PSIJM-PLUS, Yeralon 2.1

SPD 10.43.03

are provided for the control of the operation of the X.25 software. This includes loading and unloading the sottw...
defining the lines, specification of addntsaing Information

for Incoming C8ls and access to error counters and other
rnak1t8nance fl.l1Ctlons. This interface provides a subset of
the DIGITAL Netwcn Architecture specification for Network Management.
RSX-11 PSl/M-PLUS supports two types of communications Interface as presented in the table below. They differ
in many respects, particularly in their effect on CPU utilization. The table shows rated bandwidth for each device type
used at maximum configuration for that device. Bandwidth
Is defined as the total number of bits per second full duplex
(input and output), including protocOI overhead, being handed by the RSX-11 PSl/M-PLUS software. Maximum Una
Speed Is defined as the maximum number of bits per seoond per hardware device that Is supported by the software.
Therefore, the following algorithm may be used In determining valid configurations:

•

MINIMUM HARDWARE REQUIRED
Any valld RSX-11 M-PLUS system configuration with:

Memory Requirements
•

CommunlcdaM

•

SVCS and other network facilities and their support must
be prepared jointly by the customer and DIGITAL

Character Interrupt Devices - With the DUP11, CPU
cycles are required for X.25 packet and frame level pro-o
tocol processing, and also for each character sent and

•

A minimum of 20K words additional memory for resident
RSX-11 PSl/M·PLUS software and data storage. This
includes sufficient memory for basic X.25 operation for
8 virtual circuits. Additional memory is required for
optional features and additional circuits; for example,
each additional virtual circuit will require approxinately
250 words.

A minimum of 9K words additional memory for the RSX11 PSl/M-PLUS X.29 software if Remote Terminals are
supported

•

A minimum of 26K words of additional memory to
dynamically load the RSX-11 PSl/M-PLUS software

RSX Pool Requirements
•

A minimum of 60 words plus 10 words for each network
task • for basic X.25 operation

•

An additional 22 words for each Remote Terminal

received

Operation with DECnet-11 M·PLUS

The KMS11-B and KMS11-P are medium-speed Direct
Memory Access (OMA) communications controllers.
The KMS11-BD/E is an 8-line multiplexer of which 2
lines are supported. The KMS11-PX/Y is a single-line
device. Character transmission and reception and the
X.25 frame level protocol (LAPB) processing Is executed in microcode by the KMS11 communications controller. The PDP-11 CPU processes only the X.25
packet level protocol.

•

Mulmum Mulmum Mllxlmum
Une lpMd Number of IMldwldth
Support9d Supported
(Klllts/MC)
Linn

•

2
2
2

38.4
19.2
76.8

OMA

19.2

76.8

OMA

64.0

128.0

BO/E
KMS11·

•

PDP-11/23-PLUS, PDP-11/24, PDP-11/44, or PDP-11/
70 central processors with one of the following communications devices supporting one (1) One:

•
•
•
•

DUP11-DA low-speed synchronous interface
DPV11-DA low-speed sychrcnous interface
KMS11-BD/E medium-speed synchronous interface
KMS11-PXJY medium-speed synchronous interface

Note:

PX
KMS11·

A maximum of 25,000 blocks of disk space Is required
for Network Generation, of which approximately 5000
blocks must be on a disk that is available throughout the
generation process and will subsequently be used for
RSX-11 PSl/M-PLUS operation.

Processors

Supported
(Klllts/MC)

9.6
4.8
19.2

OUP11
Character
OPV11
Character
OMA
KMS11·

Operation of X.25 virtual circuits under DECnet-11 M·
PLUS incurs extra memory requirements. (Please consult the DECnet-11 M-PLUS SPD (SPD 10.66.xx) for fur·
ther details.)

Disk Space

Table 1
Type

...

PY
Note: This table describes the physical hardware configurations supported by RSX-11 PSl/M·PLUS. It
should be noted that the attachment of such
devices as A/D converters and timesharing terminals can reduce the maximum number of lines or
bandwidth that can be supported.

For PTT certification purposes, the combination of
any KMS11 ·B controller hardware and X.25 level 2
microcode (which is supplied as part of RSX-11
PSl/M-PLUS product) is known as the KMX11.

GROWTH CONSIDERATIONS
The minimum hardware requirements for any future version
of this product may be different from the minimum hard·
ware requirements for the current version.
OPTIONAL HARDWARE

PREREQUISITE SUPPORT PLAN
A Netwcn Profile and Customer Support Plan covering all
the intended network nodes, their usage of PVCs and

A communications interface and/or additional line. The
product supports up to two (2) DUP11s or one (1) KMS11
line together with one (1) DUP11.

t
192

SPD 10.43.03

RSX·11 PSl/M·PLUS. Ver91on 2.1

For network• and coumry comblnetlona other lllen
thoM llamd In Table 2 under WARRANTY LIMITATIONS

PREREQUISITE SOFTWARE
RSX·11M-PLUS Operating System

erence Table (SPD 20.99.xx) for the required version.

THIS PRODUCT IS PROVIDED "AS IS" WITHOUT ANY
WARRANTY OF ANY KIND EITHER EXPRESS OR
IMPLIED.

OPTIONAL SOFTWARE

WARRANTY LIMITATIONS

Refer to the RSX-11 M-PLUS Optional Software Cross Ref·

DECnet-11 M-PLUS

DIGITAL has designed or adapted this software product to
operate on the networks in the associated countries listed
in Table 2.

FORTRAN IV/RSX

FORTRAN-77/RSX

SOFTWARE WARRANTY
For networks Hated In Table 2 under WARRANTY LIMI·
TATIONS when operamd In the aa90Clat9d country as
shown
Warranty for this software product is provided by DIGITAL
with the purchase of a license for the product. There is no
additional charge. This software product is warranted to
conform to the Software Product Description (SPD). This
means that DIGITAL will remedy any nonconformance
when it is reported to DIGITAL by the customer during the
warranty period.

The warranty period is ninety (90) days. It begins when the
software is instalted or thirty (30) days after delivery to the
end user, whichever occurs first and expires ninety (90)
days later. An warranty related support for this software wiH
end 180 days after release of the subsequent version.
Warranty is provided in the country of purchase. DIGITAL
will provide a service location which will accept reporting (in
a format prescribed by DIGITAL) of a nonconformance
problem caused when using the licensed software under
normal conditions as defined by the SPD. DIGITAL will remedy a nonconformance problem in the current unaltered
release of the licensed software by issuing correction information such as: correction documentation, corrected code,
or notice of availability of corrected code; or a restriction or
a bypass. The customer will be responsible for the
preparation and submission of the problem report to the service location.
Warranty Exclusion

(

DIGITAL DOES NOT WARRANT THAT THE SOFTWARE
LICENSED TO CUSTOMER SHALL BE ERROR FREE,
THAT THE SOFTWARE SHALL OPERATE WITH ANY
HARDWARE AND SOFTWARE OTHER THAN AS SPECIFIED IN THIS SPD, THAT THE SOFTWARE SHALL SAT·
ISFY CUSTOMER'S OWN SPECIFIC REQUIREMENTS.
OR THAT COPIES OF THE SOFTWARE OTHER THAN
THOSE PROVIDED OR AUTHORIZED BY DIGITAL
SHALL CONFORM TO THE SPD.
DIGITAL MAKES NO WARRANTIES WITH RESPECT TO
THE FITNESS AND OPERABILITY OF MODIFICATIONS
NOT MADE BY DIGITAL.
IF THE SOFTWARE FAILS TO FUNCTION FOR REA·
SONS STATED ABOVE, THE CUSTOMER'S WARRANTY
WILL BE INVALIDATED AND ALL SERVICE CALLS WILL
BE BILLABLE AT THE PREVAILING PER CALL RATES.

(
193

While this software may function correctly with other
packet-switching networks, DIGITAL cannot offer its standard warranty for this software unless it has been tested
with such networks and found acceptable to DIGITAL.

Table 2
~-epecltlc

DIGITAL lnst811ed

documentmtlon
Included

llld Suppor'9d

yes
yes

yes
yes
yes

yes
yes

Datapec (Cenada)
Datex-P (Waet Germany)
PSS (United Kingdom)
Telenet (United States)
Telepac (Switzerland)
Transpac (France)
Tymnet (United States)
Pacnet (Taiwan)

yes

Since the Introduction of this software, otts configurations
may have been tested. Please contact your local DIGITAL
office for up-to-date infonnation regarding listed configura-

tions.

INSTALLATION

Customer Reaponlibllltlea
Before installation of the software, the customer must:
•

Previously have installed all requisite software and hardware including terminals.

•

Obtain, install and demonstrate as operational any
modems and other equipment and facilities necessary
to interface to DIGITAL's communication equipment.

•

Demonstrate equivalency of operation for modems
other than Bell 208A, 208B, 209, 212A synchronous
modems or In Europe, PTT approved modems.

•

Make available for a reasonable period of time, as mutually agreed by DIGITAL and the customer, all hardware.
communication facilities and terminals that are to be
used during installation.

•

For multi-node networks, designate one adjacent node
to verify installation/connectivity.

•

The X.25 network verification portion of this product's
installation requires that the customer subscribe to the
Open User Group and to at least one Switchec:I Virtual
Circuit. Systems with exclusively Permanent Virtual Circuits or Closed User Group membership require spe-

SPD 10.43.03

RSX-11 PSIJM-PLUS, Version 2.1
cia11y negotiated arrangements for DIGITAL lnstallatiOn
of this product.
Delays cauaed by any failure to meet the responsibilities
win be charged at the then prevdng rate for time and materials.
For thoH network• Hat9d In Table 2 under WARRANTY
LIMITATIONS
DIGITAL requires that a customer's first purchase of this
software product include DIGITAL Installation Services.
These services provide for installation of the software product by an experienced DIGITAL Software Specialist.
For subsequent purchases of this product only experienced customers should attempt installation. DIGITAL recommends that all other customers purchase DIGITAL's
Installation Services.
DIGITAL's Installation Services can be purchased as a separate service.
Courteay lnatalletlon Service
This software product wtH be installed by DIGITAL at no
additional charge if you purchase it concurrent with a
Startup Service Package that includes installation service.
Both the operating system and this product must be
installed concurrently.
For network• other than thoM llamd In Table 2 under
WARRANTY LIMITATIONS
This software product can be installed by the customer
using the step-by-step documentation available for this
product.

•

Single-Use License Option, and

•

Distribution and Documentation Option

The license gives you the right to use the software on a
single CPU and the Distribution and Documentation Option
provides the machine-readable software and retated documentation.
To use this software product on additional CPUs, you must
purchase for each CPU as a minimum:
•

Single-Use License Option

In addition to the right to use, the license gives you the onetime right to copy the software from your original CPU
installation to the additional CPU. Therefore, the Distribution and Documentation Option is not required, but
optional.
MATERIALS AND SERVICE OPTIONS
Dlatributlon and Documentation Option

The Right-To-Copy Option allows a customer with multiple

ORDERING INFORMATION

CPUs to copy a revised version of a software product from

Single-Use licensed software is furnished under the licensing provisions of DIGITAL's Standard Terms and Conditions of Sale, which provide in part that the software and
any part thereof may be used on only the single CPU on
which the software is first installed, and may be copied, in
whole or in part (with the proper inclusion of DIGITAL's
copyright notice and any proprietary notices on the software) for use on such CPU.
You wlU need a separate license for each CPU on which
you wtH be using the software product (except as otherwise
specified by DIGITAL). Then you will select the Materials
and Service Options you need to utilize the product effectively. IF YOU ARE ALREADY FAMILIAR WITH THESE
OPTIONS, YOU MAY OBTAIN THE ORDERING INFORMA·
TION DIRECTLY FROM THE SOFTWARE OPTIONS
CHART. In most cases, you wiH want to review the following descriptions to determine what options you require.
LICENSE OPTIONS

Single-UM LicenM Option

The Single-Use License is your right to use the software
product on a single CPU and it includes your 90 day warranty.
For your first installation of this software product you must
purchase as a minimum:

194

one CPU to another. Each CPU must be licensed for that
product. You first install the revised software on one CPU;
then you can make copies for additional CPUs by purchasing the Right-To-Copy Option for each additional CPU.

If you prefer to automatically obtain the right-to-copy, you
must purchase a Service Right-to-Copy for each additional
CPU; this is a service added to a Software Product Service
Agreement.
Documentatlon-Qnfy Option
You can obtain one copy of the basic documentation by
purchasing the Documentation-Only Option.
lnatallatlon Service Option
DIGITAL's Installation Service is provided by a DIGITAL
Software Specialist and accelerates your productive use of
this product. For more information on what is included in
this service, please obtain the appropriate Service Description from your local DIGITAL office.
Installation Service will be provided at no additional charge
(Courtesy Installation) under the conditions described in the
Installation section above.
Consult Table 2 under WARRANTY LIMITATIONS for a list
of networks and countries where this service is available.

...

(

RSX-11 PSl/M·PLUS, Venlon2.1

SPD 10.43.03

Sottwllre Product Service Agreements
DIGITAL offers licensed customers annual Software Product Service Agreements to maintain their software:
DECaupport Service is the most comprehensive level of
service offering critical problem on-site assistance and
scheduled preventative maintenance. You receive telephone support that gives you timely answers and solves
most software problems. In addition, you get revised versions of the software and documentation, and system
newsletters or dispatches.
BASIC Service is ideal for customers who have a staff
whose experience and expertise enables them to analyze
and communicate a software problem to DIGITAL remote
support centers. You receive telephone support that gives
you timely answers and solves most software problems. In
eddltion, you get revised versions of the software and documentation, and system newsletters or dispatches.
Self-Mlllntenance Service is designed for customers who
require revised versions of the software and documentation from DIGITAL. In addition, you get system newsletters
or dispatches and may submit software performance questions.
All agreements are available to licensed DIGITAL customers on an annual, contractual basis. Service coverage is
extended to the DIGITAL Engineering Certified networks (in
the specified countries) listed in Table 2.
A variety of service options may be added to an existing
Software Product Service Agreement, such as service for
multiple-like systems. Contact your DIGITAL representative for additional information and ordering details.

The Prerequisite Software, as specified by this SPD. must
have the equivalent level Software Product Service.

(
195

For more information on what is included in these agreements, please obtain the appropriate Service Description
from your local DIGITAL office.
Training From Educdonal Services
To ensure customer success with DIGITAL products, Edu·
cational Services sells training for the installation, maintenance and/or management of DIGITAL software. Course
formats vary from seminars to packaged training materials
that include self·paced instruction and computer-based
instruction to traditional lecture/labs at DIGITAL's worldwide Training Centers.
For a complete listing of course schedules and prices, refer
to the DIGEST, Educational Services' quarterly publication.
For curriculum-specific information, training recommend&·
tions and assistance in planning training programs, please
contact your Educational Services Representative.

Profe1sl01111I Software Servicel
DIGITAL Software Specialists are available on a per-call or
resident contract basis to help in all phases of software
development or implementation. Speciallsts are available to
serve as technical consultants, decision support consult·
ants or business systems analysts. Resources are available to:
•
•
•
•

Supplement your programming staff
Assume project management responsibility
Develop software
Augment a system start-up service package with tai·
lored services to meet specific needs

Contact your DIGITAL representative for additional information and ordering details.

RSX·11 PSI/II-PLUS, Venlon 2.1

SPD 11.43.03
SOFTWARE OPTIONS CHART

The distribution Media Codes used in the Software Options Chart are described below. You specify the desired Media Code
at the end of the Order Number, e.g., QJD92-HD • binaries on 9-track 800 BPI Magtape (NAZI).
D • 9-track 800 BPI Magtape (NAZI)
H • RL02 Disk Cartridge
M • 9-track 1600 BPI Magtape (PE)

V • RK07 Disk Cartridge
Z = No hardware dependency

NOTE: The avallablllty of these software product option• and aervice• may vary by country. Customers should con·
tact their local DIGITAL office tor intonnatlon on availablllty
OPTIONS

ORDER
NUMBER

LICENSE OPTIONS: A LICENSE IS REQUIRED FOR EACH CPU.
Singl&-Use License

QJD92-UZ

MATERIALS AND SERVICE OPTIONS:
Distribution and Documentation Option

QJD92-HD
QJD92-HH
QJD92-HM
QJD92-HV

Software Revision Right-To-Copy Option

QJD92-HZ

Documentation Only Option

QJD92-GZ

Installation Service Option

QJD92-ID
QJD92-IH
QJD92-IM
QJD92-IV

DECsupport Service

QJD92-9D
QJD92-9H
QJD92-9M
QJD92-9V

Basic Service

QJD92-8D
QJD92-8H
QJD92-8M
QJD92-8V

Self-Maintenance Service

QJD92-3D
QJD92-3H
QJD92-3M
QJD92-3V

t
196

(

Software
Product
Description
PRODUCT NAME:

PDP-11 PASCAL/RSX, Version 1.2
•

DESCRIPTION
PDP-11 PASCAL/RSX is an implementation of the Pascal
language that accepts programs compatible with Level
of the ISO Specification for the Computer Programming
Language Pascal (Draft International Standard 7185).
PDP-11 PASCAL/RSX is a multipass optimizing compiler
that provides all standard Pascal data types and statements as well as extensions.

lie/OT P..cal LAnguage Element•

INTEGER, REAL, CHAR, BOOLEAN, enumerated and
subrange data types

•

ARRAY, RECORD, SET and FILE structured data

MODULE reserved word for separate and independent
compilation

•

STATIC and AUTOMATIC allocation attributes

•

%INCLUDE directive to allow multiple compilation units
to access the same program text

•

Binary, hexidecimal, and octal constants

•

Exponential operator

•

Dollar sign ($) and underscore (_) characters in identi-

fiers

The data types, control statements, and predeclared functions and procedures provided by Pascal include:
•

SPO 14.18.0I

•

Value initialization in declaration section at program
level

•

Predefined procedures CLOSE, DATE, OPEN, TIME,
and HALT

types

Complletlon

•

FOR, REPEAT, WHILE repetitive control statements

•

CASE, IF-THEN, and IF-THEN-ELSE conditional statements

•

BEGIN ... END compound statement

PDP-11 PASCAL/RSX programs can be compiled in interactive mode or with an indirect command file. The PDP-11
PASCAL/RSX compiler performs optimizations designed
to improve execution speed, including constant folding,
constant conversion, constant pooling, and global register
assignment. Optional instruction to the compiler and input
and output file attributes are specified by compiler
switches that:

•

GOTO statement

•

READ, WRITE, READLN, and WRITELN input and
output procedures

•

FORWARD procedure and function directive

POP-11 PASCAL/RSX EldWlllon1
•

•

Perform run-time checks of array bound, case selectors, pointers, string bounds, and subrange bounds

•

Umit the number of error messages printed and allow
compilation to continue regardless of the number of

Support for RSX File Control System (FCS) sequential
files with fixed or variable length records

errors
Cause code to be generated that provides source line
numbers at run-time

•

Determine whether to generate EIS or FPP instructions

•

Sequential access to fixed or variable length records,
and both direct and sequential access to fixed length
records

•

User-Mode Instruction and Data space support on processors where both the hardware and software support this feature.

• Produce an optimal, machine-code listing

•

EXTERNAL procedure and function directive

•

OTHERWISE clause in case statements

•

REM operator to supply the remainder in division operations

•

GLOBAL, LOCAL, and EXTERNAL attributes on variables and subprograms

•

Identify the PDP-11 PASCAL/RSX compiler version
number

•

Print warning-level messages that identify the use of
PDP-11 PASCAL/RSX extensions

•

Provide automatic spooling of the listing file

•

Maintain qualifier settings for subsequent compilations
in interactive mode or in the same indirect command
file

October 1985

softWare
(
197

AE-Nl17G-TC

SPD 14.11.0I

PDP·11 PASCAL/RSX, Version 1.2
Task Bulldlng
After compilation, the RSX Task Builder is used to produce an executable image file, and to provide support for
both relocatable and resident object librarles. Task builder
options create checkpointable tasks, identify the use of
floating point hardware, provide On-line Debugging Tech·
nlque (ODT) support and allow simultaneous execution of
multiple versions of a single task.
RSX Environment

PDP-11 PASCAL/RSX allows use of the FORTRAN stan·
dard calling sequence.permitting Pascal programs to communicate with FORTRAN callable system routines for
real-time applications. However, routines written in FOR·
TRAN cannot be called from PDP-11 PASCAL/RSX. In
addition, PDP-11 PASCAL/RSX programs can call RSX
system servlcas for process-control operations, system
directives, and special peripheral access.
MINIMUM HARDWARE REQUIRED
Any valid mapped RSX-11 M or RSX-11 M-PLUS system
configuration that includes:
•

Extended Instruction Set (EIS)

•

A minimum of 30K words of available memory, with
approximately 800 free blocks of disk space required
for the compiler and OTS flies. Of the 800 tree blocks
required, 675 blocks must be contiguous.

Additional disk space is required during compiler execution. The amount of additional space required varies with
the size and complexity of the source program.

Warranty is provided in the country of purchase. DIGITAL
will provide a service location which will accept reporting
(in a format prescribed by DIGITAL) of a nonconformance
problem caused when using the licensed software under
normal conditions as defined by the SPD. DIGITAL will
remedy a nonconformance problem in the current unaltered release of the licensed software by issuing correc·
tion information such as: correction documentation, cor·
rected code, or notice of availability of corrected code; or
a restriction or a bypass. The customer will be responsible
for the preparation and submission of the problem report
to the service location.

Warranty Exclualon
DIGITAL DOES NOT WARRANT THAT THE SOFTWARE
LICENSED TO CUSTOMER SHALL BE ERROR FREE,
THAT THE SOFTWARE SHALL OPERATE WITH ANY
HARDWARE AND SOFTWARE OTHER THAN AS SPECI·
FIED IN THIS SPD, THAT THE SOFTWARE SHALL SAT·
ISFY CUSTOMER'S OWN SPECIFIC REQUIREMENTS,
OR THAT COPIES OF THE SOFTWARE OTHER THAN
THOSE PROVIDED OR AUTHORIZED BY DIGITAL
SHALL CONFORM TO THE SPD.
DIGITAL MAKES NO WARRANTIES WITH RESPECT TO
THE FITNESS AND OPERABILITY OF MODIFICATIONS
NOT MADE BY DIGITAL.
IF THE SOFTWARE FAILS TO FUNCTION FOR REA·
SONS STATED ABOVE, THE CUSTOMER'S WAR·
RANTY WIU BE INVALIDATED AND ALL SERVICE
CAUS WIU BE BILLABLE AT THE PREVAILING PER
CALL RATES.

OPTIONAL HARDWARE

INSTALLATION

•

This software product can be installed by the customer
using the step-by-step documentation available for this
product. Optionally you can purchase DIGITAL Installation
Services which provide for the installation of the software
product by an experienced DIGITAL Software Specialist.

Floating Point Processor as supported by the system
configuration

PREREQUISITE SOFTWARE
RSX-11 M or RSX-11 M-PLUS Operating System
Refer to the RSX-11 M and RSX· 11 M·PLUS Optional Soft·
ware Cross Reference Tables (SPD 20.98.xx and SPD
20.99.xx) for the required versions.
OPTIONAL SOFTWARE
None
SOFTWARE WARRANTY
Warranty for this software product is provided by
DIGITAL with the purchase of a license for the product.
There is no additional charge. This software product is
warranted to conform to the Software Product Description (SPD). This means that DIGITAL will remedy any nonconformance when It is reported to DIGITAL by the customer during the warranty period.
The warranty period is ninety (90) days. It begins when
the software is installed or thirty (30) days after delivery to
the end user, whichever occurs first and expires ninety
(90) days later. Ali warranty related support for this software wiU end 180 days after release of the subsequent
version.

19 8

DIGITAL's Installation Services can be purchased as a
separate service.

Courtesy lnatelletlon Service
This software product will be installed by DIGITAL at no
additional charge if you purchase it concurrent with a
Startup Service Package that includes installation service.
Both the operating system and this product must be
installed concurrently.
ORDERING INFORMATION
Single-Use licensed software is furnished under the licensing provisions of DIGITAL's Standard Terms and Condi·
tions of Sale, which provide in part that the software and
any part thereof may be used on only the single CPU on
which the software is first installed, and may be copied, in
whole or in part (with the proper inclusion of DIGITAL's
copyright notice and any proprietary noticeS on the soft·
ware) for use on such CPU.
You will need a separate license for each CPU on which
you will be using the software product (except as other·

PDP-11 PASCAL/RSX, Venlon 1.2

SPD 14.11.0I

wise specified by DIGITAL). Then you will select the
Materials and Service Options you need to utiHze the
product effectively. IF YOU ARE ALREADY FAMILIAR

WITH THEii! OPTIONS, YOU MAY OBTAIN THE ORDERING INFORMATION DIRECTLY FROM THE SOFTWARE
OPTIONS CHART. In most cases, you will want to review
the following descriptions to detennlne what options you

require.

LICENSE OPTIONS
The Slng!HJse License Is your right to use the software
product on a single CPU and It includes your 90 day
warranty.
For your first instillation of this software product you
must purchase as a minimum:
Single-Use License Option, and

•

Distribution and Documentation Option

The lioense gives you the right to use the software on a
slngle CPU and the Distribution and Documentation
Option provides the machine-readable software and
related documentation.
To use this software product on additional CPUs, you
must purchase for each CPU as a minimum:
• Single-Use Lloense Option
In addition to the right to use, the lioense gives you the

one-time right to copy the software from your original
CPU installation to the additional CPU. Therefore, the
Distribution and Documentation Option is not required,
but optional.
The lloensee may also reproduce and distribute object
modules and/or resident llbrarles which are necessary to
run programs compiled with this product provided such
programs are distributed: 1) in accordance with the provisions of lloensee's standard software lloense; or 2) with
lioensee's copyright notice included on such programs; or
3) if conditions (1) or (2) are not met, with DIGITAL'$
COPYRIGHT notice included on such programs.

MATERIALS AND SERVICE OPTIONS
Dlatrtbudon and Documen•llon ()piton

Single-UM LlcenM Option

•

that product. You first install the revised software on one
CPU; then you can make copies for additional CPUs by
purchasing the Right-To-Copy Option for each additional
CPU.

(
199

You can obtain one copy of the basic documentation by
purchasing the Documentation-Only Option.
lnatlllldon Service Option
DIGITAL's Installation Service is provided by a DIGITAL
Software Specialist and accelerates your productive use
of this product. For more information on what is included
in this service, please obtain the appropriate Service
Description from your local DIGITAL office.
Installation Service will be provided at no additional
charge (Courtesy Installation) under the conditions
desaibed in the Installation section above.
Soflwere Product Service Agreements
DIGITAL offers lloensed customers annual Software Product Service Agreements to maintain their software:
DECsupport Service Is the most comprehensive level of
service offering critical problem on-site assistance and
scheduled preventative maintenance. You receive telephone support that gives you timely answers and solves
most software problems. In addition, you get revised
versions of the software and documentation, and system
newsletters or dispatches.

BASIC Service is ideal for customers who have a staff
whose experience and expertise enables them to analyze
and communicate a software problem to DIGITAL remote
support centers. You receive telephone support that gives
you timely answers and solves most software problems.
In addition, you get revised versions of the software and
documentation, and system newsletters or dispatches.
Self-M91ntenence Service is designed for customers
who require revised versions of the software and documentation from DIGITAL. In addition, you get system
newsletters or dispatches and may submit software performance questions.
A variety of service options may be added to an existing
Software Product Service Agreement, such as service for
multiple-like systems. Contact your DIGITAL representative for additional information and ordering details.
The Prerequisite Software, as specified by this SPD, must
have the equivalent level Software Product Service.
For more information on what is included in these agreements, please obtain the appropriate Service Description
from your local DIGITAL office.
Tn1lnlng From Educ:etlonel Services
To ensure customer success with DIGITAL products, Educational Services sells training for the installation, mainte-

SPD14.11.0I

PDP-11 PASCAL/RSX, Ver81on 1.2
nance and/or management of DIGITAL software. Course
formats vary from seminars to packaged training materials
that include self-paced instruction and computer-based
instructiOn to traditional lecture/lllbll at DIGITAL's worldwide Training Centers.

or resident contract basis to help in all phasas of software
development or implementation. Spacialists are available
to serve as technical consultants, decision support consultants or business systems analysts. Resources are
available to:

For a complete listing of course schedules and prices,

• Supplement your programming staff
• Assume project management responsibility
• Develop software
• Augment a system start-up service package with tailored services to meet specific needs

refer to the DIGEST, Educational Services' quarterly publication. For cunlculurn-specific Information, training recommendations and assistance In planning training programs,
plaasa contact your Educational Services Representative.
Prote. .lonal Software Services

DIGITAL Software Specialists are avallable on a per-call

Contact your DIGITAL representative for additional information and ordering details.

l
200

(

SPD 14.18.08

PDP-11 PASCAL/RSX. Yenlon 1.2

SOFTWARE OPTIONS CHART
The distribution Media Codes used in the Software Options Chart are desa'lbed below. You specify the desired Media Code
at the end of the Order Number, e.g., QJ128-HD •binaries on 9-track 800 BPI Magtape (NRZI).
5 • TKSO Tape cartrtdge
D • 9-track 800 BPI Magtape (NRZI)
H • RL02 Dtsk Cartridge

M • 9-track 1600 BPI Magtape (PE)
V • RK07 Disk Cartridge
Z • No hardware dependency

NOTE: The av.ll8blllty of tlleM Mftware product option• and MrVlcea may vary by country. Cuatomera ahould contllet their loclll DIGITAL ofllce for Information on avallablllty.
ORDER
NUMBER
CLASSH1
SYSTEMS

ORDER
NUMBER
CLASS LI
SYSTEMS

QJ128-UZ

QY128-UZ

Distribution and Documentation Option

QJ128-HD
QJ128-HH
QJ128-HM
QJ128-HV

QY128-HS
QY128-HH
QY128-HM

Software Revision Right-To-Copy Option

QJ128-HZ

QY128-HZ

Documentation Only Option

QJ128-GZ

QY128-GZ

Installation Service Option

QJ128-ID
QJ128-IH
QJ128-IM
QJ128-IV

QY128-15
QV128-IH
QY128-IM

DECsupport Service

QJ128-9D
QJ128-9H
QJ128-9M
QJ128-9V

QY128-95
QY128-9H
QY128-9M

Basic Service

QJ128-8D
QJ128-8H
QJ128-8M
QJ128-8V

QY128-85
QY128-8H
QY128-8M

Self-Maintenance Service

QJ128-30
QJ128-3H
QJ128-3M
QJ128-3V

QY128-35
QY128-3H
QY128-3M

OPTIONS

LICENSE OPTIONS:A LICENSE IS REQUIRED FOR EACH CPU.
Single-Use License
MATERIALS AND SERVICE OPTIONS

Class H (for high-end systems)

-All UNIBUS models and systems
~lcroPDP-11

/83

• Class L (for low end systems)

-All a-eus models and systems except MicroPDP-11 /83
-KD11, KDF11, KDJ11 CPU modules
1lCT11, DCF11, DCJ11 mk:roprocessor chips

(
201

(

Software
Product

Descr1pt1on
PRODUCT NAME:

Micro/RSX FORTRAN·n, Version 5.0

DESCRIPTION
Micro/RSX FORTRAN-77 is an extended implementation
of the ANSI subset FORTRAN-77 standard (X3.9-1978)
that runs on the Micro/RSX Operating System. Micro/RSX
FORTRAN-77 contains all the features of the ANSI
FORTRAN- 77 subset, many of the full-set language features, and extensions that are not included in the ANSI
FORTRAN-77 standard. Switch selectable support is provided for user programs based on the previous ANSI
FORTRAN Standard (X3.9-1966).

Micro/RSX FORTRAN-77 programs can be optionally executed under control of Micro/RSX FORTRAN-77 DEBUG
(SPD 14.79.xx). Execution of application programs using
PDP-11 FORTRAN-77 DEBUG aids in the locating of
progamming errors in successfully compiled programs that
behave abnormally when executed.
Micro/RSX FORTRAN-77 includes all subset ANSI features including:
CHARACTER data type

•

Block IF construct including IF... THEN, ELSE IF,
ELSE and END IF statements, for conditional execution of blocks of statements

The Micro/RSX FORTRAN-77 compiler includes the following features of full-language FORTRAN as defined by
the ANSI Standard:
•

Double precision and complex data types

•

Intrinsic functions, including LEN, ICHAR, and
INDEX

•

Exponentiation forms, including double precision
and complex

•

Generic function selected based on argument data
type for FORTRAN-defined functions

•

Lower and upper bounds specification in array
declarators

•

Substrings of character variables and character
array elements

•

Optional syntax for 110 statements (UNIT= and
FMT=)

Micro/RSX FORTRAN-77 includes the following extensions to the ANSI Standard:

Micro/RSX FORTRAN-77 meets the Federal Information
Processing Standard Publication (FIPS PUB-69) requirement for a flagger. The flagger optionally produces diagnostic messages for syntax and/or source form elements
that do not conform to the full-level ANSI FORTRAN X3.91978 Standard.

•

SPD 18.04.01

•

Language elements for keyed and sequential
access to RMS multikey ISAM files

•

DEFINE FILE, FIND, DELETE, REWRITE, and
UNLOCK statements

•

TYPE and ACCEPT input/output statements

•

Comments permitted at the end of each source line

•

INCLUDE statement

•

BYTE data type

•

ENCODE, DECODE statements

•

Explicit specification of storage allocation units for
data types (e.g., INTEGER*4)

•

Hexadecimal and octal constants

•

Virtual array support for systems with memory management directives. Virtual arrays are memory-resident and require enough main memory to contain all
elements of all arrays.

•

O and Z format edit descriptors

The Micro/RSX FORTRAN-77 compiler produces direct
PDP-11 machine code optimized for execution-time efficiency on a Micro/PDP-11 with a floating point processor.
Micro/RSX FORTRAN-77 compiler optimizations include:
•

Optimization of arithmetic and logical IF statements

•

Common subexpression elimination

•

Format edit descriptors, including S, SP, SS, T, TL,
TR, Lw.m, and Gw.dEe

•

Removal of invariant expressions from DO loops

•

Generalized DO loop parameters

•

Allocation of processor registers across block IF
constructs and DO loops

September 1985

soft Ware
(
203

AE·BA93B·TC

Micro/RSX FORTRAN-n, Version 5.0

SPD 18.04.01

Object Time System

Warranty Exclusion

The Micro/RSX FORTRAN-77 Object Time System (OTS)
is a set of object modules that are selectively linked with
compiler-produced object modules by the operating system's task builder, to produce a task (program) ready for
execution.

Micro/RSX FORTRAN-77 provides the capability of creating an OTS based on Record Management Services
(RMS) which uses RMS to provide access to sequential,
relative, and indexed organization files.
MINIMUM HARDWARE REQUIRED
A valid Micro/RSX system configuration with a KEF11-AA
Floating Point Chip Option or an FPF11 Hot Floating Point
Processor Card.
OPTIONAL HARDWARE
The following optional workstation specific hardware is
supported:
•
•

VSxxx-AB Digitizing Tablet with cursor and stylus
LA210

DIGITAL MAKES NO WARRANTIES WITH RESPECT TO
THE FITNESS AND OPERABILITY OF MODIFICATIONS
NOT MADE BY DIGITAL.
IF THE SOFTWARE FAILS TO FUNCTION FOR
REASONS STATED ABOVE, THE CUSTOMER'S
WARRANTY WILL BE INVALIDATED AND ALL SERVICE
CALLS WILL BE BILLABLE AT THE PREVAILING PER
CALL RATES.
INSTALLATION
This software product can be installed by the customer
using the step-by-step documentation available for this
product. Optionally you can purchase DIGITAL Installation
Services which provide for the installation of the software
product by an experienced DIGITAL Software Specialist.

LASO, LA 100, and LN03 printers

PREREQUISITE SOFTWARE
Micro/ASX Operating System (Base Kit)
Refer to the Micro/RSX Optional Software Cross Reference Table (SPD 20.95.xx) for the required version.
OPTIONAL SOFTWARE

DIGITAL's Installation Services can be purchased as a
separate service.
Courtesy Installation Service

Micro/RSX FORTRAN-77 DEBUG
SOFTWARE WARRANTY
Warranty for this software product is provided by DIGITAL
with the purchase of a license for the product. There is no
additional charge. This software product is warranted to
conform to the Software Product Description (SPD). This
means that DIGITAL will remedy any nonconformance
when it is reported to DIGITAL by the customer during the
warranty period.
The warranty period is ninety (90) days. It begins when the
software is installed or thirty (30) days after delivery to the
end user, whichever occurs first and expires ninety (90)
days later. All warranty related support for this software will
end 180 days after release of the subsequent version.
Warranty is provided in the country of purchase. DIGITAL
will provide a service location which will accept reporting
(in a format prescribed by DIGITAL) of a nonconformance
problem caused when using the licensed software under
normal conditions as defined by the SPD. DIGITAL will
remedy a nonconformance problem in the current unaltered release of the licensed software by issuing correction
information such as: correction documentation, corrected
code, or notice of availability of corrected code; or a restriction or a bypass. The customer will be responsible for the
preparation and submission of the problem report to the
service location.

204

This software product will be installed by DIGITAL at no
additional charge if you purchase it concurrent with a Startup Service Package that includes installation service.
Both the operating system and this product must be
installed concurrently.
ORDERING INFORMATION
Single-Use licensed software is furnished under the licensing provisions of DIGITAL's Standard Terms and Conditions of Sale, which provide in part that the software and
any part thereof may be used on only the single CPU on
which the software is first installed, and may be copied, in
whole or in part (with the proper inclusion of DIGITAL'scopyright notice and any proprietary notices on the software)
for use on such CPU.
You will need a separate license for each CPU on which
you will be using the software product (except as otherwise
specified by DIGITAL). Then you will select the Materials
and Service Options you need to utilize the product effectively. You can order these options individually. But, to
ensure that you get the set of services you need and to
simplify ordering, DIGITAL offers Startup Service Packages designed for your environment and experience level.
IF YOU ARE ALREADY FAMILIAR WITH THESE
OPTIONS, YOU MAY OBTAIN THE ORDERING
INFORMATION DIRECTLY FROM THE SOFTWARE
OPTIONS CHART. In most cases, you will want to review
the following descriptions to determine what options you
require.

(

Micro/RSX FORTRAN-n, Version 5.0

SPD 18.04.01

LICENSE OPTIONS

If you prefer to automatically obtain the right-to-copy, you
must purchase a Service Right-to-Copy tor each additional
CPU; this is a service added to a Software Product Service
Agreement.

Single-Use License Option
The Single-Use License is your right to use the software
product on a single CPU and it includes your 90 day
warranty.

Documentation-Only Option
You can obtain one copy of the basic documentation by
purchasing the Documentation-Only Option.

For your first installation of this software product you must
purchase as a minimum:
•
•

Installation Service Option

Single-Use License Option. and
Distribution and Documentation Option

DIGITAL's Installation Service is provided by a DIGITAL
Software Specialist and accelerates your productive use of
this product. For more information on what is included in
this service. please obtain the appropriate Service
Description from your local DIGITAL office.

Single-Use License Option

In addition to the right to use. the license gives you the onetime right to copy the software from your original CPU
installation to the additional CPU. Therefore, the Distribution and Documentation Option is not required, but
optional.
The licensee may also reproduce and distribute object
modules and1or resident libraries which are necessary to
run programs compiled with this product provided such
programs are distributed: 1) in accordance with the provisions of licensee's standard software license; or 2) with
licensee's copyright notice included on such programs; or
3) if conditions (1) or (2) are not met. with DIGITAL'S
COPYRIGHT notice included on such programs.
MATERIALS AND SERVICE OPTIONS
This product is serviced by two basic mechanisms. First,
new releases of the product may provide new features and
remedies tor known software problems. Second, suggestion/problem reports will be acknowledged upon receipt by
DIGITAL. If there is a suitable workaround available tor a
suggestion/problem report it will be provided, otherwise it
will be considered tor inclusion or remedy in a future new
release. The optional service agreements include these
two mechanisms as well as other service offerings.
Distribution and Documentation Option
The Distribution and Documentation option provides the
machine-readable software in binary form and the basic
documentation. You must have. or order, a Single-Use
License to obtain this option. You will need this option to
install the software for the first time. When revised versions
of this software product become available, they may also
be obtained by purchasing this option again.
If you prefer to receive automatic distribution of revised
versions tor this product, you must purchase a Software
Product Service Agreement.

Installation Service will be provided at no additional charge
(Courtesy Installation) under the conditions described in
the Installation section above.

Software Revision Right-To-Copy Option
The Right-To-Copy Option allows a customer with multiple
CPUs to copy a revised version of a software product from
one CPU to another. Each CPU must be licensed for that
product. You first install the revised software on one CPU;
then you can make copies for additional CPUs by purchasing the Right-To-Copy Option for each additional CPU.

Software Product Service Agreements
DIGITAL offers licensed customers annual Software Product Service Agreements to maintain their software:
DECsupport Service is the most comprehensive level of
service offering critical problem on-site assistance and
scheduled preventative maintenance. You receive telephone support that gives you timely answers and solves
most software problems. In addition, you get revised versions of the software and documentation, and system
newsletters or dispatches.
BASIC Service is ideal tor customers who have a staff
whose experience and expertise enables them to analyze
and communicate a software problem to DIGITAL remote
support centers. You receive telephone support that gives
you timely answers and solves most software problems. In
addition, you get revised versions of the software and documentation, and system newsletters or dispatches.
Self-Maintenance Service is designed for customers who
require revised versions of the software and documentation from DIGITAL. In addition. you get system newsletters
or dispatches and may submit software performance
questions.
A variety of service options may be added to an existing
Software Product Service Agreement, such as service tor
multiple-like systems. Contact your DIGITAL representative tor additional information and ordering details.
The Prerequisite Software, as specified by this SPD, must
have the equivalent level Software Product Service.
For more information on what is included in these agreements, please obtain the appropriate Service Description
from your local DIGITAL office.
Training From Educational Services
To ensure customer success with DIGITAL products, Educational Services sells training tor the installation, maintenance and/or management of DIGITAL software. Course
formats vary from seminars to packaged training materials
that include self-paced instruction and computer-based
instruction to traditional lecture/labs at DIGITAL's worldwide Training Centers.

(
205

SPD11.04.01

Micro/ASX FOATAAN-77, Version 5.0

For a complete listing of course schedules and prices. refer
to the DIGEST. Educational Services' quarterly publication. For curriculum-specific information, training recommendations and assistance in planning training programs,
please contact your Educational Services Representative.

•
•
•

Assume project management responsibility
Develop software
Augment a system start-up service package with tailored services to meet specific needs

Contact your DIGITAL representative for additional information and ordering details.

Professional Software Services

DIGITAL Software Specialists are available on a per-call or
resident contract basis to help in all phases of software
development or implementation. Specialists are available
to serve as technical consultants, decision support consultants or business systems analysts. Resources are available to:
•

Supplement your programming staff

SOFTWARE OPTIONS CHART
The distribution Media Codes used in the Software Options Chart are described below. You specify the desired Media Code
at the end of the Order Number, e.g., QY803-H3 = binaries on a RX50 Floppy Diskette.
3 = RXSO Floppy Diskette
5 = TK50 Tape Cartridge
Z = No hardware dependency

NOTE: The avallablllty of th- software product options and Mrvlcea may vary by country. Cuatomera should contllct their ' - I
DIGITAL office for Information on availability.
OPTIONS

ORDER
NUMBER
CLASSL'

ORDER
NUMBER
CLASSW

QP805-UZ

QY803-UZ

LICENSE OPTIONS: A LICENSE IS REQUIRED FOR EACH CPU.
Single-Use License
MATERIALS AND SERVICE OPTIONS:

Distribution and Documentation Option

QY803-H3
QY803-H5

Software Revision Right-To-Copy Option

QY803-HZ

Documentation Only Option

QY803-GZ

Installation Service Option

QY803-13
OY803-15

DECsupport Service

QY803-93
QY803-95

Basic Service

QY803-83
QY803-85

Self-Maintenance Service

QY803-33
QY803-35

Class L Single-Use Ucense:

- All Q-BUS models and systems except MicroPDP-11/83
- KD11, KDF11, KDJ11 CPU modules
- DCT11, DCF11, DCJ11 microprocessor chips
'

Class H Single-Use Ucense:

- All UNIBUS models and systems
- MicroPDP-11/83

206

Software
Product
Descrip1ion
PRODUCT NAME:

Micro/RSX PDP-11 PASCAL, Version 1.2

SPD 18.07.02

•
DESCRIPTION
Micro/RSX PDP-11 PASCAL is an implementation of the
Pascal language that accepts programs compatible with
Level Oof the ISO Specification for the Computer Programming Langauge Pascal (Draft International Standard
7185). Micro/RSX PDP-11 PASCAL is a multipass optimizing compiler that provides all standard Pascal data types
and statements as well as extensions.

(

•

GLOBAL, LOCAL, and EXTERNAL attributes on
variables and subprograms

•

MODULE reserved word for separate and independent compilation

•

STATIC and AUTOMATIC allocation attributes

•

%INCLUDE directive to allow multiple compilation
units to access the same program text

M•/or ,,_seal L.llngu•ge Elements

•

Binary, hexidecimal, and octal constants

The data types, control statements, and predeclared functions and procedures provided by Pascal include:

•

Exponential operator

•

Dollar sign ($) and Underscore (-) characters in
identifiers

•

Value initialization in declaration section at program
level

•

Predefined procedures CLOSE, DATE, OPEN,
TIME, and HALT

•

INTEGER, REAL, CHAR, BOOLEAN, enumerated
and subrange data types

•

ARRAY, RECORD, SET and FILE structured data
types

•

FOR, REPEAT. WHILE repetitive control statements

•

CASE, IF-THEN, and IF-THEN-ELSE conditional
statements

•

BEGIN ... END compound statement

•

GOTO statement

•

READ, WRITE, READLN, and WRITELN input and
output procedures

•

FORWARD procedure and function directive

Compilation
The Micro/RSX PDP-11 PASCAL compiler performs
optimizations designed to improve execution speed,
including constant folding, constant conversion, constant
pooling, and global register assignment. Optional instruction to the compiler and input and output file attributes are
specified by compiler switches that:
•

Perform run-time checks of array bound, case selectors, pointers, string bounds, and subrange bounds

•

Limit the number of error messages printed and
allow compilation to continue regardless of the number of errors

•

Cause code to be generated that provides source
line numbers at run-time

Micro/RSX PDP-11 PASCAL Extensions
•

Support for Micro/RSX File Control System (FCS)
sequential files with fixed or variable length records

•

Sequential access to fixed or variable length
records, and both direct and sequential access to
fixed length records

•

User Mode Instruction and Data space support on
processors where both the hardware and software
support this feature

•

EXTERNAL procedure and function directive

•

OTHERWISE clause in case statements

•

REM operator to supply the remainder in division
operations

•

Produce an optimal, machine-code listing

•

Identify the Micro/RSX PDP-11 PASCAL compiler
version number

•

Print warning-level messages that identify the use of
Micro1RSX PDP-11 PASCAL extensions

•

Provide automatic spooling of the listing file

September 1985

soft Ware
(
207

AE-AU50C-TC

Micro/RSX PDP.11 PASCAL, Version 1.2

SPD 18.07.02

Task Building
After compilation, the RSX Task Builder is used to produce
an executable image file, and to provide support for both
relocatable and resident object libraries. Task builder
options create checkpointable tasks, identify the use of
floating point hardware, provide On-line Debugging Technique (ODT) support and allow simultaneous execution of
multiple versions of a single task.

normal conditions as defined by the SPD. DIGITAL will
remedy a nonconformance problem in the current unaltered release of the licensed software by issuing correction
information such as: correction documentation, corrected
code, or notice of availability of corrected code; or a restriction or a bypass. The customer will be responsible for the
preparation and submission of the problem report to the
service location.

·Micro/RSX En11lronment

Warranty Excluslon

Micro/RSX PDP-11 PASCAL allows use of the FORTRAN
standard calling sequence, permitting Pascal programs to
communicate with FORTRAN callable system routines for
real-time applications. However, routines written in
FORTRAN cannot be called from Micro/RSX PDP-11
PASCAL. In addition, Micro/RSX PDP-11 PASCAL programs can call Micro/RSX system services for processcontrol operations, system directives, and special peripheral access.

MINIMUM HARDWARE REQUIRED
Any valid Micro/RSX system configuration with:
•

KEF11-AA Floating Point Chip option or an FPF11
Hot Floating Point Processor Card

•

A minimum of 34K words of available memory, with
approximately 850 free blocks of disk space
required for the compiler and OTS files. Of the 850
free blocks required, 700 blocks must be
contiguous.

•

Additional disk space is required during compiler
execution. The amount of additional space required
varies with the size and complexity of the source
program.

OPTIONAL HARDWARE

None
PREREQUISITE SOFTWARE

Courtesy Installation Servi~

Micro/RSX Operating System Base Kit
Refer to the Micro/RSX Optional Software Cross Reference Table (SPD 20.95.xx) for the required version.
OPTIONAL SOFTWARE
Micro/RSX Advanced Programmers Kit (for ODT)

SOFTWARE WARRANTY
Warranty for this software product is provided by DIGITAL
with the purchase of a license for the product. There is no
additional charge. This software product is warranted to
conform to the Software Product Description (SPD). This
means that DIGITAL will remedy any nonconformance
when ii is reported to DIGITAL by the customer during the
warranty period.
The warranty period is ninety (90) days. It begins when the
software is installed or thirty (30) days after delivery to the
end user, whichever occurs first and expires ninety (90)
days later. All warranty related support for this software will
end 180 days after release of the subsequent version.
Warranty is provided in the country of purchase. DIGITAL
will provide a service location which will accept reporting
(in a format prescribed by DIGITAL) of a nonconformance
problem caused when using the licensed software under

208

Single-Use licensed software is furnished under the licensing provisions of DIGITAL's Standard Terms and Conditions of Sale, which provide in part that the software and
any part thereof may be used on only the single CPU on
which the software is first installed, and may be copied, in
whole or in part (with the proper inclusion of DIGITAL's copyright notice and any proprietary notices on the software)
for use on such CPU.
You will need a separate license for each CPU on which
you will be using the software product (except as otherwise
specified by DIGITAL). Then you will select the Materials
and Service Options you need to utilize the product effectively. IF YOU ARE ALREADY FAMILIAR WITH THESE
OPTIONS, YOU MAY OBTAIN THE ORDERING
INFORMATION DIRECTLY FROM THE SOFTWARE
OPTIONS CHART. In most cases, you wUI want to review
the following descriptions to determine what options you
require.

(

Micro/RSX PDP-11 PASCAL, Version 1.2

SPD 18.07.02

LICENSE OPTIONS

If you prefer to automatically obtain the right-to-copy, you
must purchase a Service Right-to-Copy for each additional
CPU; this is a service added to a Software Product Service
Agreement.

Slngl•U• LlcenM Option
The Single-Use License is your right to use the software
product on a single CPU and it includes your 90 day
warranty.

•

Documentation-Only Option
You can obtain one copy of the basic documentation by
purchasing the Documentation-Only Option.

For your first installation of this software product you must
purchase as a minimum:
•
•

Installation Service Option

Single-Use License Option, and
Distribution and Documentation Option

DIGITAL's Installation Service is provided by a DIGITAL
Software Specialist and accelerates your productive use of
this product. For more information on what is included in
this service, please obtain the appropriate Service
Description from your local DIGITAL office.

The license gives you the right to use the software on a sin·
gle CPU and the Distribution and Documentation Option
provides the machine-readable software and related
documentation.

Installation Service will be provided at no additional charge
(Courtesy Installation) under the conditions described in
the Installation section above.

To use this software product on additional CPUs, you must
purchase for each CPU as a minimum:
•

Single-Use License Option

Software Product Service Agree111!9nts

DIGITAL offers licensed customers annual Software Prod·
uct Service Agreements to maintain their software:
DECsupport Service is the most comprehensive level of
service offering critical problem on-site assistance and
scheduled preventative maintenance. You receive tele·
phone support that gives you timely answers and solves
most software problems. In addition, you get revised versions of the software and documentation, and system
newsletters or dispatches.

The licensee may also reproduce and distribute object
modules and/or resident libraries which are necessary to
run programs compiled with this product provided such
programs are distributed: 1) in accordance with the provisions of licensee's standard software license; or 2) with
licensee's copyright notice included on such programs; or
3) if conditions (1) or (2) are not met, with DIGITAL'S
COPYRIGHT notice included on such programs.

MATERIALS AND SERVICE OPTIONS
This product is serviced by two basic mechanisms. First,
new releases of the product may provide new features and
remedies for known software problems. Second, suggestion/problem reports will be acknowledged upon receipt by
DIGITAL. If there is a suitable workaround available for a
suggestion/problem report it will be provided, otherwise it
will be considered for inclusion or remedy in a future new
release. The optional service agreements include these
two mechanisms as well as other service offerings.

Self-Maintenance Service is designed for customers who
require revised versions of the software and documenta·
lion from DIGITAL. In addition, you get system newsletters
or dispatches and may submit software performance
questions.
A variety of service options may be added to an existing
Software Product Service Agreement, such as service for
multiple-like systems. Contact your DIGITAL representative for additional information and ordering details.

Distribution and Documentation Option
The Distribution and Documentation option provides the
machine-readable software in binary form and the basic
documentation. You must have, or order, a Single-Use
License to obtain this option. You will need this option to
install the software for the first time. When revised versions
of this software product become available, they may also
be obtained by purchasing this option again.

The Prerequisite Software, as specified by this SPD, must
have the equivalent level Software Product Service.
For more information on what is included in these agreements, please obtain the appropriate Service Description
from your local DIGITAL office.

If you prefer to receive automatic distribution of revised
versions for this product. you must purchase a Software
Product Service Agreement.

Training From Educational Services
To ensure customer success with DIGITAL products, Educational Services sells training for the installation, maintenance and/or management of DIGITAL software. Course
formats vary from seminars to packaged training materials
that include self-paced instruction and computer-based
instruction to traditional lecture/labs at DIGITAL's world·
wide Training Centers.

Software Revision Right-To-Copy Option

The Right· To-Copy Option allows a customer with multiple
CPUs to copy a revised version of a software product from
one CPU to another. Each CPU must be licensed for that
product. You first install the revised software on one CPU;
then you can make copies for additional CPUs by purchasing the Right-To-Copy Option for each additional CPU.

(
209

Micro/RSX PDP-11 PASCAL, Version 1.2

SPD 18.07.02

For a complete listing of course schedules and prices. refer
to the DIGEST. Educational Services· quarterly publication. For curriculum-specific information. training recommendations and assistance in planning training programs.
please contact your Educational Services Representative.
Professional Software Services

•
•
•

Assume project management responsibility
Develop software
Augment a system start-up service package with tailored services to meet specific needs

Contact your DIGITAL representative for additional information and ordering details.

DIGITAL Software Specialists are available on a per-call or
resident contract basis to help in all phases of software
development or implementation. Specialists are available
to serve as technical consultants. decision support consul·
tants or business systems analysts. Resources are available to:
•

•

Supplement your programming staff

SOFTWARE OPTIONS CHART
The distribution Media Codes used 1n the Software Options Chart are described below. You specify the desired Media Code
at the end of the Order Number. e.g .. OY806·H3 - binaries on a RXSO Floppy Diskette.
3 ~ RXSO Floppy Diskette
5 - TKSO Tape Cartridge
Z - No hardware dependency
NOTE: The availability of these software product options and services may vary by country. Customers should contact their local
DIGITAL office for information on availability.

OPTIONS

ORDER
NUMBER
CLASSL'

ORDER
NUMBER
CLASSH2

OY806-UZ

QP806-UZ

LICENSE OPTIONS: A LICENSE IS REQUIRED FOR EACH CPU.
Single-Use License
MATERIALS AND SERVICE OPTIONS
Distribution and Documentation Option

QY806-H3
OY806-H5

Software Revision Right· To-Copy Option

QY806-HZ

Documentation Only Option

OY806-GZ

Installation Service Option

QY806-13
QY806-15

DECsupport Service

QY806-93
QY806-95

Basic Service

QY806-83
QY806-85

Self-Maintenance Service

OY806-33
QY806-35

Class L Single-Use License:
- All O·BUS models and systems except MicroPDP·11 83
- KD11. KDF11. KDJ11 CPU modules
- DCT11. DCF11. DCJ11 microprocessor chips
Class H Single-Use Ucense:
- All UNIBUS models and systems
- MicroPDP-11 83

'·
.

l
210

Software
Product
Description
PRODUCT NAME:

DECserver 100 Terminal Server, ven1on 1.1

In a V AXduster or TOPS-20 Common File System environment, the DECserver 100 provides functions to help ~
ance processor loading and to maintain access to the
cluster in the event of a duster node flllure. Features
such as login load balancing, multiple terminal sessions,
and automatie login faJlover can leed to greater user
productivity.

DESCRIPTION
The DECserver 100 Terminal Server is a network terminal
switch for Ethernet Local Area Networks. The DECserver
100 provides a convenient method to logically connect up
to eight DIGITAL asynchronous terminals to one or more
service nodes (hosts) on an Ethernet. Once the terminal is
COlil 18Cted, the user can utilize application programs and
utilities as they would through a terminal directly connected to a host vta a DZ11, DMF32, or DH11 device.
Thus, it may be possible to utilize the DECserver 100 to
connect aH terminals to service nodes in place of traditional interfaces, except for host console terminals.

,........

Terminal Connection Management
Through the use of a simple command, users can estabHsh a logical connection, called a session, to any local
service node that implements the LAT protocol. This connection makes the terminal appear as If it were physically
connected to the service node, and the terminal user can
use standard system utilities and applicatlol 11 supported
by that node. Each terminal connected to the server can
connect to the same or a different service node on the
Ethernet. Furthermore, several servers can be used to
connect many terminals to one or more service nodes.

The DECserver 100 implements the Local Area Transport
(LAT) protocol for communication with service nodes that
implement this protocol on the same Ethernet. This new
interface has been optimized for high terminal 1/0 performance over an Ethernet, while reducing host CPU cycles
required to handle Interrupts. Hence. under most 1/0 loading conditions, s significant performance gain may be
realized by using the DECserver 100 over direct terminal
connections vta DZ11 s.

A service node can have one or more serviCeS that are
offered to DECserver 100 users. Services and nodes are
identified by name. Users always connect to services, not
to nodes, although often one of the service names wll be

Software that runs on the DECserver 100 is downline
loaded over the networ1< from a DECnet-VAX,
DECnet-11 M-PLUS, DECnet-Miao/RSX, or DECnet-20
load host. Terminal access using the DECserver 100 does
not require DECnet running in the same service node;
LAT uses the Ethernet addressing mechanism to transport termi1al messages. However, one Phase IV DECnet
load host must be running on the same Ethernet such that
DECserver 100 software can be downllne loaded.

the node name.
In a VAXduster environment, the DECserver 100 sees
each VAXduster on the Ethernet as a collection of service

nodes offenng a common service. Each duster node may
also offer a service whose name Is equivalent to its node
name. In this case, a terminal user can connect either to
the duster service or a service associated with a particular duster node.

For wide area network communications, terminal users
can connect to a local service node running DECnet,

Load Balancing

where they can "SET HOST" to a remote system via the
DECnet network terminal protocol. Note, too, that if this
system has the requisite X.29 or SNA 3270 access routines, a terminal user could convnunicate to a remote SNA
or X.25 host through the appropriate gateway and this

When a connection is made to a service, the actual node
for the connection is determined by load balancing. Load
balancing is a process the server uses when more than
one node offers the same service. Service nodes do not
have to be configured in a duster In order for load belanoing to be used. Using this process, the server connects to
the node with the highest rating for the service desired.
This rating Is based on the current loading on the nodes
that offer the service.

Intervening host. A DECserver 100 terminal user cannot
communicate directly to remote hosts through DECnet
Routers or X.25/SNA Gateways. Wide area networ1< traffic wlM not provide the same high level of performance as
local terminal connections, due to the additional DECnet
and internet protocol overhead.

SPD 30.43.02

soft Ware

(
211

December 1915
AE-DY97C-TIC

DECMl'Ver 100 Tennlnal Server, Vertlion 1.1
Multiple Sessions

The DECserver 100 allows each user to establish and
maintain up to four sessions to one or more service
nodes. Only one session can be active at a time. Through
simple switching commands, the user can access the
different sessions without repeating a login dialog each
time. Some operating systems may impose !imitations on
the number of LAT sessions such a hoSt wtH support.
Local Mode and Service Mode

For the most pan. the environment provided by the
DECserver 100 is identical to that the user would experience if attached directly to the service node. When operating in this mode, the user is said to be in Service Mode.
Occasionally, such as during connection establishment,
the user interacts directly with the DECserver 100. When
operating in this mode, the user is in Local Mode.
In Local Mode, the terminal input is interpreted directly by
DECserver 100 as commands to be performed by the
server. Local Mode has two different levels of operation:
nonprivileged and privileged. Nonprivileged commands
allow the terminal users to control their service sessions,
set terminal characteristics, and show server information.
Privileged mode is provided for the server manager to
control the environment of the server and of the terminal
users. Access to this mode is password piotected.
The Terminal Server Manager environment is a logical
extension of the user environment. The Server Manager is
treated as a server user with a privileged status. The
Server Manager sets a terminal to this status using a
command which requires a password. This privileged
status allows the Server Manager to enter commands not
nonnally available to server users. These commands set
server characteristics, provide control over server port
usage, and provide the ability to control the user's access
to the server and netwonc services.

SPD 30.43.02
If a preferred service is specified, the DECserver 100 wl
attempt to connect to that service as with the dedicated
service mode of operation. However, the terminal user
can enter local mode and establish other sessions.

Automatic Senion Fa/lover
If a service is available on two or more service nodes and
a connection to a service fails, the server wHI attempt to
connect the user to another service node offering the
same service. Autoconnectlon must be enabled for this
feature to work. The user does not have to be already
connected to that service node. Furthermore, the user's
context at the time of faHure is not automatically restored
and login to the new service is required.

A privileged user can change the group(s) in which a
terminal is a member. Group codes provide a restrictive
view of the netwonc. This restricted view is mainly for user
convenience and, although It also provides a form of
security, it Is not Intended to be the primary form of
access authoriZation or system security for a node.
Secutfty

The DECserver 100 provides functions which enhance
security features already available in the service nodes.
DECserver 100 security Includes the ability to loCk a
terminal's keyboard from other users, optional login protection, and nonprlvileged local mode of op91atiOl1 as a
default.

In Service Mode, the terminal input Is passed directly to
the connected service node with several exceptions. One
exception, called the local switch character, allows the
user to enter Local Mode from Service Mode. Other
exceptions, called the forward and backward switch characters, allow the user to switch between sessions without
the need to enter local mode. The switch characters are
disabled by default but may be enabled by command.
Both CTRL/S and CTRL/Q are normally interpi8ted locally
but flow control using these characters can be disabled.

A user may loCk the terminal using a loCk password. Thia
allows the user to leave sessions running at the terminal
without fear of security violatlons. When a terminal Is
locked, all input from the terminal is Ignored until the loCk
password is r&«ltered.

Autoconnection

DECserver 100 users normally have access to the
nonprivileged local mode. In this mode, users may only
issue commands that affect their own terminal envtronmerlt. The server has a privileged mode for server manager's use. The mode is password protected.

Autoconnection is a function that automatically connects a
user terminal to a service node when connection failures
occur or upon user login to the server. In conjunction with
this function, a dedicated or preferred service can be
specified for each terminal user.
If a dedicated service is specified, the DECserver 100 will
attempt to connect to that service when a character is
typed on the terminal keyboard or when an existing connection fails. In dedicated service mode, only one session
is available. As this mode is designed to simulate a direct
terminal connection, no local mode commands or messages are available to the terminal user.

•

Groups
Every terminal and service node In a LAT netwonc Is a
member of one or more groups. These groups are identified by numbers called group codes. Group codes allow
an easy means of subdividing the netwonc into what
appears to be many smaller netwoncs. A terminal user is
only aware of the services that are offered by nodes in the
same group(s).

Login passwords can be enabled on a per-line basis by
the privileged user. If enabled, the terminal user must
enter a login password to access server functions. If a
dedicated service is specified, login pi otection is not available.

Online HELP F11c:Ulty
A limited onllne HELP facility Is available to remind users
of command syntax. It is not intended as a replacement
for the documentation set.

212

(

DECMrWI 100 Termlnel Serwr, V....., 1.1

SPO 30.43.02

s.mc.

Dhcby

SenwMe~

Any DEC88Mll' 100 user can obtain a directory of services available to that user with a SHOW SERVICES
command. s.vlces for which the user is not authorized
wtl not be displayed.

T.,,,...,

p_,,,,,., Conllgurdan

Pararnetsa governing the operation of an Individual terminal can be modified and displayed by a nonprlvllegad
terminal user lntsactlvely from their terminal. In the prlvlleged mode, a server manager can modify panmeters for
other users' ports or for the server aa a whole.

Permanent charactertstlcs are maintained In DECserver
100 memory, even when the power is dsconnected. Permanent characteristics are maintained for server-wide
paramet8l'S u well u per-terminal parameters. Permanent charactertstlcs can be reset to factory defaults by
pressing the software reset button on the hardware unit
while plugging In the power cord. Terminal parameters
that can be set and displayed Include: speed, character
size, group codes, partty, and terminal type.

A prfvileged user can diagnose Ethernet communications
problems by looping messages to an Ethernet host and
through the Ethernet hardware interface at the server. To
diagnose terminal problems, users can execute a command to transmit test data to their terminal, or the server
manager can send test data to any terminal.

The server maintains a variety of statistics and counters.
These include the following: Ethernet data link statistics,
LAT protocol statistics, and terminal line error statistics.

These data can be displayed and zeroed by a privileged
terminal user. Server parameters that can be modified and
displayed Include the server identification, circuit timer,
and login limits.

TetrftlMI Operation

Remote Senw M•MflMWlf

The DECserver 100 software supports the simultaneous
operation of up to eight terminals at speeds from 75 bps
to 19.2K bps. The software also supports:

The DECserver 100 Implements the console carrier feature which enables access to the DECserver 100 local
mode from a Phase IV DECnet host on the same LAN. A
restricted set of local mode functions are available to a

•

Split speed (transmit and receive) terminal operation

• Block Mode transfers

console carrier user. This capebiHty provides centralized
server management and remote server diagnosis.

•

Automatic line speed detection

CommunlcatJon•

•

DIGITAL Personal Computer fHe transfer

•

XON/XOFF handling

The DECserver 100 software supports the following
DIGITAL terminal devices that have keyboards:

DECserver 100 software is designed to run on DECserver
hardware exclusively. This hardware includes an Ethernet
Interface for connection to an Ethernet transceiver cable,
and eight EIA RS-232-C/CCITT V.24 asynchronous line
interfaces for connecting terminals to the unit. This product is deslgll6d for local terminal use only. Support for
remote terminals and modern control is not provided.

T.,,,..,.,.

Several faclllties exist for managing and troubleshooting
server operation. A server manager in privileged mode
can set up server identtflcatlon Information, change terminal parameters, or fine tune the operating characteristics
of the server. Troubleshooting facilities include diagnostic
tests and onllne statistics.

Suppotted

•

LA12, 34, 35, 36, 36

DECaervw 100 Operation

•

VT52

•

VT100, 101, 102, 125, 131

•

VT220, 240, 241

The DECserver 100 ROM-based firmware provides the
necessary maintenance operation protocols for downllne
loading DECserver 100 software from a Phase IV DECnet
load host over the Ethernet into server memory. All self.
test diagnostics are in DECserver ROM, so downllne
loading is not a precondition for DECserver self-test. In
the event of a bugcheck caused by a fatal error, the unit
will normally attempt to upline dump server memory to a
DECnet Phase IV host. Following this, the unit will automatically initialize itself and invoke a downline load.

The DECserver 100 software also supports the following
DIGITAL Personal Computers (PCs) In both terminal emulation mode and file transfer mode:
•

Professional 325, 350, 380

•

Rainbow 100A, 1008, 1oo+, 190

•

DECmate II

•

DECmate 111

Nole:

Reattfctlons on DECaetVW 100 Ua•ge

This product is not warranted to support
non-DIGITAL tem1inal devices and Personal Computers. However, those supporting VT100-like
characteristics may operate with this product.

Modems Suppotted

None

(
213

While terminal connections using the DECserver 100 have
been designed to simulate direct tenninal connections as
much as possible, a few differences necessarily exist
because of the nature of the product. Under most circumstances, these differences are not noticed by tennlnal
users or service node application programs. However,
applications which are directly dependent on the following
functions may not operate as with a direct connection:

SPD 30.43.02

DECMrVer 100 Terminal Server, Veralon 1.1

•

Applications that depend on reading or setting the
terminal speed, character size and parity by manipulating system data structures

•

Applications that depend on an extremely fast
response time (typically less than 200 ms) to operate

•

Applications that utilize an alternate terminal driver in

the service node
•

Applications that directly receive and send BREAK
signals and/or the XON/XOFF ftow control characters
(since these characters are normally intercepted and
processed locally by the DECserver 100)

MINIMUM HARDWARE REQUIRED
The DECserver 100 software runs on either of the following packaged hardware options:
DSAVA-AA

DSRVA-AB

DECserver 100 hardware, including
eight EIA AS-232-C/CCITT V.24 asynchronous lines supporting speeds up to
19.2K bps, factory set at 120V.
DECserver 100 hardware, including
eight EIA RS-232-C/CCITT V.24 asynchronous lines supporting speeds up to
19.2K bps, factory set at 240V.

Use the following SHIELDED cable with each of the
physical lines on the unit:
BC22D

Null modem cable for local terminal connections

The DECserver hardware requires both a transceiver drop
cable and Ethernet connection, H4000 or DELNI, to connect to the Ethernet physical channel.
VMS service node software requires a valid MicroVAX I,
MicroVAX II, VAX-11/725, VAX-11/730, VAX-11/750,
VAX-11/780, VAX-11/782, VAX-11/785, or VAX 8600
system configuration.
An R80/RL02 configuration is required for V AX-11 /730
systems.
Because all software run on the DECserver is downline
loaded over the Ethernet from a Phase IV DECnet load
host, this node must be a valid VAX/VMS, MicroVMS,
RSX-11 M-PLUS, Micro/RSX, or TOPs-20 system.
Refer to the Software Options Chart below to determine
the distribution media avallable for a particular processor
and operating system.

Block Space Requirements (Block Cluster Size • 1):
Disk space required for installation

300 blocks
(153,600 bytes)
Disk space required for use (permanent)
300 blocks
(153,600 bytes)

The Block Space Requirements above refer to the disk
space required on the system disk. The sizes are approximations; actual sizes may vary depending on the user's
system environment, configuration, and software options.

GROWTH CONSIDERATIONS
The minimum hardware requirements for any future version of this product may be different from the minimum
hardware requirements of the current version.
OPTIONAL HARDWARE
None

PREREQUISITE SOFTWARE
DECnet-VAX (either full or end node license),
DECnet-11M-PLUS (either full or end node license), DECnet-20, or DECnet-Micro/ASX (end node license) support
on one or more DECserver load hosts (on the Ethernet) to
downllne load DECserver 100 software.

The DECserver 100 software license applies to the
DECserver 100 on which the server software runs, not to
service host node CPUs in the network.
Service Node end Downllne Load Host Operating
Sy9tema

Service Node
VAX/VMS,
Version 4.0 or later
Micro VMS,
Version 4.0 or later
RSX-11M-PLUS,
Version 3.0 or later
Micro/RSX,
Version 3.0 or later
TOPS-20,
Version 6.1 or later
ULTRIX-32,
Version 1.1 or later
ULTRIX-32m,
Version 1.1 or later

Load Host
DECnet-VAX,
Version 4.0 or later
DECnet-VAX,
Version 4.0 or later
DECnet-11 M-PLUS,
Version 3.0 or later
DECnet-Micro/RSX,
Version 3.0 or later
DECnet-20,
Version 4.0 or later

To support an ULTRIX-32 or ULTRIX-32m, Version 1.1 DECserver 100 combination, it is necessary to downllne
load the DECserver 100 from a service host that is capable of doing so.

OPTIONAL SOFTWARE
None

SOFTWARE WARRANTY
Warranty for this software product Is provided by
DIGITAL with the purchase of a license for the product.
There is no additional charge. This software product is
warranted to conform to the Software Product Description (SPD). This means that DIGITAL will remedy any nonconformance when it is reported to DIGITAL by the customer during the warranty period.

The warranty period Is ninety (90) days. It begins when
the software is installed or thirty (30) days after delivery to
the end user, whichever occurs first and expires ninety
(90) days later. All warranty related support for this software wiH end 180 days after release of the subsequent
version.

214

SPO 30.43.02

DECMt'Yer 100 Termlnlll Server, Vtnlon 1.1

Warranty is provided in the country of purchase. DIGITAL
wiM provtde a service location which will accept reporting
(In a format prescribed by DIGITAL) of a nonconformance
problem cauaed when using the licensed software under
normal co11dltlo11a as defined by the SPD. DIGITAL wiH
remedy a nonconformanoe problem in the current unaltered releue of the licensed software by issuing correction Information such as: correction documentation, corrected coda, or notice of avallabillty of corrected coda; or
a restriction or a bypass. The customer will be responsible
for the preparation and submission of the problem report
to the service location.

W•rninty Exclualon
DIGITAL DOES NOT WARRANT THAT THE SOFTWARE
LICENSED TO CUSTOMER SHALL BE ERROR FREE,
THAT THE SOFTWARE SHALL OPERATE WITH ANY
HARDWARE AND SOFTWARE OTHER THAN AS SPECIFIED IN THIS SPD, THAT THE SOFTWARE SHALL SATISFY CUSTOMER'S OWN SPECIFIC REQUIREMENTS,
OR THAT COPIES OF THE SOFTWARE OTHER THAN
THOSE PROVIDED OR AUTHORIZED BY DIGITAL
SHALL CONFORM TO THE SPD.
DIGITAL MAKES NO WARRANTIES WITH RESPECT TO
THE FITNESS AND OPERABILITY OF MODIFICATIONS
NOT MADE BY DIGITAL.
IF THE SOFTWARE FAILS TO FUNCTION FOR REASONS STATED ABOVE. THE CUSTOMER'S WARRANTY WILL BE INVALIDATED AND ALL SERVICE
CALLS WILL BE BILLABLE AT THE PREVAILING PER
CALL RATES.

ORDERING INFORMATION
Single-Use licensed software is furnished under the licensing provisions of DIGITAL's Standard Terms and Conditions of Sale, which provide in part that the software and
any part thereof may be used on only the single CPU on
which the software is first installed, and may be copied, in
whole or in part (with the proper inclusion of DIGITAL's
copyright notice and any proprietary notices on the software) for use on such CPU.
You will need a separate license for each Server CPU on
which you will be using the software product (except as
otherwise specified by DIGITAL). Then you will select the
Materials and Service Options you need to utilize the
product effectively. IF YOU ARE ALREADY FAMILIAR
WITH THESE OPTIONS, YOU MAY OBTAIN THE ORDERING INFORMATION DIRECTLY FROM THE SOFTWARE
OPTIONS CHART. In most cases, you will want to review
the following descriptions to determine what options you
require.
LICENSE OPTIONS
Slngle-UH llcenH Option

The Single-Use License is your right to use the software
product on a single Server and it includes your 90 day

warranty.
For your first installation of this software product you
must purchase as a minimum:
•

Single-Use License Option, and

This software product can be installed by the customer
using the s~-step documentation available for this
product. Optionally you can purchase DIGITAL Installation
Services which provtde for the installation of the software
product by an experienced DIGITAl Software Specialist.

•

Distribution and Documentation Option

Customer Rnponalbllltlff

To use this software product on additional Servers, you
must purchase for each CPU as a minimum:

INSTALLATION

Before installation of the software, the customer must:

•

Both the operating system and this product must be
installed concurrently.

Previously have installed all requisite hardware including terminals.

•

Obtain, instaM, and demonstrate as operational other
communications equipment and facilities necessary to
interface to DIGITAL's communication equipment.

•

Make available for a reasonable period of time, as
mutually agreed by DIGITAL and the customer, all
hardware, communication facilities, and terminals that
are to be used during the installation.

•

For multlnode networks, designate one Ethernet host
to verify installation/connectivity.

DIGITAL's Installation Services can be purchased as a
separate service.
Courtesy lnatalllltlon Service

This software product wiH be installed by DIGITAl at no
additional charge if you purchase it concurrent with a
Startup Service Package that includes installation service.

The license gives you the right to use the software on a
single Server and the Distribution and Documentation
Option provides the machine-readable software and
related documentation.

•

Single-Use License Option

In addition to the right to use, the license gives you the
one-time right to copy the software from your original
CPU installation to the additional CPU. Therefore, the
Distribution and Documentation Option is not required,
but optional.

VAXcluater llcenH Option
You are eligible for a VAXduster license option on your
second or each subsequent CPU that is part of a
VAXciuster system. This is a Single-Use License offered
at a reduced price and provides all of the License rights
described above. A standard, Single-Use License Option
(QDxxx-UZ, QExxx-UZ, or QKxxx-UZ) is required with the
first purchase of this software product and is also
required for the first CPU of a V AXduster system.
For software configuration purposes, a VAXciuster system is a set of VAX processors, each running the VMS
operating system, where each AX processor has a direct

(
215

DECMrver 100 Termlnlll Semlr, Venllon 1.1
path to evwy other VAX processor via Computer Interconnect (Cl) Bus.

MATERIALS AM> SERVICE OPTIONS

scheduled preventative maintenanee. You receive telephone support that gives you timely answers and solves
most software problems. In addition, you get revised
versions of the software and documentation, and system
newsletters or dispatches.

Distribution encl Documentation Option

The Distribution and Documentation option provides the
machlne-readabl software in binary form and the basic
documentation. You must have, or order, a Single-Use
License to obtain this option. You will need this option to
instaH the software for the first time. When revised versions of this software product become available, they may
also be obtained by purchasing this option again.

If you prefer to receive automatic distribution of revised
versions for this product, you must purchase a Software
Product Service Agreement.

Software Revision Right-To-Copy Option
The Right-To-Copy Option allows a customer with multiple CPUs to copy a revised version of a software product
from one CPU to another. Each CPU must be licensed for
that product. You first Install the revised software on one
CPU; then you can make copies for additional CPUs by
purchasing the Right-To-Copy Option for each additional
CPU.

If you prefer to automatically obtain the right-to-copy, you
must purchase a Service Right-to-Copy for each additional CPU; this Is a servloa added to a Software Product
Service Agreement.
Documentation-Only Option
You can obtain one copy of the basic documentation by
purchasing the Documentation-Only Option.

Installation Service Option
DIGITAL's Installation Service is provided by a DIGITAL
Software Specialist and accelerates your productive use
of this product. For more information on what Is included
in this servloa, please obtain the appropriate Service
Description from your local DIGITAL office.
Installation Service wiH be provided at

SPD 30.43.02

no additional

charge (Courtesy Installation) under the conditions
described in the Installation section above. The installation
service consists of:
•

Installation of DECserver 100 software on up to two
DECnet load hosts

•

Configuration of up to ten DECserver 100 unites on
each load host

•

Configuration of LAT service node software (i.e.
LTDRIVER) on up to two service nodes

•

Installation verification and checkout

•

Customer Orientation Demo

Sottw.re Product Service Agreements
DIGITAL offers licensed customers annual Software Product Service Agreements to maintain their software:

BASIC Service is ideal for customers who have a staff
whose experience and expt!l'tise enables them to analyze
and communicate a software problem to DIGITAL remote
support centers. You receive telephone support that gives
you timely answers and solves most software problems.
In addition, you get revised versions of the software and
documentation, and system newsletters or dispatches.

Seit-Maintenance Servlc:e is designed for customers
who require revised versions of the software and documentation from DIGITAL. In addition, you get system
newsletters or dispatches and may submit software performance questions.
A variety of servloa options may be added to an existing
Software Product Service Agreement, such as servica for
multiple-like systems. Contact your DIGITAL repr&sentative for additional information and ordering details.

The Prerequisite Software, as specified by this SPD, must
have the equivalent level Software Product Service.
For more information on what is included In these agree-

ments, please obtain the appropriate Service Description
from your local DIGITAL office.

Training From Edue11tionlll Servlc:u
To ensure customer success with DIGITAL products, Educational Services seHs training for the installation, maint&nance and/or management of DIGITAL software. Course
formats vary from seminars to packaged training materials
that Include self-paced instruction and computer-based
instruction to traditional lecture/labs at DIGITAL' s worldwide Training Centers.
For a complete listing of course schedules and prices,
refer to the DIGEST, Educational Services' quarterly publication. For curriculum-specific information, training recommendations and assistance in planning training programs,
please contact your Educational Services Representative.

Profeuional Software Servlc:u
DIGITAL Software Specialists are available on a per-call
or resident contract basis to help in all phases of software
development or implementation. Specialists are available
to serve as technical consultants, decision support consultants or business systems analysts. Resources are
available to:
•
•
•
•

Supplement your programming staff
Assume project management responsibility
Develop software
Augment a system start-up service package with tailored services to meet specific needs

Contact your DIGITAL representative for additional information and ordering details.

DEC9upport Service is the most comprehensive level of
service offering crttlcal problem on-site assistance and

216

(

DEC..,,. 100 TenNMI Server, Venton 1.1

SOFTWARE OPTIONS CHARTS
The dl8trtbutlOn Media Codes used In the Softwsa Options Chart ant dellcrtbed below. You specify the delllred Media Code
at the end of the Order Number, e.g., QC925-HG • binaries on TU58 DECtape II canrtdge.
3 • RXSO Floppy Diskette
5 • TK50 Tape Cartrtdge
G • TU58 DECtape II Certrldge •
H • RL02 Disk Certrldge

M • 9-track 1800 BPI Magtape (PE)
Y • RX01 Floppy Diskette
Z • No hardwar9 depelldelicy

• The TU58 Is to be used in a stand-elone, lightly lollded environment. If used as a fie device In a heavily lollded environment, it can degrade system performance.
Ch8rt I

..me.. may vary by country. CuatlDlnel'8 lhauld con-

NOTE: The aVllllllbllty of theM eoftwar9 product opllona and
tllet their local DIGITAL otllce for Information on avallablllty.

OPTIONS

ORDER

NUMBER

NUMBER
VAX MOO

ORDER
NUMBER
VAlM 1/725
VAX-11/730

ORDER
NUlmER
VAll-11/750 VAX-11/780
VAX-11/7129
VAX-11/711

QC925-UZ

Q0925-UZ

QE925-UZ

QK925-UZ

QD925-QZ

QE925-QZ

QK925-QZ

LICENSE OPTIONS: A LICENSE IS REQUIRED FOR
EACH CPU.
Single-Use License
VAXcluster License
MATERIALS AND SERVICE OPTIONS:

Distribution and Documentation Option

QC925-HG
QC925-HM

QD925-HG
QD925-HM

QE925-HM
QE925-HY

QK925-HM

Software Revision Right-To-Copy Option

QC925-HZ

Q0925-HZ

QE925-HZ

QK925-HZ

Documentation Only Option

QL925-GZ

Installation Service Option

QC925-IG
QC925-IM

QD925-IG
QD925-HM

QE925-IM
QE925-IY

QK925-IM

DECsupport Service

QC925-9G
QC925-9M

QD925-9G
QD925-9M

QE925-9M
QE925-9Y

QK925-9M

Basic Service

QC925-8G
QC925-IJM

QD925-8G
QD925-IJM

QE925-IJM
QE925-8Y

QK925-IJM

Self-Maintenance Service

QC925-3G
QC925-3M

QD925-3G
QD925-3M

QE925-3M
QE925-3Y

QK925-3M

• For software licensing purposes, a VAX-11/782 ls a multiprocessor that is considered a single CPU.

(,
217

DECMrVW 100 Termlnlll ..,,_, V.,...., 1.1

NOTE:

SPD 30.43.02

n. • · 1111ty ol tlleee eoftwlll9 product oplorl8 Md wvtcea mer Yllry by country. CUtlan'len 8hould conmct lllelr loc:.I DIGITAL otllce for lnfonndon on 8Ylllleblllty.

OPTION8

ORDER
NUMBER

ORDER
NUMBER
MlcroRSX

ORDER
NUMBER
RSX·11M·
PLUS

MicroVAX
I

MicroVAX
II

QN92~Z

QZ92~Z

QYAAC-UZ

QR92~Z

Distribution and Docunentatlon Option

QN925-H3

QZ925-H3
QZ925-H5

QYAAC-H3
QYAAC-H5

QR925-HH
QR925-HM

Software Revision Right-To-Copy Option

QN925-HZ

QZ925-HZ

QYAAC-HZ

QR925-HZ

Docunentatlon Only Option

QL727-GZ

QYAAC-GZ

QR925-GZ

lnstalatlon Service Option

QN925-13

QZ925-13
QZ925-15

QYAAC-13
QYAAC-15

QR925-IH
QR925-IM

DECsupport Service

QN925-93

QZ925-93
QZ925-95

QYAAC-93
QYAAC-95

QR925-9H
QR925-9M

Basic Service

QN925-a3

QZ925-a3
QZ925-85

QYAAC-83
QYAAC-85

QR925-8H
QR925-8M

Self·MUltenllnce Service

QN925-33

QZ925-33
QZ925-35

QYAAC-33
QYAAC-35

QR925-3H
QR925-3M

LICENSE OPTIONS: A LICENSE IS REQUIRED FOR
EACH CPU.
Single-Use Llcen8e
MATERIALS AND SERVICE OPTIONS:

l
218

SOFTWARE PERFORMANCE REPORT (SPR) SUBMISSIONS
Digital Equipment Corporation guarantees a response to every SPR submitted by DI Gil AL
specialists and customers who purchase software product service agreements.
Blank SPR forms are available upon request in desired quantities from SPR Administration.
P.O. Box F. Maynard, MA 01754, or your local DIGITAL office.
Inquiries on the progress of submitted SPRs should be directed to your local DIGITAL office
or SPR Administration at (617) 493-4722.
An SPR Answer Survey Card is enclosed with each SPR response. Please complete the survey
card; it provides essential feedback for monitoring the quality of our SPR responses.

Completing an SPR Form

Complete the entire form by either typing or printing clearly. Remove "Customer File Copy"
for your records. Leave carbon in tact.
Include customer name and complete mailing address.
To expedite the processing of your SPR, enter your Customer Number in the space provided.
This number is located in the upper left-hand corner of your Dispatch label. It can also be
obtained from your local DIGITAL office or by calling SPR Administration at (617) 493-6683.
If you do not want your SPR to be published, check the "DO NOT PUBLISH" box on the SPR
form. However, if the SPR is determined to be of universal value and it does not describe a
security problem, DIGITAL may elect to publish it. For SPRs which describe security problems, it is imperative that the "DO NOT PUBLISH" box be marked.
Describe one problem per SPR form. If an SPR is submitted with more than one problem. it can
lengthen the turnaround time.
State the problem clearly. If necessary. summarize the problem. then describe in detail.
Include all the information needed to reproduce the problem. The easiest problems to fix are
those reported in statements similar to the following: if you do X. Y happens when Z should.

State all version numbers and all inserted patches. The problem can be fixed sooner if the
version is known. Please include the operating system version even on operating system
SPRs. since operating system bugs sometimes manifest themselves as "bugs" in other programs. A statement of patches inserted in the relevant software is also helpful. State the type of
terminal or work station on which the software is running, e.g., VT100. VT220. PRO 350.
DECmate.
Include as much information as possible; too much information is better than not enough.
Send all information in machine-readable format if it occupies more than half a page. Please
include the following:

(

Program causing the problems

All necessary auxiliary files. such as DBMS or LIBRARY files

Assembly switches which are on (if applicable)

Switches handed to the software, since different switches cause different sections of the
code to be executed

All necessary run-time files for language run-time problems

A directory listing of media, when included: label media carefully

219

SUGGESTIONS FOR SUBMITTING TAPES WITH SPRs

To insure timely processing of SPRs submitted with tapes, please follow the suggestions
below:
1.

Use either a floppy or a magnetic tape.

If a magnetic tape is used, it should be either 800, 1600. or 6250 bpi.

Include a directory with each tape submitted.

Label each tape with the following information:
a.
b.
c.
d.
e.

Customer name
Tape format
bpi
Track
Preprinted number of the SPA submitted with the tape

Remove from the tape any unnecessary or confidential files.

Thank you.

l
220

SOFTWARE PROBLEMS OR ENHANCEMENTS
Questions and problems regarding, and enhancements to, DIGITAL software should be reported on a
Software Performance Report (SPA) form and mailed to the SPA Center at one of the following DIGITAL
offices (SPA forms are available from the SPA Center):

AREAS COVERED

SPR CENTER

United States

Corporate Administrative Services Group
P.O. Box F
Maynard, MA 01754

Canada

Digital Equipment of Canada, Ltd.
P.O. Box 13000
Kanata, Ontario
Canada, K2K 2A6

Mexico

Digital Equipment de Mexico
S.A. de C.V.
Apartado Postal 12-1009
Mexico 12, O.F.
Mexico

Puerto Rico

Digital Equipment Latin America
P.O. Box 11038
Fernandez Juncos Station
Santurce 00910
Puerto Rico

Australia, New Zealand

Digital Equipment Aust Pty Ltd
754 Pacific Hwy
1st floor
M/SSNH/8-1
Chatswood, New South Wales 2067
Australia

Brazil

Digital Equipment Comercio e
lndustria Ltda.
Avenida Augusto Severo, 156-A
20021 Rio de Janeiro, RJ
Brazil

China

Digital Equipment Hong Kong Ltd.
5-7th Floor Intercontinental Plaza
94 Granville Road
Tsimshatsui East
Kowloon
Hong Kong

Remainder of General International
District (GID)

Digital Equipment Corp.
General International District - SWS
100 Nagog Park
Acton, MA 01720-3499
United States

United Kingdom, Bahrein, Egypt,
Iraq, Jordan, Kuwait, Lebanon, Libya,
Qatar, Oman, Saudi Arabia, Syria,
United Arab Emirates, Yemen Arab
Republic

Digital Equipment Co. Ltd.
Jays Close
Basingstoke, Hampshire RG22 4DE
England

France

Digital Equipment France
Zone lndustrielle Bois de L'Epine
11 Avenue Joliot Curie BP 202
91007 Evry Cedex
France

)

(

221

AREAS COVERED

SPA CENTER

Italy

Digital Equipment S.p.A.
Viale Fulvio Testi, 11
Ang. Via Gorki 105
1-20092 Cinisello Balsamo
Milan
Italy

Japan

Nihon Digital Equipment Corp.
Sunshine 60, P.O. Box 1135
1-1 Higashi lkebukuro 3-Chome,
Toshima-Ku, Tokyo, 170
Japan

Belgium, Luxemburg

Digital Equipment N.V./S.A.
Rue De L'Aeronef 1
B-1140 Brussels
Belgium

Holland

Digital Equipment B.V.
Kaap Hoorndreef 38
NL-3563 AV Utrecht
Holland

Sweden

Digital Equipment AB
SPA Admin. M-B Duff/CSC
Allen 6
S-172 89 Sundbyberg
Sweden

Denmark

Digital Equipment Corp. A/S
Sandtoften 9
DK-2820 Gentofte
Denmark

Finland

Digital Equipment Corp. OY
Box 16
02201 ESPOO
Finland

Norway

Digital Equipment Corp. A/S
Ammerudveien 22
N-0958 Oslo 9
Norway

Austria, East Germany, West Germany,
Poland, Hungary, Rumania,
Czechoslovakia, Russia, Bulgaria

Digital Equipment Corp. GmbH
SPA Centre - D2
Freischuetzstrasse 91
8000 Muenchen 81
West Germany

Israel

Digital Equipment Ltd.
Digital House
Acadia Junction
Herzlia 46 733
Israel

Greece, Portugal, Spain, Switzerland,
Yugoslavia, (Morocco, Algeria.
Tunisia, Cyprus, Turkey, Malta)

Digital Equipment Corp. AG
Kanalstrasse 21
CH-8152 Glattbrugg (Zurich)
Switzerland

222

•

(

.,.

DIGITAL SOFTWARE LICENSING

mamaama
DATA SHEET

This data sheet explains what software licenses
are and why customers must obtain a software
license to run any item of DIGITAL proprietary
software.

Modification to the Software Product

Any modification to licensed software does not
exempt the product from DIGITAL license terms.
Every line of code from a software product falls
under the terms of the license. Only those modifications that are not part of the original software are
the customer's property. It is important to note that
warranty on the product is limited to the original
software supplied by DIGITAL.

DIGITAL does not sell software; DIGITAL
offers software under a license agreement. DIG ITAL
has a license agreement for source software and
object software. Since DIGITAL software programs
are made available primarily In object code, this
data sheet focuses on the purchase of object
programs.

Transferability of Licensed Software Products

License Transfer - A license agreement does not
automatically allow transfer of licensed software
to another party or another CPU. If the customer
intends to sell the licensed CPU and pass on the
software with the sale or move the software onto
another CPU, permission must be obtained from
DIGITAL. A case-by-case License Transfer is
required to relicense the software.

Introduction to Software Licensing

When DIGITAL hardware is purchased, all rights
of ownership (legally called "title") to the hardware
pass to the customer. This is not the case with
software. DIGITAL regards software as proprietary information. Since software is easily reproduced, it must be legally protected from improper
copying. Therefore, DIGITAL uses a combination
of trade secret and copyright legal protection for
software. DIGITAL protects its investment by
retaining title to its software at all times and
requires anyone wishing to use it to obtain a
license.

Software Subllcenslng- DIGITAL customers with
a purchase agreement authorizing sublicensing,
such as OEMs, may transfer licensed object products to their customers without a License Transfer.
A valid sublicense, executed by an OEM with its
customer, gives the DEM's customer the same
license rights and responsibilities as a license
agreement made directly with DIGITAL.

How DIGITAL Licenses Software

The license agreement for object programs is contained in DIGITAL's standard Terms and Conditions of Sale and Corporate Volume Purchase
Agreements instead of as a separate agreement.
Therefore, when software products are purchased
under DIGITAL's Terms of Sale, the software
license agreement is made at the same time.

Source Software
Sources are only available for selected products. A
license agreement for source software must be
separately executed for each facility/location which
intends to purchase sources in machinereadable, listing, or microfiche form. Further
information and availability of sources can be
found in the applicable Software Product Description (SPD).

Key Principles of the License Agreement

Object code is licensed for single use. This means
obtaining a license for a product allows the associated software to be used on the "single" CPU on
which it was first installed. Other key points are as
follows:

Software Warranty

Each licensed software product offered has an
SPD describing the warranty commitment for the
product. Software products under DIGITAL warranty must conform to the description provided for
a 90-day period, which generally begins upon
product installation or 30 days after delivery. All
other products are provided AS IS, without warranty. The SPD clearly states under which warranty category the product falls.

• If the licensed CPU temporarily malfunctions,
the software may be run on another machine
while the CPU is down.
• Copies of the software may be made for backup
purposes if appropriate proprietary and copyright notices are included.
• The software may be modified or merged with
other software if appropriate proprietary and
copyright notices are included.
• The software may be used by the customer's
employees and its agents directly concerned
with the internal use, but may not be made
available to anyone else.

223

Purchasing the License for the Software Product
A license must be obtained for each CPU on which
the licensed software will be used (unless otherwise specified by DIGITAL).

A Single-use License for object code is generally
ordered according to the type/classifcation of the
CPU or system configuration intended to run the
product. Further information and availability can
be found in the applicable SPD
Software Product

A license is a prerequisite to purchase the associated software. The Media and Documentation
Option for a product is ordered according to media
type. Further information and availability of media
can be found in the applicable SPD.
Purchasing Software Product Revisions/Updated
Versions

If a licensed customer is not covered by a product
service agreement, updated versions can be purchased when they are made generally available.
Updated versions are ordered according to media
type. A customer can also choose to run updated
versions on additional CPUs, but not purchase
multiple media distributions. If this is the case, the
Software Revision Right-to-Copy option must be
purchased for each CPU which runs the updated
version.
Software Product Services

A licensed customer can purchase annual product
service agreements to receive updated versions on
media when available. A customer may choose to
copy updated versions onto additional CPUs during this service agreement period. In this case, the
software Service Right-to-Copy must be purchaseq
for each CPU which runs the updated version.
Further information and availability can be found
in the applicable SPD. Your local DIGITAL office
can be contacted for additional assistance.

224

(

DIGITAL EQUIPMENT COMPUTER USERS SOCIETY
BENEFITS OF BELONGING

The Digital Equipment Computer Users Society
(DECUS) is one of the largest and most respected
users groups in the computer industry today. Membership in DEC US, which is free and voluntary, provides the individual user with information and services not found anywhere else .
DECUS provides an environment where users of
Digital Equipment Corporation products can share
information with other users and with DIGITAL.
Members can find out the latest news on DIGITAL's
hardware, software, and educational products. The
feedback exchange with DIGITAL allows the users
of DIGITAL's products to have a voice in the company's future.
Founded in 1961, DECUS now has three autonomous areas worldwide- DEC US U.S., DEC US Europe,
made up of eight independent chapters, and DECUS
GIA (General International Area), made up of four
independent chapters. DECUS services and activities are shared between these chapters through
mutual agreements.
All DECUS services promote the exchange of information in a noncommercial environment. Included
in these services are:

Special Interest Groups (SIGs)

These groups, formed around an area of common
interest, exist for a variety of hardware, operating
systems, languages, applications, and marketing
areas. Participation in these groups allows fellow
users to exchange information and share technical
expertise in the areas of most interest to the users.

Local Users Groups (LUGs) and
National Users Groups (NUGs)

(

LUGs and NUGs are licensed groups of individuals
who gather to share information with other users on
a periodic basis. Not only do they have common
professional interest, but they also have geographic
and cultural ties. DIGITAL representatives attending these meetings often unveil new products and
services and supply updates on existing policies
and procedures.

225

Symposia
DECUS holds symposia each year in the different
chapters, two per year in the U.S. These meetings
provide a unique opportunity for users with a wide
spectrum of experience to meet for up to five days of
intensive technical exchange. Symposium activities
include workshops, clinics, panels, tutorials, and formal paper presentations. DIG IT AL participates in symposia by sending Product Group
managers and developers to discuss strategies,
products, problems, and solutions.

Publications
The flow of information among users, as well as
between users and DIGITAL, is the primary goal of
DECUS. Various publications generated by DECUS
support this communication. They include chapter
newsletters and The Proceedings, a technical volume
published after each symposium. DECUS also pub1 is hes Special Interest Groups' newsletters that provide information pertaining to specific DIGITAL
products.
Program Library
The DEC US Program Library is the main vehicle for
the exchange of software among users of all
DIGITAL systems. The Library contains over 1000
software programs written and voluntarily submitted by users. These programs include compilers,
editors, utilities, numerical and statistical functions,
as well as games and graphic routines. The Library
publishes an annual software catalog that lists and
describes all the DECUS programs available to all
users for a minimal charge.
You are cordially invited to join over 60,000 other
users of DIGITAL products around the world and
begin to share your experiences, both successes
and problems.
For more information, contact the appropriate
DECUS chapter office listed here.

DECUS CHAPTER OFFICES - WORLDWIDE
DECUS U.S.
DECUS, U.S. Chapter
219 Boston Post Road (BP02)
Marlborough, Massachusetts 01752
U.S. Activities: (617) 480-3259 (3302)
Library: (617) 480-3521
Finance and Administration: (617) 480-3634

•

·•

DECUS Europe
DECUS At Large (in Europe)
C.P. 510
CH-1213 PETIT-LANCY 1/GE
Switzerland
DECUS Denmark
Digital Equipment Corp. A/S
Sandtoften 9
DK-2820 Gentofte
Denmark
DECUS France
BP. 136
F-91004 EVRY CEDEX

DECUS Italia
Viale Fulvio Testi 11
1-20092 CINISELLO BALSAMO
DECUS Norway
Digital Equipment Corp. A/S
Ammerudveien 22
N-0958 Oslo 9
Norway
DECUS Sweden
S-172 89 SUNDBYBERG
Sweden

DECUS Holland
Kaap Hoorndreef 38
NL-3563 AV UTRECHT
The Netherlands

DECUS U.K., Ireland and
Middle East
P.O. Box 53
READING, RG2 OTW
U.K.

DECUS Muenchen
Freischuetzstrasse 91
D-8000 MUENCHEN 81
Federal Republic of Germany

DECUS Switzerland
Schaffhauserstrasse 144
8302 Kloten
Switzerland

DECUS GIA (General International Area)
DECUS Australia
Northern Tower, Chatswood Plaza
Railway Street
Chatswood, New South Wales 2067
Australia
Phone: (02) 412.5237
DECUS Canada
100 Herzberg Road
P.O. Box 13000
Kanata, Ontario K2K 2A6
Canada
Phone: (613) 592-5111, ext. 2115

DECUS Japan
Nihon Digital Equipment KK
Sunshine 60, P.O. Box 1135
1-1, Higashi lkeburo 3-Chome
Toshima-ku, Tokyo 170
Japan
Phone: [81 ]-(3)-9897111
DECUS GIC
100 Nagog Park AK01-1/B11
Acton, Massachusetts 01720
U.S.A.
Phone: (617) 264-6561

[Q]
DEC US

226

November 1985

c
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _, l l l l m l i l l l l - · · -

(,;

digital equipment corporation

Printed in U.S.A.

I
)