Re: Rumba & Qctl

You probably have the device defined in more than one subsystem. (It could be by device type or name). As I recall, the last subsystem that requests the device gets it. QCTL starts first, it has the device. Then QINTER starts, and it gets the device. Makes sense... NOT! Anyway, If you have your backup program vary off, then vary on the device, after QINTER is down, you will not have a problem. If you are signing on and end up in QINTER, use the TFRCTL to change to the QCTL subsystem.

HTH
Bob Larkin
Larkin Computer Consulting
 Bob's Page

Joanie Clark 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.

You may ask why I need it to QCTL ?  Well, at night we back our
system up and we end the subsystem QINTER to make sure all the users
are off the system. This way we get a good, clean backup.  Although
what happens is that if the backup fails (controlled by a CL), the
subsystem QINTER does not come back up and the users call me wanting
the system back.  If I dial in and the PC is on Qinter, I won't be
able to remedy the situation.

So, any ideas why this frickin' workstation refuses to stay in the
controlling subsytem of QCTL ?

Thanks for your help !!

Joanie
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
uucp