Under exceptional circumstances, a SAS session might encounter an error that results in the session exiting unexpectedly. However, SAS gives no indication to the operating system that there was a problem, and it exits with a return code of 0.
At the console, or in a SAS log, you might see a message similar to the following:
SAS WTABORT (Line Mode Process) The SAS System has detected an abort
condition. An Exception occurred during wthtrm().
Please Contact Technical Support.
Tasks[MAIN ] [WAITING ] pri[ 5] reb[62C4C540] WC[0] WN[1]
[IDLETASK] [READY ] pri[ 9] reb[62C4C540]
[EVENTTSK] [WAITING ] pri[ 0] reb[62C4C540] WC[0] WN[1]
[sasxkern] [WAITING ] pri[ 3] reb[62C4C540] WC[0] WN[1]
[Session ] [WAITING ] pri[ 3] reb[6018CCC0] WC[0] WN[1]
[TKSRV ] [WAITING ] pri[ 3] reb[6018D360] WC[0] WN[1]
[Line Mod] [RUNNING ] pri[ 7] reb[6018DE80]
Traceback
No Traceback Available
NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414
NOTE: The SAS System used:
real time 8.07 seconds
cpu time 0.08 seconds
You might also observe this message:
ERROR: Floating Point Zero Divide.
For one example of a possible cause for the WTABORT message, see SAS Note 68472, "Disconnecting from an Oracle database might result in a WTABORT error and the message 'ERROR: Floating Point Zero Divide.'"
Contact SAS Technical Support for help with diagnosing the reason for the WTABORT message.