I was trying the lockword on the file equation *not* on the purge command
line. My mistake....

It works thus:

:FILE X=/SYS/PUB/SNTINL005
:PURGE *X/LOCKWORD   <-- fill in your lockword of course


Thanks to all who responded.....

Brian.



On Tue, 10 Jun 2008 21:31:28 -0600, Keven Miller (rtt)
<[log in to unmask]> wrote:

>Brian Donaldson wrote:
>> The construct would be --
>>
>> /SYS/PUB/SNTINL006     (no lockword) -- this file FOPEN's ok
>> /SYS/PUB/SNTINL005/ZTOGDPKZ    -- with lockword the FOPEN fails
>
>Fairchild, Craig D wrote:
> > :FILE X=/SYS/PUB/SNTINL005
> > :PURGE *X/LOCKWORD   <-- fill in your lockword of course
> > :LISTFILE ./SYS/PUB/SNTINL005
>
>Just in passing, and not having tried,
>I assumed part of the reasoning of no lockwords in HFS names
>is because of the syntax clashing.
>The "/lockword" looks like a file/folder name in HFS.
>
>All HFS parsing would see the filename as a directory, and the
>lockword as a file in that directory.
>
>I was thinking about the answer that Craig shows.
>I suppose in posix, a file utility could be provided that puts
>lockwords on a file (via AIF maybe).
>But then the open code would have to be enhanced to check for it.
>
>... but of course, there must be some MPE special code
>already in open to handle MPE (non-posix) files...
>Keven
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

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