Digital PDFs

AD-FDO6A-12

September 1986

121 pages

Original

3.6MB

Document:	The Software Dispatch RSX RSX-11M/S RSX-11M-PLUS Micro/RSX September 1986
Order Number:	AD-FDO6A-12
Revision:	0
Pages:	121
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/Software_Dispatch/RSX_Software_Dispatch_198609.pdf

OCR Text

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

(

The Software Dispatch
RSX
RSX-11M/S
RSX-11 M-PLUS
Micro/RSX
September 1986
AD-FD06A-12

(

~omooma

ware

RSX SOFTWARE DISPATCH
Published by
Technical Support Group Operations
Digital 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 (SPA) 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-11 M/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.
The following are trademarks of Digital Equipment Corporation
DEC
DEC US

~111DECnet
DECsystem-10
DECSYSTEM-20
DECwriter

DIBOL
EDUsystem
IAS
MASS BUS
PDP
PDT
RSTS

RSX
RT
ULTRIX
UNIBUS
VAX
VMS
VT

RSX Software Dispatch, September 1986

TABLE OF CONTENTS

Sequence No.
i

PRODUCT AVAILABILITY DATES

RSX-UM V4 0 2

(

COMMAND FILES
SGNPER ABORTS WHEN CREATING DATABASE FOR VTll

1.1.1.9 M

INTERNAL COMDS
SET/NOMAIN FOLLOWED BY PAR CAUSES GARBAGE OUTPUT TO TI:

2.2.1.3 M

SET /NOECHO DOES NOT WORK

2.2.s.s M

FDX-TTDRV
POWERFAIL TO OUTPUTTING DHV LEAVES LINE HUNG

3.1.3.6 M

BELLO
DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES

40 20 40 1 M

BRU
STAND-ALONE BRU /IMAGE:SAVE INCORRECTLY INITIALIZES DISKS
BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE
BRU PROBLEM WITH LARGE FID NUMBERS
BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UFOs

s.1.11.14 M
s.1.11.1s M
s.1.11.16 M
s.1.11.11 M

13
14
15
16

50 30 10 4 M

6 0 1 0 0 0 12 M

VMR

TICB

ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION
DCL

SET DEFAULT WITHOUT PARAMETERS DOES NOT WORK CORRECTLY

BASIC-PLUS-2 V2 0 3
BASIC-PLUS-2 V2 0 3 RSX UPDATE B NOTICE

RSX-llM V4 0 2 CUMULATIVE INDEX

23
RSX-US V4.2

(

COMMAND FILES
SGNPER ABORTS WHEN CREATING DATABASE FOR VTll

RSX-llS V4o2 CUMULATIVE INDEX

RSX Software Dispatch, September 1986

TABLE OP CONTENTS (Continued)
Sequence No.
RSX-llM-PLUS V3o0

COMMAND PILES
APPLICATION NOT PROPERLY INSTALLED

lololo5 M

DISTRIB KITS
CANNOT COPY SECOND BACKUP SET USING CERTAIN MS TAPE DRIVES

1.1 0 2 0 2 N

DIRECTIVES
SYSTEM CORRUPTION IN DEFAULT UIC
RPOI RETURNS IE.IOU FROM A VT:

2ololo9 N
2ololol0 M

SHP
SHUFFLER MAY CAUSE SYSTEM CRASH

2.l.2ol M

INS
INSTALL, RUN, REMOVE WINDOW ALLOWS OTHER TASKS TO ACTIVATE IT

2o2o2o3 M

SET /NOECHO DOES NOT WORK

2 0 2.5.2 M

DUDRV
SYSTEM CRASH AFTER SHADOWING

3.1.1.6 M

PDX-TTDRV
POWERFAIL TO OUTPUTTING DHV LEAVES LINE HUNG

3olo3o7 M

PCS
PCS DOES NOT PARSE ANSI FILE SPECIFICATION CORRECTLY

3o2olo2 M

BYE
BYE PROM BATCH JOB OR SILENT CLI DOES NOT ABORT INDIRECT

4.2.3.2 M

HELLO
DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES

4.2.4.3 M

PIP
PIPRES/APPEND TERMINATES WITH ODD ADDRESS

5.1.12.3 M

BRU
STANO-ALONE BRU /IMAGE:SAVE INCORRECTLY INITIALIZES DISKS
BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE
BRU PROBLEM WITH LARGE FID NUMBERS
BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UPDs

5.1.17.14 M
5.1.17.15 M
5.1.17.16 M
5.1.17.17 M

61
62
63
64

5.3.1.5 M

VMR

TICB

ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION
RSX-llM-PLUS V3o0 CUMULATIVE INDEX

•

RSX Software Dispatch, September 1986

TABLE OF CONTENTS (continued)

Sequence No.
Micro/RSX V3.0
DIRECTIVES
SYSTEM CORRUPTION IN DEFAULT UIC
RPOI RETURNS IE.IOU FROM A VT:

2.1.1.1 N
2.1.1.8 M

SHF
SHUFFLER MAY CAUSE SYSTEM CRASH

2.1.2.1 M

INS
INSTALL, RUN, REMOVE WINDOW ALLOWS OTHER TASKS TO ACTIVATE IT

2.2.2.3 M

FCS DOES NOT PARSE ANSI FILE SPECIFICATION CORRECTLY

3.2.1.2 M

BYE
BYE FROM BATCH JOB OR SILENT CLI DOES NOT ABORT INDIRECT

4 0 2.3 0 2 M

HELLO
DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES

40 20 4 0 1 M

PIP
PIPRES/APPEND TERMINATES WITH ODD ADDRESS

5.1.12.2 M

BRU
BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE
BRU PROBLEM WITH LARGE FID NUMBERS
BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UFDs

5.1.11.13 M
5.1.11.14 M
5.1.17.15 M

91
92
93

TKB
ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION

5.3.1.2 M

res

(

Micro/RSX V3.0 CUMULATIVE INDEX

SOFTWARE PERFORMANCE REPORT (SPR) SUBMISSIONS

103

SUGGESTIONS FOR SUBMITTING TAPES WITH SPRs

104

SOFTWARE PROBLEMS OR ENHANCEMENTS

105

DIGITAL SOFTWARE LICENSING

107

DIGITAL EQUIPMENT COMPUTER USERS SOCIETY (DECUS)

109

PRODUCT AVAILABILITY DATES - RSX

(

SEPTEMBER 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

(

VERSION

BASIC-PLUS-2 for RSX-llM
and RSX-llM-PLUS,PDP-11
COBOL,PDP-11
COBOL-81/RSX
DATATRIEVE-11
DBMS-11
DECdx/RSX
OECmail-11 for RSX-llM-PLUS
and Micro/RSX
DECnet Router Server
DECnet-llM
DECnet-llM-PLUS
DECnet-llS
DECnet/SNA Gateway Products
DPM
DPM-PLUS SOFTWARE
FORTRAN IV/RSX
PDP-11 SYMBOLIC DEBUGGER/RSX
(formerly FORTRAN-77
DEBUG/RSX, PDP-11)
FORTRAN-77/RSX,PDP-11
LSP-11
MicroPower/Pascal-RSX
PASCAL/RSX,PDP-11
RGl./11
RPG II , PDP-11
RSX MDE/T-11
RSX-11 2780/3780 Emulator
RSX-11 PSI/M
RSX-11 PSI/M-PLUS
RSX-11/3271 Protocol
Emulator
RSX-11M
RSX-llM V4.2 UPDATE
RSX-llM/FORTRAN Enhancement
Pkg. for MINC
RSX-llM/FORTRAN Real-Time
Pkg. for MINC

AVAILABLE

2.3
4.4
2.4
3.1
2.1
1.0
2.0

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

1.1 SPD ONLY
4.2
3.0
4.2
1.3
4.1
1.1
2.6
2.0

OCT 85
FEB 86
FEB 86
FEB 86
JAN 86
AUG 82
AUG 82
JUN 83
APR 86

5.0 SPD ONLY
1.2 DOC ONLY
2.2
1.2
1.1 DOC ONLY
8.8
1.0
4.1
2.1
2.1
3.1

JAN 86
JAN 86
JUN 86
JAN 86
JAN 86
JUL 83
DEC 82
JUL 82
FEB 86
FEB 86
MAR 86

4.2
1.3 RETIRED

JAN 86
MAY 86
MAR 86

1.2 RETIRED

MAR 86

PRODUCT AVAILABILITY DATES - RSX (cont'd)

PRODUCT
RSX-UM-PLUS
RSX-llM-PLUS DECgraph-11
RSX-llM-PLUS DECtype
RSX-llM-PLUS DIBOL
RSX-llM-PLUS V3.0 UPDATE
RSX-llS
RSX-llS V4.2 UPDATE
RTEM-11
SORT/MERGE,PDP-11
SPM-llM
SPM-1 lM-PLUS
SSP-11

VERSION
3.0
1.2 RETIRED
3.1
1.2
B

4.2
B

2.2
3.0
2.1 RETIRED
2.1 RETIRED
1.3 DOC ONLY

AVAILABLE
JAN 86
FEB 86
JUN 86
APR 86
MAY 86
JAN 86
MAY 86
APR 86
JUN 84
APR 86
APR 86
JAN 86

RSX-11 M V4.2

•
•

RSX Software Dispatch, September 1986

RSX-llM V4.2
SYSGEN
COMMAND FILES

•

Seq. No. 1.1.1.9 M
1 of 1

SGNPER ABORTS WHEN CREATING DATABASE FOR VTll (SPR ll-M89724 KN)
PROBLEM
STATEMENT:
When generating an RSX-llM or RSX-llS operating system with graphics
support, SYSGEN aborts with a fatal error in the module SGNPER.

device

RESPONSE:
In the module SGNPER, there is a subroutine call to the label UMR.
This
statement is only executed when a graphics device has been selected. This
label does not appear in the module, thus causing a fatal Indirect error.
This problem will be corrected in RSX-llM Version 4.2 Update D.

(
3

•
•

RSX Software Dispatch, September 1986

RSX-llM V4.2
MCR
INTERNAL CMDS

•
•

Seq. No. 2.2.1.3 M
1 of 1

SET/NOMAIN FOLLOWED BY PAR CAUSES GARBAGE OUTPUT TO TI: (SPR ll-M00190P JF)
PROBLEM
STATEMENT:
When using single-user MCR, the SET /NOMAIN command causes
garbage output and hang when the next command is entered.

MCR

produce

RESPONSE:
When processing the SET /NOMAIN command, MCR pops an extra word off the stack,
thus corrupting one of its buffers.
The SET /NOMAIN command removes the
partition correctly. However, when MCR processes the next command, it tries
to use the corrupted buffer and prints garbage output.
This is only a problem with the single-user version of MCR (MCR.TSK).
Single-user MCR stays active after every command, waiting for the next command
to process.

(
•
•

Multiuser MCR consists of two tasks: the primary (MCRMU.TSK) and the secondary
(SYS.TSK). The SET /NOMAIN command is processed by the secondary task, which
exits after every command. Therefore, the corruption is not propagated to the
next command. It disappears when MCR exits after the SET /NOMAIN command.
A
new copy of the MCR task image without the corruption comes into memory to
process the next command.
As a workaround, set a feature mask bit that will cause single-user MCR to
exit after every command just like the multiuser secondary. This will prevent
the corruption from being propagated to the next command.
In the Executive
map file, [l,34]RSX11M.MAP, find the address of $FMASK. Open that location
and set bit 40000, FE.MXT.
For example, if $FMASK is at address 011560, do
the following:
)OPE 11560/KNL
011560 /010250 050250<ESC>

This problem is corrected in RSX-llM Version 4.2 Update D.

(
5

•
•

•

(

RSX Software Dispatch, September 1986

Seq. No.

RSX-11M V4.2
MCR
VMR

2.2.s.s M
1 of 1

SET /NOECHO DOES NOT WORK (SPR ll-M00187P JF)
PROBLEM
STATEMENT:
The VMR command SET /NOECHO=TTnn: does not take effect when the system is
booted.
The command executes without errors and the SET /NOECHO command
displays the terminal as NOECHO. However, in the booted system, the terminal
is set to ECHO.
RESPONSE:

The terminal characteristic bit for NOECHO was changed for the current
release.
VMR, however, was not changed. VMR is setting and checking the old
characteristic bit instead of the new one, so, when the system is booted, the
terminal driver does not recognize the terminal as NOECHO. VMR will be
changed to set and check the new characteristic bit.
This problem is corrected in RSX-llM Version 4.2 Update D.

(

(
7

RSX Software Dispatch, September 1986

RSX- llM V4. 2
DRIVERS
FOX-TTDRV

Seq. No. 3.1.3.6 M
1 of 1

POWERFAIL TO OUTPUTTING DHV LEAVES LINE HUNG ( SPR ll-M026g3 LK)
PROBLEM
STATEMENT:
lf power is lost when output is occurring to the
line hangs after the power recovery.

DHV-11

terminal

line,

the

RESPONSE:
This problem occurs because of an incorrect setting of the "OMA ABORT" bit in
the Line Control Register (LNCTRL). This bit is set after the power recovery
because the driver assumes there is an output 1/0 in progress. It determines
this by looking at the US.OIU bit in the U.STS word of the terminal UCB. The
bit is zero (which means there is an output I/O in progress), but the physical
output was terminated by the power failure. Setting the "DMA ABORT" bit in
this case does not cause an output interrupt, and, therefore, the TTORV code
that clears the "OMA ABORT" bit is not executed and the terminal line stays
disabled until the system reboot.
This problem is corrected in RSX-llM Version 4.2 Update D.

(

(
9

•

(

RSX Software Dispatch, September 1986

RSX-llM V4.2
MULTI-USER TASK
HELLO

Seq. No. 4.2.4.1 M
1 of 1

DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES (SPR ll-M89782 RDH)
PROBLEM
STATEMENT:
The CLI documentation states that alternate CLI prompts (as specified in the
/CPR and /DPR subkeywords) can be from 0 through 31 characters long. This
worked fine on prior releases of RSX-11, but on Version 3.0 of RSX-llM-PLUS, a
length of zero (null prompt) will cause HELLO to trap. On Version 3.0 of
RSX-llM-PLUS and Version 4.2 of RSX-llM, lengths of one or two characters will
result in a Memory Protect or SST Abort Bad Stack trap from Indirect.
RESPONSE:

c
c

The description of the CLI command in the MCR Operations Manual includes
provision for the 0-, 1-, or 2-character prompts. It also describes that <CR>
and <LF> must be explicitly specified if they are desired in the prompt.
Unfortunately, HELLO assumes there is a leading <CR>, and Indirect assumes
there are leading <CR> and <LF> characters in the prompt.
When those
facilities concatenate the prompt and a display line, they skip over the
assumed <CR> and <LF> characters, moving the remainder of the string into an
output buffer. If the prompt is zero, one, or two characters, they will try
to move a string of zero or negative length, thereby corrupting the HELLO task
or the stack or attempting to access memory which is outside the task space.
If you wish to have a null prompt in an alternate CLI, you can work around
this problem by specifying three NUL characters; for example, specify it as:
CLI /INIT= ••••••••••• /DPR="<O><O><O>"••••••••
in your command line.
A 1- or 2-character prompt
preceding the prompt with two NUL characters such as:

can

specified

CLI /INIT= ••••••••••• /DPR="<O><O>/->/" ••••••••••
where the desired prompt is "->".
RSX-llM Version 4.2 Update D will include corrections for this problem. HELLO
and Indirect will skip past leading <CR> or <LF> characters only if they are
included in the prompt specification.

(
11

•

(

RSX Software Dispatch, September 1986

RSX-llM V4.2
UTILITIES
BRU

Seq. No. 5.1.17.14 M
1 of 1

STAND-ALONE BRU /IMAGE:SAVE INCORRECTLY INITIALIZES DISKS
(SPR ll-M00289X SIR)
PROBLEM
STATEMENT:
Stand-alone BRU initializes the second and subsequent disks of a multivolume
save set incorrectly during an /IMAGE:SAVE operation. Because the disks are
not initialized correctly, it is not possible to copy a multivolume save set
created by stand-alone BRU with either stand-alone BRU or on-line BRU. If the
save set is created by on-line BRU, all volumes of the save set are
initialized correctly and it can be copied.
RESPONSE:

c
c

Stand-alone BRU (BRUSYS/BRU64K) incorrectly initializes disks other than the
first during an /IMAGE:SAVE operation as a result of a problem in the code
which creates headers for the system files.
Because a variable is not
initialized at run time, the Extension Segment Number (M.ESQN), Extension
Relative Volume Number (M.ERVN), Extension File Number (M.EFNU), and Extension
File Sequence Number (M.EFSQ) fields in the headers of each of the system
files on volumes other than the first contain incorrect values.
The ability to restore a multivolume disk save set created by stand-alone BRU
is not affected, because BRU does not use this information when restoring the
save set.
This problem is corrected in RSX-llM Version 4.2 Update D•

•

(
13

RSX Software Dispatch, September 1986

Seq. No. 5.1.17.15 M

RSX-llM V4.2
UTILITIES
BRU

1 of 1

BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE (SPR ll-M00291X SIR)
PROBLEM
STATEMENT:
BRU does not skip over the bootable system image at the beginning of
as described in the Release Notes, when an MS: device is used.
Also, when a disk-to-tape compare operation is attempted on
bootable system image, the compare fails on all tape
following message:
BRU -- *WARNING*
I/O error code -13

tape,

a tape with a
devices with the

Tape label error

RESPONSE:
BRU is unable to skip over the bootable system image at the beginning of a
tape on an MS: device. It depends upon the device driver to return the
length of a block read from tape in order to detect the presence of the
bootable system image. RSX tape drivers, other than MSDRV, return the number
of bytes read in the second word of the I/O status block at the completion of
a QIO request. However, because of hardware limitations, MSDRV returns the
number of bytes actually transferred to the receiving buffer. Because the
number of bytes transferred will never exceed the size of the input buffer,
MSDRV returns the size of the input buff er when the block read is larger than
the input buffer. The other RSX tape drivers return the number of bytes in
the block read when this data overrun situation occurs. Because the ability
of BRU to detect a bootable system image depends upon the latter behavior, it
does not work with MS: devices. The implementation of this feature in BRU
has been changed to work correctly with all supported tape devices.
The failure of disk-to-tape compare operations on tapes with a bootable system
image is caused by the omission of the code to provide this functionality for
compare operations.
These problems are corrected in RSX-llM Version 4.2 Update D.

•

(

RSX Software Dispatch, September 1986

RSX-llM V4. 2
UTILITIES
BRU

Seq. No. 5.1.17.16 M
1 of 1

BRU PROBLEM WITH LARGE FID NUMBERS (SPR 11-M00192P RK)
PROBLEM
STATEMENT:

(

BRU displays erroneous warning messages when backing up a file with a file
identification number (FID) greater than or equal to 100000 (octal). These
warning error messages are either "File ID sequence number error" or "File not
found." If the file is a directory file, no files from that directory are
backed up.
RESPONSE:
BRU incorrectly uses a signed branch when checking the FID. This may cause a
backup operation to fail for a file whose FID is greater than or equal to
100000 (octal).
This problem does not occur if the headers in the index file are allocated
contiguously.
This may be accomplished on a disk with no bad blocks by
initializing the volume with the largest number of headers that might ever be
used.
This problem is corrected in RSX-llM Version 4.2 Update C.

(

•

(
15

· RSX Software Dispatch, September 1986

RSX-llM V4.2
UTILITIES
BRU

Seq. No. 5.1.17.17 M
1 of 1

BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UFDs
(SPR ll-M00294X SIR)
PROBLEM
STATEMENT:
When restoring a backup set containing only empty user file directories
(UFDs) and /VERIFY is specified, BRU does not create the UFDs on the output
volume correctly. Therefore, attempts to create files in these UFDs fail.
RESPONSE:
This problem occurs because BRU does not mark the headers for each UFD as "in
use" in the index file bitmap if the backup set contains only empty UFDs and
the /VERIFY qualifier is specified. This causes subsequent attempts to create
a file in the UFD to fail.
This problem does not occur if the /VERIFY qualifier is not specified for the
restore operation. The restore may still be verified by performing a separate
/COMPARE operation following the restore.
This problem is corrected in RSX-llM Version 4.2 Update D.

•

(

RSX Software Dispatch,

September 1986

RSX-llM V4.2
TASK BUILDER
TKB

Seq. No.

5.3.1.4 M
1 of 1

ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION (SPR ll-M00175P DR)
PROBLEM
STATEMENT:
The TKB option ASG will cause the following message to be reported if a
specified unit number is greater than the value found in the most recent UNITS
option:
"Illegal logical unit number"
If a UNITS option is not found prior to the ASG, then a unit number
than 6, which is the default value, will also cause the message.

greater

The DCL LINK command can inadvertently lead to this condition.

(

In RSX-llM Version 4.2 Update D, this situation does not cause the above
message to be reported. The assignment is accepted, regardless of the unit
number. After all options have been processed, the following new
diagnostic
message is reported and the larger value used as an implicit UNITS:
*DIAG*-Illegal number of logical units

•
Units set to maximum assigned

(
17

•

RSX Software Dispatch, September 1986

RSX-llM V4.2
DCL
DCL

Seq. No. 6.1.0.12 M
1 of 1

SET DEFAULT WITHOUT PARAMETERS DOES NOT WORK CORRECTLY (SPR ll-M88197 LP)
PROBLEM
STATEMENT:
The RSX-llM V4.2 DCL command SET DEFAULT currently
message:

responds

with

the

error

SET -- Invalid device
when it is issued with no arguments. According to the documentation, when SET
DEFAULT is issued with no arguments, a nonprivileged user's default device and
UFD are supposed to be returned to the login defaults. For a privileged user,
the default device is supposed to be returned to the login default, while the
UFD remains unchanged.

RESPONSE:
The behavior of the SET DEFAULT command was inadvertently changed for the
release of V4.2 of RSX-llM when new support was added to the SET command for
RSX-llM-PLUS.
This problem is corrected in RSX-llM Version 4.2 Update D.

(

(
19

•

RSX Software Dispatch, September 1986

PDP-11 BASIC-PLUS-2 V2.3
for RSX-llM V4.2

Seq. No. 10.20.1.2 N
1 of 1

BASIC-PLUS-2 V2.3 RSX UPDATE B NOTICE
The BASIC-PLUS-2 V2.3 update files received with Update B of RSX-llM V4.2 and
RSX-llM-PLUS V3.0 introduce a problem which under certain circumstances
corrupts data values used by a program or written to a file. The situation is
as follows:
Arrays declared within MAP or COMMON statements are not mapped properly. As a
result, subsequent implicit or explicit assignments to elements of this array
may overwrite the contents of other variables declared within the MAP or
COMMON.
For example:
10 MAP (TSTDAT)
20

STRING FOO = 4%,
STRING ARRAY_1(7%)

&
10%

FOO = 'ABCD'
PRINT 'FOO before making array assignment ='•, FOO
ARRAY 1(0%) = 'ZZZZZZZZZZ'
PRINT-'FOO after making array assignment ='; FOO
END

This program, when
incorrect output:

compiled

and

taskbuilt,

will

produce

the

following

FOO before making array assignment = ABCD
FOO after making array assignment = ZZZZ

This same program will work correctly when executed from the BASIC-PLUS-2
environment (i.e., OLDed and RUN) or if you do a COMPILE/MAC and then assemble
the resultant file.
NOTE
This problem exists only if you have applied the
BASIC-PLUS-2 V2.3 corrections distributed with Update B
of RSX-llM V4.2 and RSX-llM-PLUS V3.0. The problem
will be corrected in Update C.
To avoid this problem, the following alternatives exist:
1.

(

2.
3.
4.

Before applying the update, edit the BASIC-PLUS-2
file, BP2PCH.CMD, and remove the following line:
WRITE LBR -37 RSXLIB.OLB/RP = -37 objgsd
Do not apply the BASIC-PLUS-2 Update B files
COMPILE/MAC and assemble the resultant file
RUN from the BASIC-PLUS-2 environment
21

update

command

•

RSX-llM V4.2
CUMULATIVE INDEX
SEPTEMBER 1986

(

This is a complete listing of all articles for RSX-llM V4.2 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 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
1.1.1.3 M
1.1.1.4 M
1,1.1.5 M
1.1.1.6 F
1.1.1.1 M
1.1.1.8 M
1.1.1.9 M

Sep 85
Nov 85
Apr 86
May 86
Jun 86
Jul 86
Jul 86
Aug 86
Sep 86

RSX-llM V4.2
SYSGEN
SYSGEN PHASE 1 ASKS QUESTIONS THAT SHOULD NOT BE ASKED
TK50 FAILS TO INTERRUPT WHEN ACF IS RUN ON PDP-11/84
ACF MAY NOT CORRECTLY SET UP DV.NUC IN CONFIG 0 DAT FOR RS03/4s
SYSGEN DOES NOT USE AUTOCONFIGURE RESULTS IF NONSTANDARD EXEC
SYSGEN TRAPS DURING PHASE 1 ONLY ON PDP-11/34 WHEN ACF HAS RUN
DECIMAL NUMBER CAUSES ERROR IN OCTAL RADIX SYSGEN QUESTION
SYSGEN FOR NONZERO MU: PHYSICAL UNIT NUMBERS
BUILDING FCPSML GIVES ILLEGAL MEMORY LIMITS
SGNPER ABORTS WHEN CREATING DATABASE FOR VTll

(
23

Component

Sequence

Mon/Yr

ACD SUPPORT CAUSES AN UNDEFINED SYMBOL IN SYSGEN

2.1.1.1 M

Jun 86

ALTERNATE CLI AND MCR PASS COMMAND AROUND

2.1.1.2 N

Jul 86

PARTY USES WRONG CONDITIONAL

2.1 0 1 0 3 M

Aug 86

EXECUTIVE
DIRECTIVES

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

Jan 86

MCR
INTERNAL CMOS
TAS COMMAND ABORTS

2.2.1.1 M
2.2.1.2 M

May 86

SET /TERM DOES NOT ACCEPT LQPOl AND LQP02
SET/NOMAIN FOLLOWED BY PAR CAUSES GARBAGE OUTPUT TO TI:

2.2.1.3 M

Sep 86

INS
NEW nTASK IMAGE I/O ERROR" MESSAGE FOR DEVICES

2.2.2.1 M

Apr 86

2.2.2.2 M
2.2.2.3 R

Apr 86

SCHEDULING OF SHUFFLER MAY CRASH SYSTEM
DELETING THE DISK IMAGE OF AN INSTALLED TASK
INDIRECT, ICQ, ICM, ICP
INDIRECT CAN CONFUSE IDENTICAL LABELS
FILE NAME AND SUBSTITUTION ERRORS IN INDIRECT
INDIRECT PROBLEMS CORRECTED IN UPDATE B
24-HOUR MAXIMUM FOR 0 DELAY DIRECTIVE
INVALID CHARACTERS IN SUBSTITUTION SYMBOL NAMES
INDIRECT COMMAND

SETT <ERSEEN> LEAVES IT FALSE

.EXIT DIRECTIVE WITHIN BEGIN-END BLOCK

Jun 86

Jul 86

2.2.3.1 R*
2.2.3.2 M

Sep 85

2.2.3.3 M
2.2.3.4 M

Feb 86
Mar 86

2.2.3.5 M
2.2.3.6 M

Mar 86

2.2.3.7 M

Jan 86

Mar 86
Mar 86

ERROR IN EXECUTION ON @/LB:MODULE FROM DCL OR MCR

2.2.3.8 M

Mar 86

ESCAPE RESPONSE TO .ASKS DEFINES SYMBOL AS LOGICAL

2.2.3.9 M
2.2.3.10 M

Apr 86

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

Apr 86

2.2.3.11 M
2.2.3.12 M

Apr 86

2.2.5.1 M
2.2.5.2 M

May 86

2.2.5.3 M
2.2.5.4 M

May 86

2.2.5.5 M

Sep 86

2.2.6.l N*
2.2.6.2 M

Sep 85

SAV DOES NOT SIZE MEMORY CORRECTLY ON UNIBUS SYSTEMS
SAVE DOES NOT SIZE MEMORY ABOVE 1920 kW ON Q-BUS SYSTEMS

2.2.6.3 M

Feb 86

SUPPORT FOR DOUBLE-SIDED FLOPPY

3.1.1.1 M*

Sep 85

DDDRV TIMES OUT WHILE COPYING LARGE FILES

3.1.1.2 M

Mar 86

DLDRV's ERROR RECOVERY SHOULD MAKE COMPLETE DRIVE-STATUS CHECK
DUDRV's LBN RANGE CHECKING IS INADEQUATE

3.1.1.3 M

Mar 86

3.1.1.4 M

Jul 86

IMBEDDED PERIODS NOT ALLOWED IN

TESTPARTITION

Aug 86.

VMR
INCORRECT ERROR MESSAGE
ERROR TASK SOMETIMES WHEN BUILDING VMR
SET /NETUIC IS ALLOWED WHEN NETWORK IS NOT SUPPORTED
SET /TERM DOES NOT ACCEPT LA210, LQPOl, LQP02, AND LQP03
SET /NOECHO DOES NOT WORK

May 86
Jun 86

•

SAV/BOO
BOOT HANGS ON COPY OF A SYSTEM SAVED ON DIFFERENT CONTROLLER

Feb 86

DRIVERS
DYDRV, DUDRV, DRDRV, DDDRV, DLDRV

•

(

Component

Sequence

Mon/Yr

MUDRV, MSDRV
MUDRV DOES NOT SUPPORT MULTIPLE-DENSITY TAPE DRIVES
SYSTEM CRASHES WITH MUDRV/PUCOM MAPPED
MSDRV SPACING TIME-OUT VALUE IS INSUFFICIENT
MSDRV RETURNS IE.EOF SPACING REVERSE TO BOT

3.1.2 0 1 M
3.1.2.2 M
3.1.2.3 M
3.1.2.4 M

Mar 86
Mar 86
Jul 86
Jul 86

FDX-TTDRV
DRIVER DOUBLE FORK CAUSES SYSTEM CRASH ON 0-BUS SYSTEM
VARIOUS TTDRV PROBLEMS
GET/SET CHARACTERISTIC DOES NOT WORK WHEN GET OPTIONS NOT SELECTED
BIC OF S6.EIO NOT CONDITIONALIZED ON EXTENDED I/O
ASSEMBLY ERRORS IN THE TTATT MODULE
POWERFAIL TO OUTPUTTING DHV LEAVES LINE HUNG

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

Feb 86
Mar 86
Jun 86
Jul 86
Jul 86
Sep 86

XEDRV
VARIOUS XEDRV PROBLEMS

3.1.5.1 M

Mar 86

FILE SYSTEM
FCS
RECORDS MAY SPAN BLOCKS

May 86

FUACP
LARGE DISK SUPPORT

Jul 86

ERROR LOGGING
CONTROL FILES
RPT DOES NOT RECOGNIZE USER-WRITTEN MODULES
UPDATE ERROR-CODE TABLE IN MSCP60.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
RPT ABORTS WITH MESSAGE ERLRPT-F-CASENOMAT FOR DU1 ERRORS
LBN FOR RM80s ARE INCORRECT IN ERROR LOG REPORT

3 0 3 0 5.1 M
3.3.5.2 M
3 0 3 0 5.3 M
3.3.5.4 M
3.3.5.5 M
3.3.5.6 M
3.3.5 0 7 M

Mar 86
Mar 86
Mar 86
Mar 86
Apr 86
Jul 86
Jul 86

BATCH/QUEUE MGR
ONG

STICKINESS IS LOST IN FILE EXTENSION IF FILES DO NOT EXIST

Mar 86

LPP

•

(

LPP LOOPS ON NEGATIVE RECORD LENGTH
LN03 PRINTS 51 LINES PER SHEET IN LANDSCAPE MODE
LPP HANGS WHEN USING SIMULATED FORl'I FEEDS
UNSOLICITED INPUT FROM PRINT DEVICES CRASHES THE SYSTEM

4 0 1 0 5.1 M
4.1.5.2 M
4 0 1 0 5.3 M
4.1.5.4 M

Apr 86
Jun 86
Aug 86
Aug 86

MULTI-USER TASK
BYE
BYE HANGS WITH LOW POOL

Jun 86

HELLO
DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES

Sep 86

Component

Sequence

Mon/Yr

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.1.10.1 M

Mar 86

PIP
DELETING FILES, 10 DOES NOT ALWAYS WORK PROPERLY
PIP DISPLAYS NEGATIVE NUMBER OF FILES

5.1.12.1 M
5.1.12.2 M

Apr 86
Aug 86

BRU
BRU "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
BRU /IMAGE:RESTORE DISPLAYS ERRORS DESPITE SUCCESS
BRU64K /COMPARE/IMAGE1SAVE DOES NOT WORK PROPERLY
STAND-ALONE BRU /IMAGE:SAVE INCORRECTLY INITIALIZES DISKS
BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE
BRU PROBLEMS WITH LARGE FID NUMBERS
BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UFOs

5.1.11.1 M
5.1.11.2 N
5.1.11.J 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.11.11 M
5.1.11.12 M
5.1.11.13 M
5.1.11.14 M
5.1.11.15 M
5.1.11.16 M
5.1.11.11 M

Dec 85
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Apr 86
Jun 86
Jul 86
Sep 86
Sep 86
Sep 86
Sep 86

SYSTEM LIBRARIES
RSXMAC
MINOR ERROR IN GCII$ MACRO
FORTRAN CALLS WFLORS AND STLORS DO NOT WORK

5.2.4.1 M
5.2.4.2 M

May 86
Aug 86

CSI$1 AND CSI$2 MEMORY PROTECT
SYSLIB $DIVD CONFLICTS WITH FORTRAN IV $DIVD

5.2.6.1 M
5.2.6.2 N

Mar 86
Jun 86

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

5.J.0.1 M
5.J.0.2 M

Apr 86
Apr 86

5.J.1.1 N
5.J.1.2 M
5.J.1.J M
5.J.1.4 M

Nov 85
Feb 86
Jun 86
Sep 86

5.5.1.1 M

Apr 86

•

TKB

TKB OPENED AND CLOSED THE COMMAND FILE FOR EACH OPTION
I/D TASK LINKED TO LIBRARY AND COMMON DOES NOT BUILD
I/D TASK WITH DATA IN COMMON PSECT DOES NOT GET CAUGHT CORRECTLY
ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION
DEBUGGING AIDS

(

ODT

TASK WITH LARGE NUMBER OF LUNs HANGS IN ODT

Co1122nent

seguence

Monl'.Yr

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

5.7.1.1 N

Apr 86

PMD/SNAP
PMD PUTS OUTPUT IN WRONG PLACE

5.7.3.1 N

Jun 86

MFT/DTE
MFT FAILS TO FUNCTION PROPERLY

5 0 7 0 12 0 1 N

Mar 86

RCT
RCT DOES NOT REPLACE ALL BAD BLOCKS

5.1.15.1 M

Feb 86

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

Feb 86
Feb 86
Feb 86
Mar 86
Apr 86
Apr 86
Jun 86
Jun 86
Jul 86
Jul 86
Aug 86
Sep 86

10.5 0 1 0 1 N*

Sep 85

10.8.3.1 N
10.8.3.2 N

May 86
May 86

10.20.1.1 N

Dec 85

(

,,.

.E£!:.

(

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
DCL •sET DE· SHOULD NOT DEFAULT TO SET DEC CRT
FORTRAN /CHECK REQUIRES /F77
ADD SUPPORT FOR COBOL-81 /CONDITIONALS QUALIFIED
DCL SHOULD NOT ACCEPT TERMINAL TYPE RT02 OR RT02C
DCL SET PROTECTION DOES NOT WORK WITH FILES STARTING WITH ·L·
SET DEFAULT WITHOUT PARAMETERS DOES NOT WORK CORRECTLY

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

(

DECnet-llM/S V4.2
DECnet-11M/S PROBLEMS FIXED ON RSX-llM AND RSX-llS LAYERED UPDATE B
DECnet-RSX DELUA DEVICE SUPPORT

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

FORTRAN IV/RSX V2.6

(

OTS
LIST-DIRECTED READ

Dec 85

UPDATE C
FORTRAN IV PROBLEMS CORRECTED ON UPDATE C

Jun 86

Component

Sequence

Mon/Yr

FORTRAN IV/VAX TO RSX V2.7
INSTALLATION GUIDE/RELEASE NOTES ERRATA

Jul 86

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

Apr 86

RSX-115 V4.2

RSX Software Dispatch, September 1986

RSX-llS V4.2
SYSGEN
COMMAND FILES

Seq. No. 1.1.1.1 M
1 of 1

SGNPER ABORTS WHEN CREATING DATABASE FOR VTll (SPR 11-589724 KN)
PROBLEM
STATEMENT:
When generating an RSX-llM or RSX-llS operating system with graphics
support, SYSGEN aborts with a fatal error in the module SGNPER.

device

RESPONSE:
In the module SGNPER, there is a subroutine call to the label UMR.
This
statement is only executed when a graphics device has been selected. This
label does not appear in the module, thus causing a fatal indirect error.
This problem will be corrected in RSX-llS Version 4.2 Update D.

(
31

RSX-llS V4.2
CUMULATIVE INDEX
SEPTEMBER 1986

(

This is a complete listing of all articles for RSX-llS V4 0 2 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 duration of the current
release and will be incorporated with any future release, unless otherwise stated.

Sequence

Mon/Yr

RSX-llS V4 0 2

(

SYSGEN
COMMAND FILES
SGNPER ABORTS WHEN CREATING DATABASE FOR VTll

Sep 86

11SGEN2
11SGEN2 RETURNS "COMMAND FILE OPEN ERROR"
11SGEN2 PROBLEMS
llSGEN LOOKS FOR UML, RCT, AND CDA BLD FILES IN [1,20)
EXECUTIVE
DIRECTIVES
ACD SUPPORT CAUSES AN UNDEFINED SYMBOL IN SYSGEN

1.1.6.1 M
1.1.6.2 M
1.1.6.3 M

Feb 86
Apr 86
May 86

Jun 86

(
33

Component

Sequence

Mon/Yr

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

3.1.2.1 M
3 0 1.2.2 M

Mar 86
Mar 86

FDX-TTDRV
GET/SET CHARACTERISTIC DOES NOT WORK WHEN GET OPTIONS NOT SELECTED
BIC OF S6 0 EIO NOT CONDITIONALIZED ON EXTENDED I/O

3.1.3.1 M
3.1.3.2 M

Jun 86
Jul 86

UTILITIES
BRU
BRU •No FILES FOUND• PROBLEM CORRECTED

Dec 85

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

Mar 86

MISC SYS TASKS
RCT
RCT DOES NOT REPLACE ALL BAD BLOCKS

Feb 86

DECnet-llM/S V4.2
DECnet-llM/S PROBLEMS FIXED ON RSX-llM AND RSX-llS LAYERED UPDATE B
DECnet-RSX DELUA DEVICE SUPPORT

10.8.3.1 N
10.8.3.2 N

May 86
May 86

RSX-11 M-PLUS V3.0

(

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
SYSGEN
COMMAND FILES

Seq. No. 1.1.1.s M
1 of 1

APPLICATION NOT PROPERLY INSTALLED (SPR ll-P00173P CCS)
PROBLEM
STATEMENT:

Use of the APPLICATION= option in SYSPARAM.DAT fails to install applications
properly.
The application is started the first time the system boots;
however, it is not started on subsequent boots.
RESPONSE:
When a pregenerated RSX-llM-PLUS system boots, the startup command file checks
for a file called FASTART.CMD. If this file exists, the system assumes all
application startup commands have been placed into this file.
If the file
does not exist, it is created and the APPLICATION= commands are executed.
Unfortunately, the commands in the application's startup file are not copied
into FASTART.CMD.
Code has been added to STARTUP.CMD in RSX-llM-PLUS Version 3.0 Update D to add
the proper application commands to FASTART.CMD. The file type cannot be .INS,
since that type is reserved for the Micro/RSX optional software installation
procedure.

(
37

(

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
SYSGEN
DISTRIB KITS

Seq. No. 1.1.2.2 N
1 of 1

CANNOT COPY SECOND BACKUP SET USING CERTAIN MS TAPE DRIVES (SPR ll-P00288X CS)
PROBLEM
STATEMENT:

A user may not be able to standalone-copy the second backup set from the
RSX-llM-PLUS V3.0 1600 bpi magnetic tape distribution kit, using certain MS
device tape drives.
RESPONSE:
This problem is caused by the baseline system MS device driver (MSDRV) having
an inadequate spacing timeout value for slow MS device tape drives such as the
TSOS unit.
If you experience this problem, you may work around it by doing the following:

Copy the RSX-llM-PLUS V3.0 baseline system, as described in Section
2.4 of the System Generation and Installation Guide Manual. using the
BRUSYS system.

Hardware boot the target system disk, as described in Section 2.4.1.2
step 11, and when prompted to "Enter the date and time:," respond by
typing a CTRL/Z.

Modify the V3.0 baseline system MS
values as follows:

driver

(MSDRV)

spacing

timeout

OPE 226/DRV=MS:(CR)
226/001377 3372(ESC)
OPE 240/DRV=MS:(CR)
240/001377 3372<ESC)
4.

Reinvoke the baseline system startup command file as follows:
@[2,54]BASTART

This problem will be corrected in a future RSX-llM-PLUS product release.

(
39

(

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
EXECUTIVE
DIRECTIVES

Seq. No. 2.1.1.9 N
1 of 1

SYSTEM CORRUPTION IN DEFAULT UIC (SPR ll-P86587 EP)

PROBLEM
STATEMENT:
The default directory string is corrupt and/or the system crashes after a
period of repeatedly executing RUN commands for installed tasks (as with CHAIN
statements in BASIC).

RESPONSE:
When MCR is parsing a RUN command, it allocates a block of space for use as a
clock queue element.
MCR links the parent task's context block into this
element and properly increments the reference count in the context block.
When the requested task is run immediately, MCR deallocates the space, but
fails to delete the reference to the context block.
As RUN commands are
repeated, the reference count increases until it reaches the 400 (octal) limit
of a byte. Then it wraps around to 0 and then 1. When another process
properly attempts to delete a reference to the context block, the reference
count drops from 1 to
O, and the block is deallocated, even though there
are other valid pointers to the block, such as U.CTX in the terminal's UCB.
The space released to secondary pool is typically reallocated for use as a
command buffer, causing corruption of the default directory string recorded in
the context block. This change in the default string causes errors, such as
"Illegal file name."
Also, continued use of the reference count causes
corruption of the command queue, leading to a system crash.
This problem can be worked around by using the INSTALL-RUN-REMOVE form of
RUN command.

the

MCR has been corrected to delete the reference to a context block unless it is
going to be used and deleted in the clock queue. This problem is corrected in
RSX-llM-PLUS Version 3.0 Update C.

(
41

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
EXECUTIVE
DIRECTIVES

Seq. No. 2.1.1.10 M
1 of 1

RPOI RETURNS IE.IDU FROM A VT: (SPR ll-P00135P PW)

•
PROBLEM
STATEMENT:
The RPOI$ directive fails with the error IE.IOU - Invalid Device or Unit when
issued from a VT: device. This causes any user-written CLI, including the
TMCLI included on the kits, to be unusable in batch.

RESPONSE:
This problem is the result of the way the system keeps track of how many
tasks are active on virtual terminals.
Because it is possible to delete
virtual terminals and their data bases from the system when they are no longer
needed, the system needs to keep an active task count for each virtual
terminal. Before the terminal is deleted, the system must make sure no tasks
are referencing the terminal's data base. The active task count is used for
this purpose.
To simplify the task of keeping the active task count, task spawning
on a virtual terminal was limited to the task that created the terminal.
Unfortunately, in the case of batch, the batch processor has created the
virtual terminals, and the CLI is the task attempting to issue the RPOI
directives. The RPOI is rejected because the CLI did not create the terminal.
This has been fixed to allow CLis and tasks already running on the virtual
terminal to spawn tasks for the terminal. This correction will be included in
RSX-llM-PLUS Version 3.0 Update D.

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
EXECUTIVE
SHF

Seq. No. 2.1.2.1 M
1 of 1

SHUFFLER MAY CAUSE SYSTEM CRASH (SPR ll-P00290X JB)
PROBLEM
STATEMENT:
It is possible for the Shuffler to cause a system crash.
RESPONSE:

In Version 3.0 of RSX-llM-PLUS, the routine $DECLK was modified to handle
deallocation of a clock block which contained a pointer to a default named
directory.
The Shuffler task sometimes allocates a clock block, then
deallocates it without ever initializing the contents of the data block. On
deallocation, it calls the routine $DECLK, which checks for certain values.
If the uninitialized block happens to contain a certain valid request type in
the request field, the routine will attempt to deaccess the structure which
contains the default named directory. This pointer, however, has never been
initialized and the routine will thus corrupt random locations in memory,
which could result in a system crash.
The Shuffler will be modified to call the general
deallocating uninitialized clock block structures.
corrected in RSX-llM-PLUS Version 3. 0 Update D.

(
43

routine $DEACB when
This problem will be

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
MCR
INS

Seq. No. 2.2.2.3 M
1 of 1

INSTALL, RUN, REMOVE WINDOW ALLOWS OTHER TASKS TO ACTIVATE IT
(SPR ll-P00293X DR)
PROBLEM
STATEMENT:
A system may behave erratically and possibly crash shortly after
the following message:

INS

reports

INS -- Task active
RESPONSE:

This situation only occurs during "flying" installs, where a task is
installed, immediately run, and then removed. Because of an oversight in INS,
it is possible for a task to be activated between the following events:
o

INS enters the TCB of said task into the STD

INS uses the RPO!$ system directive to activate the task itself

INS, upon detecting the status indicating the task is already active, proceeds
to "clean up," releasing various data structures (currently in use) back to
primary pool. Beyond this point, results are unpredictable.
If the task is being activated by another task in user mode, a
to lower its priority to a value less than that of INS.

workaround

In RSX-llM-PLUS Version 3.0 Update D, INS disables context switching around
the two events described above. This at least inhibits all other tasks from
executing in user mode, thereby avoiding having a task activated during
the crucial time. This, however, does not address code running in kernal
mode. In the future, we will consider switching to system-state to further
avoid inadvertent activation.

(
45

(

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
MCR
VMR

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

SET /NOECHO DOES NOT WORK (SPR 11-P00187P JF)
PROBLEM
STATEMENT:
The VMR command SET /NOECHO=TTnn: does not take effect when the system is
booted.
The command executes without errors and the SET /NOECHO command
displays the terminal as NOECHO. However, in the booted system, the terminal
is set to ECHO.
RESPONSE:
The terminal characteristic bit for NOECHO was changed for the current
release.
VMR, however, was not changed. VMR is setting and checking the old
characteristic bit instead of the new one, so, when the system is booted, the
terminal driver does not recognize the terminal as NOECHO. VMR will be
changed to set and check the new characteristic bit.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update D.

(
47

(

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
DRIVERS
DUD RV

Seq. No. 3.1.1.6 M
1 of 1

SYSTEM CRASH AFTER SHADOWING (SPR ll-P85562A GM)

PROBLEM
STATEMENT:
A system crash occurs during disk shadowing from DUO:
to DUI:
(RA81 to
RA81).
The system consistently crashes 10-12 minutes after starting Shadow
Recording.

RESPONSE:

On UNIBUS systems, for each data transfer I/O, a UMR (UNIBUS Map Register)
wait block is allocated. The DU driver has a set of pointers to these wait
blocks and keeps a count of the UMR wait blocks it uses on a controller basis.
To indicate a wait block is in use, bit zero of the pointer to that wait block
is set.
The driver calls $GSPKT to get an I/O packet.
$GSPKT, when it finds a
specified unit is being shadowed, creates a secondary packet for that primary
packet. It then puts it in the SCB queue for that device on a priority basis
and initiates the driver before finishing the GSPKT processing for the primary
packet. When called this way, the driver calls $GSPKT again to get another
packet.
If it finds another primary packet for the unit being shadowed, it
creates a secondary packet for that primary packet, puts it in the appropriate
queue, and initiates the driver again. These repeated calls to the driver
before finishing the GSPKT processing for the primary packets results in
recursion.
Because of these recursive calls to the driver during shadowing, the driver
fails to keep proper track of the UMR wait block count. It then accesses the
location beyond the table of wait block pointers and sets bit zero in that
location.
This location contains an address of a controller specific data
structure used to store controller context. When this structure is accessed,
the system crashes with an odd address trap.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update C•

(
49

(

RSX Software Dispatch, September 1986

Seq. No. 3.1.3.7 M

RSX-llM-PLUS V3.0
DRIVERS
FDX-TTDRV

1 of 1

POWERFAIL TO OUTPUTTING DHV LEAVES LINE HUNG (SPR ll-P02693 LK)
PROBLEM
STATEMENT:
If power is lost when output is occurring to the
line hangs after the power recovery.

DHV-11

terminal

line,

the

RESPONSE:
This problem occurs because of an incorrect setting of the "DMA ABORT" bit in
the Line Control Register (LNCTRL). This bit is set after the power recovery
because the driver assumes there is an output I/O in progress. It determines
this by looking at the US.OIU bit in the U.STS word of the terminal UCB. The
bit is zero (which means there is an output I/O in progress), but the physical
output was terminated by the power failure. Setting the "DMA ABORT" bit in
this case does not cause an output interrupt, and, therefore, the TTDRV code
that clears the "DMA ABORT" bit is not executed and the terminal line stays
disabled until the system reboot.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update D.

(
51

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
FILE SYSTEM
FCS

Seq. No. 3.2.1.2 M
1 of 1

FCS DOES NOT PARSE ANSI FILE SPECIFICATION CORRECTLY (SPR ll-P88291 TS)
PROBLEM
STATEMENT:

(

During the preparse of the file specification, the unit characteristics are
not known. When the quoted string is finally reached in the specification, it
is rejected because of the unknown unit characteristics. At the final parse,
the file specification is parsed successfully, but the set of bits saved from
the incorrect parse to describe the specification overwrite the bits from the
correct parse.
One workaround for this problem is to use the regular file specification where
possible.
For example, instead of using MM:"DECSUPP.TXT", use the equivalent
file specification MM:DECSUPP.TXT, which refers to the same file name.
Another workaround is to not define the specification in a logical name and
set the bit FL.AEX in the F.FLG byte of the FDB. This will indicate to the
parse routine that the file specification has already been expanded and PARSE
will then use the old way of expansion, which does work with specifications
containing quoted strings, e.g., MM:"DECSUPP.TXT".
This problem is corrected in RSX-llM-PLUS Version 3.0 Update D.

(
53

(

RSX Software Dispatch, September 1986

(
Seq. No. 4.2.3.2 M

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

1 of 1

BYE FROM BATCH JOB OR SILENT CLI DOES NOT ABORT INDIRECT (SPR 11-P89055 RDH)
PROBLEM
STATEMENT:

When BYE is invoked because of a timeout of a batch job or from a silent CLI,
the Indirect Command Processor is not aborted if it is running. Subsequent
attempts to log in to that batch processor or from that terminal, if it was a
silent CLI, will fail.
RESPONSE:
BYE normally invokes LB:[l,2]SYSLOGOUT.CMD as a part of its processing.
This
is accomplished by calling routine CMDFIL. Within CMDFIL, prior to invoking
SYSLOGOUT.CMD, Indirect is aborted if it is still active. If the user is a
batch processor or has a silent CLI, the call to CMDFIL is omitted and
Indirect is not aborted.
Workarounds to this problem include:

(

If using a silent CLI, assure that Indirect is not active prior to
logging out. Otherwise, abort it with the ABO AT.Tnn command from a
privileged account.

If Indirect is left running from a batch processor timeout, abort
with the ABO AT.Vn command from a privileged account.

RSX-llM-PLUS Version 3.0 Update D will include corrections to this problem.
Aborting Indirect, if active, will be moved from routine CMDFIL to a new
routine INDABO, which will be called in all cases.

(
55

RSX Software Dispatch, September 1986

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

Seq. No. 4.2.4.3 M
1 of 1

DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES (SPR ll-P89782 RDH)

PROBLEM
STATEMENT:
The CLI documentation states that alternate CLI prompts (as specified in the
/CPR and /DPR subkeywords) can be from 0 through 31 characters long. This
worked fine on prior releases of RSX-11, but on Version 3.0 of RSX-llM-PLUS, a
length of zero (null prompt) will cause HELLO to trap. On Version 3.0 of
RSX-llM-PLUS and Version 4.2 of RSX-llM, lengths of one or two characters will
result in a Memory Protect or SST Abort Bad Stack trap from Indirect.
RESPONSE:
The description of the CLI command in the MGR Operations Manual includes
provision for the 0-, 1-, or 2-character prompts. It also describes that (CR)
and <LF) must be explicitly specified if they are desired in the prompt.
Unfortunately, HELLO assumes there is a leading (CR), and Indirect assumes
there are leading <CR) and <LF> characters in the prompt.
When those
facilities concatenate the prompt and a display line, they skip over the
assumed <CR) and (LF) characters, moving the remainder of the string into an
output buffer. If the prompt is zero, one, or two characters, they will try
to move a string of zero or negative length, thereby corrupting the HELLO task
or the stack or attempting to access memory which is outside the task space.

If you wish to have a null prompt in an alternate CLI, you can work around
this problem by specifying three NUL characters; for example, specify it as:
CLI /INIT= ••••••••••• /DPR="<O><O><O>" ••••••••
in your command line.
A 1- or 2-character prompt
preceding the prompt with two NUL characters such as:

can

specified

CLI /INIT= ••••••••••• /DPR="<O><O>/->/" ••••••••••
where the desired prompt is "->".
RSX-llM-PLUS Version 3.0 Update D will include corrections for this problem.
HELLO and Indirect will skip past leading (CR) or (LF) characters only if
they are included in the prompt specification.

(
57

•

RSX Software Dispatch, September 1986

(
Seq. No. 5.1.12.3 M

RSX-llM-PLUS V3.0
UTILITIES
PIP

1 of 1

PIPRES/APPEND TERMINATES WITH ODD ADDRESS (SPR ll-P00292X RK)
PROBLEM
STATEMENT:
The APPEND function of PIP (the PIPRES version) terminates with:
"Odd address or other trap four"
This happens only for certain files.
RESPONSE:
The APPEND function of PIPRES aborts with "Odd address or other trap four"
because part of the code is overwritten by the data from the input file. This
occurs because a buffer that is passed by PIPRES to FCS for transferring data
from the input file is in instruction space.
The task PIPRES is being built incorrectly, resulting in the above problem.
As a workaround, PIP can be used instead of PIPRES. Another workaround is to
build PIPRES without the /MU (multiuser) switch.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update D.

(
59

(

RSX Software Dispatch, September 1986

RSX-llM-PLOS V3.0
UTILITIES
BRU

Seq. No. 5.1.17.14 M
1 of 1

STAND-ALONE BRO /IMAGE:SAVE INCORRECTLY INITIALIZES DISKS
(SPR ll-P00289X SIR)
PROBLEM
STATEMENT:
Stand-alone BRO initializes the second and subsequent disks of a multivolume
save set incorrectly during an /IMAGE:SAVE operation. Because the disks are
not initialized correctly, it is not possible to copy a multivolume save set
created by stand-alone BRU with either stand-alone BRO or on-line BRO.
If
the save set is created by on-line BRO, all volumes of the save set are
initialized correctly and it can be copied.
RESPONSE:
Stand-alone BRO (BROSYS/BR064K) incorrectly initializes disks other than the
first during an /IMAGE:SAVE operation as a result of a problem in the code
which creates headers for the system files.
Because a variable is not
initialized at run time, the Extension Segment Number (M.ESQN), Extension
Relative Volume Number (M.ERVN), Extension File Number (M.EFNU), and Extension
File Sequence Number (M.EFSQ) fields in the headers of each of the system
files on volumes other than the first contain incorrect values.

(

The ability to restore a multivolume disk save set created by stand-alone BRU
is not affected, because BRU does not use this information when restoring the
save set.
This problem is corrected in RSX-llM-PLOS Version 3.0 Update D.

(
61

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
UTILITIES
BRU

Seq. No. 5.1.17.15 M
1 of 1

BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE (SPR ll-P00291X SIR)

•
PROBLEM
STATEMENT:
BRU does not skip over the bootable system image at the beginning of
as described in the Release Notes, when an MS: device is used.
Also, when a disk-to-tape compare operation is attempted on
bootable system image, the compare fails on all tape
following message:
BRU -- *WARNING*
I/O error code -13

tape,

a tape with a
devices with the

Tape label error

RESPONSE:
BRU is unable to skip over the bootable system image at the beginning of a
tape on an MS: device. It depends upon the device driver to return the
length of a block read from tape in order to detect the presence of the
bootable system image. RSX tape drivers, other than MSDRV, return the number
of bytes read in the second word of the I/O status block at the completion of
a QIO request. However, because of hardware limitations, MSDRV returns the
number of bytes actually transferred to the receiving buffer. Because the
number of bytes transferred will never exceed the size of the input buffer,
MSDRV returns the size of the input buffer when the block read is larger than
the input buffer. The other RSX tape drivers return the number of bytes in
the block read when this data overrun situation occurs. Because the ability
of BRU to detect a bootable system image depends upon the latter behavior, it
does not work with MS: devices. The implementation of this feature in BRU
has been changed to work correctly with all supported tape devices.
The failure of disk-to-tape compare operations on tapes with a bootable system
image is because of the omission of the code to provide this functionality for
compare operations.
These problems are corrected in RSX-llM-PLUS Version 3.0 Update D.

(

RSX Software Dispatch, September 1986

Seq. No. 5.1.17.16 M

RSX-llM-PLUS V3.0
UTILITIES
BRU

1 of 1

BRU PROBLEM WITH LARGE FID NUMBERS (SPR ll-P00192P RK)
PROBLEM
STATEMENT:

(

BRU displays erroneous warning messages when backing up a file with a
file identification number (FID) greater than or equal to 100000 (octal).
These warning error messages are either "File ID sequence number error" or
"File not found." If the file is a directory file, no files from that
directory are backed up.
RESPONSE:
BRU incorrectly uses a signed branch when checking the FID. This may cause a
backup operation to fail for a file whose FID is greater than or equal to
100000 (octal).
This problem does not occur if the headers in the index file are allocated
contiguously.
This may be accomplished on a disk with no bad blocks by
initializing the volume with the largest number of headers that might ever be
used.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update C.

(
63

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
UTILITIES
BRU

Seq. No. 5.1.17.17 M
1 of 1

BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UFDs
(SPR ll-P00294X SIR)
PROBLEM
STATEMENT:
When restoring a backup set containing only empty user file directories
(UFDs) and /VERIFY is specified, BRU does not create the UFDs on the output
volume correctly. Therefore, attempts to create files in these UFDs fail.
RESPONSE:
This problem occurs because BRU does not mark the headers for each UFD as "in
use" in the index file bitmap if the backup set contains only empty UFDs and
the /VERIFY qualifier is specified. This causes subsequent attempts to create
a file in the UFD to fail.
This problem does not occur if the /VERIFY qualifier is not specified for the
restore operation. The restore may still be verified by performing a separate
/COMPARE operation following the restore.
This problem is corrected in RSX-llM-PLUS Version 3.0 Update D.

(

RSX Software Dispatch, September 1986

RSX-llM-PLUS V3.0
TASK BUILDER
TKB

Seq. No. 5.3.1.S M
1 of 1

ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION (SPR 11-P00175P DR)
PROBLEM
STATEMENT:
The TKB option ASG will cause the following message to be reported if a
specified unit number is greater than the value found in the most recent UNITS
option:
Illegal logical unit number
If a UNITS option is not found prior to the ASG, then a unit number greater
than 6, which is the default value, will also cause the message.
The DCL LINK command can inadvertently lead to this condition.
RESPONSE:
TKB was making this comparison for validation purposes.
Since the UNITS
option controlled how many entries were created in the logical unit table, it
did not make sense for an ASG unit to be greater.
To work around this, simply position all ASG options after the UNITS option.
When using the DCL LINK command, supply a file containing the options.

(
•

In RSX-llM-PLUS Version 3.0 Update D, this situation does not cause the above
message to be reported. The assignment is accepted regardless of the unit
number. After all options have been processed, the following new diagnostic
message is reported and the larger value used as an implicit UNITS:
*DIAG*-Illegal number of logical units
Units set to maximum assigned

(
65

(

RSX-llM-PLUS V3.0

(

CUMULATIVE INDEX
SEPTEMBER 1986

This is a complete listing of all articles for RSX-llM-PLUS V3.0

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

Mandatory Patch.

The flags and definitions are as follows.

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.

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

Sequence

Mon/Yr

1.1.0.1 M

Apr 86

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

1 0 1 0 1.1 M

UNDEFINED REFERENCE IN DR4COM 0 MAP

1.1.1.2 M
1.1.1.3.N

Apr 86
May 86
Jun 86

1.1.1.4 M
1.1.1.s M

Jul 86
Sep 86

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

ACT FAILS TO DETECT FIFTH DZll
COMMAND FILES
SYSGEN FOR NONZERO MU: PHYSICAL UNIT NUMBERS
APPLICATION NOT PROPERLY INSTALLED

(
67

Component

Sequence

Mon/Yr

DISTRIB KITS
DAPRES NOT PROPERLY INSTALLED
CANNOT COPY SECOND BACKUP SET USING CERTAIN MS TAPE DRIVES

1.1.2.1 M
1 0 1.2 0 2 N

Feb 86
Sep 86

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

2 0 10 0 0 1 M

Mar 86

DIRECTIVES
FAST MAP FACILITY HAS ADDITIONAL RESTRICTION AND ERROR CODE
GSSW$ CRASHES SYSTEMS WITH NO SWITCH REGISTER
DEVICE NORMALIZATION OCCURS ON ALL LOGICAL NAME DIRECTIVES
TASKS WITHOUT EXTERNAL HEADERS CRASH SYSTEM WITH CRAW$
A PARSE OF " " CRASHES THE SYSTEM
FSS$ ALWAYS RETURNS SUCCESS
DRPFN $LNFCS REMOVES ZEROS
RESCHEDULED COPIES OF TASK ARE INITIATED WITH WRONG UIC
SYSTEM CORRUPTION IN DEFAULT UIC
RPOI RETURNS IE.IOU FROM A VT:

2.1.1.1 M
2.1.1.2 R
2.1.1.3 M
2.1.1.4 M
2.1.1.s M
2.1.1.6 N
2.1 0 1 0 7 M
2.1.1.8 M
2.1.1.9 N
2.1.1.10 M

Mar 86
Apr 86
May 86
Jun 86
Jul 86
Jul 86
Jul 86
Jul 86
Sep 86
Sep 86

SHF
SHUFFLER MAY CAUSE SYSTEM CRASH

2 0 1 0 2.1 M

Sep 86

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

2.1.5.1 M

Apr 86

MISC ROUTINES
CERTAIN CALLS TO $QRMVT SHOULD BE CHANGED TO $QRMVA
DRMAP HAS UNDEFINED SYMBOL IN FAST MAPPING SUPPORT
UNMAPPED FAST MAP WINDOW DESCRIPTOR CAUSES SYSTEM CRASH
ERROR LOGGER REPORT FOR RK07 IS MEANINGLESS

2.1.6.l M
2.1.6.2 M
2.1.6.3 M
2.1.6.4 M

Jan 86
May 86
Aug 86
Aug 86

DATA CACHING
MOUNTING A DU: DEVICE MAY CAUSE CRASH IF ANOTHER IS CACHING
CACHE REGION NAME

2.1.1.1 M
2.1.1.2 M

Jun 86
Aug 86

MCR
INTERNAL CMOS
CBD NEEDS TO KNOW ABOUT NEW REGION CHARACTERISTICS
ASN COMMANDS WITH NULL LOGICALS CAUSE SYSTEM CRASH
SET /CACHE EXTENT SIZE = 0 CRASHES SYSTEM
CACHE READ-AHEAD LESS THAN VIRTUAL CAN CRASH SYSTEM
SET /SPEED DOES NOT ACCEPT EXTA OR EXTB

2.2.1.1 M
2.2.1.2 M
2.2.1.3 M
2.2.1.4 M
2.2.1.s M

Jan 86
Apr 86
Jun 86
Jul 86
Jul 86

INS
NEW "TASK IMAGE I/O ERROR" MESSAGE FOR DEVICES
DELETING THE DISK IMAGE OF AN INSTALLED TASK
INSTLL,RUN,REMOVE WINDOW ALLOWS OTHER TASKS TO ACTIVATE IT

2.2.2.1 M
2.2.2.2 R
2.2.2.3 M

Apr 86
Jul 86
Sep 86

INDIRECT, ICQ, ICM, ICP
INDIRECT EXITS WITHOUT WARNING ON I/O ERROR
LOGICAL NAME AND SUBSTITUTION ERRORS IN INDIRECT

2.2.3.1 M
2.2.3.2 M

Jan 86
Jan 86

(

Component

Sequence

Mon/Yr

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
.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
DIRECTIVE .ASK WITH TIME-OUT CANNOT CHECKPOINT
IMBEDDED PERIODS NOT ALLOWED IN 0 TESTPARTITION

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
2.2.3.10 M
2.2.3.11 M
2.2.3.12 M
2.2.3.13 M
2.2.3.14 M

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

VMR
SET /NOTYPEAHEAD CAUSES CRASH
SET /NOECHO DOES NOT WORK

2. 2. 5.1 M

2.2.5.2 M

May 86
Sep 86

2.2.6.1 M
2.2.6.2 M
2.2.6.3 M
2.2.6.4 M

Feb 86
Mar 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
LOA
LOA /EXP DOES NOT ACCEPT SIZE VALUES OF 40000 OR GREATER

DRIVERS
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
BYE HANGS WHEN SPINNING DOWN REMOVABLE RC25 BEFORE FIXED
DUDRV's LBN RANGE CHECKING IS INADEQUATE
SYSTEM CRASH AFTER SHADOWING

3.1.1.1 M
3.1.1.2 M
3.1.1.3 M
3.1.1.4 R
3.1.1.5 M
3.1.1.6 M

Aug 85
Mar 86
Mar 86
Jun 86
Jul 86

MUDRV
MUDRV DOES NOT SUPPORT MULTIPLE-DENSITY TAPE DRIVES
SYSTEM CRASHES WITH MUDRV/PUCOM MAPPED
MSDRV SPACING TIME-OUT VALUE IS INSUFFICIENT
MSDRV RETURNS IE.EOF SPACING REVERSE TO BOT
CANNOT USE MS: DEVICE ON 22-BIT, 0-BUS I/D SYSTEM

3.1.2.1 M
3.1.2.2 M
3 0 1.2.3 M
3.1.2.4 M
3.1.2.5 M

Mar 86
Mar 86
Jul 86
Jul 86
Jul 86

CONTROL CHARACTERS TYPED TO CONTINUATION PROMPT CRASH SYSTEM
BIC OF S6 0 EIO NOT CONDITIONALIZED ON EXTENDED I/O
ASSEMBLY ERRORS IN THE TTATT MODULE
LAT TERMINALS DO NOT ALLOW I/O HANG UP
POWERFAIL TO OUTPUTTING DHV LEAVES LINE HUNG

3.1.3.1 N
3.1.3.2 M
3.1. 3. 3 M
3.1.3.4 M
3.1.3.5 M
3.1.3.6 M
3.1.3.7 M

Feb 86
Mar 86
Jun 86
Jul 86
Jul 86
Jul 86
Sep 86

XEDRV
VARIOUS XEDRV PROBLEMS

3.1.5.l M

Mar 86

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

(

Aug 86

Sep 86

Sequence

Component

Mon/Yr

CODRV
CONSOLE LOGGING TASK COT DOES NOT SUPPORT NAMED DIRECTORIES
FCS
RECORDS MAY SPAN BLOCKS
FCS DOES NOT PARSE ANSI FILE SPECIFICATION CORRECTLY

Aug 86

May 86
Sep 86

3.2.1.1 M
3 0 20 1 0 2 M

FllACP
LARGE DISK SUPPORT

Jul 86

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 TKSO ARE NOT ANALYZED PROPERLY
RPT ABORTS WITH MESSAGE ERLRPT-F-CASENOMAT FOR DU: ERRORS
LBN FOR RM80s ARE INCORRECT IN ERROR LOG REPORT
RPT FAILS WHEN A GEOMETRY SUMMARY IS REQUESTED

3.3.S.1 M
3.3.S.2 M
3.3.S.3 M
3.3.s.4 M
3.3.s.s M
3. 3. s. 6 M

BATCH/QUEUE MGR
BPR
BPR GIVES CRYPTIC ERROR MESSAGE WHEN FILE IS DELETED
SUBMIT /NOPRINT PUTS LOG FILE IN WRONG PLACE

4.1.1.1 M
4.1.1.2 M

OMG
INCORRECT ERROR MESSAGE IF DEVICE IS INVALID
STICKINESS IS LOST IN FILE EXTENSION IF FILES DO NOT EXIST
EXTERNAL HEADER INCONSISTENCY IN QMG CRASHES SYSTEM

4.1.3.1 M
4.1.3.2 M
4.1.3.3 M

Mar 86
Mar 86
Aug 86

LPP
LPP LOOPS ON NEGATIVE RECORD LENGTH
LPP MISCOUNTS PAGES IN PRINT JOB
LN03 PRINTS 51 LINES PER SHEET IN LANDSCAPE MODE
LPP HANGS WHEN USING SIMULATED FORM FEEDS
UNSOLICITED INPUT FROM PRINT DEVICES CRASHES THE SYSTEM

4.1.s.1 M
4.1.s.2 M
4.1.s.3 M
4.1.S.4 M
4.1.s.s M

Apr 86
May 86
Jun 86
Aug 86
Aug 86

MULTI-USER TASK
ACNT
IF LAST NAME CHANGED IN ACNT, PASSWORD DOES NOT WORK
A NAMED DIRECTORY OF [G,M) TYPE NOT DELETED BY ACNT
ACNT PUTS USER IN NAMED MODE IF ANYTHING TYPED FOR DEFAULT DIRECTORY
NULL PASSWORD NOT ALLOWED IN PSW
ACNT DOES NOT ALLOW REMOVAL OF DEFAULT FILE PROTECTION

4.2.1.1 N
4.2.1.2 M
4.2.1.3 N
4.2.1.4 M
4.2.1.s M

May 86
May 86
May 86
Jun 86
Jul 86

BRO
BRO ON SYSTEMS WITHOUT ACCOUNTING: GARBAGE IN USER NAME

4 0 2.2 0 1 N

Apr 86

BYE
BYE HANGS WITH LOW POOL
BYE FROM BATCH JOB OR SILENT CLI DOES NOT ABORT INDIRECT

4.2.3.1 M
4.2.3.2 M

Jun 86
Sep 86

Mar 86
Mar 86
Mar 86
Jul 86
Jul 86
Jul 86

Apr 86
May 86

•

(

Component

Sequence

Mon/Yr

HELLO
SYSTEM CRASH WHEN USER ENTERS INCORRECT PASSWORD
ODD ADDRESS TRAP IN HELLO IF SYSGEN WITHOUT ALTERNATE CLI
DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES

4.2.4.1 M
4.2.4.2 M
4.2.4.3 M

Jul 86
Jul 86
Sep 86

SHUTUP
MISLEADING ACCOUNTING WARNINGS IN SHUTUP

4.2.5.1 M

May 86

UTILITIES
BAD
/ALLOCATE AND /NOEXERCISE GIVE I/O ERROR CODE -2 IN ANALYZE

5.1.1.1 M

Jun 86

INI
INI WILL NOT EXECUTE A COMMAND LINE GREATER THAN 80 CHARACTERS

5.1.8.1 M

Aug 86

MOU
MOUNT DOES NOT WAIT FOR RA80/81 TO SPIN DOWN!
MOUNT ACCEPTS EXTENT SIZES OF ZERO FOR CACHE OPTIONS
CACHE READ-AHEAD LESS THAN VIRTUAL CAN CRASH SYSTEM
MOU WILL CLEAR VOLUME VALID ON LABEL ERROR ON SHARED DISK
MOUNT ACCEPTS EXTENT SIZE OF ZERO FOR CACHE OPTIONS

5.1.10.1 M
5.1.10 0 2 M
5.1.10 0 3 M
5.1.10.4 M
5.1.10.5 M

Mar 86
Jul 86
Jul 86
Jul 86
Jul 86

PIP
DELETING FILE, 10 DOES NOT ALWAYS WORK PROPERLY
PIP DISPLAYS NEGATIVE NUMBER OF FILES
PIPRES/APPEND TERMINATES WITH ODD ADDRESS

5.1.12.1 M
5.1.12.2 M
5.1.12.3 M

Apr 86
Aug 86
Sep 86

5.1.17.1 M
5.1.17.2 N
5.1.17.3 N
5.1.17.4 N

BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UFOS

5.1.11.5 N
5.1 0 17.6 N
5.1.17.7 N
5.1.11.8 N
5.1.17.9 M
5.1.17.10 N
5.1.17.11 M
5.1 0 17 0 12 M
5.1.17.13 M
5.1.17.14 M
5.1 0 17.15 M
5.1.17.16 M
5 0 1 0 17 0 17 M

Dec 85
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Apr 86
Jun 86
Jun 86
Jul 86
Sep 86
Sep 86
Sep 86
Sep 86

SYSTEM LIBRARIES
FORTRAN EXEC, RSXMAC
LOGICAL NAME FORTRAN INTERFACE ROUTINES RETURN IE.SOP
GDVI$ MACROS MISSING FROM RSXMAC 0 SML
MINOR ERROR IN GCII$ MACRO
FORTRAN CALLS WFLORS AND STLORS DO NOT WORK

5.2.4.1 M
5.2.4.2 M
5.2 0 4.3 M
5.2.4.4 M

May 86
May 86
May 86
Aug 86

BRU
BRU "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 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
BACKUPS TO TAPE FAIL UNDER A-TO-Z CONTROL
BRU /IMAGE:RESTORE DISPLAYS ERRORS DESPITE SUCCESS
BRU64K /COMPARE/IMAGE:SAVE DOES NOT WORK PROPERLY
STAND-ALONE BRU /IMAGE:SAVE INCORRECTLY INITIALIZES DISKS
BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE
BRU PROBLEM WITH LARGE FID NUMBERS

c
•

(

Component

Sequence

Mon/Yr

CSI$1 AND CSI$2 MEMORY PROTECT
Rl NOT PROPERLY UPDATED IN MODULE INTDAS
SYSLIB $DIVD CONFLICTS WITH FORTRAN IV $DIVD

5o2o6ol M
5.2.6.2 M
5020603 N

Mar 86
Jun 86
Jun 86

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

5.J.0.1 M
5.J.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
I/D TASK WITH DATA IN COMMON PSECT DOES NOT GET CAUGHT CORRECTLY
ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION

5.J.1.1 M
5.J.1.2 N
5.J.1.J M
5.J.1.4 M
5.J.1.5 M

Aug 85
Nov 85
Feb 86
Jun 86
Sep 86

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

5.5.1.1 M

Apr 86

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

5.7.1.1 N

Apr 86

PMD/SNAP
PMD SNAPSHOT FOR I/D SNAPSHOT DUMPS I-SPACE AND NOT D-SPACE
PMD PUTS OUTPUT IN WRONG PLACE

5.7.J.1 M
5.7.J.2 N

Apr 86
Jun 86

RMDEMO
RMD C PAGE DISPLAY WRONG WHEN CACHING SET TO 4096.

5.7.5.1 M

Jul 86

COT
COT000 ABORTS WITH ODD ADDRESS TRP

5.7.14.1 M

Jul 86

RCT
RCT DOES NOT REPLACE ALL BAD BLOCKS

5.1.15.1 M

Feb 86

6.1.0.1 M
6.1.0.2 M
6.1.0.J M
6.1.0.4 M
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

Mar 86
Apr 86
Apr 86
Jun 86
Jun 86
Jul 86
Jul 86
Jul 86
Aug 86
Aug 86

29:.
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
DCL •sET DE• SHOULD NOT DEFAULT TO SET DEC CRT
FORTRAN /CHECK REQUIRES /F77
ADD SUPPORT FOR COBOL-81 /CONDITIONALS QUALIFIED
DCL SHOULD NOT ACCEPT TERMINAL TYPE RT02 OR RT02C
DCL SHOW ASSIGNMENTS RETURNS •ILLEGAL FUNCTION" ERROR
DCL EDIT WITH NULL FILE NAME DOES NOT WORK
DCL SET PROTECTION DOES NOT WORK WITH FILES STARTING WITH "L"

(

Component

Sequence

Mon/Yr

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

Aug 85

DECnet-llM-PLUS VJ.O
DECnet-llM-PLUS PROBLEMS FIXED ON RSX-llM-PLUS LAYERED UPDATE B
DECnet-RSX DELUA DEVICE SUPPORT

10.8.2.1 N
10 0 8 0 2 0 2 N

May 86
May 86

10.20.1.1 N
10.20.1.2 N

Sep 86

BASIC-PLUS-2 V2.3
PROBLEM WITH PRINT USING
BASIC-PLUS-2 V2.3 RSX UPDATE B NOTICE

Dec 85

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

Dec 85

UPDATE C
FORTRAN IV PROBLEMS CORRECTED ON UPDATE C

Jun 86

FORTRAN IV/VAX TO RSX V2.7
INSTALLATION GUIDE/RELEASE NOTES ERRATA

Jul 86

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

Apr 86

(
73

Micro/RSX V3.0

(

RSX Software Dispatch, September 1986

Micro/RSX V3.0
EXECUTIVE
DIRECTIVES

Seq. No. 2.1.1.7 N
1 of 1

SYSTEM CORRUPTION IN DEFAULT UIC (SPR ll-X86587 EP)
PROBLEM
STATEMENT:
The default directory string is corrupt and/or the system crashes after a
period of repeatedly executing RUN commands for installed tasks (as with CHAIN
statements in BASIC).
RESPONSE:

c
(

When MCR is parsing a RUN command, it allocates a block of space for use as a
clock queue element.
MCR links the parent task's context block into this
element and properly increments the reference count in the context block.
When the requested task is run immediately, MCR deallocates the space, but
fails to delete the reference to the context block.
As RUN commands are
repeated, the reference count increases until it reaches the 400 (octal) limit
of a byte. Then it wraps around to O, and then 1. When another process
properly attempts to delete a reference to the context block, the reference
count drops from 1 to 0, and the block is deallocated, even though there
are other valid pointers to the block, such as U.CTX in the terminal's UCB.
The space released to secondary pool is typically reallocated for use as a
command buffer, causing corruption of the default directory string recorded in
the context block. This change in the default string causes errors, such as
"Illegal file name."
Also, continued use of the reference count causes
corruption of the command queue, leading to a system crash.
This problem can be worked around by using the INSTALL-RUN-REMOVE form of
RUN command.

the

MCR has been corrected to delete the reference to a context block unless it is
going to be used and deleted in the clock queue. This problem is corrected in
in Micro/RSX Version 3.1.

RSX Software Dispatch, September 1986

Micro/RSX V3.0
EXECUTIVE
DIRECTIVES

Seq. No. 2.1.1.8 M

1 of 1

RPOI RETURNS IE.IDU FROM A VT: (SPR ll-X00135P PW)

PROBLEM
STATEMENT:
The RPOI$ directive fails with the error IE.IDU - Invalid Device or Unit when
issued from a VT: device. This causes any user-written CLI, including the
TMCLI included on the kits, to be unusable in batch.

RESPONSE:
This problem is caused by of the way the system keeps track of how many
tasks are active on virtual terminals.
Because it is possible to delete
virtual terminals and their data bases from the system when they are no longer
needed, the system needs to keep an active task count for each virtual
terminal. Before the terminal is deleted, the system must make sure no tasks
are referencing the terminal's data base. The active task count is used for
this purpose.
To simplify the task of keeping the active task count, task spawning
on a virtual terminal is limited to the task that created the terminal.
Unfortunately, in the case of batch, the batch processor has created the
virtual terminals, and the CLI is the task attempting to issue the RPOI
directives. The RPOI is rejected because the CLI did not create the terminal.
This has been fixed to allow CLis and tasks already running on the virtual
terminal to spawn tasks for the terminal. This correction will be included in
a future release of Micro/RSX.

(
78

RSX Software Dispatch, September 1986

Micro/RSX V3.0
EXECUTIVE
SHF

Seq. No. 2.1.2.1 M
1 of 1

SHUFFLER MAY CAUSE SYSTEM CRASH (SPR ll-X00290X JB)

•
PROBLEM
STATEMENT:
It is possible for the Shuffler to cause a system crash.
RESPONSE:

(
79

routine $DEACB when
This problem will be

RSX Software Dispatch, September 1986

Seq. No. 2.2.2.3 M

Micro/RSX V3.0
MCR

1 of 1

INS

INSTALL, RUN, REMOVE WINDOW ALLOWS OTHER TASKS TO ACTIVATE IT
(SPR ll-X00293X DR)
PROBLEM
STATEMENT:
A system may behave erratically and possibly crash shortly after
the following message:

INS

reports

INS -- Task active
RESPONSE:

INS enters the TCB of said task into the STD

INS uses the RPOI$ system directive to activate the task itself

If the task is being activated by another task in user mode, a
to lower its priority to a value less than that of INS.

workaround

In a future release of Micro/RSX, INS will disable context switching around
the two events described above. This at least inhibits all other tasks from
executing in user mode, thereby avoiding having a task activated during
the crucial time. This, however, does not address code running in kernal
mode. In the future, we will consider switching to system state to further
avoid inadvertent activation.

(
81

•

RSX Software Dispatch, September 1986

Seq. No. 3.2.1.2 M

Micro/RSX V3.0
FILE SYSTEM
FCS

1 of 1

FCS DOES NOT PARSE ANSI FILE SPECIFICATION CORRECTLY (SPR ll-X88291 TS)
PROBLEM
STATEMENT:

File Control Services (FCS) with logical name support is unable to parse an
ANSI magnetic tape file specification when it is defined in a logical name
or present in a form which requires no translation.
RESPONSE:
During the preparse of the file specification, the unit characteristics are
not known. When the quoted string is finally reached in the specification, it
is rejected because of the unknown unit characteristics. At the final parse,
the file specification is parsed successfully, but the set of bits saved from
the incorrect parse to describe the specification overwrite the bits from the
correct parse.
One workaround for this problem is to use the regular file specification where
possible.
For example, instead of using MM:"DECSUPP.TXT", use the equivalent
file specification MM:DECSUPP.TXT, which refers to the same file name.
Another workaround is to not define the specification in a logical name and
set the bit FL.AEX in the F.FLG byte of the FDB. This will indicate to the
parse routine that the file specification has already been expanded and PARSE
will then use the old way of expansion, which does work with specifications
containing quoted strings, e.g., MM:"DECSUPP.TXT".
This problem will be corrected in a future release of Micro/RSX.

(
83

RSX Software Dispatch, September 1986

Micro/RSX V3.0
MULTI-USER TASK
BYE

Seq. No. 4.2.3.2 M
1 of 1

BYE FROM BATCH JOB OR SILENT CLI DOES NOT ABORT INDIRECT (SPR ll-X89055 RDH)
PROBLEM
STATEMENT:

If using a silent CLI, assure that Indirect is not active prior to
logging out. Otherwise, abort it with the ABO AT.Tnn command from a
privileged account.

If Indirect is left running from a batch processor timeout, abort
with the ABO AT.Vn command from a privileged account.

A future release of Micro/RSX will include corrections to this problem.
Aborting Indirect, if active, will be moved from routine CMDFIL to a new
routine INDABO, which will be called in all cases.

(
85

RSX Software Dispatch, September 1986

(
Micro/RSX V3.0
MULTI-USER TASK
HELLO

Seq. No. 4.2.4.1 M
1 of 1

DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES (SPR ll-X89782 RDH)
PROBLEM
STATEMENT:

(

The CLI documentation states that alternate CLI prompts (as specified in the
/CPR and /DPR subkeywords) can be from 0 through
31 characters long. This
worked fine on prior releases of RSX-11, but on Version 3.0 of RSX-llM-PLUS, a
length of zero (null prompt) will cause HELLO to trap. On Version 3.0 of
RSX-llM-PLUS and Version 4.2 of RSX-llM, lengths of one or two characters will
result in a Memory Protect or SST Abort Bad Stack trap from Indirect.
RESPONSE:
The description of the CLI command in the MCR Operations Manual includes
provision for the 0-, 1-, or 2-character prompts. It also describes that <CR)
and <LF) must be explicitly specified if they are desired in the prompt.
Unfortunately, HELLO assumes there is a leading <CR), and Indirect assumes
there are leading <CR) and <LF) characters in the prompt.
When those
facilities concatenate the prompt and a display line, they skip over the
assumed <CR) and <LF) characters, moving the remainder of the string into an
output buffer. If the prompt is zero, one, or two characters, they will try
to move a string of zero or negative length, thereby corrupting the HELLO task
or the stac~ or attempting to access memory which is outside the task space.

If you wish to have a null prompt in an alternate CLI, you can work around
this problem by specifying three NUL characters; for example, specify it as:
CLI /INIT= ••••••••••• /DPR="<O><O><O>"••••••••
in your command line.
A 1- or 2-character prompt
preceding the prompt with two NUL characters such as:

can

specified

CLI /INIT= ••••••••••• /DPR="<O><O>/->/"••••••••••
where the desired prompt is "->".
A future release of Micro/RSX will include corrections for this problem.
HELLO and Indirect will skip past leading <CR) or <LF) characters only if
they are included in the prompt specification.

(
87

RSX Software Dispatch, September 1986

Micro/RSX V3.0
UTILITIES
PIP

Seq. No. 5.1.12.2 M
1 of 1

PIPRES/APPEND TERMINATES WITH ODD ADDRESS (SPR ll-X00292X RK)
PROBLEM
STATEMENT:
The APPEND function of PIP (the PIPRES version) terminates with:
"Odd address or other trap four"
This happens only for certain files.
RESPONSE:

The APPEND function of PIPRES aborts with "Odd address or other trap four"
because part of the code is overwritten by the data from the input file. This
occurs because a buffer that is passed by PIPRES to FCS for transferring data
from the input file is in instruction space.
The task PIPRES is being built incorrectly, resulting in the above problem.
As a workaround, PIP can be used instead of PIPRES. Another workaround is to
build PIPRES without the /MU (multiuser) switch.
This problem will be corrected in a future release of Micro/RSX.

(
89

RSX Software Dispatch, September 1986

Micro/RSX V3.0
UTILITIES
BRU

Seq. No. 5.1.17.13 M
1 of 1

BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE (SPR ll-X00291X SIR)

PROBLEM
STATEMENT:
BRU does not skip over the bootable system image at the beginning of
as described in the Release Notes, when an MS: device is used.
Also, when a disk-to-tape compare operation is attempted on
bootable system image, the compare fails on all tape
following message:
BRU -- *WARNING*
I/O error code -13

tape,

a tape with a
devices with the

Tape label error

(
91

RSX Software Dispatch, September 1986

Micro/RSX V3.0
UTILITIES
BRU

Seq. No. 5.1.17.14 M
1 of 1

BRU PROBLEM WITH LARGE FID NUMBERS (SPR ll-X00192P RK)
PROBLEM
STATEMENT:
BRU displays erroneous warning messages when backing up a file with a
file identification number (FID) greater than or equal to 100000 (octal).
These warning error messages are either "File ID sequence number error" or
"File not found." If the file is a directory file, no files from that
directory are backed up.
RESPONSE:
BRU incorrectly uses a signed branch when checking the FID. This may cause a
backup operation to fail for a file whose FID is greater than or equal to
100000 (octal).
This problem does not occur if the headers in the index file are allocated
contiguously.
This may be accomplished on a disk with no bad blocks by
initializing the volume with the largest number of headers that might ever be
used.
This problem will be corrected in a future release of Micro/RSX.

RSX Software Dispatch, September 1986

Seq. No. 5.1.17.15 M

Micro/RSX V3.0
UTILITIES
BRU

1 of 1

BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UFDs
(SPR ll-X00294X SIR)
PROBLEM
STATEMENT:
When restoring a backup set containing only empty user file directories
(UFDs) and /VERIFY is specified, BRU does not create the UFDs on the output
volume correctly. Therefore, attempts to create files in these UFDs fail.
RESPONSE:
This problem occurs because BRU does not mark the headers for each UFD as "in
use" in the index file bitmap if the backup set contains only empty UFDs and
the /VERIFY qualifier is specified. This causes subsequent attempts to create
a file in the UFD to fail.
This problem does not occur if the /VERIFY qualifier is not specified for the
restore operation. The restore may still be verified by performing a separate
/COMPARE operation following the restore.
This problem will be corrected in a future release of Micro/RSX •

•

c
93

RSX Software Dispatch, September 1986

Micro/RSX V3.0
TASK BUILDER
TKB

Seq. No. 5.3.1.2 M
1 of 1

ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION (SPR ll-X00175P DR)
PROBLEM
STATEMENT:
The TKB option ASG will cause the following message to be reported if a
specified unit number is greater than the value found in the most recent UNITS
option:
Illegal logical unit number
If a UNITS option is not found prior to the ASG, then a unit number greater
than 6, which is the default value, will also cause the message.
The DCL LINK command can inadvertently lead to this condition.

RESPONSE:
TKB was making this comparison for validation purposes.
Since the UNITS
option controlled how many entries were created in the logical unit table, it
did not make sense for an ASG unit to be greater.
To work around this, simply position all ASG options after the UNITS option.
When using the DCL LINK command, supply a file containing the options.
In a future release of Micro/RSX, this situation will not cause the above
message to be reported. The assignment is accepted regardless of the unit
number. After all options have been processed, the following new diagnostic
message is reported and the larger value used as an implicit UNITS:
*DIAG*-Illegal number of logical units
Units set to maximum assigned

(
95

Micro/RSX V3.0
CUMULATIVE INDEX
SEPTEMBER 1986

(

This is a complete listing of all articles for Micro/RSX V3.0 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.

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

c
•

•

Sequence

Mon/Yr

Micro/RSX V3.0
SYSGEN
AUTOCONFIGURE
ACF FAILS TO DETECT FIFTH DZll

Jun 86

DISTRIB KITS
DAPRES NOT PROPERLY INSTALLED

Feb 86

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

Mar 86

(
97

Component

Sequence

Mon/Yr

DIRECTIVES
FAST MAP FACILITY HAS ADDITIONAL RESTRICTION AND ERROR CODE
ERROR IN EXECUTION OF @/LB:MODULE FROM DCL
DEVICE NORMALIZATZON OCCURS ON ALL LOGICAL NAME DIRECTIVES
TASKS WITHOUT EXTERNAL HEADERS CRASH SYSTEM WITH CRAW$
FSS$ ALWAYS RETURNS SUCCESS
RESCHEDULED COPIES OF TASK ARE INITIATED WITH WRONG UIC
SYSTEM CORRUPTION IN DEFAULT UIC
RPOI RETURNS IE.IOU FROM A VT:

2 0 1 0 1.1 M
2 0 1.1.2 M
2 0 1.1.3 M
20 1 0 10 4 M
2.1.1.5 N
2.1.1.6 M
2 0 1.1.7 N
2.1.1.8 M

Mar 86
Mar 86
May 86
Jun 86
Jul 86
Jul 86
Sep 86
Sep 86

SHF
SHUFFLER MAY CAUSE SYSTEM CRASH

Sep 86

MISC ROUTINES
UNMAPPED FAST MAP WINDOW DESCRIPTOR CAUSES SYSTEM CRASH

Aug 86

DATA CACHING
MOUNTING A DU: DEVICE MAY CAUSE CRASH IF ANOTHER IS CACHING
CACHE REGION NAME

2 0 1 0 7.1 M
2.1.7.2 M

Jun 86
Aug 86

MCR
INTERNAL CMOS
ASN COMMANDS WITH NULL LOGICALS CAUSE SYSTEM CRASH
SET /CACHE EXTENT SIZE
0 CRASHES SYSTEM
CACHE READ-AHEAD LESS THAN VIRTUAL CAN CRASH SYSTEM

2.2.1.1 M
2.2.1.2 M
2 0 2 0 1.3 M

Apr 86
Jun 86
Jul 86

INS
NEW "TASK IMAGE I/O ERROR" MESSAGE FOR DEVICES
DELETING THE DISK IMAGE OF AN INSTALLED TASK
INSTALL,RUN,REMOVE WINDOW ALLOWS OTHER TASKS TO ACTIVATE IT

2 0 2.2.1 M
2.2.2.2 R
2 0 2.2.3 M

Apr 86
Jul 86
Sep 86

20 20 30 1 M

2 0 2 0 3.9 M
2 0 2.3.10 M
2.2.3.11 M

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

3.1.1.1 M
3 0 1 0 1.2 M
3 0 1 0 1.3 M

Mar 86
Mar 86
Jul 86

INDIRECT, ICQ, ICM, ICP
LOGICAL NAME AND SUBSTITUTION ERRORS IN INDIRECT
INDIRECT PROBLEMS IDENTIFIED ON Micro/RSX V3.o
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
DIRECTIVE .ASK WITH TIME-OUT CANNOT CHECKPOINT
IMBEDDED PERIODS NOT ALLOWED IN 0 TESTPARTITION
DRIVERS
DDDRV, DUDRV, DLDRV
DDDRV TIMES OUT WHILE COPYING LARGE FILES
DLDRV's ERROR RECOVERY SHOULD MAKE COMPLETE DRIVE-STATUS CHECK
DUDRV's LBN RANGE CHECKING IS INADEQUATE

2 0 2 0 3.2 M
2 0 2.3.3 M
20 20 3 0 4 M

2 0 2 0 3.5 M
2 0 2 0 3.6 M
20 20 30 7 M
20 20 30 8 M

•

Component

MUDRV, MSDRV
MUDRV DOES NOT SUPPORT MULTIPLE-DENSITY TAPE DRIVES
SYSTEM CRASHES WITH MUDRV/PUCOM MAPPED
MSDRV SPACING TIME-OUT VALUE IS INSUFFICIENT

Sequence

Mon/Yr

30 10 20 1 M

Mar 86
Mar 86
Jul 86

3 0 1.2 0 2 M
3 0 10 20 3 M

•

FDX-TTDRV
CONTROL CHARACTERS TYPED TO CONTINUATION PROMPT CRASH SYSTEM

Jun 86

•

CODRV
CONSOLE LOGGING TASK COT DOES NOT SUPPORT NAMED DIRECTORIES

Aug 86

FILE SYSTEM
FCS
RECORDS MAY SPAN BLOCKS
FCS DOES NOT PARSE ANSI FILE SPECIFICATION CORRECTLY

3.2.1.1 M
30 20 10 2 M

FllACP
LARGE DISK SUPPORT

..
•

May 86
Sep 86

Jul 86

ERROR LOGGING
CONTROL FILES
END MESSAGE PACKETS FOR MU ARE NOT ANALYZED PROPERLY
ERROR LOG MESSAGE PACKETS FOR TK50 ARE NOT ANALYZED PROPERLY
RPT ABORTS WITH MESSAGE ERLRPT-F-CASENOMAT FOR DU: ERRORS
RPT FAILS WHEN A GEOMETRY SUMMARY IS REQUESTED

3.3.5.1 M
3.3.5.2 M
3 0 3.5.3 M
3.3.5.4 M

Mar 86
Mar 86
Jul 86
Jul 86

BATCH/QUEUE MGR
BPR
BPR GIVES CRYPTIC ERROR MESSAGE WHEN FILE IS DELETED
SUBMIT /NOPRINT PUTS LOG FILE IN WRONG PLACE

4.1.1.1 M
4.1.1.2 M

Apr 86
May 86

OMG
EXTERNAL HEADER INCONSISTENCY IN QMG CRASHES SYSTEM

40 10 3 0 1 M

Aug 86

4.1.5.1 M
4.1.5.2 M
4.1.5.3 M
4.1.5.4 M
4.1.5.5 M

Apr 86
May 86
Jun 86
Aug 86
Aug 86

4.2.1.1 N
4.2.1.2 M
4.2.1.3 N
4.2.1.4 M
4.2.1.5 M

May 86
May 86
May 86
Jun 86
Jul 86

BYE
BYE HANGS WITH LOW POOL
BYE FROM BATCH JOB OR SILENT CLI DOES NOT ABORT INDIRECT

4.2.3.1 M
4.2.3.2 M

Jun 86
Sep 86

Component

Sequence

Mon/Yr

HELLO
DEFAULT CLI PROMPT MUST BE THREE OR MORE BYTES

4.2.4.1 M

Sep 86

SHUTUP
MISLEADING ACCOUNTING WARNINGS IN SHUTUP

4 0 2 0 5.1 M

May 86

•

UTILITIES
BAD

/ALLOCATE AND /NOEXERCISE GIVE I/O ERROR CODE -2 IN ANALYZE

5 0 1.1.1 M

Jun 86

INI
INI WILL NOT EXECUTE A COMMAND LINE GREATER THAN 80 CHARACTERS

5.1.8.1 M

Aug 86

MOU
CACHE READ-AHEAD LESS THAN VIRTUAL CAN CRASH SYSTEM
MOUNT ACCEPTS EXTENT SIZE OF ZERO FOR CACHE OPTIONS
MOU WILL CLEAR VOLUME VALID ON LABEL ERROR ON SHARED DISK

5.1.10.1 M
5.1.10.2 M
5.1.10.3 M

Jul 86
Jul 86
Jul 86

PIP
PIP DISPLAYS NEGATIVE NUMBER OF FILES
PIPRES/APPEND TERMINATES WITH ODD ADDRESS

5.1.12.1 M
5.1.12.2 M

Aug 86
Sep 86

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
BACKUPS TO TAPE FAIL UNDER A-TO-Z CONTROL
BRU /IMAGE:RESTORE DISPLAYS ERRORS DESPITE SUCCESS
BRU64K /COMPARE/IMAGE:SAVE DOES NOT WORK PROPERLY
BRU SKIPPING OVER BOOTABLE SYSTEM IMAGE
BRU PROBLEM WITH LARGE FID NUMBERS
BRU /VERIFY INCORRECTLY RESTORES DISK WITH ONLY EMPTY UFOs

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.11.6 N
5 0 1 0 17 0 7 N
5.1.11.8 N
5.1.11.9 M
5.1.11.10 M
5.1.11.11 M
5.1.11.12 M
5.1.11.13 M
5.1.11.14 M
5.1.11.15 M

Feb 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Mar 86
Jun 86
Jun 86
Jul 86
Sep 86
Sep 86
Sep 86

5.2.4.1 M
5.2.4.2 M
5.2.4.3 M
5.2.4.4 M

May 86
May 86
May 86
Aug 86

MISC SYSLIB
CSI$1 AND CSI$2 MEMORY PROTECT
Rl NOT PROPERLY UPDATED IN MODULE INTDAS
SYSLIB $DIVD CONFLICTS WITH FORTRAN IV $DIVD

5 0 2.6.1 M
5.2.6.2 M
5 0 2.6.3 N

Mar 86
Jun 86
Jun 86

100

•

component

Sequence

Mon/Yr

5.3.0.1 M

Apr 86
Apr 86

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

5.3.0.2 M

TKB

I/D TASK WITH DATA IN COMMON PSECT DOES NOT GET CAUGHT CORRECTLY
ASG OPTION REJECTED IF LUN IS GREATER THAN UNITS OPTION

(

5.3.1.1 M
5.3.1.2 M

MISC SYS TASKS
PMD/SNAP
PMD PUTS OUTPUT IN WRONG PLACE

Jun 86
Sep 86

Jun 86

RM DEMO
RMD C PAGE DISPLAY WRONG WHEN CACHING SET TO 4096 0

s.1.s.1 M

Jul 86

RCT
RCT DOES NOT REPLACE ALL BAD BLOCKS

s.1.1s.1 M

Feb 86

6.1.0.1 M
6.1.0.2 M
6 0 10 0 0 3 M

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
DCL •sET DE" SHOULD NOT DEFAULT TO SET DEC CRT
FORTRAN /CHECK REQUIRES /F77
DCL EDIT WITH NULL FILE NAME DOES NOT WORK
DCL SET PROTECTION DOES NOT WORK WITH FILES STARTING WITH "L•

6.1.0.1 M

Mar 86
Apr 86
Apr 86
Jun 86
Jun 86
Aug 86
Aug 86

DOCUMENTATION
DOCUMENTATION
DOC.ERROR IN CREATING AN OPTIONAL SOFTWARE TAPE KIT

70 10 0 0 1 M

Jan 86

(
101

6.1.0.4 M
60 10 00 5 M
6.1.0.6 M

(

SOFTWARE PERFORMANCE REPORT (SPR) SUBMISSIONS
Digital Equipment Corporation guarantees a response to every SPA submitted by DIGll AL
specialists and customers who purchase software product service agreements.
Blank SPA forms are available upon request in desired quantities from SPA 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 SPA Administration at (617) 493-4 722.
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 SPA responses.

Completing an SPA 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 SPA. 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 SPA Administration at (617) 493-6683.
If you do not want your SPA to be published. check the "DO NOT PUBLISH" box on the SPA
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 rep9rted 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.
DEC mate.
Include as much information as possible; too much information is better than not enough.
Send all information in machine-readable format if 1t 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

103

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

Customer name
Tape format
bpi
Track
Preprinted number of the SPR submitted with the tape

Remove from the tape any unnecessary or confidential files.

Thank you.

104

(

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/B-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 Joliet Curie BP 202
91007 Evry Cedex
France

c
t

(

105

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.
K<lap Hoorndreef 38
NL-3563 AV Utrecht
Holland

Sweden

Digital Equipment AB
SPR 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

106

DIGITAL SOFTWARE LICENSING

mamaamn
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. DIGITAL
has a license agreement for source software and
object software. Since DIGITAL software programs
are made available prlmarlly 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 OEM's customer the same
license rights and responsibilities as a license
agreement made directly with DIGITAL.

How DIGITAL Licenses Software

The Iicense 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, whicn 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.

107

Purchasing the License for the Software Product
A license must be obtained for each CPU on which
the licensed software wlll 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 purchased
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.

'
t

108

(

DIGITAL EQUIPMENT COMPUTER USERS SOCIETY
BENEFITS OF BELONGING

(

DECUS provides an environment where users of
Digital Equipment Corporation products can share
information with other users and with DIG IT AL.
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., DECUS 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:

Symposia

The Digital Equipment Computer Users Society
(DECUS) is one of the largest and most respected
users groups in the computer industry today. Membership in DECUS, which is free and voluntary, provides the individual user with information and services not found anywhere else.

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.

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. DIGITAL 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 publishes Special Interest Groups' newsletters that provide information pertaining to specific DIGITAL
products.
Program Library
The DECUS 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.

109

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 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 Canada
100 Herzberg Road
P.O. Box 13000
Kanata, Ontario K2K 2A6
Canada
Phone: (613) 592-5111, ext. 2115

DECUS GIC
100 Nagog Park AK01-1/B11
Acton, Massachusetts 01720
U.S.A.
Phone: (617) 264-6561

[g
DECUS

110

November 1985

C,
"

(}

digital equipment corporation

()
Printed in U.S.A.