>From the z/Linux guest issue:  vmcp link * 120 120 M

        -----Original Message-----
        From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Vikesh Bhoola
        Sent: Friday, May 30, 2008 9:59 AM
        To: [email protected]
        Subject: Do we need to reIPL vm to add dasd ?
        
        

        NB: This email and its contents are subject to our email legal
notice. View <http://www.sars.gov.za/home.asp?pid=7>  our Disclaimer
        

        Dear Listers,

        We have experienced this for the second time & wondering if
perhaps we are doing something wrong here.

        Surely you don't need to reboot VM just to add dasd to a VM
guest (Linux - SLES10 SP1).

         

        Firstly, we are running VM v5.3.

         

        In SYSTEM CONFIG we have specified the following just to prevent
reIPLing VM just to add dasd:

            User_Volume_Include LNX*

         

        These are the steps I've followed :

         

        q a40e                                               

        DASD A40E SAA40E                                     

        I then initialised the volume as LNX015 using cpfmtxa &
thereafter detached it.

        q a40e          

        DASD A40E LNX015

         

        I then defined the MDISK under user SLES10X in USER DIRECT:

        MDISK 120 3390 0001 3338 LNX015 MR LNX4VM LNX4VM LNX4VM

         

        directxa user                                                

        z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 3.0 

        EOJ DIRECTORY UPDATED AND ON LINE                            

        HCPDIR494I User directory occupies 45 disk pages             

         

        cp q MDISK USER SLES10X 0120 DIRECT LOCATION

        HCPQMD040E Device 0120 does not exist   

         

        Issuing the following command in linux01 or SLES10X VM guest
does not reflect the added minidisk.

         

        linux01:~ #lsdasd   

        :

        0.0.0118(ECKD) at ( 94: 96) is dasdy      : active at blocksize
4096, 54000 blocks, 210 MB

        0.0.0119(ECKD) at ( 94:100) is dasdz      : active at blocksize
4096, 1802880 blocks, 7042 MB

         

        CP Q V DASD


        DASD 0100 3390 LNX002 R/W       3038 CYL ON DASD  A14D
SUBCHANNEL = 0000

        DASD 0102 3390 LNX002 R/W        300 CYL ON DASD  A14D
SUBCHANNEL = 0001

        DASD 0103 3390 LNX003 R/W       3333 CYL ON DASD  A140
SUBCHANNEL = 0002

        :

        DASD 0118 3390 LNX011 R/W        300 CYL ON DASD  A404
SUBCHANNEL = 0011

        DASD 0119 3390 LNX014 R/W      10016 CYL ON DASD  7F0A
SUBCHANNEL = 0012

        DASD 0190 3390 530RES R/O        107 CYL ON DASD  703B
SUBCHANNEL = 001A

         

        linux01:~ # lscss -t 3390

        Device   Subchan.  DevType CU Type Use  PIM PAM POM  CHPIDs

        
----------------------------------------------------------------------

        0.0.0100 0.0.0000  3390/0A 3990/E9 yes  F0  F0  FF   60616869
00000000

        0.0.0102 0.0.0001  3390/0A 3990/E9 yes  F0  F0  FF   60616869
00000000

        :

        0.0.0119 0.0.0012  3390/0C 3990/E9 yes  F0  F0  FF   62636A6B
00000000

        0.0.0190 0.0.001A  3390/0C 3990/E9      F0  F0  FF   62636A6B
00000000

         

        LOGON SLES10X                                               

        HCPLNM108E SLES10X 0120 not linked; volid LNX015 not mounted

         

        I'm sure we are overlooking something here. Does anyone know
what we missing here to prevent an IPL of VM just to add dasd.

         

        Your assistance is very much appreciated...

         

        Kind regards,

        Vikesh Bhoola
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or 
proprietary, and if you are not an intended recipient, please notify the 
sender, do not use or share it and delete it. Unless specifically indicated, 
this message is not an offer to sell or a solicitation of any investment 
products or other financial product or service, an official confirmation of any 
transaction, or an official statement of Merrill Lynch. Subject to applicable 
law, Merrill Lynch may monitor, review and retain e-communications (EC) 
traveling through its networks/systems. The laws of the country of each 
sender/recipient may impact the handling of EC, and EC may be archived, 
supervised and produced in countries other than the country in which you are 
located. This message cannot be guaranteed to be secure or error-free. This 
message is subject to terms available at the following link: 
http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you 
consent to the foregoing.
--------------------------------------------------------

Reply via email to