Using contextual (*ANY) transfer definitions - 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-06-11
ft:lastPublication
2024-06-11T18:33:16.692940

When the three-part name of transfer definition specifies the value *ANY for System 1 or System 2 instead system names, MIMIX uses information from the context in which the transfer definition is called to resolve to the correct system. Such a transfer definitions is called contextual transfer definition.

For remote journaling environments, best practice is to use transfer definitions that identify specific system definitions in the thee-part transfer definition name. Although you can use contextual transfer definitions with remote journaling, they are not recommended. For more information, see Considerations for remote journaling.

In MIMIX source-send configurations, a contextual transfer definition may be an aid in configuration. For example, if you create a transfer definition named PRIMARY SYSA *ANY. This definition can be used to provide the necessary parameters for establishing communications between SYSA and any other system.

The *ANY value represents several transfer definitions, one for each system definition. For example, a transfer definition PRIMARY SYSA *ANY in an installation that has three system definitions (SYSA, SYSB, INTRA) represents three transfer definitions:

  • PRIMARY SYSA SYSA

  • PRIMARY SYSA SYSB

  • PRIMARY SYSA INTRA