Charlie is right:  I would agree that some form of notification is
desirable; however, this goes more to speaking to the pitfalls of
automation.  It's too easy to turn over mundane tasks to an automated
process and think you (the collective 'you', that is    ;-) never have to
worry about it again, so  $STDLISTs and backup listings go unread.
Unfortunately, this seldom comes to pass, and you're bitten.

I think it's important, especially because of cases like this, to monitor
database capacities at least weekly to gauge trends and prepare for the
unexpected.  Additionally, most backup software of which I'm aware will
store HFS files if the fileset being stored is specified with [log in to unmask]  It's
when we specify specific files or filesets that this kind of trouble
occurs.

Adager, Bradmark, HP, Orbit, Unison, et al:   any comments re: Charlie's
request?

Lee (been there, done that, bought a pocket protector) Gunter
Regence Blue Cross Blue Shield of Oregon / Regence HMO Oregon
mailto:[log in to unmask]      voice...503-375-4498    fax.....503-375-4401
==========================================================
The opinions expressed, here, are mine and mine alone, and do not
necessarily reflect those of my employer.



From: [log in to unmask] on 10/07/97 05:35 PM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  JUMBO a new thread?




What if ...

You have automated your nightly database expansion jobs using ADAGER.
 Suddenly one dataset in the database goes jumbo and ADAGER handles the
 task with no problems.  No errors appear in the standard lists and life
 goes on ... until two months later the disc drive blows a gasket rendering
 your database inoperable.  You replace the disc drive and restore from
 your most recent backup only to find that the backup is as useless as that
 disc drive you just tossed in the garbage.

  You see, because you weren't aware that your database had gone jumbo you
 didn't modify the STORE syntax in your database backup jobs.  Potentially
 you have lost two months of data and it's time to spiff up that resume.

Wouldn't it be a good idea for the backup software vendors to default to
 storing the POSIX file structure using your MPE/iX filesets.  You could of
 course, turn this feature off if you wish but only geeks with pocket
 protectors would be interested in doing that.

What's your opinion, I'd like to know.


Charlie Fontaine     NYLCare Health Plans