Experimental Physics and
Industrial Control System

Hi Murali,

Your assumption is correct for CA servers that are real IOCs, the .NAME field should always give you the canonical record name when you're actually using an alias name. However a server that uses the PCAS could do whatever it wants with the PV name, it doesn't have to support the .FIELD syntax which the IOC uses.

- Andrew

-- 
Sent from my iPad

On Jun 5, 2013, at 1:20 PM, "Shankar, Murali" <[email protected]> wrote:

> It is my assumption that if I define a record like so
> 
> record(ai, "pvname") {
>  alias("aliasname")
>  field(DESC , "This is a desc")
> }
> 
> Then, caget on pvname.NAME and caget on aliasname.NAME will give me the same result; i.e. pvname. That is, the .NAME field is used to hold the true name of the record and is the same when I refer to the record by using the realname or the aliasname. 
> 
> Would this be a correct assumption? One of our PCAS IOC's is using the .NAME field for something else and I'm trying to determine if this would be the right thing to do.
> 
> Regards,
> Murali
> 
> 

References:

Clarification on aliases and the .NAME field Shankar, Murali

Navigate by Date:

Prev: RE: seqLog obsolete / errlog filtering based on source Mark Rivers

Next: Issue with QuadEm/AreaDetector makefile... David Reid

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <2013>  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Clarification on aliases and the .NAME field Shankar, Murali

Next: seqLog obsolete / errlog filtering based on source Emmanuel Mayssat

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <2013>  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024