JKLDEV
JKLDEV is JKL's development server. Though it does not require 24x7 availability, the data on it represent many person hours of work by the developers. Therefore it is important that in the event of a crash, the system be brought to a current state. Also, since it is a development server, changes to the data occur often.
JKLDEV is used by both web and database developers. So several different types of data are stored on this server, including stream files and database files.
JKLDEV journaling strategy
Since many of the objects on JKLDEV are important and changes often, Sharon has decided that they are good candidates for journaling.
JKLDEV is used by both web and database developers, so there are several physical files, and many stream files that she wants to journal. Sharon has decided to do the following:
- Since none of the access paths are critical to her operation, Sharon does not journal access paths.
- To simplify setup and recovery, Sharon assigns all of the objects to one journal.
- Since there are many stream files to journal, Sharon journals the integrated file system directories, in addition to individual files. She elects to use the Current folder and all subfolders option and Journal new files and folders option. This choice ensures that the objects currently in the directory and in any subfolders are journaled and objects that are created in the future are also journaled.
- Since journaling with the Journal new files and folders option can quickly make the journal receiver size grow quickly, she uses system journal-receiver management.
- Because it supports all of the options she has chosen, Sharon sets up journaling on iSeries™ Navigator.
Parent topic:
Scenario: Journal managementRelated concepts
Planning which objects to journal Reasons to journal access paths Object assignment to journals Manual versus system journal-receiver management