News
Abstract
IBM® Prerequisite Scanner Versions 1.2.0.3 to Version 1.2.0.12 provide enhancements, including new and modified prerequisite properties and configuration files. It also contains fixes for defects and service requests, previously known as PMRs.
Content
Tab navigation
Fix pack enhancements: 1.2.0.11 | 1.2.0.10 | 1.2.0.9 | 1.2.0.8 |1.2.0.7 | 1.2.0.6 | 1.2.0.5 | 1.2.0.4 | 1.2.0.3
Enhancements in Version 1.2.0.11
Ability to display a shortened version of the Prerequisite Scanner scan results
Prerequisite Scanner introduces the -s option with the detail input parameter that you can specify to output the shortened results to the command window, displaying the overall result and any prerequisite properties with FAIL or WARN results.
Ability to check the version of Prerequisite Scanner
Prerequisite Scanner introduces the version input parameter that you can specify by itself to output the tool's version and build ID to the command window.
Support for Tivoli Process Automation Engine
Prerequisite Scanner enhances support for Tivoli Process Automation Engine Version 7.6. It includes new PAC and PRX product codes and the configuration files for the version in the ips_root/UNIX_Linux and ips_root/Windows directories.
Support for CentOS Linux
Prerequisite Scanner now supports checking for the CentOS operating system.
Support for IBM Tivoli® Netcool/Impact Version 7.1
Prerequisite Scanner includes the configuration file for Tivoli Netcool/Impact Version 7.1.
Documentation changes in this modification
The Prerequisite Scanner collection that is published to IBM Knowledge Center is not updated for Version 1.2.0.11.
A Quick Start Guide is also available for download. To obtain the Quick Start Guide in different languages, access the PDF files from the Translated IBM Prerequisite Scanner Version 1.2.0.12 Quick Start Guide document
Fixed defects
For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.
Known issues
For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.
Enhancements in Version 1.2.0.10
No enhancements in this fix pack except for 3 new properties.
Documentation changes in this modification
The Prerequisite Scanner collection that is published to IBM Knowledge Center is not updated for Version 1.2.0.10.
A Quick Start Guide is also available for download. To obtain the Quick Start Guide in different languages, access the PDF files from the Translated IBM Prerequisite Scanner Version 1.2.0.10 Quick Start Guide document.
Fixed defects
For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.
Known issues
For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.
Enhancements in Version 1.2.0.9
Support for alternative home location for the configuration files
Prerequisite Scanner now allows users to set the home location of their product's configuration files, by specifying the location with the configHomeDir input parameter when they run the tool from the command line. If this optional input parameter is not set, the tool uses the configuration files from the default locations, the ips_root/UNIX_Linux and ips_root/Windows directories.
Support for Tivoli Netcool Configuration Manager
Prerequisite Scanner introduces support for Tivoli Netcool Configuration Manager Versions 6.4.0 and 6.4.1. It includes a new NCM product code and the configuration files for these versions in the ips_root/UNIX_Linux directory. It also includes a convenience script, ips_root/NCM.sh, to run the scan for Tivoli Netcool Configuration Manager. This script prompts you to choose which components to run the scan for, and automatically sets the environment variables that determine the set of prerequisite properties to check.
Support for Tivoli Network Manager
Prerequisite Scanner introduces support for Tivoli Network Manager Version 3.9. It includes a new TNM product code and the configuration files for these versions in the ips_root/UNIX_Linux and ips_root/Windows directories.
Support for IBM Tivoli Provisioning Manager Version 7.2.2
Prerequisite Scanner includes the configuration files for Tivoli Provisioning Manager Version 7.2.2.
Documentation changes in this modification
The Prerequisite Scanner documentation will be updated for Version 1.2.0.9, but it will be published in IBM Knowledge Center after GA.
Fixed defects
For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.
Known issues
For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.
Enhancements in Version 1.2.0.8
Severity levels for prerequisite properties
Prerequisite Scanner provides a set of severity levels for its prerequisite properties. A severity level represents an attribute of the prerequisite property that Prerequisite Scanner uses to flag how critical the prerequisite property is to the success of a product's or component's installation or runtime environment. If a prerequisite property has a warning severity and the scan returns a WARNING result, the overall scan result is WARNING; unless another prerequisite property has a FAIL result and then the overall result is FAIL. The product's or component's installation can continue when the overall scan result is WARNING; however, the product's or component's performance and the runtime environment might be impacted by the associated missing or incorrect prerequisite.
A prerequisite property can have a severity level of WARNING. It must be explicitly specified for the prerequisite property in the configuration file, unless the prerequisite property supports a range for the expected value and a range is specified. When a supported prerequisite property has an expected value range, the warning severity level is implicit. The list of prerequisite properties that have been updated in Version 1.2.0.8 to support expected value ranges are as follows:
- db2.home.space
- Disk for all platforms
- intel.cpu
- Memory
- risc.cpu
- Temp
- os.availableMemory
- os.RAMSize
- os.space.dir_name
- os.space.dir_name_nonroot
- os.space.dir_name_root
- os.swapSize
- os.totalMemory
- os.totalPhysicalMemory
For examples of expected value ranges for these prerequisite properties, see the Modified prerequisite properties in Fix Pack 8 section in the Modified prerequisite properties tab.
For example, by setting the following prerequisite property in a configuration file, the prerequisite check returns a WARNING result if the number of logical processors on the target machine is less than 4. The overall result is WARNING, unless there is a FAIL result for another prerequisite property.
numLogicalCPU=[sev:WARNING]4
Important: By default, all prerequisite properties have severity level of FAIL. It is implicit and is not specified for the prerequisite properties in the configuration files.
Globalization support
Prerequisite Scanner output and messages have been translated into the following languages: Brazilian Portuguese, Czech, French, German, Hungarian, Italian, Japanese, Korean, Polish, Simplified Chinese, Spanish, and Traditional Chinese. The translated messages files are located in the /nls subdirectory after you have extracted the contents of the platform-specific Prerequisite Scanner installation packages.
Serviceability
Prerequisite Scanner provides message IDs, prefixed with CTGPR, and improved text for its error, warning, and informational messages.
Support for Jazz for Service Management Version 1.1.0.2
Prerequisite Scanner includes the configuration files for Jazz for Service Management Version 1.1.0.2, including Dashboard Application Services Hub Version 3.1.0.2 and Tivoli Common Reporting Version 3.1.0.2.
Support for IBM Tivoli® Integrated Portal Version 2.2.0.13
Prerequisite Scanner includes the configuration file for Tivoli Integrated Portal Version 2.2.0.13.
Documentation changes in this modification
The Prerequisite Scanner Information Center is not updated for Version 1.2.0.8.
Fixed defects
For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.
Known issues
For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.
Enhancements in Version 1.2.0.7
Support for Jazz for Service Management Version 1.1.0.2
Prerequisite Scanner provides initial support by using the same set of 1.1.0.1 configuration files for Jazz for Service Management Version 1.1.0.2, including Dashboard Application Services Hub Version 3.1.0.2 and Tivoli Common Reporting Version 3.1.0.2.
Documentation changes in this modification
The Prerequisite Scanner Information Center is not updated for Version 1.2.0.7.
Fixed defects
For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.
Known issues
For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.
Enhancements in Version 1.2.0.6
New information message for user environment variables
Detailed results of the scan now contain an information message that specifies the environment variables associated with section evaluation in the configuration files of the scanned products or components: Environment Variable Settings: [Environment_Variable_Name=Environment_Variable_Value,Environment_Variable_Name=Environment_Variable_Value, ..]
- Environment_Variable_Name is the name of the environment variable.
- Environment_Variable_Value is the value that was set for the environment variable, or [Not_Found] if no value has been set.
New check for corrupted configuration files that contain CTRL-M characters
Prerequisite Scanner Version 1.2.0.6 checks whether the configuration files are corrupted because CTRL-M characters exist in the files. If the tool detects CTRL-M characters in a configuration file, the corruption is temporarily handled during parsing to allow the tool to complete the scan. After the scan is run, the tool displays a message that the configuration file is corrupted. The user needs to fix the corrupted file before the scan is run again.
Removal of the restriction associated with for reserved keyword in product code values in the codename.cfg file
Before Version 1.2.0.6, the use of the for keyword was restricted because it impacted how Prerequisite Scanner ran. The restriction has now been removed.
Addition of Prerequisite Scanner configuration files for component verification testing
A new CVT product code and the CVT_01010000.cfg configuration files for each platform have been added to allow the Prerequisite Scanner team to run component verification testing.
Support for IBM® Security Directory Server Version 6.3.1
Prerequisite Scanner includes the configuration file for IBM Security Directory Server Version 6.3.1.
Documentation changes in this modification
The Prerequisite Scanner Information Center is not updated for Version 1.2.0.6.
Fixed defects
For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.
Known issues
For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.
Enhancements in Version 1.2.0.5
New disk space prerequisite
Prerequisite Scanner 1.2.0.5 now checks whether the target system has sufficient disk space to run the tool. If the tool detects that there is insufficient disk space, it displays an error message and exits.
Removal of Bash shell as a prerequisite
Prerequisite Scanner no longer requires Bash shell to be installed on the target system.
Support for IBM Tivoli® Monitoring Version 6.3
Prerequisite Scanner includes configuration files for IBM Tivoli Monitoring Version 6.3.
Support for IBM Tivoli Application Dependency Discovery Manager Version 7.2.2
Prerequisite Scanner includes configuration files and convenience scripts for IBM Tivoli Application Dependency Discovery Manager Version 7.2.2. The convenience scripts are in the ips_root/TADDMScripts directory.
Support for IBM Tivoli Workload Scheduler Version 9.1
Prerequisite Scanner includes configuration files, convenience scripts, and native scripts for IBM Tivoli Workload Scheduler Version 9.1. The convenience and native scripts are in the ips_root/TWSScripts directory.
Documentation changes in this modification
The Prerequisite Scanner Information Center is not updated for Version 1.2.0.5.
Fixed defects
For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.
Known issues
For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.
Enhancements in Version 1.2.0.4
Enhancements to support Jazz for Service Management Version 1.1.0.1
New configuration files have been added and the existing convenience scripts have been modified to support the Jazz for Service Management Fix Pack 1. The new configuration files support both a fresh installation of Jazz for Service Management and an update from an existing Jazz for Service Management 1.1 installation to Jazz for Service Management Fix Pack 1.
Jazz for Service Management Fix Pack 1 uses a new environment variable to indicate whether it is a fresh Jazz for Service Management installation, JazzSM_FreshInstall=True, or an update to an existing Jazz for Service Management installation, JazzSM_FreshInstall=False.
The convenience scripts have also been updated to support the Jazz for Service Management update scenario. Users can specify the optional update parameter when they manually run a convenience script. When this parameter is specified, Prerequisite Scanner sets the value of the JazzSM_FreshInstall environment variable to false. It then scans the target system for the prerequisite properties associated with the Jazz for Service Management update scenario. If the parameter is not specified, Prerequisite Scanner sets the value of the JazzSM_FreshInstall environment variable to true and scans the target system for the prerequisite properties associated with the fresh installation scenario.
The following convenience scripts have been updated to support the optional update parameter:
ips_root/JazzSMScripts/Scenario1_DB_Server.bat|sh
ips_root/JazzSMScripts/Scenario1_EntUI_Server.bat|sh
ips_root/JazzSMScripts/Scenario2_Typical.bat|sh
ips_root/JazzSMScripts/Scenario2_Typical_noTCR.bat|sh
ips_root/JazzSMScripts/Scenario3_DB_Server.bat|sh
ips_root/JazzSMScripts/Scenario3_Ent_Server.bat|sh
ips_root/JazzSMScripts/Scenario3_UI_Server.bat|sh
For example, to check the target Jazz for
Service Management UI and reporting server before an update to this server, run the
convenience script with the optional parameter from the ips_root/JazzSMScripts
directory as follows:
Scenario1_EntUI_Server.bat update
To maintain backward compatibility with earlier stand-alone versions
of IBM Tivoli Common Reporting, the ips_root/TCR.bat|sh
script has also been updated to support this optional parameter.
Message enhancements
Some WARNING and ERROR messages have been enhanced to include the product code and version to assist users in locating the issue in the relevant configuration file. If a problem occur during the scan, for example incorrect syntax for a prerequisite property or section title in a configuration file, Prerequisite Scanner generates a WARNING message with the product code and version. This message is displayed in the command window and logged to the plain text and XML result files.
Documentation changes in this modification
The Prerequisite Scanner Information Center is not updated for Version 1.2.0.4.
Fixed defects
For a list of defects fixed in this fix pack, see the Readme.html file in the ips_root directory.
Known issues
For a list of known issues in this fix pack, see the Readme.html file in the ips_root directory.
Enhancements in Version 1.2.0.3
Removal of the Microsoft .NET Framework prerequisite
Previous versions of Prerequisite Scanner required an existing installation of Microsoft .NET Framework on Windows systems. This prerequisite has removed in Prerequisite Scanner Version 1.2.0.3.
Removal of temporary prerequisites for Windows 2012 support
In the Prerequisite Scanner Version 1.2.0.2, Prerequisite Scanner had a temporary set of prerequisites for Windows 2012 support, that is, either install Microsoft .NET Framework Version 3.5 or use a Windows activation configuration script. For Prerequisite Scanner Version 1.2.0.3, the VBScript code no longer uses the System.Collections.ArrayList class. Prerequisite Scanner no longer requires these prerequisites to support Windows 2012.
Support for Jazz for Service Management Version 1.1
Prerequisite Scanner provides a set of convenience scripts in the ips_root/JazzSMScripts directory that specify the required and optional parameters to run Prerequisite Scanner and scan for the prerequisites required for each installation scenario and server topology.
This table outlines the convenience scripts for each Jazz for Service Management installation scenario. For more information about running these convenience scripts, see the Jazz for Service Management Information Center.
Attention: The Prerequisite Scanner configuration files for Jazz for Service Management contain default values for installation paths, thereby assuming that you install the integration services and middleware to these default installation locations.
Installation scenario |
Jazz for Service Management server |
Installed integration services |
Convenience script |
---|---|---|---|
Custom installation (two server topology) | Database server only | Registry Services database |
Scenario1_DB_Server.sh|bat |
Composite server (enterprise and UI and reporting servers) | Administration Services application Administration Services UI Dashboard Application Services Hub Registry Services application Security Services Tivoli Common Reporting |
Scenario1_EntUI_Server.sh|bat | |
Simple installation (single server topology) | Combined database, enterprise, and UI server | Database and all integration services |
Scenario2_Typical.sh|bat |
Simple installation (single server topology) | Combined database, enterprise, and UI server | Database and the integration services except Tivoli Common Reporting |
Scenario2_Typical_NoTCR.sh|bat |
Custom installation (three server topology) | Database server only | Registry Services database |
Scenario3_DB_Server.sh|bat |
Enterprise server only | Administration Services application Registry Services application Security Services |
Scenario3_Ent_Server.sh|bat | |
UI and reporting server only | Administration Services UI Dashboard Application Services Hub Tivoli Common Reporting |
Scenario3_UI_Server.sh|bat |
Documentation changes in this fix pack
Prerequisite Scanner Information Center is not updated for Version 1.2.0.3. This news announcement describes all updates that would otherwise be included in the information center.
This fix pack and previous fix packs contain new configuration files. These files were added to the ips_root\Windows and ips_root/UNIX_Linux directories. The following table lists the new configuration files. For each configuration file, it outlines the associated platform, product version, and the fix pack in which it was added.
File name |
Platforms |
Product version, platform, operating system |
Introduced in |
---|---|---|---|
NCI_07010000.cfg | All | Tivoli Netcool/Impact Version 7.1 | 1.2.0.11 |
PAC_07060000.cfg | All | Tivoli Process Automation Engine Version 7.6 and later – Common | 1.2.0.11 |
PRX_07060000.cfg | Windows | Tivoli Process Automation Engine Version 7.6 – RXA | 1.2.0.11 |
NCM_06040000.cfg | UNIX | Tivoli Netcool® Configuration Manager Version 6.4 | 1.2.0.9 |
NCM_06040100.cfg | UNIX | Tivoli Netcool® Configuration Manager Version 6.4.1 | 1.2.0.9 |
TNM_03090000.cfg | All | Tivoli Network Manager Version 3.9 | 1.2.0.9 |
TPM_07020200.cfg | All | Tivoli Provisioning Manager Version 7.2.2 | 1.2.0.9 |
TIP_02020013.cfg | All | Tivoli Integrated Portal Version 2.2.0.13 | 1.2.0.8 |
DSH_03010002.cfg | All | Dashboard Application Services Hub Version 3.1.0.2 | 1.2.0.8 |
ESS_01010002.cfg | All | Security Services Version 1.1.0.2 | 1.2.0.8 |
FAS_01010002.cfg | All | Administration Services Version 1.1.0.2 | 1.2.0.8 |
FRS_01010002.cfg | All | Registry Services Version 1.1.0.2 | 1.2.0.8 |
ODP_01010002.cfg | All | Common prerequisites in Jazz for Service Management Version 1.1.0.2 | 1.2.0.8 |
TCR_03010002.cfg | All | Tivoli Common Reporting Version 3.1.0.2 | 1.2.0.8 |
CVT_01010000.cfg | All | Prerequisite Scanner Component Verification Test, internal use only | 1.2.0.6 |
IDS_06030100.cfg | UNIX | Security Directory Server Version 6.3.1 | 1.2.0.6 |
DA1_09010000.cfg | All | Tivoli Workload Scheduler Dynamic Agent Version 9.1 | 1.2.0.5 |
FTA_09010000.cfg | All | Tivoli Workload Scheduler Fault-Tolerant Agent Version 9.1 | 1.2.0.5 |
TWA_09010000.cfg | UNIX | Tivoli Workload Automation Version 9.1 | 1.2.0.5 |
TS1_07020200.cfg | All | IBM Tivoli Application Dependency
Discovery Manager Version
7.2.2 Domain Server - Small Attention: In the version of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS1_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS1_07020200.cfg.
|
1.2.0.5 |
TS2_07020200.cfg | All | Tivoli Application Dependency Discovery Manager Version
7.2.2 Domain Server - Large Attention: In the version of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS2_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS2_07020200.cfg.
|
1.2.0.5 |
TS3_07020200.cfg | All | Tivoli Application Dependency Discovery Manager Version
7.2.2 Domain Server - Enterprise Attention: In the version
of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS3_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS3_07020200.cfg.
|
1.2.0.5 |
TS4_07020200.cfg | All | Database Server for Tivoli Application Dependency Discovery Manager Version
7.2.2 Domain Server - Small Attention: In the version of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS4_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS4_07020200.cfg.
|
1.2.0.5 |
TS5_07020200.cfg | All | Database Server for Tivoli Application Dependency Discovery Manager Version
7.2.2 Domain Server - Large Attention: In the version of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS5_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS5_07020200.cfg.
|
1.2.0.5 |
TS6_07020200.cfg | All | Database Server for Tivoli Application Dependency Discovery Manager Version
7.2.2 Domain Server - Enterprise Attention: In the version
of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS6_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS6_07020200.cfg.
|
1.2.0.5 |
TS7_07020200.cfg | All | Tivoli Application Dependency Discovery Manager Version
7.2.2 Discover or Storage Server - Small Attention: In
the version of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS7_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS7_07020200.cfg.
|
1.2.0.5 |
TS8_07220000.cfg | All | Tivoli Application Dependency Discovery Manager Version
7.2.2 Discover or Storage Server - Large Attention: In
the version of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS8_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS8_07020200.cfg.
|
1.2.0.5 |
TS9_07020200.cfg | All | Tivoli Application Dependency Discovery Manager Version
7.2.2 Discover or Storage Server - Enterprise Attention: In
the version of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TS9_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TS9_07020200.cfg.
|
1.2.0.5 |
TSA_07220000.cfg | All | Database Server for Tivoli Application Dependency Discovery Manager Version
7.2.2 Storage Server - Small Attention: In the version
of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TSA_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TSA_07020200.cfg.
|
1.2.0.5 |
TSB_07020200.cfg | All | Database Server for Tivoli Application Dependency Discovery Manager Version
7.2.2 Storage Server - Large Attention: In the version
of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TSB_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TSB_07020200.cfg.
|
1.2.0.5 |
TSC_07020200.cfg | All | Database Server for Tivoli Application Dependency Discovery Manager Version
7.2.2 Storage Server - Enterprise Attention: In the version
of Prerequisite Scanner that
was bundled with Tivoli Application Dependency Discovery Manager Version
7.2.2 installation media, the name of the configuration file was TSC_07220000.cfg. It has been bundled and
renamed in Version 1.2.0.5 to TSC_07020200.cfg.
|
1.2.0.5 |
KAS_06300000.cfg | All | Tivoli Enterprise Monitoring Automation Server Version 6.3 | 1.2.0.5 |
KCJ_06300000.cfg | All | Tivoli Enterprise Portal Client Version 6.3 | 1.2.0.5 |
KCQ_06300000.cfg | All | Tivoli Enterprise Portal Server Version 6.3 | 1.2.0.5 |
KHD_06300000.cfg | All | Warehouse Proxy Agent Version 6.3 | 1.2.0.5 |
KLZ_06300000.cfg | UNIX | Tivoli Monitoring Operating System Agent for Linux Version 6.3 | 1.2.0.5 |
KMS_06300000.cfg | All | Tivoli Enterprise Monitoring Server Version 6.3 | 1.2.0.5 |
KNT_06300000.cfg | Windows | Tivoli Monitoring Operating System Agent for Windows Version 6.3 | 1.2.0.5 |
KPA_06300000.cfg | All | Tivoli Performance Analyzer Version 6.3 | 1.2.0.5 |
KSY_06300000.cfg | All | Summarization and Pruning Agent Version 6.3 | 1.2.0.5 |
KUX_06300000.cfg | UNIX | Tivoli Monitoring Operating System Agent for UNIX Version 6.3 | 1.2.0.5 |
DSH_03010001.cfg | All | Dashboard Application Services Hub Version 3.1.0.1 | 1.2.0.4 |
ESS_01010001.cfg | All | Security Services in Jazz™ for Service Management Version 1.1.0.1 | 1.2.0.4 |
FAS_01010001.cfg | All | Administration Services in Jazz for Service Management Version 1.1.0.1 | 1.2.0.4 |
FRS_01010001.cfg | All | Registry Services in Jazz for Service Management Version 1.1.0.1 | 1.2.0.4 |
ODP_01010001.cfg | All | Common prerequisites in Jazz for Service Management Version 1.1.0.1 | 1.2.0.4 |
TCR_03010001.cfg | All | Tivoli Common Reporting Version 3.1.0.1 | 1.2.0.4 |
PAD_07050100.cfg | All | Tivoli Process Automation Engine Version 7.5.1–DB2® | 1.2.0.4 |
PAM_07050100.cfg | All | Tivoli Process Automation Engine Version 7.5.1–WebSphere® Application Server Version 7.5.1 | 1.2.0.4 |
PAW_07050100.cfg | All | Tivoli Process Automation Engine Version 7.5.1–Maximo® Asset Management | 1.2.0.4 |
AMA_07000000.cfg | All | Security Access Manager Authorization Server | 1.2.0.3 |
AMP_07000000.cfg | All | Security Access Manager Policy Server | 1.2.0.3 |
AMW_07000000.cfg | All | Security Access Manager WebSEAL | 1.2.0.3 |
DSH_03010000.cfg | All | Dashboard Application Services Hub Version 3.1 | 1.2.0.3 |
ESS_01010000.cfg | All | Security Services in Jazz™ for Service Management Version 1.1 | 1.2.0.3 |
FAS_01010000.cfg | All | Administration Services in Jazz for Service Management Version 1.1 | 1.2.0.3 |
FRS_01010000.cfg | All | Registry Services in Jazz for Service Management Version 1.1 | 1.2.0.3 |
ODP_01010000.cfg | All | Common prerequisites in Jazz for Service Management Version 1.1 | 1.2.0.3 |
TCR_03010000.cfg | All | Tivoli Common Reporting Version 3.1 | 1.2.0.3 |
The fix packs contain modified configuration files. These files are in the ips_root\Windows and ips_root/UNIX_Linux directories. This table lists the modified configuration files. For each configuration file, it outlines the associated platform, product version, and the release in which it was modified.
File name |
Platforms |
Product version, platform, operating system |
Modified in |
---|---|---|---|
NOC_07040000.cfg | UNIX | Tivoli Netcool/OMNIbus server, desktop, and probe components Version 7.4 | 1.2.0.10–Updated expected values for the os.space.opt to 5.5. |
NOD_07040000.cfg | UNIX | Tivoli Netcool/OMNIbus desktop component Version 7.4 | 1.2.0.11–added sections to support checking for libraries for different operating systems |
NOP_07040000.cfg | UNIX | Tivoli Netcool/OMNIbus probe components Version 7.4 | 1.2.0.11–added sections to support checking for libraries for different operating systems /td> |
NOS_07040000.cfg | UNIX | Tivoli Netcool/OMNIbus server components Version 7.4 | 1.2.0.11–added sections to support checking for libraries for different operating systems |
PAD_07060000.cfg | All | Tivoli Process Automation Engine Version 7.6 – DB2 | 1.2.0.11–Renamed from PAD_07050100.cfg |
PAM_07060000.cfg | All | Tivoli Process Automation Engine Version 7.6 – WebSphere Application Server | 1.2.0.11–Renamed from PAM_07050100.cfg |
PAW_07060000.cfg | UNIX | Tivoli Process Automation Engine Version 7.6 – Maximo Asset Management | 1.2.0.11–Renamed from PAW_07050100.cfg |
TCR_03010001.cfg | UNIX | Tivoli® Common Reporting Version 3.1.0.1 | 1.2.0.10–Updated expected values for the os.space.opt to 5.5. |
TCR_03010001.cfg | Windows | Tivoli Common Reporting Version 3.1.0.1 | 1.2.0.10–Updated expected values for the Disk to 5461. |
TCR_03010002.cfg | UNIX | Tivoli Common Reporting Version 3.1.0.2 | 1.2.0.10–Updated expected values for the os.space.opt to 5.5. |
TCR_03010002.cfg | Windows | Tivoli Common Reporting Version 3.1.0.2 | 1.2.0.10–Updated expected values for the Disk to 1024 and 5461. |
TCR_03010002.cfg | UNIX | Tivoli Common Reporting Version 3.1.0.2 | 1.2.0.9–Added os.lib.libXm.so.4_64 prerequisite property to the RedHat Enterprise Linux Server and SUSE Linux Enterprise Server sections |
ODP_01010001.cfg | UNIX | Jazz for Service Management Version 1.1.0.1 | 1.2.0.7–Added os.servicesTCPavailablePorts prerequisite property |
TCR_03010001.cfg | UNIX | Tivoli Common Reporting Version 3.1.0.1 | 1.2.0.7–Replaced Disk with os.space.opt prerequisite properties |
TCR_03010001.cfg | Windows | Tivoli Common Reporting Version 3.1.0.1 | 1.2.0.5–Replaced user.isAdmin with user.hasAdminPrivileges |
ODP_01010001.cfg | Windows | Common prerequisites in Jazz for Service Management Version 1.1.0.1 | 1.2.0.5–Replaced user.isAdmin with user.hasAdminPrivileges prerequisite property. |
ODP_01010000.cfg | All | Common prerequisites in Jazz for Service Management Version 1.1.0 | 1.2.0.4–Updated os.package prerequisite properties to remove Installation Manager 32-bit libraries checks for Red Hat Enterprise Linux Server Version 6.0 operating systems. |
BSM_06010100.cfg | UNIX | Tivoli Business Service Manager Version 6.1.1 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
CDB_06220000.cfg | UNIX | Tivoli Composite Application Manager (ITCAM) for Applications: DB2 Version 6.2.2 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COA_07200000.cfg | UNIX | Tivoli Provisioning Manager Version 7.2 for UNIX | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COB_07200000.cfg | AIX | Tivoli Provisioning Manager Version 7.2 for AIX | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COC_07200000.cfg | AIX | Tivoli Provisioning Manager Version 7.2 for AIX V5.3.0.0 {64 bit} | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COD_07200000.cfg | AIX | Tivoli Provisioning Manager Version 7.2 for AIX 6.1 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COE_07200000.cfg | Linux | Tivoli Provisioning Manager Version 7.2 for Linux | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COF_07200000.cfg | Linux | Tivoli Provisioning Manager Version 7.2 for Red Hat Linux | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COG_07200000.cfg | Linux | Tivoli Provisioning Manager Version 7.2 for Red Hat Enterprise Linux 5 x86 64 bit | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COH_07200000.cfg | Linux | Tivoli Provisioning Manager Version 7.2 for Red Hat Enterprise Linux 5 System z® 64 bit | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COI_07200000.cfg | Linux | Tivoli Provisioning Manager Version 7.2 for SUSE 10 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COJ_07200000.cfg | Solaris | Tivoli Provisioning Manager Version 7.2 for Solaris | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COK_07200000.cfg | HP-UX | Tivoli Provisioning Manager Version 7.2 for HP-UX | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COL_07200000.cfg | Linux | Tivoli Provisioning Manager Version 7.2 for SUSE zSeries® 10 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COM_07200000.cfg | Linux | Tivoli Provisioning Manager Version 7.2 for SUSE 11 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
CON_07200000.cfg | Linux | Tivoli Provisioning Manager Version 7.2 for SUSE zSeries 11 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
COZ_07200000.cfg | Windows | Tivoli Provisioning Manager Version 7.2 for Windows | 1.2.0.4–Updated os.isServiceRunning prerequisite properties to use the actual Windows service name as the suffix identifier in the property name. |
DMO_07020000.cfg | UNIX | Prerequisite Scanner demo | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
DMO_07050000.cfg | UNIX | Prerequisite Scanner Version 1.0 demo | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
NCI_06010100.cfg | UNIX | Tivoli Netcool/Impact Version 6.1.1 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
NOC_07030100.cfg | UNIX | Tivoli Netcool/OMNIbus server components and desktop component Version 7.3.1 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
NOC_07040000.cfg | UNIX | Tivoli Netcool/OMNIbus server, desktop, and probe components Version 7.4 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
NOD_07030100.cfg | UNIX | Tivoli Netcool/OMNIbus desktop component Version 7.3.1 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
NOD_07040000.cfg | UNIX | Tivoli Netcool/OMNIbus desktop component Version 7.4 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
NOP_07040000.cfg | UNIX | Tivoli Netcool/OMNIbus probe components Version 7.4 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
NOS_07030100.cfg | UNIX | Tivoli Netcool/OMNIbus server components Version 7.3.1 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
NOS_07040000.cfg | UNIX | Tivoli Netcool/OMNIbus server components Version 7.4 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
ODP_01010000.cfg | UNIX | Common prerequisites in Jazz for Service Management Version 1.1 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character |
PAE_07050000.cfg | UNIX | Tivoli Process Automation Engine Version 7.5 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character. |
TPM_07210000.cfg | All | Tivoli Provisioning Manager Version 7.2.1 | 1.2.0.4–Updated os.package prerequisite properties to use the + special character and os.isServiceRunning prerequisite properties to use the actual Windows service name as the suffix identifier in the property name. |
FRS_01010000.cfg | All | Registry Services in Jazz for Service Management Version 1.1 | 1.2.0.4–Updated prerequisite properties |
BSM_06010100.cfg | All | Tivoli Business Service Manager Version 6.1.1 | 1.2.0.3–Updated prerequisite properties |
NCI_06010100.cfg | All | Tivoli Netcool/Impact Version 6.1.1 | 1.2.0.3–Updated prerequisite properties |
DMO_07020000.cfg | UNIX | Prerequisite Scanner demo Version 7.2 | 1.2.0.3–Renamed from DMO_0720000.cfg |
DMO_07050000.cfg | UNIX | Prerequisite Scanner demo Version 7.5 | 1.2.0.3–Renamed from DMO_0750000.cfg |
NOC_07030100.cfg | All | Tivoli Netcool/OMNIbus server components and desktop component Version 7.3.1 | 1.2.0.2–Renamed from NOC_07310000.cfg |
NOD_07030100.cfg | All | Tivoli Netcool/OMNIbus desktop component Version 7.3.1 | 1.2.0.2–Renamed from NOD_07310000.cfg |
NOS_07030100.cfg | All | Tivoli Netcool/OMNIbus server components Version 7.3.1 | 1.2.0.2–Renamed from NOS_07310000.cfg |
BSM_06010000.cfg | All | Tivoli Business Service Manager Version 6.1 | 1.2.0.1–Renamed from BSM_06100000.cfg |
NCI_06010000.cfg | All | Tivoli Netcool/Impact Version 6.1 | 1.2.0.1–Renamed from NCI_06100000.cfg |
PAE_07050000.cfg | All | Tivoli Process Automation Engine Version 7.5 | 1.2.0.0–Renamed from PAE_07500000.cfg |
The fix packs contain new prerequisite properties.
New prerequisite properties: Fix pack 10 | Fix pack 7 | Fix pack 6 | Fix pack 5 | Fix pack 4 | Fix pack 3
New prerequisite properties in fix pack 10
This table lists the new prerequisite properties for Version 1.2.0.10. For each prerequisite property, it outlines the associated platform, description, and valid values.Property name |
Platforms |
Description |
Valid Values |
---|---|---|---|
|
Platform | Description |
Valid format and values |
|
Linux, Windows | Checks the type of hardware. The tool currently
supports checking for:
|
String representing
a supported hardware type:
|
|
Linux | Checks whether the firewall is enabled | Boolean value, for example, False |
|
Linux, Windows | Checks the type of hypervisor. The tool currently
supports checking for:
|
String representing
a supported hypervisor:
|
New prerequisite properties in fix pack 7
This table lists the new prerequisite properties for Version 1.2.0.7. For each prerequisite property, it outlines the associated platform, description, and valid values.Property name |
Platforms |
Description |
Valid Values |
---|---|---|---|
os.registry. |
Windows | Checks whether the key_value value for the HKEY_LOCAL_MACHINE subkey has specified value data in the Windows Registry, based on the following qualification attributes:
user_defined_id represents a unique identifier suffix to support multiple prerequisite properties checking the same key value but for different subkeys. The prerequisite property supports the following data types for the key value data:
Restriction: This prerequisite property supports subkeys of the HKEY_LOCAL_MACHINE root key only. |
String with the following qualifier format for the HKEY_LOCAL_MACHINE subkey: os.registry.
For
example, to check whether the 1433 and 1434 ports are specified for
the ReservedPorts key value associated with the os.registry.tcpPorts=
For example, to check whether a set of privileges has been specified for the RequiredPrivileges key value associated with the SYSTEM\CurrentControlSet\services\COMSysApp subkey: os.registry.COMSysApp=
|
|
UNIX | Checks whether the TCP port for the service_type service
or a TCP port from the specified range of ports is absent from the /etc/services file. service_type refers
to a user-defined name for the service; for example, os.servicesTCPavailablePorts. The scan returns the PortsInUse: prefix and list of ports in use in the file, as the actual value. If the expected port is not in the list, then the port is available. |
Single positive integers, for example:
A range of positive integers that is specified by using the - character or a comma separated list, for example:
|
|
UNIX | Checks whether the UDP port for the service_type service
or a UDP port from the specified range of ports is absent from the /etc/services file. service_type refers
to a user-defined name for the service; for example, os.servicesUDPavailablePorts. The scan returns the PortsInUse: prefix and list of ports in use in the file, as the actual value. If the expected port is not in the list, then the port is available. |
Single positive integers, for example:
A range of positive integers that is specified by using the - character or a comma separated list, for example:
|
New prerequisite properties in fix pack 6
This table lists the new prerequisite properties for Version 1.2.0.6. For each prerequisite property, it outlines the associated platform, description, and valid values.Property name |
Platforms |
Description |
Valid Values |
---|---|---|---|
|
AIX® |
Checks whether the value for the parameter_name Virtual Memory Manager tuning parameter is specified on the target machine. parameter_name represents the Virtual Memory Manager tuning parameter that is configured by using the vmo command, for example:
If the parameter_name Virtual Memory Manager tuning parameter is not valid, the check logs an error message. It returns Not Found for the actual value and the check fails. Restriction: The path to the vmo binary must be set in the PATH environment variable; if the path is not set, the check logs an error message. It returns Not Found for the actual value and the check fails. |
Numeric format, for example:
|
|
AIX |
Checks whether the value for the parameter_name network option tunable parameter is specified on the target machine. parameter_name represents the network option tunable parameter that is configured by using the no command, for example:
If the parameter_name network option tunable parameter is not valid, the check logs an error message. It returns Not Found for the actual value and the check fails. Restriction: The path to the no binary must be set in the PATH environment variable; if the path is not set, the check logs an error message. It returns Not Found for the actual value and the check fails. |
Numeric format, for example:
|
|
Linux |
Checks whether the value for the setting_name kernel performance and tuning setting is specified on the target machine. setting_name represents the kernel performance and tuning setting that is configured by using the sysctl command, for example:
If the setting_name kernel performance and tuning setting is not valid, the check logs an error message. It returns Not Found for the actual value and the check fails. Restriction: The path to the sysctl binary must be set in the PATH environment variable; if the path is not set, the check logs an error message. It returns Not Found for the actual value and the check fails. |
String or numeric format depending on valid values for the specified setting, for example:
|
|
All | The full name and version of the operating system
that is running on the machine; alternatively, you can use a regular
expression to pass a string that represents the multiple variants
of an operating system.
Tip: Use this prerequisite property in conjunction with os.servicePack (Windows) or os.ServicePack (UNIX), and os.architecture to check the current service pack and system architecture. |
The value can be any of the following types:
Note: The values can use the special characters. Attention:This prerequisite property supersedes the OS Version prerequisite property that will be deprecated in a future release. |
|
Windows | Checks whether Microsoft .NET Framework Version 3.5 or 4.5 is installed on the machine | Numeric format, for example:
|
New prerequisite properties in fix pack 5
This table lists the new prerequisite properties for Version 1.2.0.5. For each prerequisite property, it outlines the associated platform, description, and valid values.Property name |
Platforms |
Description |
Valid Values |
---|---|---|---|
|
UNIX | Checks whether any of the specified web browser versions are installed on the machine. The web browser type is specified by browser_name in the expected value and can be one of the following types:
|
String to represent any of the required browser versions that must be installed on the machine, in the following formats:
Note: The values can use the + special character. |
|
Windows | Checks whether any of the specified web browser versions are installed on the machine. The web browser type is specified by browser_name in the expected value and can be one of the following types:
|
String to represent any of the required browser versions that must be installed on the machine, in the following formats:
Note: The values can use the + special character. |
|
Windows | Checks whether the specified WinPCap version is installed on the machine; it returns Not Found if WinPCap is not installed on the machine. | Numeric format, for example, 4.1.1
Note: The check supports using the special character + in the expected value. |
user.hasAdminPrivileges | Windows | Checks whether the logged in user has elevated, administrative privileges to run a task |
Boolean value, for example, True |
New prerequisite properties in fix pack 4
This table lists the new prerequisite properties for Version 1.2.0.4. For each prerequisite property, it outlines the associated platform, description, and valid values.Property name |
Platforms |
Description |
Valid Values |
---|---|---|---|
|
AIX | Checks whether the specified iFix or iFixes are installed on the machine. When multiple iFixes are specified, all iFixes must be installed; otherwise the check fails. Restriction: The prerequisite property has the following restrictions:
|
String in the following format:
|
|
UNIX | Checks whether the file_name file has the relevant specifications based on the following qualification attributes:
|
String with the following qualifier format:
For example, to check whether the owner, groups, and other users have read and execute permissions to the nmap binary, when the path to the binary is set in the PATH environment variable:
Note: This prerequisite property supports using the special character + in the expected value. For example, to check whether the owner, groups, and other users have read, execute, and optionally write permissions to the nmap binary, when the path to the binary is not set in the PATH environment variable:
The check also passes when the octal digit representation is 777, because the + symbol is specified. |
network.ipv4Available
|
All | Checks whether there is at least one available non-loopback Internet Protocol version 4 (IPv4) interface on the machine. |
Boolean value, for example, True |
|
Linux PowerPC® | Checks whether the specified version of the IBM_lib_name IBM library is installed on the machine based on the following qualification attributes:
The qualification attributes are delimited by the semi colon ; character. |
String in the following format:
For example:
|
|
AIX | Checks whether the required page size is enabled on the computer based on the following segments:
|
Strings to represent valid page size segments:
|
New prerequisite properties in fix pack 3
This table lists the new prerequisite properties for Version 1.2.0.3. For each prerequisite property, it outlines the associated platform, description, and valid values.Property name |
Platforms |
Description |
Valid Values |
---|---|---|---|
numLogicalCPU | All | The number of logical processors available to the operating system on the computer. The check can run under the following conditions:
Note: This property is not supported on Windows 2000 operating systems. |
Number, for example, 2 |
os.isUnixServiceRunning. |
UNIX |
Checks whether the daemon_name daemon or service is running on the machine. daemon_name represents the following daemon processes or services for which the tool checks:
The tool requires that the path to the following command, which checks the status of the daemon process or service, is set in the PATH environment variable:
Note: If the tool runs the scan on a UNIX system that has the running daemon process or service, it returns a PASS result; otherwise, it returns a FAIL result. |
Boolean value, for example: True |
os.UACEnabled |
Windows |
Checks whether User Account Control (UAC) is enabled on the target computer Note: If the tool runs the scan on a Windows system that does not have this security component, it returns a FAIL result, with [Not Found] as the actual value. |
Boolean value, for example: True |
This fix pack and previous fix packs contain modified prerequisite properties to support enhancements or to fix documentation and code defects.
Modified prerequisite properties: Fix pack 8 | Fix pack 6 | Fix pack 5 | Fix pack 4 | Fix pack 3
Modified prerequisite properties in fix pack 8
This table lists the modified prerequisite properties in Version 1.2.0.8. For each prerequisite property, it outlines the associated platform and description.
Property name |
Platforms |
Description |
Valid values |
---|---|---|---|
db2.home.space | UNIX | The available disk space for the DB2 home directory | The value can be any of the following types:
|
|
Windows | The amount of free disk space, with the following
optional qualification attributes:
If you do not the specify dir attribute or set the path parameter when running the Prerequisite Scanner script, the tool checks the default installation directories for IBM Tivoli products:
|
The value can be any of the following types:
|
|
UNIX | The amount of free disk space If you do not set the path parameter when running the Prerequisite Scanner script, the tool checks the default installation directories for IBM Tivoli products:
|
The value can be any of the following types:
|
|
All | The speed of the Intel processor | The value can be any of the following types:
|
|
All | The total amount of physical memory that is
currently available on the machine. Tip: Separately check
for the amount of physical and virtual memory available by the using
predefined prerequisite properties in the operating system category.
On AIX systems only, the following conditions apply:
|
The value can be any of the following types:
|
|
UNIX | The speed of a RISC processor | The value can be any of the following types:
|
|
UNIX | The available disk space for the specified Temp file system | The value can be any of the following types:
|
|
Windows |
Checks the amount of virtual memory that is currently available but unused by the operating system |
The value can be any of the following types:
|
|
UNIX |
Checks the RAM that the operating system can access and report on the machine, which might be less than the actual number of GBs of installed RAM depending on the operating system type |
The value can be any of the following types:
|
|
UNIX |
Checks the available disk space for the specified dir_name file system based on one or more of the following qualification attributes:
The value for dir attribute is dependant on the logged on user; thus, the value is a name value pair to represent the user type, that is, root or non-root, and the associated path. dir_name can represent for example:
Note: You cannot use this variant twice for the same file system but different user types in a single configuration file. Use a combination of the os.space.dir_name_nonroot and os.space.dir_name_root variants. |
String with the following qualifier format for the file system of a root user:
For example:
String with the following qualifier format for the file system of a non-root user:
For example:
String with the following qualifier format for the file system of any user, using only one qualifier:
For example:
String with the following qualifier format for the file system of both users, using only one qualifier:
For example:
Numeric format in MB or GBs, for example:
A range of positive integers in MBs or GBs to represent the minimum and recommended disk space, which is specified by using the - character, for example:
|
|
UNIX |
Checks the available disk space for the dir_name file system of the non-root user, based on one or more of the following qualification attributes:
dir_name can represent for example:
|
String with the following qualifier format for the file system of a non-root user:
For example:
String with the dir qualification attribute only for the file system of a non-root user:
For example:
|
|
UNIX |
Checks the available disk space for the dir_name file system of the root user, based on one or more of the following qualification attributes:
dir_name can represent for example:
|
String with the following qualifier format for the file system of a root user:
For example:
String with the dir qualification attribute only for the file system of a root user:
For example:
|
|
UNIX |
Checks whether the swap space must be greater than the RAM size or the total amount of swap space Note: On AIX systems only: If you are logged in as a non root user, you must have permissions to run the bootinfo command; otherwise, the returned results might be unexpected. |
The value can be any of the following types:
|
|
Windows |
The total amount of virtual memory to which the operating system can access |
The value can be any of the following types:
|
|
Windows |
The total amount of physical memory that the operating system can access, but it does not indicate the true amount of physical memory on the target computer |
The value can be any of the following types:
|
Modified prerequisite properties in fix pack 6
This table lists the modified prerequisite properties in Version 1.2.0.6. For each prerequisite property, it outlines the associated platform and description.
Property name |
Platforms |
Description |
Valid values |
---|---|---|---|
|
UNIX | Checks whether the file_name file has the relevant specifications based on the following qualification attributes:
|
String with the following qualifier formats:
For example, to check whether the password file exists in the specified path:
For example, to check whether the owner, groups, and other users have read and execute permissions to the nmap binary, when the path to the binary is set in the PATH environment variable:
Note: This qualifier format supports using the special character + in the expected value. For example, to check whether the owner, groups, and other users have read, execute, and optionally write permissions to the nmap binary, when the path to the binary is not set in the PATH environment variable:
The check also passes when the octal digit representation is 777, because the + symbol is specified. |
|
UNIX |
Checks whether the binary_name binary
is available on the machine. binary_name can
represent any binary, for example:
|
Boolean value, for example:
|
|
UNIX |
Checks that the supported version of the package_name package is installed on the machine. String to represent package_name, for example, in bold:
Restriction: On HP-UX systems only, the tool uses the following command and flag, swlist -l, to retrieve the list of installed packages. This command requires that the logged in user has at least super user access. If the logged in user is non-root user, then the check fails. |
String to represent the required version that must be installed, for example:
Note: This variant of the prerequisite property supports using the special character + or - in the expected value. For example:
|
os.space.dir_name prerequisite properties The dir_path value for the dir qualification
attribute that specifies the file system can have any of the following
formats:
All variants of the os.space.dir_name prerequisite property support the use of environment variables:
|
|||
|
All | Use this naming convention for checking whether
the TCP port or range of TCP ports are available for the app_type application
type. Check which TCP ports are not being listened to, for example:
The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. If the expected port is not in the list, then the port is available. |
Single positive integers, for example:
A range of positive integers that is specified by using the - character or a comma separated list, for example:
|
network.portsInUse.app_type | All | Use this naming convention for checking whether
the TCP port or range of TCP ports are in use for the app_type application
type. Check which TCP ports are being listened to, for example:
The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. |
Single positive integers, for example:
A range of positive integers that is specified by using the - character or a comma separated list, for example:
|
|
All | Use this naming convention for checking whether
the UDP port or range of UDP ports are available for the app_type application
type. Check which UDP ports are not being listened to, for example:
The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. If the expected port is not in the list, then the port is available. |
Single positive integers, for example:
A range of positive integers that is specified by using the - character or a comma separated list, for example:
|
network.UDPportsInUse.app_type | All | Use this naming convention for checking whether
the UDP port or range of UDP ports are in use for the app_type application
type. Check which UDP ports are being listened to, for example, for
example:
The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. |
Single positive integers, for example:
A range of positive integers that is specified by using the - character or a comma separated list, for example:
|
Modified prerequisite properties in fix pack 5
This table lists the modified prerequisite properties in Version 1.2.0.5. For each prerequisite property, it outlines the associated platform and description.
Property name |
Platforms |
Description |
Valid values |
---|---|---|---|
|
UNIX |
Checks whether the information for host machine is correct, including when the host machine is identified by an alias domain name |
Boolean value, for example, True |
|
UNIX |
Checks whether the entries in /etc/host are in the correct format, for example: IP_Address Host_Name Short_Name_Alias1 [Short_Name_AliasN] where:
|
Boolean value, for example:
|
Modified prerequisite properties in fix pack 4
This table lists the modified prerequisite properties in Version 1.2.0.4. For each prerequisite property, it outlines the associated platform and description.
Property name |
Platforms |
Description |
Valid values |
---|---|---|---|
|
Windows |
Checks whether the service_name service is running on the machine. service_name represents the valid Windows service name that does not contain spaces or the % character, for example:
If you use spaces or an % character in the service_name suffix, the check logs a warning message. It returns Not Found for the actual value and the check fails. Attention: You must use the actual Windows service name. If you use the display name of the service as the service_name suffix, the scan assumes that the service is not running and returns False for the actual value and the check fails or passes depending on the expected value. Note: This version of the prerequisite property supersedes earlier versions. |
Boolean value, for example:
|
os.space.dir_name prerequisite properties The dir_path value for the dir qualification attribute that specifies the file system can have any of the following formats:
All variants of the os.space.dir_name prerequisite property support the use of environment variables:
|
|||
os.package.package_name prerequisite properties Prerequisite Scanner now has two variants of the os.package.package_name property:
You can specify both variants in the same configuration file. |
|||
|
UNIX |
Checks that the supported version of the package_name package is installed on the machine. It returns a PASS result when the required version or a later one is found. String to represent package_name, for example, in bold:
Restriction: On HP-UX systems only, the tool uses the following command and flag, swlist -l, to retrieve the list of installed packages. This command requires that the logged in user has at least super user access. If the logged in user is non-root user, then the check fails. |
String, for example:
Note: This variant of the prerequisite property supports using the special character + in the expected value. |
;
|
UNIX |
Checks whether the package_name package within the specified version range is installed on the machine. package_name represents the short name of the package and [lower_range-upper_range] represents the version range. Examples of package_name include:
Restriction: On HP-UX systems only, the tool uses the following command and flag, swlist -l, to retrieve the list of installed packages. This command requires that the logged in user has at least super user access. If the logged in user is a non-root user, then the check fails. |
|
|
UNIX |
Checks whether the swap space must be greater than the RAM size or the total amount of swap space Note: On AIX systems only: If you are logged in as a non root user, you must have permissions to run the bootinfo command; otherwise, the returned results might be unexpected. |
The value can be any of the following types:
|
Modified prerequisite properties in fix pack 3
This table lists the modified prerequisite properties in Version 1.2.0.3. For each prerequisite property, it outlines the associated platform and description.
Property name |
Platforms |
Description |
Valid values |
---|---|---|---|
|
All | The number of independent physical processors on the computer. If the tool scans the computer and does not find any physical processors, it returns a Not Found result. Restriction: The prerequisite property is not supported on HP-UX 11i v2, Linux virtual machines, Linux for System z, and Linux PowerPC. |
Number, for example, 4 |
DB2 Version | All | The version of DB2 that is currently installed on the machine | The value can be any of the following types:
You can use the + special character with the fix pack number to indicate a fix pack of this level or later is acceptable. For example, FP5+, checks whether fix pack 5 or later is installed. Important: Unlike other properties that use the + special character to check for that version number or later, this property supports the special character on the fix pack number only. For example, if you specify an expected value of v9.5+, and you have DB2 Version 9.7 installed, the check fails; If you specify an expected value of V9.7 FP1+, and you have DB2 Version 9.7 FP4 installed, the check passes. |
|
All | The total amount of physical memory that is currently available on the machine. Tip: Separately check for the amount of physical and virtual memory available by the using predefined prerequisite properties in the operating system category. On AIX systems only, the following conditions apply:
|
Numeric format in GBs or MBs, for example:
|
|
All | Use this naming convention for checking whether the TCP port or range of TCP ports are available for the app_type application type. Check which TCP ports are not being listened to, for example:
The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. If the expected port is not in the list, then the port is available. |
Single positive integers, for example:
A range of positive integers, for example:
|
network.portsInUse. app_type |
All | Use this naming convention for checking whether the TCP port or range of TCP ports are in use for the app_type application type. Check which TCP ports are being listened to, for example:
The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. |
Single positive integers, for example:
A range of positive integers, for example:
|
|
All | Use this naming convention for checking whether the UDP port or range of UDP ports are available for the app_type application type. Check which UDP ports are not being listened to, for example:
The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. If the expected port is not in the list, then the port is available. |
Single positive integers, for example:
A range of positive integers, for example:
|
network.UDPportsInUse. app_type |
All | Use this naming convention for checking whether the UDP port or range of UDP ports are in use for the app_type application type. Check which UDP ports are being listened to, for example, for example:
The scan returns the PortsInUse: prefix and list of ports in use, as the actual value. |
Single positive integers, for example:
A range of positive integers, for example:
|
|
Windows |
Checks whether the service_name service is running on the machine. service_name represents the following services for which the tool checks:
Note: Ensure this prerequisite property is located after network.UDPportsInUse.app_type or network.UDPavailableports.app_type prerequisite properties. The os.isServiceRunning.service_name collector uses UDP ports temporarily and might return invalid results for the UDP port prerequisite properties. Note: Changes in this version of the prerequisite property have been superseded in 1.2.0.4 |
Boolean value, for example:
|
|
UNIX |
Checks the release of the kernel for UNIX operating systems |
String, for example:
Note: The check supports using the special characters + and * in the expected value. |
|
Red Hat Enterprise Linux |
Checks whether the default system shell is installed |
String to represent the default system shell, for example, bash |
This section provides information about any removed features or changes in behavior that impact compatibility with configuration files from earlier versions or product usage.
os.isServiceRunning.service_name
Before Prerequisite Scanner Version 1.2.0.3, the prerequisite property used predefined suffix identifiers to check whether only the following Windows services are running in the target environment: Remote Registry, DNS Client service, and Remote Desktop Services or Terminal Services. In 1.2.0.4, the prerequisite property requires that the actual Windows services name is used as the suffix identifier in the property name. The relevant configuration files have been updated to use the actual service name in the prerequisite properties.
Deprecation of the optional trace input parameter and the prs.trc file
Before Prerequisite Scanner Version 1.2.0.1, Prerequisite Scanner supported an optional trace parameter that logged the trace information in the ips_output_dir/temp/prs.trc file. The input parameter and trace file are deprecated. If you specify the trace parameter in the command line, a warning message is displayed.
Deprecation of the prs.debug file
Before Prerequisite Scanner Version 1.2.0.1, the tool logged the debugging information in the ips_output_dir/temp/prs.debug file on UNIX systems only. This file is now deprecated, with the contents logged to the precheck.log file.
Related Information
Product Synonym
PRS
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21624769