If you have the IPCS ISPF application in place, and you know the name of your DAE dataset
Get into IPCS Go to Option 3 Utility Go to Option 5 DAE (verify the correct DAE dataset is listed Next to ANY Entry you can have DAE take a new dump Enter a / next to the entry of your dreams. It will provide a pop up that includes T to take the next dump Lizette -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Knutson, Samuel Sent: Tuesday, November 10, 2020 2:25 PM To: [email protected] Subject: Re: DAE to stop dump suppression Here is my simple "big hammer" to clear DAE from the z/OS console which can be very handy to do especially when things are not going well and dumps are not be captured that are now greatly desired. You can use more surgical tools in ISPF to take the next dump for a particular set so symptoms but this approach just emptying the DAE data set is simple. This particular example uses CA-OPS/MVS but you can substitute a free or another vendor program to issue a z/OS command passed in a parameter. Also adjust the name of your DAE data set as needed I have unique names on each LPAR in a Sysplex. DAE is generally a very good thing and having it on is desirable as it protects us from SVC dump flooding and avoids collecting the same dumps over and over again. Sometimes though you want to clear it all out in a hurry and just get on with getting the dump needed to get doc for a vendor or IBM. Once you setup the PROC and define to security you can just do a S DAECLEAR from a console. SYS1.PROCLIB(DAECLEAR) - 01.02 Columns 000 ===> Scroll = ********************************* Top of Data ************************* //DAECLEAR PROC SID=&SYSNAME //* // COMMAND 'T DAE=01' //* //* EMPTY DAE DATA SET TO STOP UNWANTED DUMP SUPPRESSION AND //* START OVER. YOU CAN SELECTIVELY USE IPCS TO REQUEST THE //* NEXT DUMP BE TAKEN FOR A GIVEN ABEND BUT THIS IS FREQUENTLY //* FASTER //* //* BEFORE YOU CAN RUN THE GENR STEP YOU NEED TO //* SET DAE=01 WHICH STOPS DAE //* THIS IS DONE AUTOMAGICALLY BY THE COMMAND EMBEDDED IN JCL ABOVE //* //* ADYUPDAT CLEANUP XXX IS AN EDIT MACRO THAT CAN DO SELECTIVE CLEANUP //* OR S DAECLEAR WHICH CLEARS DAE //* //* AFTERWARDS YOU NEED TO RESTART DAE PROCESSING //* SET DAE=00 WHICH STARTS DAE //* THIS IS DONE BY THE CA-OPSMVS TSO OPSCMD BELOW. WE CANNOT USE //* ANOTHER JCL COMMAND BECAUSE THEY ALL GET EXECUTED IMMEDIATELY //* AND THIS NEEDS TO WAIT TILL AFTER THE GENR STEP //* //GENR EXEC PGM=IEBGENER //SYSIN DD DUMMY //SYSPRINT DD SYSOUT=* //SYSUT1 DD DUMMY,DCB=SYS1.&SID..DAE //SYSUT2 DD DISP=OLD,DSN=SYS1.&SID..DAE //* //OPSCMD EXEC PGM=IKJEFT01,PARM='OC C(T DAE=00)' //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DUMMY Thanks, Sam -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Bill Giannelli Sent: Tuesday, November 10, 2020 5:22 AM To: [email protected] Subject: DAE to stop dump suppression I have a dump that is being suppressed by DAE. I am not experienced with IPCS and DAE. How do I find out what dataset is being used by DAE and how do I "remove" the dump in order to get the dump? I hope that makes sense. thanks Bill The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it ---------------------------------------------------------------------- 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
