View previous topic :: View next topic
|
Author |
Message |
sreekarreddyg
New User
Joined: 22 Apr 2006 Posts: 2
|
|
|
|
Hi All,
I have a VSAM DB where its reaching 3.7 GB regularly.Hence we want to change it to OSAM so that 8 GB of space is available and prevent DB crash. We are using IMS batch &online programs to access the DB.
I would like to know
1)how complex is the process of converting VSAM to OSAM DB
2)does the existing programs needs to be changed so that they are compatible to OSAM
3)does the existing jcl's needs to be changed so that they are compatible to OSAM
I am reading about OSAM for 1st time and any information would be greatly helpful.
Thanks,Sreekar. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
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 |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
Back to top |
|
|
|