Re: Java API JCA / CAJ DBR_LONG

["Kasemir, Kay" <kasemirk@ornl.gov>]

Hi:

You're right that when I create this record:

  record(longin, "long")
  {
  }

then  'cainfo' will report
    Native data type: DBF_LONG
while CAJ shows a DBR_INT.

Still, the CAJ DBR_*_INT types provide Java int[] for the value, which is 32 bit numbers. When I
   caput long 2147483647
I do see that number in a CAJ client, it's not truncated to 16 bits as you would get with the C-client DBR_INT.

For the C client API, DBR_INT is the same as DBR_SHORT, and all of DBR_SHORT, INT, LONG exist in the API.
For the Java client, DBR_INT is basically DBR_LONG, and DBR_LONG has not been defined since it's already handled by DBR_INT..

-Kay

________________________________________
From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of Ryan Slominski <ryans@jlab.org>
Sent: Monday, January 29, 2018 2:02 PM
To: tech-talk@aps.anl.gov
Subject: Java API JCA / CAJ DBR_LONG

It appears the Java API to EPICS does not include DBR_LONG type (missing from source: https://github.com/epics-base/jca/blob/master/src/core/gov/aps/jca/dbr/DBRType.java).  When I use caget and probe on a DBR_LONG PV and compare with programmatic fetch the values don't match and Java reports the type as DBR_INT.   Maybe I'm overlooking something.  Any tips on having Java API return same value as command line tools?