Managing Your Local Console On A Network; Operations Console Simplification - IBM i Series Handbook

Connecting to operations console
Hide thumbs Also See for i Series:
Table of Contents

Advertisement

a. Select the configuration name (under System i Connection). This is the name that Operations
Console uses to refer to a specific system.
b. From the Connection menu, click Disconnect. The connection status shows Disconnecting.
c. Wait for the status to show Disconnected.
2. Cable the twinaxial console to the system and power on the twinaxial console and the system.
3. Perform an initial program load (IPL) to ensure there are no errors. Then, at a later time, remove or
move any hardware you planned for. When you are satisfied with your new console delete the
current configuration if you will not be using the cabled connection as a backup console. To delete the
configuration, do the following:
a. Select the configuration name (under System i Connection).
b. From the Connection menu, click Delete.
c. Click Yes to confirm the deletion.
d. Uninstall System i Access for Windows.
4. Turn off the PC and remove any hardware and cables that are no longer needed at this time. It is
recommended that you turn off the system before removing any cables or adapters from the system.
Results
Note: If the new console fails to work in i5/OS you may need to use another workstation to manually
delete the controller and device description associated with the old console device.
Related tasks
"Changing the console from an Operations Console to a twinaxial console in a nonpartitioned or
primary partitioned system" on page 64
To change from an Operations Console to a twinaxial console, follow these steps on the system using
the existing console.
"Changing the console from an Operations Console to a twinaxial console in a logical partition" on
page 65
To change from an Operations Console to a twinaxial cable, you need to follow these steps on the
system using the existing console.

Managing your local console on a network

After you configure a local console on a network, you can manage your console by performing tasks such
as managing the service tools device ID password and access password, creating service tools device ID,
and configuring a service host name.

Operations Console simplification

|
Operations Console can automatically create service tools device IDs, manage access passwords, and
|
|
discover systems.
Operations Console automates working with service tools device IDs. The system, by default, is set to
|
|
maintain up to ten service tools device IDs of a maximum value of 49 in addition to QCONSOLE. You no
longer have to manually create a new device ID when adding a PC to connect into a system or partition.
|
Also, Operations Console takes control of the access password activity for you. The authentication
|
|
process remains the same, but when this function is active, you are not asked to enter the access
password during a connection. However, you must provide a DST user ID and password to successfully
|
connect. This function does not affect a local console that is directly attached or any other console type.
|
Autocreate service tools device IDs
|
|
By default, the i5/OS operating system sets the value of the Autocreate service tools device IDs option
to 10. This default value gives you 11 connections to be automatically managed. You have QCONSOLE as
|
|
a default ID and then 10 additional service tools device IDs. These display as QCONSOLE00,
|
QCONSOLE 01, through whatever value is set. It is recommended that you have at least one spare so
67
Operations Console

Advertisement

Table of Contents
loading

Table of Contents