Date:         Wed, 18 Apr 2001 09:27:35 -0400
Reply-To:     Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Subject:      Re: Another SAS/Connect Q

On Wed, 18 Apr 2001 07:04:04 -0600, Darran Zenger <DZENGER@KLUNE.COM> wrote:

>I know I have posted a question on the newsgroup a while back on
SAS/Connect
>from home but I just happened to think of another question. I don't think
it
>really makes much difference, but thought I'd ask for my personal
knowledge.
>
>
>My question is, for SAS/Connect to work, do both SAS sessions have to be
>from the same version? For example, SAS for PC version 8.2 and SAS Server
>has 8.1.  I see that many are using 6.12, so what happens when using
>SAS/Connect with one as 6.12 and another as 8.x? Would that then become a
>problem?
>
>Thanks.
>
>Darran
>

For sure! Danger and obstacles are everywhere!

Connecting seems not to be a problem. We tested that and had no problem. We
have a big performance problem if we use SAS V8 on the PC with EHLLAPI
protocol. It is 5-10 times slower than V6.12

We have not seen any problems if we rest in the V6 environment. We start
the remote V8 - session with the V6 library engine as default. I expect,
that the access to V8-libraries with long variable names will not be
possible with RLS. However (we did not test that) it should be possible to
remote-submit V8-code to produce reports which can be displayed in the
local session. It should be also possible to manipulate remote data.

All in all I expect big problems in all environments where you need local
V6-SAS to do something with V8-datasets. V6 has no V8-engine! So I think,
that for example a PROC DOWNLOAD will not be successful, because you try to
bring V8-structures to V6. A PROC UPLOAD could work maybe.