|
Leo At 11:23 AM 11/25/97 -0500, you wrote: >Hi, > >I changed the System Value QQRYTIMLMT to 300 (seconds) to limit the >query runs to about 5 minutes. > >In the interactive environment, the user gets the message CPA4259 when >the query is about take longer than the time limit, with the option to >continue or cancel the request. That works fine. > >But when the request is executed in batch mode, the message gets >AUTOMATICALY the default reply 'C', not allowing anyone to enter a >reply. The only messages sent are 1) the user receives a message saying >that the system operator received a message, and 2) the system operator >receives a message saying the 'previous cl command failed' with options >C, D, I, and R. The reply to this message, obviously, will not allow the >job to run regardless of the time limit, but will either cancel/ignore >the query request (options C, D or I) or retry the same query request >(option R) with the same parameters, just to get the same results. >Unless, before replying with an 'R', somebody change the system value to >a greater number. > >What would be the best way to operate, when the job is a 'batch' type, >to allow someone (the user or the system operator) to use his/her >judgement to kill the request or to continue. >We do have many programs with OPNQRYF and I would appreciate if I would >not have to modify all of them! Also, what's the INQMSGRPY setting? Sounds like it's *DFT. Cheers Vernon Hamberg Systems Software Programmer Old Republic National Title Insurance Company 400 Second Avenue South Minneapolis, MN 55401 (612) 371-1111 x480 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@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.