IRAF installations at Starlink sites will usually have the additional Starlink packages installed. However, if they appear not to be available at your site then this section gives a few hints on how to proceed.
The directory /star/iraf should contain a subdirectory for every Starlink IRAF package present at your site. Check that this directory exists and that there is a subdirectory for the package that you are interested in. If the required subdirectory is absent then ask your site manager to install the package.
If the directory is present but the package is still not available when you start IRAF the most likely explanation is that the package is not known to IRAF as an external package. An entry for the package should be added to the hlib$extern.pkg file. Your site manager will have to add this entry. SSN/35[2], Section 4.8 contains the necessary details.
As an interim measure, perhaps to establish the cause of the problem, you can add an entry to your own login.cl file. For example, for Figaro add the following lines:
reset figaro = starlink$figaro/ task figaro.pkg = figaro$figaro.cl
These lines must be added just before the user package definition. The helpdb definition can be extended by a command like:
reset helpdb = (envget("helpdb") // ",figaro$helpdb.mip")
For other packages you would add equivalent lines, substituting the name of the package for figaro.
An Introduction to IRAF