You can perform all of the script functions manually if you really want to. The user must specify the path to the executables with a command like:
0.2cm
1.0cm >set path = $path:~ftools/ftools/bin.host
0.2cm
where the actual path should be used in the place of ~ftools/ftools/bin.host. This command should be added to the user's .login file to append the bin.host path to the previously specified path.
0.3cm
Since the release of FTOOLS 3.2, the language Perl has been standardized for FTOOLS scripts. The FTOOLS distribution now places Perl scripts in the ~ftools/ftools/bin.perl directory. If your system has Perl installed and you would like use these scripts, which include the very popular ascascreen script (which now works on all supported UNIX systems), you'll want to prepend this directory to your path as with the bin.host directory:
0.2cm
1.0cm >set path = ~ftools/ftools/bin.perl:$path
0.2cm
If the .login script file is altered it will need to be sourced with a command like:
0.2cm
1.0cm >source .login
0.2cm
before the changes to these files will take effect. There are also four environment variables which must also be set up, LOCPFILES, SYSPFILES, PFILES and PFCLOBBER. But before establishing these make a directory under the user's home directory named something like myftools with the command:
0.2cm
1.0cm >mkdir myftools
0.2cm
Set the current directory to the new myftools directory with the command:
0.2cm
1.0cm >cd myftools
0.2cm
Now make two new directories under myftools. To do this give the command:
0.2cm
1.0cm >mkdir pfiles
0.2cm
Next the user must set the environment variables. This can be done with the following commands assuming that the directory structure for the user's account follows the examples above:
0.2cm
1.0cm >setenv LOCPFILES ~/myftools/pfiles
1.0cm >setenv SYSPFILES ~ftools/ftools/bin.host
1.0cm >setenv PFILES "$LOCPFILES;$SYSPFILES"
1.0cm >setenv PFCLOBBER 1
0.2cm
You will also need to tell the perl scripts where to find the FTOOLS perl library routines. Prepend the path to the bin.perl directory to the PERLLIB environment variable. If the PERLLIB environment variable does not exist set it equal to the bin.perl path. If you have a PERL5LIB variable already set, use that instead as it overrides the PERLLIB variable.
0.2cm
1.0cm >setenv PERLLIB = ~ftools/ftools/bin.perl:${PERLLIB}
0.2cm
if you already have a PERLLIB path, or
0.2cm
1.0cm >setenv PERLLIB = ~ftools/ftools/bin.perl
0.2cm
if you don't, or
0.2cm
1.0cm >setenv PERL5LIB = ~ftools/ftools/bin.perl:${PERL5LIB}
0.2cm if you have a PERL5LIB path set.
0.2cm
The user should add these commands to their .login script file so the variables will be set up during each login. Remember that the file which is changed must be sourced afterwards to set the environment variables or the user can logout and then log back in. Once this procedure has been completed the user can go to any directory and use the Host Version of the FTOOLS tasks. See Appendix A for a list of FTOOLS tasks in this release.