3rd level Linux testing, attaching DASD

Discussion:

(too old to reply)

Clark, Carl

2006-01-23 15:51:03 UTC

VM enthusiasts:

Have any of you installed a 3nd level Linux? We are trying to install Linux as a guest to a second level z/VM v5.1 test system and the current problem is that the 3rd level user (Linux) cannot see the dasd device with volser LNX032 as shown in the msg log:

LOGON LNX032
HCPLNM108E LNX032 0191 not linked; volid LNX032 not mounted
HCPLNM108E LNX032 0201 not linked; volid LNX032 not mounted
HCPLNM108E LNX032 0202 not linked; volid LNX032 not mounted
NIC 0600 is created; devices 0600-0602 defined
HCPNDF2787E NIC 0600 not connected; LAN SYSTEM VSW1 does not exist
z/VM Version 5 Release 1.0, Service Level 0502 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: NO RDR, NO PRT, NO PUN
LOGON AT 10:43:50 EST MONDAY 01/23/06
z/VM V5.1.0 2005-12-15 17:26

Your help is appreciated,
Carl Clark
BCBST
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm

Rich Smrcina

2006-01-23 15:57:06 UTC

Permalink

The volume LNX032 has to be available to the second level VM system and
it has to be in the User_Volume list.

Post by Clark, Carl
Have any of you installed a 3nd level Linux? We are trying to
install Linux as a guest to a second level z/VM v5.1 test system and the
current problem is that the 3rd level user (Linux) cannot see the dasd
LOGON LNX032
HCPLNM108E LNX032 0191 not linked; volid LNX032 not mounted
HCPLNM108E LNX032 0201 not linked; volid LNX032 not mounted
HCPLNM108E LNX032 0202 not linked; volid LNX032 not mounted
NIC 0600 is created; devices 0600-0602 defined
HCPNDF2787E NIC 0600 not connected; LAN SYSTEM VSW1 does not exist
z/VM Version 5 Release 1.0, Service Level 0502 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: NO RDR, NO PRT, NO PUN
LOGON AT 10:43:50 EST MONDAY 01/23/06
z/VM V5.1.0 2005-12-15 17:26
Your help is appreciated,
Carl Clark
BCBST
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm

Steve Gentry

2006-01-23 16:47:40 UTC

Permalink

Yes, I have,I didn't have any problems. Response was a bit poor though.
But that was to be expected.
Steve

"Clark, Carl" <***@BCBST.com>
Sent by: VM/ESA and z/VM Discussions <VMESA-***@LISTSERV.UARK.EDU>
01/23/2006 10:51 AM
Please respond to VM/ESA and z/VM Discussions

To: VMESA-***@LISTSERV.UARK.EDU
cc:
Subject: 3rd level Linux testing, attaching DASD

VM enthusiasts:
Have any of you installed a 3nd level Linux? We are trying to install
Linux as a guest to a second level z/VM v5.1 test system and the current
problem is that the 3rd level user (Linux) cannot see the dasd device with
volser LNX032 as shown in the msg log:
LOGON LNX032
HCPLNM108E LNX032 0191 not linked; volid LNX032 not mounted
HCPLNM108E LNX032 0201 not linked; volid LNX032 not mounted
HCPLNM108E LNX032 0202 not linked; volid LNX032 not mounted
NIC 0600 is created; devices 0600-0602 defined
HCPNDF2787E NIC 0600 not connected; LAN SYSTEM VSW1 does not exist
z/VM Version 5 Release 1.0, Service Level 0502 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: NO RDR, NO PRT, NO PUN
LOGON AT 10:43:50 EST MONDAY 01/23/06
z/VM V5.1.0 2005-12-15 17:26

Your help is appreciated,
Carl Clark
BCBST
Please see the following link for the BlueCross BlueShield of Tennessee
E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm

Clark, Carl

2006-01-23 18:30:35 UTC

Permalink

That didn't help. I still receive the same message The vol is available to the 2nd level test before it's IPL, then is available to Operator and Maint users after the IPL.

Is there a way to determine if this vol was actually added to the User_Volume List?

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU]On
Behalf Of Rich Smrcina
Sent: Monday, January 23, 2006 10:57 AM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: Re: 3rd level Linux testing, attaching DASD

The volume LNX032 has to be available to the second level VM system and
it has to be in the User_Volume list.

--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com

Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm

Rich Smrcina

2006-01-23 18:24:45 UTC

Permalink

Issue Q DASD, see if it is in the list and check the SYSTEM CONFIG on
the second level system.

Post by Clark, Carl
That didn't help. I still receive the same message The vol is available to the 2nd level test before it's IPL, then is available to Operator and Maint users after the IPL.
Is there a way to determine if this vol was actually added to the User_Volume List?
-----Original Message-----
Behalf Of Rich Smrcina
Sent: Monday, January 23, 2006 10:57 AM
Subject: Re: 3rd level Linux testing, attaching DASD
The volume LNX032 has to be available to the second level VM system and
it has to be in the User_Volume list.

Steve Gentry

2006-01-23 18:47:04 UTC

Permalink

How are you making the volume available to the 3rd level? ATTACH? LINK?
DEDICATE?
And, respectfully, from my point of view, I wouldn't call it 3rd level.
When I run VM 1st level, I don't
refer to Linux as running 2nd level. With vm at 1st level I'd just refer
to it as running as a guest.
Are you perhaps thinking you are running it 3rd level but in reality is it
a guest to the 2nd level machine?
I know it's a point of view, but I was just checking.

Steve G.

Clark, Carl

2006-01-23 18:44:42 UTC

Permalink

I only changed the system config on the 2nd level VM. SHould I change the host config file too?

