Table of Contents
Advertisement
Note: The following topics are valid when the Allow console to be taken over by another console is not
|
|
enabled. For information relating to console take over and recovery see Take over or recover an
Operations Console connection.
|
|
The following links will explain the more common procedures. Select the link that best describes your
scenario.
|
|
Multiple local PC consoles on a network
When a workstation is already a console and another local console on a network attempts to become
|
the console, the connection will be successful and the user will be presented with the Console
|
|
Information Status screen. This screen will inform the user which device is currently the console.
Many connections of this type can be connected but only one can be the active console.
|
|
Multiple remote consoles through dial-up support connecting to the same local console directly
attached to the server
|
|
In this environment only one remote console is allowed to connect to the local console.
Switching from one console type to another when a console is currently available
|
|
If you know in advance that you will need a different console type, the current console can be used
to make the changes necessary to use a different console on the next IPL or the next connection.
|
|
Switching from one console type to another when the current console is not operational
If you develop a problem with the current console, you may be able to use this procedure to change
|
the console mode.
|
Take over or recover an Operations Console connection
|
New for V5R3 is a special set of actions that allow an Operations Console to take control from
|
|
another console device.
Multiple local PC consoles on a network
|
|
When a workstation is already a console and another local console on a network attempts to become the
|
console, the connection will be successful and the user will be presented with the Console Information
Status screen. This screen will inform the user which device is currently the console. Many connections of
|
|
this type can be connected but only one can be the active console. Also, leaving the newly connected PC
|
in this state will not allow the console activities to be automatically transferred to this PC. In this case
you have two choices.
|
v Disconnect the connection using the Operations Console window. To disconnect the connection, follow
|
|
these steps:
1. Select the connection name you want to disconnect.
|
2. Click Connection —> Disconnect.
|
v Disconnect the emulator session. To disconnect the emulator, follow these steps:
|
|
1. In the emulator window, click Communication.
|
2. Select Disconnect.
|
If no device is acting as the console the next time a connection is made, either through Operations
Console or the emulator, this PC will become the console. It is up to the users to determine whether or
|
not this method is the correct way to manage console activities.
|
Multiple remote consoles through dial-up support connecting to the same local
|
console directly attached to the server
|
|
In this environment only one remote console is allowed to connect to the local console. The users will
|
have to work out an arrangement in which another remote console can access the local console. If this is
needed on a regular basis it might be as easy as assigning a time period in which each remote console
|
|
would access the local console. When the time is up for the first remote, it would release control and
58
iSeries: iSeries Access for Windows Operations Console
Advertisement
Table of Contents
