Using Mr. C's suggestion to use CC you might do something like this.
[pre]
286 proc transpose data=sashelp.class;
287 var sex;
288 run;
NOTE: There were 19 observations read from the data set SASHELP.CLASS.
NOTE: The data set WORK.DATA14 has 1 observations and 20 variables.
NOTE: PROCEDURE TRANSPOSE used (Total process time):
real time 0.48 seconds
cpu time 0.00 seconds
289 %sysfunc(ifC(&syscc,%nrstr(%put NOTE: BAD CC ENDSAS?;),%nrstr(%put NOTE: All good keep going)));
NOTE: All good keep going
290
291 proc transpose data=sashelp.class;
292 var sexx;
ERROR: Variable SEXX not found.
293 run;
NOTE: The SAS System stopped processing this step because of errors.
WARNING: The data set WORK.DATA15 may be incomplete. When this step was stopped there were 0 observations and 0 variables.
NOTE: PROCEDURE TRANSPOSE used (Total process time):
real time 0.54 seconds
cpu time 0.00 seconds
294 %sysfunc(ifC(&syscc,%nrstr(%put NOTE: BAD CC ENDSAS?;),%nrstr(%put NOTE: All good keep going)));
NOTE: BAD CC ENDSAS?
[/pre]
For batch jobs a simple ENDSAS statement should be good. For a DMS session you want to keep alive you will need something else, but I'm not sure what.
A little searching at support.sas.com I find DM command WATTENTION.
http://support.sas.com/kb/38/749.html
[pre]
%sysfunc(ifC(&syscc,%nrstr(dm 'WATTENTION';),%nrstr(%put NOTE: All good keep going)));
[/pre]
WATTENTION
Message was edited by: data _null_;
Well WATTENTION does bring up the dialogue but when you select Cancel Submitted Statements it does not cancel them.
http://www.listserv.uga.edu/cgi-bin/wa?A2=ind0709C&L=sas-l&P=R17140
Message was edited by: data _null_;