After you use snrfck to create or update a service name direction file, you can implement the modified file on the DirectConnect server, as described in the following sections.
To implement a new service name redirection file
or copy a modified file
Use snrfck to create a new file, or to modify the existing file and validate it.
Stop the DirectConnect server.
Copy or rename the file, as applicable.
Restart the server.
You can use snrfck to create or update a service name redirection file, validate the file, and send it to a running DirectConnect server.
Using this method allows you to replace the contents of the snrf.tbl file that is read when the server starts, write the contents to disk, and update the memory table so the changes take effect immediately.
To update to a running server using snrfck
Use snrfck to create a new file or to modify the existing file and validate it.
Send the file to the server using the following syntax:
snrfck [-v][-?]|-h] [-t[-oresult]] [-Ssvc -Uuser -Aappl] -ifile
or
snrfck -c -Ssrv -Uuser -Ppwd ifile
where:
-v displays the program version only.
-? or -h displays this message.
-t tests the update capability.
-oresult outputs the file for results of the update test (this has no effect if you do not specify -t).
-Ssvc, -Uuser, and -Aappl are optional arguments used to test the redirection search.
-ifile indicates the service name redirection file to be tested.
-c submits the file to the server srv for an immediate update, using the specified login pwd.
-Ssrv indicates the server name.
-Uuser indicates the user name.
-Ppwd indicates the password for the user name.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
