NB: This email and its contents are subject to our email legal notice
which can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf

----
Thanks for the prompt responses.
I've tried ATT A40E SYSTEM with no luck :
DASD A40E ATTACHED TO SYSTEM LNX015 PAV BASE

When I display under linux01, it still does not show minidisk 0120 :
lscss -t 3390
Device   Subchan.  DevType CU Type Use  PIM PAM POM  CHPIDs
----------------------------------------------------------------------
:
0.0.0118 0.0.0011  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

I've even tried attaching to SLES10X (vm guest name), but then does not
map to minidisk 120 :
lscss -t 3390
Device   Subchan.  DevType CU Type Use  PIM PAM POM  CHPIDs
----------------------------------------------------------------------
0.0.A40E 0.0.0022  3390/0A 3990/E9      F0  F0  FF   60616869 00000000

Not sure if this is correct or not.

Apologies for my ignorance on this..
James, when I tried vmcp I get an error (Error: Could not open device
/dev/vmcp: No such file or directory), so issue from VM guest :
#CP LINK * 120 120 M                                          
HCPLNM108E SLES10X 0120 not linked; volid LNX015 not mounted

Kind Regards,
Vikesh Bhoola


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Rich Smrcina
Sent: 30 May 2008 04:08 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Do we need to reIPL vm to add dasd ?

Vikesh,

Surely not... the one step that is missing is

ATT A40E SYSTEM

After you clip the label.  When VM IPLs all DASD that have that match 
the labels in the User_Volume_Label tags are attached to system in a 
similar fashion automatically.

Vikesh Bhoola wrote:
> 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
> 

-- 
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service:  360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com/in/richsmrcina

Catch the WAVV!  http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009

Reply via email to