Date: Tue, 31 Oct 2000 14:01:05 -0800
Reply-To: Jennifer Gibson <jg2f@UNIX.MAIL.VIRGINIA.EDU>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jennifer Gibson <jg2f@UNIX.MAIL.VIRGINIA.EDU>
Organization: University of Virginia
Subject: SAS/CONNECT Win95 to MVS
I'm seeking some advice about using SAS/CONNECT to access MVS datasets (I
know only what I've read about SAS/CONNECT in general and specific to this
question). In particular, how difficult is it to set up on the MVS side?
Our support people on that side are overextended and indicated it would be
many moons until they have available time, so I'm trying to get a feeling
for the magnitude of what I'm asking for. I have been told that CONNECT is
licensed on the MVS side, and I know for sure it is licensed and available
on the Windows side.
I have been accessing the MVS information using a telnet session by IP
address, and I think I have figured out the sequence of commands on the
Windows side to have SAS attempt the connection. The message I'm getting
back is "ERROR: Did not understand remote session banner." which I think is
just the PC timing out waiting for some response from the remote host. So
what do I need on the remote side to get this CONNECT session working?
What I want to be able to do with the remote session is to read and write
data back and forth, allowing a portion of the processing to be done in the
remote session and a portion to be done in the local session. In
particular, since I'm not too familiar with MVS, I'm curious how the system
moves from general login to a SAS session, where I need to point the login
request so the server will respond to me, and what configuration is
necessary on the server side so it will know to listen for me.
Thank you in advance for any assistance or suggestions!