Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Job Abends with a file status code of 24 when writing VSAM

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
madhav_in

New User


Joined: 21 Nov 2006
Posts: 12
Location: chennai

PostPosted: Tue Jul 29, 2008 1:08 pm    Post subject: Job Abends with a file status code of 24 when writing VSAM
Reply with quote

Hi,
I have been getting this abend for quite sometime in the batch processing. The job uses various VSAM files in the I/O mode and sometimes the job abends when trying to write into a particular file with a return code of 24. I checked the forum about this error and found that increasing the secondary extent could do the job. But what baffles me is that , Since the files are I/O files , I need to restore them from backups before restarting the job. Now when I restore these I/O files ( without making anyother changes ) and restart, the job runs fine without any problem. Is there a logical reason to this type of an abend or is it just some environment issue ?
Back to top
View user's profile Send private message

dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6967
Location: porcelain throne

PostPosted: Tue Jul 29, 2008 1:14 pm    Post subject:
Reply with quote

When you restore them, haven't you effectively REORG'd them?
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Tue Jul 29, 2008 1:29 pm    Post subject:
Reply with quote

dbzTHEdinosauer wrote:
When you restore them, haven't you effectively REORG'd them?

Absolutely correct. You have reorganised the file and released any unusable space to be usable again.

Have a word with your JCLMS (Prod support) to schedule a periodic reorg and also to review the space allocations of the file.
Back to top
View user's profile Send private message
madhav_in

New User


Joined: 21 Nov 2006
Posts: 12
Location: chennai

PostPosted: Tue Jul 29, 2008 6:40 pm    Post subject: Reply to: Job Abends with a file status code of 24 when writ
Reply with quote

Thanks a lot for your reply icon_smile.gif, I dont understand what this REORG means ? How does restoring the file cause this REORG, I am just going to copy the backup file to the VSAM file, this causes REORG ? Is there a way to tackle this issue from my side ?
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Tue Jul 29, 2008 6:48 pm    Post subject:
Reply with quote

A good intro to VSAM

Have a read, it is well worth the effort.

But ............. a restore from backup is a little like an initial load of the VSAM cluster. Every record is in its correct place with no wasted internal space. Once a file is written to and has CI/CA splits then some space may be 'Free' but is unusable.
Back to top
View user's profile Send private message
madhav_in

New User


Joined: 21 Nov 2006
Posts: 12
Location: chennai

PostPosted: Tue Jul 29, 2008 9:26 pm    Post subject: Reply to: Job Abends with a file status code of 24 when writ
Reply with quote

Hi Expat I will surely go through the IBM redbooks link that you had mentioned to understand why this happens. So as u said when i copy from a backup, it is like an initial load and that any wasted space will be utilized. Then will having an IDCAMS step copying the backup file to the original VSAM file before the program runs, do the trick of solving the problem ?
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Wed Jul 30, 2008 11:32 am    Post subject:
Reply with quote

It will reorg the cluster, but as nI said about 8 posts ago, have a word with the people who maintain the cluster and get the space allocations changed to allow for contingency.
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 -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Testing rerad cursor for status with ... John F Dutcher DB2 7 Fri May 19, 2017 9:35 pm
No new posts Job failing with USER = 4093 REASON C... Pradeepa S ABENDS & Debugging 1 Wed May 17, 2017 3:35 pm
No new posts Converting Variable block file to Fix... bhavana yalavarthi DFSORT/ICETOOL 11 Tue May 16, 2017 2:20 pm
No new posts Getting error while opening a variabl... apandey1 COBOL Programming 5 Fri May 05, 2017 12:22 pm
No new posts Issue with NDM process to transmit ES... chetanambi All Other Mainframe Topics 6 Wed May 03, 2017 10:52 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us