×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I am thinking of changing QUPSDLYTIM to *NOMAX and using only QUPSMSGQ.
However, I can see one case where the ENDSBS may not work. That would be
if I had a job that required ENDJOBABN to kill it. (I've had a few
lately.) This being the case, how would I determine "if the total delay
time is exceeds what is allowable for awaiting the restricted-state
condition being reached"? Compare QUPSDLYTIM to the elapsed time between
the initial CPF1816 message and the current loop iteration? I don't think
there's any further status flag to check.
How would you see adjusting QUPSDLYTIM? Keep in mind that adjusting
QUPSDLYTIM in between CPF1816 and CPF1817 is ignored by the current
process. We tried adjusting that after receiving a CPF1816 once after we
determined we had plenty of juice left on our ups and we wanted to wait it
out for a while longer. It still killed the system even though the new
QUPSDLYTIM gave us plenty of time left.
Rob Berendt
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.
midrange.com
