setmasterproperty

Use the setmasterproperty subcommand to set the master properties for the database set.

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 setmasterproperty
dbset_name [ -user_db_name user_db_name] cq_login cq_password master_property new_value

Description

The setmasterproperty subcommand sets the master property for the database set. Use the setmasterproperty 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® 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 set.
new_value
Specifies the value for the master property.

Example

In the following example, the setmasterproperty subcommand sets the REMEMBER_PASSWORD flag for the mydbset database set.
installutil setmasterproperty mydbset admin "" REMEMBER_PASSWORD false

Upon any successful login to a Rational ClearQuest database, the Rational ClearQuest Client checks the REMEMBER_PASSWORD master property for the database set. If the value is discovered to be FALSE, then any saved password is removed and a dialog is displayed to the user warning them of the change. The connection is also marked in an existing file stored to disk so that, in the future, the user is not allowed to use "Remember Password" for connections to the database set. Administrators can also choose to later re-enable this feature for their users by setting the REMEMBER_PASSWORD master property to "TRUE". After logging in one more time, users are able to then use the "Remember Password" feature.

Therefore, some Rational ClearQuest Client users do not have their old saved passwords removed and the feature disabled until after they login using a saved password. There is no way for the Rational ClearQuest Client to check if the feature has been disabled until after establishing a connection to the Rational ClearQuest database. It can be guaranteed that the saved passwords are removed immediately after login.

See also

installutil


Feedback