Q
Problem solve Get help with specific problems with your technologies, process and projects.

Any reason why we shouldn't write CICS transactions in Java vs COBOL?

What's the case for using COBOL instead of Java and vice versa? Find out here.

We are starting new development project based on CICS: - clients are written in Java - server components must be...

implemented inside the CICS - current release of operating system is z/OS v1.0

System will be highly loaded by significant number of concurrent users. According to manuals, there is no problem if we write CICS transactions in Java (using HPCJ). Since we don't have practical experience our questions are:

Is there any reason why we shouldn't write CICS transactions in Java (why use COBOL instead of Java)?

What are practical experiences (performance and stability) of highly loaded system based on CICS transactions written in Java?


You do not say but I deduce from the fact that you are proposing to use HPCJ that you will be deploying your Java programs on CICS TS V1.3, at least initially. In that case you should be aware that Java is, as yet, an immature technology compared to COBOL. It is therefore to be expected that it will not perform as well as COBOL.

In terms of a ballpark figure we would expect the instruction pathlength for a typical COBOL transaction, which we think of as around 1M instructions, to be increased by a factor of 2 or 3 by rewriting it in Java. We confidently expect that number to improve over time and it can indeed be improved upon by using hot-pooling in CICS TS V1.3. But Java, or indeed any object oriented language, will always carry a significant overhead compared with COBOL.

One approach is to write the crucial, heavily used programs in COBOL, especially if they will access DB2, and write the less performance critical parts of the application in Java. This will provide you with the thoughput you need at lower CPU cost, allows you to gain experience with Java and reduces the effort should you want to change to pure Java at some time in the future.


This was last published in February 2002

Dig Deeper on IBM system z and mainframe systems

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchWindowsServer

SearchServerVirtualization

SearchCloudComputing

Close