Re: Dynamically allocated dump dataset, wrong date/time in DSN
And no doubt you are... but it seems odd that what appears to be a standard use of system symbols gets hijacked in a rather unintuitive and afaik undocumented way. And I wonder why anyone would think it useful. sas On Tue, May 11, 2021 at 3:46 PM Jim Mulder wrote: > " I endeavor to be accurate." > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Dynamically allocated dump dataset, wrong date/time in DSN
" I endeavor to be accurate." Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" wrote on 05/11/2021 02:24:08 PM: > From: "Mark Jacobs" <0224d287a4b1-dmarc-requ...@listserv.ua.edu> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 05/11/2021 03:43 PM > Subject: Re: Dynamically allocated dump dataset, wrong date/time in DSN > Sent by: "IBM Mainframe Discussion List" > > That's exactly where IBM support went to when they reviewed one of > the dumps I sent them. I passed the information to our developers > for their analysis. > > Mark Jacobs > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Dynamically allocated dump dataset, wrong date/time in DSN
That's exactly where IBM support went to when they reviewed one of the dumps I sent them. I passed the information to our developers for their analysis. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, May 11th, 2021 at 2:20 PM, Jim Mulder wrote: > That's a good question. The answer is that SDUMP uses the timestamp > > from the incident token. Per the SDUMP(X) documentation: > > ,INTOKEN=token addr > > Specifies the address of a 32-byte area that contains an incident > > token previously built by an IEAINTKN macro. If register notation > > is used, the register contains the address of the area. > > The system associates the token with the SVC dump on this > > system and with any SVC dumps requested by the REMOTE > > parameter on other sysplex systems. If the parameter is omitted, > > the system generates an incident token. > > So I would look at one of these dumps that has > > a bad timestamp to see if INTOKEN was specified in the > > SDUMP(X) parm list. IPCS STATUS WORKSHEET > > will format the SDUMP parameter list on recent releases. > > If INTOKEN was specified, then the caller of SDUMP(X) > > would need to be investigated. > > Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. > > Poughkeepsie NY > > "Seymour J Metz" sme...@gmu.edu wrote on 05/11/2021 01:57:15 PM: > > > From: "Seymour J Metz" sme...@gmu.edu > > > > To: ibm-main@listserv.ua.edu > > > > Date: 05/11/2021 02:14 PM > > > > Subject: Re: Dynamically allocated dump dataset, wrong date/time in DSN > > > Does SDUMP use the current time or the reader start time for the > > > > address space? > > > > -- > > > > Shmuel (Seymour J.) Metz > > > > http://mason.gmu.edu/smetz3 > > > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > > > > behalf of Mark Jacobs [0224d287a4b1-dmarc-requ...@listserv.ua.edu] > > > > Sent: Tuesday, May 11, 2021 12:45 PM > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > Subject: Re: Dynamically allocated dump dataset, wrong date/time in DSN > > > > Date and time are correct, the timestamp on the log shows it. Just > > > > the dataset name for the dump has the wrong date/time. > > > > Sent from ProtonMail, Swiss-based encrypted email. > > > > GPG Public Key - https://secure-web.cisco.com/148NvMITQjmpZkVkMl- > > _CeM4wfFpJwZE63w6yJOGE1njY5Mzq6rx228KRki-4j4TrtCTWWJd042V_9mxM92JZ1gcAgWtWB3eyehvwDOgIfF0ObWKXHhpaX5Aljo0JGCbA9ORuaxGJEutJDooDb4- > > > kRy-fQR- > > zRCkwvYF7S8ADIi7exMO0mruSU0dkmCYQ9Q275DPcF3ranE5goTs2QssaCfZAT0QIuRChPYSDAg2waIRUpZsfWoueIXQyPyROM5vKDkQvP1sMUdi3tInMEh3nthDCQ8ZPwlCjpgJHmZQ0rp4cjXW6BLAnmN8bih4X4lEataHNBM650g5P-3I7conYdS7bfM9sZLKPq219KCQ1zNYkCrE1Oeo7JsmUvaGT5cYI2PI2si1Z45m89SzWlaYaSw- > > > kOCAfSEDKPTdR7bVrQu0EObOyVHjKL1xR30E86aJQ/ > > https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com > > > ‐‐‐ Original Message ‐‐‐ > > > > On Tuesday, May 11th, 2021 at 12:28 PM, Lizette Koehler > > > > stars...@mindspring.com wrote: > > > > > I would check the system date D T > > > > > > Is GMT and Local correct? > > > > > > Is something doing a T CLOCK command? > > > > > > Maybe add some automation when the dump is being taken to do a D T > > > > > > Lizette > > > > > > -Original Message- > > > > > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On > > > > > > Behalf Of Mark Jacobs > > > > > > Sent: Tuesday, May 11, 2021 7:25 AM > > > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > > > Subject: Dynamically allocated dump dataset, wrong date/time in DSN > > > > > > Our DUMPDS name pattern is set to this, DD > > > > > > NAME=SDUMP. Most of > > > > > > the time dump datasets are allocated with the right date/timestamps, > > > > > > but every so often (or so I've been told) we get something like this; > > > > > > 21131 04:41:28.58 S0382268 0090 IEA794I SVC DUMP HAS CAPTURED: 837 > > > > > > 837 0090 DUMPID=734 REQUESTED BY JOB (MANDB53M) > > > > > > 837 0090 DUMP TITLE=TMDB443A SDUMP > &g
Re: Dynamically allocated dump dataset, wrong date/time in DSN
That's a good question. The answer is that SDUMP uses the timestamp from the incident token. Per the SDUMP(X) documentation: ,INTOKEN=token addr Specifies the address of a 32-byte area that contains an incident token previously built by an IEAINTKN macro. If register notation is used, the register contains the address of the area. The system associates the token with the SVC dump on this system and with any SVC dumps requested by the REMOTE parameter on other sysplex systems. If the parameter is omitted, the system generates an incident token. So I would look at one of these dumps that has a bad timestamp to see if INTOKEN was specified in the SDUMP(X) parm list. IPCS STATUS WORKSHEET will format the SDUMP parameter list on recent releases. If INTOKEN was specified, then the caller of SDUMP(X) would need to be investigated. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "Seymour J Metz" wrote on 05/11/2021 01:57:15 PM: > From: "Seymour J Metz" > To: ibm-main@listserv.ua.edu > Date: 05/11/2021 02:14 PM > Subject: Re: Dynamically allocated dump dataset, wrong date/time in DSN > > Does SDUMP use the current time or the reader start time for the > address space? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/smetz3 > > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > behalf of Mark Jacobs [0224d287a4b1-dmarc-requ...@listserv.ua.edu] > Sent: Tuesday, May 11, 2021 12:45 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Dynamically allocated dump dataset, wrong date/time in DSN > > Date and time are correct, the timestamp on the log shows it. Just > the dataset name for the dump has the wrong date/time. > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - https://secure-web.cisco.com/148NvMITQjmpZkVkMl- > _CeM4wfFpJwZE63w6yJOGE1njY5Mzq6rx228KRki-4j4TrtCTWWJd042V_9mxM92JZ1gcAgWtWB3eyehvwDOgIfF0ObWKXHhpaX5Aljo0JGCbA9ORuaxGJEutJDooDb4- > kRy-fQR- > zRCkwvYF7S8ADIi7exMO0mruSU0dkmCYQ9Q275DPcF3ranE5goTs2QssaCfZAT0QIuRChPYSDAg2waIRUpZsfWoueIXQyPyROM5vKDkQvP1sMUdi3tInMEh3nthDCQ8ZPwlCjpgJHmZQ0rp4cjXW6BLAnmN8bih4X4lEataHNBM650g5P-3I7conYdS7bfM9sZLKPq219KCQ1zNYkCrE1Oeo7JsmUvaGT5cYI2PI2si1Z45m89SzWlaYaSw- > kOCAfSEDKPTdR7bVrQu0EObOyVHjKL1xR30E86aJQ/ > https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com > > ‐‐‐ Original Message ‐‐‐ > > On Tuesday, May 11th, 2021 at 12:28 PM, Lizette Koehler > wrote: > > > I would check the system date D T > > > > Is GMT and Local correct? > > > > Is something doing a T CLOCK command? > > > > Maybe add some automation when the dump is being taken to do a D T > > > > Lizette > > > > -Original Message- > > > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On > Behalf Of Mark Jacobs > > > > Sent: Tuesday, May 11, 2021 7:25 AM > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > Subject: Dynamically allocated dump dataset, wrong date/time in DSN > > > > Our DUMPDS name pattern is set to this, DD > NAME=SDUMP. Most of > the time dump datasets are allocated with the right date/timestamps, > but every so often (or so I've been told) we get something like this; > > > > 21131 04:41:28.58 S0382268 0090 IEA794I SVC DUMP HAS CAPTURED: 837 > > > > 837 0090 DUMPID=734 REQUESTED BY JOB (MANDB53M) > > > > 837 0090 DUMP TITLE=TMDB443A SDUMP > > > > 21131 04:41:28.64 0290 IEF196I IGD17070I DATA SET > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > > > > 21131 04:41:28.64 0290 IEF196I ALLOCATED SUCCESSFULLY WITH 1 STRIP(S) > > > > 21131 04:41:28.64 0290 IEF196I IGD17160I DATA SET > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > > > > 21131 04:41:28.64 0290 IEF196I IS ELIGIBLE FOR COMPRESSION > > > > Any ideas? > > > > Mark Jacobs > > > > Sent from ProtonMail, Swiss-based encrypted email. > > > > GPG Public Key - https://secure-web.cisco.com/148NvMITQjmpZkVkMl- > _CeM4wfFpJwZE63w6yJOGE1njY5Mzq6rx228KRki-4j4TrtCTWWJd042V_9mxM92JZ1gcAgWtWB3eyehvwDOgIfF0ObWKXHhpaX5Aljo0JGCbA9ORuaxGJEutJDooDb4- &
Re: Dynamically allocated dump dataset, wrong date/time in DSN
Does SDUMP use the current time or the reader start time for the address space? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Mark Jacobs [0224d287a4b1-dmarc-requ...@listserv.ua.edu] Sent: Tuesday, May 11, 2021 12:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dynamically allocated dump dataset, wrong date/time in DSN Date and time are correct, the timestamp on the log shows it. Just the dataset name for the dump has the wrong date/time. Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://secure-web.cisco.com/148NvMITQjmpZkVkMl-_CeM4wfFpJwZE63w6yJOGE1njY5Mzq6rx228KRki-4j4TrtCTWWJd042V_9mxM92JZ1gcAgWtWB3eyehvwDOgIfF0ObWKXHhpaX5Aljo0JGCbA9ORuaxGJEutJDooDb4-kRy-fQR-zRCkwvYF7S8ADIi7exMO0mruSU0dkmCYQ9Q275DPcF3ranE5goTs2QssaCfZAT0QIuRChPYSDAg2waIRUpZsfWoueIXQyPyROM5vKDkQvP1sMUdi3tInMEh3nthDCQ8ZPwlCjpgJHmZQ0rp4cjXW6BLAnmN8bih4X4lEataHNBM650g5P-3I7conYdS7bfM9sZLKPq219KCQ1zNYkCrE1Oeo7JsmUvaGT5cYI2PI2si1Z45m89SzWlaYaSw-kOCAfSEDKPTdR7bVrQu0EObOyVHjKL1xR30E86aJQ/https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, May 11th, 2021 at 12:28 PM, Lizette Koehler wrote: > I would check the system date D T > > Is GMT and Local correct? > > Is something doing a T CLOCK command? > > Maybe add some automation when the dump is being taken to do a D T > > Lizette > > -Original Message- > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Mark Jacobs > > Sent: Tuesday, May 11, 2021 7:25 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Dynamically allocated dump dataset, wrong date/time in DSN > > Our DUMPDS name pattern is set to this, DD > NAME=SDUMP. Most of the time > dump datasets are allocated with the right date/timestamps, but every so > often (or so I've been told) we get something like this; > > 21131 04:41:28.58 S0382268 0090 IEA794I SVC DUMP HAS CAPTURED: 837 > > 837 0090 DUMPID=734 REQUESTED BY JOB (MANDB53M) > > 837 0090 DUMP TITLE=TMDB443A SDUMP > > 21131 04:41:28.64 0290 IEF196I IGD17070I DATA SET > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > > 21131 04:41:28.64 0290 IEF196I ALLOCATED SUCCESSFULLY WITH 1 STRIP(S) > > 21131 04:41:28.64 0290 IEF196I IGD17160I DATA SET > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > > 21131 04:41:28.64 0290 IEF196I IS ELIGIBLE FOR COMPRESSION > > Any ideas? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://secure-web.cisco.com/148NvMITQjmpZkVkMl-_CeM4wfFpJwZE63w6yJOGE1njY5Mzq6rx228KRki-4j4TrtCTWWJd042V_9mxM92JZ1gcAgWtWB3eyehvwDOgIfF0ObWKXHhpaX5Aljo0JGCbA9ORuaxGJEutJDooDb4-kRy-fQR-zRCkwvYF7S8ADIi7exMO0mruSU0dkmCYQ9Q275DPcF3ranE5goTs2QssaCfZAT0QIuRChPYSDAg2waIRUpZsfWoueIXQyPyROM5vKDkQvP1sMUdi3tInMEh3nthDCQ8ZPwlCjpgJHmZQ0rp4cjXW6BLAnmN8bih4X4lEataHNBM650g5P-3I7conYdS7bfM9sZLKPq219KCQ1zNYkCrE1Oeo7JsmUvaGT5cYI2PI2si1Z45m89SzWlaYaSw-kOCAfSEDKPTdR7bVrQu0EObOyVHjKL1xR30E86aJQ/https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.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 / a
Re: Dynamically allocated dump dataset, wrong date/time in DSN
I don't think we have any products like that, but I've asked my team. We're a software development organization, so I think it's unlikely we'd need it. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, May 11th, 2021 at 1:25 PM, Dave Jousma <01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > > Date and time are correct, the timestamp on the log shows it. Just the > > dataset name for the dump has the wrong date/time. > > Mark, > > Is it possible that they could be running some tool like HourGlass fooling > around with date/time? > > --- > > 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
Re: Dynamically allocated dump dataset, wrong date/time in DSN
>Date and time are correct, the timestamp on the log shows it. Just the dataset >name for the dump has the wrong date/time. Mark, Is it possible that they could be running some tool like HourGlass fooling around with date/time? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Dynamically allocated dump dataset, wrong date/time in DSN
Date and time are correct, the timestamp on the log shows it. Just the dataset name for the dump has the wrong date/time. Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, May 11th, 2021 at 12:28 PM, Lizette Koehler wrote: > I would check the system date D T > > Is GMT and Local correct? > > Is something doing a T CLOCK command? > > Maybe add some automation when the dump is being taken to do a D T > > Lizette > > -Original Message- > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Mark Jacobs > > Sent: Tuesday, May 11, 2021 7:25 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Dynamically allocated dump dataset, wrong date/time in DSN > > Our DUMPDS name pattern is set to this, DD > NAME=SDUMP. Most of the time > dump datasets are allocated with the right date/timestamps, but every so > often (or so I've been told) we get something like this; > > 21131 04:41:28.58 S0382268 0090 IEA794I SVC DUMP HAS CAPTURED: 837 > > 837 0090 DUMPID=734 REQUESTED BY JOB (MANDB53M) > > 837 0090 DUMP TITLE=TMDB443A SDUMP > > 21131 04:41:28.64 0290 IEF196I IGD17070I DATA SET > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > > 21131 04:41:28.64 0290 IEF196I ALLOCATED SUCCESSFULLY WITH 1 STRIP(S) > > 21131 04:41:28.64 0290 IEF196I IGD17160I DATA SET > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > > 21131 04:41:28.64 0290 IEF196I IS ELIGIBLE FOR COMPRESSION > > Any ideas? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.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
Re: Dynamically allocated dump dataset, wrong date/time in DSN
I would check the system date D T Is GMT and Local correct? Is something doing a T CLOCK command? Maybe add some automation when the dump is being taken to do a D T Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Tuesday, May 11, 2021 7:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Dynamically allocated dump dataset, wrong date/time in DSN Our DUMPDS name pattern is set to this, DD NAME=SDUMP. Most of the time dump datasets are allocated with the right date/timestamps, but every so often (or so I've been told) we get something like this; 21131 04:41:28.58 S0382268 0090 IEA794I SVC DUMP HAS CAPTURED: 837 837 0090 DUMPID=734 REQUESTED BY JOB (MANDB53M) 837 0090 DUMP TITLE=TMDB443A SDUMP 21131 04:41:28.64 0290 IEF196I IGD17070I DATA SET SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 21131 04:41:28.64 0290 IEF196I ALLOCATED SUCCESSFULLY WITH 1 STRIP(S) 21131 04:41:28.64 0290 IEF196I IGD17160I DATA SET SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 21131 04:41:28.64 0290 IEF196I IS ELIGIBLE FOR COMPRESSION Any ideas? Mark Jacobs Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.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
Re: Dynamically allocated dump dataset, wrong date/time in DSN
Not that I'm aware of. I'll ask around. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, May 11th, 2021 at 11:24 AM, Jim Mulder wrote: > Does your system have a a clock simulation > > program like IBM Hourglass installed? > > Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. > > Poughkeepsie NY > > "IBM Mainframe Discussion List" IBM-MAIN@LISTSERV.UA.EDU wrote on > > 05/11/2021 10:24:44 AM: > > > From: "Mark Jacobs" 0224d287a4b1-dmarc-requ...@listserv.ua.edu > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > Date: 05/11/2021 11:22 AM > > > > Subject: Dynamically allocated dump dataset, wrong date/time in DSN > > > > Sent by: "IBM Mainframe Discussion List" IBM-MAIN@LISTSERV.UA.EDU > > > > Our DUMPDS name pattern is set to this, DD > > > > NAME=SDUMP. Most of > > > > the time dump datasets are allocated with the right date/timestamps, > > > > but every so often (or so I've been told) we get something like this; > > > > 21131 04:41:28.58 S0382268 0090 IEA794I SVC DUMP HAS CAPTURED: 837 > > > > 837 0090 DUMPID=734 REQUESTED BY JOB (MANDB53M) > > > > 837 0090 DUMP TITLE=TMDB443A SDUMP > > > > 21131 04:41:28.64 0290 IEF196I IGD17070I DATA SET > > > > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > > > > 21131 04:41:28.64 0290 IEF196I ALLOCATED SUCCESSFULLY WITH 1 > > STRIP(S) > > > 21131 04:41:28.64 0290 IEF196I IGD17160I DATA SET > > > > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > > > > 21131 04:41:28.64 0290 IEF196I IS ELIGIBLE FOR COMPRESSION > > > > Any ideas? > > > > Mark Jacobs > > -- > > 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
Re: Dynamically allocated dump dataset, wrong date/time in DSN
Does your system have a a clock simulation program like IBM Hourglass installed? Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" wrote on 05/11/2021 10:24:44 AM: > From: "Mark Jacobs" <0224d287a4b1-dmarc-requ...@listserv.ua.edu> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 05/11/2021 11:22 AM > Subject: Dynamically allocated dump dataset, wrong date/time in DSN > Sent by: "IBM Mainframe Discussion List" > > Our DUMPDS name pattern is set to this, DD > NAME=SDUMP. Most of > the time dump datasets are allocated with the right date/timestamps, > but every so often (or so I've been told) we get something like this; > > 21131 04:41:28.58 S0382268 0090 IEA794I SVC DUMP HAS CAPTURED: 837 > 837 0090 DUMPID=734 REQUESTED BY JOB (MANDB53M) > 837 0090 DUMP TITLE=TMDB443A SDUMP > > 21131 04:41:28.64 0290 IEF196I IGD17070I DATA SET > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > 21131 04:41:28.64 0290 IEF196I ALLOCATED SUCCESSFULLY WITH 1 STRIP(S) > 21131 04:41:28.64 0290 IEF196I IGD17160I DATA SET > SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 > 21131 04:41:28.64 0290 IEF196I IS ELIGIBLE FOR COMPRESSION > > Any ideas? > > Mark Jacobs -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Dynamically allocated dump dataset, wrong date/time in DSN
Our DUMPDS name pattern is set to this, DD NAME=SDUMP. Most of the time dump datasets are allocated with the right date/timestamps, but every so often (or so I've been told) we get something like this; 21131 04:41:28.58 S0382268 0090 IEA794I SVC DUMP HAS CAPTURED: 837 837 0090 DUMPID=734 REQUESTED BY JOB (MANDB53M) 837 0090 DUMP TITLE=TMDB443A SDUMP 21131 04:41:28.64 0290 IEF196I IGD17070I DATA SET SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 21131 04:41:28.64 0290 IEF196I ALLOCATED SUCCESSFULLY WITH 1 STRIP(S) 21131 04:41:28.64 0290 IEF196I IGD17160I DATA SET SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 21131 04:41:28.64 0290 IEF196I IS ELIGIBLE FOR COMPRESSION Any ideas? Mark Jacobs Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
