Running utilities autonomically using Db2 Autonomics Director

• Create and schedule the maintenance windows in which utilities are permitted to run.
• View the exceptions (also called symptoms) and utilities (also call actions) that are generated by an autonomic build.
• Review autonomic utility execution output.
• Evaluate your maintenance window workload.
• Fine-tune the maintenance workload by adjusting priorities for actions, symptoms, and objects, thereby ensuring your most important jobs are run first when the maintenance window opens.
• Configure Db2 Automation Tool to send notifications by email or text message when Db2 Automation Tool job profiles are built in batch.

Autonomic actions are generated when Db2 Automation Tool job profiles that are configured for active or passive autonomics are built. Active autonomics creates an action from the output of the build that is scheduled to be run when the maintenance window opens. Passive autonomics creates an action from the output of the build, but the action does not run when the maintenance window opens. However, you can still review the actions, objects, and symptoms that generated the actions on the autonomic panels.

Like the Db2 Automation Tool utility JCL build process, the autonomic build process resolves wildcarded and dependent objects, gathers object information, and evaluates exception criteria. However, instead of writing JCL, the autonomic build process updates several Db2 repository tables, as follows:

• Utility actions on the objects are written to an Autonomics Director actions table.
• Exception criteria that triggered the action is written to an Autonomics Director symptoms table.

To allow the Db2 Autonomics Director stored procedure to run the actions in the actions table, you must define a maintenance window and then schedule it to run. A maintenance window is a specific time period that allows the actions to be run on your objects.

Once a maintenance window is associated with the job profile, when you build the job profile, the autonomic actions are generated from the build. After the associated maintenance window is scheduled and the time period that it is scheduled to run opens, the Autonomics Director stored procedure retrieves actions from the table and starts running them, until it runs out of actions to perform or the maintenance window closes.

 AUTOTOOL V4R3 ------------ Autonomic Console ------------ 2017/11/10  12:27:51 
 Option  ===>                                                                   
 -------------------------------------------------------------------------------
                                                                                
        Options: 1 - Autonomic Object Prioritization                            
                 2 - Autonomic Maintenance Windows                              
                 3 - Autonomic Execution History                                
                 4 - Autonomic Actions                                          
                 5 - Autonomic Statistics Monitor Profiles                      
                 6 - Symptom Registry Editor                                    
                 7 - Action Registry Editor                                     
                 8 - Action/Object/Symptom Priority                             
                 9 - Autonomic Event Notifications                              
                                                                                
 -------------------------------------------------------------------------------
  Db2 Subsystem ID: SS01         User: TWUSR   - Configuration ID: HAA          
 -------------------------------------------------------------------------------