Checklist: manually converting to default cooperative processing for files - assure_mimix - 10.0

Perform the following steps from the management system to enable an existing data group to use default cooperative processing for files

1. Verify the environment meets the requirements and restrictions. See Requirements and limitations of default cooperative processing for files.

2. Apply any IBM PTFs (or their supersedes) associated with IBM i releases as they pertain to your environment. Log in to Support and refer to the Technical Documents page for a list of required and recommended IBM PTFs.

3. Verify that the System Manager jobs are active. See Starting the system and journal managers.

4. Verify that data group is synchronized by running the MIMIX audits. See Verifying the initial synchronization.

5. Use the Work with Data Groups display to ensure that there are no files on hold and no failed or delayed activity entries. Refer to topic “Preparing for a controlled end of a data group” in the Assure MIMIX Operations book.

   Note: Topic “Ending a data group in a controlled manner” in the Assure MIMIX Operations book includes subtask “Preparing for a controlled end of a data group” and the other subtasks needed for Step 6 and Step 7.

6. Perform a controlled end of the data group you are converting. Follow the procedure for “Performing the controlled end” in the Assure MIMIX Operations book.

7. Ensure that there are no open commit cycles for the database apply process. Follow the steps for “Confirming the end request completed without problems” in the Assure MIMIX Operations book.

8. From the management system, change the data group definition so that the Cooperative journal (COOPJRN) parameter specifies *USRJRN. Use the command:

   
             CHGDGDFN DGDFN(
             name system1 system2
             ) COOPJRN(*USRJRN) 

9. Ensure that you have one or more data group object entries that specify the required values. These entries identify the items within the name space for replication. You may need to create additional entries to achieve desired results. For more information, see Identifying logical and physical files for replication.

10. To ensure that new files created while the data group is inactive are automatically journaled, ensure that MIMIX starts library journaling or creates QDFTJRN data areas as needed in the libraries configured for replication of cooperatively processed files, data areas, and data queues. This can be done by running the following command from the source system:

     SETDGAUD DGDFN(name system1 system2) OBJTYPE(*AUTOJRN) 

    Note: The libraries are subject to some limitations. For a list of restricted libraries and other details of requirements for implicitly starting journaling, see What objects need to be journaled.

11. From the management system, use the following command to load the data group file entries from the target system. Ensure that the value you specify (*SYS1 or *SYS2) for the LODSYS parameter identifies the target system.

    
              LODDGFE DGDFN(
              name system1 system2
              ) CFGSRC(*DGOBJE) UPDOPT(*ADD) LODSYS(
              value
              ) SELECT(*NO) 

    For additional information about loading file entries, see Loading file entries from a data group’s object entries.

12. Start journaling for all files not previously journaled. See Starting journaling for physical files.

13. Start the data group specifying the command as follows:

    
              STRDG DGDFN(
              name system1 system2
              ) CLRPND(*YES) 

14. Verify that data groups are synchronized by running the MIMIX audits. See Verifying the initial synchronization.