Providing software solutions since 1976

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

• 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

If certain diagnostic traps are enabled on z/OS, the SAS object spawner might abend with a 0C4. 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.

A hot fix is planned for this issue.

To circumvent this abend, apply the associated hot fix.

See also SAS Notes 33879, "SAS® utilities abend when some diagnostic traps are set on z/OS," 33881, "SAS/TOOLKIT® modules might receive a 0C4 abend with certain diagnostic traps enabled," and 33882, "SAS® might receive a 0C4 abend while performing TCP functions" for related hot fixes.

Operating System and Release Information