DSXchange

I'm not certain as I'm currently not on an AIX system, but isn't the uv.rc installed in /etc/rc/rc.d directory?

Do a direct 'diff' on the files. If you are using the same userid and logon to connect to the database, these files are most likely different and causing the problem.

Also, what exactly is the error you are getting?

The `.profile' gets run by every DataStage user, so that would not be a good place. The logical location would be in your uv.rc file which is called as part of the startup - but is in a different location depending upon your OS - what Unix version are you running?

p.s. Welcome to DSXChange!

Wouldn't your ODBC configuration be a good place to start looking for differences?

Your error message includes information about repartitioning. A 1-node configuration doesn't need to do that, so if the error goes away then you've narrowed down the probable cause. The Copy stage does the same thing, it might assist in finding out whether the error comes directly in the funnel or i...

The simplest solution is to put all the zip files in a directory by themselves so you don't need a filter. You could also use an external stage with a command like "uncompress -c *Z" to uncompress the files to the data stream (this version will keep the original compressed files on disk).

Limit your data to adjustment_type GE 11 then order the remaining data by ascending claim_id, descending adjustment type and ascending service_number, then take the first unique claim_id and service_number combination.

Brad, does the error occur when both datasets have some data? It is worth it to add $APT_CONFIG_FILE and $APT_DISABLE_COMBINATION as parameters and experiment with a 1-node configuration file and disabling combination at a job level to debug the problem. If the problem persists, could you try runnin...

You cannot get rid of this warning altogether, but you can set up a job level or project level handler for the message and either deprecate it (turn it into an informational message) or remove it from the logs altogether.

It is visible in the add environment option when adding parameters, it is just very well hidden in the list. Even though I know where it is I still miss it.

You need to use a transform stage in SERVER in order to do a lookup; but in PX there a specific stage called (surprisingly) a lookup stage which you need to use.

There is no certification for the Server edition. The certification for PX is done by two companies, Prometric and Pearson VUE for IBM. You can check up information on This IBM page

Yes. Add the job parameter $APT_CONFIG_FILE and you can specify the appropriate configuration file at runtime on a per-job basis.

Two options are either output to a CFF stage and make DataStage do the conversion for you or use the sdk builtin routine "DataTypePicComp3Unsigned" to explicitly convert that value to the binary representation.

There should be quite a bit more in that error message, and that information will be helpful in diagnosing what your problem is. Could you post the full error message?