Scenario: Recovering the console during a D-mode IPL

This scenario describes how to recover from a network failure during a D-mode IPL when the configured console is a local console on a network (LAN).

In this example, you are installing Licensed Internal Code as part of a system recovery action and the configured console is a local console on a network (LAN). However, the device does not become active and you receive an A6005008 system reference code (SRC). The system is large and it takes a long time to get to this point and you do not want to start over. The system is not managed by a Hardware Management Console (HMC) and the correct asynchronous communications adapter is available without further configuration changes. You can use the console service functions (65+21) to change the console type value. This automatically starts the asynchronous communications adapter associated with the local console that is directly attached. If you want to use the same PC you are using for the local console on a network (LAN), you disconnect the local console on a network (LAN) and create (or use a previously created configuration) a local console directly attached connection. When the console service functions (65+21) have successfully completed, you connect the local console that is directly attached. This device becomes the console automatically and you are at the expected step. If the network failure precedes the old console in receiving the language window, the new console presents that window. If the failure happens after you started an action, the new console is either running that action or the action might be complete, in which case you see the results of that action.

If the system is managed by an HMC and you have the asynchronous communications adapter installed, you can use the Alternate procedure: Changing the console without powering off the managed system.


Send feedback | Rate this page