Pinned topic E-COBOL 3.4 to E-COBOL 4.2 compatibility issues
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
If we have a component compiled using E_COBOL 3.4 that calls a IBM COBOL load module ( of another application ) , are there any compatibility issues likely to be faced when we upgrade to 4.2 . Is there any application changes required in such a case
Updated on 2012-03-28T00:12:59Z at 2012-03-28T00:12:59Z by SystemAdmin
Re: E-COBOL 3.4 to E-COBOL 4.2 compatibility issues2012-02-09T17:34:16ZThis is the accepted answer. This is the accepted answer.In general, the answer is that you should have no problems. Of course, there's always 'Standard Answer No.1' that starts with, "But..."
For the best migration information, I would strongly suggest that you look over the "COBOL Migration Guide" GC23-8527-01. You can find this manual and all the other pubs at:
Re: E-COBOL 3.4 to E-COBOL 4.2 compatibility issues2012-02-09T18:11:27ZThis is the accepted answer. This is the accepted answer.We recently went through the upgrade of Enterprise COBOL 3.4.1 to Enterprise COBOL 4.2 without incident. We have modules compiled with Enterprise COBOL 4.2 calling other modules compiled with any number of previous compilers, back to and including VS COBOL II.
As Carl indicates, the migration manual is your friend.
PavankumarM 270004HUV16 Posts
Re: E-COBOL 3.4 to E-COBOL 4.2 compatibility issues2012-02-10T13:50:09ZThis is the accepted answer. This is the accepted answer.Carl/Craig
Thanks for your prompt response.Wanted to check if you found an overall improvement in performance and reduced MIPS consumption by migrating to E-COBOL 4.2
Re: E-COBOL 3.4 to E-COBOL 4.2 compatibility issues2012-02-10T15:24:14ZThis is the accepted answer. This is the accepted answer.
- PavankumarM 270004HUV1
1) Review the COBOL compiler compile options that you are using. You should look at each program and not assume that some installation standard has always been used. Despite best intentions, this is often not the case. Also check the LE run-time options you are using. Most COBOL users have just assumed that IBM's defaults are OK and this may or may not be a valid assumption. And, because run-time options can be overridden at the run unit level, be sure you know if you have any overrides in place. If you have a CEEUOPT CSECT in your load module, there are LE run-time overrides.. Personally, I would start with the LE Storage Report as a run-time option tuning opportunity. And, then tune the storage use with an override.
2) Along with the above, you should download the "Enterprise COBOL Version 4 Release 2 Performance Tuning" manual from the IBM Web site. You can find it at:
Re: E-COBOL 3.4 to E-COBOL 4.2 compatibility issues2012-03-28T00:12:59ZThis is the accepted answer. This is the accepted answer.
- PavankumarM 270004HUV1
The exception to this is programs with Unicode (USAGE NATIONAL) data, they will have a significant performance improvement.
COBOL is the Language of the Future!