SECUSER

Notes:

¹ For more information on prefix keywords, see the DIRMAINT EXEC.

Purpose

Use the SECUSER operand of the DIRMAINT command to allow the general user to manipulate the secondary console field on their console statement in a directory entry.

Operands

?: queries the directory to see if a secondary user ID is currently specified on their CONSOLE statement.
OFF: specifies a request to delete the secondary user ID from their console statement.
userid: specifies the user ID to place on the CONSOLE statement to act as the secondary console.
OBServer: indicates that the specified user is an observer rather than a secondary user for the virtual machine whose console is being defined.

Usage Notes

You may use one or more of the prefix keywords (REQuest, TOsys, ASuser, BYuser, PRESET, FORuser, ATnode, NODIRectxa) with this command. These prefix keywords may be specified in any order, but each keyword may only be specified once.
For more information on the CONSOLE directory statement, see z/VM: CP Planning and Administration.
The use of SECUSER, AUTHSCIF, DSECUSER and DROPSCIF commands are closely related. The userid must have granted the issuing user authority through the AUTHSCIF command to use them as a secondary console. An error message will result if this has not been done. For example, if the userid WATCHER chooses to become the secondary console of the disconnected user SERVER, this sequence of commands is needed:
1. WATCHER issues DIRM AUTHSCIF SERVER
2. SERVER issues DIRM SECUSER WATCHER
When the secondary user facility is no longer needed, one of two commands would be needed:
1. WATCHER issues DIRM DSECUSER SERVER
2. SERVER issues DIRM SECUSER OFF
If SERVER is not going to use WATCHER as a SCIF user again, the general authority can be cancelled if WATCHER issues:
```
DIRM DROPSCIF SERVER
```
The design allows the SCIF target userid (WATCHER) to have overall control of the usage of SCIF, in case of SERVER produced SCIF output which the target was not able to handle. SERVER has sole control of the time it is turned on, but WATCHER must authorize it first. If the SECUSER command is issued before the nominated userid has granted authority with the AUTHSCIF command, an error message will result.