Only use the console service functions (65+21) when you encounter an unexpected console failure and there are no other workstations available for recovery or resolution.
The console service functions (65+21) apply to systems with or without a Hardware Management Console (HMC), as well as a control panel. Any hardware allocations or configurations must be completed before using the console service functions (65+21). For example, if you tagged an IOA as the console device, you must tag another IOA to change the type of console or connectivity.
You can access the console service functions (65+21) from the control panel, Operations Console remote control panel, or the HMC. All of these functions, except dumping Operations Console-related flight recorders to vlogs during a D-mode initial program load (IPL), are supported using the OPSCONSOLE native macro.
You can use the console service functions (65+21) to change the console value in IBM® i5/OS from its current value to another value.
Example: You ordered a server with a local console on a network (LAN) but you have problems getting it to work. Because you received the Operations Console cable for a local console that is directly attached, you want to change the console value from Operations Console (LAN) to Operations Console (Direct).
Native macro: OPSCONSOLE CNSLTYPE x (1, 2, 3, or 4)
You can disassociate the current Operations Console LAN adapter. You might use this option to overcome a mistake in the configuration. Depending on your intent to clear the LAN adapter configuration, you might also want to stop and restart the LAN adapter.
Example: You did not see a keying error and you entered in the IP address of another device. At connection time, the client configured the server's LAN adapter for Operations Console, but Operations Console failed to connect because the other device was active. This option clears the server's network data for Operations Console and allows you to delete the client configuration and start over, allowing BOOTP to work. For more information about BOOTP, see Operations Console networking.
Example: You do not want to restart the server. To save time, you only want to stop and restart the LAN adapter. In this situation, clear, deactivate, and then activate the LAN adapter.
Example: You need to reset the network data on the server but do not want to restart the server. To save time, you only want to stop and restart the LAN adapter. In this situation, clear, deactivate, and then activate the LAN adapter by doing a 65, 21, 21.
Native macro: OPSCONSOLE CNFGLAN -clear
You can reset the Operations Console LAN adapter.
Example: A network issue caused the server to enter a bad state and Operations Console is not activating. Deactivating and then activating the Operations Console LAN adapter forces the LAN adapter to deactivate and then start again. This action solves the problem provided that the original problem that caused the connection failure is corrected.
Example: You do not want to restart the server. To save time, you only want to stop and restart the LAN adapter. In this situation, deactivate and then activate the LAN adapter.
Native macro: OPSCONSOLE RESTART
You can capture valuable resolution information regarding an Operations Console connection failure for support personnel. This method is less evasive than performing a main storage dump, which would force the server to restart. The console service functions (65+21) gather the flight recorder logs for Operations Console. The server then creates a set of vlogs for major code 4A00 and minor code 0500. You can then send these vlogs to your authorized service provider for analysis. When possible, continue the initial program load (IPL) of the server to IBM i5/OS to guarantee that all vlogs are created even if the IPL fails. The intent is that the licensed internal code (LIC) function has started the vlog tasks prior to performing the dump of flight recorders.
Native macro: OPSCONSOLE DUMP -vlog
You can enable or disable support for the embedded Ethernet port and for the 5706/5707 adapters. New systems have both options enabled by default. These options are only used when the system is not managed by an HMC.
For the IBM System i5™ 520 models with IOPless functionality, but are not managed by a Hardware Management Console (HMC), you can install PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) to allow your system the ability to have asynchronous adapters located in multiple slots simultaneously. These PTFs also include allowing the 2793 asynchronous adapter to be located in the IOPless slot C4. After you install these PTFs, you will be able to select an individual asynchronous adapter for use with the console, Electronic Customer Support (ECS), and remote service by using either a native macro or the console service functions (65+21). The console, ECS, and remote service functions must all remain on a single asynchronous adapter. Slot C4 cannot be selected for use with the console when using the 2793, but it can be selected for use with ECS and remote service.