Re: Retreive Source an MI program

No, you should have insisted on getting the whole source or no contract.

Source escrow, imho, is a very risky proposition...

On Wed, 9 Oct 2002, Mark Waterbury wrote:

> Dear Sas:
>
> >>>---> NOTE: Let this be a "lesson" for all ... <---<<<
>
> You should have insisted on a Source Code Escrow Agreement,
> so that, in the event the vendor goes "out of business" or bankrupt,
> insolvent, etc., you would be given access to the source code.
>
> This should be a standard part of any decent software license
> agreement, and you should always insist on it, especially when
> purchasing (or licensing) software for which you do not get the
> source code with the package.
>
> This unfortunate situation that you now find yourself in is precisely
> why "source code escrow" agreements or clauses in contracts and
> software license agreements exist, and why there is a fairly brisk
> business for software escrow agents, who maintain these copies
> of the source code for their clients.
>
> Sincerely,
>
> Mark S. Waterbury
>
> ----- Original Message -----
> From: "sas" <sas@toto.co.id>
> To: <mi400@midrange.com>
> Sent: Wednesday, October 09, 2002 8:03 PM
> Subject: Re: [MI400] Retreive Source an MI program
>
>
> > Dear Sirs,
> > The background is :
> > I have many Program on ILE (RPGLE,CLE ) and MI  , but we have no program
> > source .Last time when we want to change the logic program we just ask the
> > seller, but unfortunetly now the seller are not exist anymore ( "Out of
> > Bussiness") .
> > A year ago I already contact to source retrieval but unfortunately  they
> > didn't have decompiler for ILE
> > Regards,
> > Sas
>
>
> _______________________________________________
> This is the MI Programming on the AS400 / iSeries (MI400) mailing list
> To post a message email: MI400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/mi400
> or email: MI400-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/mi400.
>