In the spirit by which this conversation was started Acronym An abbreviation formed from the initial letters of other words and pronounced as a word
z/OS Unix is not an acronym. It is at best a short version of the entire phrase z/OS Unix System Services or might be considered the "real name"... but still is not an acronym. zUSS would qualify, by definition, as an acronym. And I think I am ready to cede providing it will shutup, gag, disable pedantic feature, put a stake in this conversation, quit filling up my inbox, and otherwise cease this very much a waste of my valuable time posting on this subject. But as he has already disputed this shortened version... even though it conflicts with the definition of acronym... this will continue with no shore in site and only postings of people with time to waste on such trivial musings. Rob Schramm Senior Systems Consultant Imperium Group On Sat, Apr 7, 2012 at 1:06 AM, Pommier, Rex R. <[email protected]> wrote: > John, > > For the most part I agree with you, except in the first line of his actual > post, the original poster made it quite obvious to anybody which of the two > USS's he was referring to, which makes this current argument all the more > stupid. I think this whole thing is painfully silly, as Mr. Mason will never > give up on his crusade to stop anybody from using USS to refer to Unix stuff, > and a few others seem to take delight in needling him on, and the vast > majority of us would prefer the whole thing just dry up. No amount of > cajoling will get either side to change their respective minds, but > unfortunately apparently no amount of begging them to "just give it up" will > make that happen either. > > And it's too bad, because I have been the recipient on a couple occasions of > some of Mr. Mason's wisdom in regards to a VTAM issue that I was having. > Unfortunately the gems get lost in the bickering. > > Like you, this will be my last (and in my case my first) post on the subject. > > Rex > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf > Of McKown, John > Sent: Friday, April 06, 2012 2:03 PM > To: [email protected] > Subject: Re: Accessing USS on Mainframe thru Telnet > > Well, possibly to the relief of all, I will hencefore ignore any and all > posts to this forum which include the letters USS which do not also > explicitly say UNIX or VTAM. I'm simply to old and tired to bother any more. > In this particular thread, I will agree that USS could be confusing since > "telnet" could refer to either accessing a z/OS UNIX shell prompt via > "historic" telnet, or to accessing an LU2 VTAM application via TN3270E which > is also a special encoded 3270 data stream using the telnet protocol. > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets(r) > > 9151 Boulevard 26 * N. Richland Hills * TX 76010 > (817) 255-3225 phone * > [email protected] * www.HealthMarkets.com > > Confidentiality Notice: This e-mail message may contain confidential or > proprietary information. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. HealthMarkets(r) is the brand name for products underwritten and > issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake > Life Insurance Company(r), Mid-West National Life Insurance Company of > TennesseeSM and The MEGA Life and Health Insurance Company.SM > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > The information contained in this e-mail may contain confidential and/or > privileged information and is intended for the sole use of the intended > recipient. If you are not the intended recipient, you are hereby notified > that any unauthorized use, disclosure, distribution or copying of this > communication is strictly prohibited and that you will be held responsible > for any such unauthorized activity, including liability for any resulting > damages. As appropriate, such incident(s) may also be reported to law > enforcement. If you received this e-mail in error, please reply to sender and > destroy or delete the message and any attachments. Thank you. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
