Re: Date/Time fields in DB file -- MIDRANGE-L

Subject: Re: Date/Time fields in DB file
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Fri, 11 Aug 2023 20:23:51 +0200
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hello Vern,

Am 11.08.2023 um 03:50 schrieb Vern Hamberg via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:

I don't have access to my pre 6.1 manuals so can't check on the older DDS. The 6.1 manual has this behavior described for date, time, and timestamp fields - look in your manual for the words "If the DFT keyword is not specified". This is in the documentation for the DFT keyword.

Found it, already for V4R5. I stand corrected.

The described fact is indeed for all three date related fields: Date, time, and timestamp.

I'm trying to remember, when did true date/time/timestamp data types come into DDS? I don't think we always had them.

They were there with V4R5 at least, but handling them programmatically is somewhat cumbersome in (ILE) RPG. The "internal" format for them in RPG is different than what's derived through external descriptions from PF/DSPF.

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Date/Time fields in DB file , Scott Klement

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.