Minimized entry-specific data for journal entries

On the Create Journal (CRTJRN) and Change Journal (CHGJRN) commands, you can specify to allow for the deposit of minimized journal entries. This will decrease the size of your journal entries.

When you specify the Minimized Entry Specific Data (MINENTDTA) parameter for an object type, the entry-specific data for the entries of those object types can be minimized. You can minimize journal entries for database physical files and data areas.

The system only minimizes entries if the minimized entry is smaller in size than a complete journal entry deposit. Therefore, even if you specify this option, not all entries that are deposited will be minimized. The Display Journal (DSPJRN) command, Receiver Journal Entry (RCVJRNE) command, Retrieve Journal Entry (RTVJRNE) command, and QjoRetrieveJournalEntries API return data that indicates whether the entry is actually minimized.

Start of changeThe *FILE, *DTAARA, and *FLDBDY values are allowed on the MINENTDTA parameter for the CRTJRN and CHGJRN commands and indicate the following: End of change

Start of change*FILE End of change
Journaled files may have journal entries deposited with minimized entry specific data. The minimizing will not occur on field boundaries, and the entry specific data may not be viewable and may not be used for auditing purposes. This value cannot be specified if *FLDBDY is specified.
Start of change*FLDBDYEnd of change
Journaled files may have journal entries deposited with minimized entry specific data. The minimizing will occur on field boundaries, and the entry specific data will be viewable and may be used for auditing purposes.Start of change
  • The DSPJRN command always displays the entries which have been minimized on field boundaries with formatting.
  • Start of changeThe *FILE value is not available in releases prior to V5R4.End of change
End of change
Start of change*DTAARA End of change
Start of changeJournaled data areas may have journal entries deposited with minimized entry specific data.End of change
Note: Start of changeYou cannot save or restore a journal receiver with minimized journal entries to any release prior to V5R1M0, nor can they be replicated to any remote journal on a system at a release prior to V5R1M0.End of change

Start of changeAn optional parameter, Format minimized data (FMTMINDTA), is available on the Retrieve Journal Entries (RTVJRNE) command, the Receive Journal Entries (RCVJRNE) command, and the Retrieve Journal Entries (QjoRetrieveJournalEntries) API. This parameter allows you to specify whether entry specific data which has been minimized on field boundaries will be returned in a readable format, which allows you to determine what changes have been made. The possible values for the FMTMINDTA parameter are *NO or *YES, with the default being *NO. By default, the methods used by these commands provide the data in their raw format. The RTVJRNE command will indicate whether or not *FLDBDY has been specified for Minimized entry specific data with a value of ‘2’ in the already existing “MINIMIZED ENTRY DATA” field for the appropriate entry formats. *FILE and *DTAARA will appear as '1' in their fields.End of change

Start of changeUsing the Display Journal (DSPJRN) command, entries are viewable to the screen, an outfile, or printed output. The DSPJRN command will also indicate whether or not the *FLDBDY value has been specified for Minimized entry specific data on the “Display Journal Entry” panel and will indicate a value of ‘2’ in the “Minimized entry specific data” field of the *OUTFILE and in the “Min” field of the printed output. *FILE and *DTAARA will appear as '1' in their fields.End of change

See the Journal code finder link below to see which entries are eligible for minimization. See the Considerations for entries which contain minimized entry-specific data link for more information and considerations when using these entries.

Start of changeSUBJECT TO ANY STATUTORY WARRANTIES WHICH CANNOT BE EXCLUDED, IBM, ITS PROGRAM DEVELOPERS AND SUPPLIERS MAKE NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT, REGARDING THE PROGRAM OR TECHNICAL SUPPORT, IF ANY. End of change

Start of changeUNDER NO CIRCUMSTANCES IS IBM, ITS PROGRAM DEVELOPERS OR SUPPLIERS LIABLE FOR ANY OF THE FOLLOWING, EVEN IF INFORMED OF THEIR POSSIBILITY: End of change

Start of change
  1. LOSS OF, OR DAMAGE TO, DATA;
  2. DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES, OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES; OR
  3. LOST PROFITS, BUSINESS, REVENUE, GOODWILL, OR ANTICIPATED SAVINGS.
End of change

Start of changeSOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF DIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, SO SOME OR ALL OF THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU.End of change

Related concepts
iSeries Navigator versus the character-based interface for journaling objects
Considerations for entries which contain minimized entry-specific data
Related tasks
Methods to estimate the size of a journal receiver
Related reference
Create Journal (CRTJRN) command
Change Journal (CHGJRN) command
Related information
Journal code finder