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&[email protected] ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, May 11th, 2021 at 11:24 AM, Jim Mulder <[email protected]> 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" [email protected] wrote on > > 05/11/2021 10:24:44 AM: > > > From: "Mark Jacobs" [email protected] > > > > To: [email protected] > > > > Date: 05/11/2021 11:22 AM > > > > Subject: Dynamically allocated dump dataset, wrong date/time in DSN > > > > Sent by: "IBM Mainframe Discussion List" [email protected] > > > > 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 > > -- > > 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
