Creating service tools device IDs on the server

This topic describes how to set up service tools device IDs on the server if you are using a local console on a network (LAN) configuration.

If you are installing a new server using Operations Console on a network (LAN) configuration, then you will need to use the default service tools device ID, QCONSOLE, during the configuration wizard.

If you already have a console or another workstation, you need to follow the instructions below to set up service tools device IDs on the server for additional local console on a network (LAN) configurations. This is accomplished by using either the dedicated service tools (DST) or the system service tools (SST). However, you must unlock the SST option before the option is usable. For additional information on SST, see Unlocking service tools device IDs in SST.

Access Dedicated Service Tools (DST) or System Service Tools (SST).
If you are using DST, select Work with DST environment, or if you are using SST, select Work with service tools user IDs and devices.
Select Service tools user IDs.
Use option 1 to create a new service tools device ID and enter the new service tools device ID name in the first blank name field. Press Enter.
(Optional) Type a description for the newly created service tools device ID and press Enter. You have finished creating a service tools device ID.
Note: The device ID and the service tools user ID must have proper authorization granted before the remote control panel and all it's functions are available for the associated logical partition. By default, the service tools device ID is granted access to the console and remote control panel for the partition it resides. If you don't want the remote control panel to be used with this service tools device ID, you must manually revoke the attribute using option 7.
To create additional service tools device IDs, repeat the steps starting at step 5.
Press F3 when you finish creating your service tools device IDs.

Notes:

If you must reset a service tools device ID, the password becomes the name of your service tools device ID in uppercase.
If you have more than one PC connected to your console, create several service tools device IDs for possible use during an emergency.
When creating a new service tools device ID for a server and Operations Console that are not installed with the same version of i5/OS^® and iSeries™ Access for Windows^®, respectively, the password becomes the name of the service tools device ID in uppercase, just as if the device ID were to be reset. For example, if the client is running V5R4 code and the server is running V5R3 code and you are creating a new service tools device ID for a new PC to connect, the server asks for a password for the device ID. Let's say you name the device "system1". When you create this on the server you are prompted for a password. You must use "SYSTEM1" because the client has no way of assigning a different password for this name. The same is true if the client is running V5R3 and the server is running V5R4. The V5R4 code, at either end, has no way to assign a password since the password is automatically made the same as the name in uppercase.
Sometimes the service tools device ID password needs to be reset. One example is when the password needs to be resynchronized between the PC and the server. When a mismatch occurs in the service tools device ID password between the server and the Operations Console PC, you need to resynchronize the password by performing recovery steps on the server. The PC no longer requires a manual reset of the service tools device ID password. For more information, see Resynchronize the PC's and the server's service tools device ID passwords. For additional information on service tools concepts, see Service tools user IDs and passwords.
Do not leave QCONSOLE in a reset state on the server. This is considered a security exposure.