Someone commented that it was somewhat "clunky", but what we've been doing for the grants is to add two COMMAND statements to each guest's CP Directory entry (actually via an include); the first does the grant for the user, and the second does a couple to connect up the vSwitch, if it isn't already connected.
Before this, each new Linux guest had to be added to either the SYSTEM CONFIG (problematic) or AUTOLOG1 (time consuming), and either method allows the person doing it to forget, make a mistake or make some typo in the addition that could cause problems much later during the next IPL, at which time it will take at least a short time to diagnose and repair. Having the whole thing taken care of in one entry in the CP Directory, and included in each guest that needs it, is much less prone to any errors someone (such as me) might tend to make. It's one less thing to remember when creating a new Linux guest. -- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 5/20/08 10:40 AM, "Ponte, Doug" <[EMAIL PROTECTED]> wrote: > You could also add the SET VSWITCH xxxxxxxx GRANT statements to AUTOLOG1's > profile (prior to RACF/VM or your ESM's autologging, as TCPIP and such should > be autologged in AUTOLOG2 profile exec in that case) OR you could add a > profile for the GRANT statements via RACF/VM or your ESM if you have one and > are really tight on security requirements. > > Doug > > > -----Original Message----- > From: The IBM z/VM Operating System on behalf of Hodge, Robert L > Sent: Fri 16-May-08 18:45 > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: VSWITCH question > > XAUTOLOG the VSWITCH controller userids; typically DTCVSW1 and DTCVSW2. > > Add the the XAUTOLOG of DTCVSW1 and DTCVSW2 to the PROFILE EXEC on the > A-disk on AUTOLOG1 or AUTOLOG2 for the next IPL of the z/VM system. > > Add define and modify statements to the z/VM SYSTEM CONFIG for the next > time z/VM is IPL'ed. > > DEFINE VSWITCH SWITCH1 RDEV devno CONNECT > > MODIFY VSWITCH SWITCH1 GRANT userid > > ________________________________ > > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Daniel Allen > Sent: Friday, May 16, 2008 4:21 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: VSWITCH question > > > I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA > addresses. The OS/390 guest is IPL'd using the system residence pack. > > I would like to have the OS/390 guest use a z/VM VSWITCH. > > I have a copyrighted 2004 IBM Corporation document showing four (4) > steps. > > Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno > CONNECT > > Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid > > Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 > > Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 > > I have done steps 1 and 2 manually. > > I have put a NICDEF statement in the USER DIRECT file for the OS/390 > guest: > > NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 > > Is there anything else I need to do ? > > > > > > ********************************************************************** > > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they are > addressed. Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please contact the > sender by reply e-mail and destroy all copies of the original message. > > ********************************************************************** > >
