Strange result from Q MDISK
A user asked me to transfer his 191 disk to his 193 disk and give him a new (larger) 191 disk. Before doing this I checked he was logged off. When he logged on again, everything was where he expected it to be but he got a strange result from Q MDISK :- q mdisk 191 TargetID Tdev OwnerID Odev PPFDEV 0191 PPFDEV 0191 Ready; T=0.01/0.01 14:36:40 q mdisk 193 TargetID Tdev OwnerID Odev PPFDEV 0193 PPFDEV 0191 Ready; T=0.01/0.01 14:36:47 When he did a Q MDISK nnn LOC he could, indeed see that the disks were defined in different places so all is well - but I am at a loss to explain why he is seeing this result. Can anyone explain this? Colin Allinson VM Systems Support Amadeus Data Processing GmbH
Re: Strange result from Q MDISK
Does someone still have a link to the old disk? From the help notes on q mdisk... The OwnerID and Odev listed in the output can be different, depending on how the disk was defined. If the disk definition in the system directory has been changed, the new OwnerID and Odev may not be immediately reflected in the QUERY MDISK output. The old designation will be shown until there are no users accessing the disk. Use the form of the command consistent with the output needed for your application. On Thu, 4 Feb 2010 16:30:37 +0100, Colin Allinson cgallin...@amadeus.com wrote: A user asked me to transfer his 191 disk to his 193 disk and give him a new (larger) 191 disk. Before doing this I checked he was logged off. When he logged on again, everything was where he expected it to be but h e got a strange result from Q MDISK :- q mdisk 191 TargetID Tdev OwnerID Odev PPFDEV 0191 PPFDEV 0191 Ready; T=0.01/0.01 14:36:40 q mdisk 193 TargetID Tdev OwnerID Odev PPFDEV 0193 PPFDEV 0191 Ready; T=0.01/0.01 14:36:47 When he did a Q MDISK nnn LOC he could, indeed see that the disks were defined in different places so all is well - but I am at a loss to expla in why he is seeing this result. Can anyone explain this? Colin Allinson VM Systems Support Amadeus Data Processing GmbH
Re: Strange result from Q MDISK
check if Q MDISK nnn LOC gives same output as Q MDISK nnn LOC DIR. maybe his PROFILE (for whatever reason) detaches 193 and links his 191 as 193? Det 193 and do CP LINK * 193 193 and repeat the Q MDISK nnn LOC From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Colin Allinson Sent: Thursday, February 04, 2010 10:31 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Strange result from Q MDISK A user asked me to transfer his 191 disk to his 193 disk and give him a new (larger) 191 disk. Before doing this I checked he was logged off. When he logged on again, everything was where he expected it to be but he got a strange result from Q MDISK :- q mdisk 191 TargetID Tdev OwnerID Odev PPFDEV 0191 PPFDEV 0191 Ready; T=0.01/0.01 14:36:40 q mdisk 193 TargetID Tdev OwnerID Odev PPFDEV 0193 PPFDEV 0191 Ready; T=0.01/0.01 14:36:47 When he did a Q MDISK nnn LOC he could, indeed see that the disks were defined in different places so all is well - but I am at a loss to explain why he is seeing this result. Can anyone explain this? Colin Allinson VM Systems Support Amadeus Data Processing GmbH This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.
Re: Strange result from Q MDISK
You could issue a Q LINKS nnn to see who has it linked. Jim Hughes 603-271-5586 It is fun to do the impossible. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Romanowski, John (OFT) Sent: Thursday, February 04, 2010 10:48 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Strange result from Q MDISK check if Q MDISK nnn LOC gives same output as Q MDISK nnn LOC DIR. maybe his PROFILE (for whatever reason) detaches 193 and links his 191 as 193? Det 193 and do CP LINK * 193 193 and repeat the Q MDISK nnn LOC From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Colin Allinson Sent: Thursday, February 04, 2010 10:31 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Strange result from Q MDISK A user asked me to transfer his 191 disk to his 193 disk and give him a new (larger) 191 disk. Before doing this I checked he was logged off. When he logged on again, everything was where he expected it to be but he got a strange result from Q MDISK :- q mdisk 191 TargetID Tdev OwnerID Odev PPFDEV 0191 PPFDEV 0191 Ready; T=0.01/0.01 14:36:40 q mdisk 193 TargetID Tdev OwnerID Odev PPFDEV 0193 PPFDEV 0191 Ready; T=0.01/0.01 14:36:47 When he did a Q MDISK nnn LOC he could, indeed see that the disks were defined in different places so all is well - but I am at a loss to explain why he is seeing this result. Can anyone explain this? Colin Allinson VM Systems Support Amadeus Data Processing GmbH This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.
Re: Strange result from Q MDISK
Hughes, Jim jim.hug...@doit.nh.gov wrote :- You could issue a Q LINKS nnn to see who has it linked. Yes, I did that. At the time I did the query ( as a sysprog I do love the power of the FOR userid CMD feature) there was no-one else. That is not to say that there was no-one else linked when he logged on. I guess I should have got him to log off on again. Romanowski, John (OFT) john.romanow...@cio.ny.gov wrote :- check if Q MDISK nnn LOC gives same output as Q MDISK nnn LOC DIR. Yes, as I said in my original post, I did that. The locations were different so he was not really looking at the same disk. At this stage I can only guess and I would put my money on overlapping links (somebody linked when he logged on that released it later). Thanks anyway to everyone for their thoughts on this. The only problem is that I like to be able to explain things that seem mysterious ;-) Colin Allinson VM Systems Support Amadeus Data Processing GmbH
