IBM System i Manual page 73

current console. The field Take over the console will show NO since it is not of the correct type (the
|
| console type is set to LAN). At LAN2, a user with the user privilege of take over console signs on. This
user will now be presented the same Console Information Status screen but the Take over the console
|
field will show a YES indicating that take over is possible. At LAN3, a user without the take over console
|
| privilege signs on. The Take over the console field will show as NO since the user does not have the
correct authority for take over.
|
At this point only one device has met all the conditions for a console take over. At the bottom of the
screen is F10 = Take over console connection. Pressing F10 will present the user with the Take over
Console Connection From Another User screen. This is a confirmation screen that gives the user a last
chance to cancel the take over. Selecting 1 and pressing Enter at this point will cause the take over to
occur. Almost immediately, LAN1 will get the special DST signon screen and LAN2, the device that
initiated the take over, will have the exact same screen LAN1 had when the transfer took place. The job,
if something was running, does not even know this action took place. In fact the original console could
have been installing Licensed Internal Code or i5/OS or even running a complete system save in
restricted state and the server would not know it. You could even disconnect the console connection and
come back later, reconnect, and you will get the current job's screen data and the job would never miss a
beat. If a large amount of screen data was sent by the job and couldn't be delivered the data will be
stored until later. When a console reconnects, by an authorized user and device, the user may see fast
screen refreshes until all the stored data has been delivered. Actually, doing a disconnect and a reconnect
is considered a recovery (not a take over).
Scenario: Recovery of a console requiring a new console type setting:
Sometimes you might have to change the console type to recover from a console error. An example of
|
| this might be the loss of your network during normal operations.
The console type could be changed using one of the following methods:
|
v DST or SST menus (delayed)
v Native macros (delayed)
v Console Service Functions (65+21) (Immediate)
| Only the console service functions (65+21) method will automatically take down the old connection and
activate all the resources for the new choice. The other methods might require manual steps to activate
|
the appropriate resources for the new console. These changes also require that the associated resources be
|
| available in a state where they can be used. For example, assume that you are using Operations Console
LAN and the network fails, that the console was in use by your logical partition, and that you do not
|
have an asynchronous communications card on the IOP tagged for the console. You have to either move
|
| a card or change the IOP tagging to allow a directly attached console to work. If the change is not
required immediately, you can also wait for the change to take effect during the next IPL, in which case a
|
newly tagged IOP allows the directly attached console to connect. In this example, however, we are
|
| attempting to change the console's connectivity and use another device right now. The recommended
method for immediate change is the console service functions (65+21) method. After this has been
|
| successfully performed, the user must sign on again. Because this scenario is from LAN to the directly
| attached console, the new console cannot get the special sign-on window or the Console Information
Status window. It is the only valid console after the console type change. When the network problem is
|
| fixed, the LAN-connected devices go directly to the Console Information Status window and cannot take
control as the console without changing the console type back to LAN. Takeover is not available when a
|
device is directly connected as the console because only one connection of this type is allowed by the
|
| system.
Another consideration for choosing the method to change the console mode will be the availability of
another workstation. If you are installing using the console then the only method available to you is the
console service functions (65+21).
65
Operations Console