× 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.


  • Subject: Re: tn5250 bug frustration, also 0.16.0pre2 released.
  • From: "Jason M. Felice" <jfelice@xxxxxxxxxxxx>
  • Date: Thu, 01 Jun 2000 09:07:00 -0400
  • Organization: Cronosys, LLC

Scott Klement wrote:
> 
> Hi,
> 
> I've been complaining about a bug since the 0.13.x series of tn5250.  The
> bug happens (at least, this is where I see it) when you do this:
> 
> 1) Type UPDDTA SOMELIB/SOMEFILE on the AS/400
> 2) Hit F10 & Enter  immediately (as fast as you can)
> 
> In March, just after version 0.15.8 was released, Mike Madore was kind
> enough to look into this bug, and fix the problem.   That really made my
> life easier, since I was not accidentally crashing tn5250 all the time.
> 
> Unfortunately, Mike's fix caused system request to stop working when the
> keyboard was locked.  Which, silly me, I also asked to have fixed.  Then,
> Jay Felice went and removed Mike's fix....  unknowingly causing my UPDDTA
> bug to resurface.
> 
> Now, another release is made!  Now?  After removing the bug fix that I
> yearned and lusted after for so long? Frustrating.

Mike and I discussed it, and we decided that, since we'd be making
a release soon, we should back out the fixes that we did for Scott. ;-)

Actually, the pre1 release was made, knowing that we must still fix that
bug, because
Mike is persuing adding lots of nifty features to tn5250 paid for by his
employer.  Adding the kind of features that Mike is will make tn5250
very
unstable, so it is appropriate to fork the `stable branch', especially
since
we have fixed a lot of bugs and worked out most of the issues with new
features added in 0.15.x

Splitting the stable and development trees without making an official 
release can cause a maintenance nightmare - it can be difficult to see
which bugs have been fixed in which branch.

This is the big bug that I intend to fix for pre2. 

BTW, for those unfamiliar with CVS, you can check out the latest on the
0.16
branch by supplying `-r b0-16' to the checkout command.  cvs update will
then
update only to the latest on that branch.  Example:

cvs -d :pserver:anonymous@cvs.cleveland.lug.net:/tn5250 checkout -r
b0-16 -d tn5250-0.16 tn5250

... will check out the latest in the 0.16 branch and put it in the
tn5250-0.16
directory.

Also, every release is tagged in cvs like so: v0-15-8 for 0.15.8, you
can use
that `-r' switch above to retreive a particular version.

Scott, I just applied your fix, except I did:

        if ((This->session->read_opcode)||(aidcode < 0)) ...

since the `pseudo aid-codes' are less than zero (currently only SysReq
and
Attention, but TestReq would belong there also).

tn5250-0.16.0pre2 is up at http://cvs.cleveland.lug.net/

> I know I'm a pest about this stuff -- but hey, I just want the thing to
> work, just as you do... :)

Hey, I appreciate you kicking my butt around - I need it, since there's
only
about a handful of things I do on the 400. <g>
(sign on, WRKOUTQ, ENDWTR, STRRMTWTR, WRKACTJOB, CRTOUTQ, PING, TELNET
(I can
hear our emulator groaning under the strain for that one), ENDTCP and
STRTCP
whenever the AS/400's hub looses power, STRTCPSVR, CFGTCP, I think
that's it).

>
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.