|
There are several system values that control the timing for this.<mailto:jlcrosby@xxxxxxxxxxxxxxxx%3c%0b>> mailto:jlcrosby@xxxxxxxxxxxxxxxx>>
QINACTITV *SEC Inactive job time-out
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_<https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_>
71/rzarl/rzarltmintvl.htm
QINACTMSGQ
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_<https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_>
73/rzarl/rzarltmmq.htm
QDSCJOBITV *SYSCTL Time interval before disconnected jobs end
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_<https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_>
72/rzarl/rzarldscjob.htm
I also created a job monitor.
All Interactive user jobs end after 12 hours.
Some of our old apps use job start date/time, and if there changes that go
into effect at midnight, there job would not sense the change.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob Berendt
Sent: Thursday, May 03, 2018 9:23 AM
To: Midrange Systems Technical Discussion
Subject: RE: Disconnect job / end job question on locks
Honestly I think the average user may be more receptive to this than in
the past. My bank's website does this. And several other websites. Some
so quick it drives me a little bonkers but that's just the way it is.
Of course killing that query from hell which takes 10 minutes may be a
little frustrating, but it may not be a bad thing from a system resource
perspective.
Then again, killing our Infor month end job, which is only ran by a very
intense guy in systems, may not end well for you.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com<http://www.dekko.com>
From: "Ed Waldschmidt" <ewaldschmidt@xxxxxxxxxx<mailto:ewaldschmidt@xxxxxxxxxx>>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>
Date: 05/03/2018 09:13 AM
Subject: RE: Disconnect job / end job question on locks
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>>
I don't think this is an ACS issue. We have a package called TIMEOUT
which is by user profile. We automatically log people off when they are
abusive. It is a relatively simple RPG program that sits in batch and
logs people off if they have been inactive for a period of time.
Ed Waldschmidt
IT Project Manager|PHD, Inc.
9009 Clubridge Drive
260.479.2283
*********************************************
[cid:1__=0ABBF515DFC231328f9e8a93df93869091@local]
http://www.phdinc.com/<http://www.phdinc.com/>
[cid:image002.jpg@01D201BD.96D3B7F0]<
https://www.phdinc.com/resources/socialmedia/<https://www.phdinc.com/resources/socialmedia/>>
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>> On Behalf Of
JRusling@xxxxxxxxxxx<mailto:JRusling@xxxxxxxxxxx>
Sent: Thursday, May 3, 2018 9:07 AM
To: midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>
Subject: Re: Disconnect job / end job question on locks
Someone should improve ACS such that, when you File>Exit or click the X on
an emulation session it can check to see if it is in a "signed-on" state,
and if so, pop up a windows message box that says "You must signoff
emulation session to exit.".
Just my 2 cents.
John
She did tell me she's been "not signing off" and merely clicking the Xto
close sessions ever since she's been here. I told her that was A BadThing.
<snip>
----------------------------------------------------------------------
message: 1
date: Thu, 3 May 2018 08:36:11 -0400
from: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx<
subject: Re: Disconnect job / end job question on locks
Just did that. The lock was gone in less than 5 seconds.
Maybe I have a less than truthful user. Nah. Can't be.
She did tell me she's been "not signing off" and merely clicking the X to
close sessions ever since she's been here. I told her that was A Bad
Thing.
</snip>
<br />
The information in this email is confidential and may be legally
privileged.
It is intended solely for the addressee. Access to this email by anyone
else is
unauthorized. If you are not the intended recipient, any disclosure,
copying,
distribution or any action taken or omitted to be taken in reliance on it,
is
prohibited and may be unlawful.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<<mailto:MIDRANGE-L@xxxxxxxxxxxx%3c>
mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l><
https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<<mailto:MIDRANGE-L-request@xxxxxxxxxxxx%3c>
mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l><
https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx%3cmailto:support@xxxxxxxxxxxx>> for any
subscription related questions.
Help support midrange.com<http://midrange.com><http://midrange.com<http://midrange.com>> by shopping at amazon.com<http://amazon.com><
http://amazon.com<http://amazon.com>> with our affiliate link: http://amzn.to/2dEadiD<http://amzn.to/2dEadiD><
http://amzn.to/2dEadiD<http://amzn.to/2dEadiD>>
Disclaimer Confidentiality Notice: This email, and any attachments and/or
documents linked to this email, are intended for the addressee and may
contain information that is privileged, confidential, proprietary, or
otherwise protected by law. Any dissemination, distribution, or copying is
prohibited unless otherwise specified. This notice serves as a
confidentiality marking for the purpose of any confidentiality or
nondisclosure agreement. If you have received this communication in error,
please contact the original sender.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.
Help support midrange.com<http://midrange.com> by shopping at amazon.com<http://amazon.com> with our affiliate
link: http://amzn.to/2dEadiD<http://amzn.to/2dEadiD>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.
Help support midrange.com<http://midrange.com> by shopping at amazon.com<http://amazon.com> with our affiliate
link: http://amzn.to/2dEadiD<http://amzn.to/2dEadiD>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.
Help support midrange.com<http://midrange.com> by shopping at amazon.com<http://amazon.com> with our affiliate
link: http://amzn.to/2dEadiD<http://amzn.to/2dEadiD>
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
