Trailing-Edge
-
PDP-10 Archives
-
dec-10-omona-u-mc9
-
beware.603
There are no other files named beware.603 in the archive.
BEWARE FILE FOR 6.03 DISTRIBUTION
Revision: 1
Date: 13 May 1977
Copyright (C) 1977
Digital Equipment Corporation, Maynard, Mass.
The software described herein including, but not limited to, the
functions, program portions and program modifications are the
proprietary information of Digital Equipment Corporation. This
software is furnished only to licensed customers for use on a
designated DECsystem-10 computer system.
Digital hereby places recipient on notice that the software described
herein is governed by the license agreement executed by recipient for
the operating system.
Permitting this software to be copied for any use other than for usage
on the designated DECsystem-10 computer system is a serious violation
of the licensing agreement. Unauthorized use of this software could
have serious legal consequences.
The information in this software is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation.
DEC assumes no responsibility for the use or reliability of its
software on equipment which is not supplied by DEC.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 2
Table of Contents
TABLE OF CONTENTS
This file contains the following information concerning the 6.03
monitor release:
1.0 List of files included in 6.03 release
2.0 Installation instructions for 6.03
3.0 Warnings of known deficiencies in 6.03
4.0 Observable differences between 6.02 and 6.03
5.0 Results of running 6.03 on our in-house systems
and at Field Test sites
6.0 Plans for future monitor releases
7.0 Unbundled Software
1) Virtual Memory
2) DC44 Support
3) DAS78 Support
4) XTCSER Support
5) TSK to TSK Communications Support
6) Networks
BEWARE FILE FOR 6.03 DISTRIBUTION Page 3
List of Files
1.0 LIST OF FILES INCLUDED IN 6.03
The following files constitute the complete 6.03 release:
1) *.MAC New monitor source files (complete except
for unbundled files).
2) 603.MCO Complete description of the monitor changes
which make up 6.03.
3) 603.DDT DDT patch file which can be applied using
the $Y feature of FILDDT to fix problems in
6.03 (see section 4.0).
4) 6497.ddt Patch file for 6.02 monitors for use in a
"DROP BACK" situation.
5) *.COR SOUP correction files for changes to CUSPS
(see section 3).
6) TOPA10.REL The combined .REL files for loading a
regular KA10 monitor.
7) TOPG10.REL The KA10 "LUG" monitor combined .REL files.
8) TOPI10.REL The combined .REL files for loading a
regular KI10 monitor.
9) TOPH10.REL The KI10 "LUG" monitor combined .REL files.
10) MONGEN.EXE Version 50(135) of MONGEN.
11) FGEN.HLP Version 075 of FGEN.HLP for use in
conjunction with MONGEN.
12) CON???.CMD COMPILE command files for assembling
monitors.
13) CMB???.CCL PIP indirect files for making TOP?10.REL.
14) BWR603.RNO This file.
15) BEWARE.603 RUNOFF output from BWR603.RNO.
In addition to the above files that constitute the standard
(bundled) 6.03 monitor release, each customer site will receive
the files associated with those unbundled portions of 6.03 which
the installation is licensed to use. See Section 2.1 of this
document for further details.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 4
Installation Instructions
2.0 INSTALLATION INSTRUCTIONS FOR 6.03
The installation of 6.03 should be straightforward. All
necessary files are on this month's distribution tape. Customer sites
using standard supported monitors may use the library files directly
to load their monitors, for instance TOPI10.REL or TOPH10.REL for KI
systems. Those sites using a non-standard set of feature test
settings will need to run MONGEN and then reassemble the monitor
(probably using CONKI.CMD on a KI). All of these are standard
procedures as documented in MIG603.
The patches given in the next section should be installed in your
6.03 monitor. For your convenience, a machine readable patch file
(603.DDT) is included. To use this patch file proceed as follows:
.GET YURMON (or whatever you called the monitor you built)
.DDT
$"/603/$Y ($=altmode or ESC)
(the patches will now be typed out automatically as they are
made)
^C
.NSAV NEWMON (or whatever name you wish to call your monitor)
However, if your installation lacks adequate core to .GET your monitor
.EXE file, it is possible instead to use FILDDT as follows:
.AS TTY LPT (otherwise $Y to FILDDT outputs to the LPT)
.R FILDDT
FILE: YURMON/P
$"/603/$Y
(the patches are now typed out as above)
^Z
2.1 Unbundled Components of the 6.03 Release
The following components of the 6.03 monitor are unbundled, and
hence are shipped only to properly licensed customers:
Virtual Memory VMSER.MAC,TOPV10.REL,TOPW10.REL
DAS78 D78INT.MAC
DA28 XTCSER.MAC
DC44 TYPSER.MAC
TSK to TSK TSKSER.MAC,TSKSER.DDT
Networks S.P11,DN*.P11,CHK11.P11,DDT11.*,NETLDR.*,NETWRK.DDT
BEWARE FILE FOR 6.03 DISTRIBUTION Page 5
Installation Instructions
If an unbundled option or options other than virtual memory is
included in your monitor, restore the unbundled monitor modules from
the distribution tape, assemble them, and load your monitor using the
following LINK command string:
/NOINITIAL /HASH:6000 YURMON/SAVE, YURMON/MAP = /LOCALS /MAXCOR:60K
COMMON,COMDEV,COMNET,COMMOD,UNB1,...,UNBN,TOPW10/SEARCH/GO
where UNB1 is the first unbundled module, UNB2 is the second unbundled
module, etc. For example, if a KL10 site required the unbundled
modules D78INT and TSKSER, the following procedure would be followed:
.R BACKUP
/INTERCHANGE ;files are written on the tape in interchange mode
/TAPE MTXn ;tape drive where tape containing D78INT is mounted
/RESTORE D78INT.MAC
!
"Done
/TAPE MTXm ;tape drive where tape containing TSKSER is mounted
/RESTORE TSKSER.MAC
!
"Done
/^C
.COMPILE F,S,D78INT,TSKSER
MACRO: F
MACRO: S
MACRO: D78INT
MACRO: TSKSER
.R LINK
*/NOINITIAL /HASH:6000 YURMON/SAVE, YURMON/MAP = /LOCALS /MAXCOR:60K
COMMON,COMDEV,COMNET,COMMOD,D78INT,TSKSER,TOPW10/SEARCH/GO
2.2 .CTL Files
Not all of the .CTL files make .EXE files even though we are only
distributing .EXE files.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 6
Warnings of Known Deficiencies
3.0 WARNINGS OF KNOWN DEFICIENCIES IN 6.03
***********************************************************
* *
* WARNING -- REQUIRED PATCHES *
* *
***********************************************************
There are three required patches to the standard monitor and
there are several required patches to some of the options. See the
appropriate option for details.
In order to have time to test 6.03, we had to stop adding new
MCO's several weeks prior to shipment. During this final test period
we only fixed problems introduced between 6.02 and 6.03. We have
learned that if we wait to ship a monitor until we fix and test "the
last bug", we never ship anything.
3.1 Required Patches To Monitor (In file 603.DDT)
Required Patch 1 - MCO 7122
SYMPTOM: Problems running on-line disk diagnostics which use
DIAG. UUO (DDRPH, DDRPI)
1. STOPCD EUE
2. Hung System
DIAGNOSIS: 1. Call to sleep after DDB is returned will do strange
things if the space is grabbed on interrupt level
by some other process.
2. Sense of a test is backwards, units on other disk
controllers will not start seeks when they should.
CURE:
FILIO$: DIASCP-3/SETZ T1, SETZB T1,F
PIKPOS+1/CAMN P1,DIACHN CAME P1,DIACHN
BEWARE FILE FOR 6.03 DISTRIBUTION Page 7
Warnings of Known Deficiencies
Required Patch 2
SYMPTOM: NXM's. Random locations get wiped out.
DIAGNOSIS: COPVJD can attempt to copy location to the high segment
when it is paged out.
CURE: Remove offending call to COPVJD.
COMCON$:
SAVEXE 13/ PUSHJ P,COPVJD JFCL
Required Patch 3 - MCO 7150
SYMPTOM: Stopcd BAC when turning around a paged IPCF message.
DIAGNOSIS: Trying to return too many words.
CURE: Change HLRZ to HLRE.
IPCSER$:
REMPAK+2/HLRZ T1,.IPCFP(T2) HLRE T1,.IPCFP(T2)
3.2 Required Patches To CUSPS
6.03 MODIFIED/DEPENDENT CUSPS
DAEMON FILDAE INITIA
MACTEN OMOUNT PLEASE
SNOOPY SYSDPY SYSERR
SYSTAT TATTLE UMOUNT
Substantive 6.03 dependent changes have been made to the
preceding Cusps making them required for 6.03. The release of version
6.03 of TOPS-10 consits of the Monitor Distribution Tape and the April
Cusp Distribution Tape. Note that JOBDAT, SCAN, WILD, and C for 6.03
are contained in the April Cusp Release.
The following patch to OMOUNT is required to support RP06's (See
file OMOUNT.COR):
File 1) DSKN:OMOUNT.26A[10,675] created: 0454 11-MAR-1977
File 2) DSKN:OMOUNT.MAC[10,675] created: 0457 11-MAR-1977
1)98 HRR B,FSTEMP ;BLOCK NUMBER
1) SUSET. B,
****
2)98 ;** GETUNB+11 [REPLACE 1 INSTRUCTION] 15-OCT-76
2) IOR B,FSTEMP ;BLOCK NUMBER
2) SUSET. B,
**************
BEWARE FILE FOR 6.03 DISTRIBUTION Page 8
Warnings of Known Deficiencies
The following patch to GALAXY release 1 is required to make
QUASAR work with the 6.03 monitor (Note that with this patch, QUASAR
does not work with 6.02) (See file QSRIPC.COR):
File 1) YELB:QSRIPC.1[10,675] created: 1417 03-JULY-1975
File 2) DSKN:QSRIPC.MAC[10,675] created: 0544 11-MAR-1977
1)8 MOVEI S1,IPCRSZ ;LOAD THE HEADER SIZE
****
2)8 ;** IPPCR.4+2 [ADD 2 INSTRUCTIONS] 11-MAR-77
2) MOVX S1,IP.CFT ;TRUNCATE IF TOO LONG
2) IORM S1,IPCFLG(AP) ;THROW AWAY WHAT WE'RE NOT PREPARED TO HANDLE
2) MOVEI S1,IPCRSZ ;LOAD THE HEADER SIZE
**************
In 6.02 and previous monitors, the monitor determined whether or
not a job was a "batch" job by looking to see whether it was
controlled by a job running "BATCON". This was both slow and
inflexible. In 6.03, if bit 2 (UU.BJP) is on in the OPEN block for a
PTY (privileged job only), then any job which is logged-in on that PTY
is condidered to be a batch job. Installations running MPB should put
up BATCON version 13 before installing 6.03. A new version of GALAXY
(including BATCON) will be released around the same time as 6.03. The
following must be applied to field-image BATCON (V 100) in order for
it to run under 6.03 (No .COR is supplied for this patch).
At FIRE.1+4,
change MOVSI A,(1B0)
to MOVSI A,(1B0+1B2)
BATCON version 102 (GALAXY) will run correctly under 6.03.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 9
Warnings of Known Deficiencies
3.3 Recommended Patches
This is MCO 7128 (See file CHKACC.DDT).
SYMPTOM: If the monitor is built with M.XFFA non-zero, CHKACC
doesn't work for privileged programs.
CURE: If the program doing the CHKACC is privileged and
M.XFFA is non zero, do the normal checking.
PATCH:
FILFND$:
ACCCHK 15/ SKIPN FDAJOB JRST PAT 1 _
PAT+1/ 0 PUSHJ P,PRVJO
PAT+2/ 0 CAIA
PAT+3/ 0 SKIPN PAT\ 0 M.XFFA
PAT+4/ 0 SKIPN FDAJOB
PAT+5/ 0 JRST ACCCH0
PAT+6/ 0 JRST ACCCHK 17
PAT+7/ 0 PAT:
PATSIZ/ MOVEI T1,CONPPB+42 MOVEI T1,PAT
The 6.03 monitor requires that ECO number 1 be installed in the
LP100. If this ECO is not installed, the monitor will loop whenever
the LPT connected to the LP100 is turned off. The following patch
will allow the monitor to run even though ECO number 1 has not been
installed in the LP100. However, this patch disables all of the
additional features available in the LP100 LPT interface. All sites
which have LP100's should have field service install ECO number 1 at
their earliest possible convenience (See file LP100.DDT).
LPTSER$:
LPTOUT 5/ TRO U,ERRPNT+6 $Q-CO.FEN
LPTREL 3/ MOVEI U,RTEVMI+1 $Q-CO.FEN
LPTSCO 2/ IORI U,DSKSCN# JFCL
LPTST1/ TRO U,HNGST7#+5 $Q-CO.FEN
LPTRTI 1/ TRO U,HNGST7#+5 $Q-CO.FEN
BEWARE FILE FOR 6.03 DISTRIBUTION Page 10
Warnings of Known Deficiencies
If the MONGEN parameter is set so that the scheduler uses the
non-class scheduling algorithim, the following monitor patch is
required (See file SCHED1.DDT):
SCHED1$:
NXTJB1+3/ MOVEI F,0 JRST PAT
PAT/ 0 PUSHJ P,INRNQ
PAT+1/ 0 JRST CKJB0A
PAT+2/ 0 MOVEI F,0
PAT+3/ 0 JRST NXTJB1+4
PAT:
PATSIZ / MOVEI T1,JUNK MOVEI T1,PAT
Without this patch, you may get NTE stopcodes during DAEMON device
error reporting.
In addition, the SCHED. UUO gives an error return which causes
LOGIN to issue an error message. Also, if a user logs onto the system
on a DN87, he/she is logically LOCATEd at the DN87 rather than the
central site and spooled output would be queued for the non-existant
LPT on the DN87. The following FILCOM represents edits 632 and 633 to
LOGIN. Edit 632 prevents LOGIN from attempting to do SCHED. UUOs if
ST%NCS (not class scheduler) is set in CNFST2. Edit 633 causes LOGIN
to LOCATE the user at the central site if 1) the user is logging in on
a node other than the central site, 2) the node does not have an LPT,
and 3) the user has not specified a LOCATE switch either on the LOGIN
line or in his SWITCH.INI (See file LOGIN.COR).
File 1) DSKN:LOGIN.MAC[10,675] created: 0528 01-FEB-1977
File 2) BLKF:LOGIN.MAC[7,1342] created: 1344 30-SEPT-1976
1)1 ;Copyright (C) 1969, 1970, 1971, 1972, 1973, 1974, 1975, 1976, 1977 Digital
1) ; Equipment Corporation, Maynard, Mass.
****
2)1 ;Copyright (C) 1969, 1970, 1971, 1972, 1973, 1974, 1975, 1976 Digital
2) ; Equipment Corporation, Maynard, Mass.
**************
1)1 VEDIT==633
1) VWORD==BYTE (3)VWHO(9)VLOGIN(6)VMINOR(18)VEDIT
****
2)1 VEDIT==631
2) VWORD==BYTE (3)VWHO(9)VLOGIN(6)VMINOR(18)VEDIT
**************
1)2 ST%NCS==1B16 ;[632] ON IF NOT CLASS SYSTEM SCHEDULER
1) .NDRCI==5 ;[633] REQUEST NODE CONFIGURATION INFORMATION
1) .STDEF==33 ;[620] SETUUO CODE FOR DEFAULT STUFF
****
2)2 .STDEF==33 ;[620] SETUUO CODE FOR DEFAULT STUFF
**************
1)3 ;632) DON'T TRY TO SET SCHEDULER CLASS QUOTAS IF 6.03 SCHEDULER
1) ; RUNNING IN WMU MODE
1) ;633) LOCATE USER AT CENTRAL SITE IF LOGGING IN ON A NODE WITHOUT
1) ; AN LPT (DN87)
BEWARE FILE FOR 6.03 DISTRIBUTION Page 11
Warnings of Known Deficiencies
1) ;***END OF REVISION HISTORY
****
2)3 ;***END OF REVISION HISTORY
**************
1)60 TXNN T1,ST%NCS ;[632] SKIP THIS IF 6.03 SCHEDULER IN WMU MODE
1) TXNN T1,ST%SCD ;[425] DOES MONITOR HAVE SCHED. UUO?
****
2)60 TXNN T1,ST%SCD ;[425] DOES MONITOR HAVE SCHED. UUO?
**************
1)92 TXNN T1,ST%NCS ;[632] SKIP ON IF NOT CLASS SCHEDULER
1) TXNN T1,ST%SCD ;[425] DOES MONITOR HAVE SCHED. UUO?
****
2)92 TXNN T1,ST%SCD ;[425] DOES MONITOR HAVE SCHED. UUO?
**************
1)98 USRST5: SKIPL T1,U.STA ;[633] GET STATION
1) JRST LGNLUF ;[633] ONE WAS SPECIFIED, USE IT
1) MOVEI T1,.GTLOC ;[633] GETTAB FOR NODE NUMBER OF CENTRAL SITE
1) GETTAB T1, ;[633] GET CENTRAL SITE NODE NUMBER
1) JRST USRS5A ;[633] MONITOR MUST NOT SUPPORT NETWORKS
1) HRROI T2,.GTLOC ;[633] THIS JOB'S LOCATION
1) GETTAB T2, ;[633] GET THAT
1) JRST USRS5A ;[633] NO NETWORK SOFTWARE
1) CAMN T1,T2 ;[633] ALREADY LOCATED AT THE CENTRAL SITE?
1) JRST USRS5A ;[633] YES, NO POTENTIAL PROBLEMS THEN
1) MOVEM T2,NODLOC ;[633] STORE THIS JOB'S LOCATION IN NODE BLOCK
1) MOVEI T2,4 ;[633] LENGTH OF THE ARGUMENT BLOCK
1) MOVEM T2,NODLEN ;[633] STORE IN NODE UUO ARGUMENT BLOCK
1) MOVEI T2,.TYLPT ;[633] DEVICE TYPE
1) MOVEM T2,NODDEV ;[633] STORE THAT IN THE ARGUMENT BLOCK
1) MOVE T2,[.NDRCI,,NODBLK];[633] NODE UUO ARGUMENT
1) NODE. T2, ;[633] GET NODE CONFIGURATION INFORMATION
1) JRST USRS5A ;[633] NOT IMPLEMENTED?
1) HLRZ T2,NODDEV ;[633] NUMBER OF LPT'S AT THIS NODE
1) JUMPN T2,USRS5A ;[633] JUMP IF THERE ARE SOME
File 1) DSKN:LOGIN.MAC[10,675] created: 0528 01-FEB-1977
File 2) BLKF:LOGIN.MAC[7,1342] created: 1344 30-SEPT-1976
1) ;[633] IF NO LPT'S, LOCATE JOB AT CENTRAL SITE
1) LGNLUF: MOVEI M,[ASCIZ /%LGNLUF LOCATE UUO failed.
****
2)98 USRST5: SKIPGE T1,U.STA ;GET STATION
2) JRST USRS5A ;[620] NONE SPECIFIED
2) LGNLUF: MOVEI M,[ASCIZ /%LGNLUF LOCATE UUO failed.
**************
1)105 NODBLK:
1) NODLEN: BLOCK 1 ;[633] LENGTH OF NODE UUO ARGUMENT BLOCK
1) NODLOC: BLOCK 1 ;[633] NODE NUMBER
1) BLOCK 1 ;[633] RESERVED ARGUMENT
1) NODDEV: BLOCK 1 ;[633] NUMBER OF DEVICES,, DEVICE TYPE
1) PRGEND
****
2)105 PRGEND
**************
BEWARE FILE FOR 6.03 DISTRIBUTION Page 12
Warnings of Known Deficiencies
The following patch to SOS is required to make SOS work
correctly with the File Daemon:
File 1) WORK:SOS.OLD[10,2162] created: 0953 09-FEB-1977
File 2) WORK:SOS.MAC[10,2162] created: 1052 21-MAR-1977
1)1 ;*** COPYRIGHT 1973,1974 DIGITAL EQUIPMENT CORP., MAYNARD, MASS. ***
****
2)1 ;EDIT TO DELETE THE PROTECTION 4XX MAGIC FOR THE FILE DAEMON
2) ;*** COPYRIGHT 1973,1974 DIGITAL EQUIPMENT CORP., MAYNARD, MASS. ***
**************
1)25 TRNE FL,READOF ;IF READ ONLY, LOOKUP IS ENUF
1) JRST GUDPRV
1) LDB T2,[POINT 9,XBLOCK+2,8]
1) CAIL T2,400 ;CHECK IF OK TO EDIT
1) SKIPE NEWNAM ;NO GOOD IF NO OUTPUT SPEC
1) GUDPRV: SKIPA T1,PTHADR ;ATTN PROGRAM BUMMERS
****
2)25 LDB T2,[POINT 9,XBLOCK+2,8] ;GET PROTECTION
2) GUDPRV: SKIPA T1,PTHADR ;ATTN PROGRAM BUMMERS
**************
1)58 FIXPRT: MOVEI T2,200 ;GENERATE XOR CONST
1) CAIGE T1,300
1) IORI T2,100
1) XOR T1,T2 ;ZAP IT
1) POPJ P, ;RETURN WITH PROT IN T1
1)59 NSCAN: TLNE FL2,AUTOF ;SPECIAL IF AUTO MODE
****
2)58 FIXPRT: POPJ P,
2)59 NSCAN: TLNE FL2,AUTOF ;SPECIAL IF AUTO MODE
**************
There is a bug in PIP which became apparent when a monitor bug
was fixed in 6.03 which causes a ?FILE NOT FOUND error when trying to
copy multiple files, some or all of which are in a LIB:, and DSK: was
specified as the input device.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 13
Warnings of Known Deficiencies
A bug in LINK 3A's Polish fixup processing has been discovered
that must be corrected before any monitor that has been assembled with
MACRO 52 can be loaded. The major symptom of this bug is that many
locations in the loaded monitor will be off by about 340000, although
other errors are possible.
The correction for this problem is edit 572 to LINK. This edit
was first distributed in LNK3A.BWR, the beware file shipped with the
LINK 3A release. The same edit was also shipped in a more convenient
form with the MACRO 52 release as the following files:
LNK572.PCO FILCOM and problem description.
LNK572.COR Correction file for direct insertion of the
edit into the LINK sources with FED.
LNK572.MAC Test program to verify that the edit is
properly installed.
We strongly recommend that this edit be installed in LINK 3A
(preferably with LNK572.COR and the FED program) before any attempt is
made to load monitors that have been assembled with MACRO 52. Note
that this edit is not needed if the monitor is assembled with MACRO
50A, but that no future monitors, LIR'S, or monitor SPR answers are
guaranteed to assemble with MACRO 50A.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 14
Observable Differences between 6.02 and 6.03
4.0 OBSERVABLE DIFFERENCES BETWEEN 6.02 AND 6.03
4.1 General Warnings
In the standard monitor, on run - queue time is no longer
calculated to save monitor overhead. Thus, the .GTTRQ GETTAB always
returns a zero. However, the code was not removed from SCHED1 but was
simply jumped around and may be reinstalled by changing the JRST to a
JFCL.
In the 6.03 monitor, in support of the accounting project,
several new entries have been added to file retreival information
blocks (RIBS). The following patch (MCO 6497) must be applied to your
6.02 monitor to enable it to read files created by the 6.03 monitor.
This patch is included as a patch file (6497.DDT) on the distribution
tape and may be installed in your 6.02 monitor by following the
procedures outlined in section 2 above (substituting "6497" for
"603"). All sites upgrading from 6.02 or 6.02A to 6.03 should install
this patch in their 6.02 monitor to insure the ability to drop back in
the event of difficulties with the 6.03 monitor.
FILUUO$:
PAT/ 0 GTLPT: PUSHJ P,SPTRW
GTLPT+1/ 0 HLRE T2,T1
GTLPT+2/ 0 SUB T1,T2
GTLPT+3/ 0 MOVE T2,-1(T1)
GTLPT+4/ 0 POPJ P,
GTLPT+5/ 0 PAT:
ALLP0B 1/ MOVE T1,CHNQUL(F) PUSHJ P,GTLPT
ALLP0B+2/ MOVE T2,DLC2#+12(T1) JFCL
FILIO$:
PTRBL4 2/ MOVE T1,CHNQUL(F) PUSHJ P,GTLPT
PTRBL4+3/ SKIPE DLC2#+12(T1) SKIPE T2
EXTRB1 7/ MOVE T1,CHNQUL(F) PUSHJ P,GTLPT
EXTRB1+10/ MOVE T2,DLC2#+12(T1) JFCL
PATSIZ/ MOVEI T1,GTLPT MOVEI T1,PAT
The 6.03 monitor is designed for use with RSX20F as the front end
operating system. Booting RSX20F from disk requires that a BM873YH
Rom module be installed in the console front end. (booting from
DECtapes works with the existing Rom). This is an ECO to be installed
in all KL10 systems. RSX20F also ignores that the DTE interrupt at
priority level 6. Some 1080's have the DTE connected to level 4.
RSX20F will notice this condition and print an error message. To
correct this, you must have field service modify the jumper which
selects the DTE interrupt priority. For more information, contact
your local Field Service.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 15
Observable Differences between 6.02 and 6.03
On KL10 based systems, it may, under certain circumstances, be
desirable to run the monitor with KLDCP and/or RSX10F rather than
RSX20F. Since the monitor expects to be running with RSX20F as the
front end software, it starts up the so called "primary communications
protocol" which KLDCP does not understand. To disable this the
following patch should be installed in the monitor:
PPCPAT/ PUSHJ P,STMPPC JFCL
Note that if the monitor is patched in this fashion, it will
still work with RSX20F but RSX will not automatically attempt to cause
the monitor to reload itself whenever it detects that the KL10 has
stopped. Also, the front end device will not be available.
It is recommended that the RSX20F parser not be used while the
system is time-sharing.
Until 6.03 there was a monitor bug which allowed jobs which had
at some point done a HIBER UUO with the wake enable bits set to do a
SLEEP UUO and be awakened by the occurrence of one of the conditions
specified in the HIBER UUO. This has been fixed so that now the only
event which will cause a return from the SLEEP UUO is the expiration
of the specified sleep time. This may break programs that relied on
this "feature of the SLEEP UUO".
In support of the majority of terminals manufactured today, the
default initial setting for terminals assumes that ASCII codes 175 and
176 are generated by typing left and right curley braces rather than
by depressing a key labeled ALTMODE or ESC(ape). Thus, the default
action is to pass 175 and 176 on to the program rather than converting
them to 33. This default may inconvenience users of model 33 and 35
teletypes and possibly other terminals which generate these codes when
the ALTMODE or ESCAPE key is depresssed. The monitor default may be
overridden by defining the parameter TTYALT,1 in the "DEFINE
SYMBOL,VALUE" portion of the MONGEN dialog. Specific hard wired
terminal defaults may be specified by running INITIA on each line
terminated by such a terminal and including in TTY.INI "ALTMODE" for
that line.
If the system configuration includes both disks and magtapes on
RH20 channels, the disks must be on lower numbered RH20s than the
magtapes; e.g., if the system has 2 RH20s for disks and 1 RH20 for
magtapes, the disks should be on RH20s number 0 and 1 and the magtapes
should be on RH20 number 2. There is a bug in 6.03 which limits the
system to a maximum of 5 RH20 channels in slots 0,1,2,3,5 (five).
Sites who do not wish to use the class scheduler, may turn it off
by defining the symbol M.CLSS,0 in the "DEFINE SYMBOL,VALUE" portion
of the MONGEN dialogue.
The 6.03 monitor supports two channels/controllers, each
connected to one of the dual ports on a string of RP04 and/or RP06
disk pack drives. This can substantially increase disk I/O throughput
since if one channel/controller is busy transfering on one drive, I/O
BEWARE FILE FOR 6.03 DISTRIBUTION Page 16
Observable Differences between 6.02 and 6.03
can be started on another drive on the second channel/controller.
However, it has been discovered that hardware difficulties arise if an
attempt is made to take advantage of this feature using RP04s equipped
with dual port kits containing the M7775 board. Consult field service
about upgrading your RP04 dual port kits to the M7787 board.
The 6.03 monitor contains support for a Macro Interpreted Command
facility. Distributed with the 6.03 monitor is a program called MIC
which implements a powerful macro command language. This program was
developed by Hatfield Polytechnic Institute and is being distributed
by Digital as a convenience to our customers. The support level for
MIC will be category C. However, if SPRs are submitted to Digital
they will be forwarded to those persons interested in MIC maintenence
and development. The documentation included on the distribution tape
describing MIC and its features is believed to be essentially correct
except that the monitor command to execute a MIC macro is "DO" rather
than "/" as stated. To summarize, the TRMOP.'s which have been
implemented in the monitor to support MIC (and similar applications)
will receive category A support but the MIC program will not be
supported by DECsystem-10 software development, support, or
maintenence personel.
The 6.03 monitor requires version 4 of the DX10 microcode for the
proper functioning of TU70/TU71 magtape drives.
When BACKUP is doing a save it requests the monitor not to do any
error recovery, just to inform it whenever a tape error is detected.
There was a bug in 602/602A which ignored this request by BACKUP, so
that error retry was attempted. This bug has been fixed in 603, so
that any soft error will immediately be passed on to BACKUP. BACKUP
then types out a message about parity error on tape, and rewrites the
same data in the next block on tape, with 1 bit on indicating that it
is a retry record. This does not mean that the tape drive is bad,
since soft errors are to be expected on mag tapes.
When listing magtape statistics for a TU70 SYSERR may print
incorrect numbers for tape position before error, and number of
characters in the bad record. This is due to a monitor bug which
causes these numbers not to be stored on an error which is detected as
hard without any retry attempted. The problem is fixed by MCO 7158
which will be in the 603A Soup release.
For those customers who have developed their own device service
routines, two new words have been added to the short device data block
(DDB). These new words are called DEVESE and DEVHCW. Also, a new
entry point has been added to the device dispatch vector (DDVO=-4).
These words and the new entry point must be included in the DDB's and
dispatch vector for all device service routines. Thus, such sites
should make equivalent changes to their device service routines before
attempting to incorporate them in the 6.03 monitor.
As with previous versions, SYSCHK halts if it detects
non-contiguous memory modules even though the monitor does not require
contiguous memory. However, this version actually checks up to 4096K.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 17
Observable Differences between 6.02 and 6.03
If this occurs, either fix the memory or say no to the SYSCHK
question.
DAEMON must be run without DSKFUL PAUSE set.
The file MACROS which had been used in the assembly of INITIA has
been merged into MACTEN. INITIA contains a "SEARCH MACTEN" line. The
correct version of MACTEN.MAC and MACTEN.UNV is 2(25).
4.2 Differences Observable to the User
Because a number of commands have been added to the 6.03 monitor,
the minimum number of characters required for a unique abbreviation of
a command has changed for some commands. For example, the GET command
requires that at least "GE" be typed for it to be unique rather than
just "G" as in 6.02.
The interpretation of the owner protection field in the high
order octal digit of the 3 digit octal protection code has been
changed in the 6.03 monitor. See FILDAE.DOC for an explanation of the
new actions which the monitor takes if the owner protection field is 4
or greater.
If a $ (dollar sign) is not echoed when the ALTMODE or ESCAPE key
is depressed on a user's terminal, the user should type the following
monitor command:
.SET TTY ALTMODE
4.3 Differences Observable to the Operator
There are three new monitor support programs distributed with the
6.03 monitor. These are DTELDR, FILDAE and MIC. The operator may
wish to include these in the OPR.ATO file so that they are started
automatically on a system reload. See the DOC files for DTELDR,
FILDAE and MIC for more details.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 18
Results of Running 6.03 on our In-house Systems
5.0 RESULTS OF RUNNING 6.03 ON OUR IN-HOUSE SYSTEMS AND AT
FIELD TEST SITES
We have run 6.03 on our in-house software development and
marketing systems, including KA10, KI10, and KL10 configurations, for
more than two weeks with no unresolved crashes. Our in-house
experience with preliminary versions of 6.03 covers more than six
months of heavy usage with steadily increasing reliability.
Fifteen field-test sites have run several early versions of 6.03.
All field test sites report 6.03 to be more reliable than 6.02.
We have run the final version of the 6.03 KI10 "LUG" monitor for
one shift during which we successfully edited, assembled, and CREFed
monitor source files.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 19
Plans for future 6.03 monitor releases
6.0 PLANS FOR FUTURE 6.03 MONITOR RELEASES
Products as large and complex as a major release of TOPS-10
always contain some deficiencies when first distributed. As we learn
of problems, fixes are published in the BULLETIN and the DISPATCH.
After collecting a set of important patches, we produce an updated
monitor (sometimes known as a SOUP monitor) containing all important
fixes and subject this monitor to careful testing. Such monitors are
distinguished from a major release (with new features) by appending a
letter to the name of the original release. 6.03A is not expected
before the Dec 1977 distribution tape. If there is any need for a
6.03B, it is not likely to appear for at least four months after
6.03A.
It is also planned that a Limited Interim Release (LIR) will be
provided to the recipients of 6.03 which, when applied to the 6.03
class scheduler, will enhance its performance and functionality. It
is not currently known what the schedule for the release of this LIR
will be. There will also be a NETWORK.LIR.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 20
Unbundled Software
7.0 UNBUNDLED SOFTWARE
7.1 SUPPORT FOR UNBUNDLED OPTION - VM
7.1.1 LIST OF FILES INCLUDED IN THE 6.03 VM SUPPORT PACKAGE
The following files constitute the complete 6.03 virtual memory
support package:
1) VMSER.MAC 6.03 monitor source file which implements
virtual memory.
2) TOPV10.REL The combined .REL file for KI10 virtual
memory monitors analogous to TOPI10.REL.
3) TOPW10.REL The combined .REL file for KL10 virtual
memory monitors.
4) CONVI.CMD Command files for assembling KI10 virtual
CMBVI.CCL Memory monitors and creating combined .REL
files.
5) CONVL.CMD Command files for assembling KL10 virtual
CMBVL.CCL Memory monitors and creating combined .REL
files.
6) MAKPFH.MAC Page fault handler.
MAKPFH.EXE
PFH.VMX
7) DDT.VMX VMDDT.
8) GET.* User mode program to .GET virtual memory
GET2.RND executable programs.
7.1.2 INSTALLATION INSTRUCTIONS
Installation of virtual memory monitors is very straightforward
and similar to non-VM monitors. The differences are mainly obvious
file substitutions such as TOPV10.REL or TOPW10.REL in place of
TOPI10.REL.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 21
Unbundled Software
7.2 SUPPORT FOR UNBUNDLED OPTION - DC44
7.2.1 LIST OF FILES INCLUDED IN THE 6.03 DC44 SUPPORT PACKAGE
The following file constitutes the complete 6.03 DC44 support
package:
1) TYPSER.MAC 6.03 monitor source file for DC44 interface.
7.2.2 INSTALLATION INSTRUCTIONS
The particular instructions that apply in order to include DC44
support are:
Assemble TYPSER.MAC by typing the following command string:
COMPILE F,S,TYPSER
Then LINK your monitor following the procedure described in section
2.1.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 22
Unbundled Software
7.3 SUPPORT FOR UNBUNDLED OPTION - DAS78
7.3.1 LIST OF FILES INCLUDED IN THE 6.03 DAS78 SUPPORT PACKAGE
The following files constitute the complete 6.03 DAS78 support
package:
A. MONITOR CODE
1) D78INT.MAC 6.03 monitor source file for DAS78 interface.
B. DAS78 PDP-11 CODE
1) DAS78.CTL Control file to assemble the PDP-11 code.
2) DAS78.P11 Sources for DAS78 PDP-11 code.
3) DAS78.BIN Executable DAS78 PDP-11 code.
4) DAS78.EXE DDT11 file for the PDP-11 code.
C. DAS78 SPOOLER - USED TO SHIP FILES TO/FROM THE DAS78
1) D78SPL.CTL Control file to assemble D78SPL.
2) D78SPL.MAC Source code for D78SPL.
3) D78SPL.EXE Executable code.
D. DAS78 QUEUE AND QMANGR - FOR USE WITH D78SPL
1) QUE.CTL Control file to assemble QMANGR and QUEUE.
2) QUEUE.D78 Source code for DAS78 modified QUEUE.
3) QUEUE.EXE Executable code.
4) QMANGR.D78 Source code for DAS78 modified QMANGR.
5) QMANGR.EXE Executable code.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 23
Unbundled Software
E. SPOOL - DAS78 MODIFIED LPTSPL
This program is for use when using a 2780 as a Remote Batch
Station to the DECsystem-10. This modified LPTSPL also can
be used to print on the local printer.
1) SPOOL.CTL Control file for assembling a DAS78 LPTSPL.
2) SPOOL.D78 Source code for DAS78 modified SPOOL.
3) LPTSPL.EXE Executable code.
F. SPRINT - DAS78 MODIFIED SPRINT
This program is for use when using a 2780 as a Remote Batch
Station to the DECsystem-10. This modified SPRINT will also
be used to read cards from the local card reader.
1) SPRINT.CTL Control file for assembling a DAS78 SPRINT.
2) SPRINT.D78 Source code for DAS78 modified SPRINT.
3) SPRINT.EXE Executable code.
G. PDP-11 DEBUGGING PROGRAM
1) DDT78.MAC Source for DDT78 (This is a modified version
of DDT11).
2) DDT78.EXE Executable code.
3) DDT78.RNO DDT78 document.
H. MODEM DIAGNOSTIC
1) DQMODM.HLP Short document on how to use DQMODM.
2) DQMODM.BIN Executable code.
I. DOCUMENTS
1) DAS78.RNO The DAS78 "Cookbook" - WARNING: Preliminary
version.
2) D78MNT.RNO Installation hints and other useful
information.
3) DAS78.RND Changes from 6.02 to 6.03.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 24
Unbundled Software
J. MISCELLANEOUS PROGRAMS
1) C.MAC Needed for assembling QUEUE.
2) SCNMAC.MAC Needed for assembling QUEUE.
3) HELPER.REL Needed for LPTSPL, SPRINT, and QUEUE.
4) QUEUER.REL Needed for LPTSPL, SPRINT, and QUEUE.
5) SCAN.REL Needed for QUEUE (V4).
6) WILD.REL Needed for QUEUE (V5).
Note: The MACDLX assembler is required to assemble DAS78.P11,
and the BOOT11 bootstrap is required to load code from the -10 into
the -11 memory. Both these programs will be found on the main
(bundled) 6.03 monitor distribution tape.
7.3.2 INSTALLATION INSTRUCTIONS
The particular instructions that apply in order to include DAS78
support are:
Assemble D78INT.MAC by typing the following command string:
COMPILE F,S,D78INT
Then LINK your monitor following the procedure described in section
2.1.
Carefully read D78MNT.RNO, DAS78.RNO, and DAS78.RND for
installation instructions concerning the -11 portion of the DAS78 as
well as installation instructions for the D78SPL spooler. Note that
command formats are somewhat different from 6.02.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 25
Unbundled Software
7.4 SUPPORT FOR UNBUNDLED OPTION - XTCSER
7.4.1 LIST OF FILES INCLUDED IN THE 6.03 XTCSER SUPPORT PACKAGE
The following file constitutes the complete 6.03 XTCSER support
package:
1) XTCSER.MAC 6.03 monitor source file for DA28 driver.
7.4.2 INSTALLATION INSTRUCTIONS
The particular instructions that apply in order to include XTCSER
support are:
Assemble XTCSER.MAC by typing the following command string:
COMPILE F,S,XTCSER
Then LINK your monitor following the procedure described in section
2.1.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 26
Unbundled Software
7.5 SUPPORT FOR UNBUNDLED OPTION - TSK TO TSK COMMUNICATIONS SUPPORT
7.5.1 LIST OF FILES INCLUDED IN THE 6.03 TSKSER SUPPORT PACKAGE
The following files constitute the complete 6.03 TSK to TSK
communications support package:
1) TSKSER.MAC 6.03 monitor source file for TSK to TSK
communications.
2) TSKSER.DDT Patch file for MCO 7125.
7.5.2 INSTALLATION INSTRUCTIONS
The particular instructions that apply in order to include TSKSER
support are:
Assemble TSKSER.MAC by typing the following command string:
COMPILE F,S,TSKSER
Then LINK your monitor following the procedure described in section
2.1 and apply TSKSER.DDT along with 603.DDT.
7.5.3 WARNING OF KNOWN DEFICIENCIES IN TSKSER
Please keep in mind that DC75's were designed only to communicate
with DC72's. Unless FT.ANF is non-zero, DC75's will not be able to
copy binary TSKSER data over the DL10.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 27
Unbundled Software
7.5.4 TSKSER Required Patches
Local tasks were broken by a recent bug fix to remote tasks.
Without the following patch, end of file will be set on the first
input UUO (See file TSKSER.DDT).
"/MCO 7125 - FIX LOCAL TASKS/
TSKSER$:
TSKIN1 4/ TLNN LTINIT+401 TLNN S,IOSCON+IOSTSL
TSLDRQ-1/ JRST DRQMBF JRST PAT
PAT/ 0 TLNE S,IOSCON
PAT+1/ 0 PJRST DRQMBF
PAT+2/ 0 POPJ P,
PAT+3/ 0 PAT:
RMVTSK 21/ PUSHJ P,STOIOS PUSHJ P,PAT
PAT/ 0 TLZ S,IOSTSL
PAT+1/ 0 PJRST STOIOS
PAT+2/ 0 PAT:
PATSIZ/ MOVEI T1,JUNK MOVEI T1,PAT
BEWARE FILE FOR 6.03 DISTRIBUTION Page 28
Unbundled Software
7.6 SUPPORT FOR UNBUNDLED OPTION - NETWORK
7.6.1 LIST OF FILES INCLUDED IN THE 6.03 NETWORK SUPPORT PACKAGE
The following files constitute the entire 6.03 NETWORK support
package
1) *.P11 PDP-11 source files.
2) NETBLD.CTL Sample .CTL file.
3) DDT11.* DECsystem-10 program for on-line debugging of
the PDP-11 or -11 crash dumps.
4) NETLDR.* Remote node loader.
5) NEWDN8.* Technical information.
6) NETWRK.DDT Patch file for MCO's 7123 and 7124.
Note: MACDLX.EXE V27A must be used to assemble network software.
It is included as part of the main (bundled) 6.03 monitor package.
All TOPS-10 (*.MAC files) support for networks is in the bundled
monitor package.
7.6.2 INSTALLATION INSTRUCTIONS
Refer to the System Programming Procedures section of the
software notebooks (documents DC75NP to DN87). Also see NEWDN8.DOC
for changes to those documents.
MCO's 7123 and 7124 are fixes to TOPS-10 and must be made. Apply
NETWRK.DDT along with 603.DDT.
7.6.3 WARNINGS OF KNOWN DEFICIENCIES IN NETWORK SUPPORT
N.B. Many problems described refer to TOPS-10 modules, not just
DN87 modules.
1) Whenever a UUO is executed that changes a TTY parameter,
characteristics messages have to be exchanged between TOPS-10
and the PDP-11 controlling that terminal. Unfortunately,
there is a race condition in the terminal protocol that is
exercised when several parameters are changed in a short time
by TRMOPs or other UUOs. The fix to this is complex and
probably will not be in 6.03A. One way around the problem is
to pause a short time between TRMOPs to let the message
exchange occur.
BEWARE FILE FOR 6.03 DISTRIBUTION Page 29
Unbundled Software
2) Late in testing we discovered that COMMON will not assemble
for a system having DN87S's and no DC75NP's or DN87's. The
simplest way around this is to tell MONGEN during the network
dialogue that you have one DN87 on DL10 port 0.
Required Patches (See file NETWRK.DDT):
1. When a remote station goes offline, pending messages to it
are flagged to not be sent. If any of these are TTY
messages, the message blocks (PCB's) will be used later on
and must have the offline bits cleared.
"/MCO 7123 - MAKE SURE PCB.OF BITS GET CLEARED/
COMNET$:
GETNB1 1/ JRST DTEFEK+4
$Q 4/ JRST CPOPJ1 JRST PAT
PAT/ 0 MOVSI T1,PCB.OF
PAT+1/ 0 ANDCAM T1,PCBBLK(U)
PAT+2/ 0 JRST CPOPJ1
PAT+3/ 0 PAT:
PATSIZ/ MOVEI T1,JUNK MOVEI T1,PAT
2) It is possible to receive a data request for a device that is
no longer connected. When this happens, INCTBD is called
twice and will result in a RIP (Read In Progress) stopcode if
the front end is a DN87S.
"/MCO 7124 - CALL INCTBD ONLY ONCE PER BAD MESSAGE/
NETSER$:
ICMDRQ 4/ JSP T1,INCTBD POPJ P,
3) An attempted fix to a problem in the WHERE command leaving
idle DDB's on the device chain introduced a much worse bug.
The patch below removes that edit, the correct solution will
be in 6.03A.
"/PREVENT WHERE COMMAND FROM FREEING NETWORK DEVICES AT
INOPORTUNE TIMES/
COMDEV$:
CWHERE 26/ JRST LOCAT1+7 PJRST UPOPJ
BEWARE FILE FOR 6.03 DISTRIBUTION Page 30
Unbundled Software
4. DNNSP, the DECNET Compatible Port, is capable of transferring
only one file from the -10 to the -11. The problem is that a
cleared flag gets turned back on (See file DNNSP.COR).
File 1) FEEP:DNNSP.P11[7,5113] created: 1335 14-JAN-1977
File 2) DSKB:DNNSP.P11[10,417] created: 1936 17-APR-1977
1)1 VRNSP==2 ;FILE EDIT NUMBER
1) ;***********************************************************************
****
2)1 VRNSP==3 ;FILE EDIT NUMBER
2) ;***********************************************************************
**************
1)4 BEQ 10$ ;NO, BRANCH
1) BISB LES.FL!LES.WD,LE.STS(R1);YES, WE'LL HAVE TO WAIT FOR DISCONNECT FROM NCL
1) 10$: ;HERE AFTER DETERMINING IF CONNECTION COMPLETE
1) CLRB NSPNCT ;ZERO NCT
****
2)4 BEQ NSPDCO ;NO, BRANCH
2) BISB LES.FL!LES.WD,LE.STS(R1);YES, WE'LL HAVE TO WAIT FOR DISCONNECT FROM NCL
2) NSPDCO: ;HERE AFTER DETERMINING IF CONNECTION COMPLETE
2) CLRB NSPNCT ;ZERO NCT
**************
1)4 BR NSPDCR ;AND HANDLE AS DISCONNECT REJECT
1) 10$: ;HERE IF LINK IS A DEVICE
****
2)4 BR NSPDCO ;AND HANDLE AS DISCONNECT REJECT
2) 10$: ;HERE IF LINK IS A DEVICE
**************
1)4 BR NSPDCR ;AND SEND DISCONNECT TO NCL
1) .SBTTL 1.5.10 NSPDCC 0.0 17-MAY-76 -- NSP DISCONNECT CONFIRM
****
2)4 BR NSPDCO ;AND SEND DISCONNECT TO NCL
2) .SBTTL 1.5.10 NSPDCC 0.0 17-MAY-76 -- NSP DISCONNECT CONFIRM
**************
1)4 BR NXPDCR ;AND GO TO COMMON CODE
1) .SBTTL 1.5.11 NSPILS 0.0 17-MAY-76 -- NSP LINK STATUS
****
2)4 BR NSPDCO ;AND GO TO COMMON CODE
2) .SBTTL 1.5.11 NSPILS 0.0 17-MAY-76 -- NSP LINK STATUS
**************
[End of BWR603.RNO]