I would like to add some information to this discussion. When you
attach a 3270 telnet device (which is what you are doing when you
configure a 3270 type device), the device is creating a session with a
TN3270 server implemented within Hercules. The built-in TN3270 server
interacts with the 3270 CCW driver within Hercules.
There are two very different versions of Hercules here: 3.x and 4.x.
There was a lot of work done in version 4 related to telnet based
communications. In version 4.x, the TN3270 server is implemented with
the help of an external package whereas in 3.x the server was totally
part of Hercules. The two versions _are_ different.
It is entirely possible that Hercules 4.x is working as designed, but
triggering a very negative response in MTS when Vista is the client.
Why might 3.x work? 3.x may, by happenstance, be shielding MTS from
whatever Vista is sending that MTS does not like. ?
Is it working as designed? a bug? and which component?
This will be a challenge to resolve.
Harold Grovesteen
toggle quoted message
Show quoted text
On Mon, 2023-09-18 at 01:01 -0700, Fish Fish wrote:
John Palmer wrote:
There is no mode in which using Vista 3270 as the master
console works without causing a superdump in the early stages
of IPL of MTS when running Hercules 4.x.
Note, this is not the case for Hercules 3.x (3.06, 3.13). They
don't exhibit this behavior.
Then it certainly sounds like there is a bug in SDL Hercules which
needs to be investigated!
I will see about opening a ticket in order to help diagnose the
problem.
Thank you. I would appreciate that very much.
