Display record lock message via webspeed?

K

Kernel

New Member
Wondering if there is an easy way to do this... note that we're on an ancient version of Progress (9.1D) and are unable to upgrade at this time due to many reasons so please no flames... :)

We have users that connect to our WMS via RF guns. These guns each have an assigned linux username that kick into the WMS when logged in. More often than not, when a gun battery dies the user simply puts the gun in a cabinet, grabbing a new one, rather than getting another battery and resuming the session. This nevitably causes a record lock.

I can lookup the gun user ID locking the record with a quick query but I'm wondering if there is a way to do this from Webspeed so that the lock message would display in the browser without having to press CTRL C to end the script. The goal is to have the warehouse personell find these guns and fix the situation rather than waking us in the night to do it for them.

Example output from the editor on a query where I know there is a lock:

pick in use by mem_gun68,69 on pts/2. Wait or press CTRL-C to stop. (121)

Thanks!
 
You can find all locked records by querying _lock (leave as soon as you run into a _lock-usr with the unknown value).
But how are you going to know if a record is legally locked or not?!?
Why are the locks being left over in the first place - a gun dying is apparently not the same as a gun logging out.
 
You might also want to try the -lkwtmo startup option.

BTW - 9.1D isn't just ancient... it's also obsolete and unsupported. And buggy. But it's better than 9.1c so that's something.

Ultimately though the question that Stefan raises is the real problem. Why isn't the dead battery resulting in a logout? This sounds like some sort of serious misconfiguration. My guess would be that you're trapping SIGHUP somewhere on the Linux side.
 
Good question on the battery dying not resulting in a logout. It's actually because the guns connect to an intermediary Telnet server that keeps the connection alive so that battery changes do not require a logout. But perhaps I need to look at that intermediary server so that it will disconnect users when they are idle for a few minutes.
 
You must log in or register to reply here.
Back
Top