Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Configuring your local system z/OS UNIX System Services Planning GA32-0884-00 |
|
To configure your local system for UUCP access, you must: take
the following actions
Determine your local system nameTo
determine what your system is called in the shell, issue:
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 fileUUCP 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:
Define the group ID and the user ID to RACFAs a customization
step for UUCP, a UUCP-specific group ID (uucpg), and at least
two user IDs are defined. The user IDs are:
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:
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):
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.
Tip: Using
the alias table causes poorer performance and increases systems management
costs and complexity. For more information about the alias table,
see USERIDALIASTABLE.
|
Copyright IBM Corporation 1990, 2014
|