Date: Sat, 31 Jul 2004 18:16:42 -0500
Reply-To: "A. Michielsen" <amichielsen@COMCAST.NET>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "A. Michielsen" <amichielsen@COMCAST.NET>
Organization: Your Company
Subject: Re: SAS via X server software & UNIX environment variables
It's not clear if you are connecting to use the X-Windows
Common Desktop Environment (X-CDE) or just a X-Telnet session.
If you are using the CDE - there are a set of CDE login scripts
that are used/created that are seperate/different from the standard
login scripts. You'd just need to add the SAS specific references
to the Desktop startup script. If I recall, the CDE .profile file
is called .dt_profile. Once in the CDE - there are a number of
'terminal' sessions that you can use from. Not all of the include
the login - so if the one being used doesn't work, try one of the
other ones.
If you aren't using the CDE - but just X-Telnet - something similiar
is true. On the Exceed setup, there are connection options besides
the REXEC - use one of those - but the command line changes. I don't
have a SUN command line example - we are using IBM - but it was a
task getting the complete command line correct so it worked right.
I don't even know who got ours working - now it's just a cut and
paste job. I believe that REXEC does reference startup files with
a different name - if you want/need to use REXEC. The secret would
be to figure out what file it is looking for, and copy what you need
into that file.
Nigel.Pain@SCOTLAND.GSI.GOV.UK (Nigel Pain) wrote in
> A number of users use Exceed X server software to get a SAS session,
> using the REXEC connection method. Unfortunately, when this happens,
> Solaris login scripts (/etc/profile and $HOME/.profile) are not run.
> These would set some important UNIX environment variables
> (LD_LIBRARY_PATH, ODBCINI) that are needed for connection to external
> ODBC databases.
>
> Can anyone suggest how I can get these environment variables defined
> for REXEC processes? There's probably a simple answer to this,
> exposing the limitations of my UNIX knowledge. I'm just not sure which
> FM to R!
|