Prev: Lombardi Developer -- AR
Next: Integrity Constraint Question
From: Gerhard Hellriegel on 9 Feb 2010 12:31
somewhere in the tcpunix.scr there must be a IP-address or a hostname. Has
something changed with that?

Did something change in the UNIX environment? I sometimes had problems
with a mainframe connection with that trigger-strings, like

'SESSION ESTABLISHED'

If that slightly changes, e.g. with lower- or mixed-case, the waitfor
waits the 90 sec (which is long enough) and then ends. Perhaps you could
try something with that. Under mainframes there was a way (I don't
remember exactly how) to see what was send and what came back from host.
So I could see what to waitfor. Maybe there is a way under UNIX with some
debug options to do that also?

Gerhard




On Mon, 8 Feb 2010 14:02:42 -0500, Norman Weston <nweston(a)AMGEN.COM> wrote:

>Recently I have started experiencing issues with Remote Submit. I have
>previously had not problems but the issue started about Mid Jan of this
>year.
>
>I am running a Tunnel through PuTTy which hasn't changed and I am calling
>tcipunix.scr script which also hasn't changed.
>
>It looks like the process is timing out when attempting to initiate a SAS
>session and here is the error message I get (after turning on TRACE in the
>tcipunix.scr):
>
>TRACE: Type 'sas -dmr -comamid tcp -device grlink -noterminal ';
>TRACE: Type '-nosyntaxcheck' lf;
>TRACE: Waitfor 'SESSION ESTABLISHED',
>TRACE: 90.0 seconds: nosas;
>ERROR: Cannot start remote process.
>ERROR: Cannot start remote process.
>Goodbye
>ERROR: Script file interpretation terminated due to error.
>NOTE: End of script file trace.
>ERROR: A communication subsystem partner link setup request failure has
>occurred.
>ERROR: recv call failed, lost connection with client.
>ERROR: Remote signon to SERVER cancelled.
>
>To my knowledge my PC SAS license hasn't changed, nor my permissions in
>the Unix Environment. Any thoughts on what may be causing this?
From: Norman Weston on 10 Feb 2010 18:20
So I have confirmed that this isn't specific to my ID as others are having
the same problem.

The SAS team is working on it but it is slow going. Any additional
suggestions that you folks have would be greatly appreciated. We have
eliminated the SAS License key as the issue. And again, this process was
working fine three weeks ago. Now nothing.
From: Michael Raithel on 11 Feb 2010 10:04
Dear SAS-L-ers,

Norman Weston updated us on this aggravating problem:

>
> So I have confirmed that this isn't specific to my ID as others are
> having
> the same problem.
>
> The SAS team is working on it but it is slow going. Any additional
> suggestions that you folks have would be greatly appreciated. We have
> eliminated the SAS License key as the issue. And again, this process
> was
> working fine three weeks ago. Now nothing.

Norman; BUMMER! I have been watching this conversation from the sidelines with great interest. I didn't chime in because the other respondents were hitting all of the nails that I would have pounded in. When you "went dark", yesterday afternoon, I thought maybe you had this thing beaten. Sorry to hear that you don't.

How about a review of all of the possible diagnostics/fixes/etc.? Here are my suggestions, comments, etc.--note that some would have already been suggested by other SAS-L brainiacs.

1. In your original post, it looked like you had enabled both TRACE ON and ECHO ON. Is that correct?
1.B. With TRACE ON and ECHO ON, did you get messages like this, showing that you had established a conversation between your workstation and your UNIX server:

NOTE: Remote signon to UNIX1 commencing (SAS Release whatever).

NOTE: Script file 'tcpunix.scr' entered.

NOTE: Logged onto UNIX... Starting remote SAS now.

