Examples: Using IPL levels
This section provides examples of performing a TOM IPL and shutdown by using IPL levels.
TOM IPL with IPL levels active
This example illustrates how to perform an IPL by using IPL levels and the messages issues during this process.
You specify IPLORDER=(MINIMAL,DATABASE,ONLINE) in the MAMINIxx BBPARM member. The Definition Base to be activated contains the following objects associated with the following IPL Levels:
| Object | IPL level | Description |
| JES2 | MINIMAL | JES2 task |
| JES2_CHILD | MINIMAL | Dependency on JES2 |
| TCPIP | MINIMAL | TCP/IP task |
| TSO | MINIMAL | TSO task |
| WAIT_START | MINIMAL | Object defined as Restart Only, so TOM does not initially start it |
| CICS1 | DATABASE | CICS subsystem |
| DB2MSTR | DATABASE | Db2 master task |
| IMS1 | DATABASE | IMS subsystem |
| FILESRVR | ONLINE | File Server task |
| MSGGATE | ONLINE | Message Gateway task |
| PAYROLL | ONLINE | Payroll system task |
| ALWAYS_DOWN | No associated IPL level | Defined with a schedule so that TOM will never start it |
| MESSAGES | No associated IPL level | Messages task |
| TRANSIENT | No associated IPL level | Runs for 5 seconds then ends |
When you start TOM PAS with IPLL=Y, TOM issues the following messages:
MAMOD2260I IPL Level processing is active
MAMOD2293I There are 3 levels defined in IPLORDER
TOM then starts the objects that are associated with the first defined IPL level, MINIMAL, and issues the following messages:
MAMOD2211I There are 5 objects defined with IPLLEVEL MINIMAL for system SJSG
MAMOD2263I IPLLEVEL MINIMAL START timeout is 00:00:25 (hh:mm:ss)
MAMOD2290I 3 objects are eligible for Start at IPLLEVEL MINIMAL
MAMOD2213I Start initiated for 3 eligible objects with IPLLEVEL MINIMAL
These messages have the following explanations:
| Message | Explanation |
| MAMOD2211I | Five objects are associated with the MINIMAL IPL level for the local system, SJSG. |
| MAMOD2263I | The START TIMEOUT value is 25 seconds. Because you didn't specify a timeout start time in the IPLORDER= parameter, TOM calculates the time as the number of objects associated with the MINIMAL IPL level on the local system multiplied by five seconds (5 x 5 = 25). |
| MAMOD2290I | Only three (not five) objects are eligible to start. TOM doesn't start WAIT_START because it is defined as Restart Only. The dependency for JES2_CHILD is not yet satisfied because JES2 is not yet active. |
When the three objects start and become active, TOM continues to analyze the objects for the MINIMAL level and issues following messages:
MAMOD2290I 4 objects are eligible for Start at IPLLEVEL MINIMAL
MAMOD2213I Start initiated for 1 eligible objects with IPLLEVEL MINIMAL
These messages have the following explanations:
| Message | Explanation |
| MAMOD2290I | Only four objects are eligible to start: the three objects in the previous MAMOD2290I message in the previous evaluation cycle, and the JES2_CHILD object, which can now start because the dependency is now satisfied. |
| MAMOD2213I | One object, JES2_CHILD, started. |
Because TOM didn't start WAIT_START, TOM issues the following messages if that object does not become active before the timeout occurs:
MAMOD2219W IPLLEVEL MINIMAL START did not complete within 00:00:25 (hh:mm:ss) time limit
MAMOD2291I 1 objects not status ACTIVE after start IPLLEVEL MINIMAL:
MAMOD2292I WAIT-START WAIT_START
These messages have the following explanations:
| Message | Explanation |
| MAMOD2219W | The timeout for the MINIMAL IPL level has occurred at the indicated time. |
| MAMOD2291I | This message acts as a heading for subsequent messages that list the objects that did not reach the specified status in time. |
| MAMOD2292I | This message is issued for any object that is not in the specified state at the end of the timeout period. |
If the WAIT_START object becomes active, TOM issues the following message:
MAMOD2214I START of IPLLEVEL MINIMAL has completed
This message has the following explanation:
| Message | Explanation |
| MAMOD2214I | This message indicates that the start of the IPLLEVEL is completed. |
If WAIT_START does not become active, TOM doesn't issue the MAMOD2214I message.
You then issue the START IPLLEVEL command. TOM begins processing objects associated with the next IPL level, DATABASE. TOM issues the following messages:
MAMBD4225I BAOMXD1 UI START IPLLEVEL HOST(SJSG)
OD2300I User BAOMXD1 requested START of SYSTEM
MAMOD2211I There are 3 objects defined with IPLLEVEL DATABASE for system SJSG
MAMOD2263I IPLLEVEL DATABASE START timeout is 00:00:15 (hh:mm:ss)
MAMOD2290I 3 objects are eligible for Start at IPLLEVEL DATABASE
MAMOD2213I Start initiated for 3 eligible objects with IPLLEVEL DATABASE
MAMOD2214I START of IPLLEVEL DATABASE has completed
These messages have the following explanations:
| Message | Explanation |
| MAMOD2211I | Three objects are associated with the DATABASE IPL level. |
| MAMOD2263I | The calculated timeout start value is 15 seconds. |
| MAMOD2290I | All three objects are eligible to start |
| MAMOD2213I | All three eligible objects started |
| MAMOD2214I | This message indicates that the start of the IPLLEVEL is completed. |
You again issue the START IPLLEVEL command. TOM begins processing objects associated with the next IPL level, ONLINE. TOM issues the following messages:
MAMBD4225I BAOMXD1 UI START IPLLEVEL HOST(SJSG)
OD2300I User BAOMXD1 requested START of SYSTEM
MAMOD2211I There are 3 objects defined with IPLLEVEL ONLINE for system SJSG
MAMOD2263I IPLLEVEL ONLINE START timeout is 00:00:15 (hh:mm:ss)
MAMOD2290I 3 objects are eligible for Start at IPLLEVEL ONLINE
MAMOD2213I Start initiated for 3 eligible objects with IPLLEVEL ONLINE
MAMOD2214I START of IPLLEVEL ONLINE has completed
These messages have the following explanations:
| Message | Explanation |
| MAMOD2211I | Three objects are associated with the ONLINE IPL level. |
| MAMOD2263I | The calculated timeout start value is 15 seconds. |
| MAMOD2290I | All three objects are eligible to start |
| MAMOD2213I | All three eligible objects started |
| MAMOD2214I | The processing ended before the timeout period expired. |
You again issue the START IPLLEVEL command. Because all defined IPL levels are started, TOM starts to process objects that are not associated with a defined IPL level. TOM issues the following messages:
MAMBD4225I BAOMXD1 UI START IPLLEVEL HOST(SJSG)
OD2300I User BAOMXD1 requested START of SYSTEM
MAMOD2211I There are 3 objects defined with IPLLEVEL <null> for system SJSG
MAMOD2263I IPLLEVEL <null> START timeout is 00:00:15 (hh:mm:ss)
MAMOD2290I 2 objects are eligible for Start at IPLLEVEL <null>
MAMOD2213I Start initiated for 2 eligible objects with IPLLEVEL <null>
MAMOD2219W IPLLEVEL <null> START did not complete within 00:00:15 (hh:mm:ss) time limit
MAMOD2291I 1 objects not status ACTIVE after start IPLLEVEL <null>:
MAMOD2292I STOPPED ALWAYS_DOWN
These messages have the following explanations:
| Message | Explanation |
| MAMOD2211I | Three objects that do not specify an IPL Level |
| MAMOD2263I | The calculated start timeout value is 15 seconds |
| MAMOD2290I | Only two of the objects are eligible to start. That is because the object ALWAYS_DOWN has a schedule that is not satisfied. |
| MAMOD2213I | The start of the IPL Level timed out because the ALWAYS_DOWN object cannot be started. |
| MAMOD2219W | The timeout for the <null> IPL level has occurred at the indicated time. |
| MAMOD2291I | This message acts as a heading for subsequent messages that list the objects that did not reach the specified status in time. |
| MAMOD2292I | This message is issued for any object that is not in the specified state at the end of the timeout period. |
TOM shutdown with IPL Levels Active
This example illustrates how to shut down TOM by using IPL levels and the messages issued during this process. Assume that you have created the same IPL levels as in TOM IPL with IPL levels active.
The current IPL level is the <null> level, meaning that all objects in the Definition Base that can be started have been started. To bring the first level of objects associated with the <null> level down, issue the STOP IPLLEVEL command. TOM issues the following messages:
MAMBD4225I BAOMXD1 CONS STO,IPLL
OD2300I User BAOMXD1 requested STOP of SYSTEM
MAMOD2287I Start of IPLLEVEL <null> has been canceled
MAMOD2287I Start of IPLLEVEL MINIMAL has been canceled
MAMOD2211I There are 3 objects defined with IPLLEVEL <null> for system SJSG
MAMOD2263I IPLLEVEL <null> STOP timeout is 00:00:30 (hh:mm:ss)
MAMOD2290I 3 objects are eligible for Stop at IPLLEVEL <null>
MAMOD2213I Stop initiated for 1 eligible objects with IPLLEVEL <null>
MAMOD2214I STOP of IPLLEVEL <null> has completed
These messages have the following explanations:
| Message | Explanation |
| MAMOD2287I | These two messages indicate that the START IPLLEVEL command for the <null> level and the MINIMAL level have been canceledbecause there are objects in both of those levels that did not become active within the timeout period. However, TOM still monitors the objects in these groups and if they do become active, the MAMOD2214I message will be issued indicating the start of the IPL Level is complete. |
| MAMOD2211I | Three objects associated with the <null> IPL level. |
| MAMOD2263I | The calculated stop timeout value is 30 seconds. |
| MAMOD2290I | Although three objects are associated with the <null> level, only one of them is eligible to stop. The ALWAYS_DOWN object has a schedule that prevents it from starting and the TRANSIENT object is a transient object that ran and ended and is in a COMPLETED status, so it is not active. |
| MAMOD2213I | Only one object is currently eligible to be stopped at this time. |
| MAMOD2214I | The stop of the <null> level has completed. |
The current IPL Level is now ONLINE. You now issue STOP IPLLEVEL. TOM stops all objects in the ONLINE level and issues the following messages:
MAMBD4225I BAOMXD1 UI STOP IPLLEVEL HOST(SJSG)
OD2300I User BAOMXD1 requested STOP of SYSTEM
MAMOD2211I There are 3 objects defined with IPLLEVEL ONLINE for system SJSG
MAMOD2263I IPLLEVEL ONLINE STOP timeout is 00:00:30 (hh:mm:ss)
MAMOD2290I 3 objects are eligible for Stop at IPLLEVEL ONLINE
MAMOD2213I Stop initiated for 3 eligible objects with IPLLEVEL ONLINE
MAMOD2214I STOP of IPLLEVEL ONLINE has completed
These messages have the following explanations:
| Message | Explanation |
| MAMOD2211I | Three objects are associated with the ONLINE IPL level. |
| MAMOD2263I | The calculated stop timeout value is 30 seconds.
|
| MAMOD2290I | There are three objects in the ONLINE IPL Level eligible to be stopped.
|
| MAMOD2213I | All three objects will be stopped.
|
| MAMOD2214I | The stop of the ONLINE level has completed. |
The current IPL Level is now DATABASE. You now issue STOP IPLLEVEL. TOM stops all objects associates with the DATABASE level and issues the following messages:
MAMBD4225I BAOMXD1 UI STOP IPLLEVEL HOST(SJSG)
OD2300I User BAOMXD1 requested STOP of SYSTEM
MAMOD2211I There are 3 objects defined with IPLLEVEL DATABASE for system SJSG
MAMOD2263I IPLLEVEL DATABASE STOP timeout is 00:00:30 (hh:mm:ss)
MAMOD2290I 3 objects are eligible for Stop at IPLLEVEL DATABASE
MAMOD2213I Stop initiated for 3 eligible objects with IPLLEVEL DATABASE
MAMOD2214I STOP of IPLLEVEL DATABASE has completed
These messages have the following explanations:
| Message | Explanation |
| MAMOD2211I | Three objects associated with the DATABASE IPL level. |
| MAMOD2263I | The calculated stop timeout value is 30 seconds. |
| MAMOD2290I | All three objects are eligible to stop |
| MAMOD2213I | All three objects will be stopped. |
| MAMOD2214I | The stop of the DATABASE level has completed. |
The current IPL Level is now MINIMAL, which is the lowest defined IPL level. You issue STOP IPLLEVEL. TOM issues the following messages:
MAMBD4225I BAOMXD1 CONS STO,IPLL
OD2300I User BAOMXD1 requested STOP of SYSTEM
MAMOD2286W Currently at lowest IPLLEVEL MINIMAL; SHUTSYS required
After TOM is at the lowest defined IPL level, you cannot issue the STOP IPLLEVEL command to stop the remaining objects. Instead, issue SHUTSYS. When you issue SHUTSYS, TOM issues the following messages:
MAMBD4225I BAOMXD1 SHUTSYS LOCK HOST(SJSG) SYSPLEX(BMCPLEX1) DEFBASE(IPLLEVEL-DOC)
OD2300I User BAOMXD1 requested SYSTEM SHUTLOCK of SYSTEM
OD2701I ********** Total Object Manager system shutdown initiated ***********
OD2703I 4 objects are active
MAMOD2264I Current active IPL Level is MINIMAL
MAMOD2265I IPL LEVEL SHUTDOWN timeout is 00:00:50 (hh:mm:ss)
IC1003I TOM Shutdown Processing Complete
These messages have the following explanations:
| Message | Explanation |
| OD2703I | Four active objects are associated with the MINIMAL IPL level. |
| MAMOD2264I | The calculated shutdown timeout value is 50 seconds. |
| MAMOD2265I | TOM successfully completes shutdown processing. |
You must now terminate TOM. Any time before issuing SHUTSYS, you can issue START IPLLEVEL commands to have TOM start objects in the current IPL level backup.