VMS/IRAF Installation and Site Manager's Guide
VMS/IRAF Installation and Site Manager's Guide
Login again as SYSTEM and copy the recently edited file
irafdisk:[iraf.vms.hlib.libc]iraf.h to the system library, ensuring that the
file has world read permission (be sure not to copy [iraf.vms.hlib]iraf.h by
mistake):*
$ set default sys$library
$ copy disk:[iraf.vms.hlib.libc]iraf.h []/protection=w:r
- Add the following statement to the system SYLOGIN.COM file, making the
appropriate substitution for disk.
$ iraf :== "@disk:[iraf.vms.hlib]irafuser.com"
- Add the following statement to the SYSTARTUP_V5.COM file, read by the system
at startup time. This is necessary to cause the IRAF executables to be
reinstalled in system memory when the system is rebooted.
$ @disk:[iraf.vms.hlib]install.com
- While still logged in as SYSTEM, type in the above command interactively to
perform the initial executable image installation. It may be necessary to
increase the number of system global pages for the command to execute
successfully. If you do not want to install the set of IRAF executables
normally installed at NOAO, edit [iraf.vms.hlib]install.lst before
executing install.com (see §8.2).
Lastly, log out of SYSTEM, and back in as IRAF. Update the date stamp
of a file that is used to ensure that newly updated parameter sets are
used rather than any old versions a user might have around:
$ set default irafhlib
$ copy utime. utime.
$ purge utime.
*On a VMS cluster, make sure the IRAF.H file is added to
SYS$COMMON:[SYSLIB] rather than SYS$SYSROOT:[SYSLIB], so that all nodes in
the cluster may transparently access the file. The same precaution is
needed when editing the system-wide login procedure file (e.g.,
SYLOGIN.COM), which will probably want to go into SYS$COMMON:[SYSMGR]. The
SYSTARTUP_V5.COM file, on the other hand, should go into
SYS$SYSROOT:[SYSMGR] if the bootstrap procedure is different for each node.