Hi
I get an input inhibited keyboard lock when displaying a 24x80 window from
a 27x132 display. It's happened in all versions I've tried since 0.12.51,
so it's not a new thing. To reproduce it open up SEU in 27x132 mode, hit
F21 to get a command line and run DSPSYSVAL QTIME. The screen is shown
correctly, but shows X II at the bottom, and needs a C-r to reset it. In a
source debug tool we use (that has a 27x132 mode) a cursor invoked
DSPPGMVAR gets the same error, and the 27x132 screen shows it when
returning to that screen. It seems linked to output only formats - if any
input capable fields are on the 24x80 screen, everything works fine.
Another weird one relates to using the attention key from inside a systems
request. In CA, pressing the attention key while in one of the systems
request options does nothing. In tn5250, it does nothing, but pressing
enter causes the session to lock up (can be freed by a SysReq 2, though).
This is an improvement, because prior to 0.15.6 the session died at this
point. I found this because we use a group job menu system driven by the
attention key, and also have SysReq 3 running a WRKJOB, rather than DSPJOB
(only for authorised users, that is). I quite often forget I've done a
SysReq 3 to get a command line, and hit C-a to swap jobs somewhere down the
line.
Other than that, 0.15.6 has been extremely stable for me. If I can work out
how to put Frank Richter's cursor position code in place (unless that's
pencilled in for 15.7/16.0) I'll be well way.
Regards, Martin
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to [EMAIL PROTECTED]
| To subscribe to this list send email to [EMAIL PROTECTED]
| To unsubscribe from this list send email to [EMAIL PROTECTED]
| Questions should be directed to the list owner/operator: [EMAIL PROTECTED]
+---