....asked a different way: are you sure that SAS/Connect was able to successfully log you into your UNIX server? (I know it didn't start SAS, but did it get you onto the platform)?

2. From your detailed log with TRACE ON and ECHO ON, were you able to determine that the UNIX login prompts did not change? As you know, the TCPUNIX.SCR script is looking for about a half-dozen key words that tell it that UNIX is responding to it--see the section of the script around "waitfor". If your UNIX administrators introduced something new in the way of prompts, the script may not recognize it and... time out.

3. Did you establish that you can log into native UNIX and run the SAS script; thereby executing a SAS program directly on the server?

4. When you log directly into UNIX, do you arrive at the same "Norman's account root directory" (illustrated via the "pwd" command) that you do when executing SAS/Connect, with all of the same permissions?

5. Could the permissions on the SAS executable have been changed? In UNIX executable files need to be marked as executable; maybe a maintenance changed this.

6. Could the permissions of the SAS directories have been changed to exclude you or your group?

Norman, that is about all that I can think of from my snow-bound abode in the white, fluffy suburbs of Washington, DC. I hope that one or more of these prove fruitful. It will be very interesting to hear how this pans out.

Norman, best of luck to you in all your SAS endeavors!


I hope that this suggestion proves helpful now, and in the future!

Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Michael A. Raithel
"The man who wrote the book on performance"
E-mail: MichaelRaithel(a)westat.com

Author: Tuning SAS Applications in the MVS Environment

Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172

Author: The Complete Guide to SAS Indexes
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I hope everybody is doing well in the snowpocalypse of 2010! - Michael A. Raithel
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From: Michael Raithel on 11 Feb 2010 14:29
Dear SAS-L-ers,

Norman Weston posted the following:

>
> To answer your questions in order:
>
> 1. Yes, ECHO and TRACE are both on.
> 1.B. No, the error message I get is:
> TRACE: unxspawn:
> TRACE: Type '/opt/local/sas/SAS_9.1/sas -dmr -comamid tcp -device
> grlink
> -noterminal ';
> TRACE: Type '-nosyntaxcheck' lf;
> TRACE: Waitfor 'SESSION ESTABLISHED',
> TRACE: 120.0 seconds: nosas;
> ERROR: Cannot start remote process.
> ERROR: Cannot start remote process.
> Goodbye
> ERROR: Script file interpretation terminated due to error.
> NOTE: End of script file trace.
> ERROR: A communication subsystem partner link setup request failure has
> occurred.
> ERROR: recv call failed, lost connection with client.
> ERROR: Remote signon to SERVER cancelled.
>
> 2. The prompts did not change.
>
> 3. Yes. I can log into Unix and execute as SAS job and also open an
> Xwindow
> SAS session.
>
> 4. When I log into Unix, I start out at my home directory.
>
> 5. I have looked into permissions along with some help from SAS tech
> support
> and we have not found anything out of the ordinary.
>
> 6. It is possible but we haven’t seen which one has changed. Any
> ideas on
> where to look?
>
>
> I appreciate any assistance that you can offer. And any ideas that you
> guys
> have to try. thanks in advance.

Norman, thanks for answering my questions in order:-) Based on your answers--especially 1, 1.B, and 3--I don't believe that this is a SAS issue at all. I believe it is likely that you are experiencing a TCP IP issue of some kind or another. I base this on the fact that you don't have confirmation that the SAS/Connect script successfully established a conversation with your UNIX server. It must establish that conversation--the link between your workstation and the UNIX server--before it can invoke SAS. That part is pretty mechanical; it is just a script.

A quick check here with ECHO and TRACE enabled nets me this message:

NOTE: Logged onto UNIX... Starting remote SAS now.

....directly before the:

" Type '/opt/local/sas/SAS_9.1/sas -dmr -comamid tcp -device "

....statement.

If you are not seeing anything like that, it is bad news.

Hmmm... did the UNIX server ask you for a userid and password? That would be a good sign. But, the fact that you are not getting a direct message stating you are logged into the UNIX server is troubling. Maybe some systems-y TCP IP setting was changed. That would explain why multiple folks are getting this error. Time to bring your talented systems staff into the fray.

Norman, best of luck in all your SAS endeavors!


I hope that this suggestion proves helpful now, and in the future!

Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Michael A. Raithel
"The man who wrote the book on performance"
E-mail: MichaelRaithel(a)westat.com

Author: Tuning SAS Applications in the MVS Environment

Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172

Author: The Complete Guide to SAS Indexes
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Advice is like snow - the softer it falls, the longer it dwells
upon, and the deeper in sinks into the mind. - Samuel Taylor Coleridge
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From: Norman Weston on 11 Feb 2010 13:56
To answer your questions in order:

1. Yes, ECHO and TRACE are both on.
1.B. No, the error message I get is:
TRACE: unxspawn:
TRACE: Type '/opt/local/sas/SAS_9.1/sas -dmr -comamid tcp -device grlink
-noterminal ';
TRACE: Type '-nosyntaxcheck' lf;
TRACE: Waitfor 'SESSION ESTABLISHED',
TRACE: 120.0 seconds: nosas;
ERROR: Cannot start remote process.
ERROR: Cannot start remote process.
Goodbye
ERROR: Script file interpretation terminated due to error.
NOTE: End of script file trace.
ERROR: A communication subsystem partner link setup request failure has
occurred.
ERROR: recv call failed, lost connection with client.
ERROR: Remote signon to SERVER cancelled.

2. The prompts did not change.

3. Yes. I can log into Unix and execute as SAS job and also open an Xwindow
SAS session.

4. When I log into Unix, I start out at my home directory.

5. I have looked into permissions along with some help from SAS tech support
and we have not found anything out of the ordinary.

6. It is possible but we haven't seen which one has changed. Any ideas on
where to look?


I appreciate any assistance that you can offer. And any ideas that you guys
have to try. thanks in advance.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Lombardi Developer -- AR
Next: Integrity Constraint Question