Ah, but you aren't talking about a user's profile, or the profile of a 
user-written server; you're talking about the profile of a vended product, 
which has specific accepted ways of adding commands, that don't include editing 
the profile. You say that the profile is the domain of the customer, but isn't 
it really the domain of the individual user, which, in this case, is actually 
IBM, running a product on your system. It really isn't "your" profile. It 
belongs to the user, in this case, a service machine designed by a vendor.

You're definitely in the "Your arrow, your foot" area, as maintenance to the 
product may well wipe out any changes you've made, and you won't get a lot of 
sympathy from your avenues of support when it happens. You'd do well to read 
and heed the manual, and stay out of the profile. It can only lead to being 
found crunchy and drowned in ketchup.


-- 
Robert P. Nix           Mayo Foundation
RO-OC-1-13 (new loc)    200 First Street SW
507-284-0844            Rochester, MN 55905
-----
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Rick 
Troth
Sent: Saturday, December 03, 2005 7:44 AM
To: [email protected]
Subject: PROFILEs [was: CP MSG/MSGNOH from SMTP]

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.

Reply via email to