Single Interactive Job - Inactive time?

[David Abramowitz]

At a shop where the system value to disconnect jobs is set to thirty minutes, I have been asked to terminate one particular workstation after five minutes of inactivity. Any ideas or suggestions would be welcome. TIA, Dave

[B.Myrick]

David, I have not done this on the /400, but on the /36 I included the name of the workstation to make inactive, and used the INFDS to get the WORKSTN ID, the time the program became active and would kill the job when the allotted time of inactivity had passed. Don't know if this helps, but it's all I know about it, Bret

[Guest.Visitor]

David, try this link. It has an example of a program similiar to what you want to do. John http://as400service.rochester.ibm.com/s_dir/slkbase.nsf/adc98bf383a2fe808625680b 0002037b/ccd92ccc0c87bd60862565c2007d2aa7?OpenDocument

[David Abramowitz]

Thank you John. The example given there appears to restrice the inactivity timer to a job or set of jobs. I want to keep the inactivity timer active for all jobs, just end this one job earlier. i.e. - The inactivity timer is set for 30 min. I want to end this one job after 5 min. of inactivity. Dave

[Guest.Visitor]

David, it seems to me that you could use this technique. If you change inactivity to 5 mins for all jobs, you could fake the 30 minute inactivity whithin the program. Just a thought!

[Guest.Visitor]

David, This may or may not be useful information for you. From one of the IBM manuals: "The QINACTMSGQ system value determines what action the system takes when an inactive job exceeds the specified interval. When the system is started, it checks for inactive jobs at the interval specified by the QINACTITV system value. For example, if the system is started at 9:46 in the morning and the QINACTITV system value is 30 minutes, it checks for inactive jobs at 10:16, 10:46, 11:16, and so on. If it discovers a job that has been inactive for 30 minutes or more, it takes the action specified by the QINACTMSGQ system value. In this example, if a job becomes inactive at 10:17, it will not be acted upon until 11:16. At the 10:46 check, it has been inactive for only 29 minutes. " So, what I'm saying is that your particular user may actually be inactive for 9 minutes before the OS/400 detects this inactivity. Your client may need to know this. Chris

[David Abramowitz]

Thank you for your response. I want to keep the 30 min limit for all jobs.. .. ..Except this one. I want to cut this user short after five minutes of inactivity. Dave