Ticket #147 ( Closed )

Short Description migration to tn3270 is causing failures
Entered By: PeteL When: 1998-09-14 08:30:58 Build: 1.03.23c
Categories Type: Problem   Department: Product   Category: TN3270 Connection
My automated logon process is working fine for straight 3270 sessions, but is breaking when run over TN3270. It is not 100% consistent, but what does seem consistent is when I turn on the datastream trace, it works fine - when I turn it off, it breaks. Makes it a little hard to proceed. Would you like a copy of the trace that does work?
Append By: WindSurfer  When: 1998-09-14 11:25:31  New Status: Pending Customer
Comment Yes, please send a copy of your TN3270 connection when it IS working-- this will identify the time-sensitive areas so that we can figure-out why it works with tracing but fails without...
Append By: PeteL  When: 1998-09-14 14:11:15  New Status: Closed
Comment hyenalog and template traces of working one sent via email, also a vtam-type trace of the failure, although that one doesn't have a matching template trace
Append By: PeteL  When: 1998-09-14 14:14:14  New Status: Pending IE
Comment sorry, i closed this by accident
Append By: WindSurfer  When: 1998-09-15 18:56:43  New Status: Pending Customer
Comment Please try ftp://ftp.ieinc2.com/pub/surfer/t1_3_25e.zip-- this has new logic to better handle multiple 3270 buffers in a single TN3270 record.
Append By: PeteL  When: 1998-09-16 06:06:17  New Status: Pending IE
Comment still having problems - will send new trace this morning
Append By: WindSurfer  When: 1998-10-28 19:36:46  New Status: Pending Customer
Comment How is progress on this issue?
Append By: PeteL  When: 1998-10-29 09:50:44  New Status: Pending IE
Comment just got back to it this morning for awhile - my autologons fail miserably with UseEmptyWrites, so I had to rig it so that wasn't set till after the logons. Did a little testing and it seemed OK, but then it seemed OK to me until you pointed out that place where the PF7 went to 20 second hell. Anyway, you may or may not have seen the email I sent yesterday about a screen.sessiontype that would be helpful here, since the setting should be different for 3270 vs. tn3270 - right now I'm using the terminal ID to determine, since at the moment, the 4th position is "T" for tn3270, but I don't like depending on that. I could also use screen.group, since LU_group_1 is 3270 and LU_group2 is tn3270, but that, too could change and I'd forget to change the code. So a screen.sessiontype = "3270" or "tn3270" or "5250", etc. would be helpful. (btw, is 5250 support in?)
Append By: PeteL  When: 1999-01-06 06:22:35  New Status: Pending IE
Comment well, screen.sessiontype i think would still be helpfull, but no longer to me - we had a 3174 controller fail yesterday, and of course it was the one that Screensurfer was using, so I took the opportunity to switch over to full TN3270 and bypass the controller - all seems to be working fine, at least after about 1/2 day. Do you want to close this one, or leave it open for the screen.sessiontype suggestion? your call, feel free to close if you'd like.
Append By: WindSurfer  When: 1999-01-06 07:29:45  New Status: Closed
Comment The screen.sessiontype is already in another ticket that is currently "accepted"...so I'll close this one.