Table of Contents
Advertisement
disconnect. The next remote would then connect at its assigned time and request control. This assumes
|
|
that the local console did not have control when the first remote got control.
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 for use with a different console on the next IPL or in some cases, the next connection.
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 mode and activating
|
|
the associated hardware resource. However, if hardware used for the targeted console type will require
allocation of hardware 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 adapter and the PC. You can use either DST or SST to
|
change the console mode to a 2 for Operations Console direct. The asynchronous adapter will not be
|
|
active at this time since the console mode 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. See Activate the
|
communications line on the server for details on how to perform the activation. Once the
|
|
communications line is active you can disconnect the LAN-connected console and create a configuration
for the direct 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 direct-attached console to
|
|
enter either DST or SST and change the console mode 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 adapter manually, see Deactivate the
|
|
communications line on the server or just wait until the next IPL. The IPL will not start the asynchronous
adapter because the console mode is now set for LAN.
|
Switching from one console type to another when the current console is not
|
operational
|
If you develop a problem with the current console, depending on the type of problem, you may be able
|
|
to use one of the following methods to change the console mode:
|
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) to change the console mode. See Using the console service
|
|
functions (65 + 21) for more details.
v Use the appropriate native macro from another workstation.
|
|
Note: Any hardware allocations or configurations will have to be accomplished before connecting with
another connectivity. For example, if you are using a shared IOP in an LPAR environment you
|
can deallocate and allocate the resource from one partition to another, if your hardware supports
|
|
this method. If you planned for a backup console some or all of this work may already be done.
If you do not have a backup console in place, some tasks may require one or more IPLs to get
|
the system into a state where you can use the new console.
|
Using the same configuration example above (LAN to direct) and assuming all hardware and
|
configurations have been done, you would disconnect the existing console (LAN-connected); use the
|
|
console service functions (65+21), native macro, or SST from another workstation to set the console mode
to a 2 for directly attached consoles, then connect the local console directly attached. However, if you
|
|
used the native macro or SST from another workstation, you may also have to activate the asynchronous
|
adapter. Using the console service functions (65+21) automatically activates the adapter.
|
Note: There are several console service functions (65+21) that might be needed to recover or debug an
Operations Console problem depending on the problem, connectivity used for the current console,
|
59
Operations Console
Advertisement
Table of Contents
