I've certainly compiled and modified the ARS Perl code - which is in c -
when it was needed for new ARS releases.  

 

If you are getting an ARERR 90 it is a connectivity error.  

 

Misi is right about -malign-double being needed but that is probably a
default with your version of gcc.  A 90 is always a connectivity error.  An
ARS Perl not being ready for the current or installed API results
(generally) in compile errors.  When you say "link" I am assuming you mean
"link to the ARS Server" and not the link step of the build of ARS Perl (ie
making the .so's).  

 

I would suggest you check that you are issuing the SetServerPort if needed
(or else issue an export ARTCPPORT=xxx BEFORE firing your Perl code).  This
is needed if your server is not using portmapper.

 

To see what's happening, simple set ARAPILOGGING=1 before running your code.
Ensure you can ping whatever server you have configured in your Perl app.
With APILOGGING set, you will get two log files generated.  One will tell
you what API calls you are making (I think with arguments) and the other the
results of said API calls.

 

Cheers

 

Ben Chernys

Senior Software Architect
Software Tool House Inc.

Canada / Deutschland / Germany
Mobile:      +49 171 380 2329    GMT + 1 + [ DST ]
Email:        <mailto:[email protected]> Ben.Chernys _AT_
softwaretoolhouse.com
Web:          <http://www.softwaretoolhouse.com> www.softwaretoolhouse.com

Check out Software Tool House's free Diary Editor.

Meta-Update, our premium ARS Data tool, lets you automate 
your imports, migrations, in no time at all, without programming, 
without staging forms, without merge workflow. 
 <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/  

 

 

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Nathan Neulinger
Sent: December-15-10 18:54
To: [email protected]
Subject: Re: 64bit linux (lx64) api still broke with 7.6.3?

 

** Wanted to let you know that I had a few minutes to get back to this and
check - the C API definitely works for me - it's specific to linking against
perl. I checked with gdb, the content of the control structure is exactly
identical between a simple C test app that does an ARInitialization and then
ARVerifyUser and the same code in the ars_Login code in the ARS perl module.

The C code returns the proper status, the perl code always gets the ARERR
#90 can't encode arguments error.

The perl module gets the same error whether compiled with -malign-double or
not.

I'd say without assistance from BMC on the internals of the AR client
library or someone who knows a lot more about how this code works it's going
to be difficult to debug. (Or someone with access to the source code of the
library who could try compiling arsperl (latest cvs) on lx64 platform to see
if they can resolve the issue. 

-- Nathan

On Thu, Sep 16, 2010 at 2:45 AM, Misi Mladoniczky <[email protected]> wrote:

Hi,

Did you use the -malign-double compile option? I have forgotten about that
some times, and you get unexpected problems...



        Best Regards - Misi, RRR AB, http://www.rrr.se

Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.

> Ugh. That is sounding like it either is a problem ONLY when linking with
> perl, or something else is going on.
>
> Thank you for checking into this, looks like I need to do some further
> testing. If it's specific to linking with perl libs, may wind up not being
> able to resolve the problem, but at least will know the specifics of the
> problem.
>

> -- Nathan
>
> ------------------------------------------------------------
> Nathan Neulinger                       [email protected]
> Missouri S&T Information Technology    (573) 612-1412
> System Administrator - Principal       KD0DMH
>
>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList)


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to