IMHO it was the same error as nowadays: bad naming.
I didn't work with removable DASD, but I worked with physically
removable, human-operated tapes. And it was administrator responsibility
to have proper naming convention and unique volume serials. Exceptions
in justified scenarios only.
Of course nowadays duplicated DASD volsers are usually (not always)
result of volume cloning, which is a little bit different animal.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 22.11.2020 o 00:33, Tony B. pisze:
Anyone else out there remember removable DASD, Pizza Ovens and 3340? Having
duplicate volsers was more prone to human error at the physical level.
On Sat, Nov 21, 2020 at 11:48 AM Jesse 1 Robinson <[email protected]>
wrote:
Your DASD managers are the culprits. As I said in another post, this
condition could persist for quite some time until an attempt to vary a
duplicate volser online or to IPL.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf
Of Steve Lee
Sent: Friday, November 20, 2020 2:13 PM
To: [email protected]
Subject: (External):Re: IEA213A DUPLICATE VOLUME
*** EXTERNAL EMAIL - Use caution when opening links or attachments ***
Hi Robinson,
Good to know the experience you were with.
Ops has a enough time to reply the WTORs in those particular lpars.
Those Volumes are 3400/3800/4800 strings, not all of volumes but some of
ranges.
I need to check with Storage if those has been CLIPped.....
These messages started coming out from a few last IPL cycles, no messages
until the last few IPLs which I think Storage made a change before.
Possible solution would be that being allowed to indicate that in the case
of a dup, either the HIGHER or LOWER address be put offline in IO
Configuration part in IODF when a dup is encountered if the CLIPped is a
necessity at their end.
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl,
e-mail: [email protected]. Sąd Rejonowy dla m. st. Warszawy XII Wydział
Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, NIP: 526-021-50-88.
Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi
169.401.468 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850
Warszawa,www.mBank.pl, e-mail: [email protected]. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169.401.468 as at 1 January 2020.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
