In this wizard, you can change the colors of the lines
in the COBOL code. You can also use this wizard to ignore some differences
in the COBOL compare editor and to manage the control of the subfunctions
nesting levels.
- Generated code color settings
- Click the color rectangles that represent the foreground and background
colors of the Pacbase generated
lines, when they are viewed through the PDP COBOL editor.
Clicking
the color rectangles opens a palette where you can select colors.
- Macro color settings
- Click the color rectangles that represent the foreground and background
colors of the Pacbase Macro
lines in the generated program, when these lines are viewed through
the PDP COBOL
editor.
Clicking the color rectangles opens a palette where you
can select colors.
- Micropattern color settings
- Click the color rectangles that represent the foreground and background
colors of the lines that are generated from micropattern insertions,
when these lines are viewed through the PDP COBOL editor.
Clicking
the color rectangles opens a palette where you can select colors.
- Function color settings
- With this option, you can differentiate the colors of the start
and end tags of the Pacbase functions
and subfunctions in the specific code and the code from the Macros.
This option applies to the PDP COBOL
editor.
If this option is selected, you can click the color rectangles
that represent the text color of the tags. In the palette that opens,
you can select a new color. Moreover, you can specify whether the
text is to be displayed in bold.
If this option is not selected,
the tags are displayed like the other lines.
- COBOL comparison
- The following preferences filter the differences that are displayed
in the COBOL compare editor of Rational® Developer
for System z® and Rational Developer for AIX® and Linux. They apply when the compare editor opens
but they can be modified for each comparison from the editor contextual
menu.
- Ignore comments: This option only applies
to the display of the migration differences. If it is selected (default
value), the differences in the comments are not flagged. If you change the selection of this option in the contextual
menu of the compare editor, you must close and open the editor again
to take the modification into account. Moreover, this modification
is saved and changes the default preference.
- Ignore EXIT: If this option is selected
(default value), the differences in the presence or absence of the EXIT statements
after the tags are not flagged in the compare editor. Changing the
selection of this option in the compare editor immediately modifies
the display of the differences. However, it does not modify the default
preference.
- Ignore END-EXEC format: If this option
is selected (default value), the formatting differences of the END-EXEC statements
are not flagged. In Rational Programming Patterns, the END-EXEC statements
are always generated on continuation lines. It is not always the case
in Pacbase. This
formatting difference applies to the Macro code, the generated code,
and the specific code. You can choose to ignore these differences. If you change the selection of this option in the contextual
menu of the compare editor, you must close and open the editor again
to take the modification into account. Moreover, this modification
is saved and changes the default preference.
- Ignore micropattern id: If this option
is selected (default value), the differences in the internal identifiers
of micropatterns are not flagged in the compare editor. These identifiers
are automatically added upon generation according to the order number
of the micropattern calls in the code. They are displayed as id=n (where n is
the order number of the micropatterns call). This n number
is carried over to the generated lines of the micropattern, from column
73. In this case, non-significant zeros are added to it so that it
is displayed on 6 characters.
Differences in micropattern identifiers
can be flagged in the compare editor by the migration help because
these identifiers are generated in Rational Programming Patterns but not
in Pacbase. Differences
can also occur in a COBOL code that comes from two streams.
Changing
the selection of this option in the contextual menu of the compare
editor immediately modifies the display of the differences. However,
it does not modify the default preference.
- Structure checking before generation management
- This preference enables or disables the checking of the subfunctions
nesting levels before a Program, Screen, or Server is generated. The
following options are available:
- Enable label structure checking before generation.
This option is the default option. If the checking detects errors
in the subfunctions nesting levels, it blocks the generation.
- Enable label structure checking before generation (trace
mode). If the checking detects errors in the subfunctions
nesting levels, it blocks the generation. A log file
is generated in the temporary directory to enable you to analyze the
errors. If you cannot correct some errors, send this log file
to the support.
- Disable label structure checking before generation
(trace mode). The checking is completed but it does not
block the generation if it detects errors. The generated COBOL code
can then contain errors. A log file is generated
in the temporary directory to enable you to analyze the errors. The
use of this option is not advised. It must be restricted to the particular
case where errors can be corrected by a new generation.
- COBOL syntax for type 3 (UNIX, Windows) certified as compatible
with IBM COBOL for AIX syntax
- This option applies to the COBOL files that were generated with
a type 3: UNIX, Windows and transformed by
the transform.txt file upon the migration to
become compatible with the IBM® compiler.
You
must select this option to restore the syntactic control of their
COBOL code.