Neoview Workload Management Services Guide (R2.4)

Table B-1 New WMS Commands for Neoview Release 2.4 (continued)
New WMS CommandsFunction
— “HOLD Command” (page 113)
◦ HOLD QUERIES SERVICE
— “RELEASE Command” (page 125)
◦ RELEASE QUERIES SERVICE
To hold or release all queries in a service:
— “ALTER WMS RESET STATS Command”
(page 109)
— “STATUS SERVICE SEGMENT STATS
Command” (page 147)
— “STATUS WMS SEGMENT STATS Command”
(page 151)
To display aggregated statistics about the queries running
in WMS:
What Changed for This Release
The following functionality changed for this release:
Table B-2 Comparison of WMS Functionality Between Neoview Release 2.3 and 2.4
WMS Functionality in Neoview Release 2.4WMS Functionality in Neoview Release 2.3
Permission to run WMS commands:
Only administrators are permitted to run any WMS
command. By default, administrators include ROLE.DBA
and the super IDs, super.services and super.super. Users
other than administrators may execute only these
commands:
• INFO WMS
• STATUS QUERIES
• STATUS QUERY
• STATUS WMS
All types of users are permitted to run WMS commands.
SET SERVICE command:
SET SERVICE is no longer a valid command. A new
mechanism, which is transparent to client applications,
removes the capability of client applications to set their
service and allows an administrator to specify
client-to-service name associations for the Neoview
platform based on connection rules.
Anytime a client application connects to the Neoview
platform, the NDCS server automatically assigns a service
name to the client application based on connection rules
that you, the administrator, defined. If a client application
from a previous release tries to set its service, the NDCS
server ignores the SET SERVICE command (or ODBC or
JDBC connection attribute) and returns an error to the
client application.
Each ODBC or JDBC client application used the SET
SERVICE statement to associate SQL queries with a
service. If the service specified by the SET SERVICE
statement did not exist, WMS first looked for a service
name that matched the second part of the client role, such
as MGR in ROLE.MGR. If WMS found a service name
that matched the role, WMS assigned the queries to that
service. If WMS did not find a service name that matched
the role, WMS assigned the queries to the default service,
HP_DEFAULT_SERVICE.
Default threshold values:
A service uses threshold values from the WMS system
configuration if you do not specify those values in the
ADD SERVICE command. By default, the WMS system
configuration is set to 100% for MAX_CPU_BUSY and
85% for MAX_MEM_USAGE. If you explicitly set a
threshold value to zero, it means that WMS does not check
the threshold.
The default values for the system resource thresholds,
MAX_CPU_BUSY and MAX_MEM_USAGE, was zero,
which meant that you had not altered the WMS system
configuration and that WMS was using the internal values
of 100% for MAX_CPU_BUSY and 85% for
MAX_MEM_USAGE.
156 New and Changed Information