×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
That will affect all date fields in your program, it may not be an issue,
but be careful. You can add the DATFMT to the D spec when you define the
output field.
From:
Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
To:
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Date:
09/16/2009 12:43 PM
Subject:
Re: Date Data Type in O-Spec
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx
just use your H spec DATFMT(*USA)
Thanks,
Tommy Holden
From:
Mike <koldark@xxxxxxxxx>
To:
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Date:
09/16/2009 11:44 AM
Subject:
Date Data Type in O-Spec
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx
I find it weird I can't find anything on this. I am putting out a date
data
type field on a report defined as O-Specs (minor updates to an older
program). How do I format the date to a format I want? Currently it comes
out as *ISO. I want it in *USA. I am trying to do:
O ADUEDATE 34DDATFMT(*USA)
but I get a invalid date format error.
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
