The table below describes the Component Maker Document extraction options.
| Option | Language | Description |
|---|---|---|
| Comment-out Sliced-off Legacy Code | COBOL, RPG | Retain but comment out unused code in the component source. In the Comment Prefix field, enter descriptive text (up to six characters) for the commented-out lines. |
| Emphasize Component/Include in Coverage Report | COBOL, Natural, PL/I, RPG | Generate a Interactive Analysis list of sliced constructs and colorize the constructs in the Coverage Report. |
| Generate Audit Report | COBOL | Generate an audit report. |
| Generate Support Comments | COBOL, RPG | Include comments in the component source that identify the component properties you specified, such as the starting and ending paragraphs for a structure-based COBOL component. |
| Include Reason Codes | COBOL | Include reason codes in the audit report explaining why a line was changed or deleted.
Note: Generating reason codes is very memory-intensive and may cause crashes for extractions from large programs.
|
| List Options in Component Header and in Separate Document | COBOL, RPG | Include a list of extraction option settings in the component header and in a separate text file. The text file has a name of the form <component>.BRE.options.txt. |
| Mark Modified Legacy Code | COBOL, RPG | Mark modified code in the component source. In the Comment Prefix field, enter descriptive text (up to six characters) for the modified lines. |
| Print Calculated Values as Comments | COBOL | For domain-based component extraction only, print the calculated values of variables as comments. Alternatively, you can substitute the calculated values of variables for the variables themselves. |
| Use Left Column for Marks | COBOL, RPG | Place the descriptive text for commented-out or modified lines in the lefthand column of the line. Otherwise, the text appears in the righthand column. |