|
The Lillian date is related to the Gregorian calendar, IIRC - you could do a google on it if interested. Anyway, it is for real.
There is another API that converts seconds since that date to a character date string - CEESECM - and another that converts to integers - CEESECI - separate integers for year, month, etc.
I think you could figure out the number of seconds that the MS starting date comes after the above starting date, add that amount to whatever value they give you, then use one of the above APIs to convert.
BTW, there is a feedback code parameter - make sure to always include it - it is called omissible, but that does not mean it is optional - it is 12 bytes long - just always include it - it can be a character variable of length 12. If you don't pass it, you have to pass a NULL pointer - good luck doing that in RPG!!
Scott Klement has a lot of good info on these APIs - check the archives here or find his website.
HTH Vern At 08:51 PM 1/14/2007, you wrote:
I am doing some work reading Active Directory LDAP data from an RPG program. I have not problem getting the data but for some reason MS elected to not show date/time stamps in any rational fashion. The date/time stamp is in seconds since 00:00:00 January 1 1601 like 127122881993040000. Anyone know how to translate the number of seconds elapsed since 00:00:00, January 1, 1601, to a date and time? -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.