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 [00000224d287a4b1-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.&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, 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 / 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
