RE: Year 2000

[Glenn Ericson <Glenn-Ericson@xxxxxxxxxxxxxxxxxxxxxxxxxxx>]

Bob 
your absolutely right. There are  three major reasons:

1 Minimize modifications/change to ensure a high success rate in minimum time
2 the RPG III  support for the data  type
3 Performance  concerns.

Net is is  also a double conversion  from RPG IIII [group] to  the  newer
versions.

 During the  Y2K conversions many are, and  lots more will be racing the
Clock to achieve business continuity at minimum.  Once  one realizes the
size of the  2000 marshmallow all that t  remains is to determine how fast
one cantuck the "BIG"  thing way in time without going  broke.

Glenn
___________________________________________________
Glenn Ericson,          Phoenix Consulting                      
P O Box 701164   East Elmhurst NY 11370-3164 USA                            
Ph. 718 898 9805         Fx. 718 446 1150
AS/400 & Year 2000- - Solutions  © 1997copyright,  all rights reserved
____________________________________________________

At 02:54 PM 6/6/97 +0000, you wrote:
>Steve,
>
>I am no expert, but I believe the reason they do not convert to real AS/400 
>date fields is because they want to work with your existing code. I f you, 
>for example, have a date routine that calculates the number of work days 
>for a give period, that routine will continue to work (hopefully) after the 
>conversion. If a tool changed the data type to a date field, that routine 
>could need some reworking.
>
>As I said, I don't know for sure what the reasoning is. I suppose a tool 
>could be smart enough to move a date field to a numeric field and then back 
>again, but that does add overhead. Plus, RPGIII doesn't like native date 
>fields anyway, so the big payoff wouldn't be there unless you were moving 
>to RPG IV at the same time.
>
>Bob Cozzi
>
>
>-----Original Message-----
>From:  Cotes, Steven [SMTP:cotess@data-io.com]
>Sent:  Thursday, June 05, 1997 4:13 PM
>To:    'MIDRANGE-L@midrange.com'
>Subject:       RE: Year 2000
>
>
>
>> ----------
>> From:        Susan Durrie[SMTP:sed1@earthlink.net]
>> Sent:        Thursday, June 05, 1997 7:22 AM
>> To:  MIDRANGE-L@midrange.com
>> Subject:     Year 2000
>>
>       <snip>
>       >Our greatest debate is whether or not to use native dates or to
>       >go to an 8 digit numeric YYYYMMDD for our file date fields.
>
>A number of tools (claim to) do most what you want, including the one
>from ASC.
>Almost all of them can convert to and populate 8 digit numeric fields.
>The one feature I haven't seen is the option of converting to date data
>types.
>I'd like to know of one that does.
> - Steve Cotes
> - cotess@data-io.com
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>* This is the Midrange System Mailing List!  To submit a new message,   *
>* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
>* this list send email to MAJORDOMO@midrange.com and specify            *
>* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
>* should be directed to the list owner / operator: david@midrange.com   *
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>* This is the Midrange System Mailing List!  To submit a new message,   *
>* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
>* this list send email to MAJORDOMO@midrange.com and specify            *
>* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
>* should be directed to the list owner / operator: david@midrange.com   *
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *