Cheryl, thanks for the kind words. I am in no way a professional writer,
so a compliment from you is taken as a high honor.

To be honest, I still use USS as I see fit too. A few months ago, I was
willing to say anything to make the tortuous arguing stop. Now, I have
outlook rules in place that drop the noise level and arguments that
arise when some get offended and want to labor on over non-mainframe
technical issues.  

Tom Chicklon

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Cheryl Walker
Sent: Monday, June 27, 2011 3:25 PM
To: [email protected]
Subject: Re: An unnecessary controversy (Was: Ported tools for z/OS on
ADCD)

Tom and others,

I read my IBM-Main emails by threading them, so whenever I find a very
long thread I simply delete it because I know it's been hijacked. I
don't have enough time in my life to deal with those threads. For some
unknown reason, I started reading this. 

Tom, I loved your very sane response, but as a writer and publisher I
will not stop using USS when it makes sense for a couple of other
reasons. IBMers use it too often to get all legal about it (as you'll
see below).
</snip>


This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to