Are you missing the most important precautions when upgrading COBOL and CICS? Experts Jim Schesvold and Tom Ross...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
will outline the necessary steps to ensure your upgrade goes smoothly.
Our shop is planning to migrate old COBOL and CICS (VS COBOL, MVS COBOL) to COBOL 390. Can you please tell me what precautions I should take, what reserve words I should be aware of and whether I should test each batch and online programs after conversion?
Jim Schesvold's answer
The biggest precaution you can take, in my opinion, is to carefully research both your applications and COBOL migration considerations and tasks. Do this in conjunction with your application programmers, and communicate your findings with them when this phase of the project is complete. Then write down a thorough migration plan, including specific dates that are negotiated with the people performing the migration, and track this plan on a weekly basis. This includes weekly status meetings with the key players.
Without knowing your application program inventory, it is difficult to tell you what reserved words to be concerned with. If you don't use a specific reserved word, you obviously don't need to concern yourself with that one. The COBOL migration documentation is useful in this area. I've listed a number of key references below.
Yes, I would test every program if that is at all feasible. Solving a problem in test is less time-intensive, is more easily debugged and involves a whole lot less stress than when the problem occurs in production. And while you may view a group of programs as essentially identical from a testing perspective, sometimes the slightest difference can make a huge difference.
Here's a list of COBOL migration references which will be helpful to you:
- COBOL Migration Resources
- COBOL Migration and Upgrading
- Enterprise COBOL for z/OS V3R4 Migration Guide
- Enterprise COBOL for z/OS V3R4 Online BookShelf
- z/OS V1R7.0 Language Environment Run-Time Application Migration Guide
- z/OS V1R7.0 Language Environment Bookshelf
- SHARE Presentation: An LE Migration From A To Z
- SHARE Presentation: Migrating To COBOL Compilers Under LE
- SHARE Presentation: Migrating COBOL And PL/I Run Times To LE - Common Issues
One last thing to keep in mind: There are products from IBM and other vendors that aid in your conversion. I won't recommend any particular product, because that is in no small part dependent on the nature of your applications and how they are structured. But it is worth looking at this option, because these products can in many cases reduce the effort of performing a COBOL conversion.
Tom Ross' answer
The first step you take should be to do a run-time only migration from the older run-times to LE (Language Environment), if you have not already done so. Make sure that neither the OS/VS COBOL library nor the VS COBOL II runtime library are in your LNKLST/LPALST. After you have done this, you are fully supported by IBM service, even with your old modules. The COBOL Migration Guide will tell you how to get to LE. In most cases you don't even need to relink!
If you want to start using new compilers (after you have everything running under the new runtime library) then you will start doing recompiles. You mention moving to "COBOL 390," and I don't know what that is, but IBM had a compiler called "COBOL for OS/390 & VM" that went out of service at the end of 2004, so you should not be moving to that one. You should move to Enterprise COBOL version 3, with our last release being 3.4 in September 2005. There is a huge difference between recompiling OS/VS COBOL programs with a newer compiler versus recompiling VS COBOL II or later programs: VS COBOL II and later compilers are all compatible; OS/VS COBOL is not. So, if you really have some programs that were compiled with COBOL for MVS and VM (that is how I interpreted your reference to "MVS COBOL"), then you don't need to test those programs when you compile with Enterprise COBOL; they are guaranteed compatible. Moving from OS/VS COBOL requires some pretty good testing, on the other hand.
Reserved words are not generally a problem for the thousands of customers I have worked with, but the source conversion tools can handle them for you anyway. IBM sells a tool, CCCA, that can automatically convert OS/VS COBOL programs to Enterprise COBOL, including reserved words. As I said, VS COBOL II (with NOCMPR2) and later programs do not need to be converted when moving to Enterprise COBOL -- just recompile when ready!