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

Is there any option for VSAM file to free the space .


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
nkreddy5

New User


Joined: 06 May 2008
Posts: 7
Location: BANGALORE

PostPosted: Thu Nov 13, 2008 1:28 am
Reply with quote

in idcams step..my input file has 2 gb records..so my output file is vsam file which has cataloged in production with 4 gb space..is there any parameter can we code to free the space after idcams utility run as it will occupy only 2 gb space,rest 2 gb space will be empty..

in normal files we can give rlse or free but vsam i dont know..can you please help me to get thi info if above scenario is poossible.

Thanks,
Karthik
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Thu Nov 13, 2008 1:38 am
Reply with quote

Why is the file created with 4 GB of space if you're only using 2 GB? Change the IDCAMS DEFINE would be my first choice, although there's a lot to be understood still -- could the file have been defined as 4 GB to allow for expansion? What's the usage pattern (read only after load, inserts throughout the file, inserts only at the end)? What does the LISTCAT look like? Is there free space specified?

In general, unless you unload, delete, define, and reload the VSAM file you're not going to decrease the space used. Once a VSAM file is defined, it may get bigger but you can't make it get smaller without redefining it.
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10873
Location: italy

PostPosted: Thu Nov 13, 2008 2:45 am
Reply with quote

what is the usage pattern for the dataset ??
when defining a dataset there are many things to be taken into account
but the most important for vsam at least is the insert pattern,
and the distribution of the keys
there are insert key patterns that cause a ci split almost at every insert

but then even with lots of inserts with clustered keys it is sometimes better
to defines the ci free space percentage as 0

the first insert of a group of keys will cause a CI split and for a while there will be no more CI splits,

lots od dasd space can be saved in this way
but the issue must be closely watched and tuned
Back to top
View user's profile Send private message
expat

Global Moderator


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

PostPosted: Mon Nov 17, 2008 3:01 pm
Reply with quote

VSAM extended facilites allows for the release of allocated and unused space.

Please speak nicely to your storage people to help you
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 -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts FTP VB File from Mainframe retaining ... JCL & VSAM 4
No new posts Extract the file name from another fi... DFSORT/ICETOOL 6
No new posts How to split large record length file... DFSORT/ICETOOL 10
No new posts Replace each space in cobol string wi... COBOL Programming 3
No new posts Extracting Variable decimal numbers f... DFSORT/ICETOOL 17
Search our Forums:

Back to Top