Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
S0C4 while initializing..

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming
View previous topic :: :: View next topic  
Author Message
janusman

New User


Joined: 09 Sep 2008
Posts: 31
Location: India

PostPosted: Sat Feb 27, 2010 2:28 am    Post subject: S0C4 while initializing..
Reply with quote

Hi

I am encountering a S0C4 abend when I initialize a record (group record).
The file is opened successfully. The program which has been in the system for a couple of years now - and ran successfully - now gives an abend when it is trying to initialize.

Here is the Dump I can see in spool.


Code:
+AB400A      ===== ABEND-AID =====  215                               
   REPORT WRITTEN TO: CNCSYS.ABENDAID.SHARED.REPORT                   
   REPORT NUMBER: 0188295                                             
   JOB-THDXXXX# STEP-PS010R                                           
   LE COND CODE=CEE3204S / EXPECTED COMP CODE=S0C4                   
     ACCESS YOUR ABEND-AID REPORTS BY EXECUTING SYSTEM               
     COMMAND "AAHOTKEY" FROM ANYWHERE IN ISPF.                       
+LEAID110 LE-AID IS ISSUING U4039-8 ABEND                             
$HASP375 THDXXXX# ESTIMATED  LINES EXCEEDED                           
$HASP375 THDXXXX# ESTIMATED KBYTES EXCEEDED                           
$HASP375 THDXXXX# ESTIMATE EXCEEDED BY             500,000  LINES     
IEA995I SYMPTOM DUMP OUTPUT  839                                     
  USER COMPLETION CODE=4039 REASON CODE=00000008                     
 TIME=14.54.59  SEQ=24915  CPU=0000  ASID=0188                       
 PSW AT TIME OF ERROR  078D1000   9C0A9756  ILC 2  INTC 0D           
   ACTIVE LOAD MODULE           ADDRESS=1C0A8878  OFFSET=00000EDE     
   NAME=#XAALE31                                                     
   DATA AT PSW  1C0A9750 - 00181610  0A0D4100  00840A3C               
   AR/GR 0: 00000000/00000000_84000000   1: 00000000/00000000_84000FC7
         2: 00000000/00000000_0002BCD0   3: 00000000/00000000_000071C8
         4: 00000000/00000000_0002B89C   5: 00000000/00000000_1C0A9877
         6: 00000000/00000000_0002E968   7: 00000000/00000000_0002EA58
         8: 00000000/00000000_86250DB6   9: 00000000/00000000_00000000
         A: 00000000/00000000_0002E8F4   B: 00000000/00000000_1C0A8878
         C: 00000000/00000000_00025B40   D: 00000000/00000000_0002E610
         E: 80C8E890/00000000_9C0A94A0   F: 00000000/00000010_00000008
 END OF SYMPTOM DUMP                                                 
IEF450I THDXXXX# PS010R - ABEND=S0C4 U0000 REASON=00000004


The abend aid shows exactly the same line where it abends when I Xpedited the code. The file is not a VSAM - its a normal qsam file with Fixed block records.

Any ideas?
Back to top
View user's profile Send private message

dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sat Feb 27, 2010 3:21 am    Post subject:
Reply with quote

Hello,

Was the file successfully OPENed?

Has it already been CLOSEd?

Did the first initialize fail or had the program been running a while?

Has this code ever worked or is this something new (i.e. were changes in process)?
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8154
Location: East Dubuque, Illinois, USA

PostPosted: Sat Feb 27, 2010 3:57 am    Post subject:
Reply with quote

Quote:
I am encountering a S0C4 abend when I initialize a record (group record).
The file is opened successfully. The program which has been in the system for a couple of years now - and ran successfully - now gives an abend when it is trying to initialize.
How do you know the file opened successfully -- do you have the file status code for the OPEN statement? Is the record you are initializing the file 01 entry -- and if so, why since it is initialized by the system before you can do anything to it? If the program was running and now is not, then something changed: program, JCL, file, or something. You need to isolate what changed and that will most likely tell you the cause of the S0C4.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Getting S0C4 while running COBOL Data... kalakuntlavenkat COBOL Programming 4 Thu Feb 26, 2015 8:48 pm
No new posts Getting S0C4 when Writing a Record thesumitk COBOL Programming 7 Wed Feb 04, 2015 3:26 pm
No new posts S0C4 error, ISPF processor ended abno... Raghu navaikulam ABENDS & Debugging 5 Wed Dec 17, 2014 2:55 pm
No new posts S0C4 Abend in Stored Procedure rahuindo DB2 7 Tue Sep 16, 2014 7:04 pm
No new posts S0C4 reason code 10, gets when more c... bhushan.shete PL/I & Assembler 2 Mon Jul 07, 2014 4:36 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us