Minidisks can only be created on volumes that are either CP_OWNED, either
ATTACHed to SYSTEM. An MDISK statement defining a minidisk on any other
volume will result in
HCPLNM108E KRIS 5193 not linked; volid VSHR02 not mounted
User_Voume_include is just an easy way to have DASDs attached to SYSTEM at
IPL. You could have the same result by coding ATTACH rdev SYSTEM in the
PROFILE EXEC of AUTOLOG1 (but AUTOLOG1 will be unable to run when the
volumes for its 191 and MAINT 190 are not ATTACHED to SYSTEM yet)
For your second level VM system (with Linux) you must decide to use
- either DEDICATE, what means that the volumes to be passed on must
NOT be attached to SYSTEM in your first level VM.
- either MDISK, what means that those volumes must be attached to
SYSTEM in your first level VM system. This can only work when those volumes
have a unique disk labels.
The advantage of using MDISKs is that you can more easier get access to for
example MAINT 191 of the second level system from inside your first level
system. Just use
DEFINE MDISK 1191 startcyl size volser
You only need to know where the minidisk you need is located in the
directory of the second level VM system.
But, beware: if your second level VM system is running, this DEFINE MIDKS
gives you a MultiWrite minidisk and you can have dataloss. Use only when
your VMTEST is down.
--
Kris Buelens,
IBM Belgium, VM customer support
2007/6/22, Anne Crabtree <[EMAIL PROTECTED]>:
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!
Anne D. Crabtree
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8885
Fax 304-558-1351
>>> [EMAIL PROTECTED] 6/22/2007 9:25 AM >>>
I see a mix in the directory entry for VMTEST:
- you seem to use DEDICATE to pass the VM volumes to VMTEST
- but use MDISK to pass the Linux volumes
You could use DEDUCATE for all of them
A lesson about devices (something I explained several times when
teaching.
At the time there was not a single exception, now there are some)).
The rule:
A device can be given to 1 "person" only at a time. "person" can be
CP
itself or a virtual machine, never both.
- When you give the device to CP itself, it can maybe be shared,
depending on the device type
- for a disk, it can then host minidisks. Command: ATTACH xx
SYSTEM, or via SYSTEM CONFIG (CPOWNED or USER_VOLUME_INCLUDE)
- for a 3270 terminal: you can then logon/loggoff. Command:
ENABLE rdev
- ...
- To give a device to a virtual machine: ATTACH or DEDICATE is
used.
2007/6/22, Stracka, James (GTI) <[EMAIL PROTECTED]>:
>
> Or LINK fullpack ucb ucb M (MW or RR) on in the PROFILE EXEC of
VMTEST
> if you have a fullpack minidisk holder id.
>
> We LINK RR for 1st level volumes that VMTEST is to have READ only.
> VMTEST volumes all start VM2 (for VM 2nd Level) and LINK them MW.
>
> Each to his own.
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
> Behalf Of Bill Munson
> Sent: Friday, June 22, 2007 9:03 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: DASD second level
>
>
> Anne,
>
> You need to detach the volumes from SYSTEM on the 1st level VM That
way
> they can be attached to VMTEST to be used 2nd level.
>
> good luck
>
> Bill Munson
> IT Specialist
> VM System Programmer
> Office of Information Technology
> State of New Jersey
> (609) 984-4065
>
> President MVMUA
> http://www.marist.edu/~mvmua
>
>
>
> Anne Crabtree wrote:
> > tried that...
> > seems no matter what i do, second level just says they don't
exist!
> >
> > Anne D. Crabtree
> > System Programmer
> > WV Dept of Administration - OT
> > 304-558-5914 ext 8885
> > Fax 304-558-1351
> >
> >>>> [EMAIL PROTECTED] 6/22/2007 8:58 AM >>>
> > Anne,
> >
> > If you put:
> >
> > 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
> >
> --------------------------------------------------------
>
--
Kris Buelens,
IBM Belgium, VM customer support
