Sletten Kenneth W KPWA writes:
> [Jeff Vance] asked if this would fly:
>
> > 1. SM can alter any file's file code to any value (even negative)
>
> > 2. Non-SM can alter any file he/she has WRITE access to,
> > to a file code whose numeric value is >= 0.
>
> > 3. Non-SM cannot alter a file with a negative (PRIV) file code
> > to any file code value.
>
> Sounds reasonable to me....  Just one suggestion, along the
> lines of the recently-implemented "DBUTIL confirm PURGE
> and ERASE" enhancement:  Even if SM, for PRIV files only
> how about some kind of   "Are you *sure* you want to change
> file code of PRIV mode file < fully qualified name > to
> < new file code > ??

IMHO we only need "Are you sure?" prompts for operations that are painful
to reverse (i.e. PURGE or ERASE).

In the case of :ALTFILE CODE=, if you realize you just made a mistake, just
alter the code back to the original value.  No fuss, no muss, and no real
need for an "Are you sure?" prompt to slow you down.
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support               Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)