If you inadvertently create a service name redirection file in which an assigned access service name is not uniquely specified, the system uses precedence rules shown in Table 6-2 to resolve the problem. The first rule defines the highest precedence, the eighth one the lowest.
Rule |
Description |
|---|---|
1 |
All columns are explicitly defined. |
2 |
requested_service and user_id are specified; application_name uses a wildcard character. |
3 |
requested_service and application_name are specified; user_id uses a wildcard character. |
4 |
user_id and application_name are specified; requested_service uses a wildcard character. |
5 |
Only requested_service is specified; user_id and application_name use wildcard character. |
6 |
Only user_id is specified; requested_service and application_name use wildcard character. |
7 |
Only application_name is specified; requested_service and user_id use wildcard character. |
8 |
Nothing is specified; requested_service, user_id, and application_name use wildcard character. |
A null-requested
service is treated as any other explicitly-specified service.
| Copyright © 2008. Sybase Inc. All rights reserved. |
|
|