README for HP Neoview Release 2.4

and JDBC connection attributes or SET SERVICE command is ignored by the Release 2.4
NDCS server. An error is returned to the client application.
• The ADD SERVICE command now uses the threshold values from the WMS system
configuration if values are unspecified in the command.
In Release 2.3, the default for service-level thresholds, MAX_CPU_BUSY and
MAX_MEM_USAGE, was zero, which meant that WMS used the thresholds of the system
configuration, if set, or the internal default thresholds of 100% for MAX_CPU_BUSY and
85% for MAX_MEM_USAGE.
In Release 2.4, the WMS system configuration is automatically set to 100% for
MAX_CPU_BUSY and 85% for MAX_MEM_USAGE. When a service is added, WMS does
not use values from the WMS system configuration, but uses the threshold values set for
that particular service. If a threshold value is explicitly set to 0, the threshold is not checked.
• Pre-execution control
In Release 2.3, WMS decided whether to allow a query to execute, put a query in a queue
(waiting state), or reject a query by comparing periodic snapshots of available CPU and
memory system resources to system/service level parameters, MAX_CPU_BUSY and
MAX_MEM_USAGE. After the comparison, queries were allowed to execute or be queued
for later execution.
In Release 2.4, new commands allow you to apply a larger set of rules to the decision-making
process. These additional rules can be applied to service levels and may include optional
actions.
• Execution control
In Release 2.3, an executing query's elapsed time was periodically checked to determine if
it had been running longer than the value specified in the system/service level attribute,
EXEC_TIMEOUT. If the query had been running longer than specified in EXEC_TIMEOUT,
it was canceled. If EXEC_TIMEOUT was not set, the query was allowed to run indefinitely.
Also in Release 2.3, a query in the waiting queue was periodically checked to determine
whether the query had been waiting to execute longer than specified by the attribute
WAIT_TIMEOUT. If the query had been waiting longer than specified in WAIT_TIMEOUT,
it was canceled. If WAIT_TIMEOUT was not set, the query remained in the waiting queue
indefinitely.
In Release 2.4, new commands allow you to apply a larger set of rules based on compiler
estimates for the decision-making process. These additional rules can be applied to service
levels and may include optional actions.
• Additional output columns for the INFO WMS command:
— MAX_ROWS_FETCHED
— EXEC_TIMEOUT
— WAIT_TIMEOUT
— HOLD_TIMEOUT
— RULE_INTEVAL
• Additional output columns for the INFO SERVICE and STATUS SERVICE commands:
— MAX_ROWS_FETCHED
— HOLD_TIMEOUT
• Additional output columns for the STATUS QUERY and STATUS QUERIES commands:
— QUERY_SUBSTATE
— EST_TOTAL_MEM
— EST_RESRC_USAGE
— CMP_AFFINITY_NUM
16