Usage Note 16689: SAS/CONNECT® software spawner does not invoke a remote SAS® session without the full path to SAS
Starting with SAS® 9.1, you must specify the full path to SAS® in the SAS invocation statement if you want the SAS/CONNECT software spawner in the UNIX environment to invoke the remote SAS session. If you do not define the path to the remote SAS session, the following error message displays:
ERROR: Cannot start remote process.
In SAS 9.1, the code that starts the SAS/CONNECT software spawner was changed, and the
PATH environment variable is no longer passed to the spawner. One of the parameters
that was previously set in the PATH variable and that was sent to the spawner was
the location of the ! SASROOT directory.
You must now specify the full path to SAS in the SAS invocation
statement. For example, in the tcpunix.scr script file, specify:
type '/usr/local/sas9.1.3/sas -dmr -device grlnk
-no$syntaxcheck' lf;
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS/CONNECT | 64-bit Enabled Solaris | 9.1 TS1M3 SP2 | |
| HP-UX IPF | 9.1 TS1M3 SP2 | |
| Tru64 UNIX | 9.1 TS1M3 SP2 | |
| 64-bit Enabled HP-UX | 9.1 TS1M3 SP2 | |
| 64-bit Enabled AIX | 9.1 TS1M3 SP2 | |
| Linux on Itanium | 9.1 TS1M3 SP2 | |
*
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.
| Type: | Usage Note |
| Priority: | low |
| Topic: | Software Components ==> Connect Spawner
|
| Date Modified: | 2008-05-15 14:41:39 |
| Date Created: | 2005-12-15 11:03:46 |
