I want to thank everyone for their input.
I also now have a better understanding of the PRD libraries and how they work.
I try to control all interactive environments using a jobd libl, but some apps do not adhere to this.
Any app that has a menu driver system that manipulates the libl on the fly based on menu selections.
I cringe when I see this.
The other thing to keep in mind, before deciding on the solution, is, will the 3rd party app change their library name in a future upgrade.
This could change the solution to be implemented.
The use of these 3rd party support products is mixed, interactive, batch, and/or background tasks.
I've broken them into 3 categories, PRD APPS, PROXY APPS, NEITHER PRD/PROXY
If an app supports PRD, then I agree the PRD solutions should be used.
Some PRD apps start with a menu, STRPDM, GO BRMS, GO JS,
Other PRD apps will need the library hardcoded, TAATOOL/SWPUSRPRF
I need to Identify all locations where a TAATOOL command is used, and update source inserting TAATOOL/, will be a challenge.
I need to this before I try selling this, not sure how I will do this as of yet.
PKZIP, DBU, RDB30
Identify the commands used from these apps and create a PROXY command placed in a SYS library.
The PROXY command is a better solution than a CRTDUPOBJ of the command.
RXS, TCPIP502 (Netsocket/400) , GROUP1, may be more, still researching.
These apps are not cmd driven, library needs to be included in the libl.
Either SYSLIBL (not recommended), JOBD (Preferred), or via ADDLIBLE (least preferred).
If my summary is confusing, misleading, or if I missed anything, please let me know.
Libl, can't live with them, can't live without them.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, December 03, 2014 7:12 AM
To: Midrange Systems Technical Discussion
Subject: Re: Managing libl for multiple 3rd party products
Look at the PRDLIB parameter on CHGCMD or CRTCMD.
Here's something else to look at.
You'll notice that it isn't a "real" command. It is a "proxy" command.
QSYS/STRPDM only points to QPDA/STRPDM. If you're a wizard at the IFS and are used to this concept in other stream file based operating systems you'll see that it resembles a "symbolic link" in which one directory is just a pointer to another directory. Useful for when one package is configured to find the 'bin' directory under one location and another is configured to expect it under another. And other such cases.
Now, let's look at DSPCMD QPDA/STRPDM
Product library . . . . . . . . . . . : QPDA
And that is why, when you are at the STRPDM menu, and you type in DSPLIBL, you will see