SYSTEM COMPLETION CODE=0C4 REASON CODE=00000004 NAME=UNKNOWN running TMSINIT

book

Article ID: 126300

calendar_today

Updated On:

Products

CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options

Issue/Introduction

TMSINIT abended at IPL with Abend S0C4-4

SYSTEM COMPLETION CODE=0C4  REASON CODE=00000004           
 TIME=01.08.37  SEQ=00010  CPU=0000  ASID=0083             
 PSW AT TIME OF ERROR  070C2000   A58DC31C  ILC 4  INTC 04 
   NO ACTIVE MODULE FOUND                                  
   NAME=UNKNOWN                                            
   DATA AT PSW  258DC316 - C31CBE0F  A00012EE  4780C326    
   GR 0: 00000000   1: 00CAB208                            
      2: 00FBC7B8   3: 258B61C0                            
      4: 00CAB7E0   5: A58DC178                            
      6: 00000040   7: 258B6FFF                            
      8: 258B5FC8   9: 00CAB208                            
      A: 258C5008   B: 7F7371B0                            
      C: A58DC000   D: 00000000                            
      E: 00CAB22C   F: A58C5000                            
 END OF SYMPTOM DUMP    


No DUMP is available for this abend as the TMSINIT procedure does not have a SYSUDUMP DD statement.


                                 

Environment

Release:
Component: 1

Resolution

There is a reported problem with Abend S0C4-4 in module UNKNOWN, which is caused by ETF/A from Eberhard Klemens Co.
The S0C4 Abend occurred at the very end of TMSINIT processing, when CA 1 actually was already activated successfully, confirmed by message
----->  IEFTMS1 CA 1(TMS) IS  ACTIVE 14.0
In TMS REPORT-00 

If there is no dump available perform the following steps to verify if the abend is related to this product: 

- Look at R12 from the symptom dump and browse the address using TSO ISRDDN for example and check if it belongs to the ETF/A product
- Issue SRCHFOR X'BE0FA000' in the ETF/A loadlib and check if you can find the failing address causing the S0C4-4 Abend

If the address at R12 belongs to ETF/A and if you find the failing instruction in the ETF/A loadlib report the problem to the vendor.

If the address at R12 does not belong to the ETF/A product, then set a SLIP for the S0C4 abend and reproduce the problem.
Open a CA 1 Case in Support Online and provide the SVC Dump for review.