Operations Console migration

If you are upgrading to V5R4 and you want to change to or from Operations Console, upgrade the system before migrating Operations Console.

Upgrading the system prevents any conflict between the existing console and the new console. For instructions on upgrading i5/OS^®, see Changing consoles, interfaces, and terminals.

Prerequisite information for Operations Console users upgrading to, or installing, V5R4

You must comply with the following items before upgrading or installing your software (i5/OS, Licensed Internal Code) to V5R4:

For all upgrades and installations, you need to establish a connection between the server and the Operations Console PC using the service tools user ID of 11111111 (eight 1's). This keeps the expired user IDs from preventing a successful re-authentication of the client connection to the server. When you receive the i5/OS release media, the user IDs (except 11111111) are expired. To establish a successful re-authentication of the client connection to the server, enter the service tools user ID of 11111111 (eight 1's). This is especially important for automatic installations.
Update iSeries™ Access for Windows^® to V5R4 before you upgrade the i5/OS operating system. For more information, see Installing iSeries Access for Windows.

Important: When you restart your server and a console was not previously specified, you receive two additional windows to confirm the setting of the console type. At the first window, press F10 to accept the current console type. The second window displays that a console type value did not previously exist (a zero is present for the old value) and displays the new console type value. Press Enter to exit and set the console type automatically. The next window displayed is Install the System. This condition can happen on your first manual IPL of V5R4, for example, during the A-mode IPL following the restore of Licensed Internal Code during the upgrade or installation when a console value of zero is found.