Prev: PROC SQL insert issue with macro variable
Next: Hex code
From: Norman Weston on 8 Feb 2010 14:02
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?
 | 
Pages: 1
Prev: PROC SQL insert issue with macro variable
Next: Hex code