Paul, what is being referred to by BFS ? (backup file system comes to
     mind but I hate guess work...)  Our MVS test server I believe is at
     2.1.12 I can't say right now cause it isn't running... but this sounds
     like something I need to look into...  the only hits I got in my
     manuals for BFS was an arbitrary name  used in conjunction with data
     set prefixes on tapes...  Could  you enlighten me a little more...
     Currently it sounds like when it died it left something in an "easy to
     tell something went wrong" state and I don't think I'd want ADSM to
     allow access until it had straightened itself out... but I need a
     little more info...
     later
         Dwight


______________________________ Reply Separator _________________________________
Subject: Controlling BFS Deletes after EXPIRE
Author:  ADSM-L at unix,mime/DD.RFC-822=ADSM-L AT VM.MARIST DOT EDU
Date:    2/26/97 7:56 AM


  Hi ADSMers,
    I am running ADSM/MVS server 2.1.12.   I am having trouble with ADSM
  hanging up after EXPIRE
  ends.  After a cancel and restart of the ADSM region The BFS deletes
  begin as cleanup from the EXPIRE.
  The ADSM server will not allow access until all deletes are complete
  which normally is 4 to 5 hours of
  down time.  My question, Is there any way to prevent the EXPIRE clean up
  from starting after the ADSM reload?

  Thanks,
  Paul Brown
  Storage System Manager

  PDBROWN.ASHLAND.COM
  Ashland Inc.
  Lexington, Kentucky