Make sure everyone involved with the migration is trained on LE, especially those reviewing the LE compilation changes. Make sure the LE program or application migration issues have been previously identified and are implemented when the changes are applied.
The actual migration process (physically making the changes) requires participation of all the stewards of the application development and maintenance process. Personnel from application development and support, plus subsystem and z/OS installers, must be involved.
Summary and detailed analysis reports should be produced to satisfy the technical requirements of all participants. For instance, all issues could be broken down into three high-level categories:
- LE run-time issues
- LE-conforming compiler issues
- Middleware issues.
Each of these categories can be further subdivided by specific technologies such as CICS, DB2, and by languages. The effort should be tailored to develop the LE project plan, and the information provided to all participants so they can complete their tasks in a timely manner.
Figures 1 through 5 show sample reports that can be used in project assessment, planning, migration, and management.
LE Migration Complexity
An LE migration and conversion is neither as simple nor as complex as it may appear. For example, the conversion of old source syntax from an outdated OS/VS COBOL syntax that used the 1968 standard language to the 1985 level standard, while also having to deal with changes to the CICS commandlevel language can appear to be daunting. By applying appropriate tools such a s t h e IBM COBOL an d CICS Command-Level Conversion Aid (CCCA) tool to the process, it’s typical to find that the tool can handle more than 90 percent of the work. It isn’t unusual for CCCA to address 100 percent of the source language changes.
CCCA isn’t the only such tool; you can use several others for this portion of the migration process. The key point is that the use of appropriate tools can simplify the task from one that may initially seem a major effort into a purely mechanical task that just requires careful monitoring and some reasonable testing. On the other hand, attempting to perform this task manually can take an extended time and is quite errorprone.
Frequently, an LE and compiler migration project may take a year or more to complete, depending on the resources allocated; it also may be much shorter, depending on your starting point. More than one tool is often required to efficiently complete the migration. You should first acquire tools that help you complete the assessment phase of the LE migration. Once you have a good understanding of your inventory, you can then make a more intelligent decision about the additional tools that may be required.
The COBOL, PL/I and LE migration guides provide some complexity charts and guidelines to help you size the effort. The more complex the inventory, the more likely tools should be considered to assist in your migration process.
A rather famous saying is, “If you don’t know where you’re going, it matters not which path you take.” It also can be said that, “If you don’t know where you’re going, how do you know when you’re there?” And there’s a Yogi Berra variation, “You got to be careful if you don’t know where you’re going, because you might not get there.”
All three variations apply to an LE migration that commences without a clear understanding of the current environment, how you got there, and where you need to be.
In the past, many companies have invested millions of dollars on CICS and DB2 applications. Migration to DB2 V8 and CICS TS V3.1 provide opportunities for exploiting the interoperability of those legacy applications in the LE environment, using the new System z specialty processors, and full XML implementation.
Make sure your migration project has the full support of your IT management team. When they understand the value proposition, the importance to the business, and then communicate both to those involved in the migration project, the odds of a successful project significantly improve.
By avoiding the potholes in your LE migration plan, you position yourself to fully understand what must occur, explain why it’s required, and decide when it needs to be completed.
A clear understanding of your application portfolio will yield the necessary insight on where you are and the effort required to get you where you need to be. Once you understand where you’re going and how you intend to get there, an LE migration, a compiler migration, or a DB2 or CICS migration become a matter of executing your plan. Z