>Did I mention scheduled dumps cannot be suppressed via slip? And apparently >*someone* made the decision to *schedule* dumps again (this is new in z/OS >1.10, 1.8 didn't have this, and we always had TSO/Xpediter users who are >prone to this 878.) >Did I mention that DAE is useless in this regard (too many dump requests >before the first one has its symptom string written?)
SLIP should be able to suppress any dump for which the SDUMP macro was issued within an ESTAE(X), ARR, or FRR routine, regardless of whether the dump is asynchronous (scheduled) with respect to the SDUMP issuer, or synchronous. Now, if you have some doofus recovery routine that does a retry and then issues SDUMP (and I have seen some of those), then SLIP cannot suppress it because there is no longer any time of error context for SLIP to match against. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
