Next: Parameter Specification for Output Parameters
Up: Interface Module Search Path, ADAM_IFL
Previous: Implementation for Unix
Implementation for VAX VMS
When a program is loaded, it attempts to translate the logical name ADAM_IFL
using the tables defined by the SYSTEM logical name LNM$FILE_DEV (Normally
PROCESS, JOB, GROUP and SYSTEM in that order).
ADAM_IFL may be a search path and, if it is defined, it is used as the
filespec, together with a default filespec of `filename.IF%' (where
`filename' is the filename of the executable image and `%' is any single
character), in a call to LIB$FIND_FILE.
If such a file is found, the type is checked and, if the type is not .IFC
or .IFL, the routine continues searching until no more files matching
the specification are found.
Note that a .IFC file will be found before a .IFL file in any given
directory.
Notes:
- 1.
- It is recommended that, if required, ADAM_IFL be defined as a JOB
logical name.
It cannot be a PROCESS logical name if the program is to be run in a
subprocess, and GROUP logical names may cause confusion as they remain set
between sessions.
- 2.
- If ADAM_IFL includes filenames, they will override the name of the
executable image.
Next: Parameter Specification for Output Parameters
Up: Interface Module Search Path, ADAM_IFL
Previous: Implementation for Unix
ADAM Interface Module Reference Manual
Starlink User Note 115
A J Chipperfield, B D Kelly, S L Wright
3 September 2002
E-mail:ussc@star.rl.ac.uk
Copyright © 2002 Council for the Central Laboratory of the Research Councils