RE: XML question

Vern,

Have you added a reference to "/QIBM/XML/DTD/QcdCLCmd.dtd" in that XML? 

-Walden 


------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
vhamberg@xxxxxxxxxxx
Sent: Monday, September 12, 2005 11:53 AM
To: Midrange Systems Technical Discussion
Subject: Re: XML question 

No answer for you, but joining you in frustration. IBM's Retrieve
Command Definition (QCDRCMDD) API generates XML that describe the
command. I tried to use WDSC to work with it, to make a web page that'd
display the contents nicely. Unfortunately, in the XML perspective, when
validating the SML, WDSC reports "Document is invalid: no grammar
found". I find it silly and possibly stupid that IBM can't generate XML
that it's own tool can handle.

'Nuf said!
Vern
-------------- Original message -------------- 

> Mornin' Folks! 
> 
> I am working on converting a file to XML. I have done 
> this before (successfully, too) but this time, I am 
> getting a "poorly formed XML, line one column 1197" 
> error. When I look at the generated code with note 
> pad, I see "" which doesnt 
> appear anywhere else. I have tried debugging it (and 
> F22 stepping through all the procedures and modules) 
> to no avail. 
> 
> Any idea as to why this mystery tag is appearing? WHen 
> I line by line compare to the successful ones, I dont 
> see a difference. (insert a growly dog noise here) 
> 
> Thanks, JenR 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>