Hi,

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

For example:

MANAGER.SYS,PUB :build test/lockword
MANAGER.SYS,PUB :print test
LOCKWORD: TEST.PUB.SYS?

MANAGER.SYS,PUB :print ./TEST
                       ^
LOCKWORD VIOLATION  (FSERR 92)
The PRINT command failed. (CIERR 9080)
MANAGER.SYS,PUB :



Now some may argue that since Posix has no concept of lockwords (and we
_are_ referencing a file via Posix symantics) 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)

The operating system knows that there is a lockword:


MANAGER.SYS,PUB :listf test,-3
********************
FILE: TEST.PUB.SYS

FILE CODE : 0                   FOPTIONS: BINARY,FIXED,NOCCTL,STD
BLK FACTOR: 1                   CREATOR : MANAGER.SYS
REC SIZE: 256(BYTES)            LOCKWORD: LOCKWORD
BLK SIZE: 256(BYTES)            SECURITY--READ    : ANY
EXT SIZE: 0(SECT)                         WRITE   : ANY
NUM REC: 0                                APPEND  : ANY
NUM SEC: 0                                LOCK    : ANY
NUM EXT: 0                                EXECUTE : ANY
MAX REC: 1023                           **SECURITY IS ON
                                FLAGS   : NO ACCESSORS
NUM LABELS: 0                   CREATED : WED, SEP  1, 1999, 10:49 AM
MAX LABELS: 0                   MODIFIED: WED, SEP  1, 1999, 10:49 AM
DISC DEV #: 1                   ACCESSED: WED, SEP  1, 1999, 10:49 AM
SEC OFFSET: 0                   LABEL ADDR: $00000011.$005C6420
VOLCLASS  : MPEXL_SYSTEM_VOLUME_SET:DISC



So why doesn't it ask for it??

Now looking thru my HPFOPEN documentation I see that there is no way of
specifying the actual lockword.   Do you think this is an oversight?


Feedback on this issue will be interesting ;)



Jamie.