On Thu, Sep 11, 2014 at 11:16 AM, Charles Mills <[email protected]> wrote:
> Thanks. Agree with what you say about business. What's to disagree with?
>
> I find that "x requires y" is a general lack in the USS etc. documentation. I 
> couldn't find "POSIX(ON) requires an OMVS segment" anywhere either. (Believe 
> it or not, I searched TFM before posting what I wrote below.) But I suspect 
> it does. *We* document that our product requires an OMVS segment -- why would 
> it be so hard for the POSIX(ON) team to do the same thing?
>
> Charles

<warning comments="sarcastic">
Perhaps the UNIX people came from the COBOL team and were UNIX
developers in another life. The COBOL compiler messages are _not_
documented in a manual. According to what others have said, it is
because the COBOL team has said: "There is no need. They are self
explanatory to a COBOL programmer.". Well, what is POSIX? From:
http://en.wikipedia.org/wiki/POSIX: "POSIX (/ˈpɒzɪks/ poz-iks), an
acronym for "Portable Operating System Interface", is a family of
standards specified by the IEEE for maintaining compatibility between
operating systems. POSIX defines the application programming interface
(API), along with command line shells and utility interfaces, for
software compatibility with variants of Unix and other operating
systems." . Which <sarcasm> plainly states </sarcasm> that POSIX means
UNIX. From which it is _obvious_ that POSIX(ON) implies that z/OS UNIX
facilities are required. And that means the RACF id needs a OMVS
segment. So why bother to redundantly actually say it? And, as any
UNIX guru will tell you: "If you don't know it, then don't try to use
it!". Those who can, write code. Those who can't write code, write
documentation. Users can do neither and so shouldn't be touching
keyboards anyway. Hum, I may have a touch of UNIXism in my blood.
</warning>
-- 
There is nothing more pleasant than traveling and meeting new people!
Genghis Khan

Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to