Roger Leigh commented on XERCESC-2142:

Bear in mind that my knowledge of Tandem Non-Stop and Guardian have come from 
the Wikipedia page...

The Open System Services (OSS) POSIX layer is presumably what you need to use 
to compile and run Xerces-C++, and any C++ program using Xerces-C++.  All 
Xerces-C++ functions using the standard C file open functions would presumably 
be using the "OSS paths".  Now, I have no real clue what a Guardian path is, 
but I would presume that the caller of the Xerces-C++ methods from COBOL would 
be expected to do the path conversion from Guardian to OSS?  Surely there's 
some built-in means of doing this?  I don't think there's much that Xerces-C++ 
itself can do about this, and I don't know if anyone here has any expertise 
with this rather esoteric hardware and software environment who could provide a 
more useful answer.

A search shows up: 
and https://groups.google.com/forum/#!topic/comp.sys.tandem/mVHdoYuRQ7Q .  Is 
that any help?


> Wrong system detection on HP Tandem NonStop Kernel 
> ---------------------------------------------------
>                 Key: XERCESC-2142
>                 URL: https://issues.apache.org/jira/browse/XERCESC-2142
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: SAX/SAX2
>         Environment: HP Tandem NonStop Kernel, Guardian OS
>            Reporter: Marc Szymkowiak
>            Priority: Minor
> SAXParser parse function think the systemid is a oss path /G/..... but it is 
> an Guardian path $DATAx.xxxx.xx , but the problem only occurs if the cpp 
> modul is called from an cobol server, if we call the function from a normal 
> cpp main program it works,
> linker and compile flags are the same

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to