IBM Prerequisite Scanner User manual

Prerequisite Scanner
Version 1.1.1.10
User's Guide


Prerequisite Scanner
Version 1.1.1.10
User's Guide


Note
Before using this information and the product it supports, read the information in “Notices” on page 151.
This edition applies to Version 1.1.1.10 of IBM Prerequisite Scanner and to all subsequent releases and modifications
until otherwise indicated in new editions.
© Copyright IBM Corporation 2009, 2012.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Figures ...............v
Tables ...............vii
Chapter 1. Prerequisite Scanner
overview ..............1
Prerequisite Scanner architecture........1
Prerequisite properties ..........1
Product codes ............12
Prerequisite Scanner configuration files ....13
Prerequisite Scanner collectors .......20
Prerequisite Scanner evaluators .......22
Output formats ............23
Scanning process ............31
New in this release ............33
Chapter 2. Installing Prerequisite
Scanner ..............37
Prerequisites ..............37
Installing the compressed file ........38
Uninstalling Prerequisite Scanner .......38
Chapter 3. Extending Prerequisite
Scanner ..............39
Before you run Prerequisite Scanner ......39
Required checks and extension tasks for
Windows systems ...........39
Required checks and extension tasks for UNIX
systems...............40
Adding product codes ...........41
Creating custom configuration files ......41
Adding prerequisite properties ........43
Editing prerequisite properties ........45
Creating custom collectors for Windows systems . . 46
Creating custom VBScript collectors common to
all configuration files ..........46
Creating custom VBScript collectors specific to a
product and product version .......48
Creating custom collectors for UNIX systems . . . 50
Editing the package test script for UNIX systems . . 51
Creating custom evaluators for Windows systems 53
Creating custom evaluators for UNIX systems . . . 57
Chapter 4. Running Prerequisite
Scanner ..............59
prereq_checker .............59
Running Prerequisite Scanner from the command
line .................64
Common directory locations.........66
Chapter 5. Troubleshooting
Prerequisite Scanner ........67
Troubleshooting on Windows systems .....67
Troubleshooting on UNIX systems.......69
Execution problems............71
Return codes ..............72
Appendix A. Product codes reference 75
Appendix B. Configuration files
reference..............79
Appendix C. Prerequisite properties
reference..............83
Common data properties ..........84
Autonomic Deployment Engine data properties . . 88
Connectivity data properties.........89
DB2 data properties ...........89
MS SQL Server data properties ........90
Internet Explorer data properties .......90
Network data properties ..........91
Oracle data properties ...........92
Operating system data properties .......93
Installed software data properties ......104
User data properties ...........104
Windows network data properties ......105
UNIX network data properties .......105
Appendix D. Predefined collectors for
UNIX systems ...........107
Appendix E. Common functions for
Windows systems .........113
allFiles() ...............114
arrayToString() .............114
bigthan() ...............115
changeMG() ..............115
checkItemToString() ...........116
dictionaryToString() ...........116
exeCommand() .............117
filterCommand() ............117
filterFile()...............118
findNewest() .............118
findSuitableFile() ............119
fmt() ................120
formatForDisplay() ...........120
formatSizeForDisplay() ..........121
getDecimalSeparator() ..........121
getFirstMatch() .............121
isMatch() ...............122
notInLatter()..............122
passOrFail() ..............123
ppread() ...............124
readFile() ...............124
unitMGTOG() .............125
varToString() .............125
© Copyright IBM Corp. 2009, 2012 iii

Appendix F. Logging utility sub
routines for Windows systems ....127
Appendix G. File utility sub routines
for Windows systems ........129
Appendix H. Other common functions
and sub routines for Windows
systems..............131
ffirstMatch() ..............131
getValue() ..............132
removeSpecialCharacters() .........133
versionCompare() ............133
Appendix I. Common functions for
UNIX systems ...........135
changeMG() ..............135
AddMG()...............136
compare() ..............136
cutdown() ..............137
mes4path() ..............138
mes4Path1() ..............138
findOSInfo() ..............139
telnetNFS() ..............139
NFScheck() ..............140
Appendix J. Other functions for UNIX
systems..............141
formatSizeDisplay() ...........142
versionCompare() ............142
checkHpux()..............144
checkLinux() .............144
checkSunOS() .............144
getValue() ..............145
setValue()...............145
copyValue() ..............145
getSystemId() .............146
getClosestExistingParentDir() ........146
parseDirParameter() ...........147
printDirSize() .............147
Appendix K. Logging utility functions
for UNIX systems..........149
Notices ..............151
Support information and feedback 155
Index ...............157
iv Prerequisite Scanner: User's Guide

