Neither. It is bad code which now causes something else to happen. On Tuesday, 5 April 2016 01:35:37 UTC+1, Paul Gilmartin wrote: > On Mon, 4 Apr 2016 19:08:08 -0500, Mike Schwab wrote: > > >https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ceea100/ceea1mst83.htm > > > > > >On Mon, Apr 4, 2016 at 7:01 PM, Cameron Conacher wrote: > >> We need up turning off optimization and the program compiled. > >> We are now seeing some coding issues. We have programs that SET INDEX-ITEM > >> UP BY +1 where the value would would be larger than the OCCURS clause > >> defined. Resulting in 0C7. > >> We do not see this with previous versions if COBOL. > >> > The question then becomes, is this a new bug in the compiler, or improved > error checking discovering a long-standing error in the user's program? > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
