TSX-PLUS (Was MicroPDP 11/73)

From: Jerome Fine <jhfine_at_postoffice.idirect.com>
Date: Mon Feb 4 22:40:32 2002

>Pete Turnbull wrote:

> >On Feb 4, 17:48, Jerome Fine wrote:
> > (a) As far as I know, there are no hobby versions, as yet, for TSX-PLUS.
> > However, if there is enough interest, perhaps we could inquire. I would
> > certainly be willing to contact S&H to see if they might be interested.
> > Since I was a sort of distributor for S&H at one point and I already have
> > my own license, I would be able to support hobby users. SO!!!! Are
> > there any potential TSX-PLUS hobby users out there who would like
> > to have this software?
> Yes!

ONE! I will inquire if the total reaches FIVE!

> Like Jerome's, one or two of my RT-11 systems are SYSGENed for
> multi-terminal support. But it's not the same.

You are correct. The worst part is the scheduler. There really is none
in RT-11. Now, might that be a project that would be useful? But running
under VBGEXE provides all 64 KBytes of memory if needed for any job.
One thing nice about KEX is that:

SRUN KEX.SAV/LEVEL:n/TERMINAL:n/NAME:KEXn

is allowed so that each job can have its own name - which means that
more than one KEX can run as a system job at the same time. However,
if you are using VBGEXE to trigger the job via:

.SRUN VBGEXE.SAV/LEVEL:n/TERMINAL:n
?Program FOO

then the name of each job will be VBGEXE which is NOT allowed
for the second job. I added a few lines of code to VBGEXE to allow:

.SRUN VBGEXE.SAV/LEVEL:n/TERMINAL:n/NAME:VBGEXn
?Program FOO

such that if VBGEXn matches the value if "n" in the "/LEVEL:n" switch,
then the name of the job becomes VBGEXn which becomes unique
for each job. All the extra code does is compare the characters in the
"/NAME:VBGEXn" switch with the characters "VBGEXn" as derived
from the "/LEVEL:n" switch. If they match, then the normal default
of "VBGEXE" for the name of the job is changed to "VBGEXn"
rather than looking for a file named "VBGEXn.SAV" which is the
way that the "/NAME:FOO" is handled. Obviously this means that
the user can't have any programs named:
VBGEX1.SAV
VBGEX2.SAV
VBGEX3.SAV
VBGEX4.SAV
VBGEX5.SAV
VBGEX6.SAV
a small price to pay for the extra flexibility in my opinion. Note, I did
this before I found out that KEX accepts:

.SRUN KEX.SAV/LEVEL:n/TERMINAL:n/NAME:KEXn

but it has come in handy once or twice over the years since then.
If anyone objects, can you suggest another method?
Received on Mon Feb 04 2002 - 22:40:32 GMT