RE: PC5250 not accepting input -- MIDRANGE-L

Page down and backspace just "worked" for me. I can't even get my Sys-Rq line to come up. Attn doesn't do anything either. I received a message, so I didn't have to test that theory - it was still locked after I exited the message.
--
Sean Porterfield

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Perkins
Sent: Tuesday, June 02, 2009 11:38
To: Midrange Systems Technical Discussion
Subject: Re: PC5250 not accepting input

I was able to reproduce it. I actually have to press end+pagedown+backspace, but sometimes more that three times. I just keep pressing the keys until the the red X at the bottom disappears.

Also, the only work around I found was to send a break message, call up the attention line and end my previous request (option 2). When I do this a get a CPF7116 "End request temporarily delayed." message, but everything works after that.
--
James R. Perkins

On Tue, Jun 2, 2009 at 06:48, <tkreimer@xxxxxxxxxxxxxxx> wrote:

I know this thread had basically died out before I responded, but I
think I'm on to something here.
I can reproduce this problem on all three of my V6R1 early adopters,
but IBM says they can't reproduced it. Can anyone else with V6.1
(iSeries Access, not necessary the server OS) give it a try?
Read below, but but be sure to move the cursor off the input field and
press PageDown/End a bunch of times (three should do). Then try
function or "enter".

One of my users also manages to something that gets his session
'disconnected'. Not sure what that is all about, but I'm not sure I'm
ready to deploy 6.1 to the desktops yet.
The next service pack for 6.1 is due out end of June,

Tom

=====================
Tom Kreimer
Network Manager
Buckhorn Inc, Milford OH

From:
Tom Kreimer/Milford/Myersind@Milford
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
05/28/2009 01:49 PM
Subject:
Re: PC5250 not accepting input
Sent by:
midrange-l-bounces@xxxxxxxxxxxx

I had to dig this thread out of the trash from yesterday, as the
problem just started occurring to me today!

I can reproduce it by fat-fingering multiple keys at once while the
cursor

is not on an input field. The only keys I've found so far are the end
& page down at the same time three times (listen to three bells) and
then the function keys quit working. Those two keys are right next to
each other on my laptop, and I hit them while trying to page down
someplace where I could not. I am on the latest, V6R1 SI32504.
=====================
Tom Kreimer
Network Manager
Buckhorn Inc, Milford OH

From:
Gqcy <gmufasa01@xxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
05/27/2009 01:41 PM
Subject:
Re: PC5250 not accepting input
Sent by:
midrange-l-bounces@xxxxxxxxxxxx

I have seen this happen for as long as I have been using Client access.
And in previous versions, I needed to do A FULL REBOOT to get the key
functions back. I'm happy that now all I need to do is a restart of
the application.

Why can't Client access have a menu option to "restart the key
mapping", so the user doesn't have to kill their telnet session?

Porterfield, Sean wrote:

From: Mark Walter

Did anyone ever have an issue where PC 5250 (V5.9) wouldn't accept
input (I.e. Enter, Function Keys, etc, etc)? I can type in fields
on the screen. I can use a field exit and keys like that, it just
won't accept function keys or enter.

Yes, typically if I type something when the screen is updating.
Attn

and sys-req have historically been the most likely to cause this
problem, though in the latest and greatest PC5250 (Version 5.9
20080919 S) I've had it happen "frequently" on other keys.

--
Sean Porterfield

This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.