DSXchange

Hard to say, but if that is your entire document, I might suspect some unprintable character in the "whitespace"....look at it in hex --- you may have something other than hex 20's where blanks should be, or something other than CRLF or LF for end of line.......(hex 'OD' and '0A').... .......

paste a chunk of the actual file itself, SOAP envelope and all, in its original form.

The best reason I've seen for RCP is when you have a set of functions (stage types) that you want to use to process a vast set of tables, each that has a different structure ....especially in cases where you don't need "really specific" transformations on certain column names...... Entire ...

I always evaluate the use of Server Jobs for XML, especially if (a) I'm not using QualityStage (b) I'm in a hurry and don't have time to mess with column import with datatype and nullabilityissues (c) I'll be dealing with a lot of large variable text strings. (d) I don't need high volume parallel pr...

Could be a lot of things......Some initial suggestions would be .....Check your filenames, check your security rights, test with other xml documents, try using a Server Job instead to "get to know" xml Pack (use the Folder Stage in a Server Job [take a look at the xml entries in my blog be...

Looking more closely, I see now that you are parsing first a SOAP envelope (XML) and then probably subsequently parsing the xml beneath it. So do your initial testing with just the xml payload, manually removing all the SOAP stuff outside of it. You might also want to consider two XMLInput Stages......

We assume that all things done in steps like this are just "tests"....playing with it to get it to work initially and understand the behavior. So, yes. I would expect that you are reading one file and can edit it, change it, alter it via Notepad or other editor to determine what is require...

The defns is probably the issue. Here are some things to try: a) if you imported via the xsd, be sure that you also "load" your table def into the "namespace" tab on your output link (similar button to what you use to load your columns). b) in a test document, remove all the name...

That seems to be what is happening......do you really need or want 8 concurrent readers? How much volume do you have? Be prepared also, for the fact that the messages will no longer be ensured to be in-order (many queueing applications require that the messages be processed in a particular order). Y...

First, let's simplify things.... what happens when you have a config file with a single node. Let's not move into multiple readers just yet.

What happens?

Then tell us more about the job...what stages exactly do you have in the job, in sequence, for the job you are observing?

Ernie

Check out a tool called XMLMax....it has ways to break up large XML and might be able to be used prior to reading by DS.

Ernie

How about "it's a black box, leave it 'as is'...don't touch it, don't change it, and don't spend important brain power on it."

More seriously, I suspect that customer support can probably provide more formal steps, but changing it seems like more trouble than its worth.

Ernie

Why? Not to be sarcastic, but really to understand the business reason? Did someone lose the pwd?.....and which pwd is it? One for a db connection?

Ernie

There is a Hyperion Pack available now...... I haven't seen or touched it yet, so can't give you details, but it may be worth looking into. For years though, directly writing to a cube wasn't in big demand because most of the cube vendors prefered defining and manipulating those things in their own ...

Right...I'm referring to the formal "import" syntax within an xsd. It is a formal "command" that is available for xsd's that "points" to additional xsd's. (like an "include" statement in many other languages). That's what the current XML importer does not supp...