Neoview Workload Management Services Guide (R2.4)

connection attribute expressions of more than one connection rule defined in WMS. However,
the NDCS server evaluates each connection rule in the order in which you have associated the
connection rules with services. The NDCS server assigns the client session to the service that is
associated with the first connection rule that matches the connection attributes of the client
session.
If user-defined connection rules exist in WMS but the connection attributes of the client session
do not match any of the connection rules, the NDCS server assigns the client session to the default
service, HP_DEFAULT_SERVICE, and WMS sets the warning level to low for the client session
and saves warning information in its shared memory. Running a STATUS QUERIES WARN
command reveals the following reason for the warning:
NO MATCHING CONNECTION RULES
For more information, see “Displaying Warning Information” (page 75).
If there are no user-defined connection rules in WMS, the NDCS server assigns the client session
to HP_DEFAULT_SERVICE, and WMS does not set a warning level or save warning information.
For more information about HP_DEFAULT_SERVICE, see the “Default Service” (page 27).
If any of the connection rules are modified in WMS during the client session, the NDCS server
reloads the connection rules from WMS after a query in the session completes executing. The
NDCS server uses the reloaded set of connection rules to determine which service to assign to
the next query in the session.
To implement connection rules in WMS, see these sections:
• “Adding a Connection Rule” (page 42)
• “Associating a Connection Rule With a Service” (page 47)
Adding a Connection Rule
Use the ADD RULE CONN command to define a connection rule in WMS. For example, these
ADD RULE CONN commands define the connection rules, CONNRULE1 and CONNRULE2:
NS%ADD RULE CONN CONNRULE1 (SESSION JOB2468, LOGIN ROLE.USR1);
--- WMS operation complete.
NS%ADD RULE CONN CONNRULE2 (SESSION JOB2468, LOGIN ROLE.USR2);
--- WMS operation complete.
NS%
Both CONNRULE1 and CONNRULE2 have two connection attribute expressions. The first
expression, SESSION, defines the same session name, and the second expression, LOGIN, defines
a different client login role for each connection rule.
Here are some things to consider when defining connection rules:
• “Specifying the Connection Attribute Expressions” (page 42)
• “Specifying a Warning Level for the Connection Rule” (page 43)
• “Specifying an Action for the Connection Rule” (page 44)
• “Adding a Comment for the Connection Rule” (page 44)
For the syntax, see the “ADD RULE CONN Command” (page 86).
Specifying the Connection Attribute Expressions
You can specify up to four different expressions in a connection rule to define these connection
attributes:
• Session name using the SESSION expression
• Application name using the APPL expression
• Client login role using the LOGIN expression
• Data source name using the DSN expression
42 Configuring Rules