DSXchange

This is a DataStage function so it will only work within DataStage (in no sense will it work "in Oracle database"). It still relies on sorted data to work properly.

The value for that parameter comes from the column marked as Key in your job design. What you have to make certain is that the column name in the WHERE clause is valid in Oracle.
Only then should you be concerned with checking the values that are passed via that Key column.

Sort by field01 then by field02 (descending) prior to the Transformer stage and use stage variables to detect a change in field01. Constrain the output to those rows where you detect a change in field01.

Did you read my earlier post? If so, did you do what I asked? If so, what did you see?

OK, let's simplify things a bit. Declare a stage variable as type VarChar(8) and assign SAP_ATL_COST_SAVING_In.ZPRT_COSTSAVINGS_BEDAT to it (applying TrimLeadingTrailing if you must). Your expression will then be much simpler (and thus easier to maintain. If sv="00000000" Then SetNull(...

No. That's not how parallel jobs work. They move (large) blocks of data. The Data Set is copied (using a copy operator) into the virtual Data Set associated with the link to which it connects. Yes, you can use a Filter, Switch or Transformer stage to limit what comes off that link, but operators all...

Still haven't seen the control records from Attu, particularly //JOB.STARTED.NO.

Oh yes there is/are!

WHERE keycolumn = :1

:1 is a bind parameter

A bind parameter is not the same thing as a job parameter.

Use a Transformer stage.

Seriously.

That's why all the fiddly QS stage types no longer exist - you have the DataStage engine to do all that for you.

laknar wrote:Is Mapstage is called as Datastage TX Job in Parallel Job processing Stage.

That's the bunny.

You can't supply NULL to StringToDate() - you therefore need to re-arrange your logic and only do StringToDate() in the Else part of your conditional (If) expression.

The error message relating to set_null comes from the conversion process from your "BASIC" expression to C++ code (operators).

Substring and concatenation will suffice. InLink.TranDate[1,4]:"-":InLink.TranDate[5,2]:"-":InLink.TranDate[7,2]:" ":InLink.TranTime[1,2]:":"InLink.TranTime[3,2]":":":InLink.TranTime[5,2]:".":InLink.TranTime[7,2] I have assumed here th...

When you're viewing data you're supplying reference key values. This suggests that the illegality is somewhere in the WHERE clause. Examine the SQL (in the job log).

Use a server job or a BASIC Transformer stage. Examine each character with the BYTELEN() function - this will be greater than 1 if you have a multi-byte character. But do you really know what you're doing? For example, if you're using "pure" Unicode, every character is multi-byte (either two or four...

Or echo the first line in a before-job or before-stage subroutine (for example) then use the Sequential File stage to Append to the file.