>What precludes collisions of name/tokens? >Simply bigger name space?
Nothing precludes collisions of anything. This is one big sometimes-happy family among IBM, ISVs, and customers and I think that those who play by the rules tend to be happiest. This is why it has always been recommended that things like module and macro names, message IDs, name/token names, dynamic exit names, and many other things all begin with a prefix owned by the company that is using the name/ID. Regarding clobbering of someone's customer anchor table slot: Of course that's possible since anyone in key 0 can clobber anything (whether accidentally or maliciously or even intentionally with misguided but not malicious intent). And that includes your name/token name (it's just harder to find) which, if changed, would then make your name/token retrieve fail. Some overlays can be detected and corrected, others have limited effect, others might bring the system down. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
