By enabling the GSM Extension, you can use TOM to manage items, resources, devices, interfaces, and so on that are not addressed by the other Extensions.
A GSM object can have schedules, dependencies, servers, and so on just like any other object.
WarningNote
It is recommended that start and stop validation events are defined for a GSM object to inform TOM of changes in the state of the object’s related resource or interface, so that the object can be properly recovered or stopped according to its defined policies. The Active Check Program attribute can be used to inform TOM of its state. It does not have to be a program; an MVS command and the expected response can be specified as the Active Check Program command to indicate that the object’s item/resource state is up/active or down/inactive.
InformationExample
An object for CICSA region cannot be started unless VTAM LU CICSAPL is varied active.
Define GSM object CICSAPL with the following attributes:
- Short name = CICSAPL
- Start validation event message id/text = “IST093I &@SHORTNAME ACTIVE”
- Stop validation event message id/text = “IST105I &@SHORTNAME NODE NOW INACTIVE”
- Active Check Program command type MVS with text “DISPLAY NET,ID=&@SHORTNAME\,SCOPE=ALL” and a 0 seconds interval (0 seconds interval will execute the Active Check Program command on demand only, not on intervals; the start and stop validation events will indicate to TOM/GSM when the VTAM LU is active/inactive).
- Active Check Program command response line number = 3
- Active Check Program command response text = “IST486I STATUS= ACT/S, DESIRED STATE= ACTIV”
- Start command type MVS with text “VARY NET,ACT,ID=&@SHORTNAME”
- Stop command type MVS with text “VARY NET,INACT,ID=&@SHORTNAME”
Define STM object CICSA with a dependency on object GSM CICSAPL with ACTIVE status.
When TOM starts object CICSAPL and its status is ACTIVE, TOM will then start object CICSA.
