ESP Enhancement for WOBRETRY/WOBDELAY on WOBTRIG

Products

• ESP Workload Automation

Issue/Introduction

This enhancement introduces new initialization and WOBTRIG command parameters that allow ESP to automatically retry initialization of the WOBTRIG monitor on the agent side when the monitor fails, for example after a connectivity issue with a network folder.

Environment

Release 12.0

Resolution

The following are newly introduced parameters.
RETRYCOUNT
RETRYDELAY

NOTE:
You can use the initialization parameters WOBRETRY and WOBDELAY to have default restart behavior for WOBTRIG without the need to specify RETRYCOUNT and RETRYDELAY in each event.

EXAMPLE:

EVENT ID(ESP.WOBTRIG3)  SYSTEM(ESPx)  REPLACE            
INVOKE 'ESP.TESTPROC(ALERTWOB)'                       
WOBTRIG FILE_TRIGGER Agent(ESPAGENT) -                           
        FileName(<path>\<filename>') CREATE -
        RetryCount(3) RetryDelay(3) State(Monitored) -        
        Status('Monitored for CREATE')                        
ENDDEF 

 NOTE:
   RetryCount(3) Specifies a number of automatic retry attempts as 3.
   RetryDelay(3) Specifies a delay of 3 minutes before a retry attempt.

Following messages can show in ESP auditlog if the WOBTRIG fails:

ESP6916I SensMGR: Processing WOBMSG STATE FAILED Event(ESP.WOBTR3.XXXXXXXXXXXXXX) Status(Scan Failed) Agent(ESPAGENT) 
ESP6994I SensMGR: Automatic retry for event ESP.WOBTR3 attempt 1 of 3 scheduled in 1 minute
ESP6916I SensMGR: Processing WOBMSG STATE FAILED Event(ESP.WOBTR3.XXXXXXXXXXXXXX) Status(Scan Failed) Agent(ESPAGENT)
ESP6994I SensMGR: Automatic retry for event ESP.WOBTR3 attempt 2 of 3 scheduled in 1 minute
ESP6916I SensMGR: Processing WOBMSG STATE FAILED Event(ESP.WOBTR3.XXXXXXXXXXXXXX) Status(Scan Failed) Agent(ESPAGENT)
ESP6994I SensMGR: Automatic retry for event ESP.WOBTR3 attempt 3 of 3 scheduled in 1 minute
ESP6916I SensMGR: Processing WOBMSG STATE FAILED Event(ESP.WOBTR3.XXXXXXXXXXXXXX) Status(Scan Failed) Agent(ESPAGENT)
ESP6995E SensMGR: Automatic retry for event ESP.WOBTR3 failed. Retry limit reached.

If need them to show up on MVS console (or ESP JESMSGLG), then configure ESP SELECT statements which is loaded thru LOADESPL in ESPPARM.

After all the attempts, following shows in ESP JESMSGLG:
ESP6907E Definition of event ESP.WOBTR3 failed. Scan Failed 
ESP6970E The <path> does not exist or not a directory       

 

 

 

Additional Information

Doc link for WOBDELAY

Doc link for WOBRETRY

SELECT: Select Audit Log Messages to Copy to the JES Job Log