RE: RPG III - Object to Source DE-Compiler

["Rick Rayburn" <the400man@xxxxxxxxxxx>]

Many clients purchase software packages from vendors who also include the
source as part of the deal...especially with 400 applications. However, the
programs that contain the software security routines are usually not
observable and/or not included with the delivered materials...understandably
so too. Problem is, when they go out of business and you want to migrate to
a new machine (the protection is always at the box serial# level), you have
to go through too much crap to establish a work-around or to actually
identify and remove (if possible) the programs handling these functions. And
unfortunately, most business people are not conscious of this caveat and, as
a result, NEVER think to ask for the type of clause you mention...but it
surely is something I will think about going forward!

Thanks.

Rr


> From: "jt" <jt@ee.net>
> Reply-To: midrange-l@midrange.com
> To: <midrange-l@midrange.com>
> Subject: RE: RPG III - Object to Source DE-Compiler
> Date: Thu, 3 Oct 2002 11:22:09 -0400
>
> I'll weigh in, in agreement with Joe...  Absolutely...!
>
> |
> | They better check their agreements for a source escrow clause.  If a
> | software vendor goes out of business, general practice is to have a set
> of
> | source in escrow for their clients.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.



_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com