HP Neoview Release 2.5 Software - Manual (Page 267)

Glossary
active command A command used by the System Offender to query the database (for example, STATUS CPU
PROCESS ALL) for
offending processes . The active command appears underneath the System
Offender tab. The active command changes depending on the area you click in the System
Monitor. For more information, see “Find Offending Processes and Queries” (page 194) and
“Control the Refresh of System Offender” (page 208) .
Ad-hoc Report In Metric Miner, a scratchpad that can be used to run SQL statements and create reports. To
create a report, you enter a SQL statement into the Ad-hoc Report tab, run the statement,
configure report information in the Report Configuration dialog box, and save the report
using a different name. See also
Metric Miner and report .
Admin_Load_
DataSource One of two default data sources for the Neoview platform. Admin_Load_DataSource is the
default data source used by the Neoview Transporter. You cannot start, stop, or delete the
Admin_Load_DataSource. This data source is always started so that HPDM can continue
managing connectivity when all other data sources are stopped. Contrast with
TDM_Default_DataSource .
administrator A user who belongs to a role with administrative privileges. By default, these roles are
administrators:
• SUPER.SUPER
• SUPER.SERVICES
• ROLE.DBA
In addition, administrator users can grant administrator privileges to other users. For the current
release, HPDM allows data-source management tasks to be performed only by roles having
operator privileges, and not by users or roles having ADMIN privileges. See
operator privilege .
For more information about administrator users, see the Neoview Workload Management Services
Guide.
alert An alarm or incident report generated by the problem-management software on the Neoview
platform. Each row in the Alerts tab data grid represents an alert. For more information, see
“Understand Alerts” (page 182) .
area A broad category of features that you can manage or monitor using HPDM. See “Select an
Area” (page 35) .
association server The logical component that starts and manages NDCS SQL servers and associates a client
connection request with a specific NDCS SQL server in a data source.
MXAS2 and MXOAS are
the association servers. See also “Learn About the Association Servers” (page 156) .
configuration
server The logical component that manages the NDCS configuration data. The association server
communicates with the configuration server to retrieve the NDCS configuration values.
connection When a user interaction requires interaction with a system, the relevant code uses the system
definition for that system to transparently establish one or more ODBC connections, as needed.
data grid A tabular presentation of system data. HPDM data grids provide special features for displaying
and manipulating data. The Alerts tab, System Offender tab, and SQL Whiteboard Statement
Details
pane display information in a data grid. Tabs in the Database area do not provide
data-grid features. For more information about data-grid features, see “About Data Grids”
(page 48) .
data source A logical name that defines the information required to access data. On the client side, it defines
the driver name, network address, and specific attributes, such as the catalog and schema names.
On the server side, it defines startup values, the number of servers in a pool, DEFINEs, Neoview
SQL control statements, and resource management policies.
database user A person or an application that can use a Neoview client, such as ODBC, NCI, or HPDM, to
log on to the Neoview database and operate on database objects. A database user can have one
or more database roles (each having a name of the form ROLE.name), which determine the
objects to which the user has access and the privileges the user has in relation to those objects.
Contrast with
platform user . See also locally authenticated database user and remotely
authenticated database user .
267