Re: Date Data Type in O-Spec -- RPG400-L

× 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.

Subject: Re: Date Data Type in O-Spec
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Thu, 17 Sep 2009 15:22:50 -0400
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Mike wrote:

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.

It only wants *USA, not DATFMT(*USA).

O ADUEDATE 34D*USA

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.