Hello John
It's better to let the HTTP server handle these kind of things with its timeout mechanisms. You have among others the KeepAliveTimeout and MaxPersistentCGITimeout. If you start to mess with jobs in the HTTP server yourself you can get into very weird problems. We've been there 🙁
The other thing I would advise you is to make a proper on-exit section in your B2B-procedures to clean up record locks and cursors and so on.
kind regards,
Martijn van Breden
lead software architect
We have some RPG programs to menage a B2B site; some times happend, for lost connection or other situation, that the web connection go down, but the Ibm i job remains active and with him also some record locks, so when the user try reconnect , receive error “record already allocated by another job”. I was looking for an example that in this case , let to the rpg program , when receive that error (“record already allocated by another job”), to automatically kill the job that locks the record.
Thanks in advance
P.S. also other suggestions are welcome
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
midrange.com
