Our worldwide consultants average over ten years of advising
and implementing procedures to get the best out of Telon, and, for those
companies not wishing to continue using Telon, implementing a viable exit
strategy.
New
releases of Telon installed Releases prior
to 2.4 will not support System/390.
Customization upgraded to new release Many companies have made alterations to Telon since installing it. Sometimes a new release is installed without realizing this, with unexpected results.
Customization made release-independent If Telon has been customized by changing macros, conditional assembly language skills are required to repeat the customization in a new release. By writing a post-processor to achieve the same effect, future release installations will usually not require any change to the post-processor, and if it does, the post-processor is in COBOL.
Eliminating Telon Although Telon generates COBOL, it is not possible to maintain the programs at the COBOL level for the long term without help. The programs contain CALL statements to various 'black box' subroutines. Functional changes to the programs often require changes to the parameters passed to these black boxes, and there is no documentation on how to do this. Also, new releases of IBM software can cause these black boxes to cease functioning. CASE Integrators has years of experience in persuading Telon to generate black-box-free, functional versions of programs which can then be successfully maintained at the COBOL level. This experience has also been crystallized into our Kicks-Out detelonizing toolset.
Telon backup and recovery Have you ever lost a version of a program you needed? There are ways of reducing the risk substantially.
Telon
interfaces to other products Testing tools, source management
systems, etc. seem never to work well with Telon unless
you know how.