Figures
1. Output to the command-line interface on
Windows systems ..........25
2. Output to the command-line interface on
UNIX systems............26
3. precheck.log file ...........27
4. prs.debug file on UNIX systems......28
5. prs.trc file on UNIX systems .......29
6. result.txt file on Windows systems .....30
7. result.txt file on UNIX systems ......31
8. Prerequisite Scanner architecture and scanning
process ..............32
9. Running the script and setting the detail
parameter on UNIX systems .......62
10. Running the script without setting the detail
parameter on Windows systems......63
11. precheck.log file with the debug data ....68
12. precheck.log file without debug data ....69
13. prs.debug file on UNIX systems......70
14. prs.trc file on UNIX systems .......71
© Copyright IBM Corp. 2009, 2012 v

vi Prerequisite Scanner: User's Guide

Tables
1. Special characters to represent types of ranges 2
2. Examples of prerequisite properties .....3
3. Basic prerequisite properties categories....4
4. Predefined subtypes ..........6
5. Predefined qualifiers ..........9
6. Supported data type categories and values 15
7. Scanned sections of a configuration file for
Windows .............18
8. Scanned sections of a configuration file for
UNIX ..............19
9. New configuration files ........33
10. Modified product script files .......34
11. Defects fixed in this release .......34
12. Checks and tasks before using a configuration
file for Windows systems ........39
13. Checks and tasks before using a configuration
file for UNIX systems .........40
14. Special characters legend for the Prerequisite
Scanner script ............59
15. Execution problems checklist.......71
16. Predefined product codes ........75
17. Predefined configuration files ......79
18. Predefined categories for prerequisite
properties .............83
19. Common data prerequisite properties ....84
20. Autonomic Deployment Engine data
properties .............88
21. DB2 data properties ..........90
22. MS SQL Server data properties ......90
23. Internet Explorer data properties .....91
24. Network data properties ........91
25. Oracle data properties .........92
26. Operating system data properties .....93
27. Installed software data properties .....104
28. User data properties .........104
29. Windows network data properties ....105
30. UNIX network data properties ......105
31. UNIX collectors ...........107
32. Functions in common_function.vbs ....113
33. Called function for each variable type. 125
34. Logging utility sub routines.......127
35. File utility sub routines ........129
36. File utility functions .........129
37. Other common functions and sub routines for
Windows systems ..........131
38. Parent functions calling ffirstMatch() 131
39. Scripts using getValue() ........132
40. Parent functions calling versionCompare 133
41. Functions in common_function.sh.....135
42. Common functions in multiple files ....141
43. Common functions in TAD722_impl.sh 141
44. Parent functions calling versionCompare 143
45. Logging utility functions on UNIX systems 149
© Copyright IBM Corp. 2009, 2012 vii

viii Prerequisite Scanner: User's Guide

Chapter 1. Prerequisite Scanner overview
IBM®Prerequisite Scanner is a scanning tool that performs identification, checking,
and verification of prerequisites for specified software before the actual
deployment takes place. It scans for hardware and software prerequisites based on
the values set for prerequisite properties. The Scanner displays the results of the
scan in the command-line interface and also saves the results to text files. It also
writes informational, trace, and debugging messages to log files.
Prerequisite Scanner initially checks the operating system of the machine and
verifies whether it is the correct version for the specified software. If it is a
supported operating system, the Scanner continues the prerequisite scan and
generates the results; otherwise, it exits. If any of the individual checks for
prerequisites fail, the overall scan fails.
You can run the Prerequisite Scanner after an installation or at any time to confirm
your current environment. The Prerequisite Scanner does not require that you run
the installation program of the software for which you want to check prerequisites.
You can extend the Prerequisite Scanner to scan for prerequisites that are not part
of the core set of prerequisite checks supplied with the Scanner.
Prerequisite Scanner invokes the following types of scripts depending upon your
platform:
vWindows: VBScript and batch
vUNIX: shell
Note: You cannot run the UNIX scripts on Windows systems even if you have
installed a UNIX-like environment on the Windows machines, for example,
Cygwin.
Prerequisite Scanner architecture
IBM Prerequisite Scanner comprises the following main components: a script to
run in a command-line interface, a set of properties for the prerequisite checks,
prerequisite property configuration files, prerequisite collectors, and prerequisite
evaluators. The results of running the Prerequisite Scanner are available in various
output formats.
Prerequisite properties
Prerequisite properties are the expected values for different software and hardware
prerequisites, required by the products or solutions to be installed. Examples of
prerequisite properties include the total disk space available on the machine, the
set of ports that are not in use on a machine, and the current set of installed
applications.
Because the values for these prerequisite properties can change with different
products, the properties and their values are represented as name value pairs, with
optional qualifiers. They are contained in the prerequisite properties configuration
files. There is only one prerequisite property on each line.
© Copyright IBM Corp. 2009, 2012 1

