Re: FW: VM TCPIP (A Little Off Topic)
An interesting finding and a question; you use the term must with respect to configuring the PORTNAME option of DEFINE VSWITCH when it appears to be optional parameter. I might be taking this out of context as the statements made only refer to the placement of the PORTNAME parameter (PORTNAME must be the last parameter) but it reads like this parameter is not optional. I find that it really isn't necessary to address the port name when defining a functional switch but it might be prudent to do so. Is there any situation that you can think of where not addressing the OSA port name in the switch definition might trip someone up? This, while a little misleading, is not incorrect. The portname, while optional, MUST be the last parameter if it is specified. Not specifying the portname should not cause any problems, and is probably the better way to go. That way if someone changes it on some other system using the device, it won't break the VSWITCH's ability to use the OSA. Also, when configuring the TCPIP service machines to autolog, I find it helpful to put the MODIFY VSWITCH GRANT statements in SYSTEM CONFIG instead of using CP SET VSWITCH GRANT from the profile of AUTOLOG1. This saved me a lot of typing yesterday when AUTOLOG1 didn't start forcing me to manually start the Controller service machines (still researching why AUTOLOG1 didn't start). You do make mention of configuring access to the switch through CP SET VSWITCH but not through MODIFY. Do you see a disadvantage to making use of MODIFY from SYSTEM CONFIG in this manner? The SYSTEM CONFIG file is the better place to grant access. Regards, Miguel Diaz Staff Software Engineer TCP/IP for z/VM -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: VM TCPIP (A Little Off Topic)
On Friday, 05/21/2004 at 11:54 AST, Miguel Diaz/Endicott/[EMAIL PROTECTED] wrote: The SYSTEM CONFIG file is the better place to grant access. Until, of course, you get z/VM 5.1. Then you'll use your ESM (e.g. RACF) to grant access!! Alan Altmark Sr. Software Engineer IBM z/VM Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: VM TCPIP (A Little Off Topic)
At what point did it become optional to specify a port name? Alan Altmark [EMAIL PROTECTED] ibm.com To Sent by: Linux on [EMAIL PROTECTED] 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: FW: VM TCPIP (A Little Off Topic) 05/21/2004 11:50 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU On Friday, 05/21/2004 at 11:54 AST, Miguel Diaz/Endicott/[EMAIL PROTECTED] wrote: The SYSTEM CONFIG file is the better place to grant access. Until, of course, you get z/VM 5.1. Then you'll use your ESM (e.g. RACF) to grant access!! Alan Altmark Sr. Software Engineer IBM z/VM Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: VM TCPIP (A Little Off Topic)
OSA microcode level 3.33 Linux Driver 3G EC stream J11204 MCL032 z/VM 4.3 with APARs VM63308 and PQ73878 z/VM 4.4 base It is still required for z/OS Regards, Miguel Diaz Staff Software Engineer TCP/IP for z/VM Linux on 390 Port [EMAIL PROTECTED] wrote on 05/21/2004 02:56:41 PM: At what point did it become optional to specify a port name? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: VM TCPIP (A Little Off Topic)
On Friday, 05/21/2004 at 01:56 EST, James Melin [EMAIL PROTECTED] wrote: At what point did it become optional to specify a port name? Since October 1, 2003. See my post at http://www2.marist.edu/htbin/wlvtype?LINUX-390.41397 (Also posted to VMESA-L the same day.) Alan Altmark Sr. Software Engineer IBM z/VM Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: VM TCPIP (A Little Off Topic)
On Mon, 2004-05-17 at 13:34, ODOT zSeries Linux wrote: If you want to shoot me for being off-topic I'll understand and take my punishment. But if anyone is feeling tolerant I'd very much appreciate any pointers to White (or Red) paper about configuring a secondary TCPIP stack in VM 4.40. I'm getting through it slowly but I'm also getting the feeling that I might be making it more difficult than it really is. You may be, because I don't remember anything being especially tough about it; you pretty much create a new userid with the same privileges, duplicate and modify PROFILE TCPIP and TCPIP DTCPARMS, and away you go, as I recall. I remember it as being relatively painless. Where are you encountering difficulty? Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: VM TCPIP (A Little Off Topic)
Thanks Adam. I think my current struggle is in understanding the steps needed to implement a new service machine running TCPIP and keeping them seperated. The information on TCPIP config in Planning and Customization is pretty voluminous and I'm having difficulty creating a task list from it. It's really just a (my) problem researching these details and I had hoped there was something like a laundry list of tasks for the VM newbee. Thanks for the reply though, I think my fears (of making it more difficult than it is)have just been realized after reading your post. I'll keep digging, sorry for drifting off-topic. Steve -Original Message- From: Adam Thornton [mailto:[EMAIL PROTECTED] Sent: Monday, May 17, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: Re: FW: VM TCPIP (A Little Off Topic) On Mon, 2004-05-17 at 13:34, ODOT zSeries Linux wrote: If you want to shoot me for being off-topic I'll understand and take my punishment. But if anyone is feeling tolerant I'd very much appreciate any pointers to White (or Red) paper about configuring a secondary TCPIP stack in VM 4.40. I'm getting through it slowly but I'm also getting the feeling that I might be making it more difficult than it really is. You may be, because I don't remember anything being especially tough about it; you pretty much create a new userid with the same privileges, duplicate and modify PROFILE TCPIP and TCPIP DTCPARMS, and away you go, as I recall. I remember it as being relatively painless. Where are you encountering difficulty? Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: VM TCPIP (A Little Off Topic)
On Mon, 17 May 2004 [EMAIL PROTECTED] wrote: I think my current struggle is in understanding the steps needed to implement a new service machine running TCPIP and keeping them seperated. Steve, I discussed this in the VSWITCH and VLAN Redpaper which you can find at: http://www.redbooks.ibm.com/abstracts/redp3719.html I'd be keen to hear what you think of it, so please let me know or use the feedback e-mail address on the Redbooks site. Cheers, Vic Cross -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
