Configuration planning tips for independent ASPs - 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

A job can only reference one independent ASP at a time. Storing applications and programs in SYSBAS ensures that they are accessible by any job. Data stored in an independent ASP is not accessible for replication when the independent ASP is varied off.

For database replication and replication of objects through Advanced Journaling support, due to the requirement for one user journal per data group, it is not possible for a single data group to replicate both SYSBAS data and ASP group data.

For object replication of library-based objects through the system journal, you should configure related objects in SYSBAS and an ASP group to be replicated by the same data group. Objects in SYSBAS and an ASP group that are not related should be separated into different data groups. This precaution ensures that the data group will start and that objects residing in SYSBAS will be replicated when the independent ASP is not available.

Note: To avoid replicating an object by more than one data group, carefully plan what generic library names you use when configuring data group object entries in an environment that includes independent ASPs. Make every attempt to avoid replicating both SYSBAS data and independent ASP data for objects within the same data group. See the example in Configuring library-based objects when using independent ASPs .