Issue in Vantage with volume ADD

Products

• Vantage Storage Resource Manager

Issue/Introduction

We have active functionalities of SAMS ( scripts, automation and volume add ) running on one LPAR which is xxxx and due to decommission of xxxx we tried to move the SAMS functionalities to yyyy LPAR . All the scripts DTOC , POOL SCAN all worked good excepted VOLUME addition. Then we tried to backout the change and moved all these functions back to xxxx, but still VOLUME add is not working where it was previously running good on LPAR xxxx. 

When a volume was added for one storage group, it took up UCB , and SPARE VOLSER , and then SAMS tried to DISNEW the volume, and then tried to OFFLINE this across all LPARS.  It did the OFFLINE, but the volume is not initialized and failed, and then ENABLED the SPARE VOLSER.

 The following error message was generated: 

VANSMSAC FDRABR.VDV976C                                                         
VANSMSAC FILTSTAT='SG NAME' =     <name1>          AND CUA1     = 0000                      
EWSLSMSA % ALLOCATED=085                                                        
EWSLSMSA VOLUME CNT =002984                                                     
EWSLSMSA FREE BYTES =3,885,363,840,744                                          
EWSLSMSA TOTAL BYTES=25,658,589,080,160                                         
EWSLSMSA LARGEST EXT=       3,225,598,200                                       
EWSLSMSA ADDVOL   COMPLETED SUCCESSFULLY                                        
EWSLSMSA COULD NOT ENQ SMSSPARE TABLE. TRY LATER: RC=04                         
VANSMSAC RCODE FROM GENCONSW =8                                                 
GENCONSL ESP507E Missing or invalid agent name in prefix: <prefix name>, received 
GENCONSL VARY SMS,VOLUME(vvvvvv,nnnn),ENABLE....................................
GENCONSL IEF196I AUTOCMNX1I CMNEMNX1-I CICSMP2J (PCIxxxxx) No action required.  
VANSMSAD RCODE FROM GENCONSW =8

Environment

Vantage

Resolution

Vantage is waiting for console messages confirming the offline requests.
Vantage expects the confirming message IEE421I RO *ALL which never comes, so Vantage believes OFFLINE is failing, so the whole adding of the volume is failing and the subsequent INIT is intentionally not requested.
Vantage is not aware of the change done by OPS. Then, a next spare volume is selected and it fails again.
Using SMSROUTE (xxxx) Vantage will issue ROUTE xxxx instead of the ROUTE *ALL and also will expect IEE421I RO xxxx confirming messages.
So, it should start working after this change of the Vantage system parameter. It is probably not necessary to change anything in OPS, assumed ROUTE xxxx is accepted by OPS and will not be modified.
When changing to xxxx it is working fine.