DSXchange

So if the structure of the XML is correct, the data must be validated afterwards in a Transformer. Check there for values outside of what any validation would catch.

Yah, funny dat.

Can't say for sure where they are stored but assume it would be one of the "RT_" hashed files built by the compiler, seeing as how compiling a job loses those changes... perhaps RT_CONFIGxxx? As to the retrieval part, there is the DSGetParamInfo() function with two InfoTypes in particular:...

a) Not Supported officially.
b) Discussed here alot.

Search the forums for "CLOB" and you'll see what I mean.

Exactly.

Try an exact search of the forums here for "floating point decimal not fully supported" and see if anything it turns up helps.

There's more to it than that, for example: http://www.w3.org/TR/xml11/#sec-xml11 So, unless the underlying parser DataStage uses is already 1.1 compliant, then I'd say no as it sure seems like it would need to change to support all that. Hopefully Ernie will be along and expound on this for us - if ...

Then time to mark the post as Resolved using the green button at the top of the screen. Any discussion about reading parameters from a file should happen in a new post, not this one.

Both export jobs and basically one exports entire projects while the other can handle individual jobs.

They are all related. Did you have any space problems where DataStage is installed? Did you try to reindex the project?

What else is in this shared container?

As noted, if you've got the parameter in the Sequence to pass to the first activity, simply pass that same parameter to any other activity as well.

What happened in the two hours between when the UVFIXFILE did not work (diagnostic only) and then suddenly things were working again?

"Hotrod" hasn't posted here for 4 years. Best to go to the source for problems with that application.

What makes you think the lookups are the problem? And are they really "Universe" lookups or are they Hashed File lookups?