In a recent note, John Eells said: > Date: Mon, 27 Nov 2006 17:00:40 -0500 > <Snip!>
Thanks. And is there a Friendly Manual I should bookmark to have all this information convenient for reference? (I'll look at Packaging Guide, whatever it's called this year.) > Last, we come to what I think was the original topic, that of > tape data set names. All SMP/E-installable IBM product tape data > set names should have the high-level qualifier IBM, and RFDSNPFX > is used on the ++FUNCTION statements to tell SMP/E about the > high-level qualifiers of RELFILEs. > And available on the oldest supported SMP/E. I'm behind the times. > This function was created to solve *exactly* this problem for > IBM's products, so you would not have to define new high-level > qualifiers to your security system for every new product you got > from IBM. There is no reason I know of that other vendors cannot > use it to do the same, though I have no idea whether they do or > don't. > 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? This still leaves unaddressed VOLSER conflicts, and ENQ conflicts on SMPMCS. (But I need to try the experiment to see whether SMPMCS must be named SMPMCS.) 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
