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
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
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
, 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
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
