03-15-2013 01:58 PM
I'm asking this question here because this seems to be the best place for it ....
We use CONNECT to establish a session with a z/OS mainframe. The SAS licence on the mainframe is now in
"warning" mode (because they have not yet renewed) and is generating a pile of messages when the SAS
session is started. Because of this, the "SESSION ESTABLISHED" message is not received - it is on the next
screen which is never seen - and the session fails.
Does anyone know how to update the script (TSOCMSIP.SCR) to fix this error....??
03-18-2013 11:01 PM
I suggest you refer to the CONNECT documentation for the scripting statements. I think there is a WAITFOR type statement that you will need to modify to add a condition to trap the text 'WARNING', then you can send a "clear screen" to get to the SESSION ESTABLISHED message. You can also add TRACE and ECHO statements to your script to help you figure out what changes to make.