Linking ANALYSIS CONTROL

Once a user has generated his interface code using BUILD_JOB, he is ready to link. The following steps must be performed:

1. The user must compile the fortran file written by BUILD_JOB. (This file is in fact a ".CDF" rather than a ".FOR" file and must be compiled using the EXPAND/XFORT facility.)

2. The user must create an options file containing a list of all non-standard code he wishes to use. This options file contains the code for his own module, and also must contain the file created by BUILD_JOB. This file can have whatever name the user desires, but should have the extension .opt.

3. The user must setup the appropriate logical/environmental names by executing the following command procedure:
   

   setup a_c <version>

   This command need be executed only once per login session, regardless of how many times the user links. (Note: these logicals/env.s also must be set up before the user can run his program. It is therefore advisable to include this setup command in the user's login. The Analysis_Control logicals/env.s will automatically be set up if the user executes the offline setup command.)

4. Standard linking can be done by typing the command link_ana. This symbol/alias activates a command file that will ask the appropriate questions and will then perform the link. Alternatively link_ana can be invoked as a single command:
   

   $ LINK_ANA MYEXE_NAME MYOPT_FILE [Yes/No/All] <optional_library_list>
   

   % link_ana myexe_name.exe myopt_file.opt [no/all/user/O2] <optional_library>

   For more information on the use of the link_ana command see appendix C.