This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
IFS streamfiles need additional OIR-like attributes
IFS streamfiles have a number of attributes, many seem IBM i (OS/400) specific, visible via WRKLNK option 8=Display attributes, and can be specified or changed via the CHGATR command ATR parameter, such as: *CCSID, *ALWCKPWRT, *USECOUNT, *DISKSTGOPT, *MAINSTGOPT, *CRTOBJSCAN, *SCAN, *ALWSAV, *RSTDRNMUNL, *CRTOBJAUD, etc.
In the QSYS.LIB file system, library resident objects have additional properties or attributes maintained in the *OIR space of the containing library, visible with DSPOBJD ... DETAIL(*SERVICE) such as:
Object control level, Licensed program product PTF number, APAR ID Text descr,iption
that are not available with IFS streamfiles.
It would also be useful to have a new "*SRCSTMF" attribute to store the "source" IFS path for any IFS streamfile created (compiled) from another source stream file, e.g. using the IBM XL/C compiler, or GCC, etc..
IBM now distributes thousands of streamfiles as part of various LPPs, e.g. 5770-DG1, and 5733-OPS/, How can customers identify and keep track of which *STMFs have been altered or replaced by what PTFs or APARs? (And how can the IBM PTF install process keep proper track of this?)
In 5733-OPS, when installing PTFs, apparently a "manifest" file is created and used by the PTF install (exit) program(s) to manage what needs to be done. But if the manifest file is damaged or deleted, this causes all sorts of problems that prevent PTFs from installing properly. And the customer must then delete the entire 5733-OPS LPP (or at least one or more of its optional parts) and then re-install them again to fix this.
As more parts of the OS depend on components (stream files) in IFS directories,,a more robust mechanism is needed to make PTFs of IFS *STMFs more reliable, and comparable to handling of objects in the QSYS.LIB file system.
Also, as IBM promotes the use of GCC and git etc. to compile open source code to run in PASE, the "Object Control Level" would be very useful to identify the "version tag" from git or any other Source Control tool.
Do not place IBM confidential, company confidential, or personal information into any field.