Dwight,  the BFS files I referred to, the flat files in my second level
  storage group that is sometimes
  tape, but in my case I use only DASD.  The BFS in the file name is an IBM
  default, I believe.
  I have to run EXPIRE every day just to keep the storage groups clean.
  The ADSM region
  goes into a high CPU usage state then hangs.  This happens everyday,
  sometimes after
  EXPIRE ends and sometimes right before it completes.  We have to cancel
  ADSM because
  of the high CPU usage and on the reload the clean up from the EXPIRE
  begins.  The BFS files
  are mounted one by one to be deleted.  The delay to get signed back on to
  ADSM to do some
  restores was a record 7 HOURS yesterday.  Users are starting to complain
  as you would expect.
  As I stated all of my second level storage group is kept on disk, which I
  would expect to help
  speed things up.  This storage group is what the BACKUPPOOL  storage
  group is migrated too.
  Hope this helps.  I need some help.
  Thanks,
  Paul Brown
  PDBrown.Ashland.com
  606-357-7585
  To:  ADSM-L @ VM.MARIST.EDU
  cc:        (bcc: Paul D Brown)
  From:     decook @ AMOCO.COM
  Date:     02-26-97 08:22:09 PM CST
  Subject:  Re: Controlling BFS Deletes after EXPIRE



--0__=4AcGx1nB1zscVXJC5FOJ5YcKM54YrpFLazc0NxACXJtsiRAYi1jOV8jk
       Paul, what is being referred to by BFS ? (backup file system comes
       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


--0__=4AcGx1nB1zscVXJC5FOJ5YcKM54YrpFLazc0NxACXJtsiRAYi1jOV8jk--
=========================================================================