On Saturday, 12/03/2005 at 07:44 CST, Rick Troth <[EMAIL PROTECTED]> wrote: > On Thu, 1 Dec 2005, Alan Altmark wrote: > > I'm sorry; I must be hard of hearing, too. I thought you said "inserted > > the following code in the PROFILE EXEC". I'm sure what you actually said > > was "created an exit invoked by the :Exit. tag for the SMTP server (for > > SETUP only)". 'cuz no one in their right (or left) mind would modify the > > PROFILE EXEC of an IBM-provided TCP/IP server. No one. > > PROFILE EXEC is as much the domain of the VM/CMS customer > as $HOME/.profile is the domain of the Unix customer. > Some customers [I say "some" because I don't want to have to > define "many"] have other profiling they wish to do to all SVMs. > > Sir Charles, we are not amused. We are most annoyed. > We are greatly offended when you lay claim to our user space > and hijack it for your own cold purposes. You may well say, > "Your arrow; your foot". But take care where you tread, sir, > for the dragons may find you crunchy and tasty with ketchup.
Maybe *your* PROFILE EXECs are in the domain of the customer. The ones in the TCP/IP server suite are not. The PROFILE EXEC is a servicable part. IF we service it, unlikely though it may be, and you have not performed local mods via VMSES/E, your changes will be blown away by PUT2PROD or TCP2PROD. TCPRUN was created in the first place to eliminate PROFILE EXEC as a source of ill-advised modification. So we created a way for you to run your own programs (:Exit./TCPRUNXT) without having to modify our code. SYSPROF is in your domain. The [userid/nodeid/SYSTEM, not IBM!] DTCPARMS file, the file pointed to by the :Exit tag, and TCPRUNXT EXEC are all yours. Everything else is labeled "Keep off the Grass". ;-) A tempest in a teacup, of course, as I doubt we'll ever have to service PROFILE EXEC!! [And that's "Sir Alan". The Chuckster has never been knighted. :-)] Alan Altmark z/VM Development IBM Endicott
