Connecting to REST After ESP Master has moved to another LPAR

Products

• ESP Workload Automation

Issue/Introduction

Currently ESP on the other lpar that isn't the master, it sits in shadow mode until the  master goes down. Does the REST API task have a way to know when the master switches so that is always stays in sync with the master task?

Environment

REST

Resolution

Our REST API does not include a mechanism for connecting to another ESP master after the primary master goes down. However it is possible to use the SHADGOAL command. This allows you to stop the REST API task previously connected to the ESP master subsystem and start a new task that connects to the new ESP master subsystem (the former shadow master). Additionally you can add an event trigger to the WARM member that would trigger a maintenance ESP APPL that can contain additional logic to stop and start STC's as needed. 

Example APPL:

APPL ESPMREST                                           
                                                        
JOB ACTIVE TASK PROCESS SELFCOMPLETING                  
RUN DAILY                                               
DELAYSUB NOW PLUS 1 MINUTE                              
/*IF SYSNAME EQ 'LPAR1' THEN DO */                       
IF ACTIVE('ESPMREST') THEN DO                           
SEND 'ESPMREST IS ACTIVE WILL NOT BE STARTED' U(%USER)
EXIT                                                    
ENDDO                                                   
ELSE DO                                                 
VS 'S ESPMREST'                                         
ENDDO                                                   
ENDJOB             

                                         

Additional Information