You can modify several master properties in a Rational® ClearQuest® database set if your account
has the Super User privilege.
Use the
installutil getmasterproperty,
installutil setmasterproperty,
installutil
getmasterpropertytofile, and
installutil setmasterpropertyfromfile subcommands
to get and set the following master properties for a database set:
- HOOKS_SEE_ALL_RECORDS
- Specifies whether queries run by hooks ignore security contexts
when the queries filter result sets.
Valid values:
- TRUE
- Queries that are run by hooks return records in result sets, even
if the security contexts of the records prevent the user from directly
accessing the records.
- FALSE
- Queries that are run by hooks behave as they do when run by the
current user. This means that records the user is not allowed to see
based on security context are not included in the result sets.
Default values:
- Feature level 5 schemas initialize this value to TRUE.
- Feature level 6 schemas initialize this value to FALSE.
- HOOKS_SEE_ALL_USERS
- Specifies whether user and group queries that are run by hooks
ignore group membership when the queries filter result sets.
Valid
values:
- TRUE
- User and group queries that are run by hooks can include user
and group information in the result sets. This result is true even
if the current user is not a member.
- FALSE
- User and group queries that are run by hooks behave as they would
if run by the current user.
Default values:
- Feature level 5 schemas initialize this value to TRUE.
- Feature level 6 schemas initialize this value to FALSE.
- REMEMBER_PASSWORD
- Specifies whether a ClearQuest client
that is connecting to a user database in the database set can save
their password across login sessions.
Valid values:
- TRUE
- Enables the remember-password feature.
- FALSE
- Disables the remember-password feature.
Important: When a ClearQuest client logs on to a database,
the client checks the REMEMBER_PASSWORD master property. If the value
is FALSE, then any saved password is removed and a dialog box displays
that notifies the user of the change. In addition, the connection
is marked in an existing file on the client computer so that the remember-password
feature is not available the next time the user connects to the database
set. The result is that the saved password is not removed on the client
computer and the feature is not disabled until after the user logs
on again with the saved password. There is no way for a ClearQuest client to check whether the
feature is disabled until after the client establishes a connection
to the user database. After a user logs on, any saved passwords are
immediately removed.
- SOFT_QUERY_LIMIT
- Specifies the number of rows equal to the soft limit for queries
to return. Setting a limit of 0 for the master property value allows
an unlimited number of rows.
- HARD_QUERY_LIMIT
- Specifies the number of rows equal to the hard limit for queries
to return. Setting a limit of 0 for the master property value allows
an unlimited number of rows.
- OSLC_FRIENDSCONFIG
- Stores content that is used to establish and manage OSLC server
friends to this server. The information is based on content in the friendsconfig.rdf file.
- OSLC_MAPPINGS
- Stores a list of OSLC mapping configurations, OSLC mappings, and
information that is used to prefill field values when you open the
creation dialogs for associated OSLC 2.0 projects. The information
is based on content in the oslc-mappings.xml configuration
file.
- OSLC_OAUTHCONSUMERS
- Stores content that is used to manage which OSLC OAuth consumers
are authorized to access this server. The information is based on
content in the oauth-consumers.rdf file.
- OSLC_PROJECTAREALINKS
- Stores content that is used to manage which remote OSLC project-area
links exist for different user databases. The information is based
on content in the project-area-links.rdf file.