First thing I checked when the compile issues first appeared was to
check the loadlib's luckily they all are PDS/E's :)
I hate to assume all the V6 testing that was done before I was handed
this.... uncovered most of these issues.
I'm gonna try and research as much as I can so I can be prepared for any
issues that arise this year, then, I'll pass the baton :)
thanks Dave
Carmen
On 1/11/2022 11:23 AM, Dave Jousma wrote:
On Tue, 11 Jan 2022 11:18:55 -0600, Dave Jousma<[email protected]> wrote:
There might still be reason for a level of panic.....
COBOL V6 required PDS-E load libraries. If you are already PDSE everywhere,
then no issue. Not hard to convert, but disruptive.
CPU to compile COBOL V6 goes up exponentially.....So if CPU is constrained,
could be an issue.
There are many new features introduced in COBOL V6. Many have hold actions to
have the enabling LE support for those functions in all environments BEFORE
rolling out the COBOL PTF, otherwise you may see errors in prod.
I should have also added that we did have some application code changes to make too.
There are also some "rules" about mixed run-units (i.e. mixture of cobol
versions, assembler, etc in same run unit).
We are only a few shorts months away from EOS for V4.2.
----------------------------------------------------------------------
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
