|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Hello Dan, I do not believe that the *ISO date format will work for the TIME OpCode into a numeric field, have you tried using (*YMD)/(*CYMD)?? [I don't know if these are availble at V3R2!!) Regards John "Dan Bale" <dbale@samsa.com> Sent by: rpg400-l-admin@midrange.com 18.07.2002 00:25 Please respond to rpg400-l To: <rpg400-l@midrange.com> cc: Subject: TIME opcode to 14.0 field: how determine or change date format? NOTE: This is v3r2 RPG-IV; the TIME op code requires a numeric result field. I need to retrieve the current date (NOT job date) in an RPG-IV program compiled at v3r2 and end up storing that date in YYYYMMDD format. Here's my snipped up code: h DatFmt(*ISO) debug c Time $Time14 14 0 I was hoping that the DatFmt(*ISO) might force the TIME op code to format the date in the result field as YYYYMMDD, but it yields MMDDYYYY. If I do a CHGJOB DATFMT(*YMD), then I get the desired result. Unfortunately, I cannot change the job's date format in production. Is there a way to retrieve the current date in the format I need, or a way to determine the format that the TIME op code will generate so I can convert it as necessary at run time? - Dan Bale (I am *NOT* "Dale" http://archive.midrange.com/midrange-l/200105/msg00281.html ) _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com 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-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.