Steve, I'm going to guess that at some point the PROD lpar was IPLed and maybe it didn't have any issues with duplicate volumes.
Is there anything in the IODF related to lpar access (or not access) to some of the DASD related to the lpars. In the IODF you can grant (or not grant) access to devices. While in the IODF you might look to see if there was anything done using channel access. What I would do, if possible, is group DASD volumes addresses for a given lpar on their own channels and then grant only that lpar(s) access to the channels. Not knowing how many DASD volumes you have you could try something like the DEVSERV command to list volumes. If I recall correctly, you should be able to tell what addresses are online and offline to the PROD lpar and from that you might be able to tell what the duplicate volumes addresses are. This may also help you to understand how many messages you might get. I don't recall what the DCOLLECT utility does when it encounters an offline DASD volume. Even if it can tell you which addresses are offline, I don't know if it can tell you the volser. I don't know what you can do at this point other than suffer through the IPL and reply to a bunch of messages as to which volume you want offline on TEST and hope people do the right reply. I really don't know how you would get the DASD volser information from offline DASD. I'm not an expert but I would think you would either need the incore UCB or the ability to read the VTOC to get the volser. Paul -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Seymour J Metz Sent: Saturday, March 7, 2026 04:28 PM To: [email protected] Subject: Re: Identifying Duplicate Volsers In Environment If you can get a test system up, extract the duplicate volumrd from the master trace table, -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Steve Estle <[email protected]> Sent: Saturday, March 7, 2026 5:20 PM To: [email protected] <[email protected]> Subject: Identifying Duplicate Volsers In Environment External Message: Use Caution All, I have (inherited) a ZOS environment with many duplicate volsers spread across two LPAR's: Prod & Test. Right now Test LPAR is down and we are needing to restart / ReIPL the Test LPAR but getting many duplicate volsers during IPL process. I'm looking for tool / utility that I can use / run from Production LPAR that will list out all duplicate volsers and related unit addresses within the defined DASD environment - of course this means the utility needs to interrogate all configured DASD volumes whether online or not. Anything out there? - I tried ISMF and don't see a way to do thru the ISPF interface but possibly a trick or two with ISMF I'm not aware of? Anyways open to any / all ideas - have to believe there is a way. Possibly CBT? Thanks as always. Steve Estle CDW ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
