topic Error Message Bypass in Administration and Deployment https://communities.sas.com/t5/Administration-and-Deployment/Error-Message-Bypass/m-p/78629#M496 <HTML><HEAD></HEAD><BODY><P>Hi All:</P><P></P><P>I'm asking this question here because this seems to be the best place for it ....</P><P></P><P>We use CONNECT to establish a session with a z/OS mainframe.&nbsp; The SAS licence on the mainframe is now in</P><P>"warning" mode (because they have not yet renewed) and is generating a pile of messages when the SAS</P><P>session is started.&nbsp; Because of this, the "SESSION ESTABLISHED" message is not received - it is on the next</P><P>screen which is never seen - and the session fails.</P><P></P><P>Does anyone know how to update the script (TSOCMSIP.SCR) to fix this error....??</P></BODY></HTML> Fri, 15 Mar 2013 17:58:32 GMT OS2Rules 2013-03-15T17:58:32Z Error Message Bypass https://communities.sas.com/t5/Administration-and-Deployment/Error-Message-Bypass/m-p/78629#M496 <HTML><HEAD></HEAD><BODY><P>Hi All:</P><P></P><P>I'm asking this question here because this seems to be the best place for it ....</P><P></P><P>We use CONNECT to establish a session with a z/OS mainframe.&nbsp; The SAS licence on the mainframe is now in</P><P>"warning" mode (because they have not yet renewed) and is generating a pile of messages when the SAS</P><P>session is started.&nbsp; Because of this, the "SESSION ESTABLISHED" message is not received - it is on the next</P><P>screen which is never seen - and the session fails.</P><P></P><P>Does anyone know how to update the script (TSOCMSIP.SCR) to fix this error....??</P></BODY></HTML> Fri, 15 Mar 2013 17:58:32 GMT https://communities.sas.com/t5/Administration-and-Deployment/Error-Message-Bypass/m-p/78629#M496 OS2Rules 2013-03-15T17:58:32Z Re: Error Message Bypass https://communities.sas.com/t5/Administration-and-Deployment/Error-Message-Bypass/m-p/78630#M497 <HTML><HEAD></HEAD><BODY><P>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.&nbsp; </P></BODY></HTML> Tue, 19 Mar 2013 03:01:03 GMT https://communities.sas.com/t5/Administration-and-Deployment/Error-Message-Bypass/m-p/78630#M497 SASKiwi 2013-03-19T03:01:03Z