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%
_____________________________________________________________________________________________________
Dave Jousma
AVP | Director, Technology Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Lizette Koehler
Sent: Tuesday, October 6, 2020 12:04 PM
To: [email protected]
Subject: Re: DAE Dataset - Compression
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
I have not read this whole thread, so I apologize if I cover the same ground
DAE dataset is very old technology. It is a sequential file and I am not sure
you can make it compressed. That could be an RFS
Second - shutting down DAE like you did - is the correct process
There is no reason to keep everything in DAE unless you want to
Every time we put in a new z/OS OS. I clear out completely the DAE dataset.
Depending on how active your system is for abends, you might just want to make
it bigger.
You might need to put a process in place to clear it out weekly or daily or
other
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Mark Jacobs
Sent: Tuesday, October 6, 2020 7:06 AM
To: [email protected]
Subject: DAE Dataset - Compression
Before I open up a ticket with IBM I wanted to ask if the DAE dataset can be
allocated as compressed? I tried to migrate our shared DAE dataset to a newly
allocated one that with compression enabled. It didn't go well. One SVCDUMP we
received was this; COMPID=SC143,ISSUER=ADYTRNS FAILURE IN THE TRANSACTION
PROCESSOR FOR DAE
Mark Jacobs
Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.
GPG Public Key -
https://protect2.fireeye.com/url?k=966eb008-ca324407-966e9a90-0cc47a33347c-21744e3782d3f911&u=https://api.protonmail.ch/pks/lookup?op=get&[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL
EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
