|
Job accounting will not solve your problem, unless you are willing to do a CHGJOB before and after the program is called. It could be done in a wrapper job of CL. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com "Mike" <mshaw2456@comcas t.net> To Sent by: "'Midrange Systems Technical midrange-l-bounce Discussion'" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 05/10/2004 04:35 Subject PM RE: Program Usage Accounting Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Gord, Have you considered turning job accounting on? It will do what you are asking. It will also give you some basic performance info as well. Check the InfoCenter for setup of job accounting. <hth> Regards, Mike Shaw -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gord Hutchinson Sent: Monday, May 10, 2004 12:53 PM To: 'Midrange Systems Technical Discussion' Subject: Re: Program Usage Accounting On Mon, 10 May 2004 12:40:49 -0700, "Graap, Ken" <keg@xxxxxxxxxxxxx> wrote: >Gord - I would think that you could set up object auditing for this program: > >CHGOBJAUD OBJ(LIB_NAME/PGM_NAME) OBJTYPE(*PGM) OBJAUD(*ALL) > >Then query the audit journal for appropriate journal records (T/ZC and T/ZR) I should have been more specific. I need the usage for ALL application programs. We're interested in a ranking of most used programs. This just means that the object auditing would have to set up for all *PGM objects. I'll look into this. >My only concern is whether or not using a program constitutes a *READ (???) >Does anyone know if it does? Access Code 2 is listed as access type 'Activate Program which sounds encouraging. Thanks Gord -- Gord Hutchinson Database Administrator, IT TST Overland Express ghutchinson@xxxxxxxxxxxxxxx 905-212-6330 fax: 905-602-8895 _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.