IBM eServer iSeries Manual page 67

Access for windows operations console
Hide thumbs Also See for eServer iSeries:
Table of Contents

Advertisement

v Since there can be only one Operations Console directly attached device, the takeover function cannot
|
|
be used. However, any 5250 emulation-based device can be used to recover a loss of the console by
changing the console mode. This may require a reallocation of hardware to support the new console
|
mode.
|
|
v The DST user ID used to sign on at an eligible device must also have the user privilege of Service Tool
|
Security.
v Only devices with the same attributes (for example: 24 by 80 or 27 by 132) can perform a take over. For
|
example, if device LAN1 is running in 24 by 80 mode and LAN2 is running in 27 by 132 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 Takeover is not supported in a D-mode IPL. Two devices cannot be connected, with data, at the same
|
|
time during a D-mode IPL. See Recovery details for alternatives to take over.
|
v Console mode 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
|
mode is set to LAN, for example, a local console directly attached workstation 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.
|
|
Recovery details: These are some facts you should understand concerning the console recovery action.
v The recovery of the console using a device with the same console connectivity is directly tied to the
|
take over option. If you do not want take over capability but do want recovery from loss of the
|
|
console, you must still enable the take over option.
v Console recovery utilizes the take over function. Recovery can be from the same device or another
|
device of the same connectivity. For example, if you are using Operations Console LAN and have
|
|
multiple PCs set up to be the console and the existing console fails you can use the take over function
from the same PC, after correcting the reason for the failure, or from another PC. Regardless of what
|
the former console was doing, the new console will be in the same job, at the same step, as the original
|
|
console would have been. The job continues even though the console was not operational. Using a
directly attached console to recover a loss of a LAN-connected console doesn't fit this scenario
|
v The recoverability of the console using a different console connectivity provides additional options for
|
|
the user. If you have a backup console plan that involves the need for a change in the console mode,
consider the following:
|
– It is recommended that for ease of adapting recovery that you place all console supporting adapters
|
for use by the same IOP. This reduces the number of steps necessary to accomplish a recovery.
|
|
– The console mode change can be immediate depending on the method used to make the change.
Examples would be:
|
- Using DST or SST to change the console mode would allow the console to change only at the next
|
|
IPL. Following this action with a force DST (function 21) using the control panel or LPAR menu
|
may not always work either.
- Changing tags in the LPAR environment will also require an IPL to cause a change of the console.
|
- However, using the console service functions (65+21), forces the system to do this search and
|
|
activates the appropriate hardware and tasks and is immediate. See Using the console service
functions (65 + 21).
|
– Supporting hardware for each console type you want to use for recovery must be available at the
|
time of recovery. For example, if you want a local console directly attached to be able to recover a
|
|
local console on a network, both adapter cards must be located in their respective locations or be
properly tagged for logical partitions. For this to be completed the user would also have to change
|
|
the console mode, either using an available menu or using the console service functions (65+21).
61
Operations Console

Advertisement

Table of Contents
loading

Table of Contents