On Mon, 13 Feb 2012 09:05:03 -0500 John Gilmore <johnwgilmore0...@gmail.com> wrote:
:>We have of course been here before. :>The idea that a desired USER ABEND is best achieved by triggering a :>SYSTEM ABEND that will be minimally confusing, highly unlikely to be :>confused with the corresponding real SYSTEM ABEND, does not seem to :>want to die. Because it is quite useful. :>Why try to trick the system into issuing an ABEND when you can do it yourself? :>USER ABENDS are immediately available by coding an ABEND macro :>instruction. They specify a [USER] completion code; and they may, :>optionally but desirably, specify a fullword user code too. All of which alter the CC, and R15-R1. User abends are quite useful for known issues - missing DD statement, missing module, insufficient authority, etc.. But if the code gets a completely unexpected result there is a need to figure out how to save the environment before issuing the abend so that the problem can be diagnosed. But where and how should this be saved? :>This whole discussion of the relative merits of these triggering :>mechanisms is thus otiose at best. The only gotcha that can arise in :>connection with such an ABEND macro instruction is that one issued in :>AR mode must be preceded by a :>| SYSTATE ASCENV=AR :>macro instruction, but surely those of you who are writing AR-mode :>code can cope with this difficulty; and those of you who cannot should :>not be doing it. Not all issues can be placed into one box. The programmer should have a big enough imagination to consider other options. -- Binyamin Dissen <bdis...@dissensoftware.com> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies.
