Page History

...

1. Send email to Ken Brobeck requesting:
1. create controls infrastructure for a new IOC on facility production server, which includes the following:
   
   1.  Add boot directory: $EPICS_DATA/<ioc>  directory
   2.  Add data directories: $IOC_DATA/<ioc>/<autosave,autosave-req,restore,iocInfo,archive>  directories 
   3.  Add automatic boot scripts:  (rhel6 only) 
      1. add boot script on server defined in table 1:       /etc/inti.d/st.<ioc>

      2. add symbolic link on server defined in table 1:   /etc/rc3.d/SS98st.<ioc> ---->   /etc/init.d/st.<ioc>
         
                              Table 1
          

         Facility	Server
         LCLS	laci@lcls-daemon1
         LCLS-II	laci@lcls-daemon1
         FACET-II	flaci@facet-daemon1
         TestFac	acctf@testfac-daemon1

2. Proceed to Development Step #3

...

1. Create the $IOC_DATA directory for your iocs as follows:
1. cd $IOC_DATA
2. mkdir sioc-<area>-<subsystem-prefix><2-digit#>
3. cd  <sioc>
4. mkdir archive autosave-req autosave iocInfo restore
   
2.  Create the $EPICS_IOCS  ioc boot directory
   
   1. mkdir  sioc-<area>-<subsystem-prefix><2-digit#>
3. Setup ioc boot directory files
   1. cd $EPICS_IOCS/sioc-<area>-<subsystem-prefix><2-digit#>
   1. copy the ioc startup.cmd script from  $EPICS_IOCS/template
      1.  for Linux running iocsh:    cp ../template/startup.cmd.soft         ststartup.cmd
          Create symbolic link:         ln -s st.cmd startup.cmd
4. Edit st.cmd
   1. replace <ioc>  with your ioc name
   2. replace <t_a> with the target, such as  linux-x86  or linux-x86_64 or rhel6-x86_64 (ref. your application bin directory).
   3. replace <exe> with your IOC Application executable this ioc should load
      
   4. if your IOC Application uses a non-standard location for the st.cmd file,  change path of the EPICS_IOC_APP
   5. Setup a relative symbolic link that points to the EPICS IOC Applicaiton TOP as follows:  
               ln -s ../../iocTop/<app>/<version> iocSpecificRelease

...