What Kris said is right.
The 2nd time through you already have the access so it appears to work
After you IPL or destroy your vswitch, it wouldn’t work on the first login.
Drove me crazy.
Of course, I hate Grants ☺



Marcy 

This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose, or take any action based on this message or any 
information herein. If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message. Thank you for 
your cooperation.

From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Tom Huegel
Sent: Tuesday, December 07, 2010 8:24 PM
To: [email protected]
Subject: Re: [IBMVM] Vswitch Grant as a CMD in User's Directory?

What seems to be the problem Lee? I did the same thing and it worked just fine. 
I don't believe the order really matters. I took it out of the directory and 
put it in AUTOLOG1 because in my case the LINUX guest may be logged on and off 
several times during a z/VM IPL. Although it worked fine it produced an error 
message every time (other than the first) time the guest logged on. I don't 
remember for sure, but I think I also defined the NIC via the CMD statement. 
Oh I just saw Kris's response.. I guess I did define the NIC via CMD..

I hope that helps.

 
On Tue, Dec 7, 2010 at 7:25 PM, Lee Stewart <[email protected]> 
wrote:
It seems to me...

Rather than putting a Vswitch Grant for each Linux guest somewhere like 
AUTOLOG1's PROFILE EXEC, I thought I'd try putting a
   CMD SET VSWITCH VSW1 GRANT &USERID
in the directory profile for the Linux guests...

Alas, it seems that the GRANT isn't processed till after the NIC / LAN 
connection is attempted.  I thought I understood that CMDs in the directory 
entry were processed before the user was logged on...

Did I misunderstand or???

Thanks,
Lee

-- 

Lee Stewart, Senior SE
Sirius Computer Solutions
Phone: (303) 996-7122
Email: [email protected]
Web:   www.siriuscom.com

Reply via email to