In a recent note, John Eells said: > Date: Tue, 28 Nov 2006 08:22:33 -0500 > > http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/GIMPKG80/CCONTENTS?SHELF=EZ2ZO10H&DN=SC23-3695-10&DT=20030522104555 > Thanks.
> > Are customers alerted of the set of current registered prefixes, > > and possible future registered prefixes, so they may avoid RACF > > entanglements? Would it be reasonable to regard all 3-character > > HLQs as reserved for vendor products? > > No, and no. (The only three-letter HLQ I can think of off the > top of my head is "IBM," for RELFILEs. If I owned a company > named Eells Software, I might well use EELLS as my company's > chosen RFDSNPFX.) > 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. The SMP/E RM recommends that RFDSNPFX be no longer than three characters so it will not be truncated in standard tape labels. I'd be inclined to go quite the opposite direction, and choose the longest possible RFDSNPFX so the customer could override in case of a conflict by editing the ++FUNCTION statement. Alas, SMP/E limits RFDSNPFX to 8 characters. Thanks again, gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
