Portal | IBM Manuals | Downloads | Products | Refer | Info | Programs | JCLs | Forum Rules*| Site Map | Mainframe CD 
IBMMAINFRAMES.com - IBM Mainframe Support Forums Index
 
Register
 
IBMMAINFRAMES.com - IBM Mainframe Support Forums Index FAQ Search Memberlist Usergroups Profile Log in to check your private messages Log in
 
What is SO4C error in JCL

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL
Author Message
chkiran2

New User


Joined: 24 Jun 2004
Posts: 25
Location: Gurgoan

PostPosted: Wed Jun 30, 2004 9:55 am    Post subject: What is SO4C error in JCL
Reply with quote

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

Specialist


Joined: 03 Feb 2004
Posts: 144

PostPosted: Wed Jun 30, 2004 11:50 am    Post subject:
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: 7
Location: india

PostPosted: Tue Dec 02, 2008 12:25 pm    Post subject:
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: 3561
Location: Brussels once more ...

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

S04C or S0C4 ?

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

Global Moderator


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

PostPosted: Tue Dec 02, 2008 3:29 pm    Post subject:
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
Display posts from previous:   
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL All times are GMT + 6 Hours
Page 1 of 1