Re: DAE Dataset - Compression

2020-10-06 Thread Roger Lowe
zette > > >-Original Message- >From: IBM Mainframe Discussion List 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 c

Re: DAE Dataset - Compression

2020-10-06 Thread Lizette Koehler
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

Re: DAE Dataset - Compression

2020-10-06 Thread Jousma, David
653.8429  |  fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lizette Koehler Sent: Tuesday, October 6, 2020 12:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DAE Dataset - Compression **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on li

Re: DAE Dataset - Compression

2020-10-06 Thread Lizette Koehler
Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Tuesday, October 6, 2020 7:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DAE Dataset - Compression Before I open up a ticket with IBM I wanted to ask if the DAE dataset can be allocated as

Re: DAE Dataset - Compression

2020-10-06 Thread Jim Mulder
Discussion List" wrote on 10/06/2020 10:11:28 AM: > From: "Tom Conley" > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 10/06/2020 11:49 AM > Subject: Re: DAE Dataset - Compression > Sent by: "IBM Mainframe Discussion List" > > On 10/6/2020 10:06 AM, Mark Jacob

Re: DAE Dataset - Compression

2020-10-06 Thread Mark Jacobs
CB2H  |  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: Tuesday, October 6, 2020 10:33 AM > > To: IBM-MAIN@LISTSERV.UA.EDU

Re: DAE Dataset - Compression

2020-10-06 Thread Jousma, David
  |  MD RSCB2H  |  Grand Rapids, MI 49546 616.653.8429  |  fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Tuesday, October 6, 2020 10:33 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DAE Dataset - Compression **CAUTION EXTERNAL EMAIL

Re: DAE Dataset - Compression

2020-10-06 Thread Mark Jacobs
cussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Mark Jacobs > > Sent: Tuesday, October 6, 2020 10:18 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: DAE Dataset - Compression > > CAUTION EXTERNAL EMAIL > > DO NOT open attachments or click on links from unknown

Re: DAE Dataset - Compression

2020-10-06 Thread Jousma, David
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 On Behalf Of Mark Jacobs Sent: Tuesday, October 6, 2020 10:18 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DAE Dataset - Compre

Re: DAE Dataset - Compression

2020-10-06 Thread Mark Jacobs
I issued a T DAE=01 to stop it across the sysplex, renamed the DAE datasets and then restarted DAE, T DAE=00. 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 ‐

Re: DAE Dataset - Compression

2020-10-06 Thread Tom Conley
On 10/6/2020 10:06 AM, Mark Jacobs wrote: 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;

DAE Dataset - Compression

2020-10-06 Thread Mark Jacobs
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