Considerations for save-while-active - 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

If a file is being saved and it shares a journal with another file that has uncommitted transactions, then the file may be successfully saved by using a normal (non save-while-active) save. This assumes that the file being saved does not have uncommitted transactions. If you disable save-while-active, attempts to save any type of object will use a normal save.

In addition to providing the ability to enable the use of save-while-active for object types other than *FILE, MIMIX provides the abilities to control the wait time when using save-while-active or to disable the use of save-while-active for all object types.

Save-while-active wait time

For the default (*FILE objects), MIMIX uses save-while-active with a wait time of 120 seconds on the initial save attempt. MIMIX then uses normal (non save-while-active) processing on all subsequent save attempts if the initial save attempt fails.

You can configure the save-while-active wait time when specifying to use save-while-active for the initial save attempt of a *FILE, a DLO, or and IFS object. When specifying to use save-while-active, the first attempt to save the object after delaying the amount of time configured for the Second retry delay interval (RTYDLYITV2) value will also use save-while-active. All other attempts to save the object will use a normal save.

Note: Although MIMIX has the capability to replicate DLOs using save/restore techniques, it is recommended that DLOs be replicated using optimized techniques, which can be configured using the DLO transmission method under Object processing in the data group definition.