You might want to consider a backup console plan that involves the need for a change in the console type.
The recoverability of the console using a different console connectivity provides you with additional options. Use the following information if you have a backup console plan that involves the need for a change in the console type.
If you change the console by using the console service functions (65+21), then the change takes effect immediately.
Supporting hardware for each console type that you want to use for recovery must be available (not in use) at the time of recovery. For example, if you want a local console that is directly attached to be able to recover a local console on a network (LAN) device, both adapters must be located in their respective locations or be correctly tagged. For the console change to be completed, you must change the console type value, either by using an available menu or by using the console service functions (65+21).
To accomplish a recovery by using a different console type, you must satisfy the hardware requirements for the new console before attempting the takeover. This means that either the supporting hardware must already be available (not in use), including any logical partition tagging, or you must move supporting hardware, physically or logically, before attempting the recovery. Then, you must use one of the methods to change the console type value to the desired setting. You can use an existing workstation and SST, if available, the native macro, or the console service functions (65+21).
If you change the console tag during a D-mode initial program load (IPL), typically by using the console service functions (65+21), you are able to connect another device without performing another IPL as long as the new required resources are available. For example, if the input/output adapter to be switched to is not located on the same bus, then the bus on the target resource might not be able to perform an IPL at this time.