RE: Inactive Time Out

I have found that the System Value inactivity is a problem if you wish to
have different jobs treated with different time intervals. For instance you
may want QSECOFR to be locked after 5 minutes, QSYSOPR after an hour, and
Credit Control after 30 mins...
With QINACTITV you have to add up the 5 minute blocks to see if 30 minutes
has been reached - remembering to set it back to zero if you _don't_ get a
message in a 6 minute period.


Brendan



>The problem I saw with QINACTITV, back when I tried to use it, was that
messages were issued for each job, not >once, but each time the timer
expired, with no indication of how long that particular job had been
inactive. I >found it a nuisance. But your mileage may vary.

---

>This is by design. When the session has been inactive for the specified
period of time (QINACTITV), the >QINACTMSGQ function kicks in. This is why
the message queue handling program is desired. I looked at the code >that I
wrote for COMMON for this function in 1992, but with the explanation, it was
14 pages long. Probably too >long to put into my System Value handout.
(already 163 pages)

>It's feature, not a bug!



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---