This chapter describes how to use SysWorks to manage users.

A user is the basic mechanism which allows a person to access computers on the network. Each user must be registered on the network, and that registration has a variety of attributes which control when and to what the user has access.

The user management menu is selected using Manage => Users from the session manager. It displays the menu illustrated in Figure 8-1 and prompts for a selection.

Figure 8-1 User Management Menu

The following concepts need to be understood before managing users:

• Accounts - see Chapter 2
• Layered Products - see Section 6.4
• System User Classes - see Chapter 9

This task adds a new user to the network. It optionally creates the users home environment.

Example:

User: JONES_AB Member type (Organization/Person/Position): PERSON Surname: Jones Given name: Andrew Middle names: Brian Is this a new member (Yes/No) [Yes]: YES Title: Date of birth: Salutation: %SWRK-I-FROMNODE, Output from node SWRKA %SWRK-I-MBRADD, Member IJONES AB added %SWRK-I-FROMNODE, Output from node MELA01 Owner [Andrew B. Jones]: Initials [ABJ]: Telephone: Account: SWRK Location: UNKNOWN Create environment (Yes/No) [Yes]: Cluster [SWRKA]: (1)Initial logical sub-disk (2,3) [3]: Disk quota (0..unlimited) [5000]: UNLIMITED Password [9A4BE2FE]: WELCOME System user classes: USER,PATHWORKS %SWRK-I-FROMNODE, Output from node SWRKA (2)%SWRK-I-USGUIC, Using UIC [1000,51] %SWRK-I-USGID, Using identifier %X000100EB %SWRK-I-VMSUADD, OpenVMS username JONES_AB added %SWRK-I-OWNADD, Owner Andrew B. Jones added %SWRK-I-USRADD, User JONES_AB added %SWRK-I-FROMNODE, Output from node MELA01 %SWRK-I-FROMNODE, Output from node SWRKA %UAF-I-ADDMSG, user record successfully added %UAF-I-MDFYMSG, user record(s) updated %UAF-I-RDBADDMSGU, identifier JONES_AB value: [001000,000051] added to rights database %UAF-I-RDBADDMSG, identifier U_JONES_AB value: %X800100EB added to rights database %UAF-I-GRANTMSG, identifier U_JONES_AB granted to JONES_AB %SWRK-I-VMSUGRTSUC, OpenVMS username JONES_AB granted membership of system user class BASE %UAF-I-GRANTMSG, identifier S_BASE granted to JONES_AB %SWRK-I-VMSUGRTSUC, OpenVMS username JONES_AB granted membership of system user class USER %UAF-I-GRANTMSG, identifier S_USER granted to JONES_AB %SWRK-I-VMSUGRTSUC, OpenVMS username JONES_AB granted membership of system user class PATHWORKS %UAF-I-GRANTMSG, identifier S_PATHWORKS granted to JONES_AB %UAF-I-MDFYMSG, user record(s) updated %UAF-I-MDFYMSG, user record(s) updated (3)%SWRK-I-VMSUGRTPRD, OpenVMS username JONES_AB granted membership of product MAILWORKS %SWRK-I-TRYGRT, Trying to grant access to MAILWORKS %SWRK-I-VMSUGRTPRD, OpenVMS username JONES_AB granted membership of product VMSMAIL %SWRK-I-TRYGRT, Trying to grant access to VMSMAIL (4)Job SWRK_MANAGE_VMSMAIL_GRANT_USER (queue SWRK$BATCH_MELA01, entry 159) started on SWRK$BATCH_MELA01 %CLI-S-NORMAL, normal successful completion %SWRK-I-VMSUGRTPRD, OpenVMS username JONES_AB granted membership of product PCSA %SWRK-I-VMSUGRTPRD, OpenVMS username JONES_AB granted membership of product MSA %SWRK-I-TRYGRT, Trying to grant access to MSA %SWRK-I-VMSUGRTPRD, OpenVMS username JONES_AB granted membership of product PATHWORKS %SWRK-I-TRYGRT, Trying to grant access to PATHWORKS (5)02000029.$$$ was shared successfully. (6)JONES_AB was shared successfully. The command completed successfully. The command completed successfully. %UAF-I-MDFYMSG, user record(s) updated %SWRK-I-FROMNODE, Output from node MELA01

