What the Tools Do

This tasks in this chapter make use of four tools: prepare, analyzer, fscanner, and fnlookup.

prepare is a "front-end" to analyzer.
It identifies files that are likely to require analysis by the analyzer tool, and, optionally, invokes analyzer to process the resulting list(s) of files.

analyzer scans an ASCII file — shell script, makefile, source file, or text file — and identifies pathnames, commands, system calls and library routines that may not work correctly on 10.x.

Optionally, it creates a copy of the file, substituting 10.x absolute pathnames for 9.x absolute pathnames (but not attempting to change commands or system calls).




	: The tools never modify the original file. But `prepare` will, at your option, create files, and may also slow your system down while it's executing. Pathnames constructed by variable substitution will not be caught.

When analyzer finds a potential problem, such as a command whose options have changed, it writes a comment into the new (copied) file, or into a log file, or both. The comment indicates the nature of the problem and provides a unique reference to a text paragraph that describes the problem fully. (You can choose to have analyzer write out the paragraph to the log file.)

fscanner finds and evaluates ASCII strings in file or group of files.
If you use the analyzer keyword, fscanner will display all of the messages that analyzer has added to a converted file. fscanner has a graphical user interface similar to the elm mailer.
fnlookup maps 9.x absolute pathnames to 10.x absolute pathnames.

For complete descriptions of these tools, their options, and their output, refer to the prepare(update_aid), analyzer(update_aid), fscanner(update_aid), and fnlookup(update_aid) manpages.

What the Tools Don't Do

prepare and analyzer are aids to conversion, and they will make the process go more easily and quickly, but they are not a "black box" into which you can put your code and have it come out guaranteed to work on 10.x.

They will catch known incompatibilities between the HP-UX 9.x and 10.x "core" operating systems — the commands, utilities and libraries that comprise the basis of HP-UX. This "core" does not include all of the subsystems commonly bundled with HP-UX; for example, not all networking services are covered, and changes to the graphics and X libraries are not covered (see the Release Notes for HP-UX 10.10 for information on these subsystems). To get an idea of what is covered and what is not, you may want to look at the "databases" (actually ordinary text files) that prepare and analyzer use; if you've loaded the tools onto a 9.x system, look at /upgrade/lib/CMDS_DB and /upgrade/lib/LIBS_DB.

Use the tools in this package in conjunction with the Release Notes for HP-UX 10.10, and with your normal regression-testing and certification procedures, to get code and scripts ready to run on 10.01.

What the Tools Do

Technical documentation

» Table of Contents

What the Tools Don't Do