Highlights the changes and improvements made to Journal management.
For V5R4, there are a number of improvements and additions to journal management. The following items contain a summary of these improvements and additions.
SMAPP and access path journaling is now provided for encoded vector indexes and for most access paths with international components for unicode (ICU) sort sequence tables.
The CHGJRN command can now be used to modify the journal receiver threshold value.
The maximum number of objects that can be associated with one journal is now either 250,000 or 10,000,000.
Extension of the QDFTJRN support to allow a user to indicate that data areas and data queues created, moved, or restored into the library should automatically start journaling.
The new receiver size option value *SYSDFT will be the default value on the CRTJRN command and will be an optional value on the CHGJRN command.
A new value for the MINENTDTA parameter, *FLDBDY, allows minimizing file entries on a field boundary. Along with this new minimizing value is a new parameter that can be specified when reading journal entries, Format minimized data (FMTMINDTA). This parameter allows you to specify whether entry specific data which has been minimized on field boundaries will be returned in a readable format.
A new parameter Journal Recovery Count (JRNRCYCNT) added to the Change Journal (CHGJRN) command indicates how many journal entries can exist between the last deposited entry and the oldest forced entry for a journal.
Support has been enhanced for the commands DSPJRN, RCVJRNE, and RTVJRNE and the QjoRetrieveJournalEntries API. These commands have previously been able to selectively return journal entries related to a specific database file or set of database files but have now been extended to include selection capabilities for all objects types eligible for journaling.
Forward recovery support has been added for journaled data queues using save/restore and APYJRNCHG commands.
The enhanced Work with Journals (WRKJRN) command support now includes all object types.
i5/OS™ will provide timely and detailed messages in the event of a Remote Journal failure. If the source system cannot communicate with the target system, the source system will be notified immediately, end the remote journal environment, and provide detailed messages as to the possible cause. Similarly, if the target system cannot communicate with the source system, the target system will be notified immediately, end the remote journal environment, and provide detailed messages as to the possible cause.
The journal entry information finder includes entry-specific data for journal code B integrated file system entries, code E data area operation, code Q data queue operation, and many other journal codes. It also includes documentation for new journal entries added with this release.
To find other information about what's new or changed this release, see the Memo to Users.