An OSAICC present itself to the outside world as a 3270 TELNET server. To the host it looks as LOCAL 3270's, with indeed 4-digt addresses like D000->D0CF
The customisation defines with what address a TELNET client is present to the host. In PCOMM, the TELNET end-user one defines as part of its connection defintions not only the IP address of the OSA ICC, but also a LUNAME There are two choises - a LU Name can correspond to a single 4 digit address. If a client is already connected, others must select an other LUname - a LU Name can correspond to a list of addresses (then termed "POOL Name"), Often one predefines some single address LU names, to connect operator consoles etc. So soem workstations present themselves to the host at well-known 4-digits addresses. At least one pool is then defined for everyone else. Another practice I often see is that one changes the PORT number of the OSA ICC from 23 for example 1000 or 3270, or ... So it is a bit hidden from the public, only the "intimates" can then use the (limited number of) sessions an OSA ICC provides. This defintion all happens via the HCM, you select the channels of the CPC and then "channel Advanced facilities". 2011/3/9 Jeff Gribbin <jeff.grib...@gmail.com> > Brilliant feedback - thanks - it's good to see that this has blossomed into > something that is at-least potentially useful to more folk than just > myself. > > Just to update my personal progress, I've successfully built the second > stack and then, because I was able to now access the system through the > second stack, I've been able to configure a VSWITCH using what was the > primary stack's OSA interface and get the primary stack running through the > VSWITCH. Happiness. > > I didn't know about the OSA's internal stack - sounds like a useful > capability but not something that I'm personally in a position to currently > take advantage of. The same goes for SYSG access - not feasible on my > current administrative setup but I'm glad that it's been mentioned. > > Dumb question: If one logs on to the OSA's internal stack, what does the > SCP > actually see? Is it a local 3270 at some predefined address? I'd certainly > be interested in learning a little more about this capability - could you > maybe point me at the, 'proper' documentation? > > I have a small puzzlement in that I can't ping either of my stacks from the > other ... I guess that I'm going to be learning a little more about the > intricacies of TCP/IP and subnetting in order to get to the bottom of why > THAT is the case - but not today, the sun is shining and the dogs are > telling me that it's a good day for a walk :-) > > Again, thanks for all the input. > > Jeff > -- Kris Buelens, IBM Belgium, VM customer support
