MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2014

RE: Tracking Changes On Command CHGJOBQE



fixed

AUDJRN will show this.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Friday, August 01, 2014 5:29 PM
To: Midrange Systems Technical Discussion
Subject: Re: Tracking Changes On Command CHGJOBQE

I need to track down date/time and who is making changes.


On Fri, Aug 1, 2014 at 11:43 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

CHGOBJAUD OBJ(QSYS/CHGLIBL) OBJTYPE(*CMD) OBJAUD(*ALL)

CHGLIBL LIBL(QTEMP GPL QGPL PAULSS) of my interactive session.

Then I use either:
DSPJRN JRN(QAUDJRN) RCVRNG(*CURCHAIN) ENTTYP(JS) OUTPUT(*OUTFILE)
OUTFILFMT(*TYPE4) OUTFILE(QGPL/QASYJSJ4) OUTMBR(QASYJSJ4 *REPLACE).
Or
CPYAUDJRNE ENTTYP(CD) OUTFILE(QGPL/QSYSAUD) JRNRCV(*CURCHAIN)

Then SQL the outfile, looking for the library in question.
SELECT * FROM qgpl/QASYJSJ4 WHERE locate ('PAULSS',JOESD ) <> 0

In this case, I'm able to identify anytime CHGLIBL was used, adding
PAULSS to the library list.
I'm actually using this to confirm that a library is no longer used
and can be deleted.

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Bryan Dietz
Sent: Friday, August 01, 2014 10:42 AM
To: Midrange Systems Technical Discussion
Subject: Re: Tracking Changes On Command CHGJOBQE

what parms did you use for CHGOBJAUD?

What do what to know about the command usage?
Are you interested in who is using it or what parms are the using?

Better to read the manuals for the IBM exit programs, but in a few
words they are called when you register a command with them.
All the parms from the command are then "presented" to your exit program.

There are lots of examples out there in the inter-webs too.

--
bryan


Steinmetz, Paul said the following on Fri, 8/1/2014 10:23 AM:
Bryan,

I just did something similar with CHGLIBL, ADDLBLE, EDTLIBL.
I used CHGOBJAUD to turn on auditing for these commands.

What is different by using:
QIBM_QCA_CHG_COMMAND
QIBM_QCA_RTV_COMMAND

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Bryan Dietz
Sent: Friday, August 01, 2014 9:40 AM
To: Midrange Systems Technical Discussion
Subject: Re: Tracking Changes On Command CHGJOBQE

you should be able to also use one of these:
QIBM_QCA_CHG_COMMAND
QIBM_QCA_RTV_COMMAND

then you could save(log) any of the information entered in the command.

using the audit journal you can see who used the command.
Not sure that you see what changed.

--
Bryan

Jack Kingsley said the following on Fri, 8/1/2014 5:45 AM:
It appears the only way to log these changes to QAUDJRN is with
CHGOBJAUD.

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

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






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact