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

What is OSAM file?


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

New User


Joined: 19 Mar 2008
Posts: 12
Location: India

PostPosted: Fri Mar 28, 2008 12:04 pm
Reply with quote

Hi can any one Explain what is OSAM file. Im just want to know about it out of my curiosity i have came across this, but it not a part of any of my requirements.
Back to top
View user's profile Send private message
Gnanas N

Active Member


Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India

PostPosted: Fri Mar 28, 2008 12:15 pm
Reply with quote

Karthick,

OSAM stands for Overflow Sequential Access Method.

Converting VSAM databases to OSAM increases the addressing capability twice that of VSAM and requires no change in current application program and PSB with minor change in DBD.

It can support addressing or indexing capacity up tp 8 GB per partition where as VSAM is limited to 4GB.

So, OSAM is one of the large datebase alternatives.

At right now I am working on this for IMS databases.
Back to top
View user's profile Send private message
karthick Ramesh

New User


Joined: 19 Mar 2008
Posts: 12
Location: India

PostPosted: Fri Mar 28, 2008 12:26 pm
Reply with quote

Thank you Gnanas!!!
Back to top
View user's profile Send private message
expat

Global Moderator


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

PostPosted: Fri Mar 28, 2008 12:40 pm
Reply with quote

Quote:
where as VSAM is limited to 4GB.

Using SMS Extended ability the 4GB limit on VSAM was removed with (I think) z/OS 1.2 or 1.3
Back to top
View user's profile Send private message
Gnanas N

Active Member


Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India

PostPosted: Fri Mar 28, 2008 4:39 pm
Reply with quote

Yes, Expat.

With the release of DFSMS/MVS 1.3, if VSAM data set is SMS-managed and defined as extended format(to use EA), the new size limit for an EA data set is determined by either
1. multiplying the CI size by 4 GB
2. multiplying the volume size by 59


The original limit was based on a 4-byte Relative Byte Address (RBA), but the new system uses an 8-byte RBA that creates a new limit of 128TB.
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 Compare 2 files and retrive records f... DFSORT/ICETOOL 0
No new posts FTP VB File from Mainframe retaining ... JCL & VSAM 8
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 Extracting Variable decimal numbers f... DFSORT/ICETOOL 17
Search our Forums:

Back to Top