Managing journals

 

This topic provides instructions for managing your journaling environment.

Managing your journaling environment requires these basic tasks:

• Keep records of which objects you are journaling.

• Evaluate the impact on journaling when new applications or logical files are added.

• Regularly detach, save, and delete journal receivers.

Your journal receivers enable you to recover changes to your important objects. They also provide an audit trail of activity that occurs on your system.

Protect your journal receivers by regularly detaching them and saving them; or you can have the system take over the job of changing journal receivers by specifying system journal-receiver management.

• Swapping, deleting, and saving journals and receivers
  The management tasks that you need to perform most often for journaling are swapping journal receivers and saving and deleting journal receivers.

• Evaluation of how system changes affect journal management
  After you have established your journaling environment, you need to keep up with changes that occur on your system.

• Keeping records of journaled objects
  You must always have a current list of objects that you are journaling and their assigned journals. Print a new list whenever you add or remove objects from the journal.

• Security management for journals
  You can use journal management to provide an audit trail of changes that were made to your objects. You can determine which program or user made changes to objects by using the journal entries.

• Displaying information for journaled objects, journals, and receivers
  iSeries Navigator, Control Language commands, and APIs provide several ways for you to display information about journaled objects, journals, and journal receivers.

• Working with inoperable journal receivers
  If you have specified journaling for any objects, the system ensures that you have corrected problems that affect journaling before continuing with operations on those objects. If the attached journal receiver becomes inoperable, the operation that writes a journal entry is interrupted and the system sends an inquiry message that notifies the system operator.

• Comparing journal images
  You can use the Compare Journal Images (CMPJRNIMG) command to compare and list the differences between the before-image of a record and the after-image of that record, or the after-image of a record with the previous after-image of that record.

• Working with IBM-supplied journals
  The operating system and some licensed programs use journals to provide audit trails and assist with recovery.

• Sending your own journal entries
  You can use the Send Journal Entry (SNDJRNE) command or the Send Journal Entry (QJOSJRNE) API to add your own entries to a journal. The system places these entries in the journal's attached journal receiver along with the system-created journal entries.

• Changing the state of local journals
  Local journals can be in one of two states, active or standby. When the journal state of a local journal is active, journal entries are allowed to be deposited to the journal receiver.

 

Parent topic:

Local journal management

Related concepts
Manual versus system journal-receiver management