Can CA Allocate and Rubin ACC/SRS or StopX37 co-exist

book

Article ID: 142030

calendar_today

Updated On:

Products

CA Allocate DASD Space and Placement

Issue/Introduction

The customer is converting from Rubin ACC/SRS to CA Allocate and for some reason the VAMENVIR EOV is not passed to the software on the lpar, where both, CA Allocate and Rubin software, are active.

 

Environment

Release : 12.5

Component : CA Allocate DASD Space and Placement

Resolution

After StopX37 is started, before Allocate can be restarted, an IPL must be done to clear the StopX37 hooks out of the system.
Rubin ACC/SRS presents the same problem and an IPL must be done to clear the Rubin software hooks out of the system.

The customer confirms that when running VAM without Rubin (DIF) the EOV is handled correctly:
Rubin software (DIF) stopped
VAM started with message -
 VAM5301 EOV LOGIC ENABLED
Test job ran – EOV logic correctly ran showing messages -
 V370040 END OF VOLUME RECOVERY OPERATION STARTING FO
 V370040 ZG519411,STEP2,SYSUT2,ZG5194.TEST.DATASET.G0
 V370040 CURRENTLY ON EXTENT # 16 ON VOLUME SKS235  
VAM stopped
Test job ran again => B37 error