Takeover Details - IBM i Series Handbook

Benefits of these functions include convenience and redundancy. Console-capable devices can be placed
around a site, or multiple sites, allowing users to move around and gain control of the system from any
of these devices. Whatever the previous console's activity was, the new console is at the exact same place,
even during the process of restarting the system or installing the i5/OS operating system. When the
console option for takeover is enabled, the system also has enhanced recoverability from the loss of the
console.
Related reference
"Console planning considerations" on page 3
When you plan for Operations Console for one or more of your systems, consider these points.
"Planning considerations for your backup console" on page 5
Most system plans include a level of redundancy to allow for the event of hardware failures; however,
many people do not consider the console in their plans. To recover quickly from an unexpected loss of
your console, you need to plan for a backup console.
"Management of multiple consoles" on page 50
If you have more than one workstation that is capable of being the console to the same system or
partition, there might be more than one way of using those devices as the console, depending on your
configuration and circumstances.

Takeover details

Here is the additional information about the console takeover function.
v This function must be enabled if you want to take over the console or be protected from the loss of the
console using the recovery function.
v The option Allow console recovery and console can be taken over by another console is enabled on
the Select Console window in DST or SST.
v This function does not include support for twinaxial consoles. Only Operations Console workstations,
which use 5250 emulation, can use this function.
v Since there can be only one Operations Console directly attached device, the takeover function cannot
be used. However, any 5250 emulation-based console device can be used to recover a loss of the
console by changing the console type. This may require a reallocation of hardware to support the new
console type.
v The DST user ID used to sign on at an eligible device must also have the user privilege of take over
console, a new feature for V5R4.
v Only devices with the same attributes (for example: 24x80 or 27x132) can perform a take over. For
example, if device LAN1 is running in 24x80 mode and LAN2 is running in 27x132 mode, and LAN1 is
the console, LAN2 will see NO in the Take over the console field.
v Data on the Console Information Status screen does not change. Currently, there is no method to
automatically refresh the data. You can manually cause a refresh of all fields except the Take over the
console field by pressing Enter. The user would have to exit this screen and sign on again to see a
change to that field.
v Beginning in this release, takeover is supported in a D-mode IPL. Two devices can be connected, with
data, at the same time during a D-mode IPL.
v Console type respectability is still honored when take over is enabled. However, each console-capable
workstation will present either a DST signon or the Console Information Status window. If the console
type is set to LAN, for example, a local console directly attached, if connected, will present the Console
Information Status window without displaying the DST signon window but the Take over the console
field will show NO to indicate it cannot take over the existing console. However, it could be used for a
recovery action.
Related reference
"Recovery details" on page 42
Here is the additional information about the console recovery function.
41
Operations Console