Re: Timeout ACS SQL Session

[Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>]

Thanks all. I was leaning towards ending the jobs which were holding the
locks.  I just wanted to make sure I hadn't missed a configuration setting
somewhere.



On Tue, May 29, 2018 at 10:29 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

> I don't know of any way to time-out ODBC and remote command jobs.  My best
> advice would be to just end them as part of your backup process.
>
>
>
> -----Original Message-----
> From: Gord Hutchinson [mailto:gordm1@xxxxxxxxxxxxxxx]
> Sent: Tuesday, May 29, 2018 6:20 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: Re: Timeout ACS SQL Session
>
> 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
>
>
>
>
> --
> 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