|
Hi Peter, *DTS is an unformatted 8 byte system timestamp. It's returned or used by various APIs and MI functions - you can find an example of its usage if you take a look at the Qsy_Rtn_Entry_Usage_Attr_T structure here: http://as400bks.rochester.ibm.com/pubs/html/as400/v5r1/ic2924/info/apis/QSYF IVLA.htm For MOVE to convert character or numeric values to a timestamp they have to be in the correct external format (which *DTS isn't) - so here QWCCVTDT comes in handy... Best regards, Carsten Flensburg ----- Original Message ----- From: <midrange-l-admin@midrange.com> To: <midrange-l@midrange.com> Sent: Saturday, September 15, 2001 7:44 PM Subject: Re: QWCCVTDT API and *DTS format > > > Hi Carsten, > > What is a *DTS timestamp as opposed to the kind of timestamp that MOVE will > convert? > > Btw, I wrote a general purpose file display program 10 years ago similar to > WRKDBF and DBU using those numeric edit API's, which is why I brought that > one up -- a really good example of how bif's are so much easier than API's, > when they're available. > > Still curious, > Peter Dow > Dow Software Services, Inc. > 909 425-0194 voice > 909 425-0196 fax > > From: "Carsten Flensburg" <flensburg@novasol.dk> > > I mostly use QWCCVTDT to convert *DTS timestamps these days - as you say, > > MOVE will do nicely for most other data conversions. > > > > In general, I prefer to use bifs if they offer the functionality I need. > > Calling an API to do something the programming language already offers in > my > > opinion only adds unnecessary complexity to a program. - Let the > compiler > > do the work - and the RPG/IV reference the documentation. > > > > Talking about the edit APIs compared to their bif counterparts you'll > have > > to do two calls involving some rather exciting parameter definitions to > edit > > a numeric field, in stead of a single and simple bif expression. If you > > however require the ability to edit a field whose attributes are not > known > > at compile time, the _LBEDIT (Late bound edit) builtin makes this > possible > > whereas the bifs and APIs do not. > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-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.