TELON to CICS Conversion

TELON to CICS Conversion   Introduction   Conversion guidelines   Call programs   Maps/Screens   Function keys Processing   Attribute Handling   Others   Team Details

Introduction CA-TELON, developed by "Computer Associates" is a productivity tool for the IBM Mainframe. It provides all facilities necessary to bring an application from the early stages of design – through development and testing – to full production and maintenance. It is used to develop Batch and Online programs easier and quicker than normal COBOL programming, as it involves a step-by-step process to build a complete application. The programmer simply provides information about the design of the program, rather than writing it in a higher-level language. TELON takes care of generating all the detailed syntax required by the language compiler. As TELON uses some standard procedures for developing COBOL codes, we need to find out some sort of guideline for converting an existing application form TELON to some other technology for re-engineering purposes. This document deals with the guidelines for TELON to CICS conversion. The main concern in this conversion procedures are inbuilt subroutines used by TELON, attribute handling, Screen processing and Function Key processing. You may require some additional guidelines for converting an existing application from TELON to CICS, which were beyond our project scope. Guidelines mentioned in this document are based on our project experience and existing application.

Conversion Guidelines Please refer TELON ppt, to get a fundamental understanding of the flow of a TELON program. The section names given in TELON.ppt are generated in all TELON programs and are followed in the conversion guidelines as well.

Call Programs/Subroutines Telon uses some in-built subroutines for standard validations e.g., date validations, character/integer validations etc. We need to replace these subroutines with the corresponding COBOL call programs or we may have to add extra code for these validations. Table 1.1 consists of some of the in-built subroutine with their description, which we faced in our project and require separate call programs. Other than these subroutines some routines don’t require separate call programs, but the removal of those routines require slight modification to the code. These subroutines are ILALPHA and IFULLNUM. There may be some other subroutines available in Telon for which one need to analyze and find out the purpose of that particular subroutine. The conversions for in-built subroutines can be understood by following example: $$$$$$$$$$$$$$$$$----------------- OLD ----------------

CALL 'ODATE' USING

TPO-FROMDT TPO-FROMDT-LTH WORKFLD-NUMERIC.

$$$$$$$$$$$$$$$$$----------------- NEW ----------------

CALL 'XXXXX' USING

TPO-FROMDT TPO-FROMDT-LTH WORKFLD-NUMERIC.