z/OS UNIX System Services Planning
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Steps for setting up for rlogin

z/OS UNIX System Services Planning
GA32-0884-00

Before you begin:
  1. You need to set up the appropriate security as described in:
    1. Preparing RACF.
    2. Defining z/OS UNIX users to RACF.
    3. Defining group identifiers (GIDs)
    4. Controlling access to files and directories.
    5. Setting up TCP/IP security
  2. You also need to customize the SUBFILESYSTYPE statement in BPXPRMxx to include TCP/IP.

Perform the following steps to set up for rlogin.

  1. Set up security for the inetd and rlogind daemons. See Steps for preparing the security program for daemons.

    _______________________________________________________________

  2. Establish the connection between TCP/IP and z/OS® UNIX; see z/OS Communications Server for more information.
    1. Define port 513 in /etc/services (if this file is to be used) or in the hlq.ETC.SERVICES data set, where hlq is the prefix defined by DATASETPREFIX in the TCP/IP profile ("TCPIP" by default). If /etc/services is defined, it will be used instead of hlq.ETC.SERVICES. The format of the line is:
       login		513/tcp
    2. IPL or re-IPL if needed.
    3. Start TCP/IP.

    _______________________________________________________________

  3. Customize /etc/inetd.conf. It tells inetd how to handle Internet service requests on Internet sockets. If you do not have that file, copy it from /samples.
    Example:
    cp /samples/inetd.conf /etc/inetd.conf
    Make these changes in the file:
    1. Change the user ID of the login server (which is rlogind) to an ID with daemon authority.
      login stream tcp nowait OMVSKERN /usr/sbin/rlogind rlogind -m
    2. Comment out any servers that are not needed by putting a # in the first column.

    _______________________________________________________________

  4. Start the inetd daemon. It is typically started from /etc/rc, which is executed when the system is initialized. Put these lines in /etc/rc, or uncomment them out, as the case might be:
    _BPX_JOBNAME='INETD' /usr/sbin/inetd /etc/inetd.conf&
    Tips:
    • When you start inetd from the shell, you need to do it from an OMVS session.
    • If TCP/IP is not yet up, you will receive error messages, but inetd will try again in a few minutes.
    • To obtain debugging information, issue:
      /usr/sbin/inetd -d
    • To verify that inetd is listening on port 513, issue the TSO NETSTAT INTERVAL command and check the output.

    _______________________________________________________________

When you are done, you can issue the rlogin command to log in from a remote UNIX system.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014