Ed Finnell wrote:
In a message dated 6/29/2006 1:49:41 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
That's a component prefix and as such it must be unique. USS
is an acronym. While desirable acronyms do not have to be
unique.
Even component prefix is not always uniques. See IKJnnnnn messages. Some
of them belongs to RACF.
It need not to be unique. It is *strongly suggested*. It is
*convenient*. But the system and systems programmers can surviver
without full uniquity.
Mainframe has a lot of such "standards". For example: Snnnnn libraries
are target libraries (DDDEFs), while Annnn libraries are distribution
libraries. *Usually*. With a number of exceptions, like LINKLIB or
LPALIB (no S). Many of them are exceptions because they existed before
those rules arised.
BTW: USS is not unique acronym, no doubt. See www.acronymfinder.com
24 results. Only in English. Including USS as Unix System Services (with
'IBM' annotation) and United Star Ship form Star Trek.
Did I mentioned United States Ship ? <g>
<forgive me my poor english>
Acronym is a set of first letter of some concept. No more, no less.
There are no 'official' acronyms. There can be copyrights, reserved
names (Like Microsoft or IBM - acronym). However acronym itself is not a
subject copyright law. It is a part of language. No official body can
decide what acronym is. Again: Acronym is word formed from the initial
letters of a series of words.
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
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
