By experimentation, V5.2 cannot perform INITCHECK at any OPT level even with REGION=1536M (the largest region I am allowed to use here) for very large programs (30K+ lines actual code). It does succeed at OPT(1) and OPT(2) for more reasonably-sized programs (less than 6K lines) with REGION=350M.
I will check out those videos, thanks. As for IBM's "thinking" on this subject, maybe PFCSK syndrome? Insufficient real-world experience? Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Woodger Sent: Friday, January 27, 2017 12:33 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL V5.2 question: INITCHECK option incompatible with OPTIMIZE(0)? (Msg IGYOS4021-W) "Actually, Tom Ross in his migration presentation recommends this procedure:..." Yes, unfortunately that was May 2016, and INITCHECK appeared in September 2016. The reference I was making was to the V6.1 Migration Guide. The advice seems not to be in the MG for V5.2, although INITCHECK is there. With V6.1, the compiler "back end" uses 64-bit addressing, allowing larger programs (which are generally "generated" programs) to be optimised than with V5.2. The only reason it is V6, not V5.3, is because of this change. Have a look at Youtube for Enterprise COBOL V6.1. There's an Introduction, which is only two weeks old, and a two-month old "Migration Assistant" video. I've not seen either yet... If it were easy to use INITCHECK with OPT(0), but the compile would take longer, why didn't they just do it? It's a migration and perhaps "initial compile" thing? If it takes longer, it is then your choice to use it or not. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
