“[debug]” on page 64
Optional parameter
“[trace]” on page 64
Optional parameter
"
Product_Code
[
Product_Version
][,
Product_CodeN
[
Product_VerN
]]..."
You must set at least one
Product_Code
parameter to identify the product or
component for which to run the prerequisite check and the associated
configuration file.
Product_Code
is the product code that you set in the
ips_root
/codename.cfg
file.
For example,
KMS
is the product code for the Tivoli Enterprise Monitoring Server in
the
product.cfg
file. To run the Scanner, enter the following script with the
product code:
./prereq_checker.sh
KMS
If you set a
Product_Code
parameter that does not have a corresponding
configuration file, the Prerequisite Scanner ignores it without error. The log file
contains a message that no configuration file was found.
The
Product_Version
parameter for the associated
Product_Code
parameter
indicates the version of the product. It is the 8-digit code to represent the version,
release, modification, and level, with two digits for each part of the code; for
example, 7.3.21 is 07032100.
Product_Version
is an optional parameter. If you do
not set it, the Prerequisite Scanner checks the latest available version.
You can set one or many
Product_Code
parameters with the optional
Product_Version
parameter, each separated by a comma.
Important:
When you set more than one
<Product_Code>
parameter with the
optional
<Product_Version>
parameter, enclose the parameters in quotation marks.
If you do not, the Scanner fails.
This example checks prerequisites for the latest version of Tivoli Monitoring
Operating System Agent for Windows and Version 6.2.1 of Tivoli Monitoring Agent
for DB2.
prereq_checker.bat
"KNT,KUD 06210000"
[detail]
This optional parameter indicates whether to display detailed results of the scan in
the command-line interface.
Important:
Do not enclose this parameter in quotation marks.
When you set the
detail
parameter, the detailed results contain:
v
The version of the Prerequisite Scanner
v
The version of the operating system on which the Scanner was run
v
The name of the products or components for which the prerequisites checks
were run
v
For each prerequisite property: the name of the prerequisite property checked,
the PASS or FAIL result, the actual value, and expected value
60
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 ...