|
<snip> it's been my experience that keeping all these devices also slows down ending and staring QINTER </snip> At V5R4 the underlying code was changed so a subsystem that allocates devices can do it multithreaded now. Waaayyyy faster and better. Avoids many of the locks as well. For years I have set up systems to have one subsystem allocate all of the on line devices, and then use a routing program to transfer the job into a subsystem set up just for that type of user. Say accounting, shipping, IT, and shop floor can all have their own subsystems and by definition their own class as well. Now you can control who can use what resources etc. very cleanly. You can put a check in there using some of the API's Scott Klement has talked about to see how many sessions a user has open and limit it, by the user profile. Since it is CL and at V5R4 CL can cleanly get to most of the APIs (Thank you Rochester and Guy Vig!!) you can do almost anything you want. The program is smart enough to recognize operators and push them to the controlling subsystem, and as an added bonus, presents a nice screen that says: "sorry the systems not available right now" if the administrator has the user's subsystem down for any reason. Various folks have taught the advanced work management class at COMMON, me, Paul Weyer, and most recently Larry Bolhuis. If anyone wants the code that accomplishes what I am describing, contact me or Larry Bolhuis privately. Jim Oberholtzer Systems Architect CDW The Right Technology. Right Away.(tm)
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.