Prerequisite properties adhere to the following format:
[prefix_identifier.]property_name[.suffix_identifier]=
[[qualifier_name:qualifier_value]]property_value
where:
vprefix_identifier is an identifier for a predefined category of prerequisite
properties as outlined in Table 3 on page 4. This prefix identifier is required by
some of the predefined categories.
vproperty_name is the name of the prerequisite property.
vsuffix_identifier is an optional identifier for a subtype of prerequisite properties as
outlined in Table 4 on page 6.
vqualifier_name is an optional attribute for the prerequisite property. IBM
Prerequisite Scanner uses it to qualify the prerequisite property or type of check
to perform on the prerequisite property.
Note: You can have multiple qualifiers, each separated by a comma. The set of
qualifiers must be enclosed by [] square brackets.
vqualifier_value is the value for the optional attribute. Each qualifier and its value
must be delimited by a :colon.
vproperty_value is the value for the prerequisite property and it can be a string or
integer.
A prerequisite property can have one or many values depending upon the data
type and qualifier as follows:
vA single integer, for example, 8080 to represent the value of a port number.
vA range or group of integers represented by using special characters as outlined
in Table 1.
Table 1. Special characters to represent types of ranges
Special character Description
*Identifies a placeholder for multiple values. For example, ports.*
can represent a superset of ports for both a database product,
ports.DB and IBM WebSphere®Application Server, ports.WAS.
+Identifies that the actual version must at least match the value for
expected version. For example, os.versionNumber=5.0+, means that
the version must be 5.0 or later.
-Identifies that the actual version must at most match the value for
expected version. For example, os.versionNumber=5.0-, means that
the version must be 5.0 or earlier.
.* Identifies that the actual version can match any wildcard value for
the expected version. For example, os.versionNumber=5.*, means
that the version can be 5.0, 5.0.1 or 5.5.
Restriction: On Windows systems, the *wildcard is only supported if used
within a regular expression in the OS Version prerequisite property.
vA string that can represent any of the following values for prerequisite types:
– A numeric value with a unit, for example, 8GB or 10MB
– An application, operating system, architecture, or package, for example, IBM
Lotus Symphony, RedHat Enterprise Linux 5.4, 32-bit,orftp
Note: A string might also comprise multiple values separated by a comma,
for example, a list of applications.
2Prerequisite Scanner: User's Guide

– Either or values represented by one of the following combinations, such as,
True|False, Available|Unavailable,orEnabled|Disabled
Table 2 outlines examples of prerequisite properties.
Table 2. Examples of prerequisite properties
Prerequisite property Explanation
Disk=1GB The amount of free disk space, where:
vproperty_name is Disk
vproperty_value is 1GB
user.isAdmin=True Whether the logged on user belongs to an
Administrator group, where:
vprefix_identifier is user, for user prerequisite
properties
vproperty_name is isAdmin
vproperty_value is True
network.availablePorts.DB=60000-
60005
network.availablePorts.WAS=8080
network.availablePorts.FTP=21
Checks whether ports 60000-60005 are available for
the database server, port 8080 is available for the
WebSphere Application Server, and port 21 for FTP,
where:
vprefix_identifier is network, for general prerequisite
properties
vproperty_name is availablePorts
vsuffix_identifier are DB for available database ports,
WAS for the available WebSphere Application
Server port, and FTP for the available FTP port
vproperty_value is 60000-60005,8080,or21
os.dir.home=[dir:/
home,type:permission]755+
Checks whether the home directory has drwxr-xr-x
permissions, where:
vprefix_identifier is os, for operating system
prerequisite properties
vproperty_name is dir
vsuffix_identifier is home for the directory to check
vqualifier_name are dir and type that qualify the
prerequisite property and type of check
vqualifier_value are home and permission, the values
for the qualifiers
vproperty_value is 755+, that is, the octal digit
representation of the access permissions for the
home directory
You can add or edit predefined prerequisite properties for each product for which
you want to run the Prerequisite Scanner. You can also create custom prerequisite
properties and use Prerequisite Scanner collectors and evaluators as required to
scan for and compare the prerequisite properties.
Chapter 1. Prerequisite Scanner overview 3

