DSXchange

Yes, so use my second suggestion. Perhaps use Sort-Merge as the collection algorithm, if it makes any sense to do so.

Welcome aboard. Challenge them to provide a reference. They are right in that the node name is irrelevant. It is only for the convenience of humans and programmers. DataStage treats the first-named node as node #0, the second-named node as node #1, and so on. Does that make any difference? Probably ...

I'm not clear what the problem is using the Row Number Column property with the Sequential File stage. Could you please clarify?

Otherwise, use a sequential-mode Transformer or Column Generator stage downstream of the reading stage to add the row number.

Read the manual.

Probably someone has the log open for that job. Have them close it.

Several options are available, including the one you indicated. They include: calling the stored procedure from a parallel stage (probably one forced to run on a single node) calling the stored procedure using BCI functions in a before-job subroutine including the server ODBC stage in a server Share...

alnum() function.

ANY additional operation will add demand for resources.

The fact that little/no difference was observed in elapsed time indicates that your engine had surplus resource availability.

Welcome aboard.

Do you have any XSD that describes the XML layout?

If not, you will need to generate metadata by importing a "table definition" from the XML (in a file) itself.

Or, perhaps, specify the -x option with your orchadmin command.

Q1. True. Store selected standardized values in the reference table as additional columns. Thus you don't have to re-standardize anything. After you update the reference table, you will need to re-generate frequencies, but that can be done "off line". Q2. Source only needs to be a persiste...

It appears that both (d,s) and (m,s) are checking only for a one- or two-digit number, without performing any range check.

If you think this is a bug, please contact IBM, get their take on it, and let us know.

Anyone else like to test it using other versions?

You might use the Performance Analysis tool or, perhaps, the DataStage Operations Console to answer this question.

As well as all that I would, if possible, put resource disk and resource scratchdisk on separate drives. They are accessed quite differently. Scratch disk tends to have a more random pattern of access, where as DataSet segment files are effectively read sequentially (each).

You should be able to make one call to the webservice for each row being processed in your job (I'm assuming you're using a WebService Transformer stage or similar). To invoke three webservices, or to invoke the same webservice three times, you would need three WebService Transformer stages in the j...