Date:         Sun, 24 Feb 2002 04:01:33 -0800
Reply-To:     "Karsten M. Self" <kmself@IX.NETCOM.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Karsten M. Self" <kmself@IX.NETCOM.COM>
Subject:      Re: Multiple SAS sessions/same account?
In-Reply-To:  <200202211700.g1LH0R412260@listserv.cc.uga.edu>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";

on Thu, Feb 21, 2002, Gerhard Hellriegel (ghellrieg@T-ONLINE.DE) wrote:
> On Thu, 21 Feb 2002 17:59:54 +0200, Arjen Raateland
> <arjen.raateland@VYH.FI> wrote:
> 
> >Initiating a second SAS session on the Win 2000 machine under the same
> >user account locks up the first SAS session completely.
> >The second session sets up a WORK.PROFILE as usual. The first session
> >will not return to life after the second session has been exited,
> >either.

> I think the problem are the SASUSER and the WORK libs.
> You must use a different CONFIG file for each user. Or you can try to setup
> your entries for the pathes variable e.g. with the user as part of the path.
> Maybe it works if you say:
> -sasuser sasuser
> instead of
> -sasuser c:\sas\sasuser

...under GNU/Linux, VMS, and Unices, multiple concurrencies were happier
if the RASASUER option was specified, though neglecting to do so merely
resulted in a warning, not an abortion (well, other than the
obvious....;-)

Might look to that.

Peace.

-- 
Karsten M. Self <kmself@ix.netcom.com>    http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?       There is no K5 cabal
  http://gestalt-system.sourceforge.net/         http://www.kuro5hin.org


[application/pgp-signature]