Hmmm. Not sure I totally see the distinction. I am sure I don't get the philosophy. If anything, wouldn't the opposite make sense: return codes for user errors and ABENDs for system problems?
In any event the distinction ought to be documented (assuming it is not rather than it's there and I am not seeing it). I just found this in the Services Guide. It is misplaced: it is under Creating a guard area and changing its size. It is not the answer but it is a hint. Use COND=YES, conditionally requesting the change, to avoid an abend if the request exceeds the MEMLIMIT established by the installation or if there are insufficient frames to back the additional usable area of the memory object. If it cannot grant a conditioned request, the system rejects the request, but the program continues to run. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Smith Sent: Friday, January 25, 2019 3:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IARV64 - why ABEND rather than return with reason code? I don't know, but I think I can make an educated guess: because that's a program[mer] error, not a system condition. Beyond that, I suppose it goes back to their design philosophy. I have to admit that makes sense to me. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
