Chapter 4. Customizing Preinstalled NQE

If you have received a new UNICOS or UNICOS/mk system that was delivered with NQE preinstalled, you need to customize the NQE installation for your site. Complete the steps in this chapter if you have either the full NQE configuration or only the NQE subset (NQS and FTA) configuration.


Note: All steps in this chapter should be completed before starting NQE.



Caution: Ensure that you have installed your FLEXlm license file for this release. The FLEXlm license included with your NQE 3.3 release may be only a temporary license. If it is only a temporary license, you must order and install your permanent NQE license and then restart NQE 3.3.

Cray PVP UNICOS systems that run only the NQE subset (NQS and FTA) do not require a FLEXlm license file.

For information about FLEXlm licensing requirements, see Chapter 6, “FLEXlm License Requirements”.

The modules package should already have been installed on your system. To verify that the modules package is installed, enter the following command:

ls /opt/modules
2.2 modules

For information about installing modules with NQE, see Chapter 16, “Using modules with NQE”.

For information about planning your configuration, see Chapter 7, “Planning Your Configuration”.


Note: To complete the following steps, you must have root permission.

To customize NQE software that has been preinstalled on your system, perform the following steps:

Procedure 4-1.

  1. Attach your system to the network, and define the host name and IP address of the machine.

  2. During the NQE preinstallation process, the symbolic link /etc/nqeinfo may have been created. Ensure that this symbolic link is removed by executing the following command:

    rm -f /etc/nqeinfo

  3. Create a host-specific configuration directory without a domain name extension, as follows:

    cd /nqebase/version
    mkdir `hostname | cut -d. -f1`
    cd `hostname | cut -d. -f1`

    For example, if you were installing NQE 3.3 on a system named thunder.cray.com, you should now be in the /nqebase/3.3/thunder directory.

  4. Generate a new nqeinfo file by invoking the NQE configuration utility (nqeconfig(8)), as follows:

    ../bin/nqeconfig -a -o ./nqeinfo

    For information about using the NQE configuration utility, see Appendix B, “Configuring NQE Variables”.

    A new nqeinfo file should now exist in the current directory; this file contains information specific to the host name of your system.

  5. Create symbolic links by using the NQE maintenance utility (nqemaint(8)). First, invoke nqemaint(8) as follows:

    export DISPLAY=myhost:0
    ../bin/nqemaint

    After invoking the nqemaint(8) utility, click on the Make Default button to create all of the necessary symbolic links. After the process is complete, exit nqemaint(8). For information about running nqemaint(8), see Chapter 13, “NQE Version Maintenance Utility”.

  6. Read Chapter 14, “Read This Before You Start NQE”, for important information you should know about before you start NQE 3.3.

To prepare a node to run NQE and to start NQE, see Appendix A, “Preparing a Node to Run NQE”.

For information about how to start and stop NQE, see the nqeinit(8) and nqestop(8) man pages. On UNICOS systems that run only the NQE subset (NQS and FTA components), for information about how to start and stop NQS, see the qstart(8) and qstop(8) man pages.