Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-22 Thread Brian Westerman
; Lloyd >> >> -Original Message- >> From: IBM Mainframe Discussion List On Behalf Of Tony Thigpen >> Sent: Tuesday, July 21, 2020 11:32 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior >> &

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Tony Thigpen
console. Regards. Lloyd -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tony Thigpen Sent: Tuesday, July 21, 2020 11:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior I don't have an answer to that. I know what works

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Tony Thigpen
I don't ever use SYSC. Hum, I thought that was the 3270 emulation in the HMC that did not use an ICC connection. (I never use the HMC 3270 emulation either.) Maybe I am not understanding the SYSC stuff. Tony Thigpen Christian Svensson wrote on 7/21/20 11:24 AM: +1 on Tony's remark - but I

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Lloyd Fuller
mason.gmu.edu/~smetz3 > > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > behalf of Tony Thigpen [t...@vse2pdf.com] > Sent: Tuesday, July 21, 2020 9:18 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Multi-channel OSA-ICC routing and TCP

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Tony Thigpen
-MAIN@LISTSERV.UA.EDU] on behalf of Tony Thigpen [t...@vse2pdf.com] Sent: Tuesday, July 21, 2020 9:18 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior Brian, In regards to the '3270' or 'console' setting, that is very specific to z/OS. On z/VSE and z

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Christian Svensson
+1 on Tony's remark - but I do find the discussions and experiences of the people here always fascinating and entertaining :-). As it was mentioned, the 3270 / console setting - I had to use the "operator console" to get my z/VM 6.3 instance to play along. If I used the 3270 option for the SYSC

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Dana Mitchell
We recently migrated to z14's and I was working on setting up the ICC definitions on the new boxes. One of the docs I ran across pointed out the fact that there is only one gateway address, and had a nice diagram showing one of the ports connected to the outside world, and the other port

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Seymour J Metz
] on behalf of Tony Thigpen [t...@vse2pdf.com] Sent: Tuesday, July 21, 2020 9:18 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior Brian, In regards to the '3270' or 'console' setting, that is very specific to z/OS. On z/VSE and z/VM the consoles

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Tony Thigpen
And, this is were the discussion has drifted. His original question had noting to do with the operating system side of the ICC. It had to do with the limited IP configuration when using both ports. He had it working with one port, but he thought he was misunderstanding the limitations on the

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Tony Thigpen
From: IBM Mainframe Discussion List on behalf of R.S. Sent: 20 July 2020 12:17 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior Excuse me, but IMHO OSA-ICC is just way to get rid off old equipment like 3174L. It is NOT replacement, it is only for loc

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Seymour J Metz
Westerman [brian_wester...@syzygyinc.com] Sent: Tuesday, July 21, 2020 4:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior The important thing though is that it works as local 3270, and that's what the OP wanted to use it for. Since it will work

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Brian Westerman
>R.S. >Sent: 20 July 2020 12:17 >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior > >Excuse me, but IMHO OSA-ICC is just way to get rid off old equipment >like 3174L. It is NOT replacement, it is only for local (called non-

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-21 Thread Brian Westerman
The important thing though is that it works as local 3270, and that's what the OP wanted to use it for. Since it will work, there is no good reason not to use it. Brian On Mon, 20 Jul 2020 13:17:00 +0200, R.S. wrote: >Excuse me, but IMHO OSA-ICC is just way to get rid off old equipment

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-20 Thread Seymour J Metz
...@bremultibank.com.pl] Sent: Monday, July 20, 2020 7:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior Excuse me, but IMHO OSA-ICC is just way to get rid off old equipment like 3174L. It is NOT replacement, it is only for local (called non-SNA) terminals

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-20 Thread Parwez Hamid
of R.S. Sent: 20 July 2020 12:17 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Multi-channel OSA-ICC routing and TCP port behavior Excuse me, but IMHO OSA-ICC is just way to get rid off old equipment like 3174L. It is NOT replacement, it is only for local (called non-SNA) terminals, printers

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-20 Thread R.S.
W dniu 20.07.2020 o 05:47, Timothy Sipples pisze: Mike Schwab wrote: Port 23 is standard telnet. Port 3270 is non-standard TN3270E. IANA has actually reserved port 3270 for "Verismart":HMC Integrated 3270 console

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-20 Thread R.S.
Excuse me, but IMHO OSA-ICC is just way to get rid off old equipment like 3174L. It is NOT replacement, it is only for local (called non-SNA) terminals, printers and ...CONSOLES. Consoles are the most important. Of course 3172, 3274, and other controllers were not the goal. IBM went looong

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-20 Thread Timothy Sipples
Brian Westerman wrote: >So you are using TCP to get to them inside the ICC, but they >are technically local 3270 terminals. I think you can make >some of them printers if you want, but that seems like a waste. I recently worked with an organization that configured an OSA-ICC TN3270E printer

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-19 Thread Timothy Sipples
Mike Schwab wrote: >Port 23 is standard telnet. Port 3270 is non-standard TN3270E. IANA has actually reserved port 3270 for "Verismart": https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt I have no idea what Verismart is, or was. It's probably moribund,

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-19 Thread Christian Svensson
Thanks Tony, it makes calmer knowing I'm not the only one being confused about this :-) On Sun, Jul 19, 2020 at 3:18 PM Tony Thigpen wrote: > Christian, > I was dismayed too when I first discovered this limitation. The OSA-C > was originally intended to eliminate the local 3174 requirement. It

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-19 Thread Tony Thigpen
Christian, I was dismayed too when I first discovered this limitation. The OSA-C was originally intended to eliminate the local 3174 requirement. It was not really designed to replace the 3172-003, which is what many are using it for today. And, you also need to look back at the OSA-C's

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-19 Thread Christian Svensson
Thanks for the input folks. Brian: I have it working just fine, the setup was easy as you said - the reason I started this thread was because I couldn't understand why the limitations on the TCP port number and the philosophy behind the routing. It seems pretty weird to me that IBM implemented

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-18 Thread Brian Westerman
You can set up some of the ports to be local VTAM terminals, then you can use VISTA (or any 3270 emulator) to connect into the ICC port 3270, and use the LUNAME of the 3270 you defined as a local 3270 terminal. Since you can have over 100 terminals per port, making them all os consoles is a

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-18 Thread Mike Schwab
Port 23 is standard telnet. Port 3270 is non-standard TN3270E. On Sat, Jul 18, 2020 at 10:10 PM Tony Thigpen wrote: > > Christian, > > IMHO: For use as an OSA-C, the second port is of minimal use. About the > only good use is to attach a local non-routable lan segment so that > local consoles

Re: Multi-channel OSA-ICC routing and TCP port behavior

2020-07-18 Thread Tony Thigpen
Christian, IMHO: For use as an OSA-C, the second port is of minimal use. About the only good use is to attach a local non-routable lan segment so that local consoles can be isolated from your main network so that the network people do not mess with your z/OS consoles. Tony Thigpen

Multi-channel OSA-ICC routing and TCP port behavior

2020-07-18 Thread Christian Svensson
Hi, I have been experimenting with setting up OSA-ICC cards on a z114. These are OSA Express3 cards with 4 ports / 2 channels. Let's look at a single channel in this card, named CHPID 200. These are the configuration parameters for this card: > Channel ID: 0200 > LAN port type: OSA-ICC 3270 >