General Structure of Software Directories
- AT$ - Executable images, command procedures and
data files necessary for array operation.
- LIB$ - Software libraries to which
programs in the OBS$ area link.
- OBS$ - Software development areas for executable
on-line and off-line programs.
- SYS$ - VMS system maintenance and service files.
- USR$ - Personal directories for observatory staff
and visitors.
- UTL$ - Utility programs not required for array operation.
- AT$
- Each of the AT$ areas is named according to its contents
- Eg.
- AT$RUN - Executables
- AT$LOG - Log files
- AT$ANTENNA - Antenna related files
- AT$SCHED - Schedule files
- AT$CAT - Catalogues
- AT$LOG - Log files
- AT$RUN - Executables
- LIB$
- There can be as many LIB$ areas as there are disks. These are
designated LIB$1, LIB$2,..., LIB$n.
At present only LIB$1 exists.
Within each LIB$n area are a number of directories, each named after and containing a particular software library, for example, LIB$:[ATE], LIB$:[MENU] and LIB$:[TIM].The structure of each LIB$[XXX] is as follows: The top level directory of a library (LIB$[XXX]) should contain the library file XXXLIB.OLB and the two directories: LIB$[XXX.WORK] and LIB$[XXX.CODE] .
- OBS$
- As with the libraries, there can be a number of OBS$ areas,
depending on their physical location.
Each major program has its own subdirectory within this, and is at
the top of a directory tree of the form given
below.
Examples of program units stored in the OBS$ area include ARRAY, CAOBS and CAMON. - SYS$
- The SYS$ device holds files required for system operation and
maintenance.
- UTL$
- This area has not yet been implemented, but it is envisaged that
it will contain utility programs which do not fall into any
of the other categories.
Examples include many of the files currently residing in SYS$UTILITY:. Eg. kermit, xeyes, etc.
Directories Containing Source Code
Directory trees which hold source code are structured as per the following diagram:
The top level directory (ARRAY in the example) has two subdirectories: [ARRAY.WORK], where development occurs and working files are kept, and [ARRAY.CODE] which holds the CMS (Code Management System) directory structure.
Original: nmckay (23-Feb-1995)
Modified: nmckay (9-Oct-1995)