Related concepts:
“Predefined qualifiers for prerequisite properties” on page 8
IBM Prerequisite Scanner provides a set of basic qualifiers for some prerequisite
properties in a predefined category. Qualifiers represent attributes of the
prerequisite property that Prerequisite Scanner uses to qualify the prerequisite
property or type of check to perform on that prerequisite property.
Predefined categories of prerequisite properties
IBM Prerequisite Scanner provides a set of basic prerequisite properties for
different categories of data: common, installed software, operating system, user,
connectivity, Internet Explorer, database server, environment variables, and
network including platform-specific properties for Windows and UNIX.
<prefix_identifier> is an identifier for a predefined category of prerequisite
properties.
Table 3 outlines the predefined categories of hardware and software prerequisites.
Table 3. Basic prerequisite properties categories
Data category Description
Required prefix
identifier
Common This category checks common prerequisites such as processor speed,
RAM, disk, and temporary space. This example is the prerequisite
property for checking the operating system:
OS Version=RedHat Enterprise Linux 5.4
None
Installed
software
This category checks installed software prerequisites such as the programs
registered in the Windows registry and whether cygwin and gskit are
installed. This example is the prerequisite property for scanning the
operating system registry for installed programs with locations:
installedSoftware=list_of_installed_programs
None
User This category checks user prerequisites such as whether the logged on
user had administrative rights or is the root user. This example is the
prerequisite property for checking whether the logged on user is a
member of the Administrator group:
user.isAdmin=True
user
Operating
system
This category checks operating system prerequisites such as version,
architecture, total memory, available memory, and total physical memory.
This example is the prerequisite property for checking whether the remote
registry service is running:
os.isServiceRunning.remoteRegistry=True
os
Connectivity This category checks connectivity prerequisites such as whether Telnet is
running and to which IP addresses and ports the Scanner can connect.
None
Network This category checks network prerequisites that can be common across all
platforms such as whether there are ports available. This example is the
prerequisite property for checking whether the 8080 port is available for
IBM WebSphere Application Server:
network.availablePorts.was=8080
network
Windows
network
This category checks Windows network prerequisites such as whether
NetBIOS and DHCP are enabled on the machine, and pinging properties.
This example is the prerequisite property for checking whether at least
one adapter with a valid IP address has NetBIOS enabled as a protocol:
network.netBIOSEnabled=True
network
4Prerequisite Scanner: User's Guide

Table 3. Basic prerequisite properties categories (continued)
Data category Description
Required prefix
identifier
UNIX network This category checks UNIX network prerequisites such as whether
NetBIOS and DHCP are enabled on the machine, and pinging properties.
This example is the prerequisite property for checking whether the local
host responds to the ping protocol:
network.pingLocalhost=True
network
Internet
Explorer
This category checks Microsoft Internet Explorer prerequisites such as the
version. This example is the prerequisite property for checking whether
the Internet Explorer version is 7.0:
internetExplorer.version=7.0
internetExplorer
Database server,
DB2®
This category checks DB2 prerequisites such as the version. This example
is the prerequisite property for whether the DB2 version is at least 9.5:
DB2 Version=9.5.*
DB2
Database server,
Oracle
This category checks Oracle prerequisites such as the version. This
example is the prerequisite property for checking whether Oracle client
version is at least 9.2.0.8:
oracle.Client=9.2.0.8+
Oracle
Environment
variables
This category checks environment variable prerequisites such as whether
the environment variable has been set. This example is the prerequisite
property for checking whether the class path contains the Derby JAR file:
env.classpath.derbyJAR=False
env
Autonomic
Deployment
Engine
This category checks Autonomic Deployment Engine prerequisites such as
whether the Autonomic Deployment Engine is installed or the installation
unit for Tivoli®Integrated Portal. This example is the prerequisite
property for checking whether the installation unit for Tivoli Integrated
Portal Version 2.1.1.0 or 2.1.1.1 is installed on a Windows system:
de.installationUnit=regex{.*C37109911C8A11D98E1700061BDE7AEA.*
|.*TIP 2.1.1.0.*|.*TIP 2.1.1.1.*}
de
Database server,
MS SQL
This category checks MS SQL prerequisites such as the version. This
example is the prerequisite property for checking whether MS SQL Server
version is SQL Server 2008 R2 Developer Edition:
mssql.Server=10.50.1600.1
mssql
Predefined subtypes for prerequisite properties
IBM Prerequisite Scanner provides a set of basic subtypes for some prerequisite
properties in a predefined category. Subtypes further categorize a prerequisite
property such as categorization by application, utility, or service subtype.
Chapter 1. Prerequisite Scanner overview 5

