Like your update, the insert must have some way to not use commitment
control. Perhaps like:
INSERT ... WITH NC
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/db2/rbafzbackup.htm
Or, you could stop fighting journalling and just go with it. Disk space
concerns might be addressable by doing a CHGJRNRCV immediately prior to
your backup, and having the backup delete any journals that have been
backed up.
Honestly, there are some performance concerns with journalling. We ended
up purchasing IBM's
Resource
ID Option Feature Description
5770SS1 42 5117 HA Journal Performance
That significantly helped our month end's. Much more so than SSD's did.
Rob Berendt
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.
midrange.com
