Dynamic Resources

The concept of dynamic resources was introduced to primarily address automated (DevOps) deployment scenarios for single address spaces, for example, APLs representing CICS and IMS regions and USS resources. Its purpose is to have one or more predefined templates in the policy that can be used by operators or automation to dynamically bring these resources into the scope of SA z/OS without running through a policy build and refresh cycle.

The general steps to use dynamic resources and a few things to consider are as follows.
  1. Set up the backend database to store dynamic resources. System Automation offers two options to store dynamic resources: its internal data store and IBM Db2 for z/OS (the later option is enabled in OA63123). Technically, dynamic APL resources are persisted in the backend database rather than the policy and automation control file. Therefore, it is a prerequisite to run through the documented setup for the backend database when you plan to use dynamic resources.

    You need to choose between the two database options. You cannot switch back and forth between the database. Once you choose between any one, the data would be fetched and inserted into the database chosen.

    Note: If the database is not available, INGDYN will issue an error. Also, in a policy refresh or automation restart scenario, the creation of dynamic resources depends on the availability of the database. In case of issues with the database availability, the automation of dynamic resources is delayed in such a refresh or restart scenario until the database is available again.
  2. Define one or more APLs with type TEMPLATE in the Customization Dialog.
    • Templates support only limited CLASS inheritance. If class inheritance is used, relationships, trigger, service periods, runtoken, and desired available status are not inherited. Since templates can be considered as a 'class concept' itself, it is recommended to specify everything on the template.
    • Dynamic resources cannot be supporting resources for other resources.
  3. Build and refresh the configuration. No automation resources are created at build time. However, the template information is made available to the agents on all systems in the SAplex.
  4. Operators can use the INGDYN command at runtime to create dynamic APL resources based on the available templates. No build and refresh is needed.
    • A dynamic resource that is created by INGDYN is initially placed into a suspended state. It is expected that an operator or other automation (for example, via INGDYN AOFEXC29 exit) resumes the newly created resource.
    • If a dynamic resource is added to a hosting APG during INGDYN creation processing and this group is a MOVE or SERVER group, the resource will be added as an 'operator' role for model 2 groups and with preference value 1 for model 1 groups. It is expected that an operator or other automation sets the expected role or preference value via INGGROUP command before resuming it.

This process enables you to apply enterprise policies to the content of a template via the existing change control mechanisms, while giving additional speed and flexibility to create resources at runtime based on template definition.

For more information, see policy dialog help for templates as well as command help in particular for INGDYN.