DSXchange

Have you attempted to reset the jobs in question in the director and then looking for a log entry titled "from previous run..."? This might help you diagnose the problem.

It will load the file to memory until it determines that it won't fit; the program isn't smart enough to detect from the file size that it cannot fit. This load causes IO and CPU and can take a long time on many systems, so it is best to do as Craig has already suggested and don't set the switch.

...If a particular stage is used for look up and simultaneously updated in the same job... That is a very contrived example, since turning on any type of buffering would force the same thing to happen without use of IPC. In addition, if you make the IPC buffer size less than double the record size ...

If you are using a simple TRIM you will be removing all leading, trailing and duplicate spaces as well at tabs from the string. This is not the same thing as a null. I recall a setting in PX for Oracle where a string of spaces can be treated as null, but as far as I recall that doesn't happen in ser...

The routines cannot be viewed from the operating system, the data is stored in hashed files and can only be accessed using DataStage.

I have to partially agree and disagree with the previous 2 posters regarding how an IPC stage affects processing. In a nut shell IPC stage allows as to use multiple CPUs at the same time. The important differentiation there is not the CPU usage, but that by using an IPC you have created distinct pro...

What you want in this case is to use the multi-instance capabilities of DataStage.

DataStage server doesn't care about data types. The trim function can be used on string or numeric contents, i.e. you can TRIM("123",'2','A') to remove all 2's from a number.
What kind of a TRIM() call are you using and what do you wish to do with the data?

It looks like your selector doesn't account for all possible data values.

What selector mode have you specified? What have you put into your "not found" condition?

-1 means you have specified one or more invalid input parameters. Is your first parameter, the job handle, being set correctly with a DSAttachJob() call or using the DSJ.ME variable? Are the stage and link names correct? Once all 3 are set appropriately you will get a non-negative number back - eith...

Have you tried entering this SQL directly to see if the same error occurs - and if it might give more output?

If your input data is sorted by key and fld1 then you can use the "classical" approach as done in Server jobs. Put in a transform stage and use stage variables to store your interim output columns and last column data data, set the constraint to only output rows when the key-fld1 changes and output ...

The DSGetJobInfo() call will retrieve much of the information you are looking for. There are other DSGet{Link/Stage/Parameter}Info() calls which supply additional information.

Another option is to check this forum for references to Kim Duke's ETLSTATS

In your sequential definitions what character did you specify as EOR?

pre-sort the incoming data and tell the aggravator about it.