Re: Buffering of DB output with *INLR=*OFF

Journaling can be a problem if you don't watch it, but since you are
watching it, it shouldn't be a problem. Just make sure the system doesn't
automatically delete the journal receiver so you can query it for problems.
Delete out old receivers as you don't need them to save on space.

On Tue, Apr 8, 2008 at 3:42 PM, Adam Glauser <adamglauser@xxxxxxxxxxxx>
wrote:

joannegiblin@xxxxxxxxxxxxx wrote:

Why don't you just turn journaling on the file? The journals will tell

you

what you want to know.

Thanks for the suggestion. It's mostly because I'm not really familiar
with the ins and outs of journalling either. Also, this isn't something
that happens regularly, and it seems like I'd have to do a lot of work
to dig out the relevant journal entries. If journalling were already
enabled for this file I'd have tried that route.

Is it really that easy to "just turn journaling on". Given that there
are potentially many updates to this file in a short period of time, it
seems like keeping the information for all changes could present storage
concerns. Again, I'm not familiar with the details so please correct me
if I'm wrong.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.