FAQs: Troubleshooting Z39.50 Connections and Searches

The Gateway Policy in OPAC Configuration is used for a number of different types of searches. The Z39.50 Search Gateway Type is used to create a search to access Z39.50 server. The searches branch off of Group elements. By default, a KNOWLEDGE_PORTAL search group is delivered with a Z39.50 Sites group list, which is where most libraries define Z39.50 connections. When Z39.50 Search Type Gateway Elements are properly defined, destinations are available for Z39.50 client searches in the following ways.

•

In WorkFlows when you select the SmartPort wizard and select Destinations

•

In the e-Library when you perform broadcast searches for other libraries

•

In the e-Library when you select the Knowledge Portal and the Z39.50 Sites link (one destination only)

There are a few key parts of a Z39.50 Search Type Gateway Element that control your client's search session.

Basic Tab/Available Servers for Access

The Basic tab contains a selection to determine what clients will display this destination for selection. Client names that are available for selection specify the underlying controlling agent, rather than the actual client that is accessing the destination server.

•

WorkFlows controls servers that display whent the SmartPort wizard is selected

•

e-Library controls the available Knowledge Portal selections and "Other Libraries" broadcast search capabilities

Destination Tab

The Destination Tab describes the server itself. Much of this information must be obtained from the library or vendor you are connecting to. (If you are connecting to a SirsiDynix Symphony server, much of the connection information is in the destination's Catalog Zserver policy.)

•

The Database Name is typically UNICORN when you are connecting to a SirsiDynix Symphony server. To limit the connection to a particular library within a multilibrary system, you can specify a valid policy name for the destination Library, such as MADISON.

•

Format specifies a Z39.50 Format to display server results.

•

Z39.50 Search Mapping specifies a Name Mapping policy associated with the server you are connecting to.

Search Field Tab

The Search Field tab for Z39.50 Search and Reference Database Gateway Elements lets you define the searches that display when you use the client to connect to this destination. The Search Fields selections represent Z39.50 Use Attributes (attribute position 1). You can add up to eight different search fields, but you add any that conflict with the specified in the Z39.50 Search Mapping field.

The Operators that you can specify relate to values entered into multiple fields. If you enter multiple words into the same field, an operator is not specified, and the destination server supplies a default operator, if Word List (6) is a supported attribute.

Why am I getting “Error in setting result set format” messages on LC?

This message indicates that the record syntax you have defined in the destination element is incorrect. Correct this by modifying the appropriate gateway (the one associated with the environment of the user profile of the user receiving the message).

For example, modify the Library of Congress Z39.50 gateway element that causes the message to display. On the Destination tab, in the Z39.50 Record Syntax, type the following text.

USMARC

Save your changes and halt and run the server.

How are Library of Congress MARC Tags Mapped into Z39.50 searches?

MARC tag mappings are subject to change.

Use Attribute	Attribute Name	Tags Mapped with Subfields
1	Personal Name	100/abcdegknu4, 400/abcdekqu4, 700/abcdegnqu4, 800/abcdekqu4
2	Corporate Name	110, 111, 410, 411, 710, 711, 810, 811 subfields abcdegknu4
3	Conference Name	111, 411, 711, 811
4	Title	130, 222, 240, 245, 246, 247, 400.410, 411, 440, 700, 710, 711, 730, 740, 760, 762, 765, 767, 770, 772, 773, 774, 775, 776, 777, 780, 785, 786, 787, 800, 810, 811, 830
5	Series Title	440
6	Uniform Title	130
7	ISBN	020/az and subfield z in the following tags: 534, 556, 581, 765, 767, 770, 772, 773, 774, 775, 776, 780, 785, 786, 787
8	ISSN	022/ayz and subfield x in the following tags: 274, 400, 411, 440, 490, 510, 534, 700, 710, 711, 730, 760, 762, 765, 767, 770, 772, 773, 774, 775, 776, 777, 780, 785, 786, 787, 800, 810, 811
9	LCCN	010
12	Other Number	010/abz, 016/az, 035/az and subfield w in the following tags: 760, 762, 765, 767, 770, 772, 773, 774, 775, 776, 777, 780, 785, 786, 787
13	Dewey Call No.	082
16	LC Call No.	05X
17	NLM Call No.	060
20	Other Call No.	084
21	Subject	650, 600, 610, 611, 630, 651, 654, 655, 656
25	MESH Subject	650 indicator 2=2
27	LC Subject	650
28	RVM Subject	650 indicator 2=6
29	Local Subject	650 indicator 2=4
31	Date of publication	260/cg
33	Key Title	222
41	Variant Title	246
42	Former Title	247
43	Abbreviated Title	210
48	National Bibliog. No.	015
50	Govt Doc No.	086
51	Publishers No.	028
54	Language Code	041/abdefgh, 500/a, 546/ab and subfield l in the following tags: 100, 110, 111, 130, 240, 243, 400, 410, 411, 600, 610, 611, 630, 700, 710, 711, 730, 800, 810, 811, 830
55	Geographic Area Code	043
56	Institution Code	040
57	Name and Title	100/abcdefgklnpqtu4, 110/abcdefgklnptu4, 240/adfghklmnoprs, 245/abcfghknps, 400/abcdefgklnptuvx4, 410/abcdefgklnptuvx4, 600/abcdefghklmnopqrstuvxyz234, 610/abcdefghklmnoprstuvxyz234, 700/abcdefghklmnopqrstux345, 710/abcdefghklmnoprstux345, 800/abcdefghklmnopqrstuv4, 810/abcdefghklmnoprstuv4
58	Geographic Name	651
59	Place of Publication	260
60	CODEN	030
63	Note	051/c, 246/i, 249/i, 310/ab, 321/ab, 340/abcdefhi3, 351/abc3, 355/abcdefghj, 362/az, 500/a35, 501/a5, 502/a, 504/ab, 505/agrt, 506/abcde35, 507/ab, 508/a, 510/abcx3, 511/a, 513/ab, 514/abcdefghijkm, 515/a, 516/a, 518/a3, 520/ab3, 521/ab3, 522/a, 524/a23, 525/a, 530/abcde, 533/abcdefmn37
1002	Name	100/abcdekqu4, 110/abcdegknu4, 111/abcdegnqu4, 400/abcdekqu4, 410/abcdegknu4, 411/abcdegnqu4, 534/a, 600/abcdekqu4, 610/abcdegknu4, 611/abcdegnqu4, 651/ab, 700/abcdekqu4, 710/abcdegknu4, 711/abcdegnqu4, 720/ae4, 760/a, 762/a, 765/a, 767/a, 770/a, 772/a, 773/a, 774/a, 775/a, 776/a, 777/a, 780/a, 785/a, 786/a, 787/a, 800/abcdekqu4, 810/abcdegknu4, 811/abcdegnqu4
1003	Author	100, 110, 111, 400, 410, 411, 600, 610, 611, 700, 710, 711, 800, 810, 811
1004	Author Personal Name	100/abcdekqu4, 400/abcdekqu4, 600/abcdekqu4, 700/abcdekqu4, 800/abcdekqu4
1005	Author Corporate Name	110/abcdegknu4, 410/abcdegknu4, 610/abcdegknu4, 710/abcdegknu4, 810/abcdegknu4
1007	Standard Identifier	020/az, 022/ayz, 024/acdz2, 247/x, 400/x, 410/x, 411/x, 440/x, 490/x, 510/x, 534/xz, 556/z, 581/z, 700/x, 710/x, 711/x, 730/x, 760/x, 762/x, 765/xz, 767/xz, 770/xz, 772/xz, 773/xz, 774/xz, 775/xz, 776/xz, 777/x, 780/xz, /785/xz, /786/xz, /787/xz, /800/x, /810/x, 811/x
1009	Subject: personal name	600
1016	Any Keyword fields	010 to 999/all subfields
1018	Name of Publisher	260
1024	Cartographic Math Data	033/bc, 034/b, 255/abcdefg, 507/ab
1027	Standard Tech. Rpt. No.	027
1032	Electronic Location and Access	856

The following are not accessible by SmartPort at this time.

Use Attribute	Attribute Name	Tags Mapped with Subfields
1056	Dissertation Note	502
1074	Subject Name	600, 610, 611 subfields abcdegkquvxyz24
1078	Subject Title	600/fghklmnoprstvxyz2, 610/dfghklmnoprstvxyz2, 611/fghklnpstvxyz2, 630/adfghklmnoprstvxyz2
1079	Subject Topical	600/x, 610/x, 611/x, 630/x, 650/abcdvxyz, 651/x, 655/x, 656/x, 657/x
1185	Credits/Performers

What are some searching tips and limitations of the Voyager server?

For multi-term searches the default operator is adjacent. In other words, multiple search terms are searched as phrases. If you need to search for terms appearing in a field or fields in any order combine the terms with the boolean operator “AND”. This is particularly important when searching for authors which must be entered as: surname first name, as follows.

JOHN SMITH (no records found)

SMITH JOHN (records found)

SMITH AND JOHN (records found)

The truncation symbol is the question mark (?). If you use the truncation symbol you must enclose the entire search statement in double quotes, as follows.

AFRO-AMERICAN WOM? (error message)“AFRO-AMERICAN WOM?” (records found)

Limitations of the Voyager Server

There is a limit of 10, 000 records which may be retrieved in a result set. The records in a result set are sequenced by LCCN number. Since SORT is not supported by the server, the records are output beginning with the oldest records.

Diacritics and special characters may not be captured correctly.

Voyager is supposed to support SCAN (browsing), but it does not work with either SirsiDynix Symphony clients or other Z39.50 clients.

Authorities are not searchable.

How do I limit a search to a particular library on the destination server?

It is possible to limit a search to a particular library when you are setting up a connection to another SirsiDynix Symphony Z39.50 server. However, since a separate destination will need to be set up for each library, this feature should be restricted to libraries which have a very specialized subject concentration, such as a law or medical library, or which need to be separated out for some other unique purpose.

If a SirsiDynix Symphony Z39.50 Server is specified when a Z39.50 destination is created, a database name of UNICORN is typically specified. When the database name is UNICORN, searches default to the entire catalogue. If the database name is anything other than UNICORN, the destination SirsiDynix Symphony Zserver software will check the database name against its Library policies and if it finds a Library policy Name match, it will limit searches to that specific library. If a match is not found, a diagnostic message displays indicating that the database does not exist, along with the attempted match name.

Contact your destination server library prior to setting up the destination to get the valid Library policy name.

I cannot connect to my SmartPort destination. Could it be an issue with my firewall?

If you are unable to connect to a Z39.50 destination with SmartPort and you have configured the destination properly, the problem may be associated with a firewall at your site. If you have a firewall and want to test access, issue the following command from the UNIX prompt.

$ telnet zcat.oclc.org 210

You should see the following response.

Trying...Connected to zcat.oclc.org. Escape character is ‘^]’.

