×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Thu, 14 Apr 2005, Ruel, Marc-Antoine wrote:
I tried to read this but it gives me nausea. :) Did you advance in your
research?
I finally have some interesting results. Running a sniffer revealed that
iSeries Access sends the following to the iSeries when pressing enter on
the first menu seletion (on my particular test screen):
12 a0 00 00 04 00 80 03 01 03 f1 ff ef
but tn5250 sends:
12 a0 00 00 04 00 00 03 01 03 f1 ff ef
the difference is the second byte after the hex 04 (the length of the
variable portion of the header). According to the RFC, this should always
be 00, i.e. the way tn5250 does it. Why iSeries Access does it
differently is unclear, but changing tn5250 to always send 0x80 causes it
to terminate unexpectedly. So far I can't find any docs to tell me what
the 0x80 might mean or under what conditions to send it. The RFC I'm
looking at is:
http://www.faqs.org/rfcs/rfc1205.html
Specifically in section 3. Data Stream Format.
If anyone has any clues I'd love to hear from you.
James Rich
It's not the software that's free; it's you.
- billyskank on Groklaw
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.