Manually deploying configuration changes - assure_mimix - 10.0

You or a MIMIX Services representative can use these instructions to manually deploy configuration changes within MIMIX. You may want to manually deploy configuration to verify that new or changed data group entries for a data group will include all expected objects or to avoid a potentially lengthy delay when starting replication processes for a data group. For an environment that includes a journal-centric data group, you may want to manually deploy configuration to ensure that all objects journaled to the associated user journal are added to the internal list of objects eligible for replication and that any data group object entries or IFS entries that identify objects to exclude or that provide additional qualifying attributes are deployed.

MIMIX automatically deploys configuration information during requests to start data group replication. This occurs the first time a data group is started and on start requests when MIMIX has detected configuration changes for a data group that affect the scope of objects configured for replication (the name space). However, this may take an extended amount of time. For environments that replicate large quantities of IFS objects, this may be significant and may take hours. Manually deploying some or all of the configuration may avoid delays if performed in these scenarios:

• Before the first time you start new data groups. This is recommended.

• Before starting a data group whose configuration has been changed to use journal-centric replication. This is especially true for data groups that replicate large quantities of IFS objects.

• Before starting a data group whose data group IFS entries have changed.

MIMIX uses the deployed information to create an internal list of the current objects being replicated. After the configuration is deployed, MIMIX processes keep the internal list up to date as objects are deleted, moved in or out of the name space, or as other cooperative processing activities affecting the name space are performed.

To manually deploy configuration for a data group, do the following:

1. If the data group is active, do the following:

   1. Perform a controlled end of the data group. See the Assure MIMIX Operations book for how to end a data group in a controlled manner.

   2. Ensure that all pending activity for objects and IFS objects has completed. Use the command WRKDGACTE STATUS(*ACTIVE) to display any pending activity entries. Any activities that are still in progress will be listed.

2. From the source system of the data group, type DPYDGCFG and press F4 (Prompt).

3. The Deploy Data Grp. Configuration (DPYDGCFG) display appears. To identify what will be deployed, do the following:

   1. Specify the data group in the Data group definition prompts.

   2. At the Include entries prompt, specify the type of data group entries you want to deploy.

4. At the Submit to batch prompt, do one of the following:

   • If you do not want to submit the job for batch processing, specify *NO and press Enter to start deploying.

   • To submit the job for batch processing, accept the default. Press Enter to continue with the next step.

5. At the Job description and Library prompts, specify the name and library of the job description used to submit the batch request.

6. At the Job name prompt, accept *CMD to use the command name to identify the job or specify a simple name.

7. To start deploying, press Enter.

If you want to validate the list of objects to be replicated resulting from deploying configuration, use the Replicated Objects portlet in the Assure UI portal.