How to start TOM

TOM is started when the MVS START command is issued either by an operator or by automation (such as a BMC AMI Ops Automation Rule or EXEC). After TOM starts, it starts all of the objects in the active Definition Base which are eligible to be started.

where :

OMODE parameter and TOM startup

You can specify a command label, BMC AMI Ops Automation Shared pool variable, or a z/OS system symbol that contains a start command label with the OMODE parameter that TOM resolves during startup. The command label must match a value that you defined with the OMODE parameter in BBPARM member MAMINIxx.

If the command label does not match a value defined in the MAMINIxx member. the TOM PAS will not complete startup and will terminate after issuing the following message:

When you specify a command label with the OMODE parameter, TOM issues the following message to its job log and logger:

If you do not specify a command label with the OMODE parameter, TOM starts objects using their default commands.

Only the object's start command is considered for the OMODE parameter value. So if an object has a start command with a label that matches the OMODE parameter value, then it will be used and any of the other start-sequence commands with a matching label will also be used (as well as the non-labeled start-sequence commands). Start-sequence commands include pre-start, start, retry-start, and post-start commands. Therefore, if a pre-start command has an OMODE label but the start command does not, TOM uses the default commands to start objects.

TOM resolves and uses the OMODE value only when the TOM PAS starts during an IPL. Therefore, if TOM is stopped and re-started for a situation other than an IPL and the OMODE parameter is specified, TOM ignores the OMODE value during startup. If you activate a different object Definition Base after TOM has started, TOM uses the existing OMODE values to start objects. To override this default behavior, use the RESET DEFBASE RESETOPT=(OMODE) command to reset the objects' operating mode.

IPLL | IPLO parameter and TOM startup

Use the IPLL or IPLO parameter to specify whether TOM processes the values specified with BBPARM member MAMINIxx IPLORDER parameter and IPLLEVEL object attributes during an IPL. The value of the IPLLEVEL attribute for objects in the active Definition Base must match one of the values that you specified with the IPLORDER parameter.

If an object has a non-null IPLLEVEL attribute value that is not listed in the IPLORDER parameter value, the following warning message is issued and TOM treats the object as though it has a null (highest or last level) IPLLEVEL value.

MAMOD2210W IPLLEVEL <level> not specified in IPLORDER for <objName>

The following list describes the valid settings for the IPLL or IPLO parameter:

• IPLL | IPLO=N ignores all object IPLLEVEL attribute values and the IPLORDER parameter (if specified) and attempts to start all objects in the active Definition Base. This is the default setting.

• IPLL | IPLO=Y specifies that TOM processes the values specified with the IPLORDER parameter and starts the objects in the first IPL level.

  To start each subsequent level of objects when you are ready, issue the START IPLLEVEL command for each level. Issue STOP IPLLEVEL to stop the current level of objects.

  When you specify IPLL | IPLO=Y, you must also specify a value for the IPLORDER parameter for this feature to take effect. For more information about how to specify values for the IPLORDER parameter, see the comments in BBPARM member MAMINIxx.

EVAL parameter and TOM startup

Use the EVAL parameter to specify whether TOM is going to run object evaluation. Starting TOM with EVAL=SUSPEND will result in TOM starting without starting or stopping any objects.

Without object evaluation cycles, object and set statuses and states might not be correct and TOM might not automatically start or stop objects. You can issue operator commands but some may produce unexpected results.

There are two values that you can use with the EVAL parameter:

• NORMAL: this is the default setting.
  Using this parameter value causes TOM to run object evaluation after initialization and whenever requested by either TOM or an operator.
• SUSPEND: this parameter value causes TOM to never run object evaluation.

You can issue the ACTIVATE EVAL command from the operator console, the TOMEXEC FUNC(ACTIVATE) EVAL request, or the TSYS view to resume normal TOM object management.

MANAGE parameter and TOM startup

The MANAGE parameter allows you to control whether you want all of the objects in the active Definition Base to be started or stopped by TOM when object evaluation has determined if an object needs to be started or stopped. Specifying MANAGE=SUSPEND instructs TOM to initialize and run an evaluation cycle without automatically starting or stopping or managing any objects.

There are two values that you can use with the MANAGE parameter:

• NORMAL: this is the default setting.
  Using this parameter value causes TOM to issue start and stop commands when object evaluation has determined that these commands need to be issued for an object.
• SUSPEND: this parameter value causes TOM to never issue commands for an object.
  MANAGE=SUSPEND will cause TOM to behave as though control mode is SUSPEND for every object in the active Definition Base.

You can use the ACTIVATE MANAGE command from the operator console, the TOMEXEC FUNC(ACTIVATE) MANAGE request, or the TSYS view to resume normal TOM object management.

Messages issued during TOM startup

If the BMC AMI Ops Automation PAS named in the AOID parameter of the BBPARM member MAMTOMxx cannot be detected for processing requests then TOM will wait during its initialization. Before waiting, TOM will issue the following message:

If BMC AMI Ops Automation stops running after TOM has initialized, any in-flight object start, stop, or bounce action terminates and TOM sets the object's status to FAILURE-AOLINK. After TOM detects that BMC AMI Ops Automationis available, TOM resets all of the objects with status of FAILURE-AOLINK.

If BMC AMI Ops Infrastructure is not found, the following message is issued:

This message indicates that the TOM PAS cannot detect the BMC AMI Ops Infrastructure CAS that is specified in the TOM BBPARM member MAMTOMxx.

When the specified BMC AMI Ops Automation PAS is available, the following message is issued:

When the specified BMC AMI Ops Infrastructure CAS is available, the following message is issued:

Messages when TOM has completed startup

When TOM is fully initialized, the TOM PAS issues the message:

TOM can now access the required automation services and you can perform TOM procedures.