IPL and SHUTSYS considerations

Total Object Manager (TOM) provides several features that are useful for an initial program load (IPL) and the SHUTSYS function.

Starting objects by using IPLLEVEL

After an IPL, you can use the IPLLEVEL feature to start one or more objects in different phases or stages. TOM automatically starts the objects that have the IPLLEVEL attribute value, which matches the first value of the IPLORDER parameter in MAMINIxx. To start objects of the remaining IPLORDER values (levels or stages), you must issue the START IPLLEVEL command. Using IPLLEVEL is useful when you have various databases or other resources that you must manually check and approve before allowing full access to all subsystems and applications.

You can also stop objects by using IPLEVEL. For more information, see Controlled-starting-of-objects-during-IPL-with-IPLLEVEL.

Starting objects by using the Operating Mode parameter

You can use OMODE (Operating Mode) at IPL or when you manually start an object. If you start TOM with the OMODE=cmd-label parameter after an IPL, all objects with the start command label cmd-label are started, and that Operating Mode is saved in the Registry for that object until it is reset. You can specify object dependencies using Operating Modes so that they are started or not-started for certain modes.

For more information, see OMODE parameter and TOM startup.

Preventing an object from being started at IPL

To prevent an object from being started at IPL, administrators can specify the Lock at IPL=Yes object attribute. Operators can also accomplish this by using the LOCK function with the IPL=NO|ALL|nn parameter. For more information, see LOCK-function.

Reinstating a SUSPENDED object at IPL

You can define an object by using the Reinstate at IPL object attribute so that the object's SUSPEND control is removed at IPL, allowing TOM to start and stop it again. For more information, see How-TOM-reinstates-a-SUSPENDED-object and SUSPEND-function.

Starting objects at IPL before TOM initializes by using restart-only

You should define objects that need to be started at IPL before TOM initializes or by another automation by using the Restart Only=Yes object attribute. This object attribute tells TOM not to start the object, but to manage it after detecting that it is active in the system, and then restart it if it terminates. For more information, see Restart-only objects

Configuring TOM PAS to stop itself by using SHUTDOWN_TERMINATE=YES

You can configure the TOM product address space (PAS) to stop itself after SHUTSYS has completed by specifying the SHUTDOWN_TERMINATE=YES parameter in BBPARM member MAMINIxx.

Defining TOM to manage the entire system

When starting the TOM PAS, TOM uses the Runtime Component System (RTCS) and BMC AMI Ops Automation. TOM also uses Logger, but it writes messages by using IBM Write to operator (WTO) when the Logger is not available. You can define BMC AMI OpsA to start Logger and have TOM manage it as a restart-only object, or let TOM manage it as a normal object.

Defining TOM to manage JES2 by using SUB=MSTR

You should define BMC AMI OpsA to start with the SUB=MSTR parameter after the RTCS is available, so that TOM can manage JES2. TOM connects to JES2 after it completes initialization and disconnects from JES2 when it's terminated. For more information, see JES2-considerations.

Viewing the object status by using the MAMSTAT utility

After TOM starts the Coordinating Address Space (CAS), you can use TOM views to see the status of objects. When the CAS is not available, you can invoke the MAMSTAT utility (EXEC in BBSAMP member) from the BMC AMI OpsA Journal or TSO, to view information similar to that provided on the TOBJOR view. You can also use the TOM OBJECT SHOW console command to obtain the object's statuses. For more information, see Reporting-status-for-objects-and-sets

Resetting the z/OS system