Re: VSWITCH initial startup
My guess is that you copied your existing TCPIP profile for your VSWITCH CONTROLLERS .. It is a case of too much information. The profiles for the controllers is very simple. The only entry you NEED in their profile is VSWITCH CONTROLLER ON... Here is what my profiles for the controllers look like. NOTRACE OSD INFORM TCPMAINT MAINT ENDINFORM ASSORTEDPARMS PERMITTEDUSERSONLY VMDUMP ENDASSORTEDPARMS OBEY TCPMAINT MAINT ENDOBEY VSWITCH CONTROLLER ON A note: The way I do it is to leave the profiles on TCPMAINT's 198 disk and name them VSWCTRL1 TCPIP and VSWCTRL2 TCPIP. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 6:05 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VSWITCH initial startup i am attempting to set up a new VSWITCH. i followed the instructions in the pdf z/VM VSWITCH with failover (with cursory glances at Alan Admarks presentation on HA and automatic network failover using VSWITCH) so, per the book, i have two VSWITCH controllers in USER DIRECT : VSWCTRL1 VSWCTRL2 with appropriate links to TCPMAINT and their own 191 disks, etc. i've logged on to them and formated their 191 A disks and copied over TCPIPMESSAGE PROFILE TCPERROR VMSESPARTCAT PROFILE EXEC from TCPIP's 191 disk and set up PROFILE TCPIP on their A disk with VSWITCH CONTROLLER ON specified. i've added the controllers to TCPMAINT's SYSTEM DCTPARMS: :nick.VSWCTRL1 :type.server :class.stack :exit.VSWCTRL :nick.VSWCTRL2 :type.server :class.stack :exit.VSWCTRL I have defined the VSWITCH: define vswitch vsw1 rdev 500 1000 then the fun begins. when i log on to VSWCTRL1 , it tries to do a COUPLE. i cannot figure out what is causing this to happen: DMSACP723I D (198) R/O DMSACP723I E (591) R/O DMSACP723I F (592) R/O Ready; T=0.01/0.01 18:01:10 DTCRUN1022I Console log will be sent to user TCPMAINT 18:01:10 DTCRUN1026I TCPRUNXT EXEC (SETUP) returned :Owner.MAINT 18:01:10 DMSCPY721I Copy VSWCTRL1 TCPIP D1 to PROFILE TCPIP A1 (old file) 18:01:10 DTCRUN1022I Console log will be sent to user MAINT 18:01:10 CTCA 0D09 DEFINED 18:01:10 HCPCPL058E CTCA 0674 busy on SP4 18:01:10 DTCRUN1001W CP COUPLE D09 SP4 0674 failed with return code 58 18:01:10 DTCRUN1026I TCPRUNXT EXEC (BEGIN) returned :Owner.MAINT 18:01:10 DTCRUN1021R To cancel TCP/IP Stack startup, type any non-blank characte r and 18:01:10 press ENTER. To continue startup, just press ENTER. the COUPLE is one that we use on TCPIP to route IP traffic from one of our VSEs why is VSWCTRL1 trying to COUPLE to my VSE? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL _ ella for Spam Control has removed 12946 VSE-List messages and set aside 12180 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com http://www.ellaforspam.com
Re: VSWITCH initial startup
Well then nothing jumps out at me.. Here is my directory entry, maybe there is something there. It still looks like somehow you are picking up the wrong configuration file. USER DTCVSW2 xxx 32M 128M G INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 IUCV *VSWITCH MSGLIMIT 65535 LINK 5VMTCP20 491 491 RR LINK 5VMTCP20 492 492 RR LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 2835 005 520W01 MR x x x -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 20, 2007 9:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH initial startup Thomas, here is my PROFILE TCPIP (straight out of the Failover document): NOTRACE ALL OBEY OPERATOR TCPMNT44 MAINT ENDOBEY VSWITCH CONTROLLER ON i also have them set up on TCPMAINT's 198 - again, per the Failover doc. i assume that is so that all the configuration is kept on TCPMAINT, is that the reason? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 05:53:37 AM: My guess is that you copied your existing TCPIP profile for your VSWITCH CONTROLLERS .. It is a case of too much information. The profiles for the controllers is very simple. The only entry you NEED in their profile is VSWITCH CONTROLLER ON... Here is what my profiles for the controllers look like. NOTRACE OSD INFORM TCPMAINT MAINT ENDINFORM ASSORTEDPARMS PERMITTEDUSERSONLY VMDUMP ENDASSORTEDPARMS OBEY TCPMAINT MAINT ENDOBEY VSWITCH CONTROLLER ON A note: The way I do it is to leave the profiles on TCPMAINT's 198 disk and name them VSWCTRL1 TCPIP and VSWCTRL2 TCPIP. _ ella for Spam Control has removed 12951 VSE-List messages and set aside 12189 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com http://www.ellaforspam.com
Re: VSWITCH initial startup
Thomas, here is my PROFILE TCPIP (straight out of the Failover document): NOTRACE ALL OBEY OPERATOR TCPMNT44 MAINT ENDOBEY VSWITCH CONTROLLER ON i also have them set up on TCPMAINT's 198 - again, per the Failover doc. i assume that is so that all the configuration is kept on TCPMAINT, is that the reason? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 05:53:37 AM: My guess is that you copied your existing TCPIP profile for your VSWITCH CONTROLLERS .. It is a case of too much information. The profiles for the controllers is very simple. The only entry you NEED in their profile is VSWITCH CONTROLLER ON... Here is what my profiles for the controllers look like. NOTRACE OSD INFORM TCPMAINT MAINT ENDINFORM ASSORTEDPARMS PERMITTEDUSERSONLY VMDUMP ENDASSORTEDPARMS OBEY TCPMAINT MAINT ENDOBEY VSWITCH CONTROLLER ON A note: The way I do it is to leave the profiles on TCPMAINT's 198 disk and name them VSWCTRL1 TCPIP and VSWCTRL2 TCPIP.
Re: VSWITCH initial startup
What does your SYSTEM DTCPARMS on TCPMAINT show? David From: The IBM z/VM Operating System on behalf of Huegel, Thomas Sent: Thu 9/20/2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup Well then nothing jumps out at me.. Here is my directory entry, maybe there is something there. It still looks like somehow you are picking up the wrong configuration file. USER DTCVSW2 xxx 32M 128M G INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 IUCV *VSWITCH MSGLIMIT 65535 LINK 5VMTCP20 491 491 RR LINK 5VMTCP20 492 492 RR LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 2835 005 520W01 MR x x x -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 20, 2007 9:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH initial startup Thomas, here is my PROFILE TCPIP (straight out of the Failover document): NOTRACE ALL OBEY OPERATOR TCPMNT44 MAINT ENDOBEY VSWITCH CONTROLLER ON i also have them set up on TCPMAINT's 198 - again, per the Failover doc. i assume that is so that all the configuration is kept on TCPMAINT, is that the reason? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 05:53:37 AM: My guess is that you copied your existing TCPIP profile for your VSWITCH CONTROLLERS .. It is a case of too much information. The profiles for the controllers is very simple. The only entry you NEED in their profile is VSWITCH CONTROLLER ON... Here is what my profiles for the controllers look like. NOTRACE OSD INFORM TCPMAINT MAINT ENDINFORM ASSORTEDPARMS PERMITTEDUSERSONLY VMDUMP ENDASSORTEDPARMS OBEY TCPMAINT MAINT ENDOBEY VSWITCH CONTROLLER ON A note: The way I do it is to leave the profiles on TCPMAINT's 198 disk and name them VSWCTRL1 TCPIP and VSWCTRL2 TCPIP. ella for Spam Control has removed 12951 VSE-List messages and set aside 12189 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com
Re: VSWITCH initial startup
i added these lines to SYSTEM DTCPARMS: :nick.VSWCTRL1 :type.server :class.stack :exit.VSWCTRL :nick.VSWCTRL2 :type.server :class.stack :exit.VSWCTRL there is a section earlier with: .** Application Class Definitions .* TCP/IP Protocol Stack :nick.stack :type.class :name.TCP/IP Stack :command.TCPIP :runtime.PASCAL :diskwarn.YES ... (a bunch of other CTCAs deleted here) :vCTC.C02 SP2TEST 0C03 :vCTC.C03 SP2TEST 0C02 :vCTC.D08 SP4 0675 :vCTC.D09 SP4 0674 :authlog.AUTHLOG FILE A is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? can i have a separate DCTPARMS just for my VSWITCH controllers ? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 10:50:19 AM: What does your SYSTEM DTCPARMS on TCPMAINT show? David From: The IBM z/VM Operating System on behalf of Huegel, Thomas Sent: Thu 9/20/2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup Well then nothing jumps out at me.. Here is my directory entry, maybe there is something there. It still looks like somehow you are picking up the wrong configuration file. USER DTCVSW2 xxx 32M 128M G INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 IUCV *VSWITCH MSGLIMIT 65535 LINK 5VMTCP20 491 491 RR LINK 5VMTCP20 492 492 RR LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 2835 005 520W01 MR x x x -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 20, 2007 9:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH initial startup Thomas, here is my PROFILE TCPIP (straight out of the Failover document): NOTRACE ALL OBEY OPERATOR TCPMNT44 MAINT ENDOBEY VSWITCH CONTROLLER ON i also have them set up on TCPMAINT's 198 - again, per the Failover doc. i assume that is so that all the configuration is kept on TCPMAINT, is that the reason? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 05:53:37 AM: My guess is that you copied your existing TCPIP profile for your VSWITCH CONTROLLERS .. It is a case of too much information. The profiles for the controllers is very simple. The only entry you NEED in their profile is VSWITCH CONTROLLER ON... Here is what my profiles for the controllers look like. NOTRACE OSD INFORM TCPMAINT MAINT ENDINFORM ASSORTEDPARMS PERMITTEDUSERSONLY VMDUMP ENDASSORTEDPARMS OBEY TCPMAINT MAINT ENDOBEY VSWITCH CONTROLLER ON A note: The way I do it is to leave the profiles on TCPMAINT's 198 disk and name them VSWCTRL1 TCPIP and VSWCTRL2 TCPIP. ella for Spam Control has removed 12951 VSE-List messages and set aside 12189 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com
Re: VSWITCH initial startup
OK. What release of z/vm are you running? I think we should simplify - get rid of the VSWCTRL exec first of all. Remove the :exit.VSWCTRL statement from SYSTEM DTCPARMS. As long as you the files VSWCTRL1 TCPIP and VSWCTRL2 on TCPMAINT 198 when those machines are IPLed they will find the right files. The doc you reference goes back to zvm42 and indeed the search order for locating the correct profile to use was different. In zvm520 onwards (maybe zvm510??) you can use the name of the machine as a profile name. Try that. David From: The IBM z/VM Operating System on behalf of [EMAIL PROTECTED] Sent: Thu 9/20/2007 12:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup i added these lines to SYSTEM DTCPARMS: :nick.VSWCTRL1 :type.server :class.stack :exit.VSWCTRL :nick.VSWCTRL2 :type.server :class.stack :exit.VSWCTRL there is a section earlier with: .** Application Class Definitions .* TCP/IP Protocol Stack :nick.stack :type.class :name.TCP/IP Stack :command.TCPIP :runtime.PASCAL :diskwarn.YES ... (a bunch of other CTCAs deleted here) :vCTC.C02 SP2TEST 0C03 :vCTC.C03 SP2TEST 0C02 :vCTC.D08 SP4 0675 :vCTC.D09 SP4 0674 :authlog.AUTHLOG FILE A is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? can i have a separate DCTPARMS just for my VSWITCH controllers ? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 10:50:19 AM: What does your SYSTEM DTCPARMS on TCPMAINT show? David From: The IBM z/VM Operating System on behalf of Huegel, Thomas Sent: Thu 9/20/2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup Well then nothing jumps out at me.. Here is my directory entry, maybe there is something there. It still looks like somehow you are picking up the wrong configuration file. USER DTCVSW2 xxx 32M 128M G INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 IUCV *VSWITCH MSGLIMIT 65535 LINK 5VMTCP20 491 491 RR LINK 5VMTCP20 492 492 RR LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 2835 005 520W01 MR x x x -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 20, 2007 9:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH initial startup Thomas, here is my PROFILE TCPIP (straight out of the Failover document): NOTRACE ALL OBEY OPERATOR TCPMNT44 MAINT ENDOBEY VSWITCH CONTROLLER ON i also have them set up on TCPMAINT's 198 - again, per the Failover doc. i assume that is so that all the configuration is kept on TCPMAINT, is that the reason? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 05:53:37 AM: My guess is that you copied your existing TCPIP profile for your VSWITCH CONTROLLERS .. It is a case of too much information. The profiles for the controllers is very simple. The only entry you NEED in their profile is VSWITCH CONTROLLER ON... Here is what my profiles for the controllers look like. NOTRACE OSD INFORM TCPMAINT MAINT ENDINFORM ASSORTEDPARMS PERMITTEDUSERSONLY VMDUMP ENDASSORTEDPARMS OBEY TCPMAINT MAINT ENDOBEY VSWITCH CONTROLLER ON A note: The way I do it is to leave the profiles on TCPMAINT's 198 disk and name them VSWCTRL1 TCPIP and VSWCTRL2 TCPIP. ella for Spam Control has removed 12951 VSE-List messages and set aside 12189 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com
Re: VSWITCH initial startup
Isn't it 5.2 that you are provided with running vswitch controllers out of the box - no instructions necessary -just bring them up? Marcy Cortes 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. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Kreuter Sent: Thursday, September 20, 2007 9:30 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup OK. What release of z/vm are you running? I think we should simplify - get rid of the VSWCTRL exec first of all. Remove the :exit.VSWCTRL statement from SYSTEM DTCPARMS. As long as you the files VSWCTRL1 TCPIP and VSWCTRL2 on TCPMAINT 198 when those machines are IPLed they will find the right files. The doc you reference goes back to zvm42 and indeed the search order for locating the correct profile to use was different. In zvm520 onwards (maybe zvm510??) you can use the name of the machine as a profile name. Try that. David From: The IBM z/VM Operating System on behalf of [EMAIL PROTECTED] Sent: Thu 9/20/2007 12:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup i added these lines to SYSTEM DTCPARMS: :nick.VSWCTRL1 :type.server :class.stack :exit.VSWCTRL :nick.VSWCTRL2 :type.server :class.stack :exit.VSWCTRL there is a section earlier with: .** Application Class Definitions .* TCP/IP Protocol Stack :nick.stack :type.class :name.TCP/IP Stack :command.TCPIP :runtime.PASCAL :diskwarn.YES ... (a bunch of other CTCAs deleted here) :vCTC.C02 SP2TEST 0C03 :vCTC.C03 SP2TEST 0C02 :vCTC.D08 SP4 0675 :vCTC.D09 SP4 0674 :authlog.AUTHLOG FILE A is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? can i have a separate DCTPARMS just for my VSWITCH controllers ? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 10:50:19 AM: What does your SYSTEM DTCPARMS on TCPMAINT show? David From: The IBM z/VM Operating System on behalf of Huegel, Thomas Sent: Thu 9/20/2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup Well then nothing jumps out at me.. Here is my directory entry, maybe there is something there. It still looks like somehow you are picking up the wrong configuration file. USER DTCVSW2 xxx 32M 128M G INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 IUCV *VSWITCH MSGLIMIT 65535 LINK 5VMTCP20 491 491 RR LINK 5VMTCP20 492 492 RR LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 2835 005 520W01 MR x x x -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 20, 2007 9:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH initial startup Thomas, here is my PROFILE TCPIP (straight out of the Failover document): NOTRACE ALL OBEY OPERATOR TCPMNT44 MAINT ENDOBEY VSWITCH CONTROLLER ON i also have them set up on TCPMAINT's 198 - again, per the Failover doc. i assume that is so that all the configuration is kept on TCPMAINT, is that the reason? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 05:53:37 AM: My guess is that you copied your existing TCPIP profile for your VSWITCH CONTROLLERS .. It is a case of too much information. The profiles for the controllers is very simple. The only entry you NEED in their profile is VSWITCH CONTROLLER ON... Here is what my profiles for the controllers look like. NOTRACE OSD INFORM TCPMAINT MAINT ENDINFORM ASSORTEDPARMS PERMITTEDUSERSONLY VMDUMP ENDASSORTEDPARMS OBEY TCPMAINT MAINT ENDOBEY
Re: VSWITCH initial startup
We are running 4.4 i took out the exit and shutdown my VSWCTRL1 and VSWCTRL2. when i restart VSWCTRL1, it still tries to COUPLE to a VSE system: DMSACP723I D (198) R/O DMSACP723I E (591) R/O DMSACP723I F (592) R/O Ready; T=0.01/0.01 11:56:36 DTCRUN1022I Console log will be sent to user TCPMAINT 12:14:16 DTCRUN1026I TCPRUNXT EXEC (SETUP) returned :Owner.MAINT 12:14:16 DTCRUN1022I Console log will be sent to user MAINT 12:14:16 CTCA 0D09 DEFINED 12:14:16 HCPCPL058E CTCA 0674 busy on SP4 12:14:16 DTCRUN1001W CP COUPLE D09 SP4 0674 failed with return code 58 12:14:16 DTCRUN1026I TCPRUNXT EXEC (BEGIN) returned :Owner.MAINT 12:14:16 DTCRUN1021R To cancel TCP/IP Stack startup, type any non-blank character and 12:14:16 press ENTER. To continue startup, just press ENTER. prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 11:29:54 AM: OK. What release of z/vm are you running? I think we should simplify - get rid of the VSWCTRL exec first of all. Remove the :exit.VSWCTRL statement from SYSTEM DTCPARMS. As long as you the files VSWCTRL1 TCPIP and VSWCTRL2 on TCPMAINT 198 when those machines are IPLed they will find the right files. The doc you reference goes back to zvm42 and indeed the search order for locating the correct profile to use was different. In zvm520 onwards (maybe zvm510??) you can use the name of the machine as a profile name. Try that. David From: The IBM z/VM Operating System on behalf of [EMAIL PROTECTED] Sent: Thu 9/20/2007 12:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup i added these lines to SYSTEM DTCPARMS: :nick.VSWCTRL1 :type.server :class.stack :exit.VSWCTRL :nick.VSWCTRL2 :type.server :class.stack :exit.VSWCTRL there is a section earlier with: .** Application Class Definitions .* TCP/IP Protocol Stack :nick.stack :type.class :name.TCP/IP Stack :command.TCPIP :runtime.PASCAL :diskwarn.YES ... (a bunch of other CTCAs deleted here) :vCTC.C02 SP2TEST 0C03 :vCTC.C03 SP2TEST 0C02 :vCTC.D08 SP4 0675 :vCTC.D09 SP4 0674 :authlog.AUTHLOG FILE A is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? can i have a separate DCTPARMS just for my VSWITCH controllers ? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 10:50:19 AM: What does your SYSTEM DTCPARMS on TCPMAINT show? David From: The IBM z/VM Operating System on behalf of Huegel, Thomas Sent: Thu 9/20/2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup Well then nothing jumps out at me.. Here is my directory entry, maybe there is something there. It still looks like somehow you are picking up the wrong configuration file. USER DTCVSW2 xxx 32M 128M G INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 IUCV *VSWITCH MSGLIMIT 65535 LINK 5VMTCP20 491 491 RR LINK 5VMTCP20 492 492 RR LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 2835 005 520W01 MR x x x -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 20, 2007 9:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH initial startup Thomas, here is my PROFILE TCPIP (straight out of the Failover document): NOTRACE ALL OBEY OPERATOR TCPMNT44 MAINT ENDOBEY VSWITCH CONTROLLER ON i also have them set up on TCPMAINT's 198 - again, per the Failover doc. i assume that is so that all the configuration is kept on TCPMAINT, is that the reason? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 05:53:37 AM: My guess is that you copied your existing TCPIP profile for your VSWITCH CONTROLLERS .. It is a case of too much information. The profiles for the controllers is very simple. The only entry you NEED in their profile is VSWITCH CONTROLLER ON... Here is what my profiles for the controllers look like. NOTRACE OSD INFORM TCPMAINT MAINT ENDINFORM ASSORTEDPARMS PERMITTEDUSERSONLY VMDUMP ENDASSORTEDPARMS OBEY TCPMAINT MAINT ENDOBEY VSWITCH CONTROLLER ON A note: The way I do it is to leave the profiles on TCPMAINT's 198 disk and name them VSWCTRL1 TCPIP and VSWCTRL2 TCPIP
Re: VSWITCH initial startup
either SYSTEM DTCPARMS is hosed, or ... perish the thought ... IBM DTCPARMS was modified? force it off. XAUTOLOG VSWCTRL1 NOIPL SEND CP VSWCTRL1 Q V send the results From: The IBM z/VM Operating System on behalf of [EMAIL PROTECTED] Sent: Thu 9/20/2007 1:17 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup We are running 4.4 i took out the exit and shutdown my VSWCTRL1 and VSWCTRL2. when i restart VSWCTRL1, it still tries to COUPLE to a VSE system: DMSACP723I D (198) R/O DMSACP723I E (591) R/O DMSACP723I F (592) R/O Ready; T=0.01/0.01 11:56:36 DTCRUN1022I Console log will be sent to user TCPMAINT 12:14:16 DTCRUN1026I TCPRUNXT EXEC (SETUP) returned :Owner.MAINT 12:14:16 DTCRUN1022I Console log will be sent to user MAINT 12:14:16 CTCA 0D09 DEFINED 12:14:16 HCPCPL058E CTCA 0674 busy on SP4 12:14:16 DTCRUN1001W CP COUPLE D09 SP4 0674 failed with return code 58 12:14:16 DTCRUN1026I TCPRUNXT EXEC (BEGIN) returned :Owner.MAINT 12:14:16 DTCRUN1021R To cancel TCP/IP Stack startup, type any non-blank character and 12:14:16 press ENTER. To continue startup, just press ENTER. prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 11:29:54 AM: OK. What release of z/vm are you running? I think we should simplify - get rid of the VSWCTRL exec first of all. Remove the :exit.VSWCTRL statement from SYSTEM DTCPARMS. As long as you the files VSWCTRL1 TCPIP and VSWCTRL2 on TCPMAINT 198 when those machines are IPLed they will find the right files. The doc you reference goes back to zvm42 and indeed the search order for locating the correct profile to use was different. In zvm520 onwards (maybe zvm510??) you can use the name of the machine as a profile name. Try that. David From: The IBM z/VM Operating System on behalf of [EMAIL PROTECTED] Sent: Thu 9/20/2007 12:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup i added these lines to SYSTEM DTCPARMS: :nick.VSWCTRL1 :type.server :class.stack :exit.VSWCTRL :nick.VSWCTRL2 :type.server :class.stack :exit.VSWCTRL there is a section earlier with: .** Application Class Definitions .* TCP/IP Protocol Stack :nick.stack :type.class :name.TCP/IP Stack :command.TCPIP :runtime.PASCAL :diskwarn.YES ... (a bunch of other CTCAs deleted here) :vCTC.C02 SP2TEST 0C03 :vCTC.C03 SP2TEST 0C02 :vCTC.D08 SP4 0675 :vCTC.D09 SP4 0674 :authlog.AUTHLOG FILE A is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? can i have a separate DCTPARMS just for my VSWITCH controllers ? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 10:50:19 AM: What does your SYSTEM DTCPARMS on TCPMAINT show? David From: The IBM z/VM Operating System on behalf of Huegel, Thomas Sent: Thu 9/20/2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH initial startup Well then nothing jumps out at me.. Here is my directory entry, maybe there is something there. It still looks like somehow you are picking up the wrong configuration file. USER DTCVSW2 xxx 32M 128M G INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 IUCV *VSWITCH MSGLIMIT 65535 LINK 5VMTCP20 491 491 RR LINK 5VMTCP20 492 492 RR LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 2835 005 520W01 MR x x x -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 20, 2007 9:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH initial startup Thomas, here is my PROFILE TCPIP (straight out of the Failover document): NOTRACE ALL OBEY OPERATOR TCPMNT44 MAINT ENDOBEY VSWITCH CONTROLLER ON i also have them set up on TCPMAINT's 198 - again, per the Failover doc. i assume that is so that all the configuration is kept on TCPMAINT, is that the reason? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM
Re: VSWITCH initial startup
Q V STORAGE = 32M XSTORE = none CPU 00 ID FF008B0A20968000 (BASE) STOPPED CONS 0009 ON LDEV L0019 TERM STOP HOST TCPIPFROM 10.80.15.67 0009 CL T NOCONT NOHOLD COPY 001READY FORM STANDARD 0009 TO VSWCTRL1 PRT DIST VSWCTRL1 FLASHC 000 DEST OFF 0009 FLASH CHAR MDFY 0 FCB LPP OFF 0009 3215 NOEOF CLOSEDNOKEEP NOMSG NONAME 0009 SUBCHANNEL = 0007 RDR 000C CL * NOCONT NOHOLD EOF READY 000C 2540 CLOSEDNOKEEP NORESCAN SUBCHANNEL = 0004 PUN 000D CL A NOCONT NOHOLD COPY 001READY FORM STANDARD 000D TO VSWCTRL1 PUN DIST VSWCTRL1 DEST OFF 000D FLASH 000 CHAR MDFY 0 FCB 000D 2540 NOEOF CLOSEDNOKEEP NOMSG NONAME 000D SUBCHANNEL = 0005 PRT 000E CL A NOCONT NOHOLD COPY 001READY FORM STANDARD 000E TO VSWCTRL1 PRT DIST VSWCTRL1 FLASHC 000 DEST OFF 000E FLASH CHAR MDFY 0 FCB LPP OFF 000E 1403 NOEOF CLOSEDNOKEEP NOMSG NONAME 000E SUBCHANNEL = 0006 DASD 0190 3390 VMDRES R/O214 CYL ON DASD E200 SUBCHANNEL = 0008 DASD 0191 3390 VMPRES R/W 6 CYL ON DASD E000 SUBCHANNEL = 0003 DASD 0198 3390 VMDRES R/O 9 CYL ON DASD E200 SUBCHANNEL = 0002 DASD 019D 3390 VMDRES R/O204 CYL ON DASD E200 SUBCHANNEL = 0009 DASD 019E 3390 VMDRES R/O815 CYL ON DASD E200 SUBCHANNEL = 000A DASD 0591 3390 VMDRES R/O 38 CYL ON DASD E200 SUBCHANNEL = DASD 0592 3390 VMDRES R/O 67 CYL ON DASD E200 SUBCHANNEL = 0001 prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 12:34:10 PM: either SYSTEM DTCPARMS is hosed, or ... perish the thought ... IBM DTCPARMS was modified? force it off. XAUTOLOG VSWCTRL1 NOIPL SEND CP VSWCTRL1 Q V send the results
Re: VSWITCH initial startup
On Thursday, 09/20/2007 at 12:35 EDT, David Kreuter [EMAIL PROTECTED] wrote: OK. What release of z/vm are you running? I think we should simplify - get rid of the VSWCTRL exec first of all. Remove the :exit.VSWCTRL statement from SYSTEM DTCPARMS. As long as you the files VSWCTRL1 TCPIP and VSWCTRL2 on TCPMAINT 198 when those machines are IPLed they will find the right files. The doc you reference goes back to zvm42 and indeed the search order for locating the correct profile to use was different. In zvm520 onwards (maybe zvm510??) you can use the name of the machine as a profile name. As of z/VM 5.2, you can get rid of your own VSWITCH controllers entirely, using the DTCVSW1 and DTCVSW2 that we provide. The IBM DTCPARMS file already has the needed definitions and the profiles are already there. Just remember to update AUTOLOG1. (The IBM-supplied AUTOLOG1 PROFILE EXEC autologs these controllers.) It is a Bad Idea to have any TCPIP stack acting as a controller. Only a dedicated controller should have VSWITCH CONTROLLER ON in PROFILE TCPIP. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH initial startup
On Thursday, 09/20/2007 at 01:19 EDT, [EMAIL PROTECTED] wrote: i added these lines to SYSTEM DTCPARMS: :nick.VSWCTRL1 :type.server :class.stack :exit.VSWCTRL :nick.VSWCTRL2 :type.server :class.stack :exit.VSWCTRL there is a section earlier with: .** Application Class Definitions .* TCP/IP Protocol Stack :nick.stack :type.class :name.TCP/IP Stack :command.TCPIP :runtime.PASCAL :diskwarn.YES ... (a bunch of other CTCAs deleted here) :vCTC.C02 SP2TEST 0C03 :vCTC.C03 SP2TEST 0C02 :vCTC.D08 SP4 0675 :vCTC.D09 SP4 0674 :authlog.AUTHLOG FILE A There's your error. You copied the stack class definition to your SYSTEM DTCPARMS and changed it. Don't do that. When you alter a class definition, it applies to ALL instances of :class.stack. VSWITCH controllers are :class.stack. 1. Move those :vctc tags to your :nick.TCPIP :type.server definition. 2. Remove the :nick.stack :type.class definition from SYSTEM DTCPARMS. is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? If a :vctc. fails, the whole process comes to a stop. can i have a separate DCTPARMS just for my VSWITCH controllers ? You can, but there's no need. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH initial startup
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 11:24:22 AM: On Thursday, 09/20/2007 at 01:19 EDT, [EMAIL PROTECTED] wrote: ... ... (a bunch of other CTCAs deleted here) :vCTC.C02 SP2TEST 0C03 :vCTC.C03 SP2TEST 0C02 :vCTC.D08 SP4 0675 :vCTC.D09 SP4 0674 :authlog.AUTHLOG FILE A ... is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? If a :vctc. fails, the whole process comes to a stop. Actually, that's not the reason it doesn't try to couple to SP2TEST. We only process one :vctc. tag (the last one specified). If you want multiple CTC devices (which is kind of essential), they need to be specified as: :vCTC.C02 SP2TEST 0C03, C03 SP2TEST 0C02, D08 SP4 0675, D09 SP4 0674 Regards, Miguel Delapaz z/VM TCP/IP Development
Re: VSWITCH initial startup
Alan, thanks for spotting that. I inherited this system, so I am still sorting out what is where. is there a manual that explains how to code DTCPARMS ? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL There's your error. You copied the stack class definition to your SYSTEM DTCPARMS and changed it. Don't do that. When you alter a class definition, it applies to ALL instances of :class.stack. VSWITCH controllers are :class.stack. 1. Move those :vctc tags to your :nick.TCPIP :type.server definition. 2. Remove the :nick.stack :type.class definition from SYSTEM DTCPARMS. is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? If a :vctc. fails, the whole process comes to a stop. can i have a separate DCTPARMS just for my VSWITCH controllers ? You can, but there's no need. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH initial startup
The DTCPARMS file is discussed in TCP/IP Planning and Customization Chapter 5. General TCP/IP Server Configuration Regards, Miguel Delapaz z/VM TCP/IP Development The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 09/20/2007 12:31:42 PM: Alan, thanks for spotting that. I inherited this system, so I am still sorting out what is where. is there a manual that explains how to code DTCPARMS ? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL There's your error. You copied the stack class definition to your SYSTEM DTCPARMS and changed it. Don't do that. When you alter a class definition, it applies to ALL instances of :class.stack. VSWITCH controllers are :class.stack. 1. Move those :vctc tags to your :nick.TCPIP :type.server definition. 2. Remove the :nick.stack :type.class definition from SYSTEM DTCPARMS. is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? If a :vctc. fails, the whole process comes to a stop. can i have a separate DCTPARMS just for my VSWITCH controllers ? You can, but there's no need. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH initial startup
Miquel, that explains a lot. thank you. i have fixed this in our DTCPARMS. prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL Actually, that's not the reason it doesn't try to couple to SP2TEST. We only process one :vctc. tag (the last one specified). If you want multiple CTC devices (which is kind of essential), they need to be specified as: :vCTC.C02 SP2TEST 0C03, C03 SP2TEST 0C02, D08 SP4 0675, D09 SP4 0674 Regards, Miguel Delapaz z/VM TCP/IP Development
Re: VSWITCH initial startup
ok - it is working correctly now. i moved the :vctc tags over to our :nick.TCPIP :type.server . that right there helped me understand the :type.class sections. i restarted the VSWITCH controllers and there is on attempt to couple to VSE. great. thank you all for helping sort this out. prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL There's your error. You copied the stack class definition to your SYSTEM DTCPARMS and changed it. Don't do that. When you alter a class definition, it applies to ALL instances of :class.stack. VSWITCH controllers are :class.stack. 1. Move those :vctc tags to your :nick.TCPIP :type.server definition. 2. Remove the :nick.stack :type.class definition from SYSTEM DTCPARMS. is my VSWCTRL1 trying to COUPLE to SP4? but then, why isn't trying to COUPLE to SP2TEST as well? If a :vctc. fails, the whole process comes to a stop. can i have a separate DCTPARMS just for my VSWITCH controllers ? You can, but there's no need. Alan Altmark z/VM Development IBM Endicott
