|
At 14:44 06/21/2000 , Phil wrote: >Has anyone had any success (or even attempted) limiting or excluding certain >UserID's from the Inactive Job timeout function? We have a PC based data >collection system that passes data to the AS/400 using a Rumba session. This >job needs to stay active all the time, but there could be long periods of no >activity. These's another system value, QINACTMSGQ. If you put the name of a user message queue in it, the system will send message CPI1126 when the inactivity time limit expires instead of disconnecting or ending the job. You can write a fairly simple CL break handling program to monitor the queue and do whatever you like. Both the device name and user ID can be retrieved from the message data, which consists of the qualified job name (job number, user ID, device name). Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | 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 +---
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.