Using System State Manager › How to Specify and Store Actions › SSM Action Processes Default Logic › How SSMRETRY Limits a Repetitive Action Sequence

How SSMRETRY Limits a Repetitive Action Sequence

The SSMRETRY request rule is a technique used to limit a repetitive action sequence from occurring, such as starting a problem resource.

The SSMRETRY request rule performs the following actions and causes these effects:

• Parameters passed to SSMRETRY specify how many start attempts should be made within a defined time period.

  For example, if a resource is started on a system by SSM as a result of DESIRED_STATE='UP', the resource starts on the system (CURRENT_STATE='STARTING') but then terminates abnormally (CURRENT_STATE='DOWN'), the SSMRETRY logic limits SSM from attempting another start of the resource and sets the current state to failed (CURRENT_STATE='FAILED').

• Parameters passed to SSMRETRY specify a maximum time that a resource should reach its initialization state. If a resource does not reach its initialization state (CURRENT_STATE='UP' as set by associating SSM rule packet), then the SSMRETRY logic will set the current state to timeout (CURRENT_STATE='TIMEOUT').

  For example, if the maximum initialization time for JES2 is set to five minutes, when SSM starts JES2, and if it goes into some internal loop (never produces $HASP492), then after five minutes the logic created by SSMRETRY will set the CURRENT_STATE = 'TIMEOUT' for JES2.

• The SSMRETRY request rule is invoked as a nested action within the DOWN_UP action process for a resource such as:

  EVRULE("SSMRETRY &SSMTABLE &JOBNAME,1,300,START UP");MVSCMD("START &JOBNAME")
  

  This START UP action process is limited to one start attempt and the resource should reach its initialization state (CURRENT_STATE = UP) within 300 seconds. These parameters can be change accordingly. The invocation of the SSMRETRY as an EVRULE action allows the code to inform SSM to either process or bypass the nested or subsequent start resource action. (start resource)

  For further details and complete implementation guidelines, see the comments within the SSMRETRY request rule.