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.

Smith, Ann (ISD, IT) wrote:
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 [mailto:[EMAIL PROTECTED] Behalf Of *Clark, Carl
*Sent:* Monday, January 23, 2006 10:51 AM
*To:* [email protected]
*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



*************************************************************************
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.
*************************************************************************

--
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

Reply via email to