Switching From One Console Type To Another When A Console Is Currently Available; Switching From One Console Type To Another When The Current Console Is Not Operational - IBM i Series Handbook

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 you to determine whether or not this
method is the correct way to manage console activities.

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, you can use the current console to
make the changes necessary for use with a different console.
If the hardware resources for the targeted console type have already been specified and configured for
use as a console, making the change may be as simple as specifying the new console type and activating
the associated hardware resource. However, if hardware used for the targeted console type will require
allocation or configuration, you will need to use the appropriate information in Change from one
console type to another.
An example would be the planned loss of the network used by your LAN-connected console. You will be
doing some infrastructure changes requiring more than a day. You also have the console cable already
installed between the server's asynchronous communications adapter and the PC. You can use either DST
or SST to change the console type to a 2 for Operations Console (direct). The asynchronous
communications adapter will not be active at this time since the console type is set for LAN so you
would have to manually start the asynchronous card with a function 66 on the control panel or remote
control panel. Once the communications line is active you can disconnect the LAN-connected console and
create a configuration for the directly attached local console, if a configuration doesn't already exist, and
start a connection. To switch back to the LAN-connected console you would only have to use the directly
attached console to enter either DST or SST and change the console type to a 3, disconnect the existing
console and restart the LAN-connected console. Since the hardware resource configuration didn't change,
there isn't a need for further changes. You could deactivate the asynchronous communications adapter
manually or just wait until the next IPL. The IPL will not start the asynchronous communications adapter
because the console type is now set for LAN.
Note: To activate the new console without an IPL, you could perform the console service function of
65+21+21. Once the console type has been updated, performing the console service function will
disconnect the current console and restart the console type you just specified.
Related tasks
"Activating the asynchronous communications line on the system" on page 39
These instructions apply only to configurations of a local console that is directly attached. To manually
activate the asynchronous communications line on the system, complete these steps:
"Deactivating the asynchronous communications line on the system" on page 39
These instructions apply only to local consoles that are directly attached. To manually deactivate the
asynchronous communications line on the system, follow these steps:
Related reference
"Changing from one console type to another" on page 52
Depending on how your console connection is set up, you can change to a different console type.
Switching from one console type to another when the current console is not
operational
If you develop a problem with the current console, you can use one of these methods to change the
console type.
v If you are using a LAN-connected PC for the console and have another PC set up to be the console,
you might be able to use the other PC for the console until the problem with the first console is fixed.
v Use SST from another workstation.
v Use the console service functions (65+21).
51
Operations Console