DSXchange

ravindras83 wrote:Also is it true that a stages default partition method (one chosen by Datastage when Auto is selected) can differ with versions/releases of Datastage?

No. At least not so far (version 9.1.2).

ravindras83 wrote:Now I know a person (happens to be my job reviewer) who thinks Entire is not default partitioning method for reference link and we have to explicitly specify (Entire) on the reference link.

This person is wrong.

I have the understanding that internally lookup stage uses "entire" partitioning on the reference link if we choose "Auto". Is there a possibility of above not being true ? (Considering everything is normal and no env variables set etc.) No. You can prove this by inspecting the ...

It seems to me that your Custom Attribute is a Valid Values List type. If this is the case you will not be able to update to any value that is not on the list.

You're setting a rule that requires the count itself to be 9999.

It's not totally clear what you actually want; is it that the count of rows in which CUST_SCORE is 9999 to exceed a certain number/percentage?

As well as what Stuart suggested, make sure that the requisite port numbers are open in any firewall you have installed.

Exponential notation is exactly that - a notation convention. You could convert to (CAST as) VarChar.

Are the metadata (file name, format as well as columns) absolutely identical both sides of the Sequential File stage?

Show the exact syntax you used, the value of APT_ORCHHOME environment variable at the time, and any output (even error message) you received. Issue the command echo $? immedicately after orchadmin and report the output of that.

I see the same thing as Stuart, but at version 8.7. Check your classification table. If it's causing you grief, use an Input Text Override.

What Craig said is your best choice. Make n a job parameter, and compare it to @ITERATION as your loop continuation condition.

Yes, but not if you insist upon using command line utilities. Check out the DataStage API (Programmer's Guide) to learn how to code it more exactly suited to your particular requirements, for example filtering on timestamps and establishing the start timestamp of the most recent run.

To be visible in IA they must be shared table definitions. In general table definitions imported using DataStage are not shared (the exception, possibly, being when the Connector Import Wizard is used). You need to use the Shared Table Creation Wizard in DataStage Designer client to convert local ta...

For already existing components it also provides information about where they're used, in case you want to check (and you should, you know) whether the changed component that you're importing will affect the components that depend upon it.