Paul Gilmartin wrote:
[...]
The Right Solution would be to enlarge the VOLSER name space, so you
could use, e.g. "BT2092.dasdvol.SOGEI.IT".
IMHO it doesn't change to much.
In your example there is still no warranty of name uniqueness, only it
would be less likely. What about "ZOS.VERSION1.REL9.CAT8" ? Or
"ZOS.DATA.INTERCHANGE.1" ?
In fact there is some kind of solution: WWID for tapes. Each cart has
it's own unique ID. Recorded in a chip. And this ID is unique as
Ethernet address or FC WWN (although the numbers can be changed to
confilcting values).
For DASD, there should be similar process of generating (emulated)
volume ID's - maybe based on vendor ans S/N.
Last, but not least: system support!
Without support any ID would be useless. I can imagine the following idea:
we still use 6-character volsers, however system (SMS, RMM, other
components) recoginzez WWID.
In case of volser conflict there is a way to provide "extended volser",
i.e. BT2092.wwid-number.
Similar technique is used when you try to issue MVS CANCEL and two
started tasks have the same name - you have to provide unique ASID.
To complement the idea above: first BT2092 would be "primary BT2092", so
any reference without WWID would be directed to it, the second would
require WWID to be recognized.
My €0.02
--
Radoslaw Skorupka
Lodz, Poland
--
BRE Bank SA
ul. Senatorska 18
00-950 Warszawa
www.brebank.pl
Sąd Rejonowy dla m. st. Warszawy
XII Wydział Gospodarczy Krajowego Rejestru Sądowego,
nr rejestru przedsiębiorców KRS 0000025237
NIP: 526-021-50-88
Według stanu na dzień 01.01.2008 r. kapitał zakładowy BRE Banku SA wynosi
118.642.672 złote i został w całości wpłacony.
----------------------------------------------------------------------
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
