You can test the redirection process by supplying values for requested_service, user_id, and application_name, subject to the following restrictions:
You must specify values for user_id and application_name.
You can use a null argument for requested_service to allow matching on a null service.
When you supply these values, snrfck displays the sorted entries and the assigned service to which the request would be directed.
For example, suppose you use the preceding sample file and enter the following:
snrfck -itestfile -Sdb2 -Ujane -Aisql
where:
db2 is the requested service.
jane is the user ID.
isql is the application name.
You receive the match shown in Table 6-6:
requested_service |
user_id |
application_name |
assigned_service |
|
---|---|---|---|---|
1: |
<tab> |
root |
ksh |
svc_ksh |
2: |
db2 |
joe |
isql |
svc_db2a |
3: |
db2 |
jane |
isql |
svc_db2b |
4: |
db2 |
sonia |
Omni |
svc_db2c |
5: |
db2 |
ramon |
Omni |
svc_db2d |
6: |
db2 |
sven |
* |
svc_db2gen |
7: |
other |
* |
* |
svc_other |
The following is displayed:
assigned service for (db2,jane,isql): svc_db2b
If the service redirection comparison does not find a match, the value returned for assigned_service is simply the requested_service value.
For example, suppose you use the preceding sample file and enter:
snrfck -itestfile -Sdb2 -Uramon -Aisql
where:
db2 is the requested service.
ramon is the user ID.
isql is the application name.
You receive the failed entry match shown in Table 6-7:
requested_service |
user_id |
application_name |
assigned_service |
|
---|---|---|---|---|
1: |
<tab> |
root |
ksh |
svc_ksh |
2: |
db2 |
joe |
isql |
svc_db2a |
3: |
db2 |
jane |
isql |
svc_db2b |
4: |
db2 |
sonia |
Omni |
svc_db2c |
5: |
db2 |
ramon |
Omni |
svc_db2d |
6: |
db2 |
sven |
* |
svc_db2gen |
7: |
other |
* |
* |
svc_other |
assigned service for (db2,ramon,isql): db2 |
The following is displayed:
assigned service for (db2,jane,isql): svc_db2b