68859 - A "SAS WTABORT" error occurs, and a SAS® session ends unexpectedly, but the SYSCC code is 0

Problem Note 68859: A "SAS WTABORT" error occurs, and a SAS® session ends unexpectedly, but the SYSCC code is 0

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.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
Product Family	Product	System	Reported	Fixed*	Reported	Fixed*
SAS System	Base SAS	z/OS	9.4_M6		9.4 TS1M6
		z/OS 64-bit	9.4_M6		9.4 TS1M6
		Microsoft® Windows® for x64	9.4_M6		9.4 TS1M6
		Microsoft Windows 8 Enterprise 32-bit	9.4_M6		9.4 TS1M6
		Microsoft Windows 8 Enterprise x64	9.4_M6		9.4 TS1M6
		Microsoft Windows 8 Pro 32-bit	9.4_M6		9.4 TS1M6
		Microsoft Windows 8 Pro x64	9.4_M6		9.4 TS1M6
		Microsoft Windows 8.1 Enterprise 32-bit	9.4_M6		9.4 TS1M6
		Microsoft Windows 8.1 Enterprise x64	9.4_M6		9.4 TS1M6
		Microsoft Windows 8.1 Pro 32-bit	9.4_M6		9.4 TS1M6
		Microsoft Windows 8.1 Pro x64	9.4_M6		9.4 TS1M6
		Microsoft Windows 10	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2008	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2008 R2	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2008 for x64	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2012 Datacenter	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2012 R2 Datacenter	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2012 R2 Std	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2012 Std	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2016	9.4_M6		9.4 TS1M6
		Microsoft Windows Server 2019	9.4_M6		9.4 TS1M6
		Windows 7 Enterprise 32 bit	9.4_M6		9.4 TS1M6
		Windows 7 Enterprise x64	9.4_M6		9.4 TS1M6
		Windows 7 Home Premium 32 bit	9.4_M6		9.4 TS1M6
		Windows 7 Home Premium x64	9.4_M6		9.4 TS1M6
		Windows 7 Professional 32 bit	9.4_M6		9.4 TS1M6
		Windows 7 Professional x64	9.4_M6		9.4 TS1M6
		Windows 7 Ultimate 32 bit	9.4_M6		9.4 TS1M6
		Windows 7 Ultimate x64	9.4_M6		9.4 TS1M6
		64-bit Enabled AIX	9.4_M6		9.4 TS1M6
		64-bit Enabled Solaris	9.4_M6		9.4 TS1M6
		HP-UX IPF	9.4_M6		9.4 TS1M6
		Linux for x64	9.4_M6		9.4 TS1M6
		Solaris for x64	9.4_M6		9.4 TS1M6

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

Type:	Problem Note
Priority:	high

Date Modified:	2022-03-28 09:52:17
Date Created:	2022-02-01 04:18:37