SET SECUSER

Read syntax diagramSkip visual syntax diagram Set SECUSER Privilege Class A or CPrivilege Class G
Privilege Class A or C
Read syntax diagramSkip visual syntax diagram 1 targetid OFFRESETuserid*2
Privilege Class G
Read syntax diagramSkip visual syntax diagramtargetidOFFRESETuserid
Notes:
  • 1 If SET SECUSER is executed with the AT command, the targetid operand is required.
  • 2 If SET SECUSER is executed with the AT command, the * operand is not allowed.

Authorization

Privilege Class: A, C, G

Purpose

Use SET SECUSER to change the secondary user for a virtual machine. The second user is a virtual machine that receives console messages from and can enter commands to the console of a disconnected virtual machine. If you are a class G user, you can change the secondary user for your own virtual machine. If you are a class A or C user, you can change the secondary user for any virtual machine.

Operands

targetid
is the user ID of the virtual machine whose secondary user is to be set or reset. If you are a class A or C user and you do not specify targetid, CP sets or resets the secondary user for your user ID. If you are a class G user, you can stop being the secondary user for targetid by specifying targetid OFF.
OFF
cancels the secondary user setting. OFF terminates any console sharing with an existing secondary user.
RESET
sets the secondary user for targetid or the command issuer to the user ID specified on the CONSOLE statement in the user's directory entry.
userid
is the user ID of the secondary user virtual machine.
*
sets the secondary user to the virtual machine that issues the command.

Usage Notes

  1. If secondary user support is used with large console messages that are close to the free storage limit of X'1FD' doublewords, it is possible that the message could be truncated at the end in order to add the header at the beginning which indicates the user ID from which the message originated.
  2. A virtual machine cannot have both a secondary user and an observer defined by any combination of the SET SECUSER and SET OBSERVER commands and the CONSOLE directory statement.
  3. If the designated secondary user is currently unable to function in that capacity (for example, not logged on, or disconnected with no connection to *MSG or *MSGALL), the setting is nevertheless accepted by CP, and the relationship is established when the specified user ID meets the necessary criteria.
  4. In an SSI cluster, the secondary user and the primary user can be logged on to different member systems.
    If either user is a multiconfiguration virtual machine:
    • The secondary user will function in that capacity only when it is local (logged on to the same member as the primary user). If the primary user is a multiconfiguration virtual machine, the secondary user must be logged on to the member where the SET SECUSER command was issued.
    • If the secondary user is remote:
      • The secondary user can issue SEND commands to the primary user. The AT sysname operands are required if the primary user is a multiconfiguration virtual machine instance.
      • The secondary user will not receive responses to SEND commands or any other output from the primary user.

Examples

Example 1:

USERA (a general user) designates USERB (another general user) as its secondary user by issuing the following command:
set secuser userb
USERB can stop being the secondary user for USERA by issuing the following command:
set secuser usera off
If USERC is the secondary user for USERD, USERD can remove its secondary user by issuing the following command:
set secuser off

Example 2:

USERC (a class A or class C user) issues the following command to assign USERD as the secondary user for USERB:
set secuser userb userd
USERD receives the following message:
HCP6768I SECUSER of USERB initiated for you by USERC.
At the same time, USERB receives one of the following messages:
HCP6768I Your SECUSER set to USERD by USERC.
-or-
HCP6769I Your SECUSER terminated by USERC.

Example 3:

USERC can remove the secondary user for USERB by issuing the following command:
set secuser userb off
This causes the user ID that was the secondary user (USERD) to receive the message:
HCP6769I SECUSER of USERB terminated for you by USERC.

Example 4:

If the command issuer becomes the secondary user, the message issued at initiation is:
HCP6768I SECUSER of primary_userid initiated.
When the secondary user option is terminated, the message issued is:
HCP6769I SECUSER of primary_userid terminated.

Messages

  • HCP002E Invalid operand - operand
  • HCP003E Invalid option - command contains extra option(s) beginning with option
  • HCP007E Invalid userid - userid
  • HCP017E User userid is being observed and cannot have a SECUSER
  • HCP026E Operand missing or invalid
  • HCP045E userid not logged on
  • HCP053E userid not in CP directory
  • HCP0150E User userid has issued a CP or VM read.
  • HCP1149E Error communicating with another SSI member. It cannot be determined if command executed remotely.
  • HCP6768I SECUSER for primary_userid of secondary_userid is not functional
  • HCP6768I SECUSER of primary_userid initiated.
  • HCP6768I SECUSER of primary_userid initiated for you by userid.
  • HCP6768I Your SECUSER set to secondary_userid by userid.
  • HCP6769I SECUSER of primary_userid terminated.
  • HCP6769I SECUSER of primary_userid terminated for you by userid.
  • HCP6769I Your SECUSER terminated by userid.