OK, I've tried the "att 829...." command and it worked as expected. I
can now IPL the guest and the disk is there.

Thanks to those who replied.  Watch your mail for the big box full of
fame and glory.
 

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
John Schnitzler Jr
Sent: Thursday, June 08, 2006 12:44 PM
To: [email protected]
Subject: Re: Help with new MDISKS.

You need to attach the disk to the system so that it can be used by the
guest.

from Maint

att 829 system lx0006

then you can ipl the guest and pick up the disk.

That will add it dynamically, if you want the attach to be there after
you IPL then you need to add the disk to the system config file on
maints cf1 disk


john




             MOEUR TIM C
             <[EMAIL PROTECTED]
             om>
To
             Sent by: Linux on         [email protected]
             390 Port
cc
             <[EMAIL PROTECTED]
             IST.EDU>
Subject
                                       Help with new MDISKS.

             06/08/2006 03:34
             PM


             Please respond to
             Linux on 390 Port
             <[EMAIL PROTECTED]
                 IST.EDU>






What am I doing wrong?  Fame and glory promised to he (or she) that
first identifies the trouble.

Here's the situation.  We are using z/VM 5.2 for the first times with
several zLinux guests.  Until recently I've had a single zLinux image in
an LPAR.  I do have the zLinux guests up and they are performing will.
It's time now to add some disk space for these guests.

I'm attempting to create some new dasd for use by one of the zLinux
guests - LIN0501.  I've done these steps:

>From the MAINT machine on VM:
- ATT 829 *  (that's the correct unit address).
- Format that volume using CPFMTXA.  I called the volume LX0006.
- Edit the user directory and added this single line:  MDISK 503 3390
001 3338 lX0006 MR READ WRITE MULT
- DIRECTXA USER DIRECT to move the dir into memory.
- Logoff off LIN0501.
- Log on to LIN0501

When LIN0501 logs on I see this message:

HCPLNM108E LIN0501 0503 not linked; volid LX0006 not mounted

And, by extension, I can't see the volume with the YAST utility (I'm
using Suse) to format or partition the dasd.

I've tried various combinations of VARY OFF 829, DET 829, from the MAINT
id.  While the commands work, I still can't get LIN0501 to see the disk
when it logs on.

What complicates this further is that I have other LX00zz volumes that
are being properly mounted.   As I said before, we're new to VM (go easy
on me!) so I'm certain that I'm missing some steps in my process that
will hopefully become part of the routine,  but at this point I sure
don't know what those steps are.

Hopefully someone on the list will recognize the steps I'm missing and
enlighten me.  Fame and glory await....

Tim



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to