At 07:13 PM 12/29/97 +0000, you wrote:
>I'm running a HP PC with Rumba and attempting to use QCTL as the 
>controlling subsystem. The main reason is that I use this PC to dial 
>in from home vai PC Anywhere..... 
>What's been happening is that I can't get it to connect to QCTL, it 
>always wants to connect to QINTER. I've added the workstation entry 
>in the subsystem description and have verified that's it's name 
>etc... sometimes if I turn the PC off and turn it back on (maybe even 
>several times) it finally does connect to QCTL. 

Usually, the last subsystem that can allocate a device does so. Since QCTL
is always active before QINTER, you'll never end up in QCTL by default,
unless your QINTER subsystem description contains device name entries that
preclude running there. However, you can TFRCTL into QCTL. I used to work
at a place where we did that every afternoon for exactly the same reasons
that you refer to. I think this behavior is a little capricious though, in
that it may depend on how you are attached (we used an ASCII controller and
WYSE50 emulation). I've tried this trick using SDLC connections, and it has
not worked. It may even be release sensitive. One thing you can do however,
which is what we do at my present employer, is to use another subsystem (we
use QPGMR), and add specific device name entries to this subsystem only. We
always bring up QPGMR after QINTER, and generally (but not always), the
device description ends up being allocated by it. In any case, if QPGMR is
active and QINTER is not, the dial-in device will attach there.


Pete Hall

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "".
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.