[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference movies::decdtm-vms

Title:DECDTM-VMS
Notice:DECdtm Conference. 260.* for docs & kits. Digital Confidential
Moderator:MOVIES::PLAYFORD
Created:Fri Aug 12 1988
Last Modified:Fri May 30 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:353
Total number of notes:1278

350.0. ""INCORRECT DATE/TIME IN DTM JOURNAL FILE"" by DEKVC::JUNGYULBAEK () Thu Mar 13 1997 08:34

I am trying to analize dump of dtm journal file as follows.
 
$ MCR LMCP
 LMCP>dump /active
      -file: system$hse
  
 dump of transaction log DSA35:[DTM$JNL]SYSTEM$HSE.LM$JOURNAL;1
 End of file block 30000 / allocated 30000
                .
                .
 Transaction state (2):COMMITTED
 Transaction ID: 040F4DFE-BO4C-4CA6-0100-000052545224 (24-JUL-4471 22:51:52.12)
 DECdtm Service log format V1.1                        =======================
 
 But ,as you see,the date and time is incorrect.
 I dont know why?
 
 Thanks for your reply
 
 ---------------------------------------------------
 VMS version : alpha vms V6.2-1H3 with alpddtm03_070
 Two alpha8200 system with CI cluster.                  
 ---------------------------------------------------
 regards
 BAEK.
T.RTitleUserPersonal
Name		DateLines
350.1halt::POTTERhttp://www.vmse.edo.dec.com/~potter/Thu Mar 13 1997 09:038
These are transaction IDs generated by RTR.  They are not UIDs, and hence do
not have the date/time of creation embedded in them in the same way as real 
UIDs do.  Hence the date/time part of the TID is nonsense, as you saw.

If the client is who I think it is, they already know this!

regards,
//alan
350.2"incorrect date/time"DEKVC::JUNGYULBAEKFri Mar 14 1997 09:1514
    Hi, alan
    Thanks for your reply.
    But I dont understand that "date/time part of the TID is nensense"and
    what UID is.
    
    Transaction log gernerated by RDB is ok,but log gernerated by rtr is
     incorrect.
    why?
    
    regards
    //baek
350.3MOVIES::MJOHNSONMike Johnson - VMS EuropeFri Mar 14 1997 14:2619
What Alan means is that the UID (unique identifier) that DECdtm uses
for it's TID (transaction identifier) has the date at the time of
creation of the UID encoded within it. LMCP uses this knowledge to
decode the date information and display it. 

Of course, this only works for UID's derived from the generation
method used by DECdtm which I believe is the same as that used by the
SYS$CREATE_UID system service and is governed by some sort or ANSI/TPC
standard (it's been some time since I worked on DECdtm). I guess that
Rdb either uses the system service or at least the same method but
that RTR uses something different. Hence when LMCP tries to decode the
time in a TID generated by RTR, it is unable to make any sense of it
and you get to see some really odd 'dates'.

I hope that help explain things a little.

Mike