The Journal Management system has been designed to allow complete tracking of transactions. This is handled by the following programs under Cross Applications > Journal Management menu.

Start journalling – this program begins the Journal Management System. All changes to transactions details will be saved to a temporary journal receiver.
Process journalling – this program processes the files and saves changes to transaction details made up until this point. It must be run as part of End of Day process but can also be run directly from the menu.
Stop journalling – this program stops the Journaling management system and loses all changes transactions details from the last time the details were captured.
Generic journal display of file changes – displays the file changes for review.

Setup for journalling process

The following control files must be setup for the Journal Management process.

Control file
********/JNL-ATTR Journal attributes Defines for each System defined attribute where to put the journals and what the journal is to be named as. This Control File acts as a receiver. The value field can be left blank or a file name can be entered when a record has been changed. The Receiver is used to hold new changes. It receives journals and changes journals and decides how many it can hold before it becomes obsolete and creates a new receiver.
******/JNL-FIL Journal files This Control File defines which file you want to start journalling. Any changes to the file gets recorded. Receive Image: After – when it updates a record it only captures the look of the change Both – when it updates a record it captures the look of the change before and after the change. Primary & Secondary program – Holds the process programs; upto 2 process programs can be run. Process Program is used to read the journal then output into a file with the data structure. For example, for the Customer Masterfile, it writes to a similar customer Masterfile. It creates a journal for the customer Masterfile, with journal day, change day and who changed it followed by the customer Masterfile record. Comment** – optional field

Control file

********/JNL-ATTR Journal attributes

Defines for each System defined attribute where to put the journals and what the journal is to be named as. This Control File acts as a receiver. The value field can be left blank or a file name can be entered when a record has been changed.

The Receiver is used to hold new changes. It receives journals and changes journals and decides how many it can hold before it becomes obsolete and creates a new receiver.

********/JNL-FIL Journal files

This Control File defines which file you want to start journalling. Any changes to the file gets recorded.

Receive Image:

After – when it updates a record it only captures the look of the change

Both – when it updates a record it captures the look of the change before and after the change.

Primary & Secondary program – Holds the process programs; upto 2 process programs can be run. Process Program is used to read the journal then output into a file with the data structure. For example, for the Customer Masterfile, it writes to a similar customer Masterfile. It creates a journal for the customer Masterfile, with journal day, change day and who changed it followed by the customer Masterfile record.

Comment – optional field