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

Hi Adam,

Starting journalling is easy, and I noted that you use DBU, which makes looking at the resulting journal entries easy as well. The only trick is stopping journalling when you're done -- you'll need exclusive access to end journalling.

CRTJRNRCV JRNRCV(MyLib/MyRcvr) THRESHOLD(5000)

CRTJRN JRN(MyLib/MyJrn) JRNRCV(MyLib/MyRcvr) MSGQ(MyUserID) MNGRCV(*SYSTEM)

STRJRNPF FILE(lib/file) JRN(JRN) IMAGES(*BOTH) OMTJRNE(*OPNCLO)

To look at the journal, you can use

DSPJRN JRN(MyLib/MyJrn)

or

DBU FILE(MyLib/MyJrn) DBUTYP(*JRN)

DBU will prompt you for the file name and the same stuff as the DSPJRN command concerning date and time ranges of entries you want to look at. The nice thing about using DBU is that it shows the record images broken down into fields, as if you were using it to look at the file's records.

hth,
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

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