A couple quick comments from me: 1. IBM eliminated Single Version Charge (SVC) time limits. If, for example, you have an OS/VS COBOL application that's still lagging behind, you could keep a CICS Transaction Server 2.3 AOR running it until you can get it pulled forward, and surround that laggard AOR with CICS Transaction Server 5.3 (or better yet 5.4) regions for everything else you run. CICS TS 2.3, the last release that supported OS/VS COBOL applications, has reached End of Service, of course. So has OS/VS COBOL for that matter. However, CICS has long supported freely intermixing interoperating releases, unless exceptionally documented otherwise. And there shouldn't be any financial obstacle in doing that now.
2. It's nearly certain you're taking a longer path length through the OS/VS COBOL execution versus an optimized Enterprise COBOL Version 6 alternative reality. Try to make the trek if you can, as soon as you can. There's considerable reward in that, especially if this OS/VS COBOL code is either contributing to your monthly peak 4HRA utilization, or if it is elongating your batch execution time when your batch execution time is your peak demand driver. 3. If the problem is that you lost the source code, reasonable source recovery might be possible. (There are some previous discussions about that.) -------------------------------------------------------------------------------------------------------- Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z and LinuxONE, AP/GCG/MEA E-Mail: sipp...@sg.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
