XML Phantom

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
jim.paradies
Premium Member
Premium Member
Posts: 25
Joined: Thu Jan 31, 2008 11:06 pm
Location: Australia

XML Phantom

Post by jim.paradies »

I've got a Server job which is fairly simple.

FOLDER----------->XML---------->ODBC

The job produces the following warning:

DataStage Job 1839 Phantom 10528
XSLT Warning: Source tree node: SoftwareResourceLocator. (, line 168, column 64.)

Now when I run it with tracing on, the warnings disappear.

I'd appreciate any help on resolving this or even if someone can tell me how to view the XSLT generated. I'm not certain but I thought that in DS Server Version 6, I could see the generated XSLT in the log when tracing was turned on.

Thanks
Jim Paradies
lstsaur
Participant
Posts: 1139
Joined: Thu Oct 21, 2004 9:59 pm

Post by lstsaur »

For version 8.0.1, you must apply the patch in oder for select "Tracing" tab to work.
jim.paradies
Premium Member
Premium Member
Posts: 25
Joined: Thu Jan 31, 2008 11:06 pm
Location: Australia

Post by jim.paradies »

In case anyone's interested.

If you ever have to use the XML stage, make sure that you use the text() function when defining a path to an element otherwise DataStage spits the dummy and you end up with a Phantom.
Jim Paradies
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Thanks for the information.

Oh, and in case anyone's interested, had to look that one up. :wink:

Spit the dummy.
-craig

"You can never have too many knives" -- Logan Nine Fingers
eostic
Premium Member
Premium Member
Posts: 3838
Joined: Mon Oct 17, 2005 9:34 am

Post by eostic »

Hi Jim...

Thanks for the info.... for additional detail, can you define what was there instead of the text() bits?

Was it something like /element1/element2 ?
or /element1/element2/ ?

The second example above is somethng that is critical for many/most techniques, and something I use all the time. It would be interesting to know if that's what causes your phantom. Of course, as noted in the thread, there is a patch to XMLPack, although the phantom result was not one of the smptoms defining the patch I'm thinking about.

I recall in 7.x the phantom used to appear regularly with XMLPack in general when used on Solaris, although I see you are using Windows.

Ernie
Ernie Ostic

blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
jim.paradies
Premium Member
Premium Member
Posts: 25
Joined: Thu Jan 31, 2008 11:06 pm
Location: Australia

Post by jim.paradies »

If you were using straight XSLT, you could define the value of an element like this

Code: Select all

/node1/node2
but with DataStage, you have to explicitly use the text() function thus:

Code: Select all

/node1/node2/text()
Jim Paradies
lstsaur
Participant
Posts: 1139
Joined: Thu Oct 21, 2004 9:59 pm

Post by lstsaur »

So, you didn't need to apply the patch for XML stage at all. Just wondering were you able to accessing the generated XSLT style sheet from the job's log.
jim.paradies
Premium Member
Premium Member
Posts: 25
Joined: Thu Jan 31, 2008 11:06 pm
Location: Australia

Post by jim.paradies »

lstsaur,

Thanks for your reply before.

In answer to your question, no I haven't applied any patches. I will be looking at doing that though. It would be very handy to be able to see the generated stylesheet.


Thanks again.


By the way, is there a specific patch that I need to be asking for?
Jim Paradies
Post Reply