Displaying The Remote Control Panel In Read-Only Mode; Requesting And Releasing Control At The Local Console - IBM System i Manual

2. Identify the Current User/System Name values. These values belong to the user who has control.
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 system.
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.

Displaying the remote control panel in read-only mode:

If you have the remote control panel installed and configured at the local console, you can display the
remote control panel in read-only mode. This allows you to see the remote control panel when you do
not have System i control.
For example, you can see the progress of an initial program load (IPL) at a system in a remote location.
You can display the remote control panel in read-only mode in the following cases:
v At a local console if the local console user is not in control.
v At a remote console after the remote console connects to a local console or a local console requests
control.
v At a remote console after the remote console releases control to a local console.
To display the remote control panel, from the Connection menu, click Remote Control Panel.
Displaying the remote control panel in read-only mode allows you to see the remote control panel when
you do not have System i control.

Requesting and releasing control at the local console:

When your local console with remote support does not have System i control, you must request control
at the local console to work with a system.
Requesting control at the local console forces control back from a remote console if the remote console
has control. After finishing your work, you must release control to allow Operations Console to
automatically grant control to a requester.
Related tasks
"Identifying user in control of a system" on page 51
Identifying the user who has System i control at a given time can help you determine how to proceed
when you want to obtain control. This information applies to a local console directly attached with
remote support and a remote console.
"Sending a message to a controlling remote console" on page 53
When using Operations Console, you might need to communicate with the user who has System i
control. Operations Console allows a local console and a remote console to exchange messages when
connected. Only the user that does not have control can initiate a message.
"Releasing control at the remote console" on page 54
Releasing System i control at the remote console allows control to go back to the state that the local
console was in when the first remote console requested control.
Related reference
52
System i: Connecting to System i Operations Console