My sysval QINACTITV QINACTMSGQ QDSCJOBITV are not working properly always.

1480 pts.
Tags:
AS/400
Following are the values of my 3 sysvalues

QINACTITV      15

QINACTMSGQ   *DSCJOB

 QDSCJOBITV   45

While i have found them working fine, there are cases when i find a particular id showing as active for more than an hour.  Whereas the above sysvalues should ensure the id gets inactive in an hours time from the time the id was left unattended on the system.

Why could this be happening.?

Johnson

 



Software/Hardware used:
os 400 i series
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TomLiotta
    I have not directly investigated the QDSCJOBITV system, but I'd expect it to work similarly to the QINACTITV timer. A particular detail about QINACTITV might be useful to you regardless of how the behavior of QDSCJOBITV might match or not. The QINACTITV timer essentially sets the interval at which the system checks all devices. That is, a specific device is not checked every 15 minutes; it is checked when the 15-minute timer expires for the entire system. The timer is set system wide. So if a device enters an inactive state at 1 minute into the system-wide interval, it will show as only being inactive for 14 minutes when the first interval expires. If the device remains inactive, it will be an additional 15 minutes before the second system-wide interval expires. At that point, the device will have been inactive for 29 minutes and will exceed the limit set in the system value. On average, then, devices will be inactive for just under 1.5 times the QINACTITV value before getting marked. Some will happen just before an interval ends and others will happens just after an interval begins. That's not too hard to compensate for. In your case, you might simply choose to set QINACTITV to 10 minutes for example. But you also might need to experiment with QDSCJOBITV to see if it also is based on a system-wide timer. Start a few sessions at perhaps 5-minute intervals to track precisely when each one gets disconnected; and then mark when each one actually ends. I would suspect that all of them that are disconnected in the same system inactivity interval would end at the same time. If any of them get marked in a second inactivity interval, it might cause them to be ended after a second QDSCJOBITV interval passes, a full 45 minutes after the first group. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: