Restrictions of minimized journal entry data - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

The following MIMIX and operating system restrictions apply:

  • If you plan to use keyed replication do not use minimized journal entry data. Minimized journal entries cannot be used when MIMIX support for keyed replication is in use, since the key may not be present in a minimized journal entry.

  • Minimized before-images cannot be selected for automatic before-image synchronization checking.

Your environment may impose additional restrictions:

  • If you rely on full image captures in the receiver as part of your auditing rules, do not configure for minimized entry data.

  • Even if you do not rely on full image captures for auditing purposes, consider the effect of how data is minimized. The minimizing resulting from specifying *FILE does not occur on field boundaries. Therefore, the entry specific data may not be viewable and may not be used for auditing purposes. When *FLDBDY is specified, file data for modified fields is minimized on field boundaries. With *FLDBDY, entry-specific data is viewable and may be used for auditing purposes.

  • Configuring for minimized journal entry data may affect your ability to use the Work with Data Group File Entries on Hold (WRKDGFEHLD) command. For example, using option 2 (Change) on WRKDGFEHLD to convert a minimized record update (RUP) to a record put (RPT), will result in failure when applied. RPTs requires the presence of a full, non-minimized, record.

See the IBM book, Backup and Recovery for restrictions and usage of journal entries with minimized entry-specific data.