I think, but am not sure, that if you have done a DEFINE MDISK against that volume somewhere along the way, that you see this. Look through the virtual device configuration of all the usual suspects (MAINT, OPERATOR, the userid of whatever does full volume backups, etc) or log them off.
________________________________ From: The IBM z/VM Operating System on behalf of Marcy Cortes Sent: Sun 9/14/2008 12:53 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Can't detach a DASD device from system halt de33 Halt was not initiated to DASD DE33 because the device is not active Ready; T=0.01/0.01 11:51:49 Nope. It's very odd. I was taking 17 volumes off, and only this one got stuck... Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Imler, Steven J Sent: Sunday, September 14, 2008 9:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Can't detach a DASD device from system Try HALT DE33 ... JR (Steven) Imler CA Senior Sustaining Engineer Tel: +1 703 708 3479 [EMAIL PROTECTED] > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Marcy Cortes > Sent: Sunday, September 14, 2008 12:48 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Can't detach a DASD device from system > > What is wrong with this device? Why can't I detach it from system? > > q de33 > DASD DE33 CP SYSTEM V8XES1 0 > Ready; T=0.01/0.01 11:43:51 > det de33 system > HCPDTS143E DASD DE33 in use by system > Ready(00143); T=0.01/0.01 11:43:54 > q sys de33 > > DASD DE33 ATTACHED SYSTEM 0000 V8XES1 > DASD MDISKS NOT FOUND > Ready; T=0.01/0.01 11:43:59 > q alloc v8xes1 > HCPCQA1002E Volume identifier V8XES1 does not exist. > Ready(01002); T=0.01/0.01 11:44:05 > > q dasd details de33 > DE33 CUTYPE = 2107-E8, DEVTYPE = 3390-0C, VOLSER = V8XES1, CYLS = 32760 > CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY > -SUBSYSTEM Y Y Y - N N > -DEVICE Y - - Y N N > DEVICE DETAILS: CCA = 33, DDC = -- > DUPLEX DETAILS: -- > PPRC DETAILS: PRIMARY VOLUME > CU DETAILS: SSID = DE00, CUNUM = DE00 Ready; T=0.01/0.01 > 11:46:08 > > > This is z/VM 5.3 RSU 0801. > > > Marcy > > > "This message may contain confidential and/or privileged information. If > you are not the addressee or authorized to receive this for the > addressee, you must not use, copy, disclose, or take any action based on > this message or any information herein. If you have received this > message in error, please advise the sender immediately by reply e-mail > and delete this message. Thank you for your cooperation."
