>Three main reasons to have recovery come to mind >-- to release resources that you have obtained >-- to gather diagnostic data to help debug your error >-- to protect your caller from unexpectedly getting control in its >recovery
A fourth, of course: for protecting the system against bad user input while avoiding time of check to time of use exposures. For example, referencing user storage in user key, expecting to handle any 'blowing up' in your recovery. By the way, do not expect that the system will capture diagnostic data (such as via SDUMP) for an error in your code (such as an error in an exit routine). It might do so, but generally will not (and should not). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
