On Thu, 30 Mar 2017 14:48:24 -0500, Joel M Ivey <[email protected]> wrote:
>I mis-spoke. At the time of my first post we had NOT moved the fresh copy of >IEFACTRT from cbt109 into production. We did this past weekend and S071 >abends were resolved. (You were correct, the USING R15 was absent in the old >IEFACTRT.) However, the 0C4 abends stlil occur within certain address spaces >with high utilization. Also on these address spaces the output gets garbled: > (Also notice the comma in front of EXCP TOTAL.) >. . . The problem in the recovery routine will only show up if some other abend causes it to be entered. Support did tell you that the recovery routine was entered because of a prior 0C4, but I don't know if they also said anything about the cause of the 0C4. As nobody else seems to have had this problem with the CBT109 IEFACTRT, you will have to look at what caused the 0C4. I took a very quick peek at the code in the CBT109 IEFACTRT that formats the EXCP TOTAL, and it appears that the leading comma is due to the 8 byte field in the line being too small for the value (it EDITs the value into a larger field, then moves only part of the result into the message, losing some of the high-order digits). I don't see a potential 0C4 there, but I might have missed something. I also don't know if the value it was tying to display is actually correct, but EXCP total could easily be greater than 999,999. Perhaps this has been happening for years but nobody noticed it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
