Adaptive Server uses the following rules to resolve conflicting precedence when multiple execution objects and execution classes have the same scope.
Execution objects not bound to a specific execution class are assigned these default values:
Entity type |
Attribute name |
Default value |
|---|---|---|
Client application |
Execution class |
EC2 |
Login |
Execution class |
EC2 |
Stored procedure |
Execution class |
EC2 |
An execution object for which an execution class is assigned has higher precedence than defaults. (An assigned EC3 has precedence over an unassigned EC2).
If a client application and a login have different execution classes, the login has higher execution precedence than the client application (from the precedence rule).
If a stored procedure and a client application or login have different execution classes, Adaptive Server uses the one with the higher execution class to derive the precedence when it executes the stored procedure (from the precedence rule).
If there are multiple definitions for the same execution object, the one with a narrower scope has the highest priority (from the scope rule). For example, the first statement gives precedence to the “sa” login running isql over “sa” logins running any other task:
sp_bindexeclass sa, LG, isql, EC1
sp_bindexeclass sa, LG, NULL, EC2
