|
V3R1 I believe. > -------- Original Message -------- > Subject: RE: When did IBM introduce the date data type > From: "Chris Payne" <CPayne@xxxxxxxxxxxxxxx> > Date: Fri, December 02, 2005 1:03 pm > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > > Or to put it a non-caveman sounding way; When could RPG programs access > these new date data types? > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Payne > Sent: Friday, December 02, 2005 12:59 PM > To: Midrange Systems Technical Discussion > Subject: RE: When did IBM introduce the date data type > > When could access date types through RPG? > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bruce Vining > Sent: Friday, December 02, 2005 11:52 AM > To: Midrange Systems Technical Discussion > Subject: Re: When did IBM introduce the date data type > > Around 1992 there was a partial release known as V2R1.1. This release > provided database support for date, time, timestamp, variable length > fields, and nulls. > > Bruce Vining > > > > > > "Chris Payne" > > <CPayne@TheCrownG > > rp.com> > To > Sent by: <midrange-l@xxxxxxxxxxxx> > > midrange-l-bounce > cc > s@xxxxxxxxxxxx > > > Subject > When did IBM introduce the date > > 12/02/2005 10:14 data type > > AM > > > > > > Please respond to > > Midrange Systems > > Technical > > Discussion > > > > > > > > > > When did the date data type become available on DB2 for the iSeries? > > > > Chris > > > > ___________________________________ > Christopher Payne > CPayne@xxxxxxxxxxxxxxx > System Administrator/Programmer > > > > The Crown Group > Corporate Offices > 2111 Walter Reuther Drive > Warren, MI 48091-6199 > > > > Phone: (586) 575-9800 > Direct: (586) 558-5317 > Fax: (586) 575-9856 > > > > > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-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.