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

Changing the translator parm from COBOB2 to COBOL3

What is the impact of not changing the translator parm to COBOL3 from COBOL2?

We are using COBOL for OS/390 2.1.2 and CICS translator 5.3.0. We have found that we have some purchased software that includes pretranslated procedure division copybooks. When using the COBOL3 parm, several fields are no longer inserted into working storage. DFHEIV0 is needed for the pretranslated copybooks.

We are planning on upgrading to Enterprise COBOL 3.2, probably in the third quarter. Are the impacts any different?

I must confess that COBOL is not my favorite area of expertise. You might be better off asking this question to my Language Environment chum on the Web site. All the info about changing COBOL compiler levels is documented in the (exhaustive) Language Environment manuals.

Two things, however, spring to mind. The first is that you cannot mix the levels of COBOL in a given compilation. If your copybooks are translated assuming a given CICS translator setting, then that's the one you have got to use for the rest of the module.

The second is that if you move to the latest level of the Enterprise COBOL compiler band CTS 2.2, you can use the integrated translator and not bother about having copybooks pretranslated. You also get the correct line numbering for such an item as well.

My understanding that the COBOL2 translator option and the COBOL3 option do not have any prereq upon the COBOL language for the code, so changing up the level should not have any drastic effects.

Robert Harris
CICS Technical Strategist -- CICS expert at Search390.com

Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .VO7aaqqaAFk.0@/search390>discussion forums.

Dig Deeper on IBM system z and mainframe systems

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.