Table of Contents
Advertisement
allowing all Operations Console connections to see where the console is. This is associated with the new
|
|
console option Allow console to be taken over by another console but the option does not have to be
enabled for this behavior to occur. For more information regarding this new function see Take over or
|
recover an Operations Console connection.
|
Perform the following steps to identify the user who has control:
|
1. In the iSeries Operations Console Connection Window, look for the row that shows the connection
|
|
details for the configuration in question.
|
2. Identify the Current
Current User shows the user ID with which the user in control signed on to the operating system of
|
the PC in control or completed the connection. System Name shows the PC name where the user is in
|
|
control.
3. Identify the Local Console value. It is the name of the PC that is directly attached to the server.
|
4. Compare the System Name and Local Console values as follows:
|
v The local console has control if the System Name and Local Console values are the same. This
|
|
comparison is useful to the connected remote console user.
v A remote console has control if the System Name and Local Console values are different. This
|
comparison is useful to the local console user.
|
v No user has control if SERVER appears as the Current User/System Name values. This is useful to
|
|
either the local console or the remote console user. A request for control will automatically be
granted.
|
|
Grant or refuse control to a remote console: As an operator of a local console with remote support, you
must handle incoming requests for iSeries control when you have control. Granting control allows
|
another user to work with the server. Refusing control denies a requesting user access to the server and
|
|
allows the current user to continue to have control. When you grant control to another user, your console
session and the remote control panel window close. You remain connected, and the remote control panel,
|
if installed and configured at the local console, is available in read-only mode.
|
When a remote console requests control, the Operations Console Request window appears at the local
|
console. The window shows the service tools user ID with which the requesting remote console user
|
|
signed on to the operating system of the remote console (PC). The default is set to grant control.
Granting control:
|
To grant control to a remote console, in the Operations Console Request window, click OK.
|
|
Refusing control:
To refuse control to a remote console, follow these steps:
|
|
1. In the Operations Console Request window, click Reject request.
|
2. (Optional) In the Message field, type an explanation for the refusal.
3. Click OK.
|
iSeries control: Control of your server means to have an active console or a functional remote control
|
|
panel (if installed and configured at the local console), or both, at a PC. An active console is a command
interface to a server (5250 emulation) that is currently interacting with the server. A functional remote
|
|
control panel allows you to perform control panel functions from the PC. Thus, the PC in control
|
becomes the console and can perform remote control panel functions. Only one PC can have control at a
time.
|
|
If your local console starts in attended mode you have control immediately after you Connect a local
console directly attached to the server. When you have control at this local console, you need to be
|
|
present to grant or refuse control to requesting remote consoles.
52
iSeries: iSeries Access for Windows Operations Console
®
User/System Name values. These values belong to the user who has control.
Advertisement
Table of Contents
