|
 |
HP STKs online
(documents only)
|
|
|
|
|
|
|
The
STK file scanners detect coding issues that may require attention in
porting to HP-UX 11i systems. The STK file scanners provide
functionality to:
- Support C, C++, Fortran, COBOL, scripts, and makefiles
- Help assess the porting effort
- Identify specific lines of source code that cause problems
- Generate impact statements describing the porting problems and offering advice on how to solve them
There
are several variants of the STK to help you migrate to HP-UX 11i from
Tru64 UNIX, Linux, Solaris, or older versions of HP-UX.
|
The scanwizard utility assists you in generating a custom detailed report (using
the scandetail utility) or summary report (using the scansummary
utility). This is an interactive command-line wizard and it is recommended
for new users accessing the STK file-scanning technology.
To run scanwizard,
enter:
/opt/STK/bin/scanwizard
» View an example of the scanwizard utility as it steps you through the process.
The scandetail report (either stk_detail.html or stk_detail.txt) gives detailed information for each occurrence of an identifier type. This report provides the following information:
- File name and line number associated with each impact
- Identifier type (functions, header files, and others)
- Problem synopsis and ID
- Impact information
To run scandetail for all files, enter:
/opt/STK/bin/scandetail -r <directory/filename>
See the example reports for stk_detail.html or stk_detail.txt included here.
The scansummary report (either stk_summary.html or stk_summary.txt, indicates which API impacts occur for each line of your source files. It provides the following information:
- Number of and types of API transition impacts
- Identifier type (functions, header files, and others)
- Problem synopsis
- Impact information
To run scansummary for all files, enter:
/opt/STK/bin/scansummary -r <directory/filename>
See the example reports for stk_summary.html or stk_summary.txt included here.
The impact statements identify specific application migration issues between
source and destination platforms, and provide solutions or references
to more information to resolve the issues.
» View the example
Each impact statement contains the following information:
-
Type and severity (critical or non-critical)
-
Problem description
-
Identifiers
-
Old behavior
-
References to manpages for the source platform
-
Solution description
-
New behavior
-
References to manpages for the target platform
The possible impact types are:
- unavailable
- changed
- non-standard
- warning
- enhancement
- obsolete
Note that not all types are used in each STK.
» Back to Tools & Reports
» Back to tutorial home
|
