Appendix A. Preparing a Node to Run NQE

This appendix describes the steps necessary to prepare a node to run NQE.


Note: : Before you start NQE, you must perform the steps necessary to configure licensing, as described in this appendix. On each server, complete all the steps. On each client, complete only steps 1 through 3; if NPPA authentication is required, also complete step 6.


Procedure A-1.

To set up NQE, complete the following steps:


Note: You must complete steps 1, 2, and 3 on each NQE client. Also, step 6 is required in order for NPPA authentication to work. If NPPA is not required, connections to a client through FTA may be handled by the client's ftpd.


  1. If this is the first time NQE is being set up at your site, place the following entries in the /etc/services file:

    fta     605/tcp         #NQE fta services
    msql    603/tcp         #NQE msql service
    nlb     604/tcp         #NQE nlb service
    nqs     607/tcp         #NQE nqs service

  2. Add the NQE binary directory to your search path. This lets you issue commands without specifying their full path names.

    For sh or ksh, use the following command:

    export PATH=/nqebase/nqeversion/bin:$PATH

    For csh, use the following command:

    setenv PATH /nqebase/nqeversion/bin:$PATH

  3. Copy the license file to the /nqebase/nqeversion/etc directory and name it license.dat.

  4. Verify the integrity of the license file you received from Cray Research by using the following command.


    Note: The instructions for configuring the FLEXlm license manager assume that you have no other applications using FLEXlm licenses. If you do have other applications using FLEXlm licenses, consult FLEXlm documentation about combining licenses from multiple vendors.
    lmcksum -c /nqebase/nqeversion/etc/license.dat


    You will receive output about your license.dat file. The last line should give you a checksum number, as in the following example:

    lmcksum - Copyright (C) 1990 by Globetrotter Software, Inc.
    lmcksum: using license file "/nqebase/nqeversion/etc/license.dat"...
    52: (overall file checksum)

    This checksum (52: (overall file checksum)) should match the checksum line in your license.dat file. To see whether the checksums match, view the file. If the checksums do not match, contact your NQE customer service representative.

  5. Set the file access permissions on license.dat as follows:

    chown root /nqebase/nqeversion/etc/license.dat

    chgrp other /nqebase/nqeversion/etc/license.dat

    chmod 644 /nqebase/nqeversion/etc/license.dat

  6. Ensure that the /etc/inetd.conf file has the following entry.


    Note: For UNICOS and UNICOS/mk systems, include the -N option after ftad to enable NPPA.


    fta stream tcp nowait root /nqebase/nqeversion/bin/ftad  ftad

    The link to the /nqebase/bin/ftad path name is created after you start NQE.

  7. If you edit /etc/inetd.conf, send a hang-up signal (SIGHUP or kill -1) to the inetd process. This signals inetd to read /etc/inetd.conf. For example, if inetd has the process ID (pid) 634, use the following command:

    kill -1 634


    Note: : On AIX systems, if you manually edit the inetd.conf file, you must synchronize the inetd.conf file and the object data manager (ODM) database by using the inetimp command.


  8. By default, an NQS machine identifier (mid) is generated for your local host. If you want to change the mid for the local host or add mids for other local hosts, edit the /nqebase/nqeversion/etc/nqs_config file. For additional information, see NQE Administration, publication SG-2150, Chapter 7, or the qmgr(8) man page.

  9. If you are running the MLS feature on UNICOS systems or if you are running the ML-Safe feature on UNICOS/mk systems and want to change your MLS or ML-Safe configuration, see NQE Administration, publication SG-2150, Section 7.21.4; also, to install PALs, see NQE Administration, publication SG-2150, Section 7.21.2.

To set this NQE release to be the default NQE version, see Chapter 13, “NQE Version Maintenance Utility”.