The CDCTSTMP function returns the eight (8) byte storeclock (STCK) value from a changed data capture (CDC) record in a 26 byte human readable format. The value identifies the time (based on a 24 hour clock) that the update took place within a transaction or program. While the storeclock value is actually 8 bytes in length, the timestamp returns a value with microsecond precision, in effect loosing the last 12 bits of the 64 bit storeclock. The timestamp is in YYYY-MM-DD-HH.MM.SSSSSS format.
The CDCSTCK function returns the eight (8) byte storeclock (STCK) value from a changed data capture (CDC) record in a 16 byte displayable hexadecimal character format. The value identifies the time (based on a 24 hour clock) that the update took place within a transaction or program. A human readable version of the Storeclock can be retrieved using the CDCTSTMP Function.
Category
Change Data Capture
CDCTSTMP(<source_datastore>)| Parameter | Description |
|---|---|
| source_datastore | The name of the source datastore that contains the changed data capture (CDC) records. |
Example
SRC_TSTAMP = CDCTSTMP (CDCIN)2021-08-20-15:12:33.086193 - UTC2021-08-20-11:12:33.086193 - EDT- See STORECLOCK for more information including how to convert from and to the STCK value outside the product.
- Most zOS mainframe environments use UTC or Coordinated Universal Time (the abbreviation came about as a compromise between English and French speakers who preferred "Coordinated Universal Time - CUT" and "Temps Universel Coordonné - TUC". The International Astronomical Union wished to minimize confusion and designated the single abbreviation UTC for use in all languages. UTC does not favor any particular language and is consistent with the abbreviation for Universal Time, which is UT, with the variations UT0 and UT1. Connect CDC SQData cannot determine if UTC or a timezone was used when MVS was configured.
- This function replaces the IMSCDCTSTMP and DB2CDCTSTMP functions, although these functions are still supported in Connect CDC SQData V4.