Home > IT Answers > Storage > timestamp value
Pprasad123
0 pts.
 timestamp value
Backup & recovery, i5, iSeries, OS/400, tips and tricks, Tools
Hi, I am receiving TIMESTAMP value from the iSeries system as an unsigned 64 bit integer value. Is it possible to convert this timestamp into a readable format in windows machine? The iSeries timestamp value is an unsigned 64 bit integer value. All the time management routines which I can use on a windows machine deal with signed integer value. So the iSeries timestamp appears as a negative value to the routines like ctime64() or gmtime64(). Any clues? P.Prasad

Software/Hardware used:
ASKED: July 21, 2005  9:39 AM
UPDATED: July 21, 2005  4:44 PM
RELATED QUESTIONS
Answer Wiki:
Can you provide a bit more detail as to where in Windows you are going to be using the value? The solution may be different in .NET vs Excel vs ASP etc.. Thanks, Jason
Last Wiki Answer Submitted:  July 21, 2005  9:57 am  by  JAS400   0 pts.
All Answer Wiki Contributors:  JAS400   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

I use the timestamp value in .NET environment. Basically, I transfer security journal entries from iSeries to a windows client so that I can do further processing there. The entries are in the form of records with multiple fields. One of the fields is the unformatted TIMESTAMP (system timestamp – DTS) field.

Pprasad123
 0 pts.
 

The QWCCVTDT API was first made available in V2R1 of OS/400, so I suspect that the *DTS format is proprietary to OS/400 and isn’t in any format that can be handled on any other system. I don’t recall ever seeing any description of the *DTS format. AFAIK, that format can only be converted by that API; none of the other APIs for date/time seem to be able to handle it. (APIs might exist; I just don’t know of any.)

If a *DTS value is needed on another platform, it probably must be converted to a standard form first.

IBM probably would find it difficult to change this. Old journals and journal receivers can go back a lot of years. The audit information that is held there must remain consistently accessible into the future. There are a lot of programs that already exist that expect the *DTS format to be sent through QWCCVTDT.

And journal information is not intended to be accessible through other platforms. If you want it in Windows, then you are responsible for doing the conversion.

Unfortunately, that’s about as far as I can go with this. Our company sells products that make entries from QAUDJRN available for 3rd-party consoles such as SiteProtector from ISS for example. So, I can only supply directions that point to IBM documentation.

Tom

TomLiotta
 107,755 pts.