× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.