JKLPROD
JKLPROD is the system that JKL uses for all of their customer orders and where their business applications are installed (inventory control, customer orders, contracts and pricing, accounts receivable). The information about this server is extremely critical to their business and changes often.
Also, there are several users who have remote access to the system from home connection. In addition, even though the company's web site is static, the company has plans to establish a transactional site. Because of the importance of the information about JKLPROD, Sharon wants to be able to audit the activity that occurs on the system.
JKLPROD journaling strategy
Since the objects on JKLPROD are crucial to JKL, and since they change often, Sharon has decided that they are good candidates for journaling.
- Since there are access paths that are critical to her operation, Sharon journals access paths.
- Sharon already separates the information about JKLPROD on separate disk pools:
- Disk pool 2 - inventory control
- Disk pool 3 - customer orders
- Disk pool 4 - contracts and pricing
- Disk pool 5 - accounts receivable
Since the journal and the journaled objects must be in the same disk pool, Sharon creates four journals.
- Since she wants to audit the activity that occurs on the system, and since people have remote access to the system, Sharon journals fixed-length data using the following values:
- Job name (*JOB)
- User profile (*USR)
- Program name (*PGM)
- Remote address (*RMTADR)
- Since Sharon is using the FIXLENDTA parameter, she cannot minimize the fixed-length portion of the journal entries.
- Because she is using the FIXLENDTA parameter for all of the journals, and since she is journaling access paths Sharon uses the character-based interface to set up journaling.
Parent topic:
Scenario: Journal managementRelated concepts
Planning which objects to journal Reasons to journal access paths iSeries Navigator versus the character-based interface for journaling objects