Not necessarily. I use a CPUID value which is in my SYSTEM NETID as a different system name. *CPUID SYSID RSCS 07120D PROD RSCS 123456 TSTIP2 RSCS
Then, I can put a TSTIP2 TCPIP and a TSTIP2 DTCPARMS on the same 198 as all the other TCPIP files. And if in my TCPIP DATA file I have: PROD: TCPIPUSERID TCPIP TSTIP2: TCPIPUSERID TCPIP2 So, everything works just fine... Any user who has to use that other stack gets the CPUID of 123456 and then IDENTIFY tells him that he is on the TSTIP2 node, and needs to contact TCPIP2 for TCP services. Shimon ---- Original message ---- >Date: Wed, 25 Mar 2009 18:32:58 -0400 >From: Rich Greenberg <[email protected]> >Subject: Re: Question about separate TCP stacks and SSL server machines >To: [email protected] > >On: Wed, Mar 25, 2009 at 04:05:35PM -0400,Craig Dudley Wrote: > >} Do I need a TCPIP DATA (with TCPIPUSERID TCPIPW2H) on SSLSRV1s A-disk >} for SSLSRV1 to use TCPIPW2H as its stack? > >Yes. > >-- >Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353 >Eastern time. N6LRT I speak for myself & my dogs only. VM'er since CP-67 >Canines:Val, Red, Shasta & Casey (RIP), Red & Zero, Siberians Owner:Chinook-L >Retired at the beach Asst Owner:Sibernet-L
