On Thursday, 01/28/2010 at 06:59 EST, "O'Brien, Dennis L" <dennis.l.o'br...@bankofamerica.com> wrote: > I'm setting up a DR process for a new system. I need to use a different
> PROFILE TCPIP when the system is up in the DR site. I know that the easy and > wrong way is to update TCPIP's PROFILE EXEC to copy the correct PROFILE TCPIP > to the A-disk. I'm trying to do it the right way, by using a server exit to > pass the name of the profile to the stack. I can't figure out what to pass to > get the stack to use a different profile. I've tried > > Return ':Command.TCPIP DRTEST TCPIP * > > and > > Return ':Parms.DRTEST TCPIP * > > Both yield: > DTCRUN1011I Running server command: TCPIP > DTCRUN1011I Parameters in use: > DTCRUN1011I DRTEST TCPIP * > > The problem is that the parameters don't seem to influence which file gets > used. The "problem" is that TCPIP doesn't complain about unknown parameters. There is no provision to pass the name of the config file to the stack at startup. It has only the search order. > I don't have "userid" or "node" TCPIP files, so the stack reads PROFILE > TCPIP. The userid and node name don't change during DR, so using those files > wouldn't help. Is there a way to tell the stack what file to use, or should I > just use the exit to copy the correct file to the A-disk as PROFILE TCPIP? Use the exit. That's the same technique folks were using with TCPIP DATA on SMTP prior to IPMAILERADDRESS ALL. The exit could instead play games with SET CPUID and SYSTEM NETID. E.g. Make sure you SYSTEM NETID is set up like: *CPUID NODEID NETID 029F30 HOME1 RSCS 036924 HOME2 RSCS FFFFFF DRTEST RSCS If the exit issues SET CPUID FFFFFF and IDENTIFY, the nodeid will change. Then DRTEST TCPIP will be picked up by the stack. Alan Altmark z/VM Development IBM Endicott
