We are SHARED DAE in our plex too, but I suspect it would be the same in a 
non-shared configuration, but just on the one system.  When I use IPCS option 
3.5 to modify an entry to Take the next dump, it appears that IPCS is issuing a 
SETDAE=01, which stops DAE, and then turns around and issues a SET DAE=00 to 
all systems in the plex.   ADYSET00 in parmlib has the start parameters, and 
ADYSET01 has the GLOBALSTOP command in it.   Since you manually shut DAE down, 
but then I assume you made your changes via IPCS, that it then restarted for 
you.   The TSU* address space in the snip below is my TSO session.  I didn’t 
cut/paste all of the log, as it routed the commands to all my systems in the 
plex.

NI0000000 TEC1     19261 07:52:34.47 TSU03158 00000290  SET DAE=01              
                                    
N 0000000 TEC1     19261 07:52:34.48          00000280  IEE252I MEMBER ADYSET01 
FOUND IN SYS1.PARMLIB               
N 0000000 TEC1     19261 07:52:34.48          00000281  IEF196I IGD104I 
SYS2.SYSPLEX.DAE                            
N 0000000 TEC1     19261 07:52:34.48          00000281  IEF196I DDNAME=SYS00005 
                                    
MR4000000 TEC1     19261 07:52:34.48 INTERNAL 00000090  ADY015I DAE STOP 
PROCESSING IS COMPLETE 244                 
NI0000000 TEC1     19261 07:52:36.61 TSU03158 00000290  ROUTE DEV1,SET DAE=00   
                                    
N 0000000 TEC1     19261 07:52:36.83          00000281  IEF196I IGD103I SMS 
ALLOCATED TO DDNAME SYS00006            
MR4000000 TEC1     19261 07:52:36.84 INTERNAL 00000090  ADY012I THE FOLLOWING 
DAE OPTIONS ARE IN EFFECT: 247        
DR                                        247 00000090     START                
                                    
DR                                        247 00000090     SVCDUMP  = 
NOTIFY(3,30)  MATCH  UPDATE  SUPPRESSALL      
DR                                        247 00000090     SYSMDUMP = MATCH  
UPDATE                                 
DR                                        247 00000090     RECORDS  = 400       
                                    
DR                                        247 00000090     DSN      = 
SYS2.SYSPLEX.DAE                              
DR                                        247 00000090     SHARE    = DSN  
OPTIONS                                  
ER                                        247 00000090     GLOBAL   = DSN  
OPTIONS                                  

_____________________________________________________________________________________________________
Dave Jousma
AVP | Manager, Systems 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 <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Mark Jacobs
Sent: Wednesday, September 18, 2019 7:15 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DAE Mystery

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

Where would I look in the WLM ISPF application to check that?


Mark Jacobs


Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, September 17, 2019 4:38 PM, Mike Schwab <mike.a.sch...@gmail.com> 
wrote:

> Automatic restart in your WLM?
>
> On Tue, Sep 17, 2019, 13:48 Mark Jacobs < 
> 00000224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
>
> > I manually stopped DAE on all systems so someone could remove an 
> > entry from the shared DAE dataset. Shortly thereafter it started 
> > itself, and I can't figure out how or who/what did it.
> > 14:31:35.18 *ROUTEOD 00000290 T DAE=01
> > 00000290 IEE252I MEMBER ADYSET01 FOUND IN SYS1.DEVL.PARMLIB
> > 00000290 IEF196I IEF285I SYSP.DAESHARE
> > 00000290 IEF196I IEF285I VOL SER NOS= SYS023.
> > *ROUTEOD 00000090 ADY015I DAE STOP PROCESSING IS COMPLETE 794 .....
> > 14:33:20.77 INTERNAL 00000090 ADY012I THE FOLLOWING DAE OPTIONS ARE 
> > IN
> > EFFECT: 801
> > 801 00000090 START
> > 801 00000090 SVCDUMP = NOTIFY(3,30) MATCH UPDATE SUPPRESSALL
> > 801 00000090 SYSMDUMP = MATCH UPDATE
> > 801 00000090 RECORDS = 400
> > 801 00000090 DSN = SYSP.DAESHARE
> > 801 00000090 SHARE = DSN OPTIONS
> > 801 00000090 GLOBAL = DSN OPTIONS
> > Sent from ProtonMail, Swiss-based encrypted email.
> > GPG Public Key -
> > https://api.protonmail.ch/pks/lookup?op=get&search=markjacobs@proton
> > mail.com
> >
> > For IBM-MAIN subscribe / signoff / archive access instructions, send 
> > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
>
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to