Automatic Tool for COBOL YEAR 2000 Compliance

Portugujs Italiano Espaqol Frangais Deutsch

CCC2000 is an automatic tool, that successfully converts COBOL applications, to comply with YEAR 2000. We have a very successful implementation at ZURICH ASSURANCE in Switzerland.

CCC2000 runs on following platforms: - MVS - UNIX - Windows95/NT - OS2

The application and usage: - automatic analysis and repair of COBOL to comply with YEAR 2000 - audit of applications that are already YEAR 2000 compliant - detection of programming bugs relating to the date processing - rescue missions, etc.

There are two parts available separately or together. 1. Analyser, we believe 100% accuracy, 2. Generator, 90% accuracy, requires human verification.

The usage is extremely simple and automatic. The input is the COBOL source code and output is - a protocol, pointing out all suspects (analyser) - a generated (repaired) new source code (generator)

The processing of ca. 1000 modules on UNIX platform takes - 2-3 hours for analyser - 1-3 days for generator.

SERVICE per line of code or Time and Material can be provided.

scientific description prices contact us

ccc2000_Ltd@yahoo.com

"http://www.ccc2000.com/english.html"

-- fly .:. (.@...), May 30, 1999

Answers

You're right - just have to find 'em all, convert 'em all (perfectly), and then test 'em all.

Nothing to it.

-- Robert A. Cook, PE (Kennesaw, GA) (cook.r@csaatl.com), May 31, 1999.

Such conversion tools can be very helpful with much of the tedious work, particularly the COBOL work, which is much of what needs to be done. As for the 100% claim, place your bets. The 90% claim may be plausible with COBOL programs, but needs verification. As for non-COBOL code, it's grunt work time.

Jerry

-- Jerry B (skeptic76@erols.com), May 31, 1999.

fly, how LONG have you been reading what is posted on this forum? Do you think that, even if this tool were to work as advertised, and everyone who had COBOL code that still needed to be remediated applied it starting today, that this would actually have any significant impact??

Remember all that other stuff? Like TESTING, which takes TIME that is no longer available? Like OTHER PROGRAMMING LANGUAGES, many of which are in use on old mainframes that perform vital functions? Like all those OTHER PLATFORMS that are not supported for this tool? Like passing non-compliant data, corrupting a compliant system? Like embedded chips? Like ... ehh, you get the idea.

-- King of Spain (madrid@aol.com), May 31, 1999.

KOS:

Within its limitations, such a tool might be handy for some. It could speed up remediation of any remaining unremediated COBOL code, and might even catch a few bugs you missed in the remediated code.

Dismissing this tool because it isn't universal is silly. Kind of like saying a screwdriver is useless because it won't drill holes or pound nails or cut down trees. Do you think that the more things you can think of that a screwdriver can't do, the more useless that screwdriver becomes? Try thinking for a change.

-- Flint (flintc@mindspring.com), May 31, 1999.

I am thinking. I am thinking: Titanic with big gaping hole in the side. I am thinking of Flint with a bucket. I am thinking, "I sure am glad I'm in a life-boat, so long Flint!".

-- King of Spain (madrid@aol.com), May 31, 1999.

KOS:

I think you put your finger on the problem here. Sorry I took this for granted, but try thinking about what you're *talking* about. That way, you won't be criticizing a tool for not doing what it doesn't do, and you won't look quite so foolish.

-- Flint (flintc@mindspring.com), May 31, 1999.