From: VM/ESA and z/VM Discussions
Sent: Wednesday, February 22, 2006 3:15 PM
Subject: Re: another question adding allocating dasd
L2DRW01 - DSC
Doesn't this mean the user is on and disconnected?
Yes, it does. Like I said, defining the minidisk does not connect it or
link it to a logged-on user -- the CP directory entry is read once when
the virtual machine is created at logon time, and each time you execute
a LINK command. So, the trick is the second part of my note: telling CP
to do the LINK.
In reading Davids answer it looks as if I need to log the
instance off an d on.
If I do a xautolog won't that take the the instance down?
And if I do an autolog won't it show the instance already logged on?
If a userid is already logged on, AUTOLOG and XAUTOLOG will determine
this and just tell you that. They will not shut a running instance down
(you want the SIGNAL SHUTDOWN command for that -- don't do it, though).
You need to log in to the VM userid and do #CP LINK L2DRW01 nnn nnn MR
for each of the new disk addresses you added. After you've done that,
type BEGIN to resume Linux processing, and #CP DISConnect to go back to
normal Linux operations.
My other instances show -dsc also but still show the link.
OH brother am I confused.
It's easier if you think about it this way:
CP and it's directory entry define the container that Linux operates
within. You can plug in new hardware into the container, but that
doesn't necessarily force CP to present that hardware right now -- you
have to tell it to do that. You can do that in one of two ways: force CP
to destroy and recreate the userid (logon/logoff), or explicitly make
the new hardware available by connecting it to the virtual machine (the
LINK command). #CP LINK issues the command to CP without disturbing the
contents of the virtual machine -- it plugs that new hardware into the
virtual machine configuration.
Then you can tell the operating system in the virtual machine to do
something with it.
Does that help?