|
Going through my Midrange-L and "organizing stuff" I came across this... Why not just set up a 2nd Interactive subsystem for I.S. ? That's what we did YEARS ago (actually I did it to test routing remote devices into their own subsystem for performance reasons but scrapped that idea...). Just do an add workstation name entry for each I.S. device for the 2nd subsystem. When QINTER is down, you are "in" the 2nd subsystem (be aware that you need to sign off at the time QINTER is getting terminated or you loose anything you were doing...). Chuck Gary Feinstein wrote: > Yes, I suppose that will work. He would have to make the susbsystem > entry type in QINTER WRKSTNTYPE(*ALL) AT(*ENTER). I had a similar > problem a while ago. I didn't want any users signing back onto the > system when the backup was running. After bumping all users off the > system, I revoked authority to the subsystem so that only I could get > access. Last step of backup was to grant authority again. > Gary > > boothm@ibm.net wrote: > > > > I>> The only way to do that is is to do a transfer job upon initial > > >>sign-on. I have had the same problem of trying to keep users out of > > >>QINTER without letting them even sign-on. This is a constraint using > > >>TCP-IP. > > > > I get stuff wrong sometimes, but if I understand what you've said here, > > this is what I did (with much help from the folks on this list, btw): I > > created a subsystem named "OUTSIDE" and all tcp/ip logins come into that > > subsystem. From there we let them go on to other things, but they don't > > get into QINTER until after they are logged in. > > > > -- > > ----------------------------------------------------------- > > boothm@ibm.net > (Cut Snip Paste) > I need to place a particular userid's interactive job in a particular > subsystem besides QINTER when they sign on. This user > connects via TCP/IP which means I don't get a consistent > workstation ID. > > What is the best method to do this? TFRJOB from an initial > CL program? > +--- > | 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 > +--- +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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.