Y2K

Mark - it is a '' BIG''  It depends  No one solution nor package fits all.
And you have missed several  key issues for TTEC.  

 My  feelings are that  yor  primary interests are in items 3 & 4 who what
were when and how. Plus how are the  Non-AS/400 systems being handled?
Well,  very interesting sets of considerations & details goes with all of
this. 

If  you  would like to contact me off line then we could  discuss your
specific environment - unless this is a general or marketplace survey.


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
____________________________________________________


>From: Mark Lazarus <mlazarus@TTEC.com>

>Date: Tue, 27 May 97 02:53:45 +0000
>
> I would like to know how people here are handling the Y2K problem.
>
> Some options:
>
>1) Throw out what you have and start over w/ a new package.
>
>2) Throw out what you have and start over w/ a new homegrown system.
>
>3) Use a Y2K analyzer and make the mods inhouse.
>
>4) Use a Y2K analyzer and outsource the mods.
>
>5) Retire December 31, 1999.
>
>6) "Problem?  We don't have no stinkin' problem!!!"
>
>7) Other (please elaborate).
>
> If 3 or 4, which analyzer are you (or will be) using?  Are you happy w/
>what it provides, i.e. how thorough is it, does it make suggested code / DB
>changes?  Does it handle RPG IV? Any other languages?  How is the vendor
>support?  How much is the package?  Overall, how good a value is it?
>
> How are you handling other systems - PCs, S/36, DECs, HP, other?  If you
>are making changes to a existing systems, are you using a change management
>package?  If yes, which one(s)?
>
> Misc:  Are you making enhancements at the same time?  Are you consolidating
>diverse systems?
>
> Does anyone have a writeup that they'd like to share?
>
> TIA.
>
> -mark
>
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>* 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   *
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>umidr
>
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *