BOUNCE function
The BOUNCE function corresponds to the BOUnce line command, which can be issued for objects from the TOBJOR view or sets from the TSETO view.
The BOUNCE function affects only objects that have an ACTIVE status. When you issue the BOUNCE function for objects with an ACTIVE status, TOM issues the stop and start commands for the object. During the BOUNCE process, the object’s status is ACTIVE-BOUNCE.
If the object has dependent objects, TOM does not stop and re-start those dependent objects during the BOUNCE process. While an object has the ACTIVE-BOUNCE status, any dependent objects will remain ACTIVE during the BOUNCE process.
The following lists the different ways TOM can determine the object state during the BOUNCE process:
- You can specify a user-defined active check program (ACP) to determine the object state.
- You can rely on the default Automatic Detection function to determine if the object is active or inactive.
If an object’s definition includes more than one start or stop commands, TOM uses the default start and default stop command during the BOUNCE function.
FULLAUTO parameter
By default, the pre-start, post-start, pre-stop, and post-start commands that are defined for an object are not scheduled when the BOUNCE function is executed.
If you want to schedule these commands during the BOUNCE process, use the FULLAUTO parameter.
The following lists the actions that TOM takes during a BOUNCE process with FULLAUTO specified:
- TOM schedules the pre-stop commands, and issues the objects’ stop command.
- When the object stops, TOM schedules the post-stop commands.
- When the pre-stop and post-stop commands have completed, TOM schedules the pre-start commands.
- When the pre-start commands have completed, TOM issues the object’s start command.
- When the object has started, TOM schedules the post-start commands.
The BOUNCE process is complete.
The following table shows the command and parameters:
Command | Parameters |
|---|---|
TOMEXEC FUNCTION(BOUNCE) | OBJECT(name)|SET(name) [HOST(hostname)] [FULLAUTO] [EVENTWAIT|EV (YES | NO)] [NOTE('xxx')] [TOMID(tom ID) | TOMPLEX(tomplex name)] |
The following table describes the parameters:
Parameter | Function |
|---|---|
OBJECT | Specify the object name to be bounced (mutually exclusive with use of SET parameter). For information about specifying the object name, see Object-and-set-naming-restrictions. |
SET | Specify the set name to be bounced (mutually exclusive with use of OBJECT parameter). For information about specifying the set name, see Object-and-set-naming-restrictions. |
HOST | Specify the name of a MVS system that is specified in the object definition’s valid systems list. The HOST parameter is mutually exclusive with the SET parameter. The HOST parameter is optional. If you do not specify HOST, TOM issues the function on the ACTIVE system. |
FULLAUTO | Specify to indicate that TOM will schedule all of the object's pre-start, post-start, pre-stop, and post-stop commands during the BOUNCE process. When this keyword is omitted, the stop and start occurs without scheduling these commands. |
EVENTWAIT | EV | Specify YES or NO. Specifying YES means that TOM waits for the object's stop event to occur before processing any post-stop commands, any pre-start commands and then restarting the object. Specifying NO means that TOM does not wait for the object's stop event to occur before processing any post-stop commands, any pre-start commands and then restarting the object. |
NOTE | Specify a reason for the action taken. By default this parameter is optional but it is required if you specify OPER_NOTE_REQUIRED=YES in BBPARM member MAMINIxx. If NOTE('xxx') is required but is not specified, the request will be rejected with RC147. Error message MAMOD2035E written to the log. |
TOMID | Specify the ID of the TOM PAS on which you want the command issued. |
TOMPLEX | Specify the name of the TOMPLEX where you want to issue the function. See Specifying-the-TOMID-and-TOMPLEX-parameters for usage information. |