• If you've just changed code &/or idl files

         Just execute the LIBRARY version of the bfc kumac
            i.e. exec $STAR/kumacs/chain/call_bfc_readfz_to_dst_year2
                  (or whichever one applies to you)  
    

• If you also (or only) changed the pam/dom/kumac files

          must cp $STAR/kumacs/chain/call_bfc_readfz_to_dst_year2.kumac to
           your directory and point TOP to your workdir (don't use any ~)
           so it will pick up your kumacs!!
    

• If you've changed the ACTUAL NAMES of the pams/dom/kumac then you must TEST changes using the "USER" chain!

          To TEST NEW PAM KUMACS (i.e. either the names have changed, or which
           ones you will call in what order will change or you have new ones
           that didn't exist before) use the USER kumac chain that I've
           provided in BFC:
   
        a. cp $STAR/kumacs/chain/call_bfc_readfz_to_dst_year2.kumac to
           your directory and point TOP to your workdir (don't use any ~)
           so it will pick up your kumacs!!  Add "user" to the chain list.
  
           The kumacs init_user.kumac, run_user.kumac & finish_user.kumac
           will be automatically called. The default ones are dummies in
           $STAR/pams/global/kumac so copy them to your workdir.
  
        b. Now edit the user kumacs in your workdir and put in the
           execute statements you need for your pam kumacs
  
        c. If you do it this way, Kathy will be much happier and
           quicker about implementing your new package/module into the
           official BFC kumacs.
    

        > staf 
        > exec call_bfc*