Mark Bixby and Lars Appel were kind enough to reply off list and help me
make sense out of not being able to save or build a file in across accounts,
and to feel less embarrassed for asking, not to mention providing me with a
good work around, creating a directory under the group. So anyone with
access via SAMBA can access the STORE listings see when and where a given
file was archived to tape.

I must admit that being able to overwrite an existing file across accounts
seems more problematic to me than being able to create a new file. Being
able to save across accounts seems somewhat like the issue with renaming a
file across accounts, which we can do now:

> Before, the creator field of the file label was only 8 bytes (i.e.
> user ONLY).  Thus if somebody outside of the account were to create a
> file in another account, the creator field probably wouldn't be valid.
> But on MPE/iX the creator field is now 16 bytes (i.e. user AND
> account), so I'm not aware of any obvious reasons why HP couldn't
> make SAVE:ANY really and truly mean it.

I'm not sure if being able to build and save across accounts would be as
useful, so I'm asking. The other side of this is how might this be
accomplished, while maintaining compatibility? I guess HP has gone thru this
once already, with RENAME. Would just making this possible be acceptable, or
would it be likely to break existing job streams and command files? Should
some mechanism be added, perhaps a SAVE permission on the account, and if
so, how would that be kept compatible? What would happen to existing
accounts, and existing jobs that set the other account permissions?

If this seems worthwhile, what would have to happen to suggest such an
enhancement?