Re: Disk percent busy causing software errors?

On 25 Feb 2013 08:23, rob@xxxxxxxxx wrote:

In pmr 67389 082 000 the technician is telling me that the error I
am getting may be because my WRKDSKSTS reports my disks are too busy:
msgMCH1206T/LIBNOTES in QDOMINO853 TM/FPCLIB TP/fmul stmt/3
"Floating point overflow condition detected."

<<SNIP>>

Long term corrective actions: Move this guest lpar to non guested
lpar with its own disks. Target date June 2013.

IMO the best fix for the noted error, is to correct the calculations being made in the code at the failing statement. A code change made to avoid the overflow condition, given any valid inputs.

If the issue is for invalid inputs to that program, then instead, to correct the problem with whatever is returning the bad data to the program for the operands used in the [therefore failing] calculation.

Although if the effect of the error is merely that the error condition gets logged, such that the code is getting valid inputs and producing valid outputs irrespective of an overflow [i.e. the overflow is monitored and handled], then an approach that might limit the occurrences [or simply ignoring the message] would seem acceptable. And then as a suggestion: That the code could be changed to remove the error message and optionally log a diagnostic [e.g. that the disks are so busy that the ¿whatever? calculations can not be completed] issued\logged in place of the escape... if the final outputs considered insufficient to convey that information without a diagnostic being logged.