|
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 ----------------------------------------------------------- +--- | 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.