On Wed, 4 May 2011 13:28:30 -0500, Chris Mason <[email protected]> wrote:
>Mark - who clearly hasn't cleaned the egg off yet[1]
Please try and keep this professional. I have no idea what
you are referring to, but it doesn't add to the discussion.
>
>> IBM didn't misuse it.
>
>Wrong!
>
>> The description of the parm used "official" (ahem) IBM terminology.
>
>More wrong - if possible!
>
Not the parm... which is just an 8 char name, the DESCRIPTION:
"USSHOME
The USSHOME system initialization parameter specifies the name and path
of the root directory for CICS® TS 4.1 files on z/OS® UNIX. "
~~~~~~~~~~
>> USS is still a convenient abbreviation for Unix System Services ...
>
>
>> ... and all the current pubs are still called Unix System Services something
>or other (not z/OS Unix something or other).
>
>And your point is ... ?
>
I had just made the point. USS is an abbreviation for Unix System Services.
>I thought I might have an idea what your point was until I checked the
>current V1R12 z/OS UNIX bookshelf - yes, I trust you noticed, "z/OS UNIX" -
>although it does differ from your "z/OS Unix" by using upper case - and,
>looking in the most general manual, the "Planning" manual, I noted that
>Chapter 1 was "Introduction to z/OS UNIX".
>
>http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BPXZB2B0/1.0
>
Perhaps you don't understand how the OS is packaged and documented.
The "z/OS VnRn" prefaces all the element shelves / book names for the most
part. So you can ignore that. Prior to z/OS substitute "OS/390". The
element / component names come after the "z/OS VnRn". MVS is a component,
DFSMS is a component, Security Server, Communication Server and
Unix System Services are all components of z/OS.
If you had read more than the chapter heading, you would have seen
the first sentences which read:
"The UNIX System Services element of z/OS is a UNIX operating
environment, implemented within the z/OS operating system. It is
also known as z/OS UNIX. "
z/OS UNIX itself is just another form of abbreviation because Unix System
Services is too long a name I guess or isn't catchy enough.
>
>> Just because IBM started using z/OS unix doesn't mean every software MF
>component known to man kind is going to change their parms / keywords (for
>example, ZUXHOME for CICS SIT).
>
>Ditto!
>
>What's to "change"?[2] It was wrongly composed in the first place by pure
>carelessness - egged (sorry) on by misuse by the ignorant. It was careless
>because John Eells - I believe - implied that there is a formal process whereby
>developers can discover whether implied initialisms and other abbreviations
>have been taken already and careless developers may very well imagine they
>are allowed to bypass that process when they find others extensively misusing
>a particular initialism.
>
You casting a very wide net in your disparaging remarks about IBM
developers. One example used in this discussion often is the USS
abbreviation in Health Checker. This is a relatively new component
of z/OS and I'm sure it went through all the formal processes, yet
USS is used as the abbreviation for the check names and the check
owner.
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:[email protected]
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/
----------------------------------------------------------------------
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
