1 Rje_Utils
    The following   are   a   series  of  utilities  which  aid  in  RJE
maintenance.  Most of them require no privileges, except access  to  the
input  files.   All  of  the programs must have a global foreign command
associated with the program, as all of the programs get their  arguments
from the command line:   UTIL :== $Rje_Util:UTIL

    The term  "intermediate  file"  refers  to  any  temporary file that
either the RJE program generates (RJE_SPOOL:*.RJE;1) or those  generated
by    the   MOTHER   or   CONSOLE   processes   (RJE_SPOOL:*.SPL;1   and
RJE_SPOOL:*.JES;1, respectively);  these files have been put  through  a
magic  blocking  process  (see  [uokrje.src.lib]block.c)  and  have very
weird characteristics. 
2 CRC
Usage:       $ crc file

Purpose:     Opens the intermediate file given,  and  evaluates  CRC  on
             data  within.   Then, compares calculated CRC with embedded
             CRC for any discrepancies.  useful  for  checking  the  CRC
             function and parts of the blocking routines. 
2 DBK
Usage:       $ dbk file1 [file2...]

Purpose:     Opens   intermediate  files,  unblocks  them,  then  prints
             resulting data on stdout (SYS$OUTPUT).  When  the  file  is
             closed,   the  name  of  the  file  is  printed  on  stderr
             (SYS$ERROR).  Useful for checking the validity of  blocking
             and deblocking services. 
2 DEBLOCK
Usage:       $ deblock file1 [file2...]

Purpose:     Submits  intermediate  files  to  the  DBLOCKER process for
             distribution to the file system.  Useful for cleaning up  a
             messy  DBLOCKER  crash  (not  that there should be any, but
             just in case).  Must be full file specifications. 
2 REQUE
Usage:       $ reque file1 [file2...]

Purpose:     Submits  intermediate  files  to  the  MOTHER  process  for
             transmit  processing.  Useful for cleaning up after a messy
             MOTHER crash (but hopefully, these are  VERY  rare).   Must
             be full file specification. 
2 ZAP
Usage:       $ zap mbx1 [mbx2...]

Purpose:     Marks  the  given  permanent  mailboxes for deletion.  must
             have  PRMMBX  privileges.   NOTE  -  mailboxes   will   not
             actually  go  away  until  all  links  to  the  mailbox are
             deleted, and even then, the system may need a  little  time
             to  get rid of the thing.  Mailbox names can be of the form
             MBAnnnn: or an equivalent logical name. 
