Starting Shadow manager with PARM=QUIESCE for ESP Workload Automation

Products

• ESP Workload Automation

Issue/Introduction

Are there any potential issues associated with starting the shadow ESP in QUIESCE mode?

Will a quiesced shadow be capable of taking over when the primary fails? 

Environment

Release : 11.4 & 12.0

Component : ESP WORKLOAD AUTOMATION HIGH AVAILABILITY

Resolution

- You can start the SHADOW with PARM=QUIESCE. 

//SHADOW  EXEC PGM=CYBJS000,     
//           PARM=(SECONDARY,QUIESCE), 
......

- The quiesced SHADOW can take over and it can be resumed with the RESTART command:

When the active Master stopped:
ESPM_4396I Master quiesce shadow goal activated, ESP master ended, Member=SYSA                          
ESPM_4397W ESP master ESPM in quiesced state for 60 seconds                  
F ESPSH,SHADOW TAKEOVER                                                        
ESPM_4372I Exiting shadow mode      

The SHADOW was in quiesce mode after it took over:                                         
ESPM_1977I ESP release 11.4 status       
ESPM_1978I EVENT SCHEDULING QUIESCED     
ESPM_1979I DATA SET TRIGGERING ACTIVE    

Then after issuing RESTART command, it's resumed:
ESPM_1960I RESTARTING 

ESPM_1977I ESP release 11.4 status    
ESPM_1978I EVENT SCHEDULING ACTIVE    
ESPM_1979I DATA SET TRIGGERING ACTIVE