That fixed it, many thanks! i ------ Original Message ------ Received: Fri, 01 Aug 2008 02:48:21 PM BST From: Kris Buelens <[EMAIL PROTECTED]> To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Loosing IP after IPL: CTC free
> It is in the PEROFILE EXEC of AUTOLOG1 that you must insert an > XAUTOLOG TCPIP. AUTOLOG1 is started after a CP IPL, it's only task is > to start other users. If you'd have RACFVM, AUTOLOG1 only starts > RACFVM; RACFVM then starts AUTOLOG2, that would then start everything > else. > > (the XAUTOLOG statements in the CP directory define which class G > users are authorized to XAUTOLOG the given userid). > > 2008/8/1 Ian S. Worthington <[EMAIL PROTECTED]>: > > Hi Rob -- > > > > My apologies: I'm much more of an MVS person - I'm only pretending to do VM as > > a favour, so your questions are a bit over my head I'm afraid. > > > > XAUTOLOG would be defined in the USER DIRECT (this is the PWD 5.3 system), > > yes? TCPIP is defined as below - no xautolog: > > > > USER TCPIP TCPIP 32M 128M ABG > > INCLUDE TCPCMSU > > OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON > > SHARE RELATIVE 3000 > > IUCV ALLOW > > IUCV ANY PRIORITY > > IUCV *CCS PRIORITY MSGLIMIT 255 > > IUCV *VSWITCH MSGLIMIT 65535 > > LINK 5VMTCP30 491 491 RR > > LINK 5VMTCP30 492 492 RR > > LINK TCPMAINT 591 591 RR > > LINK TCPMAINT 592 592 RR > > LINK TCPMAINT 198 198 RR > > MDISK 191 3390 3057 005 530W01 MR RTCPIP WTCPIP MTCPIP > > > > PROFILE TCPCMSU > > IPL CMS > > MACH XA > > SPOOL 000C 2540 READER * > > SPOOL 000D 2540 PUNCH A > > SPOOL 000E 1403 A > > CONSOLE 009 3215 T > > LINK MAINT 0190 0190 RR > > LINK MAINT 019D 019D RR > > LINK MAINT 019E 019E RR > > LINK MAINT 0402 0402 RR > > LINK MAINT 0401 0401 RR > > LINK MAINT 0405 0405 RR > > > > > > On TCPMAINT 198 there's: > > > > SYSTEM DTCPARMS D1 V 71 1BLK 08/08/01 > > ===> > > .********************************************************* > > .* SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 1 Aug 2008 > > .* Configuration program run by MAINT at 09:04:12 > > .********************************************************* > > :nick.TCPIP :type.server > > :class.stack > > :attach.0E40-0E41 > > * * * End of File * * * > > > > As IP does come up after the IPWIZARD I would guess the device definitions are > > ok? Currently I see: > > > > q ctc > > CTCA 0E40 ATTACHED TO TCPIP 0E40 > > CTCA 0E41 ATTACHED TO TCPIP 0E41 > > > > > > Is it just a case of adding an XAUTOLOG to the TCPIP defintion? > > > > Apologies for my ignorance. > > > > ian > > ... > > > > > > > > ------ Original Message ------ > > Received: Fri, 01 Aug 2008 02:22:19 PM BST > > From: Rob van der Heij <[EMAIL PROTECTED]> > > To: IBMVM@LISTSERV.UARK.EDU > > Subject: Re: Loosing IP after IPL: CTC free > > > >> On Fri, Aug 1, 2008 at 3:14 PM, Ian S. Worthington > >> <[EMAIL PROTECTED]> wrote: > >> > I've successfully run IPWIZARD and can connect to my system until I ipl. > >> > > >> > After that I notice that the CTC is FREE, whereas after IPWIZARD its > > "ATTACHED > >> > TO TCPIP". > >> > > >> > I'm guessing this is the cause of the problem. What do I have to do to > > make > >> > this sticky please? > >> > >> Do you XAUTOLOG TCPIP during startup? You should have 2 devices > >> attached. Did the DTCPARMS file get built by IPWIZARD ? Can the > >> devices be attached to TCPIP? (it does by default an ATTACH where > >> real=virt and that breaks when your real device happens to be where > >> the sample stack has another device). > >> > >> Rob > >> > > > > -- > Kris Buelens, > IBM Belgium, VM customer support >
