Many Thanks Wayne, We send them the corresponding request. But I really think this is not the issue. STCK to LRSN Delta is usually defined as no more than a number of seconds, and we are dealing with years...Moreover, as well as I understand some (described below) inputs, this is not a clock at all. I compared the different between some DB2 events (INSERT operation to a table with TIMESTAMP column setting to CURREMT_TIMESTAMP) and between LRSN in these events. The different in the column was 2.8 seconds when in LRSN - 1.5 second...
On Wed, Aug 20, 2014 at 9:24 PM, Wayne Driscoll <[email protected]> wrote: > You will want to check in the BSDS of the DB2 data sharing group (using > offline utility DSNJU004) to determine if there is a STCK to LRSN Delta > defined for the data sharing group. This delta is required when a DB2 > subsystem is converted to data sharing with a (then) current log RBA that > was greater then the high order 6 bytes of the STCK value. If this value > is non-zero, it will need to be subtracted from the LRSN value prior to > converting it to a timestamp field. > ============================================== > Wayne Driscoll > OMEGAMON DB2 L3 Support/Development > wdrisco(at)us(dot)ibm(dot)com > All opinions are mine, and do not represent > IBM Corporation. > ============================================== > > IBM Mainframe Discussion List <[email protected]> wrote on > 08/18/2014 09:34:06 AM: > > > From: Arie Kremer <[email protected]> > > To: [email protected] > > Date: 08/18/2014 09:34 AM > > Subject: [IBM-MAIN] Strange LRSN value in DB2 Log Records > > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > We use IFI to analyze DB2 logs. "lrh_time" field in the log record header > > is assumed to contain LRSN in SYSPLEX environment, when LRSN is usually > > derived from the Coupling Facility clock, i.e. may be be used as a clock. > > In most cases, this works perfect. > > We have a customer that their Coupling Facility clock and the clock of > > other processors are different (5 hours). In their DB2 environment, we > get > > LRSN that being converting to the timestamp means the year 2038, and > seems > > as not a clock. The values are acceding, and seems as the problem is only > > when interpreting LRSN as a timestamp. > > Does somebody know what does it mean? What is this LRSN means and how to > > convert it to the real time? > > > > Many thanks > > Arie Kremer > > > > ---------------------------------------------------------------------- > > 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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
