Re: Lock condition... sort of

["Carel Teijgeler" <coteijgeler@xxxxxxxxx>]

Tony,

This came up last week, too, should be in tje MIDRANGEL. But no good 
explanation/answer was given.

I aasume you are using a Client Access emulation (or similar). My guess it is a 
communication error: Your emulation session does not make contact with the host 
anymore. So the cursor can be moved around (it is in the client) but the 
function keys or the Enter key does not send anything back and the system will 
not respond.

Pressing the [X] in the top right  corner is not a good idea, either.

I would opt for the Communication menu in the client, disconnect and reconnect 
again. You have to log in again. If that is possible, your sesion connects with 
the host again.

I had this once, other users im my shop have had it more frequently. This is 
the way I solved my "lock".

What if the user is in a application, with open transactions? Perhaps 
disconnecting the job from WRKACTJOB (option 13), and hopefully the user will 
get the same device name again and can log in.

Hopefully others have a better solution than mine. I lack the experience with 
this. It has been put to the attention of our system manager.

Regards,
Carel Teijgeler

*********** REPLY SEPARATOR  ***********

On 26-3-04 at 9:11 CarollaT@xxxxxxxxxxxxxx wrote:

>Where do I start... I am not 100% certain this is an RPG problem, but it 
>involves an RPG program, so here goes:
>
>I have written an RPG application, using a display file and an RPG module
>(pretty lengthy), and I will include this if necessary, but I first wanted
>to see if anyone else has had this problem, and knows a solution, or a clue 
>they could hand off...
>
>The user presses an Function key, and my display window pops up (a DSPF with
>the ASSUME keyword in a format), they type in their data, press enter, or F3
>to exit, and the main program takes over.  Perfect.
>
>But sometimes, the user's screen "locks up".  When I say locks up, here is
>what happens:  none of the F-keys work at the terminal, nor does the Enter
>key.  They can type, but they can't press Enter or Sys Req, or anything. 
>No input inhibit, nothing.  If they get a break message, they can F3 out of
>that, but back to the "lock" condition. 
>
>I have the Fkeys defined in my DSPF (at the file level), and I have
>responses that work 99% of the time in my program.