1. Note that logical sub-disks on the system disk are not used as defaults. As a result, a single disk system will never have a default initial logical sub-disk. Under those circumstances it would be necessary to explicitly enter the only available value, which is usually 2.
2. SysWorks determines the UIC for the user.
3. After granting access to the various system user classes, SysWorks determines which products the user has access to and attempts to grant access to each of the products. For the USER and PATHWORKS system user classes combined, is was determined that the user needed to be registered for the following products:
   • VMSMAIL
   • MAILWORKS
   • PCSA
   • MSA
   • PATHWORKS
4. A batch job is submitted under the new users name to set their OpenVMS mail configuration as this must be done under the users OpenVMS username.
5. This share name is based on the users UIC. It is a hidden share, and is used as the users home share when the username is greate than 8 characters in lengtb.
6. If the username is greater than 8 characters in length, only the UIC based share name will be created, otherwise this username based share will become the users home share.

This task create a users home environment. The use must have already been added to the network.

Example:

User: JONES_AB Cluster [SWRKA]: Initial logical sub-disk (2,3) [3]: Disk quota (0..unlimited) [5000]: UNLIMITED Password [9A4BE2FE]: WELCOME System user classes: USER,PATHWORKS

See the example for Add a user for the remainder of this example.

8.3 Delete a user's environment

This task deletes a users home environment. It optionally removes the user from the network. If the remove option is not used, the user will remain registered on the network.

Example:

User: JONES_AB

8.4 Modify a user's environment

This task modifies a users network details and/or their home environment.

Example:

User: JONES_AB

8.5 Move a user's disk area

This task moves a users disk area from one disk to another.

Example:

User: JONES_AB

8.6 Remove a user

This task removes a user from the network. It optionally deletes the users home environment first if necessary. If the option to delete is not used and a home environment for the user is found, the user will not be removed from the network.

Example:

User: JONES_AB

8.7 Rename a user

This task renames a user. Some external actions are implemented using a rename. These include renaming the username in the authorization file, and renaming the disk directory. Other external actions such as Pathworks registration require deleting the old username and creating the new one.

Example:

User: JONES_AB New username: AJONES

8.8 Generate a report about users

This task generates a report about users.

Example:

Output [SYS$OUTPUT]:

8.9 Secure a user's environment

This task sets the security of the users home area to the standard user security model.

Example:

User: JONES_AB

8.10 Set a user's password

This task sets the users password. If the user is registered for products which also require passwords (such as Pathworks (LAN Manager)), they will also be changed.

Example:

User: JONES_AB

8.11 Disable a user

This task disables a users home environment, which means that the cannot login. No other actions are taken. The users home environment and network management remain intact. Use the Enable a user task to reverse the effect of this task.

Example:

User: JONES_AB

8.12 Enable a user

This task enables a users home environment. It is used to reverse the effect of the Disable a user task.

Example:

User: JONES_AB

This chapter describes how to use SysWorks to manage system user classes.

Note that the set of system user classes provided with SysWorks is normally sufficient for most organizations, so a full understanding of how they work is generally unnecessary.

The system user class management menu is selected using Manage => System User Classes from the session manager. It displays the menu illustrated in Figure 9-1 and prompts for a selection.

Figure 9-1 System User Class Management Menu

The following concepts need to be understood before managing system user classes:

• Layered Products - see Section 6.4

The following standard pre-defined System User Classes exist:

System User Class	Usage
ACMS	ACMS user - provides access to ACMS.
ALL	All users - provides base level functions for all users.
ALLIN1	All-In-1 user - provides access to All-In-1.
APPLICATION	Applications - provides base level functions for all applications.
BASE	Automatically granted to provide basic OpenVMS authorization details.
CAPTIVE	Captive users - provides reduced base level functions for captive users.
DBA	Database Administrator - allows a users to use the SysWorks database administration features.
DCL	DCL user - allows a user access to DCL. Note that this system user class is only necessary when the USER system user class does not allow access to DCL by default.
DEVELOPER	Allows a users to use the SysWorks development features.
GROUP	Groups - provides base level functions for all groups.
OPERATOR	Operator - almost full read access and limited read/write access to all information.
PATHWORKS	Pathworks user - provides access to Pathworks including LAN Manager, PCSA and Macintosh variants.
PRINTER_CONTROLLER	Printer controller - may start and stop print queues and print jobs.
SYSTEM_MANAGER	System manager - full read/write access to all information.
USER	User recognized by SysWorks - All users should be a member of this system user class - the exception being Digital and other third party product usernames.
USER_REGISTRAR	User registrar - may add, create, delete and remove users from clusters and the security domain. Note that although a user registrar may register any user, they may only grant access to system user classes which they are a member of. Thus only members of the SYSTEM_MANAGER system user class may register other system managers. The exception to this rule is that a member of the SYSTEM_MANAGER system user class is an implicit member of all system user classes, so they can grant a user access to any system user class.

