We have a application that occasionally runs into problems where users leave a record locked in one session (could be faulty data / unanticipated user action etc.) and then start new sessions which again hit the same record lock and become unresponsive. As documented in other posts in the forum, these sessions are unkillable in the p4 session manager. We are considering using LOCKED_ROWS_RETURNED=Y in our .ini to allow us to use the Record Locked logic position to display some user-friendly message, DSEL(F) etc. As this setting is system-wide, we are trying to establish as fully as possible the impact(s) changing this setting. Can anyone share (unexpected) behaviour they experienced after changing this setting? Or perhaps there is an equivalent logic command that we could set / unset within the scope of the functions that cause us most problems, avoiding a system-wide change. A complete regression test is not a realistic proposition.
The environment is ProIV 5.5 Native, Windows Server 2003, Oracle 9i.
No replies to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users