cd $EPICS_IOCS/sioc-<area>-<subsystem-prefix><2-digit#>
copy the ioc startup.cmd script from $EPICS_IOCS/template
for Linux running iocsh: cp ../template/startup.cmd.soft startup.cmd
Edit st.cmd
replace <ioc> with your ioc name
replace <t_a> with the target, such as linux-x86 or linux-x86_64 or rhel6-x86_64 (ref. your application bin directory).
replace <exe> with your IOC Application executable this ioc should load
if your IOC Application uses a non-standard location for the st.cmd file, change path of the EPICS_IOC_APPSetup a relative symbolic link that points to the EPICS IOC Applicaiton TOP as follows: ln -s ../../iocTop/<app>/<version> iocSpecificRelease
Modify $EPICS_IOCS/screeniocs– Please note that this is a symbolic link to a CVS file.
verify that the file in use has not been modified without being committed.
cd $EPICS_IOCS/All/<facility> , where facility is Dev,Prod,facet,acctest
cvs diff -r HEAD screeniocs
if there are issues, then send email to whoever made the change or to controls-software that you are about to update this file and uncommitted edits will be lost, so please commit your changes to CVS. If you don't get a response, you can either add the changes to CVS in addition to yours or just add yours.
check out screeniocs from CVS into your work area
cd
cd <work> cvs co epics/iocCommon/All/<facility> , where facility is Dev,Prod,facet,acctest
cd epics/iocCommon/All/<facility>/screeniocs
edit screeniocs
add line for <ioc>. For server refer to table 1 above. format: sioc-<area>-<subsystem prefix><2-digit #> <executable w/full absoluete path> sioc <server> [#comment}
The "comment" field in screeeniocs is optional and must be preceded by a "#".
add comment in the "Mod:" section of the header
commit your changes of screeniocs to CVS as follows: