> For anyone interested (part 1 of 2)... 
>  
> From support: 
> We've tested this issue internally using both 7.1 and 7.5 API. It
> looks like there is a defect in the API on how it handles the negative
> value. Strangely enough the Mid Tier is able to process the request
> with no problems.
> 
> However according to the arapi logging for the java test it shows that
> it never makes the call; seems internal processing of the qual rejects
> it.
> --------------------------------------------------------
> Connecting to AR Server...
> Connected to AR Server atlwin01
> Retrieving entryies with qualification ( 'Create Date' > "1/1/2009" )
> Query returned 2 matches.
> Request Id Short Description
> 000000000000003 Demo
> 000000000000002 Demo
> Retrieving entryies with qualification ( 'Integer Field' = -90000 )
> Problem while querying by qualifier.
> Status List is empty.
> Stack Trace:ERROR (1587): Unknown field referenced in query line; at
> position 2 ( 'Integer Field' )
> at com.bmc.arsys.qual.a.a.c.a(Unknown Source)
> at com.bmc.arsys.qual.a.a.b.int(Unknown Source)
> at com.bmc.arsys.qual.a.a.b.a(Unknown Source)
> at com.bmc.arsys.qual.a.a.b.if(Unknown Source)
> at com.bmc.arsys.qual.a.a.b.for(Unknown Source)
> at com.bmc.arsys.qual.n.a(Unknown Source)
> at com.bmc.arsys.api.ARServerUser.parseQualification(Unknown Source)
> at JavaAPITest.queryEntrysByQual(JavaAPITest.java:67)
> at JavaAPITest.main(JavaAPITest.java:22)
> Retrieving entryies with qualification ( 'Integer Field' = -(90000) )
> Problem while querying by qualifier.
> Status List is empty.
> Stack Trace:ERROR (1587): Unknown field referenced in query line; at
> position 2 ( 'Integer Field' )
> at com.bmc.arsys.qual.a.a.c.a(Unknown Source)
> at com.bmc.arsys.qual.a.a.b.int(Unknown Source)
> at com.bmc.arsys.qual.a.a.b.a(Unknown Source)
> at com.bmc.arsys.qual.a.a.b.if(Unknown Source)
> at com.bmc.arsys.qual.a.a.b.for(Unknown Source)
> at com.bmc.arsys.qual.n.a(Unknown Source)
> at com.bmc.arsys.api.ARServerUser.parseQualification(Unknown Source)
> at JavaAPITest.queryEntrysByQual(JavaAPITest.java:67)
> at JavaAPITest.main(JavaAPITest.java:23)
> User logged out.
> 
> So we will create a defect for the Java API and let you know once it's
> been accepted.
> 
> 
> 
> ________________________________
> 
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of LJ Longwing
> Sent: Tuesday, November 03, 2009 3:19 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Java API - parseQualification Error
> 
> 
> ** 
> good luck, let us know how it goes...:)
> 
> ________________________________
> 
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of Roys, Eric D
> Sent: Tuesday, November 03, 2009 2:13 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Java API - parseQualification Error
> 
> 
> ** 
> Thanks, LJ. 
>  
> I'll try to uprev to patch 3 before dropping this in support's lap
> since I know that's always the first step in troubleshooting according
> to support ;-)
>  
> -Eric
> 
> ________________________________
> 
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of LJ Longwing
> Sent: Tuesday, November 03, 2009 3:03 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Java API - parseQualification Error
> 
> 
> ** 
> Well...using the 7.1P6 Java API the output of both are
>  
> [Operation=4,Operand Left=[Operation=1,Operand Left=[Operand
> Type=[type=1],Operand=1702],Operand Right=[Operand
> Type=[type=3],Operand=[Operation=6,Operand Left=<null>,Operand
> Right=[Operand Type=[type=2],Operand=900000]]]],Operand Right=<null>]
> 
> [Operation=4,Operand Left=[Operation=1,Operand Left=[Operand
> Type=[type=1],Operand=1702],Operand Right=[Operand
> Type=[type=2],Operand=900000]],Operand Right=<null>]
>  
> Obviously the two are different...the only difference between the two
> is that the top one has -900000 and the bottom has 900000...so I would
> say that we have an API bug...big surprise
> 
> 
> 
> ________________________________
> 
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of Roys, Eric D
> Sent: Tuesday, November 03, 2009 12:37 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Java API - parseQualification Error
> 
> 
> ** 
> LJ, 
>  
> This is the string output from the latter :
>  
> [Operation=4,Operand Left=[Operation=1,Operand Left=[Operand
> Type=[type=1],Operand=1702],Operand Right=[Operand
> Type=[type=2],Operand=900000]],Operand Right=<null>]
>  
> // where 1702 is the db id for Role ID field and "900000" is the
> value.
>  
> -Eric
> 
> ________________________________
> 
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of LJ Longwing
> Sent: Tuesday, November 03, 2009 1:24 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Java API - parseQualification Error
> 
> 
> ** 
> I would say you have likely found a bug....but if you use the second,
> and then output the .toString() of it, what does it give you?
> 
> ________________________________
> 
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of Roys, Eric D
> Sent: Tuesday, November 03, 2009 12:07 PM
> To: arslist@ARSLIST.ORG
> Subject: Java API - parseQualification Error
> 
> 
> ** 
> 
> I hope someone can provide some clarity to this or substantiate that
> this is a bug... 
>   
> ARS7.5 p1 (server/api) 
> Win2003 
> Java 1.6 
>   
> Using QualifierInfo qual = ctl.parseQualification("Roles", "'Role ID'
> = -900000"); // has negative sign 
>   
> returns ERROR (0) : Message not in catalog; Message number = 0; Error
> while decoding. 
>   
> Using QualifierInfo qual = ctl.parseQualification("Roles", "'Role ID'
> = 900000");  // no negative although invalid role id
> 
> 
> returns no error and also no matching results (as expected). 
>   
> So it appears the parseQualification is having some issues with "-"
> interpretation. 
>   
> Thoughts/suggestions? 
> 
> Kind Regards, 
>   
> Eric Roys 
> Sr. Sales Engineer 
> GSSI 
> Verizon Business 
> 
> 
> _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the
> Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist:
> "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net
> ARSlist: "Where the Answers Are"_ _Platinum Sponsor:
> rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum
> Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_
> _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the
> Answers Are"_ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"

Reply via email to