Comments on: Data Compression with Remote Journal

By: rhoover

rhoover — Wed, 03 Aug 2011 14:10:58 +0000

The database file is part of a third-party software package so we would prefer not modifying it. As for the Minimized Entry-Specific Data option, it is my understanding that this feature reduces the number of fields recorded in the journal entry to only those that have changed. These records are not changes but adds and they only contain a single field so there are no fields to exclude.
I have discussed this problem with iTera in detail with no resolution. They suggested contacting IBM as iTera HA uses native IBM Remote Journaling. Thought I would try here first. Thanks for the feedback.

By: yorkshireman

yorkshireman — Wed, 03 Aug 2011 08:15:39 +0000

I’d never really thought about this in depth, but surely journal entries are held packed anyway? I clearly recall ‘unpacking’ data from a dump listing in order to restore a critical item which was broken with no backup – years ago. (lucky it dumped!)

By: tomliotta

tomliotta — Wed, 03 Aug 2011 02:29:02 +0000

Without knowing what your process does, the only possibility seems to be the Minimized Entry-Specific Data feature that came other changes to journaling in V5R4. But you'd want to have iTera Support tell you if they support it and what steps you should take to get it working in your environment. Other than that, the only way I can think of is to use a variable length field in the file and don't store trailing blanks in it. Tom