|
Hi Peter
I think I wandered across that article, looking for prototype and other stuff - Tim's example was in C but understandable.
Now, if I continue with this, I need to put some time zone stuff there - the *UTC types are dates and times at Greenwich, I think.
Vern
On 10/23/2020 3:10 PM, Peter Dow wrote:
Hi Vern,
I happen to have run into the same issue. The watch monitor (STRWCH) passes event data to a monitor program. One of those items is MsgTimestamp char(8).
I found this:
https://www.mcpressonline.com/programming/apis/the-api-corner-how-do-you-want-that-date-and-time
which explains how to use the QWCCVTDT api.
I'm just getting started on a test program.
--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx>
/
On 10/22/2020 11:33 PM, Vernon Hamberg wrote:
Hi all
There are 3 UTC data types in message data fields. In particular, message CPF1241 has these in the message data.
I would like to extract them for use in the HISTORY_LOG table function. They are each 8-byte values - does anyone know how to get a presentation value? They are supposed to have date and or time that is adjusted for UTC offset - something like that.
I've looked at the MI CVTD function, but there isn't anything obvious there. I've not yet looked at other date/time conversion functions.
Cheers
Vern
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.