Nice to hear from you - I do see that you are still busy and posting not a
little to the forum. ---
Yes your example is correct. BUT - did you try the name option in in the
If you put the device number in the name Field(Define tn3270E - for some
reason it works - Ask Ivan why J )
Then your tn3270 sessions will always connect to the same device and not the
first available device. Try using 023 - Normally you rarely will get that
But if you put it in the name field you will always connect to 023. Then
when you reconnect you first get disconnected by the system an d you can
This little trick seems to simulate an old COAX connection --- If the power
went off say.
Proper protocol would be that you get the Logon Screen and then you can
reconnect. That's what happens with the CP fix I made.
About the console 1050 - I never have any problem reconnecting to the user
console ff the window gets lost, disconnected - I use simple telnet for the
console and it works fine
From: email@example.com [mailto:firstname.lastname@example.org] On
Behalf Of paoloG
Sent: Wednesday, June 05, 2013 8:09 AM
Subject: [hercules-390] Re: hercules 3.08 unexpected disconnects not handled
I had already performed your tests of disconnection and reconnection (look
at VM forum), and I noticed there were some issues(if you disconnect or
cancel a TN3270 session (for example at address 021 - user ROCKY) and try to
logon on another '3270' (for example a TN3270 session at address 022 already
started - with VM LOGON screen), you cannot logon because the user ROCKY is
reported to be already connected to the terminal 021.
This is the situation Dhurgee reported in his original post (before talking
of 1052 and 3215),as not accettable in his environment, as in P/370 the
disconnection of a TN3270 session ended with a disconnession of the logged
I suspected (and now I'm certain) that a real mainframe behaved exactly as
Hercules does - and it's not a fault of VM - is was the option IBM chose
when she decided that 3274 should not notify to the CPU that a 3270 had
What could the OS do in this situation to detect a power off of a 3270? a
polling of all local terminals? Perhaps - or even better the 3274 could
notify the terminal power off to the CPU.
In a generous attempt to resolve Dhurgee's issue I found that adding a
line of code in module console.c of Hercules VM behaved as Dave desired,
forcing disconnection of the active user when closing a TN3270 session - as
I've made extensive tests of this mod with VM/SP5 and it works very well...
with Vista TN3270.
Of course the mod was intended only for VM and could cause issues with other
OS (and perhaps it's working only with Vista TN3270).
That's all Roc; it's nice to see you again among us well alive and kicking
after your frightening experiences in the Dark Continent ;-).
Now you'll have time to modify you excellent GCIC package in order to use
the new DIAG58 support in VM/370 ;-)
Post by Rocky Martin Post by au1john
So I don't see any harm to say that P/370 management of '3270 power
off' is better than Hercules' one and avoids various issues, and if
IBM is our guide in the darkness, it should be always followed.
Paul - It seems to me that Fish summed it up correctly -
If there are issues they are with the guest OS and not with Hercules.
The problem with local non-sna 3270's is that since they are connected
directly to a host address you would want to get the same device address
With an old COAX connection that is what happened.
In TCPIP, unless you do something special you are going to get the next free
address in the pool.
Now I see some strange behavior from Hercules which sort of corrects that
Post by Rocky Martin
We need some input from IVAN as to why) -
I tried using the VISTA emulator that you said that you use and defined the
connection as tn3270E. There I can give a device name
What's strange is I am using a VM/SP5 box which predates TN3270E. But in the
name field I put the address. 020 or 021 or 022 etc. Seems that Ivan is
looking at the name field and trying to connect to the proper address.
If I put 022 then the session only connects to address 022. And my CP fix (
which I posted earlier cleans up after that situation fine).
As soon as you get the interrupt from the connect it disconnects the old
session and returns to the logo screen.
Why tn3270e is completing the negotiation is beyond me, but it works with
Vista and with my old Lognet emulation as well.
So now I get the same address every time - If my session is disconnected (
I cancelled the emulator with task manager, -
Disconnected my internet and even powered off my PC in the middle).
When I reconnected everything worked as expected - Old session
Post by Rocky Martin
and I can reconnect or logon as a different user.
Hercules seems to be doing more than I expect. And properly.
The FIX I posted for SP5 clears up the security issues and prevents hanging
Anybody want to try it, I'll give you a userid and password and address - I
have not been able to get it to hang or get the old session back without
logging on. Seems good to me.
[Non-text portions of this message have been removed]