If you do not see this response, either the server is down or your firewall is preventing you from making a connection. The solution is to ask your network administrator to open up port 210 or another port number in the firewall. If you see this response, repeat your test but replace the host and port number above to match your destination. If you are not able to connect, it is possible that the firewall at your destination is preventing a connection.

How can I modify the Z39.50 purpose format policy to display additional tags in the Search Results list?

Sites may wish to modify the display of records in the Search Results list retrieved through a Z39.50 search to add tags 260 (publication info) and 250 (edition) to the display if present. This can be accomplished by modifying the Z39.50 purpose Format policy that is used for a Z39.50 destination.

To add these tags to the display, modify the appropriate Format policy as follows.

Field	Value	Field	Value
Entry ID	260	Entry ID	250
Entry Number	260	Entry Number	250
Entry Type	NONE	Entry Type	NONE
Display	YES	Display	YES
Entry Punctuations	NO	Entry Punctuations	NO
List Field1 Rank	NONE	List Field1 Rank	NONE
List Field2 Rank	NONE	List Field2 Rank	NONE
List Field3 Rank	1	List Field3 Rank	NONE
List Field4 Rank	NONE	List Field4 Rank	1

In order to take advantage of this change, SmartPort wizard users need to go to the Properties area and change the default values for Hit Limit for Brief Display. Values such as the following are recommended.

