Rex > It would be best for everybody involved to simply make sure that their usage of the acronym isn't ambiguous.
In principle, I could agree. However, how do you make sure that there is no ambiguity when so often contributors seeking guidance have seen only the incorrect use and maybe never the correct use - and what they are discussing involves TELNET in some very often mangled form? The devil's in the details! Chris Mason On Mon, 2 May 2011 15:30:39 +0000, Pommier, Rex R. <[email protected]> wrote: >Steve, > >Not quite. The second word, System versus SystemS. It took me a while to catch that one. :-) > > >And, yes, I'm tired of the bickering back and forth. Neither side will >convince the other that they're right/wrong. It would be best for everybody involved to simply make sure that their usage of the acronym isn't ambiguous. > >Rex > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Steve Comstock >Sent: Monday, May 02, 2011 10:19 AM >To: [email protected] >Subject: Re: An unnecessary controversy (Was: Ported tools for z/OS on ADCD) > >On 5/2/2011 9:11 AM, Paul Gilmartin wrote: >> On Mon, 2 May 2011 09:25:51 -0400, Chicklon, Thomas wrote: >> >>> OK, you win. USS is officially only to be used when speaking of VTAM's >>> table thing. >>> >>> So, if you (and some others I'm sure) want to preserve the purity of the >>> acronym USS, good for you. Don't misuse it. Just leave the rest of us >>> out of it. >>> >> It's interesting that the link Kirk Wolf posted: >> >> http://www.acronymfinder.com/USS.html >> >> rates the incorrect > >USS (Unix System Services) number six, and >USS (Unix Systems Services) number fourteen respectively. > >Ummm. These are the same. > > >The >> usage correct according to the IBM Glossary doesn't even make the >> list. And when I filter by Information Technology, USS (Unix >> System Services) becomes number one, and USS (Unix Systems Services) >> becomes number two. > >the above are the same > > Now, I suspect that AcronymFinder hasn't an >> army of gnomes researching and consulting authorities to verify that >> USS (Unix System Services) or USS (Unix Systems Services) > >the above are the same > >is >> technically correct. More likely, they have a nest of spiders that >> crawl the Web, and whenever they find constructs such as USS (Unix >> System Services) or USS (Unix Systems Services) > >the above are the same > >they add weight >> to the ranking of that interpretation. >> >> When I want to understand an acronym, I rarely RTFM; more often >> I simply type the acronym in a Google search box, and take >> whatever appears in the first page of hits as conventional, >> although possibly technically incorrect. So Chris Mason's >> polemics are likely counterproductive of his end: the more >> stridently he denies that USS stands for Unix System Services, or >> that USS stands for Unix Systems Services > >the above are the same > >, provoking followups >> that sometimes quote him, the higher he boosts the construct he >> detests in AcronymFinder's ratings. >> >> He'd more effectively further his cause of eliminating use of >> USS (Unix System Services) and USS (Unix Systems Services) > >the above are the same > > >if >> he'd simply STFU. (AcronymFinder gets that one almost right.) >> >> -- gil > >??? > >-- > >Kind regards, > >-Steve Comstock ---------------------------------------------------------------------- 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
