How to fix problem of AS/400 Workstation locking up after pressing enter ?
When a user presses "Enter" the AS/400 session locks up sporadically.
The "X SYSTEM" appears on the status line like it is locked but WRKACTJOB doesn’t
show any locks or even the program processing any files.
The only way to free it is by pressing "Shift & Esc", then return to the session.
We are on V5R1M0 using Client Access Express for Windows version 5.0 .
Nothing is unique about the RPG program, and it is used about 100 time a day
by 4 users.
It appears like the AS/400 is sending to Client Access, but the screen is not changing.
Anyone have any suggestions ? (besides upgrading to a new AS/400 !)
Software/Hardware used:
Software/Hardware used:
ASKED:
August 5, 2009 5:30 PM
UPDATED:
August 7, 2009 2:35 PM
RELATED QUESTIONS
Answer Wiki:
Thanks,
I have done all that file checking and nothing moves.
I cannot duplicate the problem on demand.
At the worst I will put on the STRCPYSCN to see what the user is keying.
I am going to try :
1. Recompile DSPF & RPG Program
2. Reload Client Access
Thanks Don
To see all answers submitted to the Answer Wiki: View Answer History.
Control I or Control S causes something similar to happen on my machine. Is it possible the user is doing that before pressing Enter.
Joe
If you’re going to reload Client Access, download and install the latest PTF for it.
Have you checked NETSTAT? Look up the users remote IP address and verify the active bytes in/out for the user.
How many users are logged in? Check the active number of users in QINTER (WRKSBS F11) versus the MAXACT for the subsystem (DSPSYSSTS). If the users exceed the MAXACT, they’re going into an INEL status.;
Thanks,
I will check out the previous suggestions.
The user has two sessions going. The other session is not having any connection problems.
The MAXACT is set to *NOMAX, none of the other 40 users have reported any problems.
I recompiled the programs last night, it might be a few days until the problem rears it’s ugly hhead again !
I’ll post if any thing comes up (or not).
I am having the same problem with Client Access V6M1. IBM sent me a new file, PCSLT52.dll. It helped but has not fixed the issue. We are trying to run a trace on the keyboard and the TCP/IP events so they can find out what the problem is. I am not having the problem with clients using the old version.
In our case we can press Esc instead of Ctrl-Esc.
Well the screens hung up again, even after recompiles.
The next step is to reload Client Access.
Slhamilton, you are right the Esc works too.
Nice(?) to know someone else is having the same problem that I can talk to.
This is an i5 !
then the truth is out there..
You either have a PC issue, a comms issue, an applicatiuo issue or an i5/os question.
you say the event is random, and other users, and the same PC, are ‘usually’ OK ?
so we assume no actual faults in the software.
If it is the application, then WRKACTJOB will allow you to see if the application called is hanging on, say, a record lock – did you check all locks when you looked at the job? – if another user is accessing the same record, then a badly behaved application (poor coding) will wait.
Set up 2 screens, access a record at one, try logging in from the other.
Repeat the multi user test with as many combinations of potential problem that you can invent.
Look at the comms – use WRKCFGSTS for the device at issue and see what’s happening.
Reinstalling stuff is a PC Geeky answer – re-boot the PC’ – ‘reinstall the software’ – what kind of diagnosis/fix is that.
Praise be that Microsoft don’t make aeroplanes or they’d fall out of the sky. .