|
Dan: Your interactive subsystem has a routing entry that compares routing data for the job against a constant 'QCMDI'. The program named on that entry is normally QSYS/QCMD. Create program MyRtgPgm that does: 1. Retrieves job user 2. Lists active interactive jobs for that user 3. Retrieves the count of those jobs 4. Retrieves a *USRIDX entry keyed by user names and containing the value you want for max sessions for that user 5. Compares job count to max user sessions 6. Escapes if max sessions exceeded 7. Otherwise TFRCTL QSYS/QCMD Then CHGRTGE for the approprite routing entry to name your MyRtgPgm instead of QSYS/QCMD. MyRtgPgm can do whatever you need before the TFRCTL to check connection type, set environment, route to a different subsystem, display a message, whatever. This is ideally suited for a routing program. Just create the *USRIDX and add whatever entries you need. The logic of what to do when entries are not found is up to you or add additional data to the end of the entry to do additional work. Of course, you can use a file if you wish or any other means. Create a separate interactive subsystem to test in first and you're on your way. Tom Liotta On Wed, 29 August 2001, dturk@upt.com wrote: > Is there a way to limit the number of interactive sessions a user (either >twinax > or CA/400) can run on the same as/400? I am aware of the QLMTDEVSSN system >value > to limit a user from signing on at more than 1 workstation, but is there a way > to set a limit, say 5? -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
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.