You must run the migration help function to migrate the
code of a Program, Screen, or Server generated in Pacbase. This function copies
the Pacbase COBOL
code into your workspace and generates it again locally. The COBOL
obtained after the local generation is then compared with the initial
COBOL. The migration help function sets warnings on the lines where
it detects differences. It excludes the differences in the formatting
or comments.
With the migration help function, you can verify that the Pacbase and the local generations
were identically run. For example, you can check that they were run
from the same Library/project, with all the required Macros. It draws
your attention to significant differences (local modification of the
instance design before the migration help for example) or nonsignificant
differences (difference in the generation date and time for example).
You must manage the warnings.
The migration help function completes the following actions:
- It copies the Pacbase generated .cbl file
into your local workspace. This file is copied into the COBOL target
indicated in the Definition tab. It is named
after the COBOL program ID (for Programs) or Program
external name (for Screens or Servers) indicated in the Definition.
The file is then renamed if the Pacbase file name is not
identical to the name entered in the Definition.
Note: If
you expand the instance in the Design Explorer view
after you run the migration help, you can see the COBOL target and
the name of the file that is copied by the migration help function.
- It starts the local generation. This generation takes into account
the files that are generated by MIA1 (for Programs), MIA2 (for
Screens), MIA3 (for TUI clients), or MIA4 (for
Servers). It runs the local generation and carries out the post-processing
and code reconciliation.
Note: The generated skeleton language of
the instance is identical to the Pacbase skeleton language.
This piece of information is retrieved from the extraction of the Pacbase models and from
the import.
The result of the local generation is stored
in a sandbox. Its content will not replace the content of the .cbl file
that is already copied into your workspace unless you explicitly request
it.
- It compares the Pacbase .cbl file
with the locally generated file. If it detects differences other than
a difference in formatting or comment, it set warnings. It informs
you that you must manage the warnings and remove them before you can
work on the instance.
Note: The warnings are stored in the .cblpdp file.
So if you keep the warnings and deliver the generated instance to
the server, the users who will load the instance into their own workspaces
will see them as well.
- If you started the migration help with the --validationFile parameter,
the migration help also validates the migration. It migrates the COBOL
files and automatically validates their migration if they have no
difference after the application of the validation types.
- It generates three execution reports if the migration help was
run in batch mode. These reports are generated in the folder that
is specified in the --reportFolder parameter
of the command line.
You must then look into the warnings. They are calculated
again upon each new generation, until you correct or remove them all.
You must manage all the warnings before the local file replaces the .cbl file
that is already copied into your workspace.
An information message
is displayed when you open the COBOL code of an instance that still
contains warnings.