We are running several thin clients in our plant. Every once in a while one will appear to be in limbo but is really still connected. The user does not appear in wrkactjob, but continues to function. Since at this point we can't work with it because it is no longer showing up in QINTER, we have the user signoff power down and up and sign back in. Since the user is no longer being seen(but is really there) We have nothing to track on. We have added a signoff *list option to their menu to try to caputre the job log to see what errors ocured.
Unconfigured Ad Widget
Collapse
Announcement
Collapse
No announcement yet.
thin client to as400 losing connection but still active
Collapse
X
-
thin client to as400 losing connection but still active
cesarzn wrote: > We are running several thin clients in our plant. Every once in a > while > one will appear to be in limbo but is really still connected. The > user does not appear in wrkactjob, but continues to function. Since > at this point we can't work with it because it is no longer showing > up in QINTER, we have the user signoff power down and up and sign > back in. Since the user is no longer being seen(but is really there) > We have nothing to track on. We have added a signoff *list option to > their menu to try to caputre the job log to see what errors ocured. This doesn't seem right. If I understand you correctly, the user is still able to do his workstation work as if nothing was wrong, but you can't find them in QINTER. I would suggest doing either a WrkUsrJob with their user profile, or a WrkObjLck with their profile to find where the job is really located. Bill
Comment
Comment