What's new for IBM® i 7.1
Describes the improvements and additions to journal management.
Object name filtering ability for automatic journaling
When journaling libraries by using the Start Journal Library (STRJRNLIB) command you can now select or omit objects to automatically start journaling based on the name of the object. This allows the ability to automatically start journaling new production files in the library, but not journal temporary work files if they are named uniquely.
- Journaling libraries topic
- Start Journal Library (STRJRNLIB) command
New journal entry types for journal entry codes I and Q
For journal code I - Internal operation, there is a new entry type, IK - Access path protection.
For journal code Q - Data queue operation, there is a new entry type, QF - Change journal object attribute.
For a list of all journal entries by code and type see: All journal entries by code and type
Additional journal entries supported by the Replay Journal Entry (QjoReplayJournalEntry) API
The Replay Journal Entry (QjoReplayJournalEntry) API can now be used to replay the dequeue entries for data queues.
See the Replay Journal Entry (QjoReplayJournalEntry) API for more information.
Additional journal management functions with IBM Navigator for i
- The ability to change journal receivers and attributes associated with a journal.
- The ability to see the properties associated with a journal receiver.
- The ability to see objects journaled to a specific journal.
- The ability to add and remove remote journals.
- The ability to see the list of remote journals associated with a specific journal.
- The ability to activate and inactivate remote journals.
- The ability to view the details of a remote journal connection.
Additional details provided for System-managed access-path protection
Additional details are available for System-managed access-path protection (SMAPP) to provide essential information when there are concerns with the impact SMAPP is having on a system.
See the Effects of SMAPP on performance and storage topic for details.
Automatic restart capability with remote journaling
Remote journaling is dependent on communication networks, these networks occasionally have problems. When communication problems are encountered remote journaling ends. New this release is the capability to have remote journaling automatically restart when it ends because of a recoverable error.
See these items for more information:
Filtering capabilities with remote journal
Historically a remote journal receiver has been a duplicate of the journal receiver associated with the local journal. New this release is the ability to filter entries for a remote journal connection. Filtering out journal entries that are not absolutely needed on the target system can decrease the amount of data sent across the communication line.
See these items for more information:
Additional detail information with remote journal
In a previous release, function was added to allow you to view how far the source system is behind in sending entries to a target remote journal. New in i 7.1 is the ability from the target side to see how many seconds it is behind in receiving journal entries from the source system. Also new in i 7.1 is the ability from the source side to view the number of retransmissions occurring for a remote journal connection.
See the Work with Journal Attributes (WRKJRNA) command for further information.
What's new as of November 2010
The frequently asked questions about journaling and disk arm usage concept was updated. Frequently asked questions about journaling and disk arm usage
How to see what's new or changed
- The
image
to mark where new or changed information begins. - The
image
to mark where new or changed information ends.
To find other information about what's new or changed this release, see the Memo to users.
