SSM - SSMGA - Support of Like-Named Resources within Same SSMGAplex

Idea created by DaveB80129 on Jul 9, 2018
    Currently Planned
    • mikepitchley
    • Keijones
    • crbeeler
    • DavidSleeman
    • DaveB80129
    • teresa.mcclintic
    • Evans_John

    I have a high availability system resource that runs on two systems in a four system z/OS SYSPLEX -- as the same started task name. Due to its importance, I need to be able to use SSMGAv2 to relocate it between different systems in staggered fashion. But this configuration setup and the current capabilities of SSMGAv2 do not allow for this option. The workaround recommended by CA is to create unique names as they are used as the key to create the SYSPLEX variables. I'd like to suggest that part of the key used to build the SYSPLEX variables include the primary_system value within the key. Or other method?