The problem I've had with this has been inconsistent implementation of the TN3270E support on both the client and server sides. I started poking around with it because I couldn't get certain emulators to connect to specific addresses on Hercules, and it turns out that the emulators that seem to handle it WRONG are the ones that work the way we'd like.
The problem I've had with this has been inconsistent implementation of the TN3270E support on both the client and server sides. I started poking around with it because I couldn't get certain emulators to connect to specific addresses on Hercules, and it turns out that the emulators that seem to handle it WRONG are the ones that work the way we'd like. There's a setup dialog that happens between the TN3270 client and server when you first connect, and part of that dialog includes a flag that tells the client that the server supports TN3270E (which provides stuff like color and video attributes). Selecting a particular address uses an Extended address field called "LU Name" (c3270/x3270), "Device Name" (Extra), or "Resource Name" (Passport). Support for this is part of TN3270E, so strictly speaking, if the server doesn't tell the client it supports TN3270E, the client isn't supposed to send that field. It also shouldn't send the field if the TN3270E flag is turned off in the client (Extra), or if the model is set to a type that historically couldn't do "E", such as 3278. Extra and (especially) QWS3270 follow these rules, but Passport and x3270/c3270 don't. They'll both happily send the "Resource Name", even though the rest of the dialog is old "non-E" 3270 protocol, and many servers (including Hercules) will process the field even if they don't support TN3270E. There's another, later, part of the dialog where the client tells the server which features it actually supports (like color and fancy video), so usually the connection will still work even if you've tried to force the "E" protocol. The whole thing is really pretty forgiving most of the time. I'm sure there are folks on here that are more familiar with the protocol than I am who can explain it better, I'm just passing along what I found. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] > Behalf Of Pommier, Rex R. > Sent: Wednesday, June 14, 2006 12:17 PM > To: [email protected] > Subject: Re: [IBM-MAIN] OSA-ICC & Attachmate > > > We're successfully using RUMBA. One possible problem area is that the > emulator needs to support TN3270E and you need to plug the console ID > into the emulator device name field (at least that is the field name > within RUMBA). > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Doyle Banks > Sent: Wednesday, June 14, 2006 11:00 AM > To: [email protected] > Subject: Re: OSA-ICC & Attachmate > > I have had customers who used Attachmate successfully but it did take > some tinkering with the "model" setting and the screen size (number of > rows and columns). > > fyi...you probably know that IBM states that PROCOMM is the > "supported" > terminal emulator and while others "may" work, they won't > support them. > > Doyle Banks > Mainline Services Group > 17 W 635 Butterfield Road, Suite 120 > Oakbrook Terrace, IL 60181 > cell phone: 219.241.4902 > fax: 1-888-652-6914 > email: [EMAIL PROTECTED] > > > > > "Daniel A. > > McLaughlin" > > <Daniel_McLaughli > To > [EMAIL PROTECTED]> [email protected] > > Sent by: IBM > cc > Mainframe > > Discussion List > Subject > <[EMAIL PROTECTED] OSA-ICC & Attachmate > > .EDU> > > > > > > 06/14/2006 10:21 > > AM > > > > > > Please respond to > > IBM Mainframe > > Discussion List > > <[EMAIL PROTECTED] > > .EDU> > > > > > > > > > > Has anyone hooked up OSA-ICC using Attachmate? We are just > getting into > the > > ICC thing and are not sure if this will support it. We've > tried several > iterations of Attachmate, but don't seem to be able to make the final > connection. > Thank you in advance. > -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -------------------------------------------------------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
