This chapter describes how to start and stop NQE.
 | Caution: You must monitor the files in $NQE_SPOOL/log to ensure the log files for the startup and shutdown utilities (for nqeinit(8), nqestop(8), qstart(8), and qstop(8)) and related utilities do not accumulate and consume space needlessly. |
The nqeinit(8) script is called to start the NQE cluster and to initialize its components. It checks the NQE_DEFAULT_COMPLIST variable in the nqeinfo(5) file for the list of components to be started. You can set this list to one or more of any of the following valid NQE components:
| NQS | Network Queuing System | |
| NLB | Network Load Balancer | |
| COLLECTOR | NLB collector | |
| NQEDB | NQE database | |
| MONITOR | NQE database monitor | |
| SCHEDULER | NQS scheduler | |
| LWS | Lightweight server |
Beginning with the NQE 3.3 release, the default component list consists of the following components: NQS, NLB, and COLLECTOR.
Component names in the NQE_DEFAULT_COMPLIST component list can be specified in upper or lower case, but not mixed case for one component name. When more than one component name is specified (that is, a list of components), the component names are separated by a comma (,).
You can use the -C component option of the nqeinit command to override the NQE_DEFAULT_COMPLIST variable component list. When you use the nqeinit -C option, only the components specified (see valid component names in “Starting NQE”, above) are started and the NQE_DEFAULT_COMPLIST variable in the nqeinfo file is ignored for this invocation of the nqeinit(8) command.
 | Note: For UNICOS systems that run only the NQE subset (NQS and FTA components), use the qstart(8) command instead of the nqeinit(8) script to start NQS. For additional information, see “Starting NQS” in Chapter 6. |
| Note: Start any NQE nodes configured to run the NQE database server or the NLB server first because each node once started sends system status information to the NLB server for use in load balancing. |
Typically, nqeinit(8) should be called as part of the normal system startup procedure by using either a direct call in a system startup script or a startup utility such as sdaemon(8).
For information about nqeinit(8) command-line options, see the nqeinit(8) man page.
For information about symbolic links used by NQE, see the nqemaint(8) man page.
The nqestop(8) script is called to stop the NQE cluster and to shutdown its components. It checks the NQE_DEFAULT_COMPLIST variable in the nqeinfo(5) file for the list of components to be stopped. You can set this list to one or more of any of the following valid NQE components: NQS, COLLECTOR, NLB, NQEDB, MONITOR, SCHEDULER, and LWS. For more information on these components, see “Starting NQE”. For more information on the NQE_DEFAULT_COMPLIST variable, see “Starting NQE”.
You can use the -C component option of the nqestop command to override the NQE_DEFAULT_COMPLIST variable component list. When you use the nqeinit -C option, only the components specified (see valid component names in ???TITLE???, above) are stopped and the NQE_DEFAULT_COMPLIST variable in the nqeinfo file is ignored for that invocation of the nqestop(8) command.
| Note: For UNICOS systems that run only the NQE subset (NQS and FTA components), use the qstop(8) command to stop NQS. For additional information, see “NQS Shutdown and Restart” in Chapter 6 |
Typically, nqestop(8) should be called as part of the normal system shutdown procedure by using either a direct call in a system shutdown script or a shutdown utility such as sdaemon(8).
For information about nqestop(8) command-line options, see the nqestop(8) man page.