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