Defaults, classes, and inheritance

Defaults

Defaults are a mechanism that can save you time. SA z/OS provides defaults that are hardcoded for most values. You can also specify your own set of defaults for Applications, Systems, Sysplexes, and MVS Components.

Take the Application Defaults for example. On the Entry Type Selection panel, select 36 ADF (Application Defaults) entry and define a new entry.

  COMMANDS  HELP                                                              
------------------------------------------------------------------------------
                        Application Information Defaults                      
Command ===>  ___________________________________________________________     
                                                                              
Entry Type : Application Defaults  PolicyDB Name   : TEST_PDB                
Entry Name : MY_DEFAULTS           Enterprise Name : TEST_SYSTEMS                
                                                                              
 Captured Messages Limit. . ___        (0 to 999)                             
 Monitor Routine  . . . . . ________   (name NONE)                            
Startup information:                                                          
 Restart after IPL  . . . . _______    (START NOSTART)                        
 Start Delay  . . . . . . . ________   (time for "UP" status checks, hh:mm:ss)
 Start Cycles . . . . . . . __         (start delay checks, 0 to 99)          
 Restart Option . . . . . . _________  (ALWAYS ABENDONLY NEVER)               
Shutdown information:                                                         
 Shutdown Pass Interval . . ________   (hh:mm:ss)                             
 Cleanup Delay  . . . . . . ________   (hh:mm:ss)                             
                                                                              

The defaults are mainly for the timing intervals between various actions that the agent takes during the automation of the resource.

Classes and inheritance

A powerful technique available with the Customization Dialog is that of classes and inheritance. For example, if you are running five Db2® subsystems, you can create a single Db2 Application Class, which holds all of the complicated Db2 automation policies. Then, you link it as the Upward Class of the five Application instances that represent your Db2 subsystem. You do not have to type in and maintain your potentially complex Db2 automation five times.

The following information shows the procedure of this example.

  1. On the Entry Type Selection panel, select 6 APL.
  2. Enter new DB2_CLASS to create a new APL entry type with an Object Type of CLASS.
      COMMANDS  HELP                                                              
    ------------------------------------------------------------------------------
                                       Define New Entry                           
    Command ===> ______________________________________________________________   
                                                                                  
    Define new entry of type Application                                          
                                                                                  
      Entry name . . . . . . . DB2_CLASS                                          
                                                                                  
      Subsystem Name . . . . . ______________                               
      Object Type  . . . . . . CLASS        (CLASS INSTANCE)                      
      Category . . . . . . . . __________   (IBM-defined, user-defined or blank,
                                             see help)  
      Subcategory  . . . . . . __________   (IBM-defined, user-defined or blank,     
                                             see help)        
  3. For the DB2_CLASS entry, fill out the policies only to the degree that is common (or shared) among all Db2 subsystem instances that you plan to create. Follow the same steps that you did when creating other APL entries before.
  4. Define the Db2 subsystems applications. Set Object Type to INSTANCE.
      COMMANDS  HELP                                                               
    ------------------------------------------------------------------------------ 
                                       Define New Entry                            
    Command ===> _____________________________________________________________     
                                                                                   
    Define new entry of type Application                                           
                                                                                   
      Entry name . . . . . . . DB2_T100MSTR_____                                   
                                                                                   
      Subsystem Name . . . . . T100MSTR_____                                       
      Object Type  . . . . . . INSTANCE     (CLASS INSTANCE)                       
      Category . . . . . . . . __________   (IBM-defined, user-defined or blank,
                                             see help)  
      Subcategory  . . . . . . __________   (IBM-defined, user-defined or blank,     
                                             see help)      
      Job Type . . . . . . . . _________    (MVS NONMVS TRANSIENT)                 
      Job Name . . . . . . . . T100MSTR                                            
      Transient Rerun  . . . . ___          (YES NO)                               
  5. In the applications' UPWARD CLASS policy, select the Class you defined in step 1. With this specification, the application that is linked to the class inherits all of the Class’s policies.
     COMMANDS  ACTIONS  VIEW  HELP                                                
    ------------------------------------------------------------------------------ 
                                  Upward Link to Class                  Row 1 of 1 
    Command ===>  ______________________________________________   SCROLL===> PAGE 
                                                                                   
    Entry Type : Application           PolicyDB Name   : TEST_PDB                 
    Entry Name : DB2_T100MSTR          Enterprise Name : TEST_SYSTEMS                 
                                                                                   
    Action      Status     Entry Name            Type        Upward Class Link     
    ________    SELECTED   DB2_CLASS                                               
    ******************************* Bottom of data ********************************