This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi Jeff,
Yes the IMS 14 enhancement will satisfy my RFE.
Our OSAM DBs have gone past 60 extents & we've been able to use IBM batch utilities or batch programs against them with no problems. We've used vanilla unload & load, HP Unload & HP Load, and HP Pointer Checker against them with no problems. Realtime is the only thing that didn't allow access to the OSAM DB with more than 60 extents. We're really glad all your unload & load tools worked against them! That's how we fixed them.
Ann
Dear Ann,
Thank you for your enhancement request for IMS. I've taken a look at the request and I have some additional questions.
With IMS 14 we've changed our internal control blocks to split the OSAM DEDB between 24 bit storage and 31 bit storage. Here is the link to the change in the Release Planning Guide: https://www-01.ibm.com/support/knowledgecenter/SSEPH2_14.1.0/com.ibm.ims14.doc.rpg/ims_v14_osam_24bit_storage_relief.htm This internal change should allow IMS to have a larger number of OSAM extents but we don't think it should reach a number close to 256, perhaps it is closer to 120 now. Would the IMS 14 enhancement satisfy your RFE?
If not can you explain why you believe IMS supports a large number of extends for OSAM? Before IMS 14 the internal logic of IMS should not allow the number of extends to go beyond 60. Unfortunately there have been defects in the code that have allowed IMS to go beyond that limit in the past. Since the limit was bypassed via a defect the results are unpredictable, sometimes a function appears to work externally but internally there are problems. Therefore I am curious of the circumstances you were able to go beyond 60 extents, if it happened because of a defect, a vendor product extending the database data sets, any information you can share.
Thank you for the information.
Best Regards,
Jeff Fontaine
JFontaine@us.ibm.com
IMS Database development