Paul Gilmartin wrote:
But is there a registry maintained by IBM or any other organization (SHARE?) not only so vendors can avoid conflict with each other but so customers can be spared the OP's RACF problem? Such a registry must be anticipatory, reserving name space for future use so a vendor won't unwittingly infringe on a customer's private use of a HLQ.
Except for a small number of already-reserved HLQs (notably, SYS1), the only HLQs I think are at issue here are those used for RFDSNPFX values. There is no registry of any kind for RFDSNPFX values so far as I know. Feel free to start one. We use "IBM." ;-)
More seriously, I think each company should use no more than one RFDSNPFX. This makes it hard for the registry to be anticipatory; if a new software company starts to write z/OS software, they might want their own prefix and not agree with the namespace someone else chose. (If the namespace precluded us from using "IBM," for example....)
I don't see a particular reason, however, that companies could not *share* an RFDSNPFX. When RFDSNPFX was created (in the 1980's, IIRC), I suspect the vision was that we'd use "IBM" and other companies would pick their own RFDSNPFX values. But perhaps everyone else who is not already using a unique value of RFDSNPFX could use SWVENDOR...or something...so that our mutual customers had to define one and only one additional HLQ to install any software on the platform.
<snip> -- John Eells z/OS Technical Marketing IBM Poughkeepsie [EMAIL PROTECTED] ---------------------------------------------------------------------- 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