9.1 Add a system user class

This task adds a new system user class to the network.

Example:

System user class:

9.2 Modify a system user class's definition

This task modifies a system user class's details.

Example:

System user class:

9.3 Remove a system user class

This task removes a system user class from the network.

Example:

System user class:

9.4 Generate a report about system user classes

This task generates a report about system user classes.

Example:

Output [SYS$OUTPUT]:

This chapter describes how to use SysWorks to manage terminals.

The terminal management dispatch menu is selected using Manage => Terminals from the session manager. It displays the menu illustrated in Figure 10-1 and prompts for a selection.

Figure 10-1 Terminal Management Dispatch Menu

The terminal management menu is selected by entering TERMINALS at the selection prompt of the terminal management dispatch menu. It displays the menu illustrated in Figure 10-2 and prompts for a selection.

Figure 10-2 Terminal Management Menu

The terminal type management menu is selected by entering TYPES at the selection prompt of the terminal management dispatch menu. It displays the menu illustrated in Figure 10-3 and prompts for a selection.

Figure 10-3 Terminal Type Management Menu

The terminal server management menu is selected by entering SERVERS at the selection prompt of the terminal management dispatch menu. It displays the menu illustrated in Figure 10-4 and prompts for a selection.

Figure 10-4 Terminal Server Management Menu

The terminal server type management menu is selected by entering SRVTYPES at the selection prompt of the terminal management dispatch menu. It displays the menu illustrated in Figure 10-5 and prompts for a selection.

Figure 10-5 Terminal Server Type Management Menu

This chapter describes how to use multiple system disks.

Each node has an assigned system disk from which it boots. In some clusters a node may be moved between system disks so that when it is rebooted, it has a different set of software and/or performance characteristics. SysWorks^tm supports this concept by using separate system disks in conjunction with a three layer hierarchy within a cluster.

Each point within this hierarchy of node, tuning domain and cluster may have its own system disk. Each node has an assigned system root number. Where a node can be booted from multiple system disks, the same root must exist on each such system disk.

Table 11-1 lists the logical names defined for system roots which may reside on an alternative system disk.

Table 11-1 Logical Names for System Roots

Logical Name	Notes
SYS$SPECIFIC_TNDM	Equivalent of SYS$SPECIFIC on the tuning domain primary system disk.
SYS$COMMON_TNDM	Equivalent of SYS$COMMON on the tuning domain primary system disk.
SYS$SPECIFIC_CLUS	Equivalent of SYS$SPECIFIC on the cluster primary system disk.
SYS$COMMON_CLUS	Equivalent of SYS$COMMON on the cluster primary system disk.
SYS$SYSROOT_LIST	A search list with up to 6 equivalences which spans the full hierarchy of system roots for a node.

Table 11-2 lists the logical names defined for system files which may reside on an alternative system disk.

Table 11-2 Logical Names for System Files

Logical Name	Notes
ACMSAAF, ACMSDDF, ACMSUDF	If ACMS is present.
AUDIT_SERVER
LMF$LICENSE	File type of .LDB.
NETCIRC, NETCONF, NETLINE, NETLOGING, NETNODE_LOCAL, NETNODE_REMOTE, NETOBJECT	Used by DECnet Phase IV. Normally located in node specific system directory.
NETPROXY	Used by DECnet Phase IV. Normally located in common system directory.
NET$PROXY	Used by DECnet/OSI (i.e Phase V).
QMAN$MASTER	Only device and directory defined - no file name or type. Device and directory are unconcealed.
RIGHTSLIST
SYSALF
SYSUAF
VMSMAIL_PROFILE	File type of .DATA.
VMS$PASSWORD_HISTORY	File type of .DATA.