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 mode to a 2 for Operations Console
direct. The asynchronous communications 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. 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 communications adapter manually
or just wait until the next IPL. The IPL will not start the asynchronous
communications adapter because the console mode 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 mode has been updated performing the
console service function will disconnect the current console and restart the
console type you just specified. See link to console service function documents.