Checklist: copy configuration - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Product family
Assure MIMIX™ Software
Product name
Assure MIMIX
Assure MIMIX Administrator Reference
First publish date

Use this checklist when you have installed MIMIX in a new library and you want to copy an existing configuration into the new library.This checklist directs you through the correct order of steps for copying a configuration and completing the configuration.

Supported scenarios: The Copy Configuration Data (CPYCFGDTA) command supports copying configuration data from one library to another library on the same system. After MIMIX is installed, you can use the CPYCFGDTA command.

The supported scenarios are as follows:

Supported scenarios for copying configuration



MIMIX version 10.0

MIMIX version 10.01 

MIMIX version 9.0

MIMIX version 10.02 

1The installation you are copying to must be at the same or a higher level service pack.

2Configuration data for functionality that is not supported in the current version of MIMIX is not copied. To determine what functionality is not supported, run the Check for Deleted Functions (CHKDLTFCN) command on the instance running the older version of MIMIX.

Note: Note:The CPYCFGDTA command is not supported in INTRA environments. 

By default, the CPYCFGDTA command replaces all MIMIX configuration data in the current product library with the information from the specified library. Any configuration created in the product library will be replaced with data from the specified library. This may not be desirable.

To configure MIMIX with configuration information copied from one or more existing product libraries, do the following:

  1. To copy existing configuration data to the new MIMIX product, do the following:

    1. The products in the installation library that will receive the copied configuration data must be shut down for the duration of this procedure. Use topic “Choices when ending replication” in the Assure MIMIX Operations book to end activity for the appropriate products.

    2. Sign on to the system with the security officer (QSECOFR) user profile or with a user profile that has security officer class and all special authorities.

    3. Access the MIMIX Basic Main Menu in the product library that will receive the copied configuration data. From the command line, type the command CPYCFGDTA and press F4 (Prompt).

    4. At the Copy from library prompt, specify the name of the library from which you want to copy data.

    5. To start copying configuration data, press Enter.

    6. When the copy is complete, continue with the next step.

  2. Verify that the system definitions created by the CPYCFGDTA command have the correct message queue, output queues, and job descriptions required. Be sure to check system definitions for the management system and all of the network systems.

  3. Verify that transfer definitions created have the correct three-part name and that the value specified for the transfer protocol is correct. Verify the port number.

    Note: One of the transfer definitions should be named PRIMARY if you intend to create additional data group definitions or system definitions that will use the default value PRIMARY for the Primary transfer definition PRITFRDFN parameter.
  4. Verify that the journal definitions created have the information you want for the journal receiver prefix name, auxiliary storage pool, and journal receiver change management and delete management. The default journal receiver prefix for the user journal is generated; for the system journal, the default journal receiver prefix is AUDRCV. If you want to use a prefix other than these defaults, you will need to modify the journal definition using topic Changing a journal definition.

  5. If you change the names of any of the system, transfer, or journal definitions created by the copy configuration command, ensure that you also update that name in other locations within the configuration.

    Changing named definitions after copying a configuration

    If you change this name

    Also change the name in this location

    System definition, SYSDFN parameter

    • Transfer definition, TFRDFN parameter

    • Data group definition, DGDFN parameter

    Transfer definition, TFRDFN parameter

    • System definition, PRITFRDFN and SECTFRDFN parameters

    • Data group definition, PRITFRDFN and SECTFRDFN parameters

    Journal definition, JRNDFN parameter

    Data group definition, JRNDFN1 and JRNDFN2 parameters

  6. Verify the data group definitions created have the correct job descriptions. Verify that the values of parameters for job descriptions are what you want to use. MIMIX provides default job descriptions that are tailored for their specific tasks.

    Note: You may have multiple data groups created that you no longer need. Consider whether or not you can combine information from multiple data groups into one data group. For example, it may be simpler to have both database files and objects for an application be controlled by one data group.
  7. Verify that the options which control data group file entries are set appropriately.

    1. For data group definitions, ensure that the values for file entry options (FEOPT) are what you want as defaults for the data group.

    2. Check the file entry options specified in each data group file entry. Any file entry options (FEOPT) specified in a data group file entry will override the default FEOPT values specified in the data group definition. You may need to modify individual data group file entries.

  8. Check the data group entries for each data group. Ensure that all of the files and objects that you need to replicate are represented by entries for the data group. Be certain that you have checked the data group entries for your critical files and objects. Use the procedures in the Assure MIMIX Operations book to verify your configuration.

  9. Check how the apply sessions are mapped for data group file entries. You may need to adjust the apply sessions.

  10. Use Table 134 to entries for any additional database files or objects that you need to add to the data group.



    Do the following:

    Planning and Requirements Information

    Library-based objects

    1. Create object entries using Creating data group object entries.

    2. After creating object entries, load file entries for LF and PF (source and data) *FILE objects using Loading file entries from a data group’s object entries.

      Note: Note:If you cannot use MIMIX Dynamic Apply for logical files or PF data files, you should still create file entries for PF source files to ensure that legacy cooperative processing can be used.
    3. After creating object entries, load object tracking entries for *DTAARA and *DTAQ objects that are journaled to a user journal. Use Loading object tracking entries.

    Identifying library-based objects for replication

    Identifying logical and physical files for replication

    Identifying data areas and data queues for replication

    IFS objects

    1. Create IFS entries using Creating data group IFS entries.

    2. After creating IFS entries, load IFS tracking entries for IFS objects that are journaled to a user journal. Use Loading IFS tracking entries.

    Identifying IFS objects for replication


    Create DLO entries using Creating data group DLO entries.

    Identifying DLOs for replication

  11. Do the following to confirm and automatically correct any problems found in file entries associated with data group object entries:

    1. From the management system, temporarily change the Action for running audits policy using the following command: SETMMXPCY DGDFN(name system1 system2) RULE(*NONE) RUNAUDIT(*CMPRPR) 

    2. From the source system, type WRKAUD RULE(#DGFE) and press Enter.

    3. Next to the data group you want to confirm, type 9 (Run rule) and press F4 (Prompt).

    4. On the Run Rule (RUNRULE) display specify *NO for the Use run rule on system policy prompt. Then press Enter.

    5. Check the audit status for a value of *NODIFF or *AUTORCVD. If the audit results in any other status, resolve the problem. For additional information, see Resolving auditing problems and Interpreting results for configuration data - #DGFE audit .

    6. From the management system, set the Action for running audits policy to its previous value. (The default value is *INST.) Use the command: SETMMXPCY DGDFN(name system1 system2) RULE(*NONE) RUNAUDIT(*INST) 

  12. Ensure that object auditing values are set for the objects identified by the configuration before synchronizing data between systems. Use the procedure Setting data group auditing values manually. Doing this now ensures that objects to be replicated have the object auditing values necessary for replication and that any transactions which occur between configuration and starting replication processes can be replicated.

  13. Verify that system-level communications are configured correctly.

    1. Verify that the MIMIX TCP server is started on each system (on each "side" of the transfer definition). You can use the WRKACTJOB command for this. Look for a job under the MIMIXSBS subsystem with a function of LV-SERVER.

    2. Use the Verify Communications Link (VFYCMNLNK) command to ensure that a MIMIX installation on one system can communicate with a MIMIX installation on another system. Refer to topic Verifying the communications link for a data group.

  14. Ensure that there are no users on the system that will be the source for replication for the rest of this procedure. Do not allow users onto the source system until you have successfully completed the last step of this procedure.

  15. Start journaling using the following procedures as needed for your configuration.

    Note: If the objects do not yet exist on the target system, be sure to specify *SRC for the Start journaling on system (JRNSYS) parameter in the commands to start journaling.
  16. Synchronize the database files and objects on the systems between which replication occurs. Topic Performing the initial synchronization includes instructions for how to establish a synchronization point and identifies the options available for synchronizing.

  17. Start the system managers using topic Starting the system and journal managers.

  18. Start the data group using Starting data groups for the first time.