Output To The Command-Line Interface On - IBM Prerequisite Scanner User Manual

Figure 2. Output to the command-line interface on UNIX systems
Prerequisite Scanner generates returns codes dependent on the results of the scan
and whether it must exit because of errors. These return codes are written to the
log files. For example, if the Prerequisite Scanner fails to run the scan because
cannot read the configuration file, it generates return code of 2.
Collating memory and disk space prerequisite properties
You can run Prerequisite Scanner to simultaneously check for the prerequisites of
one or many products or components, when you specify multiple product codes as
input parameters. Prerequisite Scanner collates the results of memory and disk
space prerequisite checks in the following collated sections of the output, if the
associated prerequisite properties have been specified in the configuration files:
v On UNIX systems, in the TOTAL ALL SPECIFIED COMPONENTS section
v On Windows systems, in the ALL COMPONENTS section
The general prerequisite properties are as follows:
v Total amount of physical memory that is currently available in the target
v Disk space of the file systems for the following prerequisite properties:
Note: If opt, usr, and var have not been defined as file systems on the target
computer, Prerequisite Scanner does not display the expected values and returned
results for these prerequisite properties in the collated section.
Prerequisite Scanner displays N/A (non applicable) in the collated section, if any of
the memory or disk space prerequisite properties do not exist in the configuration
files.
Debugging log file output on Windows systems
Prerequisite Scanner outputs processing information, warning and error messages,
and the scan results in the ips_output_dir/precheck.log file. When you run the
26
Prerequisite Scanner: User's Guide
environment, that is:
Memory
– os.space.home
– os.space.opt
– os.space.tmp
– os.space.usr
– os.space.var