Quality of service (QoS) includes a journaling function. Journaling allows you to track QoS policy actions when a policy is added, removed, or changed.
Journaling creates a log of policy actions when you turn on the journaling function. This helps you to debug and spot check where policies are not operating as expected. For example, you set a policy to run from 9:00 a.m. to 4:00 p.m. You can check the journal log to see if the policy was actually added at 9:00 a.m. and removed at 4:00 p.m.
If journaling is turned on, journal entries are generated anytime a policy is added, removed, or modified. Using these journals, you create a general file on the system. You can then use the information recorded in your system's journals to determine how your system is being used. This can help you decide to change various aspects of your policies.
Be selective in what you choose to journal. Journaling can be a heavy burden on your system's resources. To start or stop journaling, you use iSeries™ Navigator. To see the journal logs, use the character-based interface.
To start or stop journaling, follow these steps:
If the system is already started before you complete the steps above, stop and restart the system. After journaling has been turned on, there are two ways to activate it. You can stop and restart the system or perform a system update. Either way rereads the policy.conf file and look for the journaling attribute.