Configuring your local system

To configure your local system for UUCP access, you must: take the following actions

Determine your local system name.
Create or edit configuration files.
Define the new user ID, NUUCP, to RACF®. The other required user ID, uucp, and group ID, uucpg, were already defined at installation time.

Determine your local system name

To determine what your system is called in the shell, issue:

uname –n

You will see the name by which your system is known in a communications network. It is the name specified by the IPL parameter SYSNAME. In z/OS® UNIX, UUCP recognizes the first eight characters of this name. Other UNIX systems might recognize more or fewer characters.

Add an entry to the permissions file

UUCP uses five different configuration files to describe various aspects of your UUCP setup. (To learn more about the configuration files, refer to Create or edit UUCP configuration files before proceeding with this section.)

The Permissions file is used to control the access that remote systems have to data and programs on the local system. You might want to change some of the default settings of the Permissions file.

If you need to change some of the default permissions for your local system (such as PUBDIR, READ, WRITE, NOREAD, or NOWRITE) then you will need an additional entry in the Permissions file for your local system. If you do not need to change the default permissions then you do not need an entry in the Permissions file for your local system.

For example, if you wanted to change your uucp public directory, your Permissions file might look like this:

   MACHINE=local                 \
          READ=/readall          \
          PUBDIR=/free
   MACHINE=site1:site2:SITE3     \
          READ=/readall          \
          COMMANDS=uucp:cat:cp:ls
   LOGNAME=NUUCP                 \
          READ=/readall          \
          PUBDIR=/free           \
          SENDFILES=yes          \
          VALIDATE=site1:site2:SITE3

Define the group ID and the user ID to RACF

As a customization step for UUCP, a UUCP-specific group ID (uucpg), and at least two user IDs are defined. The user IDs are:

uucp, the user ID that owns all the UUCP files and directories. Use it when editing configuration files or performing other administrative tasks. The user ID uucp and group ID uucpg are now requirements for ServerPac and CBPDO installations. See Security requirements for ServerPac and CBPDO installation.
A LOGNAME user ID that remote systems use when dialing in to your system. Traditionally, this user ID begins with NUUCP. For purposes of example here, we use NUUCP as the user ID. You might want to establish more than one LOGNAME user ID to handle different levels of access for remote systems.

You need to define these IDs to RACF. (If you are using an equivalent security product, refer to that product's documentation for more information about defining IDs to the security product.) All the RACF commands are issued by a TSO/E user ID with RACF SPECIAL authority. To make it easier to transport data sets from test systems to production systems, duplicate these entries in all of your security data bases, including the same UID and GID values in the OMVS segment.

If you use only uppercase IDs on your system, follow these steps to define the group ID and user IDs:

To define the LOGNAME user ID (in this example, it is specified as NUUCP), issue the following command:
```
ADDUSER NUUCP DFLTGRP(UUCPG) PASSWORD(xxxxxxx)
OMVS(UID(397) HOME('/usr/spool/uucppublic')
PROGRAM('/usr/lib/uucp/uucico'))
```
where:
- 397 is an example of a unique UID. Do not use UID(0).
- HOME('/usr/spool/uucppublic') is a required parameter that specifies the initial path name for the directory.
- PROGRAM('/usr/lib/uucp/uucico') is a required parameter that specifies the initial path name for the shell program.
Consider defining other user IDs similar to NUUCP to provide different access to your systems resources to the different remote systems issuing requests to your system. Each would have a unique UID, but would have the same attributes as NUUCP. In particular, each must have home directory of /usr/spool/uucppublic and initial program of /usr/lib/uucp/uucico. The UUCP permissions file is used to specify what these user IDs can access, as explained in The Permissions file.

Also follow these steps if you already use mixed-case group and user IDs on your system and the users do not conflict with existing names. You might want to add the lowercase names to your alias table, mapping them to uppercase names. This is not necessary, because when the lowercase names are not found in the alias table, they are folded to uppercase. For more information about the alias table, see USERIDALIASTABLE.

If a name such as NUUCP is not allowed on your system (or if it conflicts with an existing name), these are the RACF commands to define the user ID.

To define a LOGNAME user ID of xxnuucp):

ADDUSER xxnuucp DFLTGRP(UUCPG) PASSWORD(xxxxxxx)
OMVS(UID(397) HOME('/usr/spool/uucppublic')
PROGRAM('/usr/lib/uucp/uucico'))

where: xxnuucp is replaced by a 1- to 7-character user ID of your choice. This is the user ID that remote systems use when communicating with your system.397 is an example of a unique UID. Do not use UID(0). HOME('/usr/spool/uucppublic') is a required parameter that specifies the initial path name for the directory. PROGRAM('/usr/lib/uucp/uucico') is a required parameter that specifies the path name for the shell program.

You might want to define other user IDs similar to NUUCP to provide different access to your system resources to the different remote systems issuing UUCP requests to your system. Each would have a unique UID, but would have the same attributes as NUUCP. Each must have home directory of /usr/spool/uucppublic and initial program of /usr/lib/uucp/uucico. The UUCP Permissions file is used to specify the accessibility of each of these user IDs.

Define an alias for the xxnuucp user ID in your user ID and group name alias table.

xxnuucp nuucp

Tip: Using the alias table causes poorer performance and increases systems management costs and complexity. For more information about the alias table, see USERIDALIASTABLE.