MVS Link Error - "MISSING FILE NAME+" Urgent!

[gordonme]

Hello,
Having a catastrophe due to suddenly being able to connect to MVS through a script. I'm using SAS/CONNECT, here is my log. Any suggestions or ideas are much appreciated, in a massive timecrunch to get this resolved. This has worked fine for a long time and is just now breaking...

410 filename rlink '\\path\tcptso_copy.scr';
411 %let mvs=xx.xx.xx.x;
412 options remote=mvs comamid=tcp;
413 signon;
NOTE: Remote signon to MVS commencing (SAS Release 9.01.01M3P021605).
NOTE: Start of script file trace.
TRACE: Echo on;
TRACE: Log 'NOTE: Script file 'tcptso.scr' entered.';
NOTE: Script file 'tcptso.scr' entered.
TRACE: If not TCP then goto notcp;
TRACE: If signoff then goto signoff;
TRACE: Waitfor 'ACF82003 ACF2, ENTER LOGON ID -',
TRACE: 45.0 seconds: noinit;

ACF82003 ACF2, ENTER LOGON ID -
TRACE: Type 'user' lf;
TRACE: Waitfor 'ENTER PASSWORD',
TRACE: 60.0 seconds: nolog;

ACF82004 ACF2, ENTER PASSWORD
TRACE: Type 'pass' lf;
TRACE: Type lf;
TRACE: Waitfor 'READY',
TRACE: 'CURRENTLY LOGGED ON': dup_log,
TRACE: 'NOT VALID': nouser,
TRACE: 'PASSWORD INVALID': nopass,
TRACE: 'RECONNECT SUCCESS': recon,
TRACE: 120.0 seconds: nostrt;
-
XXXXXXXX:::::::::NNNNNNNN:::::::::ZZZZZZZZ:::::::::MMMMMMMM:::::::::ACF82000 ACF2, LOGON IN
PROGRESS
ACF01137 user LAST SYSTEM ACCESS 12.32-12/01/09 FROM TCP0T336
user LOGON IN PROGRESS AT 13:39:39 ON DECEMBER 1, 2009
------------------------------------------------------------------------------
You are logged on to TSO/E on CPU1 at Company.
------------------------------------------------------------------------------
READY
TRACE: Waitfor 1.0 second;
TRACE: strt_sas:
TRACE: Log 'NOTE: Logged on to TSO.... Starting remote SAS now.';
NOTE: Logged on to TSO.... Starting remote SAS now.
TRACE: Type 'sas o('dmr,comamid=TCP,tcpipprf=ssd.tcpip.vercur, ';
TRACE: Type 'noterminal,no$syntaxcheck') ';
TRACE: Type 'work('4000,4000')' lf;
TRACE: Waitfor 'SESSION ESTABLISHED',
TRACE: 30.0 seconds: nosas;

MISSING FILE NAME+
READY
TRACE: nosas:
TRACE: Log 'ERROR: Did not get SAS software startup messages.';
ERROR: Did not get SAS software startup messages.
TRACE: Abort;
NOTE: End of script file trace.
ERROR: A communication subsystem partner link setup request failure has occurred.
ERROR: Communication script processing aborted.
ERROR: Remote signon to MVS cancelled.
414
415 rsubmit;
ERROR: A link must be established by executing the SIGNON command before you can communicate
with MVS.
ERROR: Remote submit to MVS cancelled.
416 signoff;
NOTE: A link to MVS does not exist. SIGNOFF is not necessary.
417 run;


Thank you SO MUCH for any guidance