Field	Value
Single server limit	5
Multi-server limit	3
Browse terms limit	8

For example, search results from a search on JOHN GRISHAM and FIRM returns the following records.

The firm [braille] /Grisham, John.New York : Doubleday, c1991.1st ed.

The firm /Grisham, John.London : Arrow, 1991.Uncorrected proof

The firm [sound recording] /Grisham, John.[Washington, DC] : Library of Congress, 1991.

The firm /Grisham, John.New York : Doubleday, [c1991].Large Print Book Club ed.

The firm [videorecording] /Hollywood, Calif. : Paramount, 1993.

Because the publication info (260) is almost always present, while the edition field (250) is only rarely present, in these instructions the former is defined with a higher display priority, so that it displays ahead of the edition statement, even though this reverses tag order.

Is my SirsiDynix Symphony Z39.50 Catalog Server functioning properly?

Most system administrators never check the status of their Z39.50 server. The only time you discover a problem is when someone from another library calls you to complain about a connecting to or searching your server. The /Unicorn/Zserver directory contains log files that need to be examined for potential problems associated with access to the Z39.50 catalog server.

Maximum Number of Client Connections Has Been Exceeded

Look for the following message in your *.zcnt files.

19990930204012|198.76.201.189|51831|start|19990930204012|198.76.201.189|51831|end|999|Too many clients already attached|

Your Z39.50 server is configured to accept a maximum number of client connections in the Module Configuration wizard on the Config toolbar in WorkFlows. Because certain clients do not disconnect properly from your server some connections will remain open until the next halt and run of your Z39.50 server. The solution to the problem is to increase the number of client connections allowed by the server. Given that each client connection is associated with a zserver user, an increase in the number of client connections in the configuration requires a corresponding increase in the number of zserver users. Please contact SirsiDynix Customer Support for instructions on how to create additional zserver users.

Unable To Connect To A SirsiDynix Symphony Server With SmartPort

If you experience a problem connecting to a SirsiDynix Symphony server with SmartPort, make sure that the Result Naming field in the gateway element description is set to No.

Why can’t I connect to BADADUQ and COPAC?

If you attempted to create gateway elements for BADADUQ (University of Quebec) and COPAC (catalogue of the largest university research libraries in the UK and Ireland), you may see the following message.

PDU is not the required type

At the same time, another message appears at the top but records are not displayed.

QUEBEC found 21 records

The BADADUQ server is not working correctly.

Other Z39.50 clients experience the same type of problems.

For COPAC, unless you are an authorized user, you will not be able to display MARC records because COPAC does not support MARC output for outside users. The only record format they output to the public is SUTRS, which cannot be displayed by SirsiDynix clients.