Several companies have decided not to use Telon for new development, and have gradually lost expertise in Telon.  Now they are looking for ways to avoid the continuing expense of maintaining Telon expertise in-house, or paying to fly in Telon contractors.

Just save the generated COBOL (or PLI) source and throw the Telon source away?

The main problem with this is that included in this COBOL source are many CALL statements to various 'black boxes' (subroutines) for which you have no source code.  Changes to your program will require changes to the parameters passed to these subroutines, and the format of these parameters is confusing and undocumented. (If you have already fallen into this trap, we can help considerably, but not completely).

Also these subroutines are dependent upon the operating system, and one day an operating system change will blow them away.....

We could mention other problems with this approach, but these seem enough.

Can we generate COBOL source without subroutines?

Without using undocumented features of Telon, the answer is 'nearly'.  CASE Integrators Corp. can provide you with source code for the subroutines or show you how to eliminate them.

We'd really like to get rid of the 3270's too, and go client/server.

Many companies have decided to move to client/server.  Because a Telon program is really a non-procedural description, it can in fact be made to generate a client/server program.  Two products to do this have come to market.  We provide a brief Q & A to help you choose the right product for you:

Do you wish to continue paying Telon maintenance and maintaining Telon skills?  Yes No

Home Page
Back to Consulting
Office Locations and Contact information