Re: Enterprise COBOL "INITCHECK"

INITIALIZE OUTPUT-RECORD (followed by code which MOVEs values to each field in OUTPUT-RECORD) INITIALIZE PRINT-LINE MOVE HEADING-LINE TO PRINT-LINE MOVE SPACE TO SAVE-INPUT-RECORD MOVE INPUT-RECORD TO SAVE-INPUT-RECORD INITIALIZE INPUT-RECORD-AREA READ INPUT-FILE I think with V5+ the optimizer

Re: Enterprise COBOL "INITCHECK"

Init then target? That would be a natural use. Init then source? That would be an error. On Sat, Oct 8, 2016 at 4:00 AM, Bill Woodger wrote: > Yes, so far looks good. Need to see documentation. > > Waiting for its counterpart, INITSTUPID, for where data is initialised,

Re: Enterprise COBOL "INITCHECK"

On 8 Oct 2016, at 11:01, Bill Woodger > wrote: Yes, so far looks good. Need to see documentation. Waiting for its counterpart, INITSTUPID, for where data is initialised, and then next reference is as a target. Excellent idea! :) I'll vote

Re: Enterprise COBOL "INITCHECK"

Yes, so far looks good. Need to see documentation. Waiting for its counterpart, INITSTUPID, for where data is initialised, and then next reference is as a target. -- For IBM-MAIN subscribe / signoff / archive access

Enterprise COBOL "INITCHECK"

This could be quite a useful new feature: "The compiler is changed to add a new compiler option: INITCHECK, which tells the compiler to try and locate uses of data items that have not been set yet. The compiler is changed to add a new compiler option: INITCHECK". V6.1: