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.&SYSNAME..&JOBNAME..D&LYYMMDD..T&LHHMMSS..S&SEQ. 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 00000090 IEA794I SVC DUMP HAS CAPTURED: 837 837 00000090 DUMPID=734 REQUESTED BY JOB (MANDB53M) 837 00000090 DUMP TITLE=TMDB443A SDUMP 21131 04:41:28.64 00000290 IEF196I IGD17070I DATA SET SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 21131 04:41:28.64 00000290 IEF196I ALLOCATED SUCCESSFULLY WITH 1 STRIP(S) 21131 04:41:28.64 00000290 IEF196I IGD17160I DATA SET SDUMP.SYSC.MANDB53M.D101023.T110503.S00736 21131 04:41:28.64 00000290 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&search=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
