Paul writes:
> I'm processing a list containing the 'posix style' name of MPE files.   If
> a file in the list has a lockword I do not get prompted to supply it (See
> below):
>
> <SYS>:print ./TUNE2
>             ^
> LOCKWORD VIOLATION  (FSERR 92

The problem in this particular case is that MPE does not consider this an
HFS file because apparently you're in an MPE GROUP at the time you try this.
Files with lockwords that exist outside of MPE GROUPs have their lockwords
deactivated until such time as the file is moved back into an MPE group.  If
the file is in a GROUP and it has a lockword, then you must specify the
lockword in order to open the file, and there's no way to embed a lockword
into HFS syntax and there's no way to pass the lockword independent of the
filename (that I know of).  Also the open won't prompt for a lockword if you
use HFS syntax to name it.  There are privileged ways of bypassing the
lockword of course, such as the "MUSTOPEN" variant of FOPEN.

G.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *