On Tue, 6 Oct 2020 09:31:26 -0700, Lizette Koehler <stars...@mindspring.com> wrote:
>If you fix the issue, and the DAE entry is still in place, you might not see >if there is an issue. > >So as always, it depends. > >By removing the entry in DAE it might show if you actually fixed it > >Lizette > > >-----Original Message----- >From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of >Jousma, David >Sent: Tuesday, October 6, 2020 9:12 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: DAE Dataset - Compression > >I guess I don’t agree with that Lizette? I mean we can agree to disagree, >there are many ways to run our environments, but clearing out DAE will just >retrigger DUMPs for repetitive issues all over again? It may be old >technology, but it works! 1400+ unique entries in our 20% utilized dae >allocated at 45 trks. Usually it’s the DB2 sysprogs that come to me to >re-enable a certain dump that’s being suppressed. > >Now, clearing out the sysplex dump directory regularly is something I agree >with. > >--------------------------------- DAE Display --------------------------------- > Row 1 to 14 of 1,437 >Command ===> Scroll ===> CSR > Enter an Action Code next to an entry. > Enter / next to an entry to choose from a list of Action Codes. > > Dataset: 'SYS2.SYSPLEX.DAE' > Dumps since last DAE Display: 215 Total Dumps suppressed: 163672 > Events since last DAE Display: 110606 Suppression rate: 94% > Have a look in "hlq.SBLSCLI0(ADYUPDAT)" and you can possibly use that to manage DAE as one of the options is CLEANUP and with that you can specify that entries older than so many days are deleted - no need to compress DAE. Roger ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
