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.
Using the CustomPac ISPF Dialogs, we previously had the ability to change the dataset allocations for PDS/ZFS datasets shipped via ServerPac to allow for local growth, removal of secondaries & increase of dir blocks. As zOS 2.5 is now shipped as a Portable Software Instance (PSI) and is installed via zOSMF Software Management, the Deployment Operation currently does not have the capability of changing these values. Not having this capability means we have to go back to manual actions (JCL) to realign the dsn sizings after completion of the deployment. Not doing this means later actions we take for local mods mean datasets B37, run of of dir blocks or end up with secondaries when a dataset ends up in linklist (against IBM recommendations).
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Looking back on previous CPAC zOS installs we we tended to resize:-
SYS1.SISPLOAD required for the SISPLPA>SISPLOAD usermod ISPMOVE1 to ensure enough space. https://www.ibm.com/docs/en/zos/2.3.0?topic=lpa-moving-load-modules
SYS1.SHASMIG looks like a carry forward from some SMPE APPLY space issue with V2R1. Looks like PSWI is large enough.
SYS1.SCSFMOD0 ditto previous V2R1 apply issue.
SYS1.SERBLINK ditto previous V2R1 apply issue.
SYS1.SEZATCP we have this in linklist so needs zero secondary
SYS1.SORTLPA we have this in linklist so needs zero secondary
We also need to add HFNT14J fmid to the 2.5 build. During the CPAC build of 2.4 we made considerably larger a number of datasets AND ZFS's to accomodate the additional FMID. Details to follow