IMSRSC repository definitions and MSC

If the MSC links are within an IMSplex, all IMS systems share the same repository defined for the IMSplex. If the MSC links are between IMSplexes, and if the IMSplexes are within the same z/OS® sysplex, each IMSplex can either have its own repository or share the same repository. The repositories in these different IMSplexes can be managed by the same active Repository Server (RS) address space or by a different active RS address space.

The following MSC resources can be maintained in the repository:
  • Remote transactions and transaction descriptors
  • Physical and logical links
  • Link paths
  • Remote logical terminals (LTERMs)
If a remote transaction or a transaction descriptor has a program name associated with it, the program resource is not required to exist in the repository. The program resource associated with the transaction or the transaction descriptor that is defined as local must exist in the repository.
Recommendation: When MSC links are between IMSplexes within the same z/OS sysplex, define one RS and a separate repository for each IMSplex because the separate repositories are easier to manage.

If the MSC links are between IMSplexes, and if the IMSplexes are in different z/OS sysplexes, each IMSplex must have its own repository and RS address space. The repositories of these different IMSplexes must be managed by different RS address spaces.

For the resource definitions that have different attributes among IMS systems (such as the SIDR and SIDL values for each MSC-capable system), the stored resource definitions in the repository consist of a generic section (for the common attributes) and an IMS-specific section (for the attributes that are different for each IMS system).