[jira] [Commented] (XERCESC-2142) Wrong system detection on HP Tandem NonStop Kernel

[Marc Szymkowiak (JIRA)]

[ 
https://issues.apache.org/jira/browse/XERCESC-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400047#comment-16400047
 ] 

Marc Szymkowiak commented on XERCESC-2142:
--

Hello Roger,

thank you for your fast answer.

Guardian and OSS are two operating system running on a hp nonstop tandem. OSS 
is like a unix os and guardian is guardian.

There are specific compileflags for xerces-c++ for oss and guardian and we use 
the guardian one. 

The cpp program itself called from the cobol can write to the guardian path and 
open files with guardian path. only the SaxParser object has a problem with it.

Xerces try to detect if it is a relative path, and in our situation he try to 
concat the oss with the guardian path /G/xxx/$datax.xxx, but in the cpp that is 
not called from cobol he dont try concat the path and it works with $datax.xxx

 

And thank your for the links but we already now the topics

 

Regards,

Marc

> 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..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
(v7.6.3#76005)

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

[jira] [Commented] (XERCESC-2142) Wrong system detection on HP Tandem NonStop Kernel

[Roger Leigh (JIRA)]

[ 
https://issues.apache.org/jira/browse/XERCESC-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398801#comment-16398801
 ] 

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: 
https://duckduckgo.com/?q=tandem+cobol+convert+guardian+path+to+oss+path&t=canonical&ia=web
and https://groups.google.com/forum/#!topic/comp.sys.tandem/mVHdoYuRQ7Q .  Is 
that any help?


Regards,
Roger

> 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..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
(v7.6.3#76005)

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