Re: SQL Triggers where Production and Test on Same iSeries

Hi, Michael:

You may also want to look at an open-source tool called "EXPJRNE" available here:

http://www.tools400.de/English/Freeware/Utilities/Utilities.html

It can extract (or "export") journal entries to an externally described database file, where this *OUTFILE has the same fields as the original journaled file, plus extra fields to record the journal information. This makes it easy to analyze journal entries using SQL.

HTH,

Mark S. Waterbury

> On 4/12/2013 1:46 PM, Michael Schutte wrote:

Thanks Gary, quick question though, probably stupid (even though teachers
say there are no stupid questions). We had a pretty big issue occur
yesterday with another file that is journaled. I thought I knew what
caused the issue, however, looking at those programs, it doesn't appear
that my thought was correct. So here I am... I'm thinking about doing this
RCVJRNE command to call a program and track the changes. I understand I
can do RCVJRNE for specified journaled files. But I was wondering, if I
set this up one time for one file in the journal.
1. What happens when I come back and want to add another exit point program
for a different file?
2. Do the program calls line up or does the last RCVJRNE erase theca
previous? Does that make sense?
3. Also is there a way I can see what exit programs are attached to a
journal?
4. Finally, will this interfere any with the QEDD back up stuff? QEDD
currently takes the changes to another box and our back ups are performed
off that box.

thanks again