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...

Sam

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

Paul

---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com