This thread started when you mentioned you wanted to imporve the
functionality of distinguishing between various stated.
You also specifically mentioned the Pre Help Error State in your post.

I should have been more explicit in that the behavior I was describing was
specifically how to handle the help key in Pre Help Error State (which as
far as I knew was not working last time I checked. All appologies if I am
mistaken.)

When the keyboard is in Pre Help Error and the user presses the HELP it is
incorrect to send the HELP AID key (as far as I understand from the
documentation, behavior of client access, and packet captures) .
What is correct is what I mentioned. Construct a new display data stream as
described, and send that to the 400.
In turn, it will bring up a screen giving you more verbose error
information.

For example, if the error is "Cursor in protected area of display."

Then the "Additional Message Information" is:
 Message ID . . . . . . :   KBD0005       Severity . . . . . . . :   10
 Message type . . . . . :
 Message . . . . :   Cursor in protected area of display.
 Cause . . . . . :   To enter data, the cursor must be in an input field on
the
   display.  Data cannot be entered in a protected area of display.
 Recovery  . . . :   Press Error Reset key.  Move the cursor to a field
where
   the data can be entered and then enter the data.

It was just one little piece to add to the overall puzzle of various states
and actions.

If you need more specific information please contact me via email.

To avoid spam:
My account name is markb
and the domain is cms400.com



                      Scott Klement
                      <klemscot@klement        To:       linux5250@midrange.com
                      s.com>                   cc:
                      Sent by:                 Subject:  Re: [LINUX5250] 
Keyboard States
                      linux5250-admin@m
                      idrange.com


                      11/04/2002 05:03
                      PM
                      Please respond to
                      linux5250







Mark,

I was asking where I would find the "little blinking numbers" and
how to tell which one to put in the corner, not how to send the help
sequence.   None of the documentation you referenced explained this.

At any rate, I've already done a "best guess scenario" with the help
from Buck Calabro, and put it into CVS.

I decided to forego having those numbers blink in the corner, and simply
display the human-readable error message immediately.



On Mon, 4 Nov 2002 MarkB@cms400.com wrote:
> It's vaguely and poorly documented, and took me a little while to figure
> out.
>
> here
http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/CO2E2001/16.2.2.2
> and here
http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/co2e2001/15.8
>
> The return error code can be constructed by taking the 2-5 bytes of the
> current error line (assuming the error is still diplayed there) and
> creating a 2 byte code as such:
> Assuming
> 1. "errorline" contains attributes and EBCDIC values
> 2. errorline[0] represents column 1
>
> errcode[0] = ((errorline[2]&0x0f)<<4 ) | (errorline[3]&0x0f)
> errcode[1] = ((errorline[4]&0x0f)<<4 ) | (errorline[5]&0x0f)
>
> Then write a record back to the 400 with (FLAG_ERR_BYTE, screen_op_code,
> errcode)
>

_______________________________________________
This is the Linux 5250 Development Project (LINUX5250) mailing list
To post a message email: LINUX5250@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/linux5250
or email: LINUX5250-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/linux5250.








This thread ...


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

This mailing list archive is Copyright 1997-2020 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].