DSXchange

Hold on there Tex. Some stages, like the Teradata API will NOT work correctly with environment variables. That is, parameters that contain dollar signs. It could be that the 8.x Stored Procedure is also such a stage. Try a parameter without the dollar sign. If it works, there you go, you can't use t...

You can do both. The XMLInput Stage can be a pass through for non-XML fields. Identify the XML field as a being of Data element XML.
Why not try it? Your box will not explode.

Yes. There is nothing special about the source of the XML into the XMLInput Stage. Read the column that contains the XML into the XMLInput and parse as normal.

We have an open ticket with IBM on this. Ray is there a technical reason why this does not work? It seems kinda fundamental.

We use parameters in the XMLInput stage namespace declaration textbox. I have to believe the XMLOutput stage would allow it as well although I don't know for sure. I very much doubt you can call a function from there. Therefore you'll have to feed the dynamic value into the job containing the dynami...

With friends like Chulett, Ray, ArndW and the rest of the DSxchange Heavy hitters, who needs Support? I don't see how any non-IBM support option, fees per call alternative can compete with this site. Indeed, I always search here first and we have IBM Support.

Aggregate all rows on the XML Input stage? Where?

I believe you are breaking on trId. TrId is your key column and your repetitive element. This would explain the 4350 rows. Define a key column with .../tId as the description. this makes the column the repetitive element. This will break once per tId and put all the TrIDs within a tId in a single li...

1. I usually import via the Table definitions => Import => Plug-in Metadata Definitions as I am currently at an Oracle and Teradata Server shop. You might not have this option. After connecting to the database, there is a checkbox for Fully Qualified Table Names. I uncheck this box. I also verify th...

ArndW is probably talking about the schema name in the FROM clause and I think you are talking about each column derivation being fully qualified with the schema.table.columnname. Realistically, this schema string can only be changed two ways once it is imported into a job; 1. Manually in Designer. ...

Why can't you pass the FileName column directly from the Folder Stage to the stage that contains the stored procedure?

Well said. no, you can't use two folder stages nor can you pass the filename to a Sequential stage. You will have to parse the row into columns yourself. I only use the Folder stage for reading XML chunks, one per file. For that it works great. Others can advise you but I think you'd have to read th...

Ah. You were hoping that your other column definitions would work on the folder stage as they do in the Sequential File Stage. They will not. You can only have two columns FileName and a column for the entire row of a given file. Nothing else. It's documented. Page 201 of the Server's Developer Guid...

There is a limit to the number of utility slots available at any given time in a Teradata system. You are using one to return a single row. I think the Teradata API stage would be more appropriate. Also the IBM documentation clearly states that single Amp Selects are not allowed as a Teradata Distri...

Define an output Column of FileName. The FileName being read by the folder stage will be passed to the output link. Make it the key, Varchar 255. Set Fully qualifed to yes if you need it.