RE: CHGJRN

["Peter Colpaert" <Peter.Colpaert@xxxxxxxxxxxx>]

Andy,

I think I found what was the problem: we were convinced that _every_ update
was supposed to be journaled, but apparently only updates that have a
different UB and UP image are written to the journal, and not those records
where the contents of the fields was not changed, or overwritten with the
same value it already contained.

So I guess it's not a hole in the reliability of journaling.

This said, however, I do believe that it would be better if there were an
option to include _all_ updates in the journal, similar to the TRGUPDCND
(*ALWAYS) keyword for ADDPFTRG.

Anyway, thanks to all those who responded.

Peter Colpaert
Application Developer

Honda Europe NV
Langerbruggestraat 104
B-9000 GENT
Peter.Colpaert@honda-eu.com
Tel: +32 9 2501 334
Fax: +32 9 2501 231
----------
Yoda of Borg are we: Futile is resistance. Assimilate you, we will.
----------




"Andy Nolen-Parkhouse" <aparkhouse@attbi.com>@midrange.com on 20/08/2002 
12:13:48
Please respond to midrange-l@midrange.com
Sent by:  midrange-l-admin@midrange.com

To:   <midrange-l@midrange.com>

cc:

Subject:  RE: CHGJRN


Peter,

What you are describing is very important.  While it may be necessary to
find a work-around, I would encourage you to open a problem with IBM.
Journaling is the basis for system recovery in a number of scenarios and
you have described a gaping hole in its reliability.  If a transaction
cannot be recovered or recreated using a journal, what good is the
database?  Unless journaling is ended, _all_ changes _must_ be
journaled.  If IBM thought they were doing a good thing by having the
CHGJRN command process asynchronously, perhaps they need to rethink.

Regards,
Andy Nolen-Parkhouse







______________________________________________________________________
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
the entity to whom it is addressed and others authorised to receive it. If
you have received it by mistake, please let the sender know by e-mail reply
and delete it from your system.
If you are not the intended recipient you are hereby notified that any
disclosure, copying, distribution or taking any action in reliance of the
contents of this information is strictly prohibited and may be unlawful.
Honda Europe NV is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.