Re: Another assertion failed error... (fwd)

[Mike Madore <mmadore@xxxxxxxxxxxxxxxxxxx>]

Hi Scott,

This is cool.  Thanks for all the effort.  Would you be able to send me a
copy of the source to the program so I can reproduce it?

By the way, I was unable to send mail to klemscot@klements.com.  It
bounced.


To all:

What do you think the best way to handle theses non-printable characters
are?  I can easily copy the behavior of the real terminal if thats the
best solution.

Mike

---------- Forwarded message ----------
Date: Tue, 11 Apr 2000 14:17:24 -0500 (CDT)
From: Scott Klement <klemscot@klements.com>
To: Mike Madore <mmadore@mail.turbolinux.com>
Subject: Re: Another assertion failed error...


Hi Mike,

I wrote a program that displays a 1-byte field containing the EBCDIC
values from 0-255 (decimal).  I tried this same program under RUMBA 2000
under Windows 98, tn5250-0.15.8 under FreeBSD (probably not the current
one from CVS, this one is a few weeks old), and also on an IBM terminal
(3179-2).

Neither RUMBA nor the terminal ever actually "crashed", tho I did achieve
some strange results with them.   tn5250, as you know, does an assertion 
failed on some of the values :)

The attached file is in text format, with UNIX-style newlines. It tells
you what happened with each byte value.  

Here's an explanation for the results I listed in the attached file:
--------------------------------------------------------------------
Displays Blank = just a blank character is displayed.

Displays Block = a reverse-image blank, looks like a solid block

Displays Dup Char = on 5250 terminals, there is a character that means
                that the dup key was pressed. It looks like an asterisk
                with a horizontal line above it.  When Mr. Felice 
                implemented the dup key under tn5250, he chose to use
                a "block" instead, so the weird character didnt need to
                be reproduced :)

Displays Garbage = some misc character that didnt matter much to me was
                displayed :)

Screen Is Messed Up = the screen displays, but not all of the data is
                where its supposed to be.

Locks = Screen came up blank, and I had to kill the session and restart :)

RNQ1251 = The program that I wrote to display the characters crashes, with
                This IBM error message number.  You can do a:
                DSPMSGD RNQ1251 MSGF(QRNXMSG)  
                on the AS/400 to see what it means.  I could answer this
                message with a C to get back to my command prompt...



Hope you find this useful.

-Scott



On Tue, 11 Apr 2000, Mike Madore wrote:

> Hi Scott,
> 
> I'm pretty sure it is being caused by an undisplayable character.  The
> trace file seemed to be showing 0xFF.  We don't trap that one, so tn5250
> does an assert.  If you could whip together a quick program to cause the
> bug that would be great.
> 
> Mike
> 

EBCDIC  RUMBA 2000 (v6.0)
Value   U00 Build 1502.5.0      tn5250-0.15.8           IBM 3179-2 Terminal
------  ------------------      -------------------     -------------------
0       Blank                   Blank                   Blank   
1       RNQ1251                 Assertion Failed        RNQ1251
2       Cursor Pos Messed       locks                   RNQ1251
3       Screen Is Messed Up     Assertion Failed        RNQ1251
4       Locks                   Assertion Failed        RNQ1251 
5       Displays Block          Assertion Failed        Displays Blank
6       Displays Block          Assertion Failed        Displays Blank
7       Displays Block          Assertion Failed        Displays Blank
8       Displays Block          Assertion Failed        Displays Blank
9       Displays Block          Assertion Failed        Displays Blank
10      Displays Block          Displays Block          Displays Blank
11      Displays Block          Assertion Failed        Displays Blank
12      Displays Block          Assertion Failed        Displays Blank
13      Displays Block          Displays Block          Displays blank
14      Displays Block          Assertion Failed        Displays Blank
15      Displays Blank          Assertion Failed        Displays Blank
16      Screen Is Messed Up     Assertion This->curpos  RNQ1251
17      Screen Is Messed Up     Assertion (This)->cy    RNQ1251
18      Screen Is Messed Up     Assertion Failed        RNQ1251
19      Screen Is Messed Up     Assertion (This)->cy    RNQ1251
20      Screen Is Messed Up     Assertion Failed        RNQ1251
21      Screen Is Messed Up     Assertion Failed        RNQ1251
22      Displays Block          Displays Block          Displays Blank
23      Displays Block          Assertion Failed        Displays Blank
24      Displays Block          Assertion Failed        Displays Blank
25      Displays Block          Assertion Failed        Displays Blank
26      Displays Block          Assertion Failed        Displays Blank
27      Displays Block          Assertion Failed        Displays Blank
28      Displays Dup Char       Displays Block          Displays Dup Char
29      Screen Is Messed Up     Screen Is Messed Up     RNQ1251
30      Displays Garbage Char   Displays Block          Garbage Char
31      Displays Block          Displays Block          Displays Block
32-62   Displays Blank          Displays Blank          Displays Blank
63      Displays Block          Displays Block          Displays Block
64-254 "Normal Characters"
255     Displays Blank          Displays Block          Displays Blank