For example, you can have a prerequisite property for available network ports. You
can further categorize that prerequisite property to check available ports for a
database server, application server, or protocol.
<suffix_identifier> is an optional identifier for a subtype in the prerequisite property
name.
Table 4 outlines the predefined subtypes for different categories of prerequisite
properties including the <suffix_identifier>.
Table 4. Predefined subtypes
Prerequisite property
subtype Suffix identifier Platform Description
Valid values for the
subtype
Platform independent network category
network.availablePorts.
app_type
app_type All Use this naming convention
for checking whether the
port or range of ports is not
being listened to or is
available for the app_type
application type.
String to represent app_type,
for example:
vDB2 checks ports for DB2
database server
vWAS checks ports for
WebSphere Application
Server
vftp checks the FTP port
network.portsInUse.
app_type
app_type All Use this naming convention
for checking whether the
port or range of ports is
being listened to or is in use
for the app_type application
type.
String to represent app_type,
for example:
vDB2 checks ports for DB2
database server
vWAS checks ports for
WebSphere Application
Server
vftp checks the FTP port
Operating system category
os.dir.dir_name dir_name UNIX Use this naming convention
for checking the dir_name
file system. The value for
the prerequisite property
uses predefined qualifiers.
String to represent dir_name,
for example:
vtmp
vhome
os.file.
script_name
script_name UNIX Use this naming convention
for checking whether the
script_name script is
available on the machine.
String to represent
script_name, for example:
vbash
vexpect
vgzip
vtar
os.file.
isService
Running.
service_name
service_name Windows Use this naming convention
for checking whether the
service_name service is
running on the machine.
String to represent
service_name, for example:
vremoteRegistry
vDNSClient
vterminalServices
6Prerequisite Scanner: User's Guide

Table 4. Predefined subtypes (continued)
Prerequisite property
subtype Suffix identifier Platform Description
Valid values for the
subtype
os.lib.
lib_name_version
lib_name
_version
UNIX Use this naming convention
for checking that the
supported version of the
lib_name_version library is
installed on the machine.
String to represent
lib_name_version, for
example, in bold:
v32-bit libstdc++.so.#
library
v64-bit libstdc++.so.#
library
v32-bit libXft.so.# library
v32-bit libXtst.so.#
library
v64-bit libaio.so.# library
v32-bit xlC.rte XLC
runtime level
v32-bit xlC.aix50.rte XLC
run time for AIX Version
5.3
v32-bit xlC.aix61.rte XLC
run time for AIX Version
6.1
vAIX®IOCP bos.iocp.rte
library
vbos.loc.iso.en_us, the
ISO code fileset for the
AIX base operating
system
regex {str}, a regular
expression with the input
parameter,str, representing
the search pattern for the
library name, for example:
regex {.*libgcc.*}
Checks whether a version
of the GCC low-level
runtime library, libgcc, for
that operating system exists.
Chapter 1. Prerequisite Scanner overview 7

