Abnormal terminations

Abnormal terminations can occur for any object when the object terminates before TOM has instructed the object to stop.

When you define an abnormal termination event (optional) for the object as part of its definition and the event occurs, TOM is notified that an abnormal termination has occurred.

When an abnormal termination takes place, TOM takes the following actions:

Related topic

How-TOM-recovers-failed-objects

  • Increments the abend counter for the object
  • Sets the object’s status to FAILURE-ABENDED

  • Issues the IC1704I message:

     IC1704I Abend event detected for object_name
  • Executes any defined recovery commands

If you want TOM to restart an abended object automatically, with no other actions taking place, DO NOT specify an Abend Validation Event.  TOM's auto-detection processing will determine that an object has ended but should be active and will restart it.  If, on the other hand, you want to do something other than simply restart the object, then DO specify an Abend Validation Event, and specify what action is to be taken in the Recovery Command(s).

The object’s status is set to FAILURE-ABENDED unless the object has a weak relationship to its dependents (children) and then the object’s status is set to ACTIVE-ABENDED.

However, if you define that the object should be started on an alternate system when its status is set to FAILURE-ABENDED, TOM attempts to start the object on the next system in the object’s Valid System List (VSL) definition until the object restarts or the startup process has failed on each system in the VSL.

If all attempts have been made, and the object cannot start or stop successfully, on the views that display objects, TOM displays YES under the Excptn column heading.

When this situation occurs, you must do the following:

  • Determine why the object has not started.
  • Make adjustments to your automation or adjust the object’s definition.
  • Allow TOM try to start the object after a reset request schedules evaluation.

You might need to issue a status-reset by issuing the RESET command with the RESETOPT=(RUNSTAT) parameter.

If the object’s status is set to FAILURE-ABENDED, all objects that depend on the abnormally ended object will be stopped by TOM if there is a strong dependency relationship between the failed object and its dependents.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*