8005_AD-C740C-B2_rtSwDisp.pdf

8005_AD-C740C-B2_rtSwDisp.pdf
RT-11
May 1980
AD-C740C-B2
THE
SOFTWARE
DISPATCH
dligliltiall
RT-11 SOFTWARE DISPATCH
Published by
Corporate Administrative Systems Group, Software Services
Digital Equipment Corporation
P.O. Box F
Maynard, MA 01754
The RT-11 Software Dispatch complements the RT-11 Software Dispatch Review. New and revised
Software Product Descriptions, programming notes, software problems and solutions, and
documentation corrections are published here. Much of the material is developed from Software
Performance Report (SPR) answers significant to the general audience and is printed here to
supplement the maintenance notebook (established by the Software Dispatch Review).
PRODUCTS SUPPORTED in the RT-11 SOFTWARE DISPATCH
APL-11 V1 FORTRAN/RT-11 Extensions V2.1 PLOT 11/RT-11 V1.1
BASIC-11/RT-11 V2 FORTRAN IV/RT-11 V2, v2.1 RT-11 V3B, RT-11 V4
BASIC/RT Extensions V1 GAMMA-11 F/B V2C, V3 RT-11 (CTS-300) LSI-11
CTS-300 V5 Lab Applications-11 LIBRARY V3 2780 V2
DECnet/RT V1, V1.1 LSP-11 V1 RT-11/2780
FOCAL/RT-11 V1B MSB11 V1 (CTS-300/2780) V2
FORTRAN Graphics MSB/FORTRAN IV Vi SSP-11/RT-11 V1.1
Package V1.1 MU BASIC-11/RT-11 V2
DISTRIBUTION
The RT-11 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 mailing label from
the most recently received publication.
Software binary and sources are provided under licenses only. The standard Terms and
Conditions, OEM Agreement, and/or Quantity Discount Agreement contain the licenses for all
binaries other than DECsystem-10.
Eleanor F. Hunter, Editor
Ann Owens, Associate Editor
Copyright = 1980 Digital Equipment Corporation
The material is this document is for information purposes only and is
subject to change without notice. Digital Equipment Corporation assumes
no responsibility for any errors which may appear in this document.
Comments on the contents of this publication should be directed to your
local DIGITAL Field Office.
TRADEMARKS of DIGITAL EQUIPMENT CORPORATION
Maynard, Massachusetts
DEC DECwriter PDT
DECUS DIBOL RSTS
DIGITAL LOGO EDUsystem RSX
DECnet IAS UNIBUS
DECsystem-10 MASSBUS VAX
DECSYSTEM-20 PDP VMS
VT
34-4/80
RT-11 Software Dispatch, May 1980
SEQ. NO. PAGE
SPR USER LETTER 1
CTS-398 VO5
MERGING ISAM FILES 92 M 3
RT-11 [email protected]
MISCELLANEOUS |
SYSGEN FOR TU58 SUPPORT 99 F 5
DEVICE TIME-OUT SUPPORT IN SYSGEN 18 F 7
MONITOR
CORRECTIONS TO MULTI-TERMINAL SUPPORT 34 M 9
SOURCE
MULTI-CONTROLLER DY HANDLER PROBLEM 15 M 13
UTILITIES
EDITING FILES ON WRITE-LOCKED DEVICES 30 M 15
BAD BLOCK SCAN FOR LARGE DEVICES 31 M 17
RT-11 SOFTWARE DISPATCH CUMULATIVE INDEX 19
SOFTWARE PRODUCT DESCRIPTIONS (SPDs) 31
DIGITAL EQUIPMENT COMPUTER USERS SOCIETY (DECUS) 39
SPR USER LETTER
Submitted by Sheila Hatcheil, 8/11 Administration
The Dispatch SPR User Letter has been revised to reflect the new SPR form which is now
available. These forms can be obtained from your local DIGITAL Office or SPR Center, or by
requesting them from SPR Administration.
How to Make the Best Use of the SPR Form
What We Can Do for You:
1.
Blank SPR forms are available upon request in the desired quantities through the SPR
Administration (P.O. Box F) and your local office/SPR Center.
Copies of the SPR acknowledgement and answer are sent to the appropriate DIGITAL
Office/SPR Center for their information.
STATUS FOR SUBMITTED SPRs IS PROVIDED UPON REQUEST.
SPRs marked PROBLEM/ERROR will have a response for DIGITAL SUPPORTED
products. These SPRs should refer to suspected deficiencies in the software.
SPRs marked SUGGESTION are forwarded to the pertinent software group for informa-
tion purposes, and are responded to at their discretion.
What Your Can Do for Us:
1.
Fill out the form completely either by typing or printing clearly. PLEASE INCLUDE
YOUR SOFTWARE SERVICE CUSTOMER NUMBER IN THE ADDRESS BOX.
Limit only one problem per SPR form. Several problems on an SPR can lengthen the
turnaround time.
WHENEVER POSSIBLE, SUBMIT AN SPRWITHATTACHMENTS, SUCH AS MACHINE
READABLE DATA, DETAILED INSTRUCTIONS ON HOW TO REPRODUCE THE
PROBLEM, PROGRAM AND/OR DATA FILES, LISTINGS, AND CONSOLE LOG.
It would be helpful to all concerned if problems with patches are reported as soon as
possible.
For security SPRs, it is imperative that the DO NOT PUBLISH box be marked.
It would be helpful if tapes submitted with SPRs are labeled (track and density), and have
a directory attached.
Complete the questionnaire that is supplied with each SPR answer. Your feedback is
essential in monitoring the quality of our responses.
SPRs should not be used for problems concerning software policy, software distribution,
or hardware. The local office should be contacted in these cases.
RT-11 Software Dispatch, May 1980
CTS-399 VO5 Seg 2 M
SORTM VO5-00A
(PATCH 24) 1 of 2
MERGING ISAM FILES (LG)
If you create a SORT control file to merge two (or more) ISAM
files, when it is compiled with SORTM, you will receive errors
reporting three undefined names: FLBLI, IDEV, and FLBXI. You
should not receive these errors.
Patch 20 corrects this problem and changes the version number of
SORTM to VOS-00B.
All dollar sign characters appearing in the following edit of
SORTM represent the typing of the altmode key.
Please note that when sorting or merging ISAM files that the
resulting output file is NOT an ISAM file but a sequential file.
If an ISAM file is desired, you must then reCREATE it as such
with ISMUTL.
RT-11 Software Dispatch, May 1980
CTS-398 VO5
SORTM VB5-09A
(PATCH 29)
‚RENAME SORTM.,DEBL SORTM.: OLD
, EDIT/QUISORTM.,IBL SORTM.OLD
XFVOS-O0A$VE$
SORTM. DBL V05-00A
Led
»
X-CB$U$*
ъ
,
*XF + COFYR
+
у
SORTM. DRL VO5-00B
IGHT$V$SL $$
y COPYRIGHT
5 RRR KRONA KKK RRR KK KKK
RECORD FLELI»X
+ OUTFUT DEVICE
INPUT DEVICE
$ INFUT FILE NAME
¿QVERLAY TO MANIPULATE RECORD FIELDS
SFILE LABEL IN
$WORKFILE TMP EXTENSION
$ KKK KKK A KKK KKK KK KAKKK ARK R AK KR AKER AAORR KKK KKK KK
RECORD FLELI»X
RECORD
DDEV y A4
X2AVS$
$
XI RECORT
IDEV» Ad
IFILEr Al1Q
FLBXIs A10
ТЕХТ, ña
$$
X-8A%11L%%
COPYRIGHT
RECORD
IDEV» ña
IFILEy ñio
FLEXI» ñÍIO
TEXT, A4
;
RECORD
ODEV » АЗ
XF XSS5A » SVAUS #
X55A»
XI
++
X-2LL$%
ХОЗ,
XEX$$
INCR
CALL
OPEN
INCR
OFEN
CALL
# INFUT DEVICE
y INFUT FILE NAME
$ OVERLAY TO MANIPULATE RECORD FIELDS
FILE LABEL IN
s WORKFILE +TMP EXTENSION
$ OUTPUT DEVICE
I
GETFCG
CIyIrWkKNCI)>)
I
CIvy IrWkKNCI)>)
GETFCG
Seg 2 M
2 of 2
RT-11 Software Dispatch, May 1980
RT-11 VO3B-00 Seq 9 F
MISCELLANEOUS |
SYSGEN.CND [email protected] 1 of 2
SYSGEN FOR TU58 SUPPORT (SPR 11-28615 JM)
Ir
The DD.SYS build commands are omitted from DEVBLD.COM when TU58 support 1s
requested during SYSGEN.
The following patch should only be applied to the SYSGEN.CND file supplied
in the QJ813-AG, [email protected], [email protected], and QJB13-TY kits.
Patch to SYSGEN.CND
.R EDIT <RET>
*EBSYSGEN.CNDL191]<ESC>RFSYCND+DL<ESC>-2AL<ESC><ESC>
#IF DL
*I #IF DD <RET>
#1Е BLSJFB <RET>
MACRO/OBJ:BIN:DD SRC: (SYCND+DD) <RET>
LINK/EXE:BIN:DD.SYG BIN:DD <RET>
#IFN OBJ <RET>
DELETE/NOQ BIN:DD. OBJ <RET>
#ENDC OBJ <RET>
#ENDC BLSJFB <RET>
¡IF XM <RET>
MACRO/OBJ:BIN:DDX SRC: (XM+SYCND+DD) <RET>
LINK/EXE:DDX.SYG BIN:DDX <RET>
#IFN OBJ <RET>
DELETE/NOQ BIN:DDX.OBJ <RET>
#ENDC OBJ <RET>
#ENDC XM <RET>
#ENDC DD <RET>
<ESC>-17LL<ESC><ESC>
#ENDC RK
#IF DD
AIF BLSJFB
MACRO/OBJ:BIN:DD SRC: (SYCND+DD)
LINK/EXE:BIN:DD.SYG BIN:DD
#IFN OBJ
DELETE/NOQ BIN:DD. OBJ
#ENDC OBJ
#ENDC BLS JFB
¡IF XM
MACRO/OBJ:BIN:DDX SRC: (XM+SYCND+DD)
LINK/EXE:DDX.SYG BIN:DDX
4IFN OBJ
RT-11 Software Dispatch, May 1986
RT-11 VO3B-00 Seq 9 F
MISCELLANEOUS
SYSGEN.CND [email protected] 2 of 2
DELETE/NOQ BIN:DDX.OBJ
#ENDC OBJ
#ENDC XM
#ENDC DD
#IF DL
*EX<ESC><ESC>
There is no resultant version change after installing this patch.
RT-11 Software Dispatch, May 1986
RT-11 VO3B-00 Seq 10 F
MISCELLANEOUS
SYSGEN.CND [email protected] 1 of 1
DEVICE TIME-OUT SUPPORT IN SYSGEN (SPR 11-28393 JM)
The device time-out support question was not included when generating only
an FB or XM monitor. The following patch corrects this problem.
Patch to SYSGEN.CND [email protected]
.R EDIT <RET>
*EBSYSGEN.CND[ 181 JKESC>RVKESC><ESC>
; SYSGEN.CND [email protected] RT-11 SYSGEN SCRIPT FILE
#2GC<ESC>- DID<ESC>V<ESC><ESC>
SYSGEN.CND [email protected] RT-11 SYSGEN SCRIPT FILE
iG. 11C<ESC>-DID<ESC>V<XESC><ESC>
#PRINT RT-11 SYSTEM GENERATION PROGRAM [email protected]
* OFTIMESR<ESC>AL<ESC><ESC>
#IF LONG
*T #ENDC Sd <RET>
#IFN BLSJ <RET>
<ESC>-3LL<ESC><ESC>
#ENDC TIME$R
#ENDC Sd
#IFN BLSJ
#IF LONG
* 3GDEVTO<ESC>AL<ESC><ESC>
AIF LONG
#1 #ENDC BLSJ <RET>
ÿ#IF SJ <RET>
<ESC>-3LL<ESC><ESC>
#ENDC DEVTO
#ENDC BLSJ
AIF Sd
IF LONG
*EX<ESC><ESC>
The resultant version after applying this patch will be SYSGEN.CND [email protected]
RT-11 Software Dispatch, May 198%
RT-11 [email protected] Seq 34 M
MONITOR
FB (S)V83B-880 lof"
XM (S)VO3B-GOU
CORRECTIONS TO MULTI-TERMINAL SUPPORT (JM)
The following multi-terminal problems are corrected after installing the
patches below:
1. .MTSET does not set the terminal characteristics in the JSW and
terminal status word for a job.
2. "SET TT CONSOLE =n" does not wait for all output to complete
before switching consoles.
3. Automatic carriage return/linefeed does not work properly when the
carriage width is exceeded.
Ц. "SET TT NOPAGE" does not ignore CTRL/S and CTRL/Q.
5. The monitor will always start with 1 stopbit unless the speed is
defined at 118 baud.
Patch to KMOVLY.MAC:
.R EDIT <RET>
*EBKMOVLY.MAC[165 J<ESC>RV<XESC><ESC>
> KMOVLY EDIT LEVEL 1
*G1<ESC>=C2<ESC>V<ESC><ESC>
:KMOVLY EDIT LEVEL 2
*FSET55$: <ESC>GOSPL<ESC>-AL<ESC><ESC>
. IF NE BF
#115$: <RET>
<ESC>AI TSTB I.OCTR-I.CNSL(R2) <RET>
BNE 15$ <RET>
<ESC>2A<ESC>I TSTB T.OCTR(R3) <RET>
BNE 15$ <RET>
<ESC>-9LL<ESC><ESC>
MOV @R2,R3
15%:
‚IF NE BF
TSTB I.OCTR-I.CNSL(R2)
BNE 15$
OSPL 7
. IFF
TSTB T.OCTR(R3)
BNE 15$
OINTOF €6$
*EX<ESC><ESC>
RT-11 Software Dispatch, May 198%
RT-11 VO3B-090
MONITOR
FB (5)V93B-780
XM (S)[email protected]@pu
Patch to BSTRAP.MAC:
.R EDIT <RET>
*EBBSTRAP.MAC[69]<ESC>RV<ESC><ESC>
;BSTRAP EDIT LEVEL 25
*G5<ESC>=C6<ESC>VKESC><ESC>
;BSTRAP EDIT LEVEL 26
*FBSTRNG: <ESC>G 'O"<ESC>-JV<ESC><ESC>
e ASCIZ "FB (S)[email protected]'...'0O"
* -DIP<ESC>VXESC><ESC>
e ASCIZ "FB (S)[email protected]@g'...'p"
*G 'U"<ESC>-JV<ESC><ESC>
.ASCIZ "XM (S)VO3B-9'...'U"
*-DIV<ESC>V<ESC><ESC>
-ASCIZ "XM (S)[email protected]'...'y"
*F PDZOINT: <ESC>G55$: <ESC>2AL<ESC><ESC>
CMP R1,#1000
*3<I ¿ <ESC>A<ESC>><ESC>GE $N<ESC >1+DZST $P <ESC>-5LL<ESC><ESC>
BIC 4 C<LINSP$>,R1
CMP R1, 1000
; BNE 57%
; BIS HUB, RI
57$: BISB T.PUN(R®),R1
BIS #DZRCO$+DZLE$N+DZST$P,R1
*EX<ESC><ESC>
Patch to MTTINT.MAC:
.R EDIT <RET>
*EBMTTINT.MAC[U3]<ESC>RV<ESC><ESC>
;MTTINT EDIT LEVEL 2
*G2<ESC>=C3<ESC>V<ESC><ESC>
;MITINT EDIT LEVEL 3
*FCTRL.S:<ESC>V<ESC><ESC>
CTRL.S: BIS #PAGE$,T.STAT(R3)
*SKA<ESC><ESC>
#1 BPL TTINCC <RET>
<ESC><ESC>
*UI RTS PC <RET>
<ESC><ESC>
FUK<ESC>-5LL<ESC><ESC>
. ENDC
CTRL.S: TSTB (R3)
10
Seq 34 M
2 of 4
RT-11 Software Dispatch, Мау 1980
RT-11 [email protected]@[email protected] Seq 34 M
MONITCR
FB (S)VO03B-070
iM (S)VB3B-99U
Lo
о
=
=
BPL TTINCC
BIS #PAGE$,T.STAT(R3)
RTS PC
TTIDSP: TST (SP)+
*FDZOINT: <ESC>GOUTCHR<ESC>2AV<ESC><ESC>
MOVB T.OCHR(R3), (SP)
*I MOVB [email protected],8SP <RET>
; <ESC>-2LL<ESC><ESC>
BCS 15$
MO VB RO,@SP
; MOVB T.OCHR(R3),(SP)
*EX<ESC><ESC>
Patch to MTTEMT.MAC:
.R EDIT <RET>
*EBMTTEMT.MAC[22]<ESC>RVKESC><ESC>
;MTTEMT EDIT LEVEL 8
*GO<ESC>z=C1<ESC>V<ESC><ESC>
;MTTEMT EDIT LEVEL 1
*F$TTST:<ESC>3GMOVKESC>QALKESC><ESC>
MOV (RE)+, (R1)+
*I TST T.STAT(R3) <RET>
BPL 308 <RET>
BIC #127617,R2 <RET>
MOV @#JSW,-(SP) <RET>
BIC #50160 ,65Р <ВЕТ>
BIS R2,6SP <RET>
MOV (SP)+,@#JSW <RET>
11
RT-11 Software Dispatch, May 1980
RT-11 VO3B-099
MONITOR
FB (S5)V93B-070
XM (S)V93B-99U
30$: <RET>
<ESC>GDZ 11$N<ESC>GAL<ESC><ESC>
‚IF NE DZ11$N
*T TST T.STAT(R3) <RET>
BPL 17% <RET>
JSR PC, TTRSET <RET>
UB$: <RET>
<ESC>-16LI.<ESC><ESC>
TST T.STAT(R3)
BPL 30%
BIC #127617,R2
MOV E#JSW,-(SP)
BIC 157160,0SP
BIS R2,@SP
MOV (SP)+,0#JSW
30%:
MOV (RO)+,(R1)+
MOV ([email protected])+,(R1)+
MOV (RA), (RI)
TST T. STAT(R3)
BPL 40$
JSR PC, TTRSET
410$:
‚IF NE DZ 11$N
*EX<ESC><ESC>
After installing the above patches, re-assembling,
and
re-linking
Seg 34 M
4 of 4
the
resultant versions will be RT-11FB (S)[email protected]@@P and RT-11XM (S)[email protected]@@V.
12
RT-11 Software Dispatch, May 1980
RT-11 VO3B-90 Seq 15 M
SOURCE
DY Handler 1 of 1
MULTI-CONTROLLER DY HANDLER PROBLEM (SPR 11-26725 LCP)
Device errors may occur when single and double density media are used
together on a dual RX211 or RXV211 system (1 drives). The following
mandatory source patch will correct the problem in subsequently SYSGENed
monitors:
.R EDIT <RET>
*EBDY .MAC<ESC>RV<ESC><ESC>
.DY EDIT LEVEL 3
*G3<ESC>=C4 <ESC>V<ESC><ESC>
:DY EDIT LEVEL 4
*FDENOFF : <ESC>G42 <ESC>BAV<ESC><ESC>
MOV #2, DENOFF
#SI: <ESC>V<ESC><ESC>
; MOV #2,DENOFF
*GBEQ<ESC>1AU<ESC>-2A2L<ESC><ESC>
BEQ RXCDF
MOV #2 , DENOFF
*EX<ESC><ESC>
*x# NOTE ***
There is no binary patch for this problem as dual [email protected] controller support
is available only by performing a SYSGEN.
13
RT-11 Software Dispatch,
RT-11 [email protected]@
UTILITIES
EDIT VBH. 024
EDITING FILES ON WRITE-LCCKED DEVICES (SPR 11-25180 MG)
PROBLEM:
When the EB command is used to edit a file which resides on a device
?EDIT-F-System 1/0 error is returned.
while still in EDIT, the device is then write-enabled and
again for the same file, the message ?EDIT-F-File not found will be
'edit-in-progress'
second EB command found the flag set, so the
previous command was completed, renaming the file to .BAK.
is write-locked, the
issued
returned. This is due to the
after certain errors. The
May 1980
message
(2
o
LA)
=
patch corrects the problem.
applying
not being
this one. User responses are
SOLUTION:
The following mandatory
patches must be applied before
underlined.)
Patch to EDIT [email protected]@2A:
.R PATCH<RET>
FILE NAME--
*EDIT.SAV/C<RET>
*2362;9R
*ÿ,16432/ 185767 167<LF>
@, 16434 / 157832 161474<LF>
2,16436/ 100491 240<LF>
6, 16440/ 104413 240<LF>
BD, 16442/ 194417 Z40<RET>
*D,132/ 126727 105067<LF>
9,134/ 175332 227<LF>
B,136/ 177775 105737<LF>
0,110/ 1004 52<LF>
g,142/ 12700 100401<LF>
D, 144/ 1413 1944 13<LF>
0,146/ 184374 18A1T7<RET>
*P,16678/ 161248 161256<RET>
* 7, 1580/ 194417 195867<LF>
0,152/ 12700 211<LF>
0,154/ 1413 123727<LF>
D,156/ 184374 52<LF>
g,[email protected]/ 184415 177775<LF>
g,162/ PD 1004<LF>
15
SPR 11-25188/RT261
RT-11 Software Dispatch, Мау 1980
RT-11 VO3B-09 Seq 30 M
UTILITIES
EDIT VOU.B2A 2 of 2
p,164/ © 12700<LF>
9, 166/ B 1413<LF>
D,170/ D 1909374<LF>
0,172/ © 104417<LF>
92,1747 © 12/0G<LF>
0,1760/ © 1413<LF>
p,200/ $ 184374<LF>
B,202/ BY 1944 15<RET>
*7, 136608 191 192<RET>
*E
Checksum? 71351<RET>
The resultant version is EDIT [email protected]@2B.
16
RT-11 Software Dispatch, May 1589
RT-11 VO3B-00 Seq 31
UTILITIES
DUP.SAV VO3.BUE 1 of 1
BAD BLOCK SCAN FOR LARGE DEVICES (SPR 11-25489 DF)
DUP was not printing file names for bad block numbers above octal 77777.
This was caused by using a BMI instruction rather than a BLO.
The following patch to DUP corrects this problem.
.R PATCH <RET>
FILE NAME--
*DUP.SAV/C <RET>
¥11533\ 185 106 <RET>
EU219/ 190772 183772 <RET>
*E
Checksum? 36867 <RET>
The resultant version will be DUP.SAV VZ3.24F.
17
M
RT-11 SOFTWARE DISPATCH
CUMULATIVE INDEX
MAY 1980
This is a complete listing of all articles for current versions of RT-11 and related products. In the
case of subordinate software, missing sequence numbers may pertain to problems unique to interaction
with previous versions of the same product or other major operating systems,
IMPORTANT!
Unassigned articles are indicated: UNASSIGNED.
Flags are currently being installed for all articles. The flags and definitions are as follows:
M = Mandatory Patch. These patches correct errors in the software product. All users are required to
apply these patches to maintain consistent "user level" unless the accompanying article specifies
otherwise.
F = Optional Feature Patch. These patches extend or configure functionality into the product. These
functions will be treated as a supported part of the product for the duration of the current
release. and will be incorporated with any future release, unless otherwise stated.
R = Restriction. These articles discuss areas that will not be patched in the current release because
they require major modification or because they are not consistent with the design of the product.
Restrictions, except those described as permanent, are reviewed and modified when possible as part
of the normal release cycle.
N = NOTE. These articles provide explanatory information that supplements the manual set and provide
more detailed information about a program or package. They also provide procedural information to
make it easier to use a program or package.
Component Sequence Mon/Yr
APL-11 V1
APL .SAV PROGRAM PATCHES
ERRONEOUS "DEFINITION ERROR" DURING FUNCTION EDITING 01 M Nov 77
LOSS OF LOWER-CASE ON RE-ENTRY TO APL-11 : 02 M Nov 77
APL WORKSPACE 03 R Nov 77
"SYSTEM ERROR"S GENERATED BY NULL LINE ELEMENTS 04 Dec 77
INTERNAL MEMORY ALLOCATION PROBLEMS 05 M Dec 77
ERROR FOR SCALAR RESULT OF DECODE OR INNER PRODUCT OPERATION 06 M Feb 78
SYSTEM ERROR ON PARAMETER RETURN 07 M May 78
BASIC-11/RT-11 V2
RESEQUENCE PRODUCES AN INCORRECT PROGRAM UNDER CERTAIN CONDITIONS 01 M Aug 78
PRINT USING 02 M Jun 78
MAX SIZE OF LINE ENTERED TO BASIC-11 03 M Jun 78
REM STATEMENT CONTAINING LEFT PARENTHESIS CAUSES SUBSEQUENT SPACES
AND PERIODS TO BE REMOVED O4 R Jun 78
RUN (NH) COMMAND MAY GIVE AN ERROR MESSAGE 05 M Jul 78
TERMINAL MAY HANG CU 06 M Jul 78
DATA FILES 07 M Jul 78
SAVE DEV: AND REPLACE DEV: 08 M Jul 78
SINGLE PRECISION HANG AND NUMERIC CONVERSION PROBLEM (PATCH F) 09 M Aug 78
CONVERSION PROGRAM 10 M sep 78
OVERLAYING WHILE IN A SUBROUTINE 11 R Nov 78
OPERATION OF CTRLC, AND RCTRLC AND SYS (6) FUNCTIONS AND THE
CTRL/C COMMAND 12 N Nov 78
BASTC-11/RT-11 V2 CONVERSION PROGRAM PATCH 1 13 M Feb 79
OPERATION OF OLD, RUN, CHAIN AND OVERLAY WHEN THE SPECIFIED FILE
IS NOT FOUND 14 N Feb 79
CREATING AND ACCESSING VIRTUAL ARRAY FILES 15 N Feb 79
REPUBLICATION OF PATCHES 16 N Feb 79
PRINT USING - PATCH A 17 M Feb 79
RESEQ - PATCH B 18 M Feb 79
EDITING A DIM #n STATEMENT - PATCH C 19 M Feb 79
DOUBLE PRECISION HANG - PATCH D 20 M Feb 79
SAVE dev: AND REPLACE dev: —- PATCH E | 21 M Feb 79
SINGLE PRECISION HANG AND NUMERIC CONVERSION PROBLEM - PATCH F 22 M Feb 79
SAVE .XXX € UNSAVE .XXX - PATCH С 23 M Feb 79
19
Component
NEW — PATCH H
STORAGE OF THE NULL CHARACTER IN STRING VARIABLES AND VIRTUAL
STRING ARRAYS
USE OF COMPILE COMMAND
RESEQ - PATCH I
LISTNH /OLD - PATCH J
SYS(1) — PATCH K
CALL - PATCH L
DOUBLE PRECISION INTEGER VARIABLES - PATCH M
FILESIZE 0 - PATCH N
INTEGERS IN DOUBLE PRECISION BASIC-11
REM STATEMENTS ON MULTI-STATEMENT LINES - PATCH O
STRING MANIPULATION IN ASSEMBLY LANGUAGE ROUTINES
MAXIMUM ARRAY SUBSCRIPT SIZE |
BASIC/RT-11 EXTENSIONS V1
"IPK" SUBROUTINE
SAMPLING A/D CHANNEL NO. 15
SAMPLING AR11
"CLRD" AND "PUTD" ROUTINES
"SETR" AND "WAIT" COMBINATION MAY FAIL
BASIC/RT-11 EXTENSION BUILD PROCEDURE RESTRICTION
CTS-300 V5
DECFORM
TWO PROBLEMS WITH FOCOMP
DIBOL
TWO PROBLEMS: FILE CORRUPTION POSSIBILITY AND REPETITIVE I/O ERRORS
OPENING NON-STANDARD HANDLERS
ANOTHER FILE CORRUPTION POSSIBILITY
TWO PROBLEMS: OPENING O LENGTH FILE IN SUD AND OPENING LP IN I MODE
LINE PRINTER PROBLEM AND PROBLEM WITH LARGE ISAM FILE
1/0 ERRORS AND PROBLEM WITH FMAC SUBROUTINE
ISAM FILE CORRUPTION
SHUFFLE CAUSES TRAP TO 4
MISLEADING ERROR MESSAGES
ERRONEOUS 1/0 ERROR
TWO PROBLEMS WITH MULTI-VOLUME FILES
INCORRECT ERROR ON WRITING DUPLICATE FILE TO MAGTAPE
ACCEPT CAUSES ERRORS
1-0 ERROR ON ISAM STORE/DELETE
DICOMP
DICOMP DISLIKES SOME COMMENTS
ISMUTL
REORG PROBLEMS DUE TO INSUFFICIENT SPACE ON DEVICE
REDUCE
HOW TO REDUCE PAINLESSLY
A REDUCING PROBLEM
SORTM
MERGE DOES NOT ACCEPT EMPTY FILES
MERGING ISAM FILES
CTS-300 RDCP (2780/3780) V1.0
SENDING OF TRANSPARENT DATA AND TRANSLATION OF DATA AFTER
SENDING A TRANSPARENT FILE
SEND A TRANSPARENT FILE AFTER RECEIVING AN ASCII DATA FILE
AN ACK 15 RECEIVED WHEN ENQ HAS ALREADY BEEN SENT
MISCELLANEOUS ERRORS
RDCP11 LOOP MAY OCCUR
ASCII TRANSMISSION OF A FILE
20
Sequence
01
02
03
04
05
06
01
01
02
03
04
05
06
07
08
09
10
11
12
13
14
01
01
01
01
02
01
03
04
05
06
TTI ITI IED го Жо ов © “RR EZ со оо z 2 Бо = =
==
TEI охох ож ол
Feb
Feb
Feb
Mar
Mar
Mar
Mar
May
May
Jul
Jul
Aug
Aug
Aug
Aug
Sep
Nov
Apr
Mar
May
Mar
Apr
Apr
Jun
Jun
Jun
Jun
Jul
Aug
Aug
Oct
Dec
Mar
Mar
Sep
Feb
Aug
Dec
Apr
May
Jul
Oct
Oct
Aug
Oct
Oct
Mon/Yr
79
79
79
79
79
79
79
79
79
79
79
79
79
77
77
77
77
78
79
79
79
79
79
79
79
79
79
79
79
79
79
79
80
80
79
80
79
79
79
80
79
79
79
79
79
79
Component Sequence Mon/Yr
DECnet-RT V1
DAP |
DAP ROUTINES DO NOT ARBITRATE DAP SEGMENT SIZE PROPERLY 07 M Jan 79
NOTES ON CHANGES TO DAP INTERFACE 09 N Feb 79
CORRECT BUFFER POINTER ERROR 16.11 M May 79
DAP ATTEMPTS TO SEND A MESSAGE TOO LONG 17.7 M Sep 79
DDCMP
DDCMP LINE COUNTERS OVERFLOW TO ZERO G1 © Jul 78
DMC
DMC LINE COUNTERS OVERFLOW TO ZERO 010 Jul 78
DOCUMENTATION
USER'S GUIDE DOCUMENTATION ERRORS 2.1 N Aug 79
FAL
CORRECT FAL PROCESSING OF END OF STREAM MESSAGE 01 M Jan 79
FAL INCORRECTLY ALLOCATES DISC SPACE FOR FILES 02 M Feb 79
FAL INCORRECTLY HANDLES REMOTE FILE REQUESTS 04 M Feb 79
TIMING DEPENDENCY IN RT TO RSTS FILE TRANSFERS 17.5 M Jul 79
MRS FIELD NOT DEFAULTED PROPERLY 17.6 M Jul 79
FORTRAN INTERFACE
DIFFERENCES IN RT AND RSX FORTRAN INTERFACE IMPLEMENTATIONS 01 N Jul 78
USE OF THREADED AND INLINE FORTRAN COMPILER OPTIONS 04 R Jan 79
FORTRAN REMOTE OPEN FOR WRITE MODIFIES FILE ATTRIBUTES 05 N Jan 79
MODEM CONTROL
SUPPORT OF ASYNCHRONOUS HALF DUPLEX MODEMS 01 R Jul 78
NFARS
DAP ROUTINES CHANGE MODE DURING FILE TRANSFER 02 M Feb 79
CHECK FOR BLOCK MODE TRANSFER 03 M Feb 79
DAP DEFAULTS DO NOT ALLOW RECORDS TO SPAN BLOCKS 06 0 Jan 79
ASCII FILE ACCESS TO VAX/RSX SYSTEMS | | 08 M | Feb 79
INVALID FILE TYPE SENT TO VAX TN ASCIT TRANSFER 10 M Mar 79
NSP
PROTOCOL VIOLATION IN NODE INITIALIZATION 01 M Jan 79
NFT
NFT ASCII FILE TRANSFER TO VAX/RSX SYSTEMS 03 M Feb 79
LOGICAL BLOCK NUMBERS NOW START AT ONE 17.5 M May 79
FEP-11, FORTRAN ENHANCEMENT PACKAGE
(ALSO PERTAINS TO: RT-11/FORTRAN UPGRADE PACKAGE FOR MINO)
FEP-11 INITIAL PROBLEMS, SOLUTIONS AND HINTS 01 M May 79
PROBLEMS WITH IEEE-BUS SUBROUTINES 02 M | Feb 80
FMS-11 V1
CONSOLE TERMINAL SPECIAL MODE BIT CLEARED 01 M Jun 79
INCORRECT MCDEMO FILE TYPES 02 0 Jun 79
TSKINI INPUT BUFFER TOO SMALL 03 M Jun 79
ARTS ERROR MESSAGES LACK '?' 04 M Jun 79
HANDLER FETCH CORRUPTS FORM FILE ID 05 M Jul 79
ZERO-FILLED FIELD VALIDATION PROBLEM 06 M Jul 79
FILED VIDEO ATTRIBUTES PROBLEM 07 M Jul 79
FRED ERROR MESSAGES LACK'?' 08 M Jul 79
ERROR IN SCROLL FORWARD/BACKWARD CODE 09 M Jul 79
ERROR IN EXIT SCROLLED AREA FORWARD CODE 10 M Jul 79
ANNOUNCING FMS-11 FORMS MANAGEMENT SYSTEM 11 F Nov 79
FOCAL/RT-11 V1B
FOR COMMAND WITHOUT AN ARGUMENT 01 M Oct 75
OPERATE COMMAND CAUSES ERROR — 04 M Aug 76
FCLK ROUTINE GIVES INCORRECT TIME 21 05 9 Aug 76
Component Sequence Mon/Yr
"LIBRARY ASK" COMMAND 06 0 Feb 77
"/7" SWITCH 07 M Aug 77
@START NOT WORKING WHEN DOWN-LINE LOADING 08 M Mar 78
LIBRARIES FROM FOCAL SOURCE DISK MUST BE REFORMATTED 09 N Aug 78
CLOCK PROBLEM FOR PAPER TAPE (STAND-ALONE) FOCAL USERS 10 M Nov 78
FORTRAN GRAPHICS PACKAGE, V1.1
DECGRAPHIC
NMBR SUBROUTINE IN DECgraphic 01 R JAN 79
FORTRAN/RT-11 EXTENSIONS V1
RUNNING PROGRAM WITH "SETR" 01 M‘ Oct 78
IBEF NOT PROPERLY DECREMENTED 02 R Oct 78
LPS DEVICE CONFLICT CAUSED BY CALL SETR AFTER CALL RTS 03 R Oct 78
IADC AFTER RTS DOES NOT WORK 04 M Oct 78
SUBROUTINE NAMING CONFLICT 05 N Oct 78
PLOT55 DESCRIPTION 06 N Oct 78
ILLEGAL MEMORY REFERENCE ERROR 07 M Oct 78
DEVICE CONFLICT ERROR 08 R Oct 78
TWO PROBLEMS WITH THE RT-11/FORTRAN GRAPHICS EXTENSIONS 09 M Oct 78
FORTRAN/RT-11 EXTENSIONS V1B
FORTRAN CRASHES AFTER RUNNING PROGRAM WITH "SETR" 01 M Oct 78
TWO PROBLEMS WITH THE RT-11/FORTRAN GRAPHICS EXTENSIONS 02 M Oct 78
NEGATIVE INTENSITY 03 N Nov 78
PROGRAM TERMINATION ERROR USING RT-11 F/B 04 R Apr 79
FORTRAN/RT-11 EXTENSIONS V2.1
FORTRAN CRASHES AFTER RUNNING PROGRAM WITH "SETR" 01 M Mar 79
TWO PROBLEMS WITH THE RT-11/FORTRAN GRAPHICS EXTENSIONS 02 M Mar 79
NEGATIVE INTENSITY 03 N Mar 79
FORTRAN IV/RT-11 V2
COMPILER
DISPOSE = 'KEEP' OPTION 01 R Jan 79
CRASH DUMPS 02 N Jan 79
SYNTAX ERRORS IN SOURCE PROGRAM MAY CAUSE COMPILER TO ABORT 03 M Jan 79
SIMRT 04 M Jan 79
SIMRT CONTINUED 05 M Jan 79
KNOWN FORTRAN IV V2 BUGS 06 N Jan 79
USE OF THE FIND STATEMENT 07 M Jan 79
RAISING COMPLEX NUMBERS | 08 M Jan 79
EXTRA CHARACTERS MAY RESULT IN COMPILER TRAPPING 09 M Jan 79
TRANSMITTING ASCII DATA 10 R Jan 79
IN-LINE CODE 11 N Jan 79
ERRORS OCCUR WITH NO DO LOOP 12 M Jan 79
FORTRAN "ACCEPT" STATEMENT 13 R Jan 79
FORTRAN IV/RT-11 V2.1
FORTRAN IV V2.1 MAINTENANCE RELEASE 01 N Dec 78
PATCH 1 | 02 M Feb 79
PATCH 2 | 03 M Feb 79
PATCH 3 O4 M Feb 79
PATCH 4 05 M Sep 79
CARRIAGE CONTROL OPTION - PATCH 5 06 M May 79
OPEN FAILURE WITH TYPE="'OLD' - PATCH 6 07 M Sep 79
FORTRAN LIBRARY FUNCTION ERRTST - PATCH 7 08 M Aug 79
REGISTER ALLOCATION - PATCH 8 09 M sep 79
SMALLER EXECUTION-TIME PROGRAMS 10 N Jun 79
FORTRAN OTS - PATCH 9 11 M sep 79
1/0 FROM A FORTRAN COMPLETION ROUTINE - PATCH 10 12 M Aug 79
FORTRAN FAILS TO COMPILE DO-LOOPS - PATCH 11 13 M Aug 79
22
Component Sequence Mon/Yr
CALL CLOSE (FORTRAN LIBRARY SUBROUTINE) - PATCH 12 14 M Aug 79
UNFORMATTED BYTE I/O - PATCH 13 15 F Aug 79
LIST DIRECTED INPUT ERRORS - PATCH 14 16 M Aug 79
DISP='DELETE' OPTION - PATCH 15 17 M Aug 79
FORMATTED RECORD OUTPUT - PATCH 16 18 M Aug 79
COMMON SUBEXPRESSION OPTIMIZATION - PATCH 17 19 M Aug 79
CALL ASSIGN CARRIAGE CONTROL - PATCH 18 20 M Aug 79
NON-PLAS VIRTUAL ARRAY INITIALIZATION - PATCH 19 21 M Aug 79
BYTE COMPARISON AND COMMON SUBEXPRESSION OPTIMIZATION - PATCH 20 22 M Aug 79
DIRECT ACCESS READ - PATCH 21 23 M Aug 79
COMPLEX VARIABLE TO CONSTANT COMPARISON - PATCH 22 24 M Aug 79
GAMMA-11 F/B V2
DATA ANALYSIS PROGRAM 01 M Feb 79
STUDY PROGRAM DISPLAYS TOO MANY INDEX LINES PER PAGE 02 M Feb 77
BASIC AND FOCAL 03 M Feb 77
BACKGROUND PROGRAM CAN HANG THE FOREGROUND TERMINAL 04 M Feb 77
CNTL/C UNDER SINGLE JOB MONITOR 05 M Feb 77
CROSSHAIRS FAIL TO APPEAR IN SLICE 06 M Feb 77
UNDOCUMENTED PROGRAMS 07 N Mar 77
FORTRAN SUPPORT INCORRECTLY CONVERTS DATA AND TIME OF INQUISITION 08 M May 77
"REI" COMMAND TS INCORRECTLY 09 N Jun 77
GAMMA-11 F/B V2C
GATED LIST MODE IMAGES 01 0 Sep 78
TU16 SUPPORT 02 M Sep 78
PROBLEMS WITH PLAYBACK BUFFER COMMENTS AND FLOOD CORRECTIONS 03 M Oct 78
STATIC FOREGROUND ACQUISITION FAILS ON RK0O6 OR RLO1 SYSTEMS 04 M Oct 78
DYNAMIC CURVE CALCULATIONS MAY FAIL 05 M Dec 79
RK06, 7 AND RLO1 FOREGROUND ACQUISITIONS PROBLEMS 06 M Dec 78
PROBLEMS WITH FLOOD CORRECTIONS 07 M Dec 78
PROBLEMS WITH REGION OF INTEREST 08 M Dec 78
KW11-P REAL-TIME CLOCK INCORRECTLY INITIALIZED 09 M Dec 78
GAMMA-11 V2C NCV11 REAL-TIME CLOCK CAN BE DISABLED 10 M Dec 78
KW11-P REAL-TIME CLOCK RUNS TOO FAST DURING GSA STUDIES 11 M Dec 78
BUILDING AN RLO1 GAMMA-11 V2C SYSTEM 12 M Dec 78
PREDEFINED GATED LIST MODE STUDIES 13 M Dec 78
GATED LIST MODE DATA ACQUISITION SET-UP 14 M Dec 78
PROBLEMS WITH MAGTAPE DISTRIBUTION 15 N Dec 78
SUBROUTINE 'GMXG' GENERATES ILLEGAL ADDRESS MESSAGE 16 F Jul 79
FGAMMA/BGAMMA RACE CONDITION 17 M Feb 79
DELAYED START LIST MODE STUDIES 18 M Feb 79
FORMATTING GATED LIST MODE STUDIES 19 M Feb 79
SLICE PROBLEMS 20 M Feb 79
DOUBLE INTERPOLATION OF 64 X 64 MATRIX DATA 21 M Feb 79
GAMMA-11 AND RT-11 DATE ROLLOVER 22 M Feb 79
PROBLEMS WITH PATIENT MONITOR AND GSA ADMIN BLOCKS 23 M Feb 79
FOREGROUND GATED LIST MODE STUDIES FAIL 24 M Feb 79
NCV11 JOYSTICK AND LIST MODE PROBLEMS 25 M May 79
SYSTEM SUMMARY FOR RKO7 DISKS 26 0 May 79
MORE PROBLEMS WITH FLOOD CORRECTION 27 M May 79
TWO MINOR PROBLEMS WITH PLAYBACK BUFFERS 28 M May 79
TRANSFER STUDY CAN CORRUPT A DISK DIRECTORY 29 M May 79
FOUR FRAME MINIMUM FOR GSA STUDIES 30 M May 79
GAMMA-11/BASIC PATCHES 31 M May 79
CONTINUE ANALYSIS CA) OCCASIONALLY FAILS 32 M May 79
ASCII STRING VARIABLE TABLE (FORTRAN AND BASIC) — SUBROUTINE
GPAR AND GPAW — 33 M Jul 79
GAMMA-11 SYSTEMS WITH RK07 AS A DEVICE 34 M sep 79
INVOKING AN RT-11 INDIRECT COMMAND FILE FROM GAMMA-11 35 O Oct 79
PROBLEM WITH ABORTING GAMMA—11 36 M Oct 79
PROBLEMS WITH FORTRAN SUBROUTINES 'GPFR' AND 'GPFW' 37 F Nov 79
PROBLEMS WITH THE SAME COMMAND (S) IN RI 38 M Nov 79
GAMMA-11 F/B V2.4
CONTINUE ANALYSIS (CA) OCCASIONALLY FAILS OT M Oct 79
GAMMA-11 SYSTEMS WITH RKO7 DISKS AS A DEVICE 02 M Jan 80
PROBLEM WITH ABORTING GAMMA-11 03 M Oct 79
23
Component Sequence Mon/Yr
PROBLEMS WITH FOUR BIT MAP ANALYSIS COMMANDS 04 M Oct 79
PROBLEMS WITH FORTRAN SUBROUTINES 'GPFR' AND GPFW' 05 F Jan 80
PROBLEMS WITH DATA ANALYSIS 06 M Jan 80
PROBLEMS WITH DYNAMIC ACQUISTION ON RK05 GAMMA-11 07 M Nov 79
PROBLEMS WITH DATA ACQUISTION 08 M Nov 79
TRANSFER STUDIES WITH MAGTAPE PROBLEM 09 M Nov 79
LABORATORY APPLICATIONS-11 V3
A NEW MODULE TO ENHANCE DATA FLOW WITEIN LA-11 01 N Oct 76
HISTO.MAC
ACQUIRING AND PROCESSING HISTOGRAM DATA 01 M Sep 76
LABMAC.SML
ERRONEOUS MACRO 01 M Sep 77
INCLUDING LABMAC.SML TN SYSMAC. SML 02 M Mar 79
PEAK .MAC
WIDE PEAKS 01 M Mar 76
PEAK PROBLEMS AND CORRECTIONS 02 M Jul 76
ARITHMETIC CORRECTION FOR PEAK AREA 03 M Dec 76
MISSING PATCH IN RELEASE NOTES 04 M Oct 77
SPARTA
LPS AND AR-11 VECTOR AND STATUS REGISTER 01 N Dec 75
USING SPARTA AND FLOATING POINT BUFFERS 02 № Feb 76
AR-11 TIMING PROBLEMS WITH ADSAM AND SPARTA 03 0 Feb 76
FFT SCALING CORRECTION 04 M Feb 76
SCALE FACTOR CORRECTION FOR SPARTA COMMANDS FAC AND FCC 05 M Mar 76
DATA DISPLAYS USING LA-11 06 N Mar 76
DATA PREPARATION FOR SPARTA COMMANDS FAC AND FCC 07 N Apr 76
SPARTA CORRECTIONS FOR POINT-PLOT DISPLAY 08 M Apr 76
ADDING COMMANDS TO SPARTA 09 M May 76
CORRECTION FOR THE DPV COMMAND WITH POINT PLOT DISPLAY 10 M Jun 76
GENERAL SUBROUTINE MODULE FOR EAE 110 Jun 76
INCORRECT PHASE ANGLE CALCULATION 12 M Oct 76
"MOU" AND "MIN" COMMANDS CAN BE READ OUT AND IN CORRECTLY 13 N Jan 77
MULTIPLE SYNCH PULSES 14 M Jan 77
AUTO AND CROSS CORRELATION 15 M Jan 77
ALLOCATING MORE THAN 16K BUFFERS IN SPARTA 16 M Feb 77
A/D SAMPLING: FAST MODE 17 M Jul 77
A/D SAMPLING: FAST MODE EXIT 19 M Mar 78
SCALE FACTOR PRINT FOR THE FET 20 M Jan 79
SWEEP .MAC
SWEEP SAMPLING: FAST MODE 01 M Aug 77
THRU
HOW TO START DATA ACQUISITION WHEN CSTART EQUALS ZERO 01 N Jun 76
MULTICHANNEL SINGLE RATE SCHMIT TRIGGER SWITCH BOUNCE 02 M Dec 76
CONTINUOUS SAMPLING: CONDITIONAL ASSEMBLY ERRORS 03 M Jul 77
CONTINUOUS SAMPLING: DMA WITH DUAL SAMPLE + HOLD 04 M Jul 77
DOCUMENTATION CORRECTIONS 05 M Nov 77
LSP-11 V1
PATCH NO. 1 - GENERAL CORRECTIONS NO. 1 01 M Jun 79
PATCH NO. 2 - PEAK CORRECTION NO. 1 02 M Jun 79
PATCH NO. 3 ~ PEAK CORRECTION NO. 2 03 M Jun 79
LV11/RT-11 PLOTTING PACKAGE V2
SUBROUTINE PLOT DOES NOT CORRECTLY REPRODUCT VT11 PICTURE 01 M Apr 78
MSB-11 Y1.0
MSB-11 SOFTWARE ON THE PDP-11/03 01 M Jul 79
24
Component Sequence Mon/Yr
MU BASIC/RT-11 V1
BUILDING MU BASIC/RT-11 UNDER RT-11 V2C 01 Feb 76
REMOTE TERMINAL SUPPORT ON MODEMS 02 May 76
OVERLAY... LINE WORKS INCORRECTLY 03 May 76
USING TMMEDIATE MODE "GOSUBs"!-- 04 Dec 76
CLOCK LOSES TIME ON RT-11 WHEN RUNNING MU BASIC 05 Jul 77
REM STATEMENTS 06 Feb 78
ADDITIONAL FILES ON RELEASE KIT (MUB*.*) 07 N May 78
MU BASIC/RT-11 SYSTEM INSTALLATION GUIDE
REPLACEMENT PAGES 01 Jan 77
REPLACEMENT PAGES 02 N Jan 78
REPLACEMENT PAGES 03 N Jan 78
MU BASIC-11/RT-11 V2
MU BASIC-11/RT-11 V2 CONVERSION PROGRAM 01 R Nov 78
OPERATION OF CTRL/C, RCTRLC AND SYS (6) FUNCTIONS AND THE
CTRL/C COMMAND 02 N Nov 78
MEMORY REQUIREMENTS OF OPTIONAL FUNCTIONS ETC. 03 0 Nov 78
MU BASIC-11/RT-11 V2 RELEASE NOTES AND INSTALLATION GUIDE CHANGES O4 N Dec 78
ORDER OF COMMON STATEMENTS AT START OF MUCNFG.BOO, MUCNF1.B00,
MUCNF2.B0O 05 M Dec 78
OPERATION OF OLD, RUN, CHAIN AND OVERLAY WHEN THE SPECIFIED FILE
IS NOT FOUND 06 N Feb 79
CREATING AND ACCESSING VIRTUAL ARRAY FILES 07 N Feb 79
STORAGE OF THE NULL CHARACTER IN STRING VARIABLES AND VIRTUAL
STRING ARRAYS 08 N Feb 79
USE OF COMPILE COMMAND 09 N Feb 79
MU BASIC-11/RT-11 V2 CONFIGURATION PROGRAM PATCH 1 10 O Feb 79
CHATNING WITH COMMON -PATCH A 11 M Feb 79
VIRTUAL FILE 1/0 - PATCH B 12 M Feb 79
SYS (1,n) FUNCTION - PATCH С 13 M Feb 79
RESEQ - PATCH D 14 M Feb 79
VALUES IN PATCHES A, B, C 15 N Feb 79
LISTNH /OLD - PATCH E 16 M Mar 79
CALL — PATCH F 17 M Mar 79
MU BASIC-11 DEVICE INDEPENDENCE FOR INIT.BOO — SPECTIAL PATCH YY1 18 M May 79
DOUBLE PRECISION INTEGER VARIABLES - PATCH С 19 M May 79
INPUT #/PRINT # - PATCH H 20 M May 79
OLD OF A ZERO BLOCK FILE — PATCH I 21 M May 79
ADDITION TO PATCH B - PATCH J 22 M May 79
MU BASIC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. 1 23 M May 79
MU BASIC-11/RT-11 Y2 PERFORMANCE IMPROVEMENT PATCH NO, 2 ou M May 7
MU BASTC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. 3 25 M May 79
MU BASIC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. da 26 M May 79
MU BASIC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. 4b 27 M May 79
MU BASIC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. le 28 M May 79
MU BASIC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. 5 29 M May 79
MU BASIC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. 6 30 M May 79
MU BASIC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. 7 31 M May 79
MU BASIC-11/RT-11 V2 PERFORMANCE IMPROVEMENT PATCH NO. 8 32 M May 79
DEVICE MNEMONIC PROBLEM - PATCH K 33 M Jul 79
CLOSE - PATCH L 34 M Jul 79
REM STATEMENTS ON MULTI-STATEMENT LINES 35 M Jul 79
DEASSIGNING A TERMINAL - PATCH N 36 M Jul 79
OVERLAYING THE ERROR MESSAGE MODULE - SPECIAL PATCH WW1 37 M Jul 79
UNEQUAL USER PARTITION SIZE ALLOCATION - SPECIAL PATCH XX1 38 M Jul 79
HOW TO CHANGE INIT.B00's DEVICE AFTER INSTALLING SPECIAL PATCH YY1 39 M Jul 79
INTEGERS IN DOUBLE PRECISION MU BASIC-11 HO M Jul 79
STRING MANIPULATION IN ASSEMBLY LANGUAGE ROUTINES 41 N Aug 79
SIZING MU BASIC-11 2 № Aug 79
ERROR IN TABLE 4-1 OF THE USER'S GUIDE 43 N Aug 79
RESTRICTION OF USR RESIDENCY WHEN RUNNING IN FOREGROUND 44 N Aug 79
NOTES ON PERFORMANCE PATCHES NO. 4a, NO. Ab, NO. le 45 N Aug 79
MAXIMUM ARRAY SUBSCRIPT SIZE 46 N Aug 79
ASSEMBLING SOURCE FILES (SOURCE LICENSE HOLDERS ONLY) 47 M sep 79
USE OF SYS (1,n) FUNCTION WHEN ',n' IS OMITTED 48 M Sep 73
DISABLING CR/LF USING TTYSET - PATCH P 49 M Dec 79
HANDLER FETCH ERROR MAY LEAD TO MONITOR FAULT - PATCH Q 50 M Jan 80
25
Component Sequence Mon/Yr
PDL/RT-11 V1B
CLARIFICATION OF SEARCH FAILURE IN SUBROUTINE FIND 01 N Jul 78
FIND SUBROUTINE 02 R Jul 78
PATCHES TO PDL 03 M Jul 78
SUBROUTINE QKGT 04 M Jul 78
PDL SUBROUTINE 'RDAA' 05 M Sep 78
PDL PEAK ALGORITHM WILL NOT RECOGNIZE VALID PEAKS 06 M Sep 78
PEAK-11 V1
"MREPRT" AND "REPRT" GET CONFUSED 01 M Aug 78
REMOTE/RT-11 V1
SCHEDULER DOES NOT PROPERLY SET PROCESSOR PRIORITY 01 M May 76
NOEDIT- O HALTS 02 M May 76
NUSERS=1 STAYS IN A FILE MESSAGE LOOP 03 M May 76
INCORRECT SWAP AREA ALLOCATION FOR FOUR OR MORE USERS 04 M May 76
REBOOT FROM SATELLITE DURING EDIT HANGS HOST 05 M Jun 76
HARD ERROR ON LOOKUP IS FATAL 06 M Jun 76
SECONDARY MODE PROGRAM LOAD FEATURE NOT COMPLETELY FUNCTIONAL 07 M Jun 76
ONE SECOND TIMER FOR LINE TIMEOUTS IS SET INCORRECTLY 08 M Aug 76
LINE FEEDS MAY CAUSE SYSTEM ERRORS--ASSEMBLY ERROR WITH DIAL
AND NODDC 09 M Aug 76
PROPER GENERATION OF REMOTE IS DEPENDENT ON MODULE ORDER 10 M Aug 76
ASCII CODES 173 AND 174 DO NOT PRINT 11 M Aug 76
IMPROPER FILLER HANDLING FOR VTO5 12 0 Aug 76
SYSTEM CRASHES IF RUN IN FOREGROUND WITHOUT /N 130 Aug 76
"UNSAVE" COMMAND CAUSES SYSTEM ERRORS 14 M Dec 76
FLET WILL REMOVE MORE THAN ONE USER FROM THE WAIT QUEUE 15 M Dec 76
STACK FOR USER THREE IMPROPERLY SET 16 0 Dec 76
SECONDARY MODE LOADS DO NOT OPERATE PROPERLY 17 M Jan 77
@START COMMAND GIVEN ON TERMINAL WITHOUT SATELLITE CAUSES CRASH 18 0 Jan 77
"RTSIM"Y DOES NOT SUPPORT 50 Hz LINE CLOCK 190 Jan 77
CHANNEL ACTIVE ERROR 20 M Mar 77
THREE WORDS LOST ON DOWNLINE LOAD 21 M Mar 77
CSISPC NOT PROPERLY SIMULATED 22 M May 77
EXCEEDING CHARACTERS PER LINE LIMIT 23 M Oct 77
UNASSIGNED 24 XXX XX
ERE IN THE SATELLITE DOES NOT WORK 25 R Mar 78
"HANG" CONDITIONS 26 R Apr 78
UANSSIGNED 27 XXX XX
USING KG-11 CRC CALCULATOR 28 M Aug 78
PASTE CAUSES LINE DUPLICATION 29 M Aug 78
"DAISY CHAIN" ARRANGEMENT IN RTSIM.MAC 30 M Aug 78
OPTIONAL RMON IS OMITTED FROM RTS1M BY DEFINING NORMON=0 31 M Oct 78
DL-11 ERROR AND CRC ERROR IN HOST 32 M Oct 78
RT-11 V3
DOCUMENTATION
TYPOGRAPHICAL ERRORS 01 N Mar 78
ERROR IN FOREGROUND/BACKGROUND DEMONSTRATION 02 M Aug 78
THE /LIST OPTION FOR THE DIBOL, FORTRAN, AND MACRO KEYBOARD
MONITOR COMMANDS 03 M Nov 78
EDIT
EDIT DOES NOT OPERATE CORRECTLY UNDER XM MONITOR 01 M Mar 78
MACRO
-NARG FAILS WHEN AUTOMATIC LABEL GENERATION IS USED 01 M Apr 78
MISCELLANEOUS |
GETSTR AND PUTSTR ROUTINES FOR IN-LINE CODE 01 M Jun 78
ERROR IN THE CONCAT ROUTINE 02 M Jun 78
ERROR IN MTATCH ROUTINE 03 M Nov 78
ODD RING BUFFER SIZES CAUSE ASSEMBLY ERRORS 04 R Jun 79
26
Component Sequence Mon/Yr
MONITOR
INCORRECT IDENTIFIER IN .TWAIT REQUEST CAUSES PROBLEMS 01 M Mar 78
‚СНАТМ, .EXIT FROM VIRTUAL JOB; USR MOVING INTO PAR1 AREA 02 M Apr 78
PATCH TO INTERRUPT EXIT ROUTINE 03 M Apr 78
IMPROPER HANDLING OF THE KW11-P CLOCK 04 M May 78
SPECIFYING 50-CYCLE CLOCK SUPPORT DURING SYSGEN OPERATIONS 05 M Jun 78
EDITORS AND V3B MONITORS 06 M Jun 78
TYPING NON-ASCII FILES TO CONSOLE AFTER ISSUING À GTON HANGS
THE SYSTEM 07 M Jun 78
LINK/FRUN FAILS WHEN PROGRAM IS OVERLAYED AND USES LIBRARIES 08 M Jul 78
MULTITERMINAL CORRECTIONS 09 M Aug 78
PATCH TO XM ADDRESS CHECKING 10 M Aug 78
FIXES FOR TWO FB/XM PROBLEMS 11 M Aug 78
TERMINATING CONSOLE OUTPUT 12 M Aug 78
ISSUING SEEKS TO DX HANDLER IN XM CAUSES RANDOM SYSTEM FAILURES 13 M Oct 78
CERTAIN EXTENDED MEMORY REQUESTS CANNOT BE ISSUED FROM BOTH
MAINLINE CODE AND COMPLETION ROUTINES 15 M Oct 78
THE "RUN" AND "GET" MONITOR COMMANDS DO NOT CORRECTLY LOAD THE
PORTION OF A PROGRAM THAT OVERLAYS KMON 15 M Oct 78
DX SJ MONITOR BOOTSTRAP CORRECTIONS 15 0 Oct 78
TYPING CTRL/O TO THE CONSOLE TERMINAL SOMETIMES CRASHES 17 M Nov 78
LINK CAUSES ODD MONITOR ADDRESS TRAP 18 M Nov 78
CHAINING FROM A VIRTUAL JOB AND RELATED PROBLEMS 19 M Dec 78
DIRECTORY CORRUPTION 20 M Dec 78
FIXES FOR FB/XM PROBLEM IN VO3.02 21 M Apr 79
CORRECTION TO "DIRECTORY CORRUPTION" PATCH 22 M May 79
FLOPPY SYSGEN WITH KW11-P CLOCK 23 M May 79
INPUT FILE LOST WHEN USING CSIGEN 24 M Jun 79
SOURCES
UNRESOLVED DIFFERENCES IN DEMOX1.MAC 01 M Aug 78
DISTRIBUTED MAGTAPE HANDLER CORRECTIONS 02 M Sep 78
MAGTAPE XM AND FSM CORRECTIONS 03 M May 79
SYSTEM HANDLERS
DM HANDLER CORRECTIONS 01 M Oct 78
DM SYSTEM HANDLERS CORRECTIONS 02 M Dec 78
DM HANDLER ERROR HANDLING CORRECTIONS 03 M Jan 79
DM CTO AND SPFUN 376 CORRECTIONS 04 M May 79
UTILITIES
DUP DEFAULT FILE SIZE AND NULL FILE TYPES ARE INCORRECT 01 M Mar 78
DIR MAY INCORRECTLY LIST DIRECTORIES OF MAGTAPES 02 M Mar 78
/L OPTION TO PIP MAY CUASE SYSTEM CRASH 03 M Mar 78
LINK OUTPUT INVALID IF OBJ HAS AN EMPTY GSD RECORD 04 M Mar 78
PAT GIVES FATAL ERROR IF OBJ HAS AN EMPTY RECORD 05 M Apr 78
UNASSIGNED 06 XXX XX
EDIT VT11 DISPLAY FUNCTIONS WILL NOT OPERATE UNDER XM MONITOR 07 M/R Apr 78
TRANSFERS IN INTERCHANGE FORMAT WHEN NO SYSTEM DATE IS GIVEN 08 M Jun 78
DUP SCAN RATE FOR FLOPPY 09 M Jun 78
DUP /I AND /W SWITCHES DO NOT WORK PROPERLY 10 M Jun 78
LINK/FRUN FAILS WHEN PROGRAM IS OVERLAYED AND USES LIBRARIES 11 M Jul 78
DUP DOES NOT DIFFERENTIATE BETWEEN DELETED .BAD FILES AND |
PERMANENT ONES 12 M Jul 78
ERRORS IN FILEX INTERCHANGE FORMAT 13 M Jul 78
LINK PRODUCES INCORRECT .LDA FILES 14 M Sep 78
DUP DOES NOT DETECT END OF SEGMENT IF IT IS FIRST ENTRY IN A
DIRECTORY SEGMENT DURING A SQUEEZE OPERATION 15 M Oct 78
LIBR CLEARING OF LOCATION ZERO 16 M Oct 78
LINK ERROR IN PSECTS MOVED TO ROOT 17 M Oct 78
PIP ERRONEOUSLY DELETES FILES 18 M Oct 78
LIBR BLOCK BOUNDARY PROBLEM 19 M Dec 78
LINK CAN CAUSE TRAP TO В 20 M Feb 79
CORRECTIONS TO FILEX 21 M May 79
DIR CORRECTIONS 22 M Nov 79
BAD BLOCK REPLACEMENT ON RKO6s 23 N Oct 79
WILD CARD MAGTAPE COPY ERROR PROCESSING CORRECTION 24 M Oct 79
27
Component, Sequence Mon/Yr
RT-11 V3B
DOCUMENTATION |
ERROR IN FOREGROUND/BACKGROUND DEMONSTRATION 01 M Aug 78
THE /LIST OPTION FOR THE DIBOL, FORTRAN, AND MACRO KEYBOARD
MONITOR COMMANDS 02 M Nov 78
UPDATE PAGES 03 N Dec 78
RT-11 SOFTWARE SUPPORT DOCUMENTATION 04 M Feb 79
SUMMARY OF UPDATES FOR RT-11 VO3B DOCUMENTATION 05 M Feb 79
NEW DEVICE RELEASE DOCUMENTATION, RT-11 VO3B 06 N Jun 79
.FORK AND .SYNCH BLOCK DOCUMENTATION 07 N Jul 79
THE DEVICE TIME-OUT FEATURE 08 N Sep 79
CORRECTION OF ERROR RETURNS IN .SYNCH CALL 09 M — Aug 79
EXAMPLE CODE IN .FORK DOCUMENTATION IS INCORRECT 10 N Aug 79
EXTENDED MEMORY RESTRICTIONS 11 N Dec 79
NOTES ON .MFPS/ .MTPS PROGRAMMED REQUEST 12 N Apr 80
MISCELLANEOUS
ERRORS IN THE SYSGEN CONDITIONAL FILE 01 M Jul 78
ERRORS IN MTATCH ROUTINE 02 M Nov 78
ODD RING BUFFER SIZES CAUSE ASSEMBLY ERRORS 03 R Jun 79
INCORRECT NULL HANDLER DEVICE IDENTIFIER O4 M Jun 79
GENERATING A SINGLE JOB MONITOR MAY CAUSE AN UNDEFINED GLOBAL 05 M Aug 79
INCORRECT DEVICE IDENTIFIER FOR PC11 06 M Sep 79
ERROR IN MTIN AND MTOUT ROUTINES 07 M Sep 79
HIGH SPEED RING BUFFER PROBLEM ON SYSTEMS WITH ONE DL11 08 M Jan 80
SYSGEN FOR TU58 SUPPORT 09 F May 80
DEVICE TIME-OUT SUPPORT IN SYSGEN 10 F May 80
MONITOR
SOURCE PATCHING PROCEDURES FOR V3B 01 M Aug 78
MULTITERMINAL CORRECTIONS 02 M Aug 78
SINGLE JOB TIMER SUPPORT CORRECTIONS 03 M Aug 78
FIXES FOR TWO FB/XM PROBLEMS IN VP3B 04 M Aug 78
TERMINATING CONSOLE OUTPUT 05 M Aug 78
EDITORS AND VO3B MONITORS 06 0 Aug 78
SEEK IN RK DRIVER 07 M Aug 78
RLO1 CONTROLLER VECTOR AT 160 08 M Aug 78
FPU EXCEPTION HANDLING IN XM MONITOR 09 M Sep 78
TWO EXTENDED MEMORY MONITOR PROBLEMS 10 M Oct 78
TYPING CTRL/O TO THE CONSOLE TERMINAL SOMETIMES CRASHES RT-11 11 M Oct 78
DX SJ MONITOR BOOTSTRAP CORRECTIONS 12 0 Oct 78
THE EDIT AND HELP MONITOR COMMANDS FAIL AFTER A VIRTUAL JOB HAS RUN 13 M Nov 78
DIRECTORY CORRUPTION AND .UNPROTECT CORRECTIONS 14 M Jan 79
FB AND XM MONITOR CLOCK SUPPORT 15 M Apr 79
CHANGING CLOCK RATE ON GENERATED MONITORS 16 M Apr 79
MULTI-TERMINAL CORRECTIONS TO DECREASE INTERRUPT LATENCY 17 M Apr 79
FIXES FOR FB/XM PROBLEM IN V0O3B.00 18 M Apr 79
FLOPPY SYSGEN WITH KW11-P CLOCK 19 M May 79
DISTRIBUTED FB MONITOR CLOCK SUPPORT 20 M May 79
OPTIONAL PATCH TO IMPROVE PERFORMANCE ON PDP-11/03 SYSTEMS 21 0 May 79
DISTRIBUTED PD AND DD FB MONITORS CLOCK SUPPORT 22 M May 79
OPTIONAL PATCH TO IMPROVE PERFORMANCE ON PDP-11/03 AND PDT
SYSTEMS FOR DD AND PD FB MONITORS 23 0 May 79
INPUT FILE LOST WHEN USING CSIGEN 24 M Jun 79
NON-STANDARD VECTOR ADDRESSES FOR RX01 AND RX92 SECOND CONTROLLER 25 M Nov 79
ABORT DURING COMPLETION CAUSES SYSTEM FAILURES 26 M Nov 79
.ELRG CAN CAUSE THE SYSTEM TO CRASH 27 M Sep 79
CORRECTION TO BOOTSTRAP TO RECOGNIZE LSI-11/23 PROCESSOR 28 M Oct 79
FPU SAVE AREA IN XM MONITOR 29 M Dec 79
BACKGROUND JOB MAY TRAP WHEN FOREGROUND ISSUES .SYNCH FROM | |
~ INTERRUPT ROUTINE 30 M Dec 79
PROBLEM WHEN FOREGROUND AND BACKGROUND JOB USE CSI AT SAME TIME 31 M Mar 80
SYSTEM GENERATED SJ MONITOR WITH ESCAPE SEQUENCE SUPPORT 32 М Арг 80
BREAKPOINT TRAP PROCESSOR STATUS WORD CORRUPTION 33 M Apr 80
CORRECTIONS TO MULTI-TERMINAL SUPPORT 34 M May 80
SOURCES
UNRESOLVED DIFFERENCES IN DEMOX1 MAC 01 M Jul 78
ISSUING SEEKS TO DX HANDLER IN XM CAUSES RANDOM SYSTEM FAILURES 02 M Sep 78
DISTRIBUTED MAGTAPE HANDLER CORRECTIONS 03 M Sep 78
DY HANDLER DOUBLE DENSITY ONLY SUPPORT O4 M Apr 79
DL QUEUE ELEMENT AND XM ZERO FILL CORRECTIONS 05 M Apr 79
28
Component Sequence Mon/Yr
MAGTAPE XM AND FSM CORRECTIONS 06 M May 79
DL. HANDLER SEEK AND UNIT CORRECTIONS 07 M Aug 73
MAGTAPE ABORT ENTRY CORRECTION 08 M Sep 79
MAGTAPE ABORT ENTRY CORRECTION IN XM 09 M Dec 79
DL HANDLER SEEK CORRECTION 10 M Jan 80
FILE SEQUENCE NUMBER SEARCH CORRECTION 11 M Feb 80
HARD ERROR RECOVERY IN DM HANDLER 12 М Маг 80
FSM DOES NOT PROCESS ERRORS CORRECTLY IN XM 13 M Apr 80
RLO1/RLO2 HANDLER CORRECTIONS 14 M Apr 80
MULTI-CONTROLLER DY HANDLER PROBLEM 15 M May 80
SYSTEM HANDLERS
RLO1 HANDLER CORRECTIONS 01 M Sep 78
ISSUING A SEEK TO THE DY HANDLER CAUSES THE SYSTEM TO CRASH 02 M Oct 78
DM HANDLER CORRECTIONS 03 M Oct 78
DM SYSTEM HANDLERS CORRECTIONS 04 M Dec 78
DY HANDLER SPFUN CORRECTION 05 М Dec 78
DM HANDLER ERROR HANDLING CORRECTIONS 06 M Jan 79
RLO1 PATCH CLARIFICATION 07 N Jan 79
DM CTO AND SPFUN 376 CORRECTIONS 08 M May 79
BATCH INCORRECTLY LOGS TERMINAL OUTPUT 09 M Apr 80
IMPROPERLY CHECKED INPUT CAUSES UNPREDICTABLE RESULTS 10 M Apr 80
UTILITIES |
ERRORS IN FILEX INTERCHANGE FORMAT 01 M Jul 78
LINK PRODUCES INCORRECT .LDA FILES 02 M Sep 78
LIBR CLEARING OF LOCATION ZERO 03 M Oct 78
LINK ERROR IN PSECTS MOVED TO ROOT 04 M Oct 78
DUP DOES NOT DETECT END OF SEGMENT 05 M Oct 78
COPY/DEVICE FAILS ON DISK TO MAGTAPE 06 M Oct 78
LINK CAUSES MONITOR ODD ADDRESS TRAP 07 M Nov 78
LIBR BLOCK BOUNDARY PROBLEM 08 M Jan 79
EDIT ESCAPE CODE CORRECTION 09 0 Dec 78
ERROR IN ODT 10 M Feb 79
ERROR IN EDIT 11 M Feb 79
LINK CAN CAUSE TRAP TO 4 12 M Feb 79
CORRECTIONS AND ADDITIONS TO FILEX 13 M May 79
RESORC DISPLAYS STATUS OF FIRST 14 TERMINALS 15 M Jun 79
LIBR /U SWITCH PROBLEM 16 M Aug 79
IMPORTANT RESTRICTIONS FOR SQUEEZE OPERATIONS 17 M Aug 79
DIR PROBLEMS 18 M Oct 79
BAD BLOCK REPLACEMENT ON RK06s 19 N Oct 79
WILD CARD MAGTAPE COPY ERROR PROCESSING CORRECTION 20 M Oct 79
PROBLEM WITH PSECTS MOVED TO ROOT DURING LIBRARY PASS 21 M Jan 80
PIP PROBLEMS 22 M Feb 80
DIR PROBLEM 23 M Feb 80
DUMPING DISK FILES WITH MAGTAPE HANDLER LOADED 24 M Mar 80
BAD BLOCK REPLACEMENT ON RLO1s 25 M Apr 80
MDUP AND RLO1s 26 M Apr 80
CORRECTION TO PDT-11/150 SUPPORT IN FILEX 27 M Apr 80
PROBLEM WITH DUP ERRORS WHEN /W OPTION USED 23 M Apr 80
INSUFFICIENT DIRECTORY SPACE ON NON-SYSTEM FLOPPY 29 M Apr 80
EDITING FILES ON WRITE-LOCKED DEVICES 30 M May 80
BAD BLOCK SCAN FOR LARGE DEVICES 31 M May 80
RT-11/2780 V2
CORRECTIONS TO 2780 PACKAGE 01 sep 77
RUNNING 2780 ON RT-11 V3 02 Nov 77
PATCHING THE 2780 IN RT-11 V3 03 M Jan 79
CHECK FOR ZERO LENGTH RECORD 04 M Jan 79
RESTRICTION OF THE CONSOLE AS AN INPUT/OUTPUT DEVICE 05 R Jan 79
29
dilgi tla | |
Software Product Description
PRODUCT NAME: DECnet-RT, Version 1.1, RT-11 Network Software
DESCRIPTION:
DECnet-RT allows a suitably configured RT-11 system
to participate as a Phase I| DECnet node in point-to-
point computer networks. DECnet-RT offers task-to-
task communications, network file transfer and net-
work resource-sharing capabilities, using the DIGITAL
Network Architecture (DNA) protocols. DECnet-RT
communicates with adjacent nodes over synchronous
and asynchronous communication lines. Access to
DECnet-RT is supported for RT-11 user programs writ-
ten in MACRO-11 and FORTRAN.
DECnet-RT is a Phase Il network product and is war-
ranted for use only with Phase Il and Phase Ill DECnet
products supplied by DIGITAL.
The functions available to an RT-11 user depend, in
part, on the configuration of the rest of the network.
Each DECnet product offers its own level of capability
and its own set of features to the user. Networks con-
sisting entirely of DECnet-RT nodes (a two-node net-
work because DECnet-RT supports one communica-
tion iine) nave the fuii capabiiity described in this SPD.
Networks that mix DECnet-RT nodes with other
DECnet products can limit the functions available to
the DECnet-RT user because some DECnet-RT fea-
tures may not be supported by all DECnet products.
The DECnet products and functions available to users
on mixed networks can be determined by comparison
of the SPDs for the component products. An overview
of DECnet and common capabilities available with
mixed networks can be obtained from the general
Phase il (10.78) and Phase III (10.59) DECnet SPDs.
Task-to- Task Communication
Using DECnet-RT, an RT-11 user program written in
MACRO-11 or FORTRAN can exchange messages
with other programs using DECnet protocols. The two
user programs must be adjacent DECnet nodes. (Adja-
cent nodes control opposite ends of a point-to-point
communication line.) If the nodes are adjacent, the
second node can be any DECnet system. The DECnet
messages sent and received by the two user programs
can be in any data format.
Network Resource Access
File Transfer Utility
Using DECnet-RT utilities, a user can transfer sequen-
tial ASCI files between DECnet nodes. Files can be
March 1980
31
SPD 10.72.5
transferred in both directions between a locally sup-
ported RT-11 file system device and the file system of
an adjacent DECnet node.
In addition, other types of files can be transferred
where formats are compatible between the DECnet
nodes.
Additional facilities allow system command files or
batch files to be submitted to a remote node where the
list of commandsis inthe format expected by the node
responsible for the execution. DECnet-RT does not
support system command or batch files to be submit-
ted from other systems.
File Access
File access is supported to and from remote DECnet
systems by explicit subroutine calls in FORTRAN and
MACRO tasks.
READ, WRITE, OPEN and CLOSE, and DELETE oper-
ations can be initiated by local FORTRAN and MACRO
tasks for sequential files residing at remote systems.
Other nodes supporting file access can exercise this
capability for files located on the RT-11 node. Fixed
and variable length record formats are supported.
Further, files accessed remotely can contain either
ASCII or binary information.
Network Information Program
Using the DECnet-RT Network Information Program
utility, a user can set node name and password, and
display statistics related to the communication lines,
including data on traffic and errors. Output can be
directed to the terminal or to a log file.
Terminal Communication Utility
The DECnet-RT TLK utility allows a user at a DECnet-
RT node to send messages to adjacent DECnet nodes
that support the same feature. Messages can be
directed to a specific terminal or to the operator's con-
sole at the destination node. TLK dialog mode allows
users on the two systems to type messages to one
another.
Communications
DECnet-RT supports the DIGITAL Data Communica-
tions Message Protocol (DDCMP) for full- or half-
duplex transmission in point-to-point operation using
serial synchronous or asynchronous facilities.
DDCMP provides error detection/correction and phy-
sical link management facilities.
AE-D431E-TC
DECnet-RT, Version 1.1
One point-to-point link can be supported by an RT-11
node. Only one link can connect any pair of nodes.
DECnet-RT Operation
DECnet-RT is implemented as a driver under RT-11
FB/XM and as subroutines that would be linked with
the foreground or background RT-11 program. Min-
imum memory residency requirements for a driver and
network code are 7K words (14K bytes), and at least 1K
words (2K bytes) for temporary data storage. Con-
sequently, the user should plan to dedicate at least 8K
words (16K bytes) of memory storage to network con-
trol functions. Additional memory will be required fora
user-written network task or any DECnet utility func-
SPD 10.72.5
e With character interrupt devices such as the DUP11,
CPU cycles are required for not only the DDCMP
processing, but also each character sent and
received.
The following tables describe what physical hardware
configurations are supported by DECnet-RT in terms
of CPU class and communication interface. It should
be noted that the attachment of such devices as A/D
converters and multiple terminals can reduce the line
speed that can effectively be supported.
Maximum Line Configurations on 11/03 CPUs, PDT-11/130 or PDT-11/150
tions to be invoked (file transfer, TLK). Maximum addi- Device Max. No. Maximum Maximum Mode
. . .... . Group of Lines Line Speed Device
tional memory required for a DECnet-RT utility is 10K (Kilobits/sec) Bandwidth
words. (Kilobits/sec)
DECnet-RT Configuration
DUV11, 1 2.4 2.4 FDX/HDX
The process of configuring a DECnet-RT node is DLV11-E
based primarily on trade-offs of cost, performance,
and functionality, within the realm of satisfying the Maximum Line Configuration on 11/04-11/70 CPUs
user's application requirements. It can be readily Device Max. No. Maximum Maximum Mode
expected that network applications will run the full Group of Lines Line Speed Device
gamut from low-speed, low-cost situations to those of (Kilobits/sec) Kleben)
relatively high performance and capability. The per-
formance of agiven DECnet node isa function not only LT DU , pe se rox
of the expected network traffic and resultant process- DUP11
ing (global! conditions), but also of the amount of con- DMC11-AR-DA 1 192 19.2 FDX/HDX
current processing peculiar to that node (local condi- DMC11-AL-MD 1 56.0 56.0 FDX/HDX
DMC11-AL-MA 1 1000.0 1000.0 FDX/HDX
tions). Thus, node performance depends on many
factors, including:
CPU power
se Number of device interrupts per unit time
e Communication line characteristics
e Number and size of buffers
* Message size and frequency
e “Local” applications
It is important to note that the rate at which user data
can be shipped (throughput) over a communi-
cations line can sometimes approach, but will never
equal or exceed, the actual line speed. The reason,
simply stated, is that the actual throughput is a func-
tion of many factors, including the user application(s),
network topology, protocol overhead, and the factors
cited at the beginning of this section.
There are basically two groups of communications
interfaces presented in the following tables. They differ
in many respects, particulary in their effect upon CPU
utilization.
* The DMC11 is a Direct Memory Access (DMA)
device. Also, the DDCMP line protocol is executed
in microcode by the DMC11 communication con-
troller, thus, off-loading the PDP-11. Thus, the only
DECnet load the processor sees is completed in-
coming and outgoing messages.
32
“Restricted to maximum of 4.8 on PDP-11/04, 11/10, or 11/23
Maximum Number of Lines — The largest number of
physical lines that can be attached and driven by the
DECnet-RT system.
Maximum Device Bandwidth — The maximum total
number of bits per second that can be handled by a
CPU for a given communication device. For example,
DECnet-RT on a PDP-11/04 can accommodate one
fuli-dupiex character-interrupt device at 4.8KB.
Maximum Line Speed — The fastest clock rate at
which the device can be driven under DECnet-RT. This
means that even if devices have the ability to operate at
a maximum rate, they must be configured subject to
the “maximum device bandwidth” restriction above.
Mode — This indicates whether the line is operating
in either half-duplex (a single bit stream) or full-duplex
(two concurrent bit streams) mode. For some instan-
ces in tables, a half-duplex line is quoted as having
maximum bandwidth approximately double that com-
parable fuli-duplex line. This reflects the single bit
stream character of half-duplex lines, and the fact that
two of them place a load on the CPU roughly equival-
ent to one fuli-duplex line with traffic in both
directions.
DECnet-RT, Version 1.1
System Generation
Generation and installation of DECnet-RT requires a
valid RT-11 V3B or later system with at least 32K bytes
of memory and an RKO5S disk or larger plus one addi-
tional device for distribution media. Generation on
floppy diskette or TU58 DECtape il only systems is not
supported.
MINIMUM HARDWARE REQUIRED:
Any valid RT-11 FB/XM system configuration with:
e Minimum of 8K words (16K bytes additional availa-
ble memory for the DECnet-RT software and data
storage
e PDP-11/03 through PDP-11/70 central processor
with one or more of the appropriate communica-
tions devices:
e DU11-DA low-speed synchronous interface
e DUP11-DA low-speed synchronous interface
e DMC11-AR-DA remote synchronous V.24/EIA
RS-232-C interface
e DMC11-AR-FA remote synchronous V.35/DDS
interface
e DMC11-AL-MD high-speed local synchronous
interface
e DMC11-AL-MA high-speed local synchronous
interface
e DL11-E asynchronous EIA RS-232-C interface
with modem control
e DL11-C asychronous interface 20mA current
loop (1)
e DL11-WA asynchronous interface 20mA current
loop (1)
e DUVIi-DA iow-speed EiA RS-232-C synchro-
nous interface
e DLV11-E asynchronous EIA RS-232-C interface
with modem control
e DLV11-F asynchronous 20mA interface (1)
NOTE:
(1) Requires either the H319 option for optical
isolation or one side of the 20mA line to be in
passive mode.
e PDT-11/130 with TU58
e PDT-11/150 with dual floppies
OPTIONAL HARDWARE:
None
PREREQUISITE SOFTWARE:
RT-11 FB/XM Operating System, Version 03B
OPTIONAL SOFTWARE:
FORTRAN IV/RT-11, Version 2.1
-3-
33
SPD 10.72.5
TRAINING CREDITS:
No training credits are included with a DECnet soft-
ware license. Training courses on DECnet software are
scheduled at regular intervals in DIGITAL’s Training
Center. Arrangements should be made directly with
DIGITAL's Educational Services Department.
SUPPORT CATEGORY:
DIGITAL SUPPORTED
DECnet-RT is a DIGITAL Supported Software
Product. .
SOFTWARE INSTALLATION:
DIGITAL INSTALLED
DIGITAL instaliation is required for Software Product
Support. There is no charge for installation if per-
formed at the time of system installation. DIGITAL
installed software products, except for operating sys-
tems, are subject to an add-on installation fee when
purchased subsequent to system installation.
Installation under DIGITAL Supported will convert the
RT-11 system into a node with connection potential to
a DECnet network. This installation does not include a
demonstration of network connection.
SOFTWARE PRODUCT SUPPORT:
DECnet-RT includes standard services as defined in
the Software Support Categories Addendum of this
SPD.
The customer can purchase DECnet-RT licenses with
options that do not include supportservices. The cate-
gory of support applicable to such software is Custo-
mer Supported. When a DECnet-RT product option
that does not include support services is connected to
a DECnet network, the category of support applicable
to all DECnet products in the network is Customer
Supported.
CUSTOMER RESPONSIBILITIES:
Before installation of the software, the customer must:
1. Obtain, install, and demonstrate operational to
DIGITAL's satisfaction any modems and other
equipment and facilities necessary to interface DIG-
ITAL's communications line interfaces and
terminals.
2. Make available to DIGITAL personnel all hardware,
including terminals, to be used during installation
for a reasonable period of time, as mutually agreed
upon by DIGITAL and the customer, until installa-
tion is complete.
Delays caused by any failure to meet these responsibil-
ities will be charged at the then prevailing rate for time
and materials.
PREREQUISITE SUPPORT:
A Network Profile and DECnet Customer Support Plan
are required to be jointly prepared by the customer and
DIGITAL covering all intended network nodes and
their support.
DECnet-RT, Version 1.1
ORDERING INFORMATION:
All binary licensed software, including any subsequent
updates, is furnished under the licensing provisions of
DIGITAL's Standard Terms and Conditions of Sale,
which provide in part that the software and any part
thereof may be used on only the single CPU on which
the software is first installed, and may be copied, in
whole or in part (with the proper inclusion of the
DIGITAL copyright notice and any DIGITAL proprie-
tary notices on the software) only for use on such CPU.
All source licensed software is furnished only under
the terms and conditions of a separate Software Pro-
gram Sources License Agreement between Purchaser
and DIGITAL.
Options with no support services are only available
after the purchase of one supported license.
A single-use license only option is alicense to copy the
software previously obtained under license.
Source and/or listing options are only avilable after the
purchase of at least one supported license and after a
source license agreement is in effect.
The following key (D, E, G, M, Q, R, T, V, X, Y, Z)
represents the distribution media for the product and
must be specified at the end of the order number, e.g.,
QJ685-AD = binaries on 9-track 800 BPI Magtape
(NRZI).
9-track 800 BPI Magtape (NRZI)
RKO5S Disk Cartridge
TU58 DECtape II Cartridge
9-track 1600 BPI Magtape (PE)
RLO1 Disk Cartridge
Microfiche
RK06 Disk Cartridge
RK07 Disk Cartridge
RX02 Double Density Diskette
RX01 Floppy Diskette
No hardware dependency
mo
HAN ER ARO 46 AA EDO EN ADO ARCH
N<xX<IDOZO
QJ685 -A— Single-use license, binaries, documen-
tation, support services (media: D, E, G,
M, Q, T, V, X, Y)
QU685 -C— Single-use license, binaries, documenta-
tion, no support services (media: D, E, G,
M, Q, T, V, X, Y)
34
SPD 10.72.5
QU685 -D— Single-use license only, no binaries, no
documentation, no support services
(media: Z)
Source /Listing Options
QU685 -E— All sources (media: D, E, G, M, Q, T, V, X,
Y)
QJ685 -F— Listings (media: R)
Update Options
Users of DECnet-RT, Version 1.0 whose specified
Support Category warranty has expired may order
under license the following software update at the then
current charge for such update. The update is distrib-
uted in binary or source form on the appropriate
medium and includes no installation or other services
unless specifically stated.
QU685 -H— Binaries, documentation (media: D, E, G,
M, Q, T, V, X, Y)
QuU685 -H— Right to copy for single-use (under exist-
ing license), no binaries, documenta-
tion, no support services (media: Z)
QJ685 -N— Sources (media: D, E, G, M, Q, T, V, X, Y)
Users of DECnet-RT, Version 1.0, whose specified
Support Category warranty has not expired may order
under license the following software update for the
then current media charge. The update is distributed in
binary or source form on the appropriate medium and
includes no installation or other services unless specif-
ically stated.
QJ685 -W-— Binaries, documentation (media: D, E,
G, M, Q, T, V, X, Y)
QU685 -L— Sources (media: D, E, G, M, Q, T, V, X, Y)
Miscellaneous Options
QJ685 -G— Documentation only kit (media: Z)
ADDITIONAL SERVICES:
QJ680 -S— DECnet Level | Services (media: 2)
Level || services are also available. Consultthe DECnet
Phase || Products SPD (10.78) for a description of
Level | and Level I! services.
Alois
PRODUCT NAME: DECnet Phase || Products, version 1.0
DESCRIPTION:
DECnet Phase Il is the collective name for the set of
software products that extend various DIGITAL oper-
ating systems by enabling the user to interconnect
these systems with each other to form computer net-
works. The DECnet Phase I! products include DECnet-
IAS Version 2.1, DECnet/E Version 1.1, DECnet-RT
Version 1.1, DECnet-VAX Version 1.2, and DECnet-20
Version 2.0. The DECnet user can configure a variety of
networks, to satisfy a variety of applications, by choos-
ing the appropriate CPUs, line interface (and speeds),
and operating system software.
In order to satisfy these widely varying applications,
DECnet allows the user to build networks from a range
of systems and communications components. DECnet
allows users to interconnect systems using serial
asynchronous, serial synchronous, and parallel facili-
ties. When configuring DECnet systems, both ends of
any given link must use the same type of communica-
tions discipiine {e.g., synchronous, asynchronous, or
parallel) running at the same line speed.
DIGITAL Network Architecture
DECnet includes a set of layered network protocols,
each of which is designed to fulfill specific functions
within the network. Collectively, these protocols are
known as the DIGITAL Network Architecture, or DNA.
The major protocols and their functions are:
DIGITAL Data Communications Message Protocol
(PDCMP) — DDCMP handles the physical link traffic
control and physical link error recovery within DECnet.
DDCMP operates over both full- and half-duplex facili-
ties, using serial synchronous or serial asynchronous
facilities in a point-to-point mode. DDCMP has the
following important characteristics:
e Operates over a wide variety of hardware types
* Makes efficient use of full-duplex channel capacity
e Allows transmission of all data types (including
binary with low overhead)
March 1980
35
SPD 10.78.4
¢ Allows standard (character-oriented) communica-
tions hardware to be used
* Uses CRC-16 for error detection, with recovery by
retransmission
o Effective on earth/satellite links (or other links) with
long signal propagation delays
A full specification for DDCMP, Version 4.0 is available
on request. DIGITAL does not regard DDCMP as a
proprietary protocol, and allows others to implement
and use the protocol, providing an acknowledgment of
the source is made in any public documentation.
Network Services Protocol (NSP) — NSP handles net-
work management functions within DECnet. This
includes sending messages between two nodes and
routing messages within any given node. NSP makes it
possible for two programs on different machines to
establish a logical communications channel (or logical
link) between the programs, and to exchange data
using this logical link. These programs need not be
aware of either the nature of the physical link (full/half
duplex, parallel or serial) or the nature of the protocols
supporting the physical link. NSP has the following
important characteristics:
Dynamic creation of logical links between tasks
Exchange of data between tasks on a solicited basis
Exchange of data between tasks on a non-solicited
(e.g., interrupt) basis
Ability to connnect nodes dynamically within the
network once NSP initialization occurs over a pre-
viously established physical link
A full specification for the NSP, Version 3.0 is available
on request. NSP is not a proprietary protocol.
Data Access Protocol (DAP) — DAP enables programs
on one node of the network to use the 1/0 services
available on other network nodes. Some DECnet pro-
ducts provide facilities for translating operating sys-
tem’s unique 1/0 calls into the DAP standard, and vice
versa. Thus, DAP enables data requests to be pro-
cessed in a meaningful way by many (possibly hetero-
geneous) operating systems. DAP’s facilities include:
AE-D440E-TC
DECnet Phase !! Products, Version 1.0
remote file access, including OPEN, READ, WRITE,
CLOSE, and DELETE for sequential and random
access files, and command files.
It should be noted that each DAP function requires
support at both ends of the link. At the local node,
where the user program initiates a data request, the
DAP support must package the request for transmis-
sion through the network. At the remote node (where
the device or file resides), the DAP support must cause
the appropriate actions to be performed. Not ail sys-
tems support both local and remote portions of each
DAP operation.
A full specification for the DAP, Version 4.1 is available
on request. DAP is not a proprietary protocol.
DECnet Functions
DIGITAL Network Architecture, implemented across a
wide range of operating systems and hardware config-
urations, enables users to build a variety of networks.
While such networks have a common attribute, indi-
vidual systems in the network can have certain system-
specific attributes. The common attribute is:
e Task-to-task communication: Programs or tasks on
one system can create logical links and exchange
data with programs or tasks on other systems in a
real-time fashion.
Additionally, many DECnet systems support other fea-
tures that are useful in a network environment. These
include:
e Inter-system File Transfer: This facility allows an
entire data file to be moved between systems, at
either program or operator request. The common
file type supported across systems that provide this
function is sequential ASCII.
Batch/Command File Submission: Local users can
submit batch or command files to remote systems
for execution.
Batch/Command File Execution: Remote users can
cause a batch or command file that resides at a
remote node to be submitted for execution at the
local node.
Remote File Access: Tasks or programs can access
sequential files on a record-by-record basis from
files located on remote nodes.
Down-line System Loading: Initial memory images
for DECnet-11S systems in the network can be
stored on the local system, and loaded on request
into other systems in the network. Remote systems
usually require the presence of a network bootstrap
loader, implemented in read-only memory.
Down-line Task Loading: Programs to be executed
on DECnet-11S systems in the network can be
stored on the local system, and loaded on request
into other systems, under the joint control of the
36
SPD 10.78.4
operating systems at both ends of the physical link.
This and the preceding feature simplify the opera-
tion of network systems that do not have mass stor-
age devices.
Table | provides the information for determining if the
preceding functions are available on a particular
DECnet system. Note that the above descriptions
define the minimum capabilities provided by a given
function. Additional capabilities, above those
described as the minimum for a function, may be avail-
able between two of the same or different DECnet
systems.
Configuring DECnet Networks
DECnet provides a basic level of interconnection
between specific products. However, each DECnet
system has its own level of functions. The user can
recognize specific constraints when configuring a
network of heterogeneous DECnet systems. Table ||
lists the communication interfaces supported by each
DECnet Phase || product for a particular class of line
characteristics (e.g., 9.6 kilobits/second, synchron-
ous). Each column lists the connections that are per-
missible for those line characteristics in cross-product
network configurations. Individual product SPDs must
be consulted to determine whether any particular con-
figuration violates the maximum number of communi-
cations interfaces and line speeds for an individual
product.
TRAINING CREDITS:
No training credits are included with a DECnet soft-
ware license. Training courses on DECnet software are
scheduled at regular intervals in DIGITAL's Training
Centers. Arrangements should be made directly with
DIGITAL's Educational Services Department.
PRODUCT SUPPORT:
DECnet Phase Il products are DIGITAL Supported
software products. A Network Profile and DECnet Cus-
tomer Support Plan covering all intended network
nodes and their support must be prepared jointly by
the customer and DIGITAL.
The customer may purchase DECnet Phase || product
license options that do not include support services.
The category of support applicable to such software is
Customer Supported. When a DECnet product option
that does not include support services is connected to
a DECnet network, the category of support applicable
to all DECnet products in that network is Customer
Supported.
INSTALLATION SERVICE:
The installation of DECnet Phase Il software under
DIGITAL Supported/DIGITAL Installed shall consist
of:
1. Verifying that the software kit contains all software
modules and manuals offered.
DECnet Phase II Products, Version 1.0
2. Generating the DECnet software.
3. Demonstrating the use of the majority of operator
4. Running a sample DIGITAL -supplied program.
5. Introducing the customer to the sources of software
information and services.
Before installation of the software, the customer must:
1. Obtain, install, and demonstrate operational to
DIGITAL's satisfaction any modems and other
equipment and facilities necessary to interface
DIGITAL's communications line interfaces and
terminals.
2. Make available to DIGITAL personnel all hardware,
including terminals, to be used during installation
for a reasonable period of time, as mutually agreed
upon by DIGITAL and the customer, until installa-
tion is complete.
Delays caused by any failure to meet these responsibil-
ities will be charged at the then prevailing rate for time
and materials.
ORDERING INFORMATION:
All binary licensed software, including any subsequent
updates, is furnished under the licensing provisions of
DIGITAL's Standard Terms and Conditions of Sale,
which provide in part that the software and any part
thereof may be used on only the single CPU on which
the software is first installed, and may be copied, in
whole or in part (with the proper inclusion of the
DIGITAL copyright notice and any DIGITAL proprie-
tary notices on the software) only for use on such CPU.
All source licensed software is furnished only under
the terms and conditions of a separate Software Pro-
gram Sources License Agreement between Purchaser
and DIGITAL.
SPD 10.78.4
When multiple systems are connected in a single net-
work, each individual system must be licensed separ-
ately with regard to both operating system and DECnet
software.
ADDITIONAL SERVICES:
Software Consulting Services are offered on atime and
materials basis to meet specific customer needs. Two
levels of consulting services are available:
Level | Services
QJe80 -S— DECnet Level | Services (media: Z)
Level | services provide for the integration of DECnet
nodes that carry DIGITAL Installed/DIGITAL Sup-
ported support into an interconnected network, with
verification of network integrity and demonstration of
DECnet functions. Level | services use DIGITAL
sample procedures only.
Level Il Services
QS912 -S— Daily Software Consulting Services
(media: Z)
QS926 -S— Weekly Software Consulting Services
(media: 2)
QS922 -S— 6-Month Resident Software Consulting
Services (media: Z)
QS924 -S— 12-Month Resident Software Consulting
Services (media: Z)
Level ll services provide for additional support as mut-
ually agreed upon by DIGITAL and the customer in the
DECnet Customer Support Plan.
37
DECnet Phase II Products, Version 1.0 SPD 10.78.4
-4-
TABLE !
DECnet-1AS DECnet/E DECnet-RT DECnet-VAX | DECnet-20
Version 2.1 Version 1.1 Version 1.1 Version 1.2 Version 2.0
Task-to-Task YES YES YES YES YES
Intersystem YES YES YES YES YES
File Transfer
Command/Batch Requestor YES YES YES NO NO
File Submission Server YES NO NO NO YES
Command/Batch Requestor YES YES YES YES YES
File Execution Server YES YES NO YES YES
Remote File Access Requestor YES NO YES YES NO
Server YES YES YES YES NO
Down-Line YES NO NO YES NO.
System Loading
Down-Line YES NO NO NO NO
Task Loading
Requestor — Requests Service
Server — Provides Service
TABLE II
EIA EIA EIA 20mA Remote Local Local Local
Sync Sync Async Async Sync Sync Sync Parallel
< 9.6K <19.2K € 9.6K <9.6K 56K 56K 1M
bits/sec bits/sec bits/sec bits/sec bits/sec bits/sec bits/sec
DECnet-IAS DP11 DMC11-AR-DA | DL11-E DL11-C/WA DMC11-AL-MD | DMC11-AL-MA | DA11-B/AL
DU11-DA DZ11-A/8 DZ11-C/D
DUP11-DA
DV11
DQ11-DA
DECnet-RT DU11-DA DMC11-AR-DA | DL11-E DL11-C/WA DMC11-AR-FA | DMC11-AL-MD | DMC11-AL-MA
Version 1.1 DUP11-DA
5 DUV11-DA
DECnet/E DMC11-AR-DA DMC11-AR-FA | DMC11-AL-MD | DMC11-AL-MA
Version 1.1
DECnet-VAX DMC11-AR-DA DMC11-AL-MD | DMC11-AL-MA
Version 1.2
DECnet-20 DN20-BA DN21-BA DN21-BB DN21-HA
Version 2.0 (KMC/ (DMC11-AR- (DMC11-AL- (DMC11-AL-
DUP11-DA) FA) MD) MA)
38
DIGITAL EQUIPMENT COMPUTER USERS SOCIETY
LJ
DECUS
INTRODUCTION
DECUS, the Digital Equipment Computer Users Society, was established in March of 1961 to advance the
effective use of DIGITAL computers. It is a not-for-profit users group supported in part by Digital Equipment
Corporation.
OBJECTIVES
mm vd maa AAA RES + ие с
The objectives of the Society are to advance the effective utilization of computers, computer peripheral
equipment, and software manufactured and marketed by Digital Equipment Corporation, by promoting the
interchange of information concerning their uses; advance the art of computation through mutual education
and exchange of ideas and information; establish standards and provide channels to facilitate the exchange of
computer programs among DECUS members; provide feedback to the computer industry on equipment and
software needs; and to reduce the duplication of development efforts.
ORGANIZATION
The Digital Equipment Computer Users Society is a federation of chapters, whose membership is determined
by geographic location. The membership is organized to meet the specific needs of members in its area such
as Symposia and Special User Group activities. The DECUS chapters are:
AUSTRALIAN CHAPTER (Australia, Indonesia, Malaysia, New Zealand, PNG, Singapore, )
e
e EUROPEAN CHAPTER (Europe, Middle East. North Africa, Russia)
e CANADIAN CHAPTER (Canada)
e U.S. CHAPTER (U.S. and All Others)
ACTIVITIES
1. SYMPOSIA
Symposia are sponsored throughout the year by each of the DECUS Chapters and Regional/National User
Groups. These meetings provide an opportunity for users of DIGITAL computers to meet with other users
and with DIGITAL management, engineers, and customer service representatives. They provide a forum for
users to exchange information on technique and approaches to issues of common interest and to provide
feedback to DIGITAL on existing and future products and services. Sessions at the symposia include user-
driven workshops, tutorials, product panels, as well as application/system-specific presentations.
The technical papers and presentations from each symposium are published as DECUS Proceedings.
2. SPECIAL USER GROUPS
DECUS encourages subgrouping of users with common interests and/or geographical proximity.
Special Interest Groups (SIGs) promote the interchange of specialized information for application areas,
subject areas (such as languages), or specific operating systems. A group of users must petition the Chapter
Executive Board for recognition as a Special Interest Group. The group must have a chairman, a DIGITAL
representative, and its organization must meet the guidelines of the Chapter Executive Board.
Geographic subgroupings are formed to service the DECUS members within a specific area although they
may also be based on interests as in SIGs. There are four types of geographic subgroupings:
LUGs — Local User Groups
NUGs — National User Groups
RUGS — Regional User Groups
SLUGs — Student Local User Groups
E O DO
39
3. STANDARDS
DECUS promotes user activity in reviewing DIGITAL standards. Users are given the opportunity to
comment on DIGITAL standards prior to their finalization.
4. PROGRAM LIBRARY
One of the major activities of the users group is the DECUS Program Library. The Library contains
programs written and submitted by users and is maintained and operated separate from the Digital Software
Distribution Center. A wide range of software is available, including languages, editors, numerical functions,
utilities, display routines, and various other types of application software.
MEMBERSHIP
Membership in DECUS is voluntary and is not subject to membership fee. Members are invited to take an
active interest in the Society by contributing to the Program Library, to newsletters, and by participating in
its Special User Groups and Symposia. There are two types of membership: Installation Membership and
Association Membership.
INSTALLATION MEMBERSHIP
An organization, institution, or individual that has purchased, leased or has on order a computer
manufactured by Digital Equipment Corporation is eligible for Installation Membership in DECUS.
An Installation should appoint a person immediately concerned with the use of the computer to act as
delegate to the Society. A delegate receives all official communications and has a vote on DECUS policies
and elections. An organization or company is eligible for as many voting delegates as it has DIGITAL
computers. Each delegate must file an application for Installation Membership.
ASSOCIATE MEMBERSHIP
Any person who is not an appointed Installation Delegate, who has a bona fide interest in DECUS is eligible
for Associate Membership.
Membership status is acquired by submitting the enclosed application to the appropriate Chapter Executive
Secretary for approval by the Chapter Executive Board.
To obtain a membership form for DECUS, please return this form to the appropriate Chapter office listed below.
NAME:
(First) (Last /Family Name)
COMPANY: (INSTALLATION)
ADDRESS 1:
2:
3:
4:
(City Town,State Province. and Zip Postal Code)
COUNTRY:
TELEPHONE: TELEX
I obtained this form from
DECUS OFFICES
DECUS Australia DECUS Canada DECUS Europe DECUS U.S. and |
P.O. Box 384 P.O. Box 11500 P.O. Box 510 Office of the Executive Director
Chatswood Ottawa, Ontario K2H 8K8 12, avenue des Morgines One Iron Way
NSW 2067 Canada CH-1213 Petit-Lancy 1/GE Marlboro, Massachusetts 01752
Australia Switzerland USA
40 DECEMBER 1979
SOFTWARE PROBLEMS OR ENHANCEMENTS
Questions, problems, and enhancements to DIGITAL software should be reported on
a Software Performance Report (SPR) form and mailed to the SPR Center at one of the
following Digital Offices: (SPR forms are availiable from the SPR Center).
Areas Covered
United States;
remainder of Far East,
Middle East, Africa
Latin America
SPR Center
Administrative Services Group, SWS
Р.О. Вох Е
Maynard, Ma 01754
Areas Covered
Japan
SPR Center
Digital Equipment Corp. INTL
3rd Floor Kowa Bldg.
8-7 Sanban Cho
Chiyoda Ku Tokyo 102
Japan
Canada
Digital Equipment Canada
Р.О. Вох 11500
Ottawa, Ontario
Canada K2H 8K8
New Zealand
Digital Equipment N.Z. LTD
Р.О. Вох 17093
Greenlane,
Auckland 5,
New Zealand
United Kingdom, Bahraine,
Egypt, Iraq, Jordan, Kuwait,
Digital Equipment Corp. LTD
Belgium, Holland,
Digital Equipment B.V.
Lebanon, Libya, Qatar, Fountain House Butts Centre Luxemburg KAAP Horndreef 38
Oman, Saudi Arabia, Syria, GB - Reading RG17QN NL - Utrecht/Overvecht
United Arab Emirates, Yemen, England Holland
Arab Republic. |
Australia-Melbourne Digital Equipment Aust. PTY. LTD Sweden Digital Equipment Corp. AB
60 Park Street Englundavagen 7
So. Melbourne Victoria S-171 24 Solna,
Australia 3205 Sweden
Australia-Sydney Digital Equipment Aust. PTY. LTD .
| | - E . AP
123 125 Willoughby Rd. Denmark Digital quipment Corp. APS
Kristineberg 3
Р.О. Вох 491 DK-2100 Copenhagen Z
Crows Nest NSW Denmark
Australia 2065
Brazil Digital Equipment Comercio Ind. . e.
Finland } IE . OY
Rua Batatais 429 Esq AL Campin nan Digital Equipment Corp. O
01423 Jardim Paulista PL16
F - 02201 ESPOO 20
Sao Paulo 0100 Sf 02 01 ES
Brazil Finland
Caribbean De Latin America Norway Digital Equipment Corp. A/S
P. O. Box 11038 Pottenmakerveien 8
Fernando Juncos Sta. N - Oslo 5
Santurce Norway
PR 00910
France Digital Equipment France Austria, East Germany, Digital Equipment Corp. GMBH
18, rue Saarinen France West Germany, Poland, Wallsteinplatz 2
Silic 225 Hungary, Rumania, D - 8 Munich 40
F - 94528 Rungis - Cedex Czechoslovakia, Russia, West Germany
France Bulgaria
Italy Digital Equipment S.P.A. Israel DECSYS Computers LTD.
Viale Fulvio Testi 117
I-20092 Cinisillo Balsamo
Milan,
Italy
4, Yirmiyahou Str.
Р.О. Вох 6359
IL - Tel-Aviv 63505
Israel
Areas Covered
Greece, Portugal,
Spain, Switzerland,
Yugoslavia & Sina
(Morocco, Algeria,
Tunisia, Cyprus,
Turkey, Malta)
SPR Center
Digital Equipment Corp. SA
9, route des Jeunes
1211 Geneva 26
Switzerland
4
DIGITAL EQUIPMENT CORPORATION, Corporate Headquarters: Maynard,
Massachusetts 01754, Telephone: (617)897-5111 —-SALES AND SERVICE
OFFICES: UNITED STATES —ALABAMA, Huntsville ¢ ARIZONA, Phoenix and
Tucson « CALIFORNIA, El Segundo, Los Angeles, Oakland, Ridgecrest, San
Diego, San Francisco (Mountain View), Santa Ana, Santa Clara, Stanford,
Sunnyvale and Woodland Hills « COLORADO, Englewood * CONNECTICUT,
Fairfield and Meriden « DISTRICT OF COLUMBIA, Washington (Lanham, MD) e
FLORIDA, Ft. Lauderdale and Orlando e GEORGIA, Atlanta * HAWAII, Honolulu
* ILLINOIS, Chicago (Rolling Meadows) « INDIANA, Indianapolis « IOWA, Betten-
dorf e KENTUCKY, Louisville « LOUISIANA, New Orleans (Metairie) « MARY-
LAND, Odenton « MASSACHUSETTS, Marlborough, Waltham and Westfield ©
MICHIGAN, Detroit (Farmington Hills) e MINNESOTA, Minneapolis » MISSOURI,
Kansas City (Independence) and St. Louis e NEW HAMPSHIRE, Manchester e
NEW JERSEY, Cherry Hill, Fairfield, Metuchen and Princeton « NEW MEXICO,
Albuquerque « NEW YORK, Albany, Buffalo (Cheektowaga), Long Island (Hunt-
ington Station), Manhattan, Rochester and Syracuse « NORTH CAROLINA,
Durham/Chapel Hill e OHIO, Cleveland (Euclid), Columbus and Dayton » OKLA-
HOMA, Tulsa « OREGON, Eugene and Portland « PENNSYLVANIA, Allentown,
Philadelphia (Bluebell) and Pittsburgh « SOUTH CAROLINA, Columbia ® TEN-
NESSEE, Knoxville and Nashville e TEXAS, Austin, Dallas and Houston * UTAH,
Salt Lake City « VIRGINIA, Richmond + WASHINGTON, Bellevue « WISCONSIN,
Milwaukee (Brookfield) < INTERNATIONAL —ARGENTINA, Buenos Aires e
AUSTRALIA, Adelaide, Brisbane, Canberra, Melbourne, Perth and Sydney e
AUSTRIA, Vienna * BELGIUM, Brussels « BOLIVIA, La Paz « BRAZIL, Rio
de Janeiro and Sao Paulo « CANADA, Calgary, Edmonton, Halifax, London,
Montreal, Ottawa, Toronto, Vancouver and Winnipeg * CHILE, Santiago e
DENMARK, Copenhagen ¢ FINLAND, Helsinki e FRANCE, Lyon, Grenoble
and Paris «e GERMAN FEDERAL REPUBLIC, Cologne, Frankfurt, Hamburg,
Hannover, Munich, Nuremburg, Stuttgart and West Berlin + HONG KONG e
INDIA, Bombay e INDONESIA, Djakarta e IRELAND, Dublin e ITALY, Milan,
Rome and Turin e IRAN, Tehran * JAPAN, Osaka and Tokyo e MALAYSIA,
Kuala Lumpur e MEXICO, Mexico City *« NETHERLANDS, Utrecht « NEW
ZEALAND, Auckland and Christchurch « NORWAY, Oslo « PUERTO RICO,
Santurce » SINGAPORE « SPAIN, Madrid « SWEDEN, Gothenburg and Stock-
holm « SWITZERLAND, Geneva and Zurich « UNITED KINGDOM, Birmingham,
Bristol, Epsom, Edinburgh, Leeds, Leicester, London, Manchester and Reading
* VENEZUELA, Caracas e
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement