|
Peter, I don't think this was supported on V3R2. I seem to recall being very frustrated by that. Eric DeLong -----Original Message----- From: Peter Dow [mailto:pcdow@yahoo.com] Sent: Wednesday, May 16, 2001 11:15 AM To: RPG400-L@midrange.com Subject: Re: Date format in V3R2? Hi Brad, Why not skip all that stuff and simply do the TIME opcode into a timestamp result field, then move it in whatever format you want to a numeric field? D MyDate S 8p 0 D SysDate S D DATFMT(*ISO) C TIME SysDate C *ISO MOVE SysDate MYDATE Unless there's some reason you want to know the job date format independent of your objective of logging the date in yyyymmdd format. That's something you'd think would be in the program status data structure, but I don't see it. hth, Peter Dow Dow Software Services, Inc. 909 425-0194 voice 909 425-0196 fax ----- Original Message ----- From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com> To: <RPG400-L@midrange.com> Sent: Wednesday, May 16, 2001 7:37 AM Subject: Date format in V3R2? > Is there any way to get the date format used in the job in an RPG program? > > Heres my dilema. I am logging data and always want to store the date in > YYYYMMDD format in an 8,0 field. > > So, with I do a TIME operation I get the date and time. Now, I want to do a > test(d) on the date to see if it's *USA, *ISO, or *EUR. I'm seeing bugs in > the way it works, though. > > Does anyone have any suggestions on a good way to do this? It has to be > compliant with V3R2. Here's what I have that doesn't work: > > D DS > D TimeStamp 1 14 0 > D OperTime 1 6 0 INZ > D OperDate 7 14 0 INZ > * > D ISODate S D DATFMT(*ISO) > D USADate S D DATFMT(*USA) > D EURDate S D DATFMT(*EUR) > * > C TIME TimeStamp > C *USA TEST(d) OperDate 99 > C *EUR TEST(d) OperDate 98 > C *ISO TEST(d) OperDate 97 > * > C select > C when (not *IN99) > C MOVE OperDate USADate > C MOVE USADate ISODate > C MOVE ISODate MYDATE > C when (not *IN98) > C MOVE OperDate EURDate > C MOVE EURDate ISODate > C MOVE ISODate MYDATE > C other > C MOVE OperDate MYDATE > C endsl > > Example of error is: > > 20010304 > 20010304 > 20010304 > 20011004 Looks like october 4, should be April 10th. > 20011004 Looks like october 4, should be April 10th. > 20011004 Looks like october 4, should be April 10th. > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.
midrange.com
