× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It really comes down to what you want to achieve.  If you want to see
who's been changing what objects when, then the security audit journal
weill do that.

If you want to see what's been changed in a file and (perhaps more
importantly) want to either back out changes or apply changes made since
the last save, then you want data base journaling.  

With data base journaling, you can develop a save strategy that will
allow you to recover to a point beyond your nightly save.  

So whether your primary goal is security or recovery will determine
which you should implement first. 


 
 
Jeff Carey
Acxiom Corp.
Phone: 630-944-0216
Fax:  630-944-8941
Pager: jeff_carey@xxxxxxxxxxxxxx
Vote for me for COMMON Board of Directors:
http://www.common.org/about/carey.html

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Candidi
Sent: Monday, May 15, 2006 12:26 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Journaling

That's why I'm asking. I'm trying to get a feel for what's best to start
with. You're .02 is very welcome

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Friday, May 12, 2006 11:24 AM
To: Midrange Systems Technical Discussion
Subject: RE: Journaling

John,

Just my .02 but db journaling tends to be more useful day to day.

Not a week goes by that I don't use the db journal receivers to figure
out what went on or who caused a problem.



Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Candidi
> Sent: Friday, May 12, 2006 11:50 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Journaling
> 
> I think I would like to start with the security auditing then 
> move into the
> db auditing
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
> Sent: Friday, May 12, 2006 9:49 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: Journaling
> 
> John,
> 
> What are you trying to do?
> 
> The article Nick mentioned is talking about Security 
> Auditing.  Security
> Auditing tracks security related changes in the system "Audit 
> Journal."
> 
> In fact, the second paragraph says: "When we speak of 
> security auditing,
> we are not talking about journaling database files and other
> objects. We are not taking before and after images of data records."
> 
> So are you interested in Security Auditing or the journaling 
> of database
> files and other objects?
> 
> If you're interested in both, that's fine.  They are both useful for
> different reasons and every shop should be taking advantage of both.
> - Security Auditing can tell you who change a DB file's 
> properties such
> as the file's owner.
> - DB Journaling can tell you who/what/when/how fields changed in a
> particular record in a DB file.  (The why you have to beat out of the
> who ;-)
> 
> Dan's article is a good point to start for Security auditing.
> 
> Do you have questions about journaling database files and 
> other objects?
> 
> HTH,
> 
> Charles Wilt
> --
> iSeries Systems Administrator / Developer
> Mitsubishi Electric Automotive America
> ph: 513-573-4343
> fax: 513-398-1121
>   
> 
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx 
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Candidi
> > Sent: Friday, May 12, 2006 10:04 AM
> > To: 'Midrange Systems Technical Discussion'
> > Subject: RE: Journaling
> > 
> > I am not 100% sure but what I do know is that I want to start 
> > off with the
> > best basic practice and move forward from there. I guess I am 
> > looking for
> > some experienced advice. The article Nick sent seemed like a 
> > great starting
> > point
> > 
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
> > Sent: Friday, May 12, 2006 6:32 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: Journaling
> > 
> > John,
> > 
> > "journaling" by itself is usually used to refer to journaling data
> > object changes.
> > 
> > However, you mention the CHGOBJAUD command which is used to 
> along with
> > the relevant system and user profile values to control "Audit
> > Journaling"
> > 
> > Which type of journaling are you talking about?
> > 
> > Charles Wilt
> > --
> > iSeries Systems Administrator / Developer
> > Mitsubishi Electric Automotive America
> > ph: 513-573-4343
> > fax: 513-398-1121
> >   
> > 
> > > -----Original Message-----
> > > From: midrange-l-bounces@xxxxxxxxxxxx 
> > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Candidi
> > > Sent: Thursday, May 11, 2006 12:57 PM
> > > To: 'Midrange Systems Technical Discussion'
> > > Subject: Journaling
> > > 
> > > We don't use journaling at the present. I would like to turn 
> > > it on but I'm
> > > not sure of some things?
> > > 
> > >  
> > > 
> > > Should all objects and type be journaled. I don't want to 
> > > journal so much as
> > > to start chewing up storage. I thought we could start bay 
> > > journaling just
> > > object type *FILE changes. 
> > > 
> > >  
> > > 
> > > Can users be on the system when run the chgobjaud job?
> > > 
> > >  
> > > 
> > > I understand this is general but any other thoughts, ideas 
> > > would be welcome
> > > 
> > >  
> > > 
> > > John A Candidi
> > > 
> > > Rutgers Insurance Companies
> > > 
> > > IT Director - AS/400 Manager
> > > 
> > > 856-779-2274
> > > 
> > >  
> > > 
> > >  
> > > 
> > > -- 
> > > 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.
> 
> -- 
> 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.