List Info

Thread: zoom perl error




zoom perl error
user name
2007-06-26 20:47:39
I get the following error:

ZOOM error 10003 "Decoding failed" (addinfo: "ODR code 8:23 element=      ;           ;   ") from diag-set 'ZOOM'

When executing the following trivial program (based upon the documentation)

$conn = new ZOOM::Connection(';libprd.uits.indiana.edu', 2200);
$rs = $conn->search_pqf('^C1323935')
    or die $conn->errmsg();

my $n = $rs->size();
print "found $n records:n";
print $rs->record(0)->;render if $n;


Any clue where to go from here ?  This the latest yaz and zoom code downloaded today

Geoffrey
Re: zoom perl error
country flaguser name
Denmark
2007-06-27 01:47:02
Geoffrey Brown wrote:
> I get the following error:
> 
> ZOOM error 10003 "Decoding failed" (addinfo:
"ODR code 8:23 
> element=                    ") from diag-set
'ZOOM'
> 
> When executing the following trivial program (based
upon the documentation)

With yaz-client I get:

adampeanut:~$ yaz-client libprd.uits.indiana.edu:2200
Connecting...OK.
Sent initrequest.
Connection accepted by v3 target.
ID     : Unicorn GL3.1 Standard
Name   : SIRSI Corporation
Version: 3.0
Options: search present delSet scan sort namedResultSets
Elapsed: 1.009381
Z> f ^C1323935
Sent searchRequest.
Received SearchResponse.
Search was a success.
Number of hits: 1, setno 1
records returned: 0
Elapsed: 0.531149
Z> s
Sent presentRequest (1+1).
Records: 1
[DEFAULT]Record type: USmarc
(Length implementation at offset 22 should hold a digit.
Assuming 0)
01160nam  2200325 a 4500
001 ALE4171BB
008 990408s1999    inua          001 0 eng d
010    $a    99060546
020    $a 0672316498
035    $a (InU)ALE4171BB
035    $a (OCoLC)ocm41237183
040    $a JBU $c JBU $d ABC
090    $a QA76.9.H85 $b C66 1999
092    $a 004.019 $b Coo
100 1  $a Cooper, Alan.
245 14 $a The inmates are running the asylum / $c Alan
Cooper.
260    $a Indianapolis, IN : $b Sams, $c c1999.
300    $a 261 p. : $b ill. ; $c 24 cm.
500    $a "Why high-tech products drive us crazy and
how to restore the 
sanity"--cover.
500    $a Includes index.
591    $a BB: M222 T
650  0 $a Human-computer interaction.
650  0 $a Consumers $x Effect of technological innovations
on.
650  0 $a Human-machine systems.
998    $a 4/8/1999 $b 8/23/1999 $c 10/5/1999
596    $a 1 6 37 48
926    $a B-WELLS $b CHECKEDOUT $c QA76.9.H85 C66 1999 $d
NORMAL $e 
10/22/2007 $f 1
926    $a B-BUSSPEA $b STACKS $c QA76.9.H85 C66 1999 $d
NORMAL $f 1
926    $a FORTWAYNE $b STACKS $c QA76.9.H85 C66 1999 $d
NORMAL $f 1
926    $a SOUTHEAST $b STACKS $c QA76.9.H85 C66 1999 $d
NORMAL $f 1

nextResultSetPosition = 2
Elapsed: 0.341331
Z> format nx
Z> format none
Z> s 1+1
Sent presentRequest (1+1).
Decoding incoming APDU: Malformed data (code 8:23)
Element path: presentResponse databaseOrSurDiagnostics ?
record ? 
databaseRecord
[Near 44]
Packet dump:
---------
     0: [25] len=1204       tl=1, ll=3 cons=1
     4:     [24] len=1       tl=1, ll=1 cons=0
     7:     [25] len=1       tl=1, ll=1 cons=0
    10:     [27] len=1       tl=1, ll=1 cons=0
    13:     [28] len=1191       tl=1, ll=3 cons=1
    17:         SEQUENCE len=1187       tl=1, ll=3 cons=1
    21:             [0] len=7       tl=1, ll=1 cons=0
    30:             [1] len=1174       tl=1, ll=3 cons=1
    34:                 [1] len=1170       tl=1, ll=3
cons=1
    38:                     EXTERNAL len=1166       tl=1,
ll=3 cons=1
    42:                         OID len=0       tl=1, ll=1
cons=0
    44:                         [1] len=1160       tl=1,
ll=3 cons=0

YAZ refuses to decode because the OID is badly formed in the
Record 
External. That's an error in the server implementation I
believe. One 
way to get around this error is to specify a record syntax,
say USMARC. 
yaz-client does that by default. ZOOM C does not.

/ Adam


> 
> $conn = new ZOOM::Connection('libprd.uits.indiana.edu 
> <http://libprd.uits
.indiana.edu>', 2200);
> $rs = $conn->search_pqf('^C1323935')
>     or die $conn->errmsg();
> 
> my $n = $rs->size();
> print "found $n records:n";
> print $rs->record(0)->render if $n;
> 
> 
> Any clue where to go from here ?  This the latest yaz
and zoom code 
> downloaded today
> 
> Geoffrey
> 
> 
>
------------------------------------------------------------
------------
> 
> _______________________________________________
> Net-z3950 mailing list
> Net-z3950lists.indexdata.dk
> http://lists.indexdata.dk/cgi-bin/mailman/listinfo/n
et-z3950


_______________________________________________
Net-z3950 mailing list
Net-z3950lists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/n
et-z3950

Re: zoom perl error
user name
2007-06-27 06:25:35
Adam Dickmeiss writes:
 > Geoffrey Brown wrote:
 > > I get the following error:
 > > 
 > > ZOOM error 10003 "Decoding failed"
(addinfo: "ODR code 8:23 
 > > element=                    ") from diag-set
'ZOOM'
 > > 
 > > When executing the following trivial program
(based upon the documentation)
 > 
 > With yaz-client I get:
 > 
 > adampeanut:~$ yaz-client libprd.uits.indiana.edu:2200
 > [...]
 > Z> format none
 > Z> s 1+1
 > Sent presentRequest (1+1).
 > Decoding incoming APDU: Malformed data (code 8:23)
 > Element path: presentResponse databaseOrSurDiagnostics
? record ? 
 > databaseRecord
 > [Near 44]
 > Packet dump:
 > ---------
 >      0: [25] len=1204       tl=1, ll=3 cons=1
 >      4:     [24] len=1       tl=1, ll=1 cons=0
 >      7:     [25] len=1       tl=1, ll=1 cons=0
 >     10:     [27] len=1       tl=1, ll=1 cons=0
 >     13:     [28] len=1191       tl=1, ll=3 cons=1
 >     17:         SEQUENCE len=1187       tl=1, ll=3
cons=1
 >     21:             [0] len=7       tl=1, ll=1 cons=0
 >     30:             [1] len=1174       tl=1, ll=3
cons=1
 >     34:                 [1] len=1170       tl=1, ll=3
cons=1
 >     38:                     EXTERNAL len=1166      
tl=1, ll=3 cons=1
 >     42:                         OID len=0       tl=1,
ll=1 cons=0
 >     44:                         [1] len=1160      
tl=1, ll=3 cons=0
 > 
 > YAZ refuses to decode because the OID is badly formed
in the Record 
 > External. That's an error in the server implementation
I believe. One 
 > way to get around this error is to specify a record
syntax, say USMARC. 
 > yaz-client does that by default. ZOOM C does not.

This server has other, er, oddities:

$ yaz-client libprd.uits.indiana.edu:2200
Connecting...OK.
Sent initrequest.
Connection accepted by v3 target.
ID     : Unicorn GL3.1 Standard
Name   : SIRSI Corporation
Version: 3.0
Options: search present delSet scan sort namedResultSets
Elapsed: 0.791811
Z> f ^C1323935
Sent searchRequest.
Received SearchResponse.
Search was a success.
Number of hits: 1, setno 1
records returned: 0
Elapsed: 0.666002
Z> format xml
Z> elem f
Z> show 1
Sent presentRequest (1+1).
Diagnostic message(s) from database:
    [100] Unspecified error -- v2 addinfo 'Expected
CONSTRUCTED PDU not found (pdu error: 3002)'
nextResultSetPosition = 1
Elapsed: 0.122000
Z> 

So trying to fetch a full XML record also produces malformed
BER, but
in a different way from fetching a record with no format
specified.
This does not give me confidence in the server :-/

 _/|_	
____________________________________________________________
_______
/o ) /  Mike Taylor    <mikeindexdata.com>    http://www.miketaylor.or
g.uk
)_v__/  "In the forwards debate: Rush _is_ past it,
despite the odd
	 hat-trick" -- Lee Curran.


_______________________________________________
Net-z3950 mailing list
Net-z3950lists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/n
et-z3950

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )