Ok. This situation has apparently been a long term one, but I'm trying to tackle it again since the user has been bringing it to my attention again.
Our iSeries (an 170, P05) is running v5R3.
The machine in question is running Windows XP.
Every morning, the user clicks on a batch icon (that is installed on about 8 other machines as well without issue).
Normally: Two sessions are launched usually marked Session A (for the printer) and Session B (for the user's screen)
The user logs into the first session's connection and then logs into the second session's connection (None of this involves green screens).
Then they are up and running for the day.
The machines are not shutdown or rebooted overnight unless a windows update requires it automatically.
The users know to sign off of their green screen program and then choose to Exit All for the iSeries Access. (I'm aware this leaves job logs behind for the printer sessions, but that's across the board for all printers and doesn't seem to be related to this issue).
Every morning most of the users still get Session A and B, so I don't believe the letters 'mean' anything by themselves...
For the problem machine, running the batch icon produces Sessions like E and H. (always different, never just A & B, and not sequential)
She can log into the first connection and then the second session's connection blinks as if it needs her to log in.
We can see the login box, but the cursor is an hourglass.
Both sessions are now 'hung' and stuck. Leaving them alone for 10 minutes does nothing.
We stop the process's in the task manager (there are only two pwpcs.exe's as I would expect from the batch script being run.. I didn't see any 'extra' pwpcs.exe's running, perhaps abandoned from the day before for some reason).
Trying the batch script for the second time, she can now log into both connections and start her day.
I don't see anything in the Windows Event Log except for an entry about pwpcs.exe being hung.
I don't see anything on QSYSOPR about an error or a failure.
A few years ago, I'm told that the machine was sent to our service contractors who took the whole thing apart and ended up giving us a completely new machine. They couldn't find a solution and I think everything worked for a while [but that could be just an assumption. I actually have users who DON'T report issues when they find them, because they think that they just have to deal with..]
I'm trying to troubleshoot this or at least investigate further and am stumped. Has anyone ever had a similar occurrence? Or perhaps have an idea of where I should direct my efforts? I'm thinking it will have something to do with the PC talking to the AS400 but I'm not sure how to find it...
Windows system? iSeries Access Configuration? iSeries/AS400 configuration?
Thank you.
Start Free Trial
