Definition Base organization and change management

There are two types of Definition Bases (DefBase):

• Object Definition Base
• Calendar Definition Base

You can define only one active Definition Base for each type in a TOMPLEX. Having different Definition Bases for the same TOMPLEX is useful for disaster recovery and change management, and for any specific configuration requirements you might have. 

Use the following procedure when managing changes to objects, sets, and calendar entries:

1. Make a copy of the active Definition Base. On the Definition Bases (TDEFBS) view, use the REPeat command to copy a Definition Base. 

   SuccessBest practice
   If the Object Definition Base you are copying is a layer Definition Base that also contains generated objects or sets, we recommend that you use the TAG and DEPLOY actions for making a copy of the Definition Base. The TAG and DEPLOY actions include options for handling the layer Definition Bases and generated objects and sets.
   

2. Make changes to the copy of the Definition Base. 
3. Deploy the changed copy to the target's active Definition Base.

Using this process does not affect statuses in an active Definition Base. It updates the changed objects, adds new objects, and deletes objects in the active Definition Base that are not in the deployed Definition Base.

You can perform administration from a system or TOMPLEX, and then deploy the changes to the targets. You can use either of the following deployment methods:

• Using the TAG and DEPLOY actions on the TDEFBS view. This method requires that you configure the CAS-to-CAS communication, which makes deployment quick and easy. For more information, see Deploying object and calendar Definition Base changes and Using-distributed-models. 
• Using the REXX EXEC MAMEXPRT DEPLOY(Y). This method creates an import EXEC of a Definition Base package that you can't edit because the item definitions are encoded. You must upload or transfer the import EXEC via other media to the target TOMPLEX and then run it. This method is useful when the central TOMPLEX cannot communicate with the target TOMPLEX. For more information, see Registry-export-utility.