Using the console service functions (65+21)

The emergency console recovery functions and their uses

This function-set should be used only in circumstances where an unexpected console failure has occurred and there are no other workstations available for recovery or debugging. Improper use may result in the inability to use the 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 connectivity types 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 the deactivation 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, you should use that console to perform any console service functions, if possible. If a console device is not available, then perform these functions only after a failing System Reference Code (SRC) has been displayed. This SRC usually is an A6005008.

The following functions are available using the console service functions (65+21):

Change the console mode value (01-03)
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).
Clear the resource and configuration for the LAN adapter used by Operations Console (C3)
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 (A3) function to save time from having to do an IPL.
Deactivate followed by an activate of the LAN adapter used by Operations Console (A3)
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.
Dump Operations Console flight recorders to vlogs (DD)
Note: This option will not work if the system is IPLed in D-mode.

This option will allow you to capture valuable debug information regarding a console connection failure for support personnel. This method is less intrusive 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.

Note: When possible, perform an IPL on the system to guarantee all vlogs get created even if the IPL will fail. The intent is that LIC has started the vlog tasks prior to performing the dump of flight recorders.

The following is an overview of how this function works:

Note: If your system is not in manual mode, and the extended functions are not activated, or both, follow these steps:

First, if your server uses a keystick, insert it in the key slot.
Place the server into manual mode by using the system's control panel.
Using Up and Down, select function 25. Press Enter.
Use Up to select function 26. Press Enter.

A function 65 is performed from one of the input methods. You have approximately 45 seconds to enter a function 21 for the system to pair the two functions together. If not, the function 21 is a force of DST to the console. Depending on the state of the current IPL you may or may not see a change at the console, assuming the console is still present after the 65. If the 65 and 21 are entered in less than 45 seconds a System Reference Code (SRC) of A6nn500A should appear on the control panel. The value of nn is dependent upon the console type currently being used, 01 thru 03. Repeating the 65 and 21 puts the system into an edit mode in which you can make a change or cause an action to be performed. After the second 65+21 pair is entered, the control panel will respond with the SRC of A6nn500B to indicate you are in edit mode. Each repeated 65+21 within edit mode will increment nn of the SRC until you reach the value representing what action you intend to perform. At this time you enter just a single 21 which will cause the selected function to be performed. The SRC should then become A6nn500C to indicate the function was successfully submitted. If at any time you exceed 45 seconds between the 65 and 21 or between succeeding 21s, SRC A6nn500D may be presented indicating a timeout condition and the system is no longer in edit mode. If you were intending to make a change you will need to restart the operations. This SRC will be reset in approximately 3 minutes. You can cancel out of edit mode by doing a function 66. The function 66 does not have to complete successfully.

The following codes will allow you to track your progress:

A6nn 500x

Where nn means:

00 = No console defined
01 = Twinax console
02 = Direct attached Operations Console
03 = LAN Operations Console
C3 = Clear LAN configuration
A3 = Deactivate followed by an activate of the LAN Operations Console adapter
DD = Dump all console related flight recorder into a set of vlogs

Note:

Selecting 02 will automatically activate the asynchronous communications adapter used for Operations Console direct attached.
Selecting 03 may also require a function A3 to activate the LAN adapter in rare cases. Also, if a LAN connected console is connected, the emulator may go to a Disconnected state. If so, you can start it again by clicking Communication and selecting Connect.

Where x means:

A6nn 500A: You are displaying the current console mode setting.
A6nn 500B: You did a second 65+21 pair so you are in edit mode.
A6nn 500C: You executed a second 21 to cause an action, such as setting the console to another value.
A6nn 500D: You waited too long after entering edit mode to cause an action so you will have to enter edit mode again if you intended to make a change. A 21 at this time will force the console to DST, not cause an action.

If you do not want to make a change after entering edit mode you can wait 3 minutes and this completion code should show up indicating a change is no longer pending or you do a function 66 to cancel any pending changes and exit.

Note: You have 45 seconds between a 65 and the 21 to start display mode or edit mode changes. If the time between these codes exceeds this limit the 21 will become a force DST console request.

An example of a console change would be:

The console type is 01 (twinaxial) and you want to use LAN (03).

65 - 21 = A601 500A  You are in display mode and the console mode is 01
65 - 21 = A602 500B  You entered edit mode and incremented the counter
65 - 21 = A603 500B  You incremented the counter again
       21 = A603 500C  You invoked the action (set the console mode to 03)

If the LAN adapter already had a valid configuration, for example you previously configured the LAN adapter for use with the service tool server, then you would be ready to create a local console on a network configuration on the client, if one didn't already exist. You could then power off the twinaxial device and connect the Operations Console LAN configuration.

Note: To reset the console without changing the console mode value you can do a 65 - 21 - 21. The server should respond with A6nn500A after the first 21 and a A6nn500C after the second 21. This will cause the connection to the console to be dropped during the reset process. It is recommended that this function not be used when you already have a working console. This function will not correct all errors associated with a console failure, but rather resets the hardware associated with the configured console connection.