Originally posted by: SystemAdmin

Hello Folks,

I'm using WTX 8.0 We are having problems validating some XML data. The type tree was imported from the xml schemas using the Xerces option. OK, that's the background info. Now for the problem.

I'm trying to debug the issue and figure out where the data is choking against the type tree. I can see where turning on the trace file produces an XML log of the trace, as well as the old .mtr trace file. Can these two files be used together to debug, or do you have to just go by the xml trace, and ignore the .mtr file. Also, how does one use the new xml trace file? I'm having a hard time seeing how this is helpful. If anybody has some insights into this debug process, I would appreciate it. Thanks in advance

Brian

PS. I did search the online library high and low, but I couldn't find squat about that new .xml trace file. Did I miss it somewhere?
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Bring the XML log file up in a browser (IE works best). You will get different tabs. I think at that point you will see that it is useful. For now, ignore the *.mtr file. Sometimes you get a nice error in there but it should be replicated in the XML log file.

Yvonne
Resistance is NOT futile.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Thanks Yvonne,

OK, I have to admit it, I went through the online library one last time right after I posted that blasted message, and I found the 6 pages in the map designer manual talking about this new xml trace. Arg! :-)

So I was just doing what you were suggesting when I saw your post. However, when I open the .xml file in IE, I get the following error message in the browser:
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

---

Access is denied. Error processing resource 'file:///C:/Ascential/DataStageTX_8.0/xvallog.xsl'.
I've checked, and the .xsl file is in the proper directory. Any thoughts?

Brian
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

It seems to work ok at 8.0.1 on windows XP.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

This sounds like a system thing. Never seen it before and I do not have the problem from logs created in any of the versions. Sorry!

Yvonne
Resistance is NOT futile.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Thanks for the replies folks.

I finally figured it out today. It looks like that IE was not able to properly access the .xsd files referenced. So, I placed them all in the directory of the .xml log file, modified all the paths in the .xsd files to be relative to the directory they were in, and walla! It works. I think it might have something to do with the tight control of our C drives here at work. We don't have admin rights to our C drives, and maybe the IE needed that in order for it to work with these xsds? I don't know, but I thought I'd post the update.

Thanks to all for the assistance...

Brian
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: Margo

Does anyone know how to NOT generate the xml log?
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange