How to specify START command limits
You can define a maximum number of times that TOM attempts to start a failed object. For example, you specify a value of 3 for the START command limit. When TOM detects a failed object, TOM issues the START command, trying to restart the object automatically. If TOM cannot start the object, TOM displays YES under the Excptn column heading on the views that display objects and the object’s status is set to FAILURE-REC-INIT.
If the object eventually restarts and fails again, TOM issues the START command (second attempt). If the object restarts and fails again, TOM issues the START command (third and final attempt).
If the object fails a fourth time, TOM does not attempt to restart the object and issues the IC1202W message. The object’s status is set to FAILURE-CMDCOUNT, indicating that it has exceeded the specified number of times that TOM should attempt to restart the object.
When an object has exceeded its START command limit, you can restart the object in one of the following ways:
On a view that displays objects, enter the RES (RESET) line command next to the object and select Yes for the Reset START counter to 0: option on the dialog.
It is recommended that the RESET command be used to return the object to ACTIVE status. This restores the object to TOM’s control.
On a view that displays objects, enter the STA (START) line command next to the object and select Yes for the Start with FORCE: option on the START Command dialog. Then select Yes on the Bypass command count check: option on the START Command with FORCE warning dialog.
The START command will remove control from TOM and FORCE the start of the object regardless of dependencies and calendar schedules.
- Write and schedule an EXEC that issues a TOM API function to reset the START command count (specifying the keyword STARTCMDCT). See RESET-function.
You can also define that TOM resets the object’s START command count automatically when
- An object successfully terminates
- After a prescribed number of minutes following a successful start
To define that a reset takes place after a successful object termination, select Yes in the Reset start count at termination field on the object ADD or EDIT dialog as part of the object’s definition.
To define that an object’s START command count resets at some point after a successful start, specify a number of minutes between 0 and 23:59:59 in the Reset start count after: x minutes field on the object ADD or EDIT dialog.
The MAMINIxx BBPARM member parameter RESET_COUNT affects which entries in an objects’ valid system list will have their start counts reset. RESET_COUNT=ALL will reset the count for systems in the valid system list. RESET_COUNT=LOCAL will reset the count for only the local system where the TOM PAS is running.