Path: utzoo!utgpu!watserv1!watmath!att!news.cs.indiana.edu!spool2.mu.edu!sdd.hp.com!wuarchive!uunet!bbs!karl From: karl@naitc.naitc.com (Karl Denninger) Newsgroups: comp.protocols.ibm Subject: Re: IBM Mainframe SNA to TCP/IP Hosts; X-windows, etc Summary: Resolved! At least on the emulator end, that is Message-ID: <1990Dec14.200617.14005@naitc.naitc.com> Date: 14 Dec 90 20:06:17 GMT Article-I.D.: naitc.1990Dec14.200617.14005 References: <9012012326.AA11156@lilac.berkeley.edu> Reply-To: karl@bbs.naitc.com (Karl Denninger) Organization: A.C. Nielsen Co. Lines: 47 In article <9012012326.AA11156@lilac.berkeley.edu> Jay Maynard writes: >In article <12720003@hpspdra.HP.COM> bc@hpspdra.HP.COM (Bill Crandall) writes: >>You might try to reconfigure your host so that it doesn't send >>a Write Structured Field. Look in the hostgen. > >>Or check the Query Reply sent by your 3270 emulator to make sure >>that it's not telling the host that it supports WSFs. There's a bit >>in the Query Reply that indicates that (although it might be >>disguised as a "Reserved" bit -- make sure all "Reserved" bits >>are turned off). > >We ran afoul of one other gotcha: Run a VTAM trace on the failing session. >Look at the query reply, and make sure it isn't lying about its capabilities. >If not, then your host program may be making invalid assumptions about the >terminal's capabilities, and acting as though some unspecified capability >is there when it wasn't mentioned in the query reply, just because none of >the standard terminals acts that way. We were able to get this working -- sort of. We got ahold of a X-windows client that does full color and GDDM APA graphics (which is really nice)... and now, all of a sudden, it works (then again, this one understands WSF calls). The Mitek gateway, though, won't do auto-selection of terminal types, so we still have a problem. It's not as serious as it was before. Mitek says they're going to have a fix for the multidrop problem by Tuesday of next week.... if they do, and can provide automatic selection of terminal model (with a default for vt100 terminal clients) then perhaps we can get things resolved there as well. Then again, maybe not. Who really knows at this point. I've been asked not to release the source of the X-windows client for this yet, pending cleanup of the code and a real release. I'm sure we'll see it on the net eventually. Btw: It's is REAL good... I really do like it, even though it is a little rough around the edges at this point. -- -- Karl Denninger AC Nielsen kdenning@ksun.naitc.com (708) 317-3285 Disclaimer: Contents represent opinions of the author; I do not speak for AC Nielsen on Usenet.