Great if that works for your environment. We have a policy of never hardcoding libraries.
TAATOOL might be an exception, could be a hard sell.
From the TAATOOL install guide
" You should not copy TAA commands to a separate library. Either add TAATOOL to the library list or library qualify the use of the command such as TAATOOL/ADDDAT"
I tested TAATOOL/***CMD, I see the TAATOOL as the PRD library.

Run this on your system, let me know how many dups.
Use the CHKTAAPRD command with LIB(*ALL) to check for duplicate TAA commands and objects in non-TAA libraries.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sam_L
Sent: Tuesday, December 02, 2014 5:50 PM
To: Midrange Systems Technical Discussion
Subject: Re: Managing libl for multiple 3rd party products

FWIW: For TAATOOL I have always set the rule that any use in production programs must qualify the command, e.g. TAATOOL/taacmd. And I never put TAATOOL in any production library list, which happily, and quickly, enforces the rule (typically when the source control program compile for deployment to production or QA fails. If your developers can compile directly into production, all bets are off).

This works well for the TAATOOL because all its commands use a product library. It means that there is no conflict between any TAATOOL command and any other command, or program the command calls, on the system.

I would expect that most third party software products use a product library on their commands. IMHO, the product library is a neat and practical concept. Of course, its usage may be hard to retrofit if you have a boatload of existing code...


On 12/2/2014 2:13 PM, Steinmetz, Paul wrote:
Rob / Chuck

3) The remaining products below have additional issues to deal with.

TAATOOL SYS TAA Prod Tools library V7R1 10/15/13 Exception to the rule, too many cmds.
RXS SYS RPG-XML Suite v3.11 Still researching
TCPIP502 SYS Netsocket/400 No commands
RDB40 Still researching


This email has been checked for viruses by Avast antivirus software.

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].