On Jun 19,  2:19pm, Glenn Cole wrote:
> Subject: How is slash (/) handled in 5.0 ?
> I was editing a job stream on 4.0, changing lines such as
>
>    :comment  **  Print detail and/or summary, according to user input
> to
>    :comment  **  Print detail and\or summary, according to user input
>
> since anything that remotely appears to be a lockword -- even on a :COMMENT
> line -- is prevented from printing on $STDLIST. HP has said for many years
> that this could not be fixed because the "lockword stripping" was performed
> before it is known that the line is a comment.
 
This is still true in 5.0
 
>
> On 5.0, aren't we (well, YOU, for now :( ) allowed to enter things like
>
>    :file abc = /dev/data/myfile
 
Yes
 
>
> ? Doesn't this entire command print properly on $STDLIST?
 
Yes
 
>
> Bottom line: Has the behaviour of "/" in comments changed with MPE/iX 5.0 ?
 
No.  We can distinguish between "/" introducing a possible lockword from
"/" being part of an HFS name, and we still don't know what the command name
is yet.
 
If the above file command was:
    :file abc = a/dev/data/myfile  (which is an error)
the CI would think that "dev" is a possible lockword.
 
Hope this helps,
 
Jeff Vance
 
--