OPS/MVS - Correct entries for SSM#SYSLST with SSMGAV2

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Two LPARs running in a plex, A and B. SSM movable tasks were set.  In SSM#SYSLST for both A and B LPARs, the B LPAR name was in SSM#SYSLST and all worked good.  Now the plex was changed to A, B and C LPARs.  How is SSM#SYSLST to be set up properly now?

It is usually recommended: "Lists all of the available alternate systems to which it can move data.".  Before only B system was defined there, but it worked for all moves.  Now with 3 LPARs, how it should be correctly?

Environment

OPS/MVS

Resolution

SSM#SYSLSTS should contain all the systems the resource can move to, that are not the primary system. 
So for example:
RES1     Primary System = SYSA   SSM#SYSLSTS  = SYSB
RES2     Primary System = SYSB   SSM#SYSLSTS  = SYSA
This definition allows both resources to move to both systems even though they have different primary systems. 

Add the new system to the SSM#SYSLSTS of both resources and they can move to all systems.
RES1    Primary System = SYSA   SSM#SYSLSTS  = SYSB SYSC
RES2    Primary System = SYSB   SSM#SYSLSTS  = SYSA SYSC

The resource should only be defined on it's primary system. When it moves, the resource is inserted into the SSM table on the desired system and deleted from the old system. There should only be one definition for each moveable resource. 

Note:  SSM#SYSLST is never changed by the SSMGAV2 application.  It only tells the application where a resource can move to.