Date: Wed, 15 Dec 1999 10:59:16 +0100
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE>
Subject: TCP/IP connect from NT
Content-type: text/plain; charset=iso-8859-1
sometime this is a bit tricky!
I assume, that you are connecting to OS/390...?
There are some things to do:
do you have all things you need? (a CLIST with an alloc to the SAS C translib,
the appropriate access-script with the correct kind of acces - e.g.
full-screen-TSO - refer there for a correct setting of options!
Then the access script is to be modified, but how? A few tips:
- try to logon to the host with TELNET (just start TELNET in Win NT). This is,
what CONNECT does first.
- start SAS, if you was successful. You may be asked for some things during
that, like "applications", ... Try TSO, name of logon proc, ... the things you
also do in normal logon..
- if the TELNET LOGON is ok, start the SAS CLIST, you've prepared with the ALLOC
to the translib. SAS should start in line-mode, if it works.
- now start the PC environment and modify your signon-script: there are some
"waitfor"'s and "type"'s. The WAITFOR is scanning for strings on the screen.
These srings may not fit and you must modify them. A big help can be the
statement SNAPSHOT. It brings you a snapshot of the current host-screen into the
PC-SAS-log. You can see the strings there and can see, what is expected to
"TYPE" to the screen. Also the sequence of the strings, which are sent to the
host-screen can be figured out with SNAPSHOT;
For testing, you can use the little sequence to start the signon:
filename rlink "connect.scr"; /*your script file */
%let ip=184.108.40.206 23; /* the host-ip adr */
options remote=ip comamid=tcp;
If you are not successful and need further help, please contact me and provide
me with more informations. Once the TCP connect is established, it is very easy
Mit freundlichen Grüßen
D - 40217 Düsseldorf
Tel.: +49211 826 6173
Fax: +49211 826 5393