The snrfck basic command requires only the -i option. When you use this option, snrfck reads the redirection file, validates each line, and flags the first incorrect line it encounters.
For example, suppose you enter:
snrfck -ic:\cfg\testfile
where:
cfg is the directory containing the service name redirection file.
testfile is the service name redirection file.
The path cfg\testfile is
shown as a PC-based system in this example and in the remainder
of the examples in this chapter.
Next, assume the redirection file contains the entries shown in Table 6-4:
requested_service |
user_id |
application_ name |
assigned_service |
---|---|---|---|
AS400 |
Bob |
isql |
as1 |
AS400 |
* |
isql |
as2 |
AS400 |
Bob |
isql |
as2 |
AS400 |
* |
Omni |
omniA |
AS400 |
* |
Power Builder |
powerB |
DB2 |
* |
Omni |
db2omni |
DB2 |
* |
* |
db2gen |
<tab> |
* |
* |
as2 |
In this example, snrfck returns:
c:\cfg\testfile: line3: duplicate/ambiguous row
If the file does not contain errors, the rows are sorted in the order used in the redirection operation and printed to the current window.
Table 6-5 shows an example of a correctly formatted access service name redirection file, as output by snrfck. The snrfck utility adds line numbers for clarity.
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 |