If I recall, I head some issues when folks started moving to COBOL V5?
or maybe it was V6, I'm not sure. most of what I read were these same
issues, something I need to pass on to my team before anyone decides
this is the way to go before application testing.
thank you Tom
On 1/12/2022 2:51 PM, Tom Ross wrote:
Well I just inherited COBOL support and our programmers have been trying to=
debug an issue with CICS COBOL, seems Ent COBOL V4 was still being used in=
CICS TS 5.4. the tool used is Endeavor, long story short, V6 was being tes=
ted in some processes but never updated in others.=20
my question is mostly a sanity check, from what I've read the DB2 pre compi=
ler and the CICS translators are no longer needed, COBOL parms and options =
are now used if these are DB2 or CICS programs ?
this is valid ?
You can still use the separate Db2 precompiler and CICS translator!
In fact, migrating to the new integrated method is not always easy, so I
would not recommend moving to a new compiler AND a new precompile/translate
process at the same time! We often see issues with the Db2 precompiler
allowing things that should not have been allowed, like text after END-EXEC
or literals longer than 160 bytes, and these won't work with the integrated
SQL coprocessor (COBOL SQL compiler option).
Cheers,
TomR >> COBOL is the Language of the Future! <<
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email [email protected] with the message: INFO IBM-MAIN
--
/I am not bound to win, but I am bound to be true. I am not bound to
succeed, but I am bound to live by the light that I have. I must stand
with anybody that stands right, and stand with him while he is right,
and part with him when he goes wrong. *Abraham Lincoln*/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
