CP DET cuu FROM SYSTEM
This is what I see, showing the difference between dasd "attached to the system" and merely "there".
DASD 028D CP SYSTEM LNX007 0
DASD 0293 CP SYSTEM TVMPG1 0
DASD 0294 CP SYSTEM LNX005 0
DASD 0110 MVS110 , DASD 0111 MVS111 , DASD 0112 MVS112 , DASD 0113 MVS113
DASD 0114 MVS114 , DASD 0115 MVS115 , DASD 0116 MVS116 , DASD 0117 MVS117
This is a snippet from a Q DA ALL. If I wanted to reinit. 294, I would have to DET 294 FROM SYSTEM (note: that it has 0 id's linked to mdisks on it. After 294 was detached from the system, then I could ATT 294 * 294, assuming I was on MAINT or at least some id with class B privileges.
Looking further down the list, DASD 110, MVS110, is visible but is not attached. I could immediately ATT 110 * 110 to do an INIT. Of course, I might get some of my MVS peers honked off.
If an id has mdisks defined on a volume, it needs to be attached to the system. If the id gets access to the system by attaching it to itself or having it attached, then it cannot be attached to the system--it just needs to be online.
Jim
At 01:34 PM 2/21/2006, you wrote:
I'm sorry when I said devices I should have said current volumes (IE
vol123,vol345,etc) need to be changed to volabc,voldef,etc). So I'm keeping
the dev numbers the same I just want to unalloc those dev reformat them and
give them to another user.
thanks
Mace
Cornell Univ.
(607) 255-1760
