![]() |
![]() |
![]() |
![]() |
![]() |
In order to illustrate all of the migration activities performed and how to use the Rehosting Workbench Cataloger to determine whether the asset is consistent and can be migrated to the target platform, the Simple Application STFILEORA will be used. STFILEORA is provided with the Rehosting Workbench set of tools.
d. Listing 2‑1 Sample Application Hierarchy
•
•
•
• It is recommended that each time you work on a project using the Rehosting Workbench to set certain environment variables that will be useful later. The only environment variable that is mandatory is REFINEDISTRIB; others can be used for simplification reasons.Table 2‑1 explains the usage of proposed variables.
Variable used by the Rehosting Workbench Listing 2‑2 Extract from Simple Application .project File:
2. Copy a sample of the configuration (system.desc, version.mk, options-catalog, etc) files from Simple Application to $PROJECT/param directory to make any necessary modifications.
3. Copy the makefile from the source (SimpleApp) into $PROJECT/source.
4. Create a file .project under $PROJECT and initialize it with variables listed in Setting Environment and Working Variables. Variables in the file are to be exported each time you work on the project.
5. Copy the prepared source files to $PROJECT/sourceListing 2‑3 System Description for Simple ApplicationListing 2‑4 Global Options File for the Simple Application
• ${REFINEDIR} is the directory where the Rehosting Workbench tools are installed.
• $(CATALOG) is the version of the Cataloger to be used
• $(SYSTEM) is the path of the system description file.From directory $LOGS/catalog execute the command:Listing 2‑5 Parsing ExamplesThe result of this step is the binary file named symtab-SampleApp.pob that represents inter-component information.Listing 2‑6 Analysis ExampleListing 2‑7 Print Reports ExampleIn the Simple Application reports are generated in $PROJECT/source/Reports-SampleApp:
Table 2‑2 Inventory Status make is a UNIX utility intended to automate and optimize the construction of targets (files or actions).We highly recommend using make to perform the different operations that compose the migration process because this enables you to:You should have a descriptor file named makefile in the source directory in which all operations are implemented (a makefile is prepared in the source directory during the initialization of a project).The following two sections describe the make configuration and how to use the Cataloger functions thru make.The version.mk configuration file in $PARAM is used to set the variables and parameters required by the make utility.Listing 2‑8 Extract From version.mk for Simple ApplicationThe contents of the makefile summarize the tasks to be performed:From the $SOURCE directory execute the command:The log file is generated in $LOGS/parseSample: parsing the program BATCH/PGMMB02.cblThe log file is generated in $LOGS/parseThe log file is generated in $LOGS/catalogFor example, if you developed you own script (report.sh) to generate a customized report based on basic cataloguing reports, place your script in $TOOLS directory.
2. Modify makefile.debug changing REAL_CMD to COMMENT