|
In the short term(2hrs) you'll probably only be able to pull together DASD allocation (based on library or object owners) and a snapshot of users currently on the system. The DASD allocation may be a little complicated if all of your files and journals that are used by completely different applications are owned by the same group profile. It depends on how your applications are split out too. If they're split out into different libraries, that becomes much easier. If they're all thrown into one big library, best of luck to you. If you have your disk collection job running on a regular basis, you can query your QAEZDISK file, rather than wait for a dspobjd on everything on your system to finish just to get the sizes. For processing information in the short term, I think you'll have to 'best guess' it unless you already have job accounting set up. Long term, you'll need to implement job accounting and have had that running for a period of time (Day, week, month, year) to get a true feel for what department's work (based on job accounting code) is resulting in a percentage of total CPU utilization, DASD I/O, etc. If you get it all set up, it should be a snap for you to pull the information out next month (or year). Good luck on your tight deadline. _________________________ Daniel L. Gray Maverick Transportation, Inc.
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.