Nasty bug in Xerces 3 for OpenVMS - VMS

This is a discussion on Nasty bug in Xerces 3 for OpenVMS - VMS ; Hello all, Trying desperately to get done with the last couple of chapters in the SOA book. It seems almost the entire universe has conspired against the completion of that book. The Xerces 3 library had a nasty bug introduced ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Nasty bug in Xerces 3 for OpenVMS

  1. Nasty bug in Xerces 3 for OpenVMS

    Hello all,

    Trying desperately to get done with the last couple of chapters in the
    SOA book. It seems almost the entire universe has conspired against
    the completion of that book.

    The Xerces 3 library had a nasty bug introduced into it.

    $ dp :== $XERCES-C$ROOT:[000000.bin]DOMPrint.exe
    $ dp x1.xml
    Fatal Error at file "", line 0, column 0
    Message: An exception occurred! Type:RuntimeException, Message:The
    primary document entity could not be opened. Id=DEV_DSK:[HUGHES]/
    x1.xml
    %NONAME-F-NOMSG, Message number 00000004

    Notice the slash which is in between the OpenVMS DEVICE:[PATH] and
    FILE.NAME.

    I'm in the process of trying to download a prior version. I know this
    used to work back when VMS was part of the standard Xerces distro.
    Anybody else run into this?


  2. Re: Nasty bug in Xerces 3 for OpenVMS

    In article
    <92093c6d-7d41-4dbe-b482-a30b9a4182e3@d37g2000hsb.googlegroups.com>,
    yyyc186 wrote:

    > The Xerces 3 library had a nasty bug introduced into it.
    >
    > $ dp :== $XERCES-C$ROOT:[000000.bin]DOMPrint.exe
    > $ dp x1.xml
    > Fatal Error at file "", line 0, column 0
    > Message: An exception occurred! Type:RuntimeException, Message:The
    > primary document entity could not be opened. Id=DEV_DSK:[HUGHES]/
    > x1.xml
    > %NONAME-F-NOMSG, Message number 00000004
    >
    > Notice the slash which is in between the OpenVMS DEVICE:[PATH] and
    > FILE.NAME.
    >
    > I'm in the process of trying to download a prior version. I know this
    > used to work back when VMS was part of the standard Xerces distro.
    > Anybody else run into this?


    I've never fiddled with Xerces since either expat or libxml2 has always
    done what I needed, but this is a very common type of porting problem.
    Check the settings of your DECC$ features and check any configuration
    files you have control over to see if there are ways of specifying what
    path or path formats it uses.

    It very much looks as though it's taken your current working directory,
    most likely whatever is returned by the CRTL cwd(), and pasted the
    filename onto it with an intervening slash. My first swing would be to
    enable DECC$FILENAME_UNIX_REPORT and see what happens. After I wrote
    that I went and checked here:

    http://h71000.www7.hp.com/openvms/pr...notes_v30.html
    #creating_appln

    and it says the same thing: enable DECC$FILENAME_UNIX_REPORT.

    --
    Posted via a free Usenet account from http://www.teranews.com


  3. Re: Nasty bug in Xerces 3 for OpenVMS

    On Jan 4, 10:01 pm, "Craig A. Berry"
    wrote:
    > In article
    > <92093c6d-7d41-4dbe-b482-a30b9a418...@d37g2000hsb.googlegroups.com>,
    >
    >
    >
    > yyyc186 wrote:
    > > The Xerces 3 library had a nasty bug introduced into it.

    >
    > > $ dp :== $XERCES-C$ROOT:[000000.bin]DOMPrint.exe
    > > $ dp x1.xml
    > > Fatal Error at file "", line 0, column 0
    > > Message: An exception occurred! Type:RuntimeException, Message:The
    > > primary document entity could not be opened. Id=DEV_DSK:[HUGHES]/
    > > x1.xml
    > > %NONAME-F-NOMSG, Message number 00000004

    >
    > > Notice the slash which is in between the OpenVMS DEVICE:[PATH] and
    > > FILE.NAME.

    >
    > > I'm in the process of trying to download a prior version. I know this
    > > used to work back when VMS was part of the standard Xerces distro.
    > > Anybody else run into this?

    >
    > I've never fiddled with Xerces since either expat or libxml2 has always
    > done what I needed, but this is a very common type of porting problem.
    > Check the settings of your DECC$ features and check any configuration
    > files you have control over to see if there are ways of specifying what
    > path or path formats it uses.
    >
    > It very much looks as though it's taken your current working directory,
    > most likely whatever is returned by the CRTL cwd(), and pasted the
    > filename onto it with an intervening slash. My first swing would be to
    > enable DECC$FILENAME_UNIX_REPORT and see what happens. After I wrote
    > that I went and checked here:
    >
    > http://h71000.www7.hp.com/openvms/pr...c_relnotes_v30....
    > #creating_appln
    >
    > and it says the same thing: enable DECC$FILENAME_UNIX_REPORT.
    >
    > --
    > Posted via a free Usenet account fromhttp://www.teranews.com


    Thank you kindly.

    I missed that line.


+ Reply to Thread