-----INSTRUCTIONS FOR THE INSTALLATION OF AIX FULIST-------    05/15/92


  1. Make a directory for you to receive the ixfulist files ('mkdir').

  2. Download the appropriate VM binary file into the above directory.
     The filename on your AIX system (ie, the name of the resultant
     file, after download) should end in .Z   (eg, 'ixfulist.6ktar.Z')

       IXFULIST RTTRZBIN - binary executables+ for RT AIX
       IXFULIST 6KTRZBIN - binary executables+ for Risc Sytem/6000
       IXFULIST PSTRZBIN - binary executables+ for PS/2 AIX R1.2
       IXFULIST XATRZBIN - binary executables+ for 370 AIX/XA

     The binary file is compressed, and contains executable 'fu', fu.help
     file, two model fu.keys files, one model ibm.ti file, and this file.

  3. Restore the ixfulist package files :

      a. Position yourself in the ixfulist receive directory ('cd').
      b. Uncompress the received file (eg, 'uncompress ixfulist.6ktar.Z').
      c. Untar the uncompressed file (eg, 'tar -xvf ixfulist.6ktar').

  4. Decide in which directory the ixfulist executable will reside.
     Then copy 'fu' to that directory (eg, 'cp -p fu /u/user/bin').

     For convenience, you would ordinarily place 'fu' in a directory
     that is listed in your PATH environment variable.

  5. Create a custom ixfulist definition file 'fu.keys', which
     reflects your personal preferences for PFkey usage, colors, etc.

     You can use the 'fu.keys' file in the distribution as a model.

     The 'fu.keys.rt' file in the distribution is a more complex model.
     To use this file on a platform other than the RT, you would have
     to change at least the 'print' statements.

     If running on a NON-COLOR terminal, your 'fu.keys' should have :
*COLOR Tit norm Id norm Emsg inv Redisp norm Stats norm Fdata norm Dir inv

  6. Decide in which directory your ixfulist definitions will reside.
     Ensure your custom 'fu.keys' has been copied to that directory.

     For convenience, you can copy 'fu.help' to that same directory.

  7. Add 'FUPATH' environment statement to your user profile,
     pointing to directory where your custom 'fu.keys' resides :

     Bourne example as follows:
       filename:  .profile
       -----------------------------------
              added path for fulist
       
       FUPATH=HOME/utils/fulist
       export FUPATH
       -----------------------------------

     Cshell example as follows:
       filename:  .cshrc
       -----------------------------------
              added path for fulist
       
       setenv FUPATH /u/topliss/utils/fulist
       -----------------------------------


  8. To execute the changed user profile, logoff and login again.
     (Or, just enter the above statements from the command line -
      they will be good for the life of your current shell.)

  9. Type in 'fu' to startup.




-----(OPTIONAL) INSTALLING YOUR OWN TERMINFO DATA BASE-------


  If your alt-PF keys do not work with ixfulist, it may be because the
  terminfo function distributed by IBM for some platforms (eg, AIX 3.x)
  does not define alt-PF key capabilities for your terminal.

  The ixfulist program now treats KEY_SF1 thru KEY_SF10, with KEY_PPN
  and KEY_NPN (see cur02.h), as synonyms for alt-PF1 thru alt-PF12.
  A model terminfo source file "ibm.ti" is included in the VM binary.
  It defines, for TERM=hft, capabilities ('ksf1'-'ksf10','kppn','knpn')
  that support the hft keyboard emitted sequences for the alt-PF keys.


  If you wish to install a user-level customized terminfo data base :


  a. Position yourself in your work directory (eg, same as step (3)).

  b. Start with file ibm.ti that was restored in step (3),  or
     make a copy of your system's /usr/lib/terminfo/ibm.ti.

     Edit the file, to make sure that the description FOR YOUR TERMINAL
     specifies appropriate values for the capabilities you need.

  c. Set the TERMINFO environment variable to point to the directory
     where your compiled terminfo descriptions will be placed.  (Step
     (7) shows the kind of statement to use.)

  d. Compile the terminfo source ('tic file_from_step_(b)').

  e. Add 'TERMINFO' environment statement to your user profile, pointing
     to the directory (step (c)) where your custom terminfo data resides.
     See steps (7,8) for how to update your user profile.

  f. When you run 'fu', it will get the terminfo descriptions from where
     TERMINFO points.

     Note:  When you run 'fu', if your terminal type (as set in the TERM
            environment variable) is not found in the data base pointed
            to by TERMINFO, then fu will fail.
