On Mon, 19 Jan 2009 11:29:22 +0100, GIONFRIDDO MICHELE wrote: >I have a problem. > >In my environment, i have same volser per tape a disk. > BTDTGTTS. DLI. NGDIA. (Wishful thinking.)
If the problem occurs within your site, your site has a process problem. One of a very difficult type because its resolution is necessarily more political than technical (You can't tell *me* I can't call *my* tape BT2092!"). (We temporarily varied the disk volume offline.) If the conflicting tape is an interchange volume, you've encountered a global problem. The global solution is for some industry-wide organization (e.g. SHARE or IBM) to assume the responsibility of reserving a range or pattern of VOLSERs for interchange media. Several decades ago, SHARE had a project to register unique VOLSER prefixes world-wide. I assume this was Overcome By Events: name space exhaustion. The Right Solution would be to enlarge the VOLSER name space, so you could use, e.g. "BT2092.dasdvol.SOGEI.IT". I expect this not to happen, not only for technical reasons but also because of the perception that data interchange will increasingly be via Internet rather than by interchange of physical media. OS X provides a useful solution: when I mount a volume with a duplicate ID, the OS assigns a generated name and mounts that. It's the my responsibility to be aware which I'm using. But I don't have the anquish of BLP. -- gil ---------------------------------------------------------------------- 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
