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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Combing Two State Sets into One |
From: | Eric Norum <[email protected]> |
To: | Bradley Pietrzak <[email protected]> |
Cc: | [email protected] |
Date: | Thu, 22 Sep 2011 14:22:25 -0700 |
I'm not quite sure what you're asking. If you're wondering, "Is there any way for a client to get at the list of record names?" then the answer is, "no, not directly". Many sites have a standardized IOC startup sequence that contain something like: ########################################################################### # Start IOC cd "$(TOP)/iocBoot/$(IOC)" iocInit ############################################################################### # Standard post-startup commands dbl >"$(IOC_INFO)/pvdata/$(IOC)" ############################################################################### Then clients and other tools like IRMIS can get the list of names from that file. Or, if you just want a record that contains the magnet number, you could have something like this in your startup script: epicsEnvSet(MAG, "1") . . . . dbLoadRecords("db/xxxxxx.db, "MAG=$(MAG)") . . . seq &sncExample, "mag=$(MAG)" where the xxxxxx.db database file contains, say, a longin record with field(VAL, "$(MAG)") If you change the epicsEnvSet command to something like: epicsEnvSet(MAG, "$(MAG=1") you can even provide the MAG value from a shell environment variable at startup. Hi everybody, |