Re: Y2K

In a message dated 97-05-27 03:23:58 EDT, you write:

<< Subj:        Y2K
 Date:  97-05-27 03:23:58 EDT
 From:  Mark L
 Sender:        mcsnet!midrange.com!midrange-l-owner@Mcs.Net
 Reply-to:      MIDRANGE-L@midrange.com
 To:    midrange-l@midrange.com, MAJORDOMO@midrange.com
 
  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. 
NOT a GOOD  CHOICE 

 2) Throw out what you have and start over w/ a new homegrown system.
 CRAZYNESS

 3) Use a Y2K analyzer and make the mods inhouse.
 GOOD POSIBILITY - IF  FITS

 4) Use a Y2K analyzer and outsource the mods.
 PARTIAL - EXCEPT TESTING (FINAL)

 5) Retire December 31, 1999.
 A THOUGHT  If  my LEGAL LIABILITIES GO AWAY?

 6) "Problem?  We don't have no stinkin' problem!!!"
 WE ALWAY$ DO IT BETTER - HeRe !!!!  RIGHT
 
 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?

IT DEPENDS - BUT NO FOOLING the  System?
 
  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)?

 PC & S/36
 
  Misc:  Are you making enhancements at the same time?  Are you consolidating
 diverse systems? 

    DEATH WISHES
 
  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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *