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
Introduce "generic" full & easily machine parsable output for AIX commands
Command part of "list" category (lsvg, lslv, lssyscfg, lsdev, lsattr, ....) provide the entry point to capture configuration of AIX OS. Allowing all theses kind of commands to provide "full & easily machine parsable output" using flag (like already do "lsattr -O") will greatly enhance capability to interact with system. All automated "configuration collection" will be more powerful (shell script, Ansible, ... ) and POWER platform will so be easily deployed, maintained, .... thru automata.
Proposal : Search for a "not already used" option and reserve it as "generic AIX command standard option" for any new "ls*" command that may be developed later on AIX (same as -v is for version and -h is for help). Having one generic option that "work everywhere" (ie, avoid one different option per command) will provide more ease of use. This new option could be "--csv" if easily possible to use "double dash" options within AIX current commands. Also use "--delim" in order to specify the delimiter to be used (personally I like semi-colon as it is never part of "value" due to its specific shell meaning, but quite sure other people have other preferred delimiter). Add of the header in first line is mandatory in order to avoid any "foreign data" to be parsed in case of command evolution. A good direction will be to use "#" as first char in order to identify the header line easily and process it as wished. Ie: as part of "one time usage" small shell script, a simple syntax like <my_aix_command --csv | grep -v -e"^#"> will remove the header line (as any comment line within UNIX world). An for more "durable" implementation like Ansible, it will be possible to keep the header line aside and compare the expected header with the one provided by the command, so in case command evolve, there is way to detect new "fields" additions and avoid to integrate "wrong data" because it moved to an other field or was removed because obsolete or wathever reason. Of course the "formatting output" should combine with existing flags (ie: lsvg does not provide same info than lsvg <vgname> nor lsvg -P <vgname> nor any other used options) as "simply" an "machine readable output formatting".
Going this way (by addition of exhaustive format) will avoid any regression for existing scripts parsing "human readable" aix command output, and will allow aix to move lot more easily to era of automata/Infrastructure As Code/Ansible/...
This will be like a small command change (add of new output format) but giant leap for automation/Infrastructure as a code.
Do not place IBM confidential, company confidential, or personal information into any field.