Stunning relicense quote

Tue Nov 1 12:01:50 CDT 2016

Herald raises an important point about a platform change.  Focusing on the base language is misleading at best.  What he identifies as the background processing/shell scripting, etc.  Is usually more difficult to migrate than the base application.  Therefore, I suspect that there could be more to the story than simply the Powerhouse license.  For example, if the customer has some dependent 3GL code such as COBOL, a few 3rd party products such as Suprtool, MPEX along with JCL, UDC’S, Command Files the cost to migrate all of that and the database and other file types could well exceed the price of the Powerhouse license.  Further, there are some differences in how Powerhouse on a Linux platform uses databases and adaptations must be made for those. 

It will be interesting to see what all was quoted, if anything, along with the Powerhouse license. 

Charles Finley

(619) 795-0720

From: powerh-l-bounces+cfinley=xformix.com at lists.sowder.com [mailto:powerh-l-bounces+cfinley=xformix.com at lists.sowder.com] On Behalf Of Herald Kaffka
Sent: Tuesday, November 01, 2016 7:58 AM
To: Craig Lalley; Ron Seybold; powerh-l at lists.sowder.com
Subject: RE: Stunning relicense quote

Big part of those costs “should” be related to how much background processing/Shell scripting you have.

The Native Powerhouse portion should not require much programming effort, but batch/embedded shell scripts

Are an entirely different can of worms.

If that’s simply a software licensing quote, then somebody really is pushing their migration consulting services…

(We looked at moving from VMS to LINUX at one point, it wasn’t the Native Powerhouse portion that nixed the ideal, 

It was the Batch/Shell scripting work).  Decision was to “support in place” until such a time as we hit “replace in total”.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20161101/62950de8/attachment.htm>