>>Doug, >>Quarts won't fit in pints, in short >>there are things that you can do in PLI which you can't do in Cobol >>and very few things which you can do in Cobol which you can't do in >>PLI ( possibly Cobol report writer) >>PLI evolved from Cobol (and others) >>So, you can't really convert PLI to Cobol >Alpha M Style System Download. Oh REALLY? I converted 300+ programs written in PL/I to COBOL in about 1 1/2 >years.

Some of the programs were badly structured in PL/I, and I rewrote them >in structured COBOL. Many of them used the PL/I version of ALTER/GO TO, the >LABEL variable. Petrochemical Process Handbook Pdf. Those were a real thrill(!). PL/I, like any other language can >be written with spaghetti code, and I've seen lots! >Bill Reed Thu, 18 Jul 2002 03:00:00 GMT. It does appear that I've at least gotten some response back and I really appreciate the feedback but I now feel that I need to disclose some of my reasons for this effort. We are part of a migration services group that provides conversion services to our customers on a worldwide basis.

I have written tools to convert Cobol and other 4GL programs (utilizing VSAM/Indexed RMS and Cincom's TOTAL/SUPRA call structures) to open SQL environments (ORACLE, DB/2, etc.) My process is a complete turn key solution where as I convert all the programs, copybooks, DCL/JCL, data, etc from the old legacy environment to the create the new SQL environment. Typically this has been in the VMS to UNIX areas. The PL/1 issue is something new in that one of our customers wants to move all their programs to ORACLE and as Clement pointed out, Oracle is claiming that they are not going to support a PRO*PL/1 compiler. SO, this is the main driving force. Rather than rewrite the code from scratch (which would take longer than the customer has as there are several hundred programs), they have turned to us to see if an automated process is available or can be developed. As someone in the responses pointed out, not all constructs can be handled easily and we react to those on an exception basis. And if we got a 100% conversion of a program, well, that would be too optimistic.

We shoot for 70-80% of any conversion with the remaining issues handled manually during program compilation, testing, etc. Download Free Apps For Samsung Java Phones. Believe it or not, there are several companies out there who say they do this type of conversion. However, they may be too costly of a solution and they may not have any real world experiences or their solutions or too dated for us.

Ispirer MnMTK is the application migration tool, which supports COBOL to Java conversion of any level of complexity. We develop Ispirer MnMTK using our customer. TSG Software migration CA-Telon Mantis DB2 Cobol. PL/I include files are converted to Cobol copybooks; Embedded SQL and command level CICS code is adjusted for.