sudo modprobe vmcp If you login to the z/VM session yourself -- you can also enter #CP Q V DASD and see the result...
Scott Rohling On Thu, Jun 3, 2010 at 8:22 AM, LJ Mace <ljmace1...@yahoo.com> wrote: > When i enter vmcp... I get could not open device /dev//vmcp. No such file > or directory > Thx > Mace > > On Thu Jun 3rd, 2010 10:16 AM EDT Christian Paro wrote: > > >What about the `vmcp q v dasd`? The lsdasd shows whether the disk has been > >set online and is thus visible to Linux as a block device, but the vmcp > >command shows whether the disk is currently linked/attached to the guest > >containing that Linux instance. > > > >On Thu, Jun 3, 2010 at 10:12 AM, LJ Mace <ljmace1...@yahoo.com> wrote: > > > >> Yes I logged off,pn,then even rebooted > >> I did an lsdasd but 207(the new dasd) isnt shown > >> Thx > >> Mace > >> > >> On Thu Jun 3rd, 2010 9:56 AM EDT Christian Paro wrote: > >> > >> >What do you see when you do `modprobe vmcp; vmcp q v dasd` and > `lsdasd`? > >> > > >> >Also, did you do a full log-off/log-on of the guest after adding the > disk > >> to > >> >its directory statement? A complete log-off and log-on is necessary to > >> make > >> >the guest's runtime state reflect the changes made to the directory, > >> unless > >> >you're using specific CP commands to perform these changes manually and > >> just > >> >updating the directory to make sure the changes "stick" when the guest > is > >> >logged off and on in the future. > >> > > >> >Or, for that matter, did you attach the disk without updating the > guest's > >> >directory statement? Without updating the directory (either directly or > >> >through whatever tool you may be using), the disk you attached will > only > >> >remain attached for as long as the guest is logged on - and won't be > >> >re-attached upon subsequent log-ons. > >> > > >> >~ Chris > >> > > >> >On Thu, Jun 3, 2010 at 9:17 AM, LJ Mace <ljmace1...@yahoo.com> wrote: > >> > > >> >> I do have notes and I thought all that had to be done was att to the > >> guest > >> >> then logon to the guest then yast would indeed see it. > >> >> Thx > >> >> Mace > >> >> > >> >> On Thu Jun 3rd, 2010 8:53 AM EDT Richard Troth wrote: > >> >> > >> >> >Larry, I apologize. > >> >> >You did mention YaST and YaST should in fact see the disk and should > >> >> >then handle all this other magic for you ... automagically. Maybe > >> >> >Mark will chime in. > >> >> > > >> >> >-- R; <>< > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> >On Thu, Jun 3, 2010 at 08:25, Macioce, Larry > >> >> ><larry.maci...@com.state.oh.us> wrote: > >> >> >> I seem to be having a problem. > >> >> >> > >> >> >> I have added the pact to the Linux system through VM but when I go > >> into > >> >> >> yast/hardware/dasd to add it there I don't see it > >> >> >> > >> >> >> What am I missing? > >> >> >> > >> >> >> Thanks > >> >> >> > >> >> >> Mace > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> ----------------------------------------- > >> >> >> > ******************************************************************** > >> >> >> The information transmitted is intended solely for the individual > >> >> >> or entity to which it is addressed and may contain confidential > >> >> >> and/or > >> >> >> privileged material. Any review, retransmission, dissemination or > >> >> >> other use of or taking action in reliance upon this information by > >> >> >> persons or entities other than the intended recipient is > >> >> >> prohibited. If you have received this email in error please > contact > >> >> >> the sender and delete the > >> >> >> material from any computer. > >> >> >> > ******************************************************************** > >> >> >> > >> >> >> > >> >> >> > >> ---------------------------------------------------------------------- > >> >> >> For LINUX-390 subscribe / signoff / archive access instructions, > >> >> >> send email to lists...@vm.marist.edu with the message: INFO > >> LINUX-390 > >> >> or visit > >> >> >> http://www.marist.edu/htbin/wlvindex?LINUX-390 > >> >> >> > >> >> > > >> >> > >---------------------------------------------------------------------- > >> >> >For LINUX-390 subscribe / signoff / archive access instructions, > >> >> >send email to lists...@vm.marist.edu with the message: INFO > LINUX-390 > >> or > >> >> visit > >> >> >http://www.marist.edu/htbin/wlvindex?LINUX-390 > >> >> > >> >> > ---------------------------------------------------------------------- > >> >> For LINUX-390 subscribe / signoff / archive access instructions, > >> >> send email to lists...@vm.marist.edu with the message: INFO > LINUX-390 > >> or > >> >> visit > >> >> http://www.marist.edu/htbin/wlvindex?LINUX-390 > >> >> > >> > > >> >---------------------------------------------------------------------- > >> >For LINUX-390 subscribe / signoff / archive access instructions, > >> >send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or > >> visit > >> >http://www.marist.edu/htbin/wlvindex?LINUX-390 > >> > >> ---------------------------------------------------------------------- > >> For LINUX-390 subscribe / signoff / archive access instructions, > >> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or > >> visit > >> http://www.marist.edu/htbin/wlvindex?LINUX-390 > >> > > > >---------------------------------------------------------------------- > >For LINUX-390 subscribe / signoff / archive access instructions, > >send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > >http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
