This is the log book for the LEVEL 1 Code in ZEBRA_UTIL
                              started  3-JUN-1993 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ........... Philippe 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 14-JAN-1994 Philippe 

    - No success looking for a solution for PRTRGR_FIRST_BYTE_DECODING.FOR that
      would satisfy flint.
      The routine tries to be able to deal with number of bytes .le. and .gt. 4
      It receives the target argument as an array of variable lenght, but most
      cases call it with an I*4 argument (only DBSC are 5 bytes).
      Using equivalence is not allowed on a dummy argument.

      The only known solution thought of at the moment is to make 2 separate
      routines, e.g. PRTRGR_FIRST_BYTE_DECODING, and PRTRGR_FIVE_BYTE_DECODING

    - modify L1UTIL_LT_JET_LIST_BUILDER.FOR 
      include H.Greenlee solution for big-endian machine in-dependency. 
      add a DATA statement on LAST_PROCESSED_EVENT to make FLINT happy.

    - move L1UTIL_JET_LIST_BUILDER.FOR
      this routine was in LEVEL1 and is migrating to ZEBRA_UTIL

    - modify L1UTIL_JET_LIST_BUILDER.FOR 
      add a DATA statement on LAST_PROCESSED_EVENT to make FLINT happy.
      In entry L1UTIL_JET_LIST_BUILDER_FIRST fix typo-bug, use LIST_TYPE_FIRST

    - update D0$CMS:[ZEBRA_UTIL] using CMSINT, and RELEASE_NOTES to add an entry

================================================================================
NOTE: L1_DATA_FOR_HEAD_BANK is currently in the filter_util library 
================================================================================
TO DO
    - review Level2 versions of L1EXTRACT, and maybe call ours

    - for next revision of L1_DATA_FOR_HEAD_BANK.FOR 
        change low index of l1_block 1->0
        and drop the + 1 in the offset parameter.
        replace hardcoded offset with L1DBB_DATA_BLOCK.PARAMS 

    - fix GZFIND_CRATE for no TRGR found

    - change comment in L1EXTRACT_ANDOR_TERM to refer to TRIGGER.RES instead of
      D0$LVEL1$DATA:TRIGGER_RESOURCES.RCP

    - PRTGR: 
        - add a line about Andor Fired along with Specific Trigger Fired
        
    - dump
        - when programming is known, dump the state of andor terms attached
        with each specific trigger, state of front-end disable,... scalers,...