Add the ability to create/save/and use Library Lists

Your own tooling can handle this in conjunction with User Actions, I've been doing it for years. I wrote mine back in 1991 to use with PDM, still works! I run it through user actions now, set my library list for a "task" and start working. At connection time, RDi runs a command that sets the library list to the last-used one, so I don't forget (lol).

The benefit of your own tooling is that it works OUTSIDE RDi. Setting up library lists in RDi, and having RDi save them, means they are for RDi's use while running RDi, and not available to just use them on a command line.

I'd rather RDi be doing programming-effort-reduction-related mods than trying to act like a change-management package for those of you who do not have one.

The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. Although there is a work-around that each one can do themselves, it would be much better to have a consistent way for all to do it.

Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

For more information about CAAC, see www.common.org/caac

Nancy Uthke-Schmucki - CAAC Program Manager

Seems this is pretty easily done using CHGLIBL command with, perhaps, a list of LIBL's kept in a table, keyed by a name for each - have a program which has that key as parameter, then it parses things as needed for CHGLIBL. The table could be the LIBL name and each library in records.

A call to that program is easily done in RDi, also as something called when a connection is started.

We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.

In addition to saving library lists, it would be useful to be able to attach a specific library list to a filter so that when a source is compiled, or a program run from that filter, the selected library list would be used.

I know this has come up before because I reported such a requirement back in the day. Not everyone works in a single environment on IBM i.

The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed. This will make it easier for developers to manage multiple products and versions in RDi.

Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

Therese Eaton – CEAC Program Manager, IBM

Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

This would be advantageous to the IBM i O/S as a whole. The ability to switch (the user portion) of library lists through some permanent object akin to a *MSGF or *BNDDIR. This can be done programmatically, (e.g. a CL program, CHGLIBL and a *FILE). However, system support would provide a consistent mechanism for everyone to use - including RDi.