Date: Thu, 25 Mar 2004 16:18:32 -0600
Reply-To: "Skinner, Deborah" <Deborah.Skinner@ASSURANT.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Skinner, Deborah" <Deborah.Skinner@ASSURANT.COM>
Subject: SAS/Connect - Windows Server to Mainframe - running EG client on
desktop
Content-Type: text/plain; charset="us-ascii"
SAS-L ---
Please help!
Our environment is running SAS on a Windows 2000 server and Enterprise
Guide as a client on the desktop. In addition, we are running
SAS/Connect on both the Windows server and on our mainframe. So, for
purposes of SAS/Connect - this is basically 3 tiers - EG client to SAS
Windows Server to Mainframe SAS.
We have successfully configured a SAS/Connect script running via the
TELNET (tcp) method from our Windows server. I can run some test code
from the server - calling this script - and it successfully process some
RSUBMIT code on the mainframe. So, running directly from the server,
all is good.
However, when you put Enterprise Guide into the mix, that same code
running from the EG code window fails. The problem appears to be
that the prompts for the userid and password are not being returned to
the EG client from the Windows server - which I guess doesn't really
surprise me all that much. However, since EG is our desktop
environment (no terminal services for Windows SAS?) - I've got to
figure out how to make this work.
I think I see that one solution would be to have the user ID and
password hard-coded in the telnet script file - but I'm not sure that I
think that is a great idea. (However, it is what we will try if it is
the most viable solution.)
**************************************************************************************
This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof.
Thank you.
**************************************************************************************
|