Jeff Vance wrote:
>
> Is there enough interest/need in being able to purge PRIV files that
> we should consider adding this to the CI?  Is it reasonable that
> the SM (and PM?) user should be able to BUILD, PURGE, COPY, RENAME
> a priv file?
>
> If so, should CODE=nnnn be required for these command (obviously
> needed for BUILD), or should it be transparent?
>
I vote YES.

My 2 cents worth of opinions:

Of course measure should be taken to prevent accidental purging. But why this
has to take the approach of 'make it _real_ tough', as suggested by some, is beyond me.
I assume MPE exactly knows the context of any file, without me having to dig up a
filecode. So why not just give an adequate message and ask for confirmation ? E.g.:

   File XXXXX is a dataset of TurboIMAGE database YYYYY.
   Deleting it will corrupt database YYYYY.
   Do you really, really, really ... want to continue [N] ? _

If you're warned this way and still do it, well so what. If users are _that_ dumb, they'd
better have their backups handy ;-)

Goes without saying that this should only be possible having SM and PM.

Regards,
        Chris Breemer
        Compuware Europe B.V.