Operating System - OpenVMS

Re: Unexpected ODS5 wildcard file-spec result

 
P Muralidhar Kini
Honored Contributor

Re: Unexpected ODS5 wildcard file-spec result

Steven,

In the case of the directory with name a^.b^.c.dir, when XQP parses the directory filename of A^.B^.C (common routine for both file and directory), it thinks that the last dot (before C) is that of the extension and hence only characters before the last dot are considered rather than the whole filename as it should be in this case. This is why the file spec of *a* and *b* works but *c* does not.

This problem is being worked upon and hopefully there wont be another anniversary :)

Regards,
Murali
Let There Be Rock - AC/DC
Steven Schweda
Honored Contributor

Re: Unexpected ODS5 wildcard file-spec result

> This problem is being worked upon and
> hopefully there wont be another anniversary
> :)

It's nice to know that it's on someone's
to-do list, but now that my patch access has
been cut off, a fix which I can't get may not
make much of a practical difference to me.
Joseph Huber_1
Honored Contributor

Re: Unexpected ODS5 wildcard file-spec result

To narrow the time when the behaviour was introduced:
in VMS 7.3-1 it was not yet present:

$dire [.*c*...]

Directory DISK$HUBER:[HUBER.SCRATCH.a^.b^.c]
file.dot;1
Total of 1 file.
Directory DISK$HUBER:[HUBER.SCRATCH.a_b_c]
file.und;1

$ show process /parse_style
...
Parse Style: Extended

Total of 1 file.

http://www.mpp.mpg.de/~huber
P Muralidhar Kini
Honored Contributor

Re: Unexpected ODS5 wildcard file-spec result

Hi Joseph,

>> To narrow the time when the behaviour was introduced:
>> in VMS 7.3-1 it was not yet present:
Thanks for the information.

I thought it to be a day 1 bug which probably got introduced when support for extended characters were added to XQP.

As the problem is not seen on V73-1 version, it must have been introduced in one of the later versions. Interesting.

Regards,
Murali
Let There Be Rock - AC/DC