RE: Rumba & Qctl

Joanie,
while you are working through this another parm to watch for is the
Allocation AT(*SIGNON / *ENTER) for work station entries.
*SIGNON causes the device to be re-allocated to the sbs when the
sbs is started.
I'd also encourage the use of John's recommended "NIGHTINTER".
If you ever have a session error where you would like to end the sbs
to clear it and clean things up, QCTL is not the one to be in.

 -Steve Cotes
 -cotess@data-io.com

> ----------
> From:         John Earl[SMTP:johnearl@lns400.com]
> Sent:         Monday, December 29, 1997 10:22 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Rumba & Qctl
> 
> 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. 
> 
> Joanie,  Take a look at the section in the work management guide that
> deals
> with how devices are allocated by subsystems.  Subsystem device
> allocation
> is not as intuitive as you probably had hoped, but once you read this
> short
> section you'll understand the behavior you're seeing.  
> 
> To piggy back onto Bob Larkin's comments, it's the fact that QINTER is
> activated after QCTL that causes your device to be allocated to
> QINTER.
> Last subsystem up gets it.  
> 
> You could also solve this by creating a duplicate of the QINTER
> subsystem
> called NIGHTINTER.  Remove all of the workstation entries from
> NIGHTINTER,
> and then add one back in that names your device specifically.  Then
> when you
> bring down QINTER, start subsystem NIGHTINTER.  Now you'll have a
> subsystem
> that can only be accessed by your dial in PC.
> 
> >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. 
> 
> Ya' know, even under the current situation, I'd wager that if you've
> succesfully added the device to QCTL, that once QINTER ends, QCTL is
> going
> to allocate that device.  It's likely that you're fine with your
> current
> arrangement, it just looks wrong during daylight housr (when QINTER is
> up).
> Have you experience to the contrary?
> 
> 
> >
> >So, any ideas why this frickin' workstation refuses to stay in the 
> >controlling subsytem of QCTL ?   
> 
> Again, last subsystem up wins the device.
> 
> 
> 
> HTH,
> 
> jte
> 
> --
> 
> John Earl     Lighthouse Software Inc.
> 8514 71st NW  Gig Harbor, WA 98335
> 253-858-7388  johnearl@lns400.com
> 
> If you're not using Lighthouse Network Security/400, you're AS/400 is
> wide open!
> 
> 
+---
| 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
+---