John writes:
> Sounds Great!  Confirming changes to/from IMAGE's file codes would be a
> nice add-on.  I'm not sure it would be necessary for other PRIV mode file
> codes.

I don't like the confirmation prompt idea because not only is it going to
introduce another difference between interactive and batch access, but if
it only applies to "Image" files, then it may be more of a surprise when
the user runs into it.  It will complicate the situation for people who
want to use the command programmatically.

If you want a confirmation mechanism, what about requiring that the user
specify both the old and new filecodes in the command?  This would
indicate that at least they have some idea of what the filecode was.

Or rather than prompting for confirmation when changing an "Image"
filecode, what about requiring a ";IMAGE" keyword on the ALTFILE
command for these filecodes?

I agree with the idea of requiring CREATOR access for changing filecodes.

G.