Use the getmasterproperty subcommand to retrieve the master
properties for the database set specified by the setmasterproperty subcommand.
Applicability
Platform: Windows (Its value
is honored by all clients on all platforms, but installutil can only be run
on Windows.)
Command type: installutil subcommand
Synopsis
- installutil getmasterproperty
- dbset_name [ -user_db_name user_db_name] cq_login cq_password master_property | -all
Description
The getmasterproperty subcommand
retrieves the master property for the database set specified by the setmasterproperty subcommand.
Use the getmasterproperty subcommand with the following master_property
features.
- HOOKS_SEE_ALL_RECORDS. Specifies whether queries executed by hooks
should ignore security contexts in order to filter result sets. When TRUE,
records are included in the result set even if their security contexts would
have prevented the user from normally accessing them. When FALSE, the queries
executed by hooks behave as they would if run by the current user. Thus, records
the user would not normally be allowed to see are not in the result set.
Note: Feature
level 5 schema sets this value to TRUE, by default. Feature level 6 schema
sets this value to FALSE, by default.
- HOOKS_SEE_ALL_USERS. Specifies whether user and group queries executed
by hooks should ignore group membership in order to filter result sets. When
TRUE, user and group information (depending on query type) are included in
the result set even if the current user is not a member. When FALSE, the user
and group queries executed by hooks behave as they would if run by the current
user.
Note: Feature level 5 schema sets this value to TRUE, by default. Feature
level 6 schema sets this value to FALSE, by default.
- REMEMBER_PASSWORD. Specifies the Remember Password master property
for the database set. The master property determines if any Rational® ClearQuest® Eclipse
client connecting to any user database in that database set can save their
password.
- SOFT_QUERY_LIMIT. Specifies the number of rows equal to the soft
limit for queries to return. Setting a limit of 0 for the property value is
interpreted as allowing an unlimited number of rows.
- HARD_QUERY_LIMIT. Specifies the absolute number of rows equal to
the hard limit for queries to return. Setting a limit of 0 for the property
value is interpreted as allowing an unlimited number of rows.
Options and Arguments
- dbset_name
- Name of the database set or connection that contains the database to be
enabled for LDAP.
- -user_db_nameuser_db_name
- Specifies the user database to which the property applies. Default: the
property applies to all user databases.
- cq_login
- Rational ClearQuest login
name of the administrative user. This user must have Super User privileges
and be marked for Rational ClearQuest authentication.
- cq_password
- Rational ClearQuest password
for the administrative user. To specify a null password enter an empty set
of double quotes.
- master_property
- Specifies the name of the master property to get.
- new_value
- Specifies the value for the master property.
Example
In the following example, the
getmasterproperty subcommand
returns the REMEMBER_PASSWORD property for the
mydbset database set.
This master property determines if any
Rational ClearQuest Eclipse
client connecting to any user database in that database set can save their
password.
installutil getmasterproperty mydbset admin "" REMEMBER_PASSWORD
Starting test getmasterproperty
REMEMBER_PASSWORD="TRUE"
Exit code 0 for test getmasterproperty
Upon any login, the Rational ClearQuest Eclipse
client checks the REMEMBER_PASSWORD property and if false, the client clears
any password from the disk and sets any password in memory to zero associated
with that database set.
The client can cache this value along with the
rest of the connection information. This saved flag is then used by the client
to determine if users are allowed to save passwords.