Unfortunately, if you're defining commands with parameters of type *DATE, "When it is passed to the command processing program, it is always passed in the format Cyymmdd..." (from the PARM keyword help text).

I supposed you could use type *CHAR and write a validity checking program to go with it, but so far for me it hasn't been worth the effort.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 11/12/2015 9:06 AM, John Yeung wrote:
On Thu, Nov 12, 2015 at 11:45 AM, <rob@xxxxxxxxx> wrote:
[...] Otherwise, valid dates are in the range
of August 24, 1928, to May 9, 2071.

Now why it can only convert *YYMD from 20710509 into *CYMD 1710509 and not
*YYMD 20710510 into *CYMD 1710510 escapes me.
I don't understand either. My first guess was that the date range
would be either 32768 days (or slightly less) or 65536 days (or
slightly less). But it's actually 52124 days, inclusive of the
endpoints.

For what it's worth, the center of that date range is the dividing
line between December 31, 1999 and January 1, 2000.

I think I would avoid this crap and start using 'real' date columns.
I agree that it's crap. In fact, as far as I'm concerned, *CYMD is
even crappier than formats with 2-digit years.

John Y.


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].