Trailing-Edge
-
PDP-10 Archives
-
bb-jr93d-bb
-
7,6/ap015/mon703.d15
There is 1 other file named mon703.d15 in the archive. Click here to see a list.
MCO: 12974 Name: JAD Date: 26-Jun-86:10:20:54
[Symptom]
Doing a FILOP. UUO "open for super I/O" function (.FOSIO) doesn't
do anything to indicate subsequent super I/O for that DDB should
be allowed. If someone patches SETSUP to disable super USETI and
USETO, UFDSET will fail with an illegal instruction error when it
tries to recompute disk usage.
[Diagnosis]
No code.
[Cure]
Add code. Light a bit in DEVPTB which indicates a FILOP. open for
super I/O was executed. Test the bit in SETUP and allow super
USETI/USETO if the bit was set regardless of whether the patch
to disable super I/O is inserted.
[Comments]
I SPR'd this about 3 years ago and got a "stick it" answer.
This is the way it should have been answered.
[Keywords]
SUPER I/O
.FOSIO
UFDSET
[Related MCOs]
None
[Related SPRs]
35513
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 306 COMMOD DEVPTB
FILIO SETSUP
UUOCON FOPVM6
704
[End of MCO 12974]
MCO: 12975 Name: JAD Date: 26-Jun-86:11:00:20
[Symptom]
Error reading a RIB can lead to a subsequent PDA stopcode.
[Diagnosis]
User got a RIB error doing output and eventually did a CLOSE.
This time the RIB was read successfully, but the stuff left in
the pointer area of the DDB from the last error didn't agree
with what was just read.
[Cure]
Have PTRCUR exit via DDBZR if it has an error reading a RIB.
[Comments]
February 26, 1981
[Keywords]
RIB ERROR
PDA
[Related MCOs]
None
[Related SPRs]
30743
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 306 FILIO PTRCUR
704
[End of MCO 12975]
MCO: 12977 Name: KBY Date: 26-Jun-86:13:59:05
[Symptom]
Stack out of phase doing SPY pages out of ascending order
(illegal).
[Diagnosis]
Forgot to POP.
[Cure]
POP(ping tonic).
[Comments]
Edgecomb.
[Keywords]
SPY pages
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
Restricted distribution
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 306 VMSER SPYP2A
704
[End of MCO 12977]
MCO: 12979 Name: RCB Date: 1-Jul-86:05:39:25
[Symptom]
Can't define terminal types with more than 63 lines, even though such
terminals exist, and the TTY LENGTH <n> command accepts 0-255.
[Diagnosis]
6-bit byte field.
[Cure]
Redistribute some bits in TCRTAB to allow for 8-bit bytes.
[Comments]
SCC'ed onto BLKK:[1,2]
[Keywords]
MONGEN
TTY TYPE
[Related MCOs]
None
[Related SPRs]
35370
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A COMDEV TTPLNB,TTPFRM,TTPTAB,TTPLCT,TTPALT,TTPDIS,TTPNFC,TTPXNF,TTP8BT,TCRTAB
704
[End of MCO 12979]
MCO: 12980 Name: RCB Date: 1-Jul-86:07:39:18
[Symptom]
User programs get confused by line sequence numbers in their input buffers
from TSKs and network CDRs.
[Diagnosis]
Junk left in buffer.
[Cure]
BUFCLR when about to fill a buffer.
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
LSN
[Related MCOs]
None
[Related SPRs]
31896
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A NETSER NTDSIB
704
[End of MCO 12980]
MCO: 12981 Name: JAD Date: 1-Jul-86:14:11:52
[Symptom]
Monitor's load balancing across structures sometimes can cause
an ENTER to exceed the user's quota.
[Diagnosis]
FNDFIL calls UFBSZ to find a structure in the job's search
list which has free blocks AND which the user also has UFBTAL
greater than zero. In most cases this works just fine. But,
if UFBTAL happens to be less than the number of blocks tried
for on output (UNIGRP), the structure UFBSZ selects for the
ENTER shouldn't be used, since the ENTER will cause the user's
quota to be exceeded.
[Cure]
Make sure UFBTAL for any particular structure is at least
equal to (or greater than) UNIGRP. This will make subsequent
ENTERs succeed, unless the user has specified an allocation.
In that case, FILFND can't do a whole lot more and they'll
eventually get a quota exceeded error.
[Comments]
Gee, once they raised the level on this one it only
took me a day to figure it out. What's that about squeaky wheels?
[Keywords]
UFBTAL
UNIGRP
UFBSZ
[Related MCOs]
None
[Related SPRs]
31615
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 306 FILFND UFBSZ
702A
704
[End of MCO 12981]
MCO: 12982 Name: JAD Date: 1-Jul-86:16:25:23
[Symptom]
KAF if someone LOCKs a (the last) structure in the ASL.
[Diagnosis]
SWPSER won't write to a unit which has been locked against new
accesses. Unfortunately, if that's the only unit in the ASL,
the system will quickly KAF. Also, we can wind up trashing
location 55 with 200,,0 (UNPNNA) when calling RMVSTR if the
structure has a unit in the ASL.
[Cure]
Call CHKSWP in the "lock structure" code. Teach CHKSWP to
preserve U so the caller has something useful to twiddle bits
in when CHKSWP returns.
[Comments]
Thanks to Louis at ADP
[Keywords]
LOCK STRUCTURE
KAF
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 306 FILFND LOKSTR,CHKSWP
704
[End of MCO 12982]
MCO: 12983 Name: DPM Date: 2-Jul-86:07:34:14
[Symptom]
CDRIVE and IBMSPL return "DN60 not running" error messages after
setting the DTE protocol type with DTELDR.
[Diagnosis]
In DTESER, the routine DTEQUE will queue up messages to a front
end only if the protocol type is set to ANF or NOBODY (RSX-20F). The
CAL11. UUO depends on this routine to communicate with DN60s.
[Cure]
Allow front ends whose protocol type is set to IBM to use the
DTEQUE routine as well.
[Comments]
[Keywords]
DN60
DTELDR
PROTOCOL
[Related MCOs]
None
[Related SPRs]
35310
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 307 DTESER DTEQUE
703A
[End of MCO 12983]
MCO: 12984 Name: WXD/DPM Date: 8-Jul-86:03:04:59
[Symptom]
DECnet-10 and -20 sources out of synch.
[Diagnosis]
Yes
[Cure]
Merge
[Comments]
[Keywords]
DECNET MERGE
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
Restricted distribution
[MCO attributes]
New development MCO
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 306 D36PAR
D36COM
LLINKS
NTMAN
ROUTER
SCPAR
703A
[End of MCO 12984]
MCO: 12986 Name: JAD Date: 9-Jul-86:08:24:59
[Symptom]
Operator confusion.
[Diagnosis]
If RPA0 is down, typing "ATTACH RPA0" responds with the usual
monitor dot after the command is processed. If the command is
typed a second time before a pack is mounted, the monitor will
respond with "?ATTACH RPA0?". Since the command is essentially
a no-op, it seems reasonable to just ignore the command, rather
than making someone think there is an error.
[Cure]
If the unit status is "no pack mounted" pretend the command
did something useful (ignore the command).
[Comments]
No significant impact.
[Keywords]
ATTACH
[Related MCOs]
None
[Related SPRs]
31489
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 307 FILIO ATTUN0
704
[End of MCO 12986]
MCO: 12987 Name: JAD Date: 9-Jul-86:09:14:46
[Symptom]
If one port of a dual-ported disk goes offline, cycling the
drive off and on may cause KAF stopcodes when the monitor
attempts to do a transfer via the alternate port.
[Diagnosis]
After one port gets put in operator wait state FILIO appears
to be very happy to pick the alternate port to perform I/O.
[Cure]
Propagate the operator wait state (UNISTS) to the alternate
port before re-enabling disk interrupts. The free interrupt
when the drive is cycled will get both ports back (I think).
[Comments]
A February 1981 SPR from Intel.
[Keywords]
OFFLINE
KAF STOPCODE
DUAL-PORTING
[Related MCOs]
None
[Related SPRs]
30656
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 307 FILIO BADUNI
704
[End of MCO 12987]
MCO: 12988 Name: JAD Date: 9-Jul-86:09:20:50
[Symptom]
ICHPRM is incomplete.
[Diagnosis]
Missing a few definitions.
[Cure]
Add them - CRMSIZ (CRAM size) and DRMSIZ (DRAM size).
[Comments]
[Keywords]
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
Checked
[MCO attributes]
KL10 only
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 307 ICHPRM CO.DTE,CRMSIZ,DRMSIZ
[End of MCO 12988]
MCO: 12989 Name: JAD Date: 14-Jul-86:10:42:14
[Symptom]
A CI20 or NIA20 which is inaccessible at system startup can't
be added via the AUTOCONFIGURE command to CONFIG(OPR).
[Diagnosis]
The code didn't work originally; once it started working,
a POPJ in the UUO-level auto configuration never got turned into
a JRST.
[Cure]
POPJ => JRST CNFIPA
[Comments]
Probably not significant, but might help someday.
[Keywords]
IPA CHANNELS
AUTOCONFIGURE
AUTCON
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
Checked
[MCO attributes]
KL10 only
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 307 AUTCON UCNFIG
704
[End of MCO 12989]
MCO: 12990 Name: WXD/DPM Date: 15-Jul-86:04:26:18
[Symptom]
KNISER ignores the KLNI microcode that might reside in BOOT.
It always calls KNILDR to reload the KLNI.
[Diagnosis]
KNISER doesn't know how to load it's own microcode.
[Cure]
Add code. If the microcode doesn't exist, or a dump has been
requested, call KNILDR. Otherwise, always attempt to load the
microcode stored in BOOT.
[Comments]
[Keywords]
KLNI MICROCODE
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 307 KNIPRM .PBLEN
KNISER KNILOD
703A
[End of MCO 12990]
MCO: 12991 Name: RCB Date: 15-Jul-86:07:04:24
[Symptom]
Debugging SMP isn't what it ought to be, especially if the CPU that hits a
breakpoint isn't the boot CPU.
[Diagnosis]
CPNDDT was defined years ago, but no way was invented for EDDT to reference
it, so it never gets used.
[Cure]
Extend the EDV to give EDDT a handle on CPNDDT. Add two new words:
.EDCPN - (11) Physical address of CPNDDT
.EDCPU - (12) AOBJN pointer to table of APR serial numbers
This gives EDDT enough information to find the current CPU number and light
the appropriate bit in CPNDDT without requiring random external symbols to be
referenced by EDDT.
This also adds ASNTAB to COMMON. This is the table pointed to by .EDCPU,
which is set up by SYSTR0.
[Comments]
SCC'ed to BLKK:[1,2].
[Keywords]
CPNDDT
[Related MCOs]
None
[Related SPRs]
35462
[MCO status]
Checked
[MCO attributes]
Documentation change
UUOSYM change
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 307 S .EDLEN
704 COMMON .CPEDV,ASNTAB
UUOSYM .EDLEN
[End of MCO 12991]
MCO: 12993 Name: RCB Date: 15-Jul-86:07:13:58
[Symptom]
More complicated to set up mapping of a crash in FILDDT than it should be.
[Diagnosis]
No way for FILDDT to know what we want set up.
[Cure]
In DIE, when taking a dump, leave tracks. This extends the EDV by yet another
word, .EDCAC (13), the physical address of the virtual address of the crash AC
block. DIE will set up .JBEDV with the EDV of the crashing CPU for the
duration of the dump, after which it will restore the incoming value (in case
you're also debugging with EDDT and need to keep the hidden symbol blocks
around).
[Comments]
SCC'ed onto BLKK:[1,2]
Since we're already hacking the EDV, seems like a good time to do it.
[Keywords]
EDV
[Related MCOs]
12991
[Related SPRs]
None
[MCO status]
Checked
[MCO attributes]
New development MCO
Documentation change
UUOSYM change
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 307 S .EDLEN
704 UUOSYM .EDLEN
COMMON .JBEDV
ERRCON DIE1,RESTR0
[End of MCO 12993]
MCO: 12995 Name: JAD Date: 17-Jul-86:11:14:24
[Symptom]
Kimo unhappy.
[Diagnosis]
When you mount a structure after ONCE time, the unit status
of the alternate port never gets updated from "no pack mounted".
Conversely, if you dismount a structure mounted during ONCE time,
the alternate port still says "pack is mounted".
[Cure]
Copy unit status (UNYUST) to alternate port when mounting or
dismounting a structure.
[Comments]
I hope he's happy now.
[Keywords]
UNIT STATUS
UNYUST
K(THE B STANDS FOR BLUE)Y
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
None
[MCO attributes]
New development MCO
KL10 only
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 301 FILFND DEFST4,REMUN
704
[End of MCO 12995]
MCO: 12996 Name: JAD Date: 17-Jul-86:12:16:22
[Symptom]
DECnet strangeness (other than the "expected" oddities),
like IMEs, etc., where no man has gone before.
[Diagnosis]
MCO 12767 invented a new calling mechanism for DECnet
modules to call other monitor modules (MCALL macro). The
problem is that some invocations of the macro use MCSEC1
for the section number while others use MSEC1. MCSEC1 is
defined as <1,,0> while MSEC1 is defined as 1. Confusion
results when you call some of the routines in the wrong
section.
[Cure]
Since DECnet wants to use MSEC1, and since the MCALL macro
itself expects arguments in that form, change the MCSEC1
references in any MCALL macros to MSEC1.
[Comments]
Tick, tick, tick, ...
[Keywords]
MCALL
DECNOT
WHY DO WE ALWAYS CALL ONE THING BY TWENTY DIFFERENT NAMES?
[Related MCOs]
12767
[Related SPRs]
None
[MCO status]
None
[MCO attributes]
New development MCO
KL10 only
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 301 D36PAR LOTS
D36COM OF
LLMOP BAD
NTMAN MACRO
SCMUUO CALLS
704
[End of MCO 12996]
MCO: 12997 Name: JAD Date: 17-Jul-86:12:25:42
[Symptom]
IME, etc., if a program intercepts hung device interrupts for a
device which uses Exec Virtual Memory (EVM).
[Diagnosis]
DEVHNG checks if the program enabled for hung device interrupts,
and if so, will start the job running in the interrupt handler.
If the tape hung during an I/O UUO, EVM was allocated for the
device and DEVIAD/DEVOAD were diddled to point at buffers in
EVM. Subsequent I/O can cause IME's when trying to reference
the buffers in user memory using the EVM address still hiding
in DEVIAD/DEVOAD.
[Cure]
Call RTNEVM if giving the user a hung device interrupt.
[Comments]
Only ADP uses DECtapes these days ...
[Keywords]
HUNG DEVICE
EVM
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
None
[MCO attributes]
KL10 only
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 301 ERRCON DEVHN0
704
[End of MCO 12997]
MCO: 12998 Name: JAD Date: 18-Jul-86:10:32:26
[Symptom]
Edgecombe is unhappy.
[Diagnosis]
Undefining the last pathological name spec for a job
doesn't delete the table of pathological names.
[Cure]
Delete the table if undefining the last pathological name.
[Comments]
A trivial change, if he feels its so important I guess I
can accomodate him.
[Keywords]
PATHOLOGICAL NAMES
RECLAIM SPACE
[Related MCOs]
None
[Related SPRs]
34743
[MCO status]
None
[MCO attributes]
New development MCO
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 301 FILUUO PTHSL4
704
[End of MCO 12998]
MCO: 12999 Name: JAD Date: 18-Jul-86:12:31:32
[Symptom]
Edgecombe is unhappy.
[Diagnosis]
The maximum length of a pathological name specification is
127 (decimal) words. He'd like to define longer (!) ones
but is limited by the width of the field which contains
the length of the spec (7 bits wide, max = 177).
[Cure]
Expand the field to 9 bits (max = 777) so his maximum
length of a pathological name specification could be 511
(decimal) words.
[Comments]
The original SPR was against 7.01A, where defining a pathological
name using embedded pathological names caused the embedded names
to be expanded during the definition. In 7.02 embedded names
are simply stored in the spec and expanded by FILUUO when it
scans pathological names. Because of this, Edgecombe's SPR
probably isn't as important in later monitors, but making the
maximum limit larger won't help (we'll keep the default the
same as it is now).
MJM: See Monitor Tables
[Keywords]
PATHLOGICAL NAMES
MAXIMUM LENGTH
[Related MCOs]
None
[Related SPRs]
34744
[MCO status]
None
[MCO attributes]
Documentation change
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 301 COMMOD LNMMXL,LNYLEN
704
[End of MCO 12999]
MCO: 13000 Name: RCB Date: 19-Jul-86:00:32:58
[Symptom]
CTHNRT (or NRT) will die with a ?NRTINA (Interlock Not Available) error.
LPTSPL will die with a NIP (No Interrupt in Progress) stopcode when driving
a terminal.
[Diagnosis]
TTMORE is clobbering the user's PC for PSISER.
[Cure]
Teach it that it's running at UUO level, so that it will work.
[Comments]
SCC'ed onto BLKK:[1,2].
Should be in the autopatch monitor before we ship it.
[Keywords]
TTMORE
ASYNCH. TTY I/O
[Related MCOs]
12914
[Related QARs]
928017
[MCO status]
Checked
[MCO attributes]
QAR answer
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 301 SCNSER TTMORE,MORE50
704
[End of MCO 13000]
MCO: 13002 Name: DPM Date: 21-Jul-86:04:23:24
[Symptom]
MTIND. UUO sets an illegal density code of 10 in TDVSTS.
[Diagnosis]
The illegal density code is caused by an incorrect definition of
the symbol COMPAT which indicates the default density/mode bits for
industry compatble mode. However, TAPUUO will try to force the
default 1600 BPI density on all units even when that density is
inappropriate for the particular unit. This condition is corrected by
TxxKON modules, but the density range checking for TU78s is incorrect.
[Cure]
Don't change density settings just because industry compatible
mode is being set. Let the normal density setting routine (GETDEN)
select the proper density. Also, correct the density check in T78KON.
[Comments]
Thanx to ADP.
[Keywords]
DENSITY
[Related MCOs]
None
[Related SPRs]
35353
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 301 TAPUUO TPM9TK,TPSETI
T78KON T78SI1
703A
[End of MCO 13002]
MCO: 13003 Name: RCB Date: 22-Jul-86:04:07:26
[Symptom]
Incoming NRT connects lose input characters due to no particular fault
of the user.
[Diagnosis]
DECnet's message buffering is causing NRTSER to choke SCNSER, and NRTSER
isn't noticing.
[Cure]
Move the pseudo-XOFF code from being CTERM specific to being NRTSER-wide.
This way, we won't do any DECnet receives for a line that SCNSER has threatened
to choke on. As soon as SCNSER tells us it's willing to accept more characters
we'll give it another chance.
[Comments]
SCC'ed onto BLKK:[1,2]
[Keywords]
NRT
Lost input characters
[Related MCOs]
None
[Related SPRs]
35393
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A NRTSER NRB,NRTREM,NRTIN1
704
[End of MCO 13003]
MCO: 13006 Name: RCB Date: 22-Jul-86:06:06:50
[Symptom]
MCO 12862 (range-checking path blocks in LOOKUP/ENTER/RENAME) went too
far for a lot of user programs that just want to delete a .TMP file.
[Diagnosis]
It turns out that an awful lot of programs just do a
SETZM T1
RENAME T1
to delete a file. However, since MCO 12862, this causes the contents of
T4 to be checked as a PPN word. Since it's unrelated junk, this often bombs
the program.
[Cure]
Since SETLER won't allow a name word of zero if it's going to use the path
pointer, don't range check the path pointer in FCLERB if the name word is zero.
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
DIP
SCC
RENAME-->DELETE
[Related MCOs]
12862, 12859
[Related SPRs]
None
[MCO status]
Checked
Restricted distribution
[MCO attributes]
New development MCO
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A UUOCON FCLERB,FCLER1
704
[End of MCO 13006]
MCO: 13007 Name: RCB Date: 22-Jul-86:06:16:49
[Symptom]
Problems with TTY CRLF and .TOFLM when mixing PIM mode and regular ASCII-mode
output.
[Diagnosis]
SCNSER thinks all characters are image, but the FE's know better.
[Cure]
Don't skip so much of regular XMTCHR when in PIM. Just treat PIM output like
regular image-mode output, except for skipping the MIC stuff.
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
PIM
TTY CRLF
COMFLM
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
Checked
[MCO attributes]
New development MCO
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A SCNSER XMTDSP,XMTPIM,ZAPBUF
704
[End of MCO 13007]
MCO: 13008 Name: KBY Date: 22-Jul-86:07:17:20
[Symptom]
High seg not always mapped correctly in EVM after LOCKing
it in core.
[Diagnosis]
Sometimes MAPHGH doesn't run for the job in doing the LOCK
for the high segment until after LOKEVM has copied the old map pointers
into the exec map.
[Cure]
Don't except setting REDOMP/SEGMB for the job doing the LOCK; this
will force MAPHGH to be called at clock level before the job is run
again (LOKEVM runs at UUO level).
[Comments]
[Keywords]
lock
EVM
high seg
[Related MCOs]
None
[Related SPRs]
35508
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
702A LOKCON LOCK22
703A 301
704
[End of MCO 13008]
MCO: 13011 Name: RCB Date: 23-Jul-86:09:20:28
[Symptom]
MIC BREAK is broken on old-style PTYs.
[Diagnosis]
Excess paranoia about how to deliver the ^B.
[Cure]
TLNE T2,LDLMCP!LDLMCB --> TLNE T2,LDLMCP
[Comments]
SCC'ed onto BLKK:[1,2].
A 7.01A SPR. And we call this a service?
[Keywords]
MIC
OLD PTY
[Related MCOs]
None
[Related SPRs]
34173
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
702A SCNSER PTYMCK
703A
704
[End of MCO 13011]
MCO: 13013 Name: JAD Date: 23-Jul-86:13:00:45
[Symptom]
AR/ARX parity trap on one CPU in an SMP configuration can cause
that CPU to hang on the DIE interlock. Eventually some other CPU
breaks the interlocks and the original CPU gets a CIB stopcode.
[Diagnosis]
Tests in KLSER in the parity trap routine conditionally obtain
the DIE interlock if the trap didn't occur at APR interrupt level.
However, there are some paths through other monitor modules which
can get the DIE interlock when doing a sweep at clock level. This
can cause a hang in KLSER waiting for the interlock we already own.
[Cure]
Make the DIE interlock recursive such that subsequent calls to
the interlock routine only increment the level of nesting. Calls
to release the interlock are no-ops until the nesting unwinds.
[Comments]
Gee, wasn't there a project some brash young man proposed for
7.04 dealing with cleaning up interlocks to make them recursive?
Or am I just hallucinating again?
[Keywords]
Parity traps
CIB stopcodes
[Related MCOs]
None
[Related SPRs]
35255
[MCO status]
None
[MCO attributes]
New development MCO
KL10 only
Multi CPU only
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 302 CLOCK1 APPSWP
COMMON .CPDIE,SPRIN5,DUMMYS
CPNSER LOKDIE,ULKDIE,BRKDIE,CHKDI3,BRKLO2
ERRCON DIE2,CPUST2
KLSER PRTRP,PRHF1A,PRHMF4,PRHMF5,PTXIT1
S DIELOK,DIENLK
704
[End of MCO 13013]
MCO: 13014 Name: DPM Date: 25-Jul-86:02:57:54
[Symptom]
If SET WATCH MTA is enabled by a user, and a reel switch is done
to the same tape drive, the WATCH statistics are never typed on the
user's terminal.
[Diagnosis]
Since PULSAR performs the unload, the monitor sees PULSAR as the
owner of the tape. This is actually correct because PULSAR uses a
label DDB for the unload operation, and PULSAR does own that DDB.
[Cure]
Teach routine TPSTAT to fetch the user's DDB if the job doing the
unload is the tape labeler.
[Comments]
[Keywords]
REEL SWITCH
[Related MCOs]
None
[Related SPRs]
35396
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 302 TAPUUO TPSTAT
703A
[End of MCO 13014]
MCO: 13015 Name: KBY Date: 25-Jul-86:07:58:05
[Symptom]
Stopcode PQW, most often seen running LINK virtual.
[Diagnosis]
Missed one place where the virtual page number that a physical
page on an "IN" queue belongs to gets changed (.PGMOV). This function
is pretty much only exercised by LINK.
[Cure]
Update the right place (PT2TAB, not MEMTAB).
[Comments]
[Keywords]
LINK
MOVE PAGES
[Related MCOs]
12925
[Related SPRs]
None
[MCO status]
None
[MCO attributes]
PCO required
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 302 VMSER MVPMT
704
[End of MCO 13015]
MCO: 13016 Name: KBY Date: 25-Jul-86:11:43:21
[Symptom]
MERGE. UUO fails if job is over its physical but not virtual limit
whereas GETSEG doesn't.
[Diagnosis]
Special checks for GETSEG.
[Cure]
Remove checks so we'll page out the low seg. The original
intent was probably to prevent doing this on a RUN rather than just
allowing it on GETSEG, but that shouldn't matter any more either.
[Comments]
[Keywords]
MERGE
[Related MCOs]
None
[Related SPRs]
35051
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 302 SEGCON CKSIZ5,MORDR2
704
[End of MCO 13016]
MCO: 13021 Name: KBY Date: 7-Aug-86:09:34:45
[Symptom]
MERGE. UUO still fails under some virtual conditions
[Diagnosis]
PAGLOW clobbers T1.
[Cure]
Reload T1 before calling CRPAGE.
[Comments]
[Keywords]
[Related MCOs]
None
[Related SPRs]
35543
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 304 SEGCON MORDR2
704 310
[End of MCO 13021]
MCO: 13024 Name: RCB Date: 9-Aug-86:00:46:47
[Symptom]
Machine hangs during $X or $P after a breakpoint in an SMP configuration
after MCO 12991
[Diagnosis]
EDDT turns on the PI system during $X processing, but CPNDDT is still
non-zero. Thus, TMnINT thinks that we should wait for the CPU to come
out of the breakpoint. This results in a hang if the DDTing CPU was the
same one that just took the interrupt.
[Cure]
Since we risk a CIB if we don't leave CPNDDT non-zero, teach TMnINT not to
wait for itself, but only for other CPUs.
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
EDDT
EDV
CPNDDT
[Related MCOs]
12991
[Related SPRs]
None
[MCO status]
Checked
[MCO attributes]
PCO required
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 310 COMMON AP?BCK
703A
[End of MCO 13024]
MCO: 13026 Name: DPM Date: 12-Aug-86:05:08:18
[Symptom]
A customer may not easily change the default PFH timer trap
interval.
[Diagnosis]
No MONGEN symbol exists. The value of 60 ticks is hard wired
into MONPFH.
[Cure]
Create symbol M.PFHT which is the default PFH timer trap interval
in ticks.
[Comments]
DOC change affects the installation manual where the MONGEN symbols
are listed.
[Keywords]
PFH TIMER TRAP
[Related MCOs]
None
[Related SPRs]
35553
[MCO status]
None
[MCO attributes]
Documentation change
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 311 COMMON M.PFHT
MONPFH PFH
703A
[End of MCO 13026]
MCO: 13027 Name: JMF Date: 12-Aug-86:07:27:07
[Symptom]
Virtual program does a large dump mode input and gets no data,
does a large dump mode output and writes no data, PFNOIO stopcds, other
things are possible.
[Diagnosis]
If the entire map was scanned to find some pages to page out
so that the whole IOWD will fit in core and none were found, we look for
as many pages to page in as can be found to do the largest piece of the
IOWD possible. However, if no pages could be paged out there are none that
can be paged in.
[Cure]
Don't try to page in pages if none could be found to page out.
[Comments]
SCC'ed to BLKK:[1,2]. This might very well fix all of CH2M Hill's
QARs on virtual programs doing dump mode I/O.
[Keywords]
virtual
dump mode I/O
[Related MCOs]
None
[Related SPRs]
35554
[MCO status]
Restricted distribution
[MCO attributes]
New development MCO
VM only
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
703A 304 MONPFH PFHMKR
704 310
[End of MCO 13027]
MCO: 13028 Name: DPM Date: 12-Aug-86:08:20:20
[Symptom]
Can't set CORMAX to desired numbers if there are large jobs. There
is no way to lower CORMAX such that when jobs relinquish core, they
will not expand beyond the new lower limit.
[Diagnosis]
No concept of a "soft" CORMAX.
[Cure]
Add a new bit to the .STCXP function of the SETUUO to indicate "soft"
CORMAX is being set. With the bit turned on, CORMAX will be set to
the new lower limit regardless of any jobs using more core than the
new limit. When the jobs contract core below the new limit, they will
never grow beyond it again.
[Comments]
A trivial answer for a 4 year old problem. DOC change affects the
Monitor Calls Manual volume 2, under SETUUO function .STCXP.
[Keywords]
CORMAX
[Related MCOs]
None
[Related SPRs]
33121
[MCO status]
None
[MCO attributes]
Documentation change
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 311 COMCON SETMXP,SETMX1,SETMX2
703A
[End of MCO 13028]
MCO: 13033 Name: DPM Date: 14-Aug-86:08:59:24
[Symptom]
If a tape drive is hung as a result of an MTAPE operation which
does not set IOACT (such as write tape mark), and the monitor is
trying to force a scheduled interrupt, the KDB and UDB hang forever.
[Diagnosis]
The hung timer is never reset prior to requesting the interrupt
from the controller, leaving the KDB and UDB "in use".
[Cure]
Reset the hung timer to TAPTIM seconds prior to requesting an
interrupt.
[Comments]
[Keywords]
TAPE HANGS
[Related MCOs]
None
[Related SPRs]
32672
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 312 TAPSER TAPSE1
703A
[End of MCO 13033]
MCO: 13034 Name: RCB Date: 19-Aug-86:02:40:41
[Symptom]
The simulated G-Floating opcodes (under the EXTEND instruction) fail via
UADERR.
[Diagnosis]
Inability to perform EA calculation on a word with an opcode in it.
[Cure]
Add code. New routines in VMSER, to parallel CHKIND:
CHKINS - Check instruction word
CHKINX - ditto, but section for IFIW resolution is in T2 (not PCS)
CHKEFI - Check EFIW word
CHKEFX - ditto, but with IFIW section in T2
For all routines, on entry T1 has the word whose EA is to be found. On
non-skip return, some address or indirect word was illegal. On the skip
return, the resolved address is in T1, the section of reference is in the RH of
T2, and the EA-is-global flag is in the LH of T2. The section-of-reference
flag is used when T1 indicates an AC reference. The EA-is-global flag
determines whether OINKSR will use a global reference or an IFIW reference when
calling GETEWD.
These routines preserve PCS and all registers other than T1 & T2.
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
G-Floating
OINKSR
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 312 KLSER OINKSR,GFLTXX
703A VMSER CHKINS,CHKINX,CHKEFI,CHKEFX,CHKIN0
[End of MCO 13034]
MCO: 13035 Name: RCB Date: 19-Aug-86:02:59:23
[Symptom]
Output on remote printers stops but the node does not crash.
[Diagnosis]
NCL messages ACKed out of order. In particular, we are flushing our
queue of messages to send when we receive an ACK for a message which we have
never sent before.
[Cure]
Pay no attention to ACKs for messages which have never been sent. Maximimze
with NDBLMS (Last Message Sent) rather than NDBLMA (Last Message Assigned).
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
Hung NCL traffic
[Related MCOs]
None
[Related SPRs]
34361
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 312 NETSER CHKNCA
703A
[End of MCO 13035]
MCO: 13036 Name: RCB Date: 19-Aug-86:03:07:12
[Symptom]
When SAVEing to a disk file, the user's current and maximum virtual limits are
usually swapped.
[Diagnosis]
RELDRX (the fast SAVE to disk code) pops them in the wrong order.
[Cure]
Right order.
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
SAVE
.PDMVL
.PDCVL
[Related MCOs]
None
[Related SPRs]
35542
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 312 COMCON RELDRX
703A
[End of MCO 13036]
MCO: 13037 Name: RCB Date: 19-Aug-86:03:51:07
[Symptom]
Lower- or mixed-case input to the MONGEN special terminal configuration will
not have the desired results.
[Diagnosis]
MONGEN validates the input after converting to SIXBIT, but COMDEV just does
straight IFIDNs.
[Cure]
Teach COMDEV to compare in SIXBIT, too.
[Comments]
SCC'ed onto BLKK:[1,2].
Edgecombe
[Keywords]
SPCTRM
Lowercase
[Related MCOs]
None
[Related SPRs]
35528
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 312 COMDEV TRMCR1,CTCTAB
703A
[End of MCO 13037]
MCO: 13038 Name: RCB Date: 19-Aug-86:05:11:49
[Symptom]
Asynchronous image-mode input is never initialized until after at least one
character has been typed. This causes such interesting characters as control-U
to be lost.
[Diagnosis]
Checking for having no input before setting up for image input.
[Cure]
Change order of tests.
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
Image input
UU.AIO
[Related MCOs]
None
[Related SPRs]
32129
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 312 SCNSER TTYINA,TTYIN0
703A
[End of MCO 13038]
MCO: 13039 Name: RCB Date: 19-Aug-86:05:46:31
[Symptom]
Image-mode input is not initialized for a terminal being connected to an MPX:
channel. This causes interesting characters such as control-U to be lost.
[Diagnosis]
No code to diddle LDLIMI, or anything else in the LDB.
[Cure]
Add routine TTYMPX in SCNSER, and call it from CNDDBI in MSGSER when we notice
that we're connecting a TTY.
[Comments]
SCC'ed onto BLKK:[1,2].
[Keywords]
MPX
IO.IMG
[Related MCOs]
None
[Related SPRs]
31766
[MCO status]
Checked
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 312 MSGSER CNDDBI
703A SCNSER TTYMPX
[End of MCO 13039]
MCO: 13048 Name: DPM Date: 22-Aug-86:05:41:54
[Symptom]
A program OPENs the controlling TTY, enables for PSI on
Control-C, and the trap routine is terminated with an EXIT UUO. It
reads characters from the terminal using either INCHRS or INCHSL UUOs
even though an OPEN has been done. If the user then types a single
Control-C, the program will hang in 'TI' state in the middle of the
EXIT UUO. If the user types another Control-C, the program appears to
branch to an unpredictable memory location.
[Diagnosis]
The job hangs in 'TI' state because an EXIT UUO implicitly causes
all pending I/O to complete. The DEVIOS word for the terminal DDB has
both the I/O wait and I/O active bits turned on. The implied call to
the RELEASE UUO puts the job into 'TI' state because the I/O bits are
set. The user PC now points to the EXIT UUO plus one. When the user
types a second Control-C, the monitor takes the job out of 'TI' state
(because only one Control-C is necessary to stop the job when it's in
'TI') and starts the job at the last PC. Since the program did not
expect to continue after the EXIT UUO, the words following the EXIT
UUO may not contain valid instructions. If a subroutine follows, the
subsequent POPJ will return control to an indeterminate PC.
[Cure]
Prior to granting the PSI interrupt to the job, check to see if
the TTY chunks contain any characters that may be input. If not, then
clear the I/O wait and active bits in the DDB. This will always work
for several reasons. If the job is doing blocking input, a single
Control-C will take the job out of 'TI' state. Therefore, clearing
the I/O wait and active bits presents no problems. If the job is
doing an asynchronous input as in the case of INCHRS or INCHSL UUOs,
and the TTY chunks are empty, the program is not expecting to do any
input and again, it is safe to clear the I/O bits. If there are
characters available, then the job will pass through a 'TI' state, but
again, a single Control-C will terminate the I/O, so clearing the I/O
bits will work. The PSI status word in the interrupt vector will
still reflect the true state of I/O making this change transparent to
all programs. The solution elimiates any I/O hangs for the terminal
in the EXIT UUO. Because of this, the side effect of restarting the
job at the wrong PC is removed.
[Comments]
[Keywords]
PSI
CTRLC
[Related MCOs]
None
[Related SPRs]
33587, 34608
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 313 CLOCK1 STOP1H
SCNSER TICAVL
703A
[End of MCO 13048]
MCO: 13057 Name: DPM Date: 25-Aug-86:07:05:31
[Symptom]
Lower case punctuation characters act as break characters during COMCON
command parsing.
[Diagnosis]
In SCNSER, routine RIALTO clobbers the input character count in T2 with
the contents of LDBDCH. Later, T2 is checked for having more than 72
characters and a break is simulated.
[Cure]
Preserve T2.
[Comments]
QAR# 868740
[Keywords]
ALTMODE
[Related MCOs]
None
[Related SPRs]
None
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 313 SCNSER RIALTO
703A
[End of MCO 13057]
MCO: 13060 Name: DPM Date: 26-Aug-86:05:21:05
[Symptom]
If a user issues an ASSIGN command to set a logical name for a
device which is INIT'ed by some context for that job, the ASSIGN
fails.
[Diagnosis]
In UUOCON, routine ASSASD fails because the device is already
INIT'ed by a context whose job/context handle does not match that of
the job trying to set the logical name. When COMCON processes ASSIGN
commands, a context number of zero is used to indicate the assign is
job-wide. ASSASD should detect this case.
[Cure]
If the device in question is already INIT'ed, and a logical name
is being set by the job who has the device INIT'ed, then let the
assign succeed.
[Comments]
QAR# 868184
[Keywords]
ASSIGN
[Related MCOs]
11102
[Related SPRs]
None
[MCO status]
None
[MCO attributes]
None
[Validity]
Monitor Load Module Tags
------- ------ ------ ------
704 313 UUOCON ASSA2Z
703A
[End of MCO 13060]