This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
Meant to say AVGREC=M with 1000 primary is used to represent 1 billion records.
AVGREC={U,K,M) which represents units, units in thousands, or units in millions. Well, what are we to do when records are created in billions? The purpose of AVGREC was to make setting allocation requirements easier based on record creation estimates. I would like to see that trend continue. So, what should be done as we begin to grow into the billions of records? For now, AVGREC=1000 is used to represent a billion. Just trying to prepare us for the future.
Hello there,
Can we know which type of data sets you need this support? VSAM or non-VSAM (physical sequential data sets) ?
Why can't you use CYL or M (Mega-byte) ?
Please let us know.
Thank you!
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - DFSMS SMS
Operating system - IBM z/OS
Source - Client
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - General
Operating system - IBM z/OS
Source - Client
This looks like a similar request in RFE: http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=92670
Add additional AVGREC sizes to Space definitions in JCL and IDCAMS
This looks like a similar request in RFE: http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=92670