> (cough) I'm sorry. My hearing is bad. You did what? (For a minute there > I thought you you modified PROFILE EXEC. Whew!) You meant to say that > you use the :vctc. tag in SYSTEM DTCPARMS to cause VM TCPIP to reestablish > the connections, right? Because we all know that you never modify PROFILE > EXEC. ;-)
(cough) I'm gonna say it again: The "product" should be run from a sandbox EXEC and the customer should be able to do whatever he blankety-blank wants with "PROFILE EXEC". Give them a sample. Let them customize it. (For those who do not know, this is a point where Alan and I disagree. Though on many other points we are in "violent agreement".) On UNIX (thus on Linux) many of the best products live in their own "sandbox". Some call it a "product home directory". Others might call it a "package root directory". VM is a superb example of this where we enjoy Service Virtual Machines that not only can be isolated to their own minidisk (or two or more; it depends) but may also do so read only. (R/O sharing ... what a concept!) Substantial portions of the VM TCP/IP service machine suite can be made to run from a common PROFILE EXEC with the "product EXECs" invoked automatically. This is not how IBM ships VM TCP/IP, but it works VERY NICELY. Many many other VM based services run this way without being at odds with the vendor.
