Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile
• My SAS

• Print  |
• Feedback  |
• Share

  • E-mail
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Certain diagnostic traps set on z/OS can cause SAS utility programs to fail with a 0C4 abend. These utilities include v6check, tcptest, and cleanwrk. The traceback might look something like the following:

IEF450I BPXROOT8 STEP1 - ABEND=S0C4 U0000 REASON=00000038 LOGON
+LSCX041 **** ERROR ****
+        ABEND occurred in  RELEASE(L$CHEAP),offset 000395
+        Program terminated by operating system. ABEND code = S0C4
+Calling trace:
+    Function        Line    Offset    Context
+ RELEASE(L$CHEAP)   ----    000395
+HPDESTRO(L$CHEPM)   ----    000170
+ FREEALL(L$CHEPM)   ----    00008C
+  HPUTIL(L$CHEPM)   ----    000266
BPXP018I THREAD 1BBDC3C000000000, IN PROCESS 16777847, ENDED 579 WITHOUT
BEING UNDUBBED WITH COMPLETION CODE 940C4000, AND REASON CODE 00000038.

Select the Hot Fix tab in this note to access the hot fix for this issue.

To avoid these abends, apply this hot fix and others related to diagnostic traps.

See SAS Notes 33881, "SAS/TOOLKIT® modules might receive a 0C4 abend with certain diagnostic traps enabled," 33882, "SAS® might receive a 0C4 abend while performing TCP functions," and 33883, "The SAS® object spawner might abend with a 0C4 if certain diagnostic traps are enabled" for related hot fixes.

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at: