> Is it a "feature" of MPE that you cannot specify a lockword on
> an MPE file accessed via Posix semantics?

Yes, by design.

> For example:
...snipped...
> Now some may argue that since Posix has no concept of
> lockwords (and we _are_ referencing a file via Posix semantics)
> it is correct in its refusal to request a lockword.
>
> But I would question that idea since the command being issued
> is in the MPE shell and the file is in the MPE filesystem
> (irrespective of how it is "referenced", e.g. TEST.PUB.SYS or
> /SYS/PUB/TEST)

A lockword can be specified inline in MPE filename syntax,
e.g. print file/lockwd

It is ambiguous to specify a inline lockword using POSIX
filename syntax, e.g. print ./file/lockwd

Due to this conflict, and the fact that POSIX file security
does not include the concept of a lockword, we decided to
not accept lockwords via the POSIX syntax and semantics.  It
did not make sense to us to support lockword prompting and
inline specification for MPE syntax, but support only lockword
prompting in POSIX syntax.

> The operating system knows that there is a lockword:
...
> So why doesn't it ask for it??

Hopefully my explanation above helps some.

> Now looking thru my HPFOPEN documentation I see that there is
> no way of specifying the actual lockword.

Correct.

> Do you think this is an oversight?

I don't.

regards,
Jeff Vance, CSY