Skip to main content

Journals & Retrieve Data from Journals

Journaling on IBM i:

On IBM i, Journaling means process of recording an object's activity.

When it comes to journaling of Physical file, It records Open/Close/Write/Update/Delete Operations on Physical file.

How to Start Journaling:

1.      Use the Create Journal Receiver (CRTJRNRCV) command to create a journal receiver.

The journal receiver is where the journal entries are actually recorded. The journal "connects" the receiver to the file.

Also, you should put journal receivers in the same library as the file.

2.      Create a journal. Use the Create Journal (CRTJRN) command to create a journal and specify the receiver created in step 1.

Although you can journal multiple files to the same journal, you will generally want to have a journal "serving" a single file.

3.      Start journaling the file. This is done by using the Start Journal Physical File (STRJRNPF) command.

This is how you associate a file to a journal. Once the association is made, the system will record in the journal receiver a copy of any record added, updated or deleted from the file.

Other activity, such as when the file is opened and closed, can also be recorded in the journal receiver if you choose by selecting the appropriate options on the STRJRNPF command.

Retrieve Data from Journal:

You would get a scenario where records were deleted wrongly or update happened wrongly, You would need to retrieve the data back.

Below are the steps to be followed in order to retrieve data from Journal.

1.     Issue DSPJRN Command by specifying Journal Name & Journalled Physical File Name.

You might want to consider giving specific Journal Receiver Name. By default it would be current Receiver.

2.    Create a Copy of Physical File to include Journal Fields along with Original Physical File Fields.

3.    Use CPYF Command with FMTOPT(*NOCHK) from DSPJRN Outfile to JR file with Journal fields.


DDS of Physical File (TESTFILE):

     A          R TESTFR                                                        
     A            TSFLD1        10A                                             
     A            TSFLD2        10A                                             
     A            TSFLD3        10A                                             
     A            TSFLD4        10A                                             

DDS of JR File with Journal Fields (JRTESTFILE):

     A          R JRTESTFR                                                      
     A            JOENTL         5S 0                                           
     A            JOSEQN        10S 0                                           
     A            JOCODE         1A                                             
     A            JOENTT         2A                                             
     A            JODATE         6A                                             
     A            JOTIME         6S 0                                           
     A            JOJOB         10A                                             
     A            JOUSER        10A                                             
     A            JONBR          6S 0                                           
     A            JOPGM         10A                                             
     A            JOOBJ         10A                                             
     A            JOLIB         10A                                             
     A            JOMBR         10A                                             
     A            JOCTRR        10S 0                                           
     A            JOFLAG         1A                                             
     A            JOCCID        10S 0                                           
     A            JOINCDAT       1A                                             
     A            JOMINESD       1A                                             
     A            JORES          6A                                             
     A            TSFLD1        10A                                             
     A            TSFLD2        10A                                             
     A            TSFLD3        10A                                             
     A            TSFLD4        10A                                             

Issue DSPJRN Command on TESTFILE:


Use CPYF Command to get formatted Output of file data.


You would need to check the scenario where you need to recover the data and can query based on requirement.


Popular posts from this blog

All about READ in RPGLE & Why we use it with SETLL/SETGT?

READ READ is one of the most used Opcodes in RPGLE. As the name suggests main purpose of this Opcode is to read a record from Database file. What are the different READ Opcodes? To list, Below are the five Opcodes.  READ - Read a Record READC - Read Next Changed Record READE - Read Equal Key Record READP - Read Prior Record READPE - Read Prior Equal Record We will see more about each of these later in this article. Before that, We will see a bit about SETLL/SETGT .  SETLL (Set Lower Limit) SETLL accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Corresponding Record (or Next Record if exact match isn't found).  SETGT (Set Greater Than) SETGT accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Next Record (Greater Than the Key value). Syntax: SETLL SEARCH-ARGUMENTS/KEYFIELDS FILENAME SETGT  SEARCH-ARGUMENTS/KEYFIELDS FILENAME One of the below can be passed as Search Arguments. Key Fiel

What we need to know about CHAIN (RPGLE) & How is it different from READ?

CHAIN READ & CHAIN, These are one of the most used (& useful) Opcodes by any RPG developer. These Opcodes are used to read a record from file. So, What's the difference between CHAIN & READ?   CHAIN operation retrieves a record based on the Key specified. It's more like Retrieving Random record from a Database file based on the Key fields.  READ operation reads the record currently pointed to from a Database file. There are multiple Opcodes that start with READ and all are used to read a record but with slight difference. We will see more about different Opcodes and How they are different from each other (and CHAIN) in another article. Few differences to note.  CHAIN requires Key fields to read a record where as READ would read the record currently pointed to (SETLL or SETGT are used to point a Record).  If there are multiple records with the same Key data, CHAIN would return the same record every time. READE can be used to read all the records with the specified Ke

Extract a portion of a Date/Time/Timestamp in RPGLE - IBM i

%SUBDT Extracting Year, Month, Day, Hour, Minutes, Seconds or Milli seconds of a given Date/Time/Timestamp is required most of the times.  This can be extracted easily by using %SUBDT. BIF name looks more similar to %SUBST which is used to extract a portion of string by passing from and two positions of the original string. Instead, We would need to pass a value (i.e., Date, Time or Timestamp ) and Unit (i.e., *YEARS, *MONTHS, *DAYS, *HOURS, *MINUTES, *SECONDS or *MSECONDS) to %SUBDT.  Valid unit should be passed for the type of the value passed. Below are the valid values for each type. Date - *DAYS, *MONTHS, *YEARS Time - *HOURS, *MINUTES, *SECONDS Timestamp - *DAYS, *MONTHS, *YEARS, *HOURS, *MINUTES, *SECONDS, *MSECONDS Syntax: %SUBDT(value : unit { : digits { : decpos} }) Value and Unit are the mandatory arguments.  Digits and Decimal positions are optional and can only be used with *SECONDS for Timestamp. We can either pass the full form for the unit or use the short form. Below i