Year 2000
charles_kinghorn,_charking@niagara.com
And is there any good literature on the subject?
Romel Rivera
Charles Kinghorn, char...@niagara.com writes:
> Does anyone have experience yet with the maintenance of existing programs in preparation for the year 2000? If so, how was it?
> And is there any good literature on the subject?
>
We at Xinotech Research have a metalanguage-based tool that can be used
to transform COBOL code automatically to solve the year 2000 problem.
We have not written the transformation rules to support year 2000
correction, but we would like to approach this issue soon. Our tools
can also be used to transform to OO COBOL 95, it that would be of
interest. Let me know if interested, i'll send information and papers.
Romel Rivera,
Director of Reseach,
ro...@xinotech.com
612-379-3844
Peter Lacey
Computerworld. It rather implies that not everyone is taking this
seriously yet.
David C. DeForest
>Subject: Year 2000
>Date: 20 Apr 1995 11:25:29 GMT
>Does anyone have experience yet with the maintenance of existing programs in
> preparation for the year 2000? ...
My solution was a flat out file convertion with the simple if statement for
the date.
01 DATE.
05 CC PIC 9(2)
05 YY PIC 9(2)
05 MM PIC 9(2)
05 DD PIC 9(2)
IF YY > 50
MOVE 19 TO CC
ELSE
MOVE 20 TO CC.
This may not be the best solution but it works, I'll worry about the
problem this little algorithim causes in 2020.
D.C. DeForest
defo...@defcal.ultranet.com
Bob Brown
solution seems to be changing procedure rather than file conversions. The
problem with file conversion is that all programs using files being
converted must be completed at the same time. With procedure only,
programs can be converted individually. Two problems with this: 1) when
the date is part of a sort 2). when the date is part of an index or key
to a file. In both of these you must do a file conversion.
I will change procedure as follows:
If effective-date > expiration-date (I work for an insurance company)
move xyz to abc.
Change to:
call "convert-year" using effective-date, ws-date-y2k-1.
call "convert-year" using expiration-date, ws-date-y2k-2.
if ws-date-y2k-1 > ws-date-y2k-2
move xyz to abc.
A copy book will be inserted in each program where this is used.
We have macro's for TSO that make coding the call statements and changing
the IF statements very easy.
As far as I can tell only IF statements with > or < won't work. EQUAL's
should still work. COMPUTE's need special care but coudl be handled in a
similar way.
Any thought's on it?
-
BOB BROWN MBG...@prodigy.com