If you have problems with names such as UUCP, UUCPG, and TTY

If names such as uucp, uucpg, and TTY are not allowed on your system (or if they conflict with existing names), the following examples show the RACF® commands to define the group ID and user IDs.

To define a group ID instead of the TTY group, issue:
```
ADDGROUP xxtty OMVS(GID(2))
```
where 2 is an example of a unique group ID on your system, and XXTTY is replaced by a 1-to 8-character group ID of your choice. Do not connect users to this group. This would be the same group name to be specified in the TTYGROUP statement in the BPXPRMxx member on your target system.
To define a group ID instead of the UUCPG group, issue:
```
ADDGROUP xxuucpg OMVS(GID(8765))
```
where 8765 is an example of a unique group ID on your system, and xxuucpg is replaced by a 1-to 8-character group ID of your choice.
To define a user ID instead of the UUCP user ID, issue:
```
ADDUSER xxuucp DFLTGRP(UUCPG) PASSWORD(xxxxxxx)
OMVS(UID(396) HOME('/usr/spool/uucppublic') 
PROGRAM('/bin/sh'))
```
where:
- 396 is an example of a unique UID. Do not use UID(0).
- xxuucp is replaced by a user ID of your choice. This is a normal user ID which owns all the UUCP files and directories. Use this user ID when editing configuration files or performing other administrative tasks.
- HOME('/usr/spool/uucppublic') is a required parameter that specifies the initial path name for the user ID.
- PROGRAM('/bin/sh') is a required parameter that specifies the path name in the shell program for the user ID.
Set up a user ID alias table.
Tip: Using the alias table reduces performance and increases systems management costs and complexity. For more information about the alias table, see USERIDALIASTABLE.

If you do not have a user ID alias table defined, you will need to create one. Create it first on your driving system and then on any system image using this product. This fits in with the IBM® strategy to place all customized data in the /etc directory. This table is specified by the USERIDALIASTABLE keyword in the BPXPRMxx member. Because the user ID name alias table must be protected from update by nonprivileged users, only users with superuser authority should be given update access to it. All users should have read access to the file.
Your user ID alias table will need to contain your MVS™ chosen names and the associated required names. Your chosen MVS user ID and group names must be located in columns 1-8 and the associated aliases must be located on the same line in columns 10-17.
```
:groups
XXTTY        TTY        
XXUUCPG  uucpg     
:userids 
XXUUCP     uucp
```
Activate the user ID alias table. If you are already using the user ID alias table, new database queries will yield the new alias if the userid performing the query has read/execute access to the userid/group name alias table. The table is checked every 15 minutes and refreshed if it has been changed. If a change needs to be activated sooner, you can use the SETOMVS or SET OMVS operator commands.
If you are not using the user ID alias table, you can use the SET OMVS operator command to activate it now. For example:
```
SET OMVS USERIDALIASTABLE=/etc/tablename 
```
where /etc/tablename is the name of your user ID alias table. You can also use the SETOMVS operator command.
Specify USERIDALIASTABLE in your BPXPRMxx member to make this change permanent for your next IPL.
Perform these tasks on all of your driving, test, and production system images.

For more information, see: