Troubleshooting
Problem
Customer defined a sysplex move group (APG) consisting of 2 applications he wanted to alternate between 2 systems and found that the movement of the applications between systems was not taking place as expected.
Cause
Let's examine sample definitions to illustrate this situation:
Customer used SA tso dialog to define an application (APL) resource called APPLX. It was defined to run on two systems by linking it to the required system level application groups (APG). Customer also has a service period (SVP) linked to APPLX to govern its normal operating schedule. Customer also created a sysplex type MOVE application group (ie. MOVEAPLX) and selected the APPLX resource to be in that new group.
When customer used the INGGROUP panel and changed MOVEAPLX preference so that the underlying resource would start on an alternate system, they found no requests sent to stop the resource on the original system nor to start it on the new alternate system.
Resolving The Problem
The customer found that there was an override on the SVP for the alternate system to keep the affected resource down, because the SVP was linked to the application rather than the group.
In order to employ a service period (SVP) for applications involved in a MOVE group, the SVP should be linked to the application group (APG) rather than the application instance (APL). This makes administration of SVPs much easier when dealing with groups of common resources that share the same scheduling times.
When customer removed the override and modified the SVP linkage definition (followed by SA PDB build and INGAMS REFRESH), the expected behavior was now observed and the application resource was able to move between the systems.
Product Synonym
SA SAzOS SAz
Was this topic helpful?
Document Information
Modified date:
08 August 2018
UID
swg21192044