Creating a collision resolution class - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

To create a collision resolution class, do the following:

  1. From the Work with CR Classes display, type a 1 (Create) next to the blank line at the top of the display and press Enter.

  2. The Create Collision Res. Class (CRTCRCLS) display appears. Specify a name at the Collision resolution class prompt.

  3. At each of the collision point prompts on the display, specify the value for the type of collision resolution processing you want to use. Press F1 (Help) to see a description of the collision point.

    Note: You can specify more than one method of collision resolution for each prompt by typing a + (plus sign) at the prompt. With the exception of the *HLDERR method, the methods are attempted in the order you specify. If the first method you specify does not successfully resolve the collision, then the next method is run. *HLDERR is always the last method attempted. If all other methods fail, the member is placed on hold due to error.
  4. Press Page Down to see additional prompts.

  5. At each of the collision point prompts on the second display, specify the value for the type of collision resolution processing you want to use.

  6. If you specified *EXITPGM at any of the collision point prompts, specify the name and library of program to use at the Exit point prompt.

  7. At the Number of retry attempts prompt, specify the number of times to try to automatically synchronize a file. If this number is exceeded in the time specified in the Retry time limit, the file will be placed on hold due to error

  8. At the Retry time limit prompt, specify the number of maximum number of hours to retry a process if a failure occurs due to a locking condition or an in-use condition.

    Note: If a file encounters repeated failures, an error condition that requires manual intervention is likely to exist. Allowing excessive synchronization requests can cause communications bandwidth degradation and negatively impact communications performance.
  9. To create the collision resolution class, press Enter.