IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

What is SO4C error in JCL


IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
chkiran2

New User


Joined: 24 Jun 2004
Posts: 24
Location: Gurgoan

PostPosted: Wed Jun 30, 2004 9:55 am
Reply with quote

What is SO4C error in JCL?
Back to top
View user's profile Send private message
bluebird

Active User


Joined: 03 Feb 2004
Posts: 127

PostPosted: Wed Jun 30, 2004 11:50 am
Reply with quote

taken from chicago's soft appl :

Code:

0C4                                                                         
  System ABEND: S0C4                                                         
                                                                             
  Description:  This ABEND is caused by a hardware detected virtual         
                address translation error, or a storage protection           
                violation. The cause of the error is indicated by the       
                reason code, as follows:                                     
                                                                             
  Reason Code                Description                                     
  -----------------------------------------------------------------------   
      4         Protection Exception: the protect key in the currently       
                executing program's PSW does not match the protect key of an
                instruction operand or a storage area that the program was   
                trying to reference.                                         
                                                                             
                References to pages protected with the PGSER PROTECT service
                or specified shared with a read-only view to the IARVSERV   
                service can also cause this exception.                       
                                                                                                           
  10        Segment translation exception: a program that was running 
            disabled for interrupts tried to reference storage while   
            the page table for that storage was paged out. To correct 
            the error, page-fix the storage before a program running   
            disabled attempts to reference it.                         
                                                                       
            Another possible cause is that a program tried to         
            reference storage that had not been obtained. To correct   
            the error, allocate the storage before attempting to       
            reference it.                                             
                                                                       
            Finally, a program running in a subspace attempted to     
            reference storage that was not accessible to the subspace 
            at the time of error. To correct the error, ensure that   
            the program running in a subspace references only the     
            storage assigned to that subspace, or storage that can be 
            referenced by all subspaces.                               
    11        Page-translation exception. This error is caused by
              one of the following:                             
                                                                 
              A program that was running disabled attempted to   
              reference storage while that storage was paged     
              out. To correct the error, page-fix the storage   
              before a program running disabled attempts to     
              reference it.                                     
                                                                 
              A program attempted to reference storage that had 
              not been obtained. To correct the error, allocate 
              the storage before attempting to reference it.     
                                                                 
              A program running in a subspace attempted to       
              reference storage that was not accessible to the   
              subspace at the time of error. To correct the     
              error, ensure that the program running in a subspace     
              references only the storage assigned to   that subspace, or storage that can be referenced 
 by all subspaces.                                                                         

                                                                           
     12C        SMS abend. The reason code is X'12C'.                       
                                                                           
  User Action:  Correct the program logic error that generated the invalid 
                address or storage reference. When analyzing the dump,     
                remember that the PSW saved when an 0C4 abend occurs may   
                point at the failing instruction or it may point at the     
                next instruction after the failing instruction.             
                                                                           
                Check to ensure that your program is obtaining, using, and 
                freeing storage properly.  Moving data to a zero address   
                or to an address less than 512 (decimal) is a very         
                frequent cause of this abend.                               
                                                                           
              COBOL: Invalid address was referenced due to subscript error   
                     or bad parameter passed                                 
                     In group move, receiving record variable length         
                        defined incorrectly                                 
                     Tried moving variable length record that was larger     
                        than target field size                               
                     Tried to read or write a file which was not open       
                     Used DD DUMMY with logic that moves high values to     
                      FD                                                     
                     Tried to call within COBOL SORT I/O procedure           
                     Tried to "goback" in the SORT output procedure         
                                                                             


I would go for the file not open check first.
Back to top
View user's profile Send private message
sprasannapathy

New User


Joined: 04 Jan 2008
Posts: 42
Location: india

PostPosted: Tue Dec 02, 2008 12:25 pm
Reply with quote

Hi,

Could any one explain how to handle if the reason code is 11 (Page Translation Exception) for VSAM file. The VSAM file is KSDS.

Thanks
Prasannaa S
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Tue Dec 02, 2008 12:36 pm
Reply with quote

S04C or S0C4 ?

Please post the error statements and codes.
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Tue Dec 02, 2008 3:29 pm
Reply with quote

Hi,

