Jerry Fochtman wrote:
>
> At 02:50 AM 1/22/99 +0000, Tom <[log in to unmask]> wrote:
> >One thing to be *REALLY* careful about is with DB maintenance utilities
> >such as DBGENERAL. If the group you're running in is on a different
> >volume set than the group containing the dataset you're expanding, the
> >dataset gets trashed.
>
> We've sent several notes to this individual and also searched our
> technical support database log attempting to identify the person so
> we could follow-up personally to better understand what prompted the
> particular comment involving DBGeneral. We've also searched our logs
                               ^^^^^^^^^

I didn't say that DBGENERAL caused the problem. We have DBGENERAL on our
system but it turns out that Growthpower's DB Expander calls something
called DBCSI.DISK.SYS to expand the DB. Growthpower runs in PUB and the
databses are in DATA. I saw the problem in DBCSI and said that,
generally, one should be careful of one's environment.

I was incognito because I moved last week so I was out-of-pocket for
several days. I ran the File Expand Utility and then used MPEX to
SHOWPROC the expand process and see what was getting run.

That particular problem happened in a Training account and didn't impact
live production. Since the Train account was the only one on a private
volume set, we felt it didn't warrant a call-in. Our self-work-around
was to not put the DB'a on a different volume set that PUB.