Grant Ritchie writes -
>
>I've been lurking about for a while in the UK as well and joined this group
>mainly to get help on year 2000 issues on the 3000.
>
>Much of our software is inhouse and uses the good old TurboIMAGE/COBOL/VPLUS
>combination. Mainly we look to be opting to place bits of code into programs
>that check if a date, in YYMMDD format, is less that, say 300101 and if so
>assume it's year is >= 2000 otherwise it's 19xx. We are reckoning on having
>some other systems in place before 2030!! :-)
>
>Any other ideas guys?
>
 
   Using the SETCLOCK command on my 5.5 iX box to set the current date to
   Sept. 19, 2001 (don't worry - this is a crash and burn development
   machine with no Image logging), I found the CURRENT-DATE Special
   Register in COBOL returned 09/19/01 (mm/dd/yy - in a PIC 9(8)).  Some
   code I ran into first took this value and converted it to a PIC S9(4)
   YYMMDD value prior to doing compares and other arithmetic.  Thus,
   the resulting integer 10919 would compare less than today's (actual)
   date of 960919.  So the "bits of code" in this case should occur
   *prior* to the conversion from the PIC 9(8) to the PIC S9(4) values.
 
   Maybe I'm stating the obvious here, but have a colleage review your
   changes, or better-yet have a structured walk-through prior to
   implementation.
 
   cv
 
--
Craig Vespe [log in to unmask] Unison Software 811 Barton Springs, Austin Tx.78704
512-478-0611 http://www.unison.com NASDAQ UNSN disclaimer quote ANSI graphics