What I have done is after IPLing second level, I issued 'ATT 163C to
VMTEST' and that seemed to work and now on second level OPERATOR, it
shows:
11:01:27 Q 163C
11:01:27 DASD 163C ATTACHED TO WVLNX30 0A81 R/W LX163C
So, I think that's what I want, but I don't think I have definitions
quite right. Seems like I shouldn't have to do that everytime I ipl.
Anyway, it got me where I needed to be for now.
THANKS Everyone for the help!
Anne D. Crabtree
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8885
Fax 304-558-1351
>>> [EMAIL PROTECTED] 6/22/2007 10:50 AM >>>
In the second level system, do a "Q DASD ALL" and look at the results;
Do
you see your disks there, and what is their state?
In the first level system, do a "Q DASD label" for the two disks in
question, and see what their state is there.
There has to be a reason that the disk isn't finding its way into the
second
level system as a usable device.... Just need to figure out what that
is.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OE-5-55 200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
On 6/22/07 9:15 AM, "Anne Crabtree" <[EMAIL PROTECTED]> wrote:
> In VMTEST, I was only using DEDICATE for hipersocket devices??? not
for
> any volumes..
> The MDISK was the only way I could think to make VMTEST see that
dasd.
> I don't understand why the User_Volume_Include * doesn't allow me to
see
> all dasd.
>
> After I IPL VMTEST, I did 'ATT 163C TO VMTEST' from MAINT 1st level
and
> that seemed to work. At least it exists on 2ndlevel anyway.
>
> Thanks for the info...I'm hoping to learn a lot at SHARE!
>>>
>>> User_Volume_Include *
>>>
>>> in your SYSTEM CONFIG of your 2nd level system, then all the
> available
>>
>>> volumes will be attached to system at IPL time.
>>>
>>> Ronald van der Laan
>>>
>> --------------------------------------------------------
>>
>
