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 running the SAS/IntrNet Application Dispatcher, if you are
unable to submit a request using Launch Service, the following
suggestions may be helpful when diagnosing the problem.

 1.  Submit a request from your Web browser, using the
     _debug=1024 option.  For example:


   http://a.b/cgi-bin/broker.exe?_debug=1024&_service=newsas&_program=ping


     This will cause output to be sent to your Web browser
     indicating the entire command that would have been issued
     to launch the SAS job (with all SAS options).
     Check the command for accuracy, including all options.
     As a test, try to invoke SAS using the SAS executable that
     is specified on the command.

 2.  Submit a request from your Web browser using the _debug=4096
     option. This will cause the SAS log and other "working files" to be
     saved in the directory specified by "TmpDir" in the broker.cfg
     file.  Check the SAS log (if one is created) for error messages.

 3.  The _debug=2305 option may also provide useful information.  See
     the following url for more information on debugging:


http://support.sas.com/onlinedoc/913/getDoc/en/dispatch.hlp/debuging.htm

 4.  Check the permissions on your SAS installation directory as well
     as any other directories that are used in the Launch Service
     definition (as in the SasBin, SasOpts, TmpDir or SasCommand
     directives).  With a Launch Service, the SAS session is started
     using the userid of the Web server (which varies across platforms),
     so it is necessary to open up permissions for that userid to
     execute SAS.

See SAS Note V6-BROKER-F775 for tips pertaining to IntrNet 1.2.

Operating System and Release Information