Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>Run away!</strong></p> <p>At least until your client comes around to using a real database system to implement the order entry system. All transaction processing systems need to ensure <a href="http://en.wikipedia.org/wiki/ACID" rel="nofollow noreferrer">ACID</a> properties are maintained for every transaction. This is one of the fundamental reasons why real data processing systems use databases. Not using a DBMS is a sure formula for disaster (sooner or later).</p> <p>Can COBOL be interfaced to a web service or a GUI type application? The answer is definitely yes and it is not an uncommon practice. Making it happen can be a more or less painful process depending on how the COBOL application is structured. If it has a <a href="http://en.wikipedia.org/wiki/Client%E2%80%93server" rel="nofollow noreferrer">Client/Server</a> type structure, then you only need to replace the Client side components with web/GUI components, insert the appropriate middle-ware to connect to the server and you are pretty much done. If the COBOL application was developed as a <a href="http://en.wikipedia.org/wiki/Big_ball_of_mud" rel="nofollow noreferrer">big ball of mud</a>, then you are in for a rough ride. Since your client developed his system on a stand-alone platform by himself, I am willing to bet serious money the "big ball of mud" model applies. Be prepared for the worst.</p> <p>If this application only took "hours" instead of "months" to understand it doesn't sound all that complex - you may find rebuilding it from scratch is a viable option. However, don't underestimate the work in doing that either!</p> <p>As for upgrading the AIX system or switching to Linux, I cannot help you. </p> <p>Here are a couple of resources for COBOL on AIX that you might want to review:</p> <ul> <li><a href="http://www-01.ibm.com/software/awdtools/cobol/aix/" rel="nofollow noreferrer">COBOL AIX vendor information</a></li> <li><a href="http://publibfp.dhe.ibm.com/epubs/pdf/igyapg00.pdf" rel="nofollow noreferrer">COBOL for AIX User's guide</a></li> </ul> <p>If you choose to go the Linux route I would recommend checking out:</p> <ul> <li><a href="http://www.opencobol.org/" rel="nofollow noreferrer">OpenCOBOL</a> COBOL to C translator</li> <li><a href="http://opencobol.add1tocobol.com/#how-do-i-use-opencobol-for-cgi" rel="nofollow noreferrer">OpenCOBOL CGI programming</a></li> </ul> <p>Your client expressed interest in MicroFocus COBOL. MicroFocus is probably the largest COBOL vendor outside of the mainframe market. They have a very good reputation. <a href="http://www.microfocus.com/products/micro-focus-developer/micro-focus-cobol/cobol-UNIX-and-Linux/server-express.aspx" rel="nofollow noreferrer">MicroFocus also supports web development on Linux platforms</a> and tends to have good support for IBM COBOL dialects which may be a consideration if migrating from AIX.</p> <p>My final words of advice are to run away until your client wakes up to the following facts:</p> <ul> <li>Data and transactions need to be managed using a real DBMS that supports ACID.</li> <li>tacking a web based order entry system onto a "ball of mud" is not a week-end project. It may require a complete refactoring and possibly a complete re-write of the existing system</li> </ul> <p>BTW... If you want to retain a working relationship with this person, don't call his system a "ball of mud" even if it is one. He built this thing and probably sees it as one of his children.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload