Related concepts
:
Writing messages to log files is disabled by default on UNIX systems. You can
enable debugging or tracing functions by using the
debug
and
trace
input
parameters. The Scanner writes the debug and trace data to different log files and
uses timestamps to flag the start and end times of steps or functions. You can use
both files to correlate and troubleshoot a specific issue, function, or prerequisite
check.
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.
The
prereq_checker
script runs the IBM Prerequisite Scanner and checks for
prerequisites based on the set of parameters that you specify when you run the
script.
Return codes
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.
Prerequisite Scanner generates return codes based on a set of defined outcomes as
follows:
Return code
Description
0
Returns
0
when Prerequisite Scanner runs
successfully and all scan results are
PASS
.
1
Returns
1
when Prerequisite Scanner runs
successfully, but one or many prerequisite
checks return
FAIL
.
2
Returns
2
when Prerequisite Scanner does
not run successfully, and must exit because
of an error categorized as follows:
v
Script usage errors
v
Collector errors
v
Other errors
Script usage errors
Prerequisite Scanner can exit because of any of the following usage errors when
running the script:
v
The
Product_Code
input parameter is not valid; for example, it was not found or
is not a supported format.
v
The pattern for the
Product_Code
and
Product_Version
input parameters is not
valid; for example, more than just code and version are provided within
quotation marks, or the pattern is not enclosed by quotation marks.
v
The
Product_Version
input parameters is not valid; for example, the product
version is not all numeric characters.
v
No input parameters were entered in the command-line interface.
v
The syntax was incorrect when entered in the command-line interface; for
example, a non-supported command-line argument was entered.
v
No required
Product_Code
input parameter was entered.
72
Prerequisite Scanner: User's Guide
Summary of Contents for Prerequisite Scanner
Page 1: ...Prerequisite Scanner Version 1 1 1 10 User s Guide ...
Page 2: ......
Page 3: ...Prerequisite Scanner Version 1 1 1 10 User s Guide ...
Page 8: ...vi Prerequisite Scanner User s Guide ...
Page 10: ...viii Prerequisite Scanner User s Guide ...
Page 40: ...Figure 6 result txt file on Windows systems 30 Prerequisite Scanner User s Guide ...
Page 46: ...36 Prerequisite Scanner User s Guide ...
Page 68: ...58 Prerequisite Scanner User s Guide ...
Page 78: ...Figure 11 precheck log file with the debug data 68 Prerequisite Scanner User s Guide ...
Page 84: ...74 Prerequisite Scanner User s Guide ...
Page 88: ...78 Prerequisite Scanner User s Guide ...
Page 92: ...82 Prerequisite Scanner User s Guide ...
Page 116: ...106 Prerequisite Scanner User s Guide ...
Page 122: ...112 Prerequisite Scanner User s Guide ...
Page 136: ...126 Prerequisite Scanner User s Guide ...
Page 138: ...128 Prerequisite Scanner User s Guide ...
Page 140: ...130 Prerequisite Scanner User s Guide ...
Page 158: ...148 Prerequisite Scanner User s Guide ...
Page 164: ...154 Prerequisite Scanner User s Guide ...
Page 166: ...156 Prerequisite Scanner User s Guide ...
Page 170: ...160 Prerequisite Scanner User s Guide ...
Page 171: ......
Page 172: ... Printed in USA ...