|Date: ||Tue, 31 Oct 2000 15:29:44 -0500|
|Reply-To: ||Abelson_R <Abelson_R@BLS.GOV>|
|Sender: ||"SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>|
|From: ||Abelson_R <Abelson_R@BLS.GOV>|
|Subject: ||Re: SAS/CONNECT Win95 to MVS|
If SAS/CONNECT is already installed on the MVS side, go ahead and read the
rest of this reply. If it isn't, you're at the mercy of the systems folks
and won't be able to do anything until they install it. If, as you say, it's
licensed, then it probably is installed.
Getting SAS/CONNECT working with an MVS system is always a little tricky,
since there are lots of settings that will vary from site to site. However,
SAS supplies the CONNECT script files. By necessity, they're pretty generic,
so they work almost nowhere, but they contain enough of the basics so that
you can modify them to work with your local setup.
I'm going to assume that since you can access MVS via telnet, you can use
the script file tcptso.scr that you should be able to find somewhere in a
Windows subdirectory of SAS. This will have to be modified to conform to
the prompts that you see when you log onto TSO. It will help if you can
capture these in a file. You also will need to set OPTIONS COMAMID=TCP
Expect a lot of trial and error here before you get it working.
Once you've modified this file (don't overwrite the original!), you will
need to let your local (Windows) SAS session know how to connect to MVS. I
take care of this in my autoexec.sas file by adding a couple of lines:
options comamid=TCP remote=<name of MVS host>; * this tells SAS to
communicate with the host using TCP/IP access method;
filename RLINK "<directory>\tcptso.scr"; * this points to the script file;
This way, when you click Locals, Signon, you don't have to fill in any of
the boxes other than User ID and Password once you are prompted.
Best of luck.
Bureau of Labor Statistics
"The generation of random numbers is too important to be left to chance."
-- Robert R. Coveyou, Oak Ridge National Laboratories
> From: Jennifer Gibson[SMTP:jg2f@UNIX.MAIL.VIRGINIA.EDU]
> Sent: Tuesday, October 31, 2000 5:01 PM
> To: SAS-L@LISTSERV.UGA.EDU
> 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
> 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
> 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
> 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
> 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!