Also risking the wrath of Chuckie, I can tell you what the person on
IBMLink told me when I opened an ETR for this same request:
I added my second stack to SYSTEM DTCPARMS:
:nick.TCPIP2 :type.server
:class.stack
:attach.0C00-0C01
I created a TCPIP2 TCPIP file, which only does TN3270. It only has
port 23 open and it has its own DEVICE and LINK for the non-QDIO port
pair C00-C01 from our OSA-E, its own HOME address, but same mask and
gateway handed down from the mount by the Network Gods.
I created a TCPIP2 DATA file on 592 with the TCPIPUSERID set to TCPIP2.
And its been running that way for a couple of years.
I do use the TCP TCPIP2 option on NETSTAT commands.
IIRC, the TCPIP person who led me through this was musing that they
really should document how to do this in the manuals, since so many
people ask the same question. I have not gone to look at the recent
books.
Ron
On Sat, Mar 5, 2011 at 10:07 AM, Jeff Gribbin <jeff.grib...@gmail.com> wrote:
> Greetings,
> I may be a, 'VM-Oldie' but I'm most certainly a, 'TCP/IP Newbie' and, true
> to form, I'm already wishing to push the envelope a little ...
>
> I'm helping to maintain a not-very-busy z/VM system which is pretty-much
> starting from scratch and currently has no asociated SLA's or the such to
> worry about. It's not quite a sandpit, but pretty close. I access the
> system via TN3270 and, in order to allow me to perform surgery on the main
> TCP/IP stack (bog-standard vanilla configuration, straight out of the box),
> I'm looking to place a second IP stack alongside the primary stack that will
> give me at-least a TN3270, 'back door' into the system.
>
> My, 'problem' is TCPIP DATA, which appears to be a unique filename. 'TCP/IP
> Planning and Customization' states quite categorically that TCPIP DATA
> defines parameters used by TCPIP -client- applications. If this is truly
> the case then it would seem that all I need in order to implement a second
> stack purely for TN3270 purposes is to create appropriate '<userid>
> DTCPARMS' and '<userid> TCPIP' files on TCPMAINT's 0198 and I'm away.
>
> Would I be correct in thinking that TCPIP DATA is, 'merely' read by the,
> 'client' commands in order (e.g.) to locate the servers that they need to
> interact with. If this is so, would it be acceptable practise (that is,
> behaviour that would not bring the Wrath of Chuckie upon me) to keep a
> second copy of TCPIP DATA, configured according to the userid(s) of the
> second stack, on a separate minidisk and access that minidisk in front of
> TCPMAINT's 592 when wishing to, 'converse' with the second stack? (For
> example, in order to issue a NETSTAT command without needing to specify the,
> 'TCP' option every time.)
>
> I can, of course, discover most of this empirically for myself - and will
> indeed be experimenting a little (what else to do on a wet Saturday
> afternoon?) - but if for no other reason that the Fear of Chuckie I would be
> reassured if somebody with more experience were willing to sanity-check my
> hypothesis and proposed, 'solution'.
>
> Thanks
> Jeff
>