Table 4. Predefined subtypes (continued)
Prerequisite property
subtype Suffix identifier Platform Description
Valid values for the
subtype
os.package.
package_name
package_name UNIX Use this naming convention
for checking that the
supported version of the
package_name package is
installed on the machine.
String to represent
package_name, for example,
in bold:
vbash shell
vexpect for the TCL
extension package
vlibgcc for GCC low-level
runtime package
vopenssh for the Open
Source secure shell
vopenssl for the Open
Source toolkit for
SSL/TLS
vperl for the Perl scripting
package
vrpm for the RPM or RPM
Build packages
vtelnet for the Telnet
package
vwget for the GNU file
retrieval package
os.space.
dir_name
dir_name UNIX Use this naming convention
for checking the available
disk space for the specified
dir_name file system. The
value for the prerequisite
property uses predefined
qualifiers.
String to represent dir_name,
for example:
vusr
vhome
vtmp
vvar
Predefined qualifiers for prerequisite properties
IBM Prerequisite Scanner provides a set of basic qualifiers for some prerequisite
properties in a predefined category. Qualifiers represent attributes of the
prerequisite property that Prerequisite Scanner uses to qualify the prerequisite
property or type of check to perform on that prerequisite property.
For example, you can have a prerequisite property for a file system. You can
qualify which check to perform for that prerequisite property based on its file
system name and access permissions attributes. You can also qualify which type of
units to use when checking the available disk space based on the file system path
and unit attributes.
Qualifiers support customization to meet the needs of your environment and
prevent the Scanner having to make implicit assumptions about the attributes of
multidimensional prerequisites such as the default path and access permissions.
You can change the values for the predefined qualifiers, but you cannot add new
qualifiers to the existing set of predefined qualifiers for a predefined prerequisite
property.
Qualifiers must adhere to the following format:
[qualifier_name:qualifier_value,qualifier_name:qualifier_value]
property_value
8Prerequisite Scanner: User's Guide

where:
vqualifier_name is an optional attribute for the prerequisite property that IBM
Prerequisite Scanner uses to qualify the prerequisite property or type of check to
perform on the prerequisite property.
vqualifier_value is the value for the optional attribute.
The value for the qualifier can also be a name value pair to support multiple
valid values depending upon user type. For example, different paths for the
home directory depending up whether it is a root or non-root user.
vproperty_value is the value for the prerequisite property and it can be a string or
integer.
Each qualifier and its value must be delimited by a :colon. You can have multiple
qualifiers, each separated by a comma. The set of qualifiers must be enclosed by []
square brackets.
Table 5 outlines the predefined qualifiers for different categories of prerequisite
properties. Some prerequisite properties also use predefined subtypes to further
categorize a prerequisite property.
Important: You cannot use the predefined qualifiers with other predefined
prerequisite properties.
Table 5. Predefined qualifiers
Prerequisite property Platform Description Valid qualifiers and values
Operating system category with predefined subtype
os.dir.dir_name UNIX Checks the dir_name file system based
on the following qualification attributes:
vdir attribute, to determine which file
system to check
vtype attribute, to determine which
attribute of the file system to check,
for example, the <octal_digits> octal
digit representation for the access
permissions to that file system
<dir_name> can represent for example:
vtmp
vhome
String with the following qualifier
format:
[dir:dir_name,
type:permission]
octal_digits+
For example, to check whether the
home directory has drwxr-xr-x
permissions:
os.dir.home=[dir:/home,
type:permission]755+
Chapter 1. Prerequisite Scanner overview 9

Table 5. Predefined qualifiers (continued)
Prerequisite property Platform Description Valid qualifiers and values
os.space.
dir_name
UNIX Checks the available disk space for the
specified dir_name file system based on
one or more of the following
qualification attributes:
vdir attribute, to determine which
path to the file system to check
vunit attribute, to determine which
units for disk space to use
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:
vusr
vhome
vtmp
vvar
String with the following qualifier
format for the file system of a root
user:
[dir:root=dir_path,
unit:unit_name]
disk_space
For example:
os.space.usr=
[dir:root=/usr/ibm/common/acsi,
unit:GB]200
String with the following qualifier
format for the file system of a
non-root user:
[dir:non_root=dir_path,
unit:unit_name]
disk_space
For example:
os.space.home=
[dir:non_root=USERHOME/.acsi_HOST,
unit:MB]200
String with the following qualifier
format, using only one qualifier:
[dir:dir_path]
disk_space MB
For example:
os.space.home=[dir:/home/sat]250MB
Operating system category without predefined subtype
os.mountcheck UNIX Checks whether the file system is
mounted based on the following
qualification attributes:
vdrive attribute, to determine which
directory is the mounted file system
vnosuid attribute, to determine
whether the mount option is set if
the file system is mounted
String with the following qualifier
format:
[drive:dir_name,
mount_option:
false|true]
True|False
For example, to check whether /home
directory is mounted and the nosuid
option is not set:
os.mountcheck=[drive:/home,
nosuid:false]True
10 Prerequisite Scanner: User's Guide