topic tsotcp in SAS Programming

tsotcp

SASPhile — Wed, 02 Nov 2011 16:24:01 GMT

I dont know how to resolve this:

NOTE: Remote signon to SNACIP01 commencing (SAS Release 9.01.01M3P020206).

NOTE: Script file 'tcptso.scr' entered.

ERROR: Did not understand remote session banner.

ERROR: A communication subsystem partner link setup request failure has occurred.

ERROR: Communication script processing aborted.

ERROR: Remote signon to SNACIP01 cancelled.

35 rsubmit snacip01;

ERROR: A link must be established by executing the SIGNON command before you can communicate

with SNACIP01.

ERROR: Remote submit to SNACIP01 cancelled.

I used the following to download the datasets from Mainframe to PC sas:

filename snacip01 'C:\Documents and Settings\ac43926\Desktop\tcptso.scr';
options remote=snacip01 compress=yes;

signon snacip01;
rsubmit snacip01;
LIBNAME rmtdata "QINCQA.TST.RCAHMO.CATGCLMS.HEDIS10" disp=old;
PROC download DATA=rmtdata.hedis10 out=work.hedis10 ;
run;

endrsubmit;
signoff snacip01;

tsotcp

Tom — Wed, 02 Nov 2011 16:51:59 GMT

Edit your .scr file and turn on TRACE and ECHO. Normally the ones from SAS already have the

trace on;

echo on;

commands in them, but they are commented out.

If you do not see anything obviously wrong in the responses from your mainframe then open a ticket with SAS support and they should be able to help you more detail.

tsotcp

SASPhile — Wed, 02 Nov 2011 17:17:13 GMT

Uncommented trace on and echo on.

Opened ticket with SAS,

Neither was helpful.

tsotcp

Peter_C — Wed, 02 Nov 2011 17:27:47 GMT

if you show the text returned by the script dialog, we might recognise where the problem is.

tsotcp

Tom — Wed, 02 Nov 2011 17:29:01 GMT

I have never worked with TSO connection scripts, but most of the problems I have had with connecting to Unix, VMS, Windows machines have been either unexpected responses from the host or time-out issues. For time-out issues you can increase the time that it waits for the next prompt.

For the others you can look at what your host is sending and see if you can figure out how to get to the right point to send the username, password, sas command etc. So you might need to add some more waits to get past extra levels of prompts from the host. You might need to change the string that the script is waiting for because your system uses a different prompt. Or the string you are waiting for is included in the banner message so SAS sends the response too early and the remote is not ready.

tsotcp

SASPhile — Wed, 02 Nov 2011 18:45:01 GMT

NOTE: Remote signon to SNACIP01 commencing (SAS Release 9.01.01M3P020206).
NOTE: Script file 'tcptso.scr' entered.
ERROR: Did not understand remote session banner.
ERROR: A communication subsystem partner link setup request failure has occurred.
ERROR: Communication script processing aborted.
ERROR: Remote signon to SNACIP01 cancelled.
35   rsubmit snacip01;
ERROR: A link must be established by executing the SIGNON command before you can communicate
       with SNACIP01.
ERROR: Remote submit to SNACIP01 cancelled.
36   signoff snacip01;
NOTE: A link to SNACIP01 does not exist. SIGNOFF is not necessary.

tsotcp

SASKiwi — Wed, 02 Nov 2011 19:38:48 GMT

A few questions:

Has your signon process ever worked or is this the first time you have tried to get it going?

Are there other SAS users at your site doing mainframe signons, and are they successful? If they are, check your settings with them to see what you are doing differently.

Most SAS sites using TCP connections no longer use script files for logging on, but use the non-script method instead. If my understanding is correct this requires the SAS spawner to be running so it can listen for connection requests, and then start SAS instead of the script file starting SAS.

Do you have the SAS spawner running on your mainframe or not? If it is running then you can bypass the use of script files.

If you have to use a script file, then it appears you need to customise it so that it recognises your mainframe welcome screen.

tsotcp

SASPhile — Wed, 02 Nov 2011 20:03:47 GMT

I'm the only one,or the first one to do this.

How do I know if SAS spawner is running on MF?

tsotcp

Peter_C — Wed, 02 Nov 2011 22:54:18 GMT

that extract from your log is showing no screen from the server side of the signon dialog!

Please can you retry with an updated tsotcp having

ECHO ON

TRACE ON

near the start

and report what banner messages appear

Can you telnet to your mainframe?

tsotcp

SASKiwi — Wed, 02 Nov 2011 22:57:57 GMT

The spawner would have to be installed as a started task on the mainframe.

I would ask a friendly systems programmer how to look at MF started tasks.....

I also assume that SAS/CONNECT is installed and licenced on the MF.

If you can locate a MF SAS support person, and ask them if the SAS spawner was configured and set up that would also be useful.