DSXchange

Great. So like we have been discussing, build your Job with something like a RowGen or dummy flat file as the source (NOT isdInput since you don't want the job to be "always on"), with only one row to be processed, and then in a downstream transformer, have a Job Parameter in a derivation ...

Great. So like we have been discussing, build your Job with something like a RowGen or dummy flat file as the source (NOT isdInput since you don't want the job to be "always on"), with only one row to be processed, and then in a downstream transformer, have a Job Parameter in a derivation ...

Exactly.

The default behavior is for the element to simply not appear if the value is truly null.

What release are you on?

Ernie

This is a wonderful example to illustrate what the repetition element means. First, it has nothing to do with "key" --- that is simply the only simple indicator available for this important characteristic. By marking an element as the "repetition element" you are telling DataStag...

...however, I still must add my confusion to this thread as to what your ultimate question is. Let's say that you have an ISD Job that performs a lookup. And you want that ISD Job to handle multiple rows in an array (ie...be able to send up 1000 rows... perform the lookups....and then send back 1000...

pass it xml, or a string of comma delimited rows.... put only one column on the output link from the ISDinput Stage, and then pass that to either a pivot or an xmlOutput Stage.... one row in becomes nnnnnn rows after xmlOutput or pivot. There's your "array".

Ernie

I've seen other sites do exactly as Ray describes. 9.1 offers the "is-a-type-of" relationship, which isn't exactly the same as the concept you are describing, but could be used in that way. The modifier and type properties are holdovers from modeling concepts in InfoSphere Data Architect. ...

...-btw --- I did some brief checking....it appears that attributes are not allowed to be declared nillable in an xsd, which somewhat explains the behavior.

Ernie

There are a lot of us 'ol server types around. :). You shouldn't need the second xml stage, unless you are playing some other kinds of tricks. Just go directly to a seq stage and put a 000 in both the delimeter and quote properties and it will work fine. ....and I've passed HUGE documents without an...

Well...they're attributes, so they are treated a bit differently (than if they were sub-elements). You will probably need to zap them out of the string afterwards by sending the produced xml to a downstram transformer and use ereplace(). If these are the only two, that's the easiest solution. Just p...

Cool! Nice solution for those times when it might be needed......and then get it on record that the "other" tooling needs to upgrade it's parser.

No idea at the moment.....I can only guess, since clearly the Linux server is "seeing" your desktop and you were able to select one of the bridges, and your local client tools can find the server ok. You might try adding the linux server's ip and hostname to the windows machine's hosts fil...

Are you talking about the WSDL for the service or the Job that "is" your service, or are you talking about how to CALL that service from within ANOTHER DataStage Job? For the Job that "is" the service you don't have to do anything. One will assume that if you are choosing array f...

Are you talking about the WSDL for the service or the Job that "is" your service, or are you talking about how to CALL that service from within ANOTHER DataStage Job? For the Job that "is" the service you don't have to do anything. One will assume that if you are choosing array f...