RE: Intermittent Member lock after UPDATE using ACS Run SQL Scripts

I see similar behavior when using the SQuirreL client. I've found that by running a different query, the lock goes away.

I seldom use iACS SQL Scripts, and, when I do, I never leave it running.


HTH



-----Original Message-----
From: Paul Bailey [mailto:PabloMotte+Midrange@xxxxxxxxx]
Sent: Tuesday, November 28, 2017 3:13 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Intermittent Member lock after UPDATE using ACS Run SQL Scripts

I'm on the latest version of ACS (1.1.7.2) and v7r1. I created the JDBC connection to the i in the ACS Run SQL Scripts (RSS) with all the default options except for the "default sql schema" (list of relevant libraries).
Journalling is switched on for all data files, but the "isolation level" in the JDBC properties is set to "no commit" (the default).

I've noticed that "sometimes" when I do an update to a file using the RSS screen a SHRRD member lock is HELD after the update has finished and never goes away unless the RSS JDBC session is ended. This doesn't happen every time, but regularly enough that a handful of updates will end up keeping locks on some/all members updated. (The job with the member locks is specified in the RSS plugin's status bar.)

Has anyone else noticed this? You just need to run the same update a small handful of times before the lock is then HELD.

It isn't a huge problem, but obviously things like CLRPFM on workfiles won't work if someone has a lock. Getting rid of the lock requires finding out whose RSS session is locking it and getting them to disconnect/reconnect... but it is still slightly inconvenient!


-Paul.