EPICS application source/release control Page: 3 of 20
This report is part of the collection entitled: Office of Scientific & Technical Information Technical Reports and was provided to Digital Library by the UNT Libraries Government Documents Department.
The following text was automatically extracted from the image on this page using optical character recognition software:
The following conventions and/or representations apply to the remainder of this document.
" <appSR> Represents the full path name of an appSR release
" <epics> Represents the full path name of an EPICS release
" <top> Represents the root node of an application system area. It is the directory from
which we can access EPICS components.
" <shadow> Represents the top node of an application shadow node. "shadow node"
and "shadow area" are synonymous.
" <archV> Represents the vxWorks target architecture. Currently hkv2 f for the 68020
and mvl67 for the 68040.
" <archU> Represents the Unix architecture. Currently sun4.
" % Indicates a prompt for user input or activity.
" <EDIT> Means: edit the file according to the sccs rules. Refer to the sccs
procedures section "Source/Release Control Commands" on page 3. Note: <EDIT>
includes doing a delget if in the system area.
In order to use the Application Source/Release tools and executables you need to have the
following item in your path:
Ask your EPICS site manager for the name of a file which you can source from your .cshrc file
to satisfy the above appSR path requirements as well as all the EPICS Unix environment and
At APS an EPICS user needs only the following statement in his/her .cshrc file placed after any
set path statements.
The Unix sccs utility is used to put all user editable files under source/release control. The
Unix documentation should be consulted for a complete description of sccs. This section
gives a brief description of the commands normally used by application developers. Wherever
<filename> is shown a list of filenames is allowed.
%sccs create <filename>
This command places a file under sccs control for the first time. After the file is placed under
sccs control a read only copy is created, i.e. an sccs edit command must be issued before
the file can be modified.
This command also creates a backup copy of the original file. It is the original file with a
comma prepended to the name. It is a good idea to remove this file, now.
%sccs edit <filename>
This command checks out a file so that it can be modified. If a file is checked out in an
application shadow area, other developers will not see any modifications until an sccs delta
If a developer checks out a file in a shadow area it is actually checked out from the system area,
i.e. no other developer can try to modify the same file. Other developers do not, however, see
any changes made in the shadow area until the developer checks in the modified files.
EPICS Release: R3.12 EPICS Application Source/Release Control 3
EPICS Release: R3.12
EPICS Application Source/Release Control
Here’s what’s next.
This report can be searched. Note: Results may vary based on the legibility of text within the document.
Tools / Downloads
Get a copy of this page or view the extracted text.
Citing and Sharing
Basic information for referencing this web page. We also provide extended guidance on usage rights, references, copying or embedding.
Reference the current page of this Report.
Zieman, B.; Anderson, J. & Kraimer, M. EPICS application source/release control, report, December 31, 1995; Illinois. (https://digital.library.unt.edu/ark:/67531/metadc668962/m1/3/: accessed April 25, 2019), University of North Texas Libraries, Digital Library, https://digital.library.unt.edu; crediting UNT Libraries Government Documents Department.