Re: Timeout ACS SQL Session

Gord

I've run into a similar issue with the Run SQL Scripts thing - not overnight, since I shut my company laptop down and take it home with me all the time.

Still, locks can surprise me at times, esp. on a development LPAR - interesting question and a needful answer.

One thought on the script thing - is there a setting in the JDBC stuff that could affect this?

Cheers
Vern

On 5/29/2018 6:19 AM, Gord Hutchinson wrote:

Yes, I suppose I could have been clearer about the issue.

Most of our developers are now using Run SQL Scripts in ACS. The problem
is they sometimes go home at night and leave the Run SQL Scripts window
open. If they have an SQL result open, the objects (and sometimes records)
remain allocated to the QZDASSINIT job. This has impacted our save as well
as other jobs.

I have the same issue with RDi sessions. They go home and leave locks on
the source files which then don't get backed up.

I would like to know if there is a way to terminate these jobs similar to
QINACTITV for 5250 sessions.


Thanks,


Gord



On Mon, May 28, 2018 at 11:18 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Hi Gord

Isn't this controlled with a system value or 2? Maybe tell us just what
kind of termination you are thinking of.

Cheers
Vern

On 5/28/2018 1:40 PM, Gord Hutchinson wrote:

Is there a way to terminate ACS SQL sessions after x amount of inactive
time?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD