See the ESTAE, ESTAEX, and SETRP macros in the System Services books for more info, but here is the operative part:
If you specify RECORD=YES, the system records the entire SDWA (including the fixed length base, the variable length recording area, and the recordable extensions) in SYS1.LOGREC when the associated ESTAE recovery routine returns control, unless the recovery routine indicates otherwise by issuing the SETRP macro with RECORD=NO. If you specify RECORD=NO, the system does not record the SDWA in SYS1.LOGREC, unless the recovery routine indicates otherwise by issuing the SETRP macro with RECORD=YES. No matter how careful we are, there will always be the possibility that some code will go into an infinite loop using up some finite resource, such as ejecting paper on a printer (I've done this myself), writing SVC dumps (done this too), writing software records into SYS1.LOGREC (which is where EREP gets the info it prints on ABENDs), writing hardware records into SYS1.LOGREC (used to happen with hot I/O interrupts), writing SMF records, needing more DASD extents or tape volumes when writing an output file, requesting more CSA/SQA to build a system control block (SYNCH macro), etc. IBM made RECORD=NO the default and RECORD=YES an option for very good reasons. Bill Fairchild ----- Original Message ----- From: "Shane Ginnane" <[email protected]> To: [email protected] Sent: Wednesday, April 16, 2014 5:56:41 AM Subject: EREP: was: Dumps when starting Started Tasks I was more than a little surprised when talking to some of the system design/test people at Share in Boston to be disavowed of my notion that an abend always cuts an EREP entry. I have in the past used EREP to keep an eye on CICS developers who decide to inhibit dumps, and have always assumed I had a good tool for such. I would be *much* happier if I could rely on it to always have an entry for any abend. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
