John A. Dundas III wrote:
If RSTS/E
looks like an SJ environment, then it should provide that
information to an
RT-11 request to determine if a mapped monitor is being used. That
will be PERFECT
since the problems can occur ONLY with a mapped RT-11 monitor.
It claims to be SJ.
Looks like it is a close as it could be under RSTS/E. Very Good
Can anyone
verify that the CONFG2 (location 300 offset) word will
show an unmapped monitor?
Yes.
Please see Table 6-3, page 6-16:
<http://dundas-mac.caltech.edu/~dundas/retro/DEC%20Docs/RSTS/Documentation/V9.0/aa-ez10a-tc.pdf>
Later revisions of the manual agree with the information given.
Earlier versions do not contain this level of detail, but I believe
the answer is the same.
THANK YOU AGAIN!!!! This is exactly what I required.
The information in this manual confirms that the .GVal EMT request for
location 300 (it is actually CONFG1)
will state that an unmapped monitor is running.
The only other question is how to determine the device name of the
program which is
running. Under RT-11, the .CStatus EMT returns the physical device name
of the
program file which is open on channel 17 since it is overlaid. The
manual states that
.DStatus EMT is available, but ignores the .CStatus EMT, except by
default which
leads me to interrupt that such information is not available under
RSTS/E. Is anyone
familiar with the RSTS/E RT-11 run time system? Was .CStatus ever
added for
support. The possible solution is to default to assuming the program is
on the system
device, SY:, which is already known to work. I can place a -1 in the
.CStatus area
before the EMT request and if that value is still there, use SY: for the
device name.
Disappointing, but not much of any other option I can think of. Can
anyone else
suggest something I have missed?
Jerome Fine