Profound Logic Forums

I have a mobile app running on a tablet where information is just scanned into fields on the screen requiring no additional input on the screen. When the last field is scanned I have a pui.click() to simulate them hitting enter. They can successfully scan through this screen about 20 time, sometimes more, sometimes less, and then it kicks them out to the signon screen. There are no errors that I can see that would cause this. Does anyone have any suggestions?????

Hello Patti,

We're sorry to hear that you are having issues with this. It sounds like you may be having an issue with your timeout timers. To correct this, you may want to extend your server side timeouts, set appropriate length client side timeouts, or submit the screen after each scan rather than after having scanned all barcodes. You can learn more about timeouts on our doc pages at the following links:

• http://www.profoundlogic.com/docs/displ ... de+Timeout
• http://www.profoundlogic.com/docs/displ ... on+Timeout
• http://www.profoundlogic.com/docs/displ ... t+A+Screen

We hope this helps! If you have any additional questions, please let us know!

Thanks,

I don't think this is a timeout issue. It is not happening if the screen sits idle. They are constantly scanning 2 barcodes and then control is sent back to the program. They can do this about 20 times and then it just goes back to the sign on screen.

I did check the links you included, and we have everything set according to the documentation.

Patti,
Just curious, is your IBM i OS version 7.3?
We've had a couple reports from an installation running on 7.3 where users were moving through browser screens (not mobile) as normal then suddenly they are returned to a signon screen. We too have all the PUI timeout settings as documentation suggests, timing sessions out at an hour of inactivity which users are accustom to which is why they reported this behavior to us knowing it wasn't normal.
It only started with them after upgrading to IBM i 7.3, but has only happened randomly to a couple users as far as we know. There was nothing abnormal in their job log, just that they ended their session.
Just fishing for answers at this point, nothing frequent enough or traceable to substantiate a support ticket. Don't want to hijack your thread.
Kevin H.

If it is timing out, there'd be a message that pops up saying that the session has timed out. If you are getting that when you dont' expect to (like Kevin's description) then it should be reported to Profound Logic Support.

If it's not giving a timeout message, then it's not timing out... at least not in a way that I'm familiar with! And, Patti never said anything about time outs, so I don't think that makes any sense, here?

Typically, the only reason an application goes back to the sign-on is because the back-end program (customer-written RPG, Node.js, PHP or Cobol program that drives the process) has ended. The first thing you should do is debug that program and determine what is going on when this happens... is it ending? is it receiving an error? If "nothing" is happening, what does that mean, that the program is still waiting on the display file?

More info please.

I just ran it through debug with a break point set on the EXFMT and on the 21st time when I stepped past that command, it just went back to the signon screen.... It never came back to the program. I checked the active jobs and the job seems to be still running. What information can I send you that will help you with this?

The active shows the function as being PGM-PUI0001202.

a) We're going to need to handle this in Support. There's no way it can be handled in the forums. Please contact support@profoundlogic.com for support.

b) We're going to need to be able to reproduce it.

Okay. Thanks Scott!

Started getting this problem when, I applied PTF's last week. Was there ever a solution?