Table of Contents
Advertisement
If the deactivation is successful, the Function/Data window displays D1008065. See Failure to display
D1008065 and D1008066 automatically after calling the function, if the expected reference code did not
appear in a few minutes.
Using the console service functions (65 + 21)
|
|
When an unexpected console failure is encountered there may be no other workstations available for
recovery or debug. This function-set should be used only in this circumstance. Improper use may result
|
in the inability to use an intended console. Any hardware allocations or configurations will have to be
|
|
accomplished before using the console service functions (65+21). 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.
The console service functions (65+21) are standard control panel functions. They can be entered at the
|
|
physical control panel, any of the remote control panel connectivities providing a graphical user interface
in Operations Console or using the LPAR menus on a primary partition. Since the first function is a 65,
|
which is a deactivate of the communications line used by the local console directly attached, you may see
|
|
the status of a connection using a serial cable go to Connecting console.
Important: In order to use these functions, the server must be far enough through the IPL for the code to
|
|
run properly. If a console device is available, perform these functions after the first screen is displayed. If
a console device is not available, then perform these functions only after a failing System Reference Code
|
(SRC) has been displayed. This is usually a A6005008 or B6005008.
|
The following functions are available using the console service functions (65+21):
|
v Change the console mode value
|
You can use the console service functions (65+21) to change the console mode from its current value to
|
|
another. For example, you ordered your server with Operations Console LAN but you are having
trouble getting it to work. Since you should have received the console cable for a direct attached
|
console you would like to change the value from a 3 (LAN) to a 2 (direct).
|
|
v Clear the resource and configuration for the LAN adapter used by Operations Console
|
This option allows you to disassociate the current LAN adapter used for Operations Console. You
might use this option to overcome a mistake in the configuration. For example, you didn't see a keying
|
|
error and you entered in another device's IP address. At connect time the client configured the server's
|
LAN adapter for use by the console but the console fails to connect because the other device is active.
This option would clear the server's network data for the console and allow you to delete the client's
|
|
configuration and start over, allowing BOOTP to work again. See Prepare for your network
environment for more information about BOOTP.
|
Depending on your intent to clear the LAN adapter configuration you might also want to stop and
|
restart the LAN adapter. The example here would benefit from following the clear function with a
|
|
deactivate and activate to save time from having to do an IPL.
v Deactivate followed by an activate of the LAN adapter used by Operations Console
|
This option will allow you to reset the LAN adapter used by Operations Console in the event some
|
|
network issue caused the server to get into a bad state and the console won't become active. This will
|
force the LAN adapter to deactivate, and then start back up again. This may clear up the problem
providing the original problem that caused the connection failure has been corrected.
|
This option may be used in place of an IPL for some circumstances, such as after a clear of the LAN
|
|
adapter configuration.
v Dump Operations Console-related flight recorders to vlogs
|
This option will allow you to capture valuable debug information regarding a console connection
|
failure for support personnel. This method is less invasive than performing a main storage dump
|
|
which would force an IPL. By using the console service functions (65+21) an attempt is made to gather
all the flight recorder logs from the many parts of the code used by Operations Console. A set of vlogs
|
|
is created for major code 4A00 and minor code 0500. These vlogs can then be sent to your service
|
provider for analysis.
89
Operations Console
Advertisement
Table of Contents