I believe it's S0C4, thread is qiute old, but reopened..hopefully Prasannaa would post the requested info.
Back to top
View user's profile Send private message
TONYTAPES

New User


Joined: 03 Dec 2008
Posts: 4
Location: new jersey

PostPosted: Fri Dec 05, 2008 10:26 pm
Reply with quote

A old system programmers joke

what is a soc4 --keep your feet warm icon_lol.gif
Back to top
View user's profile Send private message
sprasannapathy

New User


Joined: 04 Jan 2008
Posts: 42
Location: india

PostPosted: Mon Dec 08, 2008 7:37 pm
Reply with quote

Hi,

Sorry for my delay.

Please find the job log message below.

Code:
IEA995I SYMPTOM DUMP OUTPUT  568                           
 SYSTEM COMPLETION CODE=0C4  REASON CODE=00000011           
  TIME=23.30.33  SEQ=27630  CPU=0000  ASID=01FC             
  PSW AT TIME OF ERROR  070C0000   80C199D4  ILC 4  INTC 11 
    NO ACTIVE MODULE FOUND                                   
    NAME=UNKNOWN                                             
    DATA AT PSW  00C199CE - 80084110  6418BD17  20354770     
    GR 0: 00000000_00000448   1: 00000000_00C19A40           
       2: 00000000_000DBFCC   3: 00000000_00FD9A40           
       4: 00000000_009FF050   5: 00000000_009FD5F0           
       6: 00000000_00C19628   7: 00000000_00F8BD80           
       8: 00000000_0099CBB8   9: 00000000_105EB800           
       A: 00000000_00C330A8   B: 00000000_7F59B5B8           
       C: 00000000_00000000   D: 00000000_00000004           
       E: 00000000_40C1950C   F: 00000010_00C19628           
  END OF SYMPTOM DUMP                                       
 IEF450I LFDC69 EXPORT2 - ABEND=S0C4 U0000 REASON=00000011  5
         TIME=23.30.41                                       
 -LFDC69   EXPORT2           *S0C4    992    684 551177    .0

Message from Dump master

Code:
***** The abend occurred while processing a request for system service  *****
***** The following is the status of the program that made the request  *****
                                                                             
.
.
.
.
Last instruction was 0A14 - SVC   20  (CLOSE) 
.
.
.

This step is an export step that exports only the catalogue information of the VSAM dataset to an ordinary PS file.
The DCB parameter coded for the ordinary PS out put file is
Code:
//             DCB=(DP.DSCB,BUFNO=20),

I read that the Logical record length (LRECL) and the record format (RECFM) will be automatically cared by the system while exporting the VSAM dataset. Therefore, I thought it would be because of DP.DSCB. I tried a test run by removing DP.DSCB in DCB parameter. However, the job got abended again with S0c4 error. Next I tried by removing the BUFNO=20 and having DP.DSCB in the DCB parameter. Goodness the job ended fine.

When I did looked in to the output dataset it contains only the catalogue information that is only two lines of information. I doubt this might have been happened because of huge amount of buffer allocation.

Kindly explain me what would have happened because of buffer allocation and/or this might be because of any other reasons.

I am thankful to Mainframe forum that helped me in many ways and all people who helped me a lot in clarifying my queries.

Thanks
Prasannaa S

Edited: Please use BBcode when You post some code, that's rather readable...Anuj
Back to top
View user's profile Send private message
Bill Dennis

Active Member


Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA

PostPosted: Mon Dec 08, 2008 9:17 pm
Reply with quote

The LRECL and RECFM will be the same as DP.DSCB unless the program specifies them.

1) Maybe you have two long records with all the data strung together and the wrong LRECL?

2) Maybe you OPEN/CLOSE the file multiple times and so only the final records written will be there.
Back to top
View user's profile Send private message
sprasannapathy

New User


Joined: 04 Jan 2008
Posts: 42
Location: india

PostPosted: Tue Dec 09, 2008 8:54 pm
Reply with quote

Thanks
Prasannaa S
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> ABENDS & Debugging

 


Similar Topics
Topic Forum Replies
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts Error while running web tool kit REXX... CLIST & REXX 5
No new posts Getting Error while trying to establi... DB2 3
Search our Forums:

Back to Top