If you have a report of a problem with the TRELLIS Z39.50 server, record the information from the user as normal. Be sure to ask what z39.50 client is being used (Endnote, Bookwhere, Voyager cataloguing, etc). Be sure that they are trying to go to TRELLIS and are not complaining about trying to get to some other Z39.50 site. Then please do the following:
1. Confirm that the Z39.50 service is really down
If the site times out there is a good chance the TRELLIS z39.50 server is down.
2. Double-check that Webvoyage is working. Do a title search at http://trellis1.tug-libraries.on.ca/.
3. If the two z39.50 checks in item 1 above work, it is likely that the user is having problems with their own z39.50 client. Record the information and forward it to Charles Woods for followup; it is not an emergency. Refer the user to z39.50 client information at :
4. If the two Z39.50 checks in #1 fail but WebVoyage is ok, proceed to contact one of the TRELLIS UNIX specialists. Try in this order:
5. The TRELLIS UNIX specialists should go onto the voyager account on l1.uwaterloo.ca. Bill, Gail and Chris have rlogin access.
6. Try starting another incident of the z39.50 daemon:
7. If the z39.50 service still does not work, gather information and contact Endeavor via the standard Endeavor contact routine:
Note: There is a z39.50 log in /m1/voyager/triudb/log/z3950svr_access.log that may help diagnose problem.