Usage Note 36283: Configuring Platform LSF and Process Manager daemons so that they start automatically as Windows services
Sometimes a Windows operating system does not start all of the Platform services automatically when you initialize your system. This note explains how to configure the services to properly start in sequence.
Set the LSF_GETCONF_* System Environment Variables So That They Are Available upon System Initialization
- Select Start ► Settings ► Control Panel ► System.
- On the Advanced tab, click the Environment Variables button to display the Environment Variables dialog box:
-
In the System variables section, click New to open the New System Variable window, as shown here:
- In the Variable Name text box, enter LSF_GETCONF_INTERVAL. In the Variable Value text box, enter the value 5. Then click OK to save your variable and its value in the registry.
- Repeat the previous step for the LSF_GETCONF_TIMES environment variable and use a value of 10.
- Then click OK to close the Environment Variables window and to save your changes.
Set the Platform LSF and Process Manager Service Dependencies
Next, set the Load Information Management (LIM) service to be dependent on another Windows service (for example the Server or Workstation services) that is known to begin late in the services start-up cycle.
To set the LIM service, you must first obtain the exact service names from the Windows Services administrator window. To open the Services window:
- Do one of the following:
- Select Start ► Settings ► Control Panel ► Administrative Tools ► Services.
- Enter the following command from a command prompt:
services.msc
-
Then, double-click the LSF services and record the exact service name from the text box of the same name. For example, in the following display, for the LSF cluster1 LIM display service name, the name in the Services window is LIM-cluster1, as shown below:
You need to set the following dependencies:
- Set the RES service to be dependent on the LIM service.
- Set the SBD service to be dependent on the RES service.
- Set the Process Manager service to be dependent on all three services: LIM, RES, and SBD.
- Then, from a Windows command prompt, configure the services dependencies by submitting the following commands. Use the exact service names that you find in your Services window to replace the user-supplied values in the following commands:
C:\> sc config LIM-service-name depend= LanmanWorkstation/LanmanServer
C:\> sc config RES-service-name depend= LIM-cluster1
C:\> sc config SBD-service-name depend= RES-cluster1
C:\> sc config “Process Manager” depend= RES-service-name/SBD-service-name
Note that in the Windows Services window, the two "Lanman" services show up simply as "Workstation" and "Server," respectively. Also note that there is a required syntactic space after the "depend=" option for the commands.
After you make all of these changes, all of the services should start automatically when you initialize your system.
Operating System and Release Information
| SAS System | Platform Computing Suite for SAS | Microsoft Windows XP 64-bit Edition | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Standard Edition | 2.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 2.1 | | 9.1 TS1M3 SP4 | |
| Windows Vista | 2.1 | | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Date Modified: | 2009-12-16 13:15:53 |
| Date Created: | 2009-06-18 15:29:04 |