When logged on the 3rd level linux a q dasd shows this: (505C is the device not reachable)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
q dasd all
HCPQVC022E A virtual device number was not supplied or it was invalid.
Ready(00022); T=0.01/0.01 13:39:50
q dasd
DASD 0190 3390 510RES R/O 107 CYL ON DASD 5060 SUBCHANNEL = 0007
DASD 019D 3390 510W01 R/O 146 CYL ON DASD 5061 SUBCHANNEL = 0008
DASD 019E 3390 510W01 R/O 250 CYL ON DASD 5061 SUBCHANNEL = 0009
DASD 0592 3390 510W01 R/O 67 CYL ON DASD 5061 SUBCHANNEL = 000A
Ready; T=0.01/0.01 13:39:53
q 505c
HCPQVD040E Device 505C does not exist
Ready(00040); T=0.01/0.01 13:40:22
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

When logged on to the 3rd level maint user the q dasd shows this:

q dasd
DASD 5060 CP OWNED 510RES 42
DASD 5061 CP OWNED 510W01 37
DASD 5062 CP OWNED 510W02 1
DASD 5063 CP OWNED 510SPL 1
DASD 5064 CP OWNED 510PAG 0
Ready; T=0.01/0.01 13:41:50
q dasd all
DASD 5060 CP OWNED 510RES 42
DASD 5061 CP OWNED 510W01 37
DASD 5062 CP OWNED 510W02 1
DASD 5063 CP OWNED 510SPL 1
DASD 5064 CP OWNED 510PAG 0
DASD 0190 MNT190 , DASD 0191 VDISKA , DASD 019D MNT19D , DASD 019E MNT19E
DASD 505C LNX032 , DASD 5D2D MNTSVC
An offline DASD was not found.
Ready; T=0.01/0.01 13:41:56
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Thanks for your ideas.

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU]On
Behalf Of Rich Smrcina
Sent: Monday, January 23, 2006 1:25 PM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: Re: 3rd level Linux testing, attaching DASD

Issue Q DASD, see if it is in the list and check the SYSTEM CONFIG on
the second level system.

Smith, Ann (ISD, IT)

2006-01-23 21:59:06 UTC

Permalink

This post might be inappropriate. Click to display it.

Rich Smrcina

2006-01-24 02:23:34 UTC

Permalink

You certainly have to do whatever is comfortable for you, but if you
have consistent naming you can use the User_Volume_Include directive in
SYSTEM CONFIG.

I have a customer with two LPARs, the user volumes are VM1xxx (for
LPAR1) and VM2xxx (for LPAR2). The SYSTEM CONFIG files have:

User_Volume_Include VM1*

for LPAR1 and

User_Volume_Include VM2*

for LPAR2. This way I don't have to update either SYSTEM CONFIG or a
PROFILE EXEC if a new volume were to be added to either system.

Post by Smith, Ann (ISD, IT)
We do run a couple of linux guests on a second level VM system. We use
DEDICATE statements in the directory for the second level VM guest.
On the second level VM system, we have automated the CP ATTACH xxxx TO
SYSTEM commands(part of AUTOLOG1's tasks). I think you need to do the
CP ATTACH xxxx TO SYSTEM prior to bringing up the linux guest. It looks
like your dasd volume has the same name as the guest userid. Maybe a
naming standard you are using? In any case, try attaching the LNX032
dasd to the system from MAINT or OPERATOR prior to logging onto the
LNX032 id.
[Smith, Ann (ISD, IT)]
-----Original Message-----
*From:* VM/ESA and z/VM Discussions
*Sent:* Monday, January 23, 2006 10:51 AM
*Subject:* 3rd level Linux testing, attaching DASD
Have any of you installed a 3nd level Linux? We are trying to
install Linux as a guest to a second level z/VM v5.1 test system and
the current problem is that the 3rd level user (Linux) cannot see
LOGON LNX032
HCPLNM108E LNX032 0191 not linked; volid LNX032 not mounted
HCPLNM108E LNX032 0201 not linked; volid LNX032 not mounted
HCPLNM108E LNX032 0202 not linked; volid LNX032 not mounted
NIC 0600 is created; devices 0600-0602 defined
HCPNDF2787E NIC 0600 not connected; LAN SYSTEM VSW1 does not exist
z/VM Version 5 Release 1.0, Service Level 0502 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: NO RDR, NO PRT, NO PUN
LOGON AT 10:43:50 EST MONDAY 01/23/06
z/VM V5.1.0 2005-12-15 17:26
Your help is appreciated,
Carl Clark
BCBST
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************

Jeff Gribbin, EDS

2006-01-24 08:14:00 UTC

Permalink

This post might be inappropriate. Click to display it.

Clark, Carl

2006-01-24 16:03:15 UTC

Permalink

This may be the problem. I thought only an mdisk entry was needed in the 2nd level user direct.

Thanks to all of you for your great responses. Also, Jeff Gribbin's comments are very helpful, at this point I'm considering a dedicate statement in the 2nd level user direct .

Steve G. , thanks for the correction about "3rd level", I agree now. I will post back the conclusion at end of day.

Carl Clark

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU]On Behalf Of Steve Gentry
Sent: Monday, January 23, 2006 1:47 PM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: Re: 3rd level Linux testing, attaching DASD

How are you making the volume available to the 3rd level? ATTACH? LINK? DEDICATE?
And, respectfully, from my point of view, I wouldn't call it 3rd level. When I run VM 1st level, I don't
refer to Linux as running 2nd level. With vm at 1st level I'd just refer to it as running as a guest.
Are you perhaps thinking you are running it 3rd level but in reality is it a guest to the 2nd level machine?
I know it's a point of view, but I was just checking.

Steve G.

Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm