Adding or changing a data group IFS entry - 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
Note: If you are converting a data group to use user journal replication for IFS objects, use this procedure when directed by Checklist: Change *DTAARA, *DTAQ, IFS objects to user journaling.

New or changed IFS entries become available to audits at the start of the next audit and to replication processes after replication processes for the data group are ended and restarted.

From the management system, do the following to add a new data group IFS entry or change an existing IFS entry:

  1. From the MIMIX Intermediate Main Menu, type a 1 (Work with data groups) and press Enter.

  2. From the Work with Data Groups display, type a 22 (IFS entries) next to the data group you want and press Enter.

  3. The Work with Data Group IFS Entries display appears. Do one of the following:

    • To add a new entry, type a 1 (Add) next to the blank line at the top of the display and press Enter.

    • To change an existing entry, type a 2 (Change) next to the entry you want and press Enter. (IFS entries with a process type of *INCLD (A) cannot be changed.)

  4. The appropriate Data Group IFS Entry display appears. When adding an entry, you must specify a value for the System 1 object prompt.


    • The object name must begin with the '/' character and can be up to 512 characters in total length. Any component of the object name contained between two '/' characters cannot exceed 255 characters in length.

    • The object name can be a simple name, a name that is qualified with the name of the directory in which the object is located or a basic generic name. Press F1 (Help) for descriptions.

    • You can also specify an advanced generic name in an IFS entry that specifies *EXCLD for process type. If you specify consecutive asterisks (*) or forward slashes (/) in the path, they will be compressed to one character in the resulting DG IFS entry. An IFS entry with an advanced generic name acts as a filter to exclude objects that would otherwise be included by an existing entry with a basic generic name.

    • All objects in the specified path are selected. When changing an existing IFS entry to enable replication from a user journal (COOPDB(*YES)), make sure that you specify only the IFS objects you want to enable.

  5. If necessary, specify values for the System 2 object and Object auditing value prompts.

  6. At the Object type prompt, specify *ALL to replicate all supported IFS object types within the IFS directory, or specify *DIR to replicate only objects of type *DIR.

  7. At the Process type prompt, specify whether resulting data group object entries should include (*INCLD) or exclude (*EXCLD) the identified objects. If you specified *DIR for the Object type, you must specify *INCLD here.

  8. Specify the appropriate value for the Cooperate with database prompt. To ensure that journaled IFS objects can be replicated from the user journal, specify *YES. To replicate from the system journal, specify *NO. If you specified *DIR for the Object type, you must specify *NO here.

  9. If necessary, specify a value for the Object retrieval delay prompt.

  10. Press F10 (Additional parameters).

  11. If the changes you specify on the command result in adding objects into the replication namespace, those objects need to be synchronized between systems. At the Synchronize on start prompt, specify the value for how synchronization will occur:

    • The default value is *NO. Use this value when you will use save and restore processes to manually synchronize the objects. If you do not synchronize before replication starts, the next audit that checks all objects (scheduled or manually invoked) will attempt to synchronize the objects if recoveries are enabled and differences are found.

    • The value *YES will request to synchronize any objects added to the replication namespace through the system journal replication processes. This may temporarily cause threshold conditions in replication processes.

    • If necessary, specify a value for the Attributes to ignore prompt. This parameter allows auditing to ignore detected attribute differences to streamline environments that use non-switchable data groups and data groups whose target node is a replicate node of an application group. For other configurations, this parameter is ignored.

  12. Press Enter to create or change the IFS entry.

    Note: If the entry specified an advanced generic name and a process type of *EXCLD, you will see a confirmation display. Press Enter to confirm your choices.
  13. For IFS entries configured for user journal replication, if you were directed to this procedure from Checklist: Change *DTAARA, *DTAQ, IFS objects to user journaling, return to Step 7 to proceed with the additional steps necessary to complete the conversion.

  14. Manually synchronize the IFS objects identified by this data group object entry before starting replication processes. You can skip this step if you specified *YES in Step 11. The entries will be available to replication processes after the data group is ended and restarted. The next time an audit that checks all objects runs, the entries will be available and the MIMIX audits will attempt to synchronize the objects they identify if recoveries are enabled.