Potential Problem 1: The first program that migrated used
a print form so the migration tool migrated to the print statement.
Another program uses the same function, but with a text form.
Solution 1: Use VisualAge Generator Compatibility
mode. Edit the function and change the print statement to a display
statement.
Potential Problem 2: A problem arises if you want to
eliminate the use of VisualAge Generator Compatibility mode and two programs
use the function -- one with a text form and one with a print form.
Possible Solution 2A: If a specific target environment
always uses display maps and other environments always use print maps, you
could change the EGL function to something similar to the following:
if (sysVar.systemType is zoscics)
DISPLAY_FUNCTION();
else
PRINT_FUNCTION();
end
where DISPLAY_FUNCTION and PRINT_FUNCTION use the display and print
statements, respectively.
Possible Solution 2B: Assuming the function migrated to a
display statement, change the function from the following:
before-logic
display textForm;
after-logic
to the following:
before-logic-function();
display textForm;
after-logic-function();
Putting the before-logic and after-logic into separate functions enables
you to keep most of the logic in common functions. Then you can make a
copy of the modified display function and change it to use print map, but
still use the common before-logic-function and after-logic-function.
Disadvantage: This has the potential to ripple back into functions that
use the original DISPLAY function.
|