Keeping track of changes to scheduling objects

Keep a detailed auditing track of all changes to scheduling objects in your environment

Maintaining and keeping control of a complex scheduling environment can be a challenging task: multiple schedulers, operators, and administrators have access to the job flows and can implement changes. Regardless of the complexity of this task, however, you must keep a record of every change being implemented. You can now easily track down everything with IBM® Workload Scheduler and obtain detailed reports with just a few clicks using the integration with Tivoli Common Reporting.

Administrators can optionally enforce a policy by which each user making a change to an object must provide a justification for the change.

Administrators can maintain an audit trail, consisting of detailed information about the user who performed the change, the time and date when the change was performed, the reason why the change was implemented, and the details of the change for every modified item.

From the Dynamic Workload Console, IBM Workload Scheduler administrators, operators, and schedulers can review all changes to scheduling objects, both in the database and in the plan, discover which user performed a specific change, and the time and date when the change was performed.

Schedulers can review the history of all changes made on a specific object at any time and check previous versions of the object in scheduling language.

For more information, see Keeping track of changes to scheduling objects

You can find more information and a detailed business scenario in the Stay in control of your workload video.

This new feature causes three changes in your default optman settings:
auditStore
When you upgrade the master domain manager from a previous release, the default value for this global option is changed. The default value is now both. If you customized the default value in the previous release, the value is overwritten with the new value, with the exception of the auditStore option with the DB value assigned. If the auditStore option was set to DB, this value is maintained and is not overwritten.
enDbAudit
When you upgrade the master domain manager from a previous release, the default value for this global option is changed. The default value is now 1. If you customized the default value in the previous release, the value is overwritten with the new value
enPlanAudit
When you upgrade the master domain manager from a previous release, the default value for this global option is changed. The default value is now 1. If you customized the default value in the previous release, the value is overwritten with the new value