Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

When Platform LSF Process Manager (the job flow daemon [jfd]) does not start, check the following:

• Make sure that jfd is running. At a UNIX system prompt, type ps -ef | grep jfd.
• Verify that the license file is valid by checking that the line containing the string EXPIRE 'PRODNUM151' contains a valid date in the future. To view the license file, type the following at a UNIX system prompt:

  prompt: cd !JS_TOP/conf 
  prompt: cat license.dat

• Make sure that the parent directory to JS_TOP (that is, the installation directory of the Process Manager) has Read/Write/Execute permission:
  • In the executable directory, $JS_SERVERDIR, run the following command:

    ./jfd -3

  • If the following error messages display in the output after running this command, then the parent directory of JS_TOP needs the Read/Write/Execute permission set as described below:

    Jun 02 15:50:53 454954 1 3 Error 24001: Unable to obtain var_comm directory.
    Jun 02 15:50:53 454954 1 4 ThreadEx::opCtrl (): write error: Bad   
    file number --  m_hController <-1>

  • To set Read/Write/Execute permission, perform the following:
    1. Locate the Process Manager subdirectory. For example, the path might be /opt/sas/Platform.
    2. Submit the following command to set Read/Write/Execute (drwxr-xr-x) permission for the /opt/sas/Platform directory:

       prompt: chmod 755

If these suggestions do not solve the problem, turn on the debugging facility for jfd in the UNIX environment. For more information about the debugging facility, see SAS Note 30570, "Turning on the debugging facility for the job flow daemon (JFD) in the UNIX environment."

In addition, you can send the jfd.log.machine_name file to SAS Technical Support. This file is found in the !JS_TOP/log directory. You can also send the output to SAS Technical Support.

Operating System and Release Information