go to bug id or search bugs for
RPG programs called from a web environment should never fail and should monitor for all errors BUT in my real world scenario legacy programs can
occasionally hang on MSGW.
When using persistant connection the MSGW causes the disastrous effect on my website where other users requests begin to fail because they are waiting for the job which is now stopped on MSGW.
I need a modification to ibm_db2 that ensures that other users requests do not wait for the job that is stuck in MSGW.
Thanks to the guys at IBMi who have provided me with a test ibm_db2 on their YIPS website with a 'executing' flag solution.
This solution was success in resolving my issue.
This is a formal issue request to add 'executing' flag support beyond 2.0.1.
Add a Patch
Add a Pull Request