DSXchange

You can buy a server-only licence, even in the latest versions. The SAP R/3 Pack was originally designed for server jobs, and continues to be supported for them.

Not possible with CFF stage.

Four nodes? Four counts.

Two other possibilities. Your Copy stage might be being optimized out of the design (so could not deliver a row count). Set its Force property to ensure that it is in the flow. Instead of the input row count to the Data Set stage you could obtain the output row count from the Copy stage (which is ne...

jhansi wrote:without transformer can we do this scenario?

Is this an interview question?

Why do you want to do it without a Transformer stage?

It used to be the case that the Transformer stage was inefficient but they did a lot of work to it (version 8.1.x ?) and that advice is no longer correct.

You must ask the provider. I am aware of at least 14 different ways in which Japanese characters may be encoded, and that's without referring to mainframe encodings.

You want to allow for null output, so you will need an If..Then..Else to cover the possibility that all source columns are null. If IsNull(InLink.colA) And IsNull(InLink.colB) And IsNull(InLink.colC) And IsNull(InLink.colD) Then @NULL Else NullToEmpty(InLink.colA) : NullToEmpty(InLink.colB) : NullTo...

Probably a fix to /etc/hosts file.

DSJ.ME is a DataStage constant that you would use in the routine code itself, for example in calls to functions such as DSGetJobInfo().

You will need to create and compile the routine - it's not there by default. Create a new server routine and make its type "before/after subroutine".

The compiler (xlC_r) is not part of the deal. You can get away with only a single compiler licence, but this means that only one developer will be able to compile at any one time.

Tables in the DSODB schema are open and documented. You can examine the scripts that create them.

8.7 Operations Console also relies on the process metadata being stored in a table. When setting it up you create a database schema called DSODB. This is open and documented. So you could create appropriate views on it for your users - or show them just the pictures from Operations Console!

Then you're not doing it right. Show us exactly what stage variables you are using, how each is initialized and how each is derived as each row is processed.

Did you search DSXchange? The technique of using stage variables to remember a value from the previous row has been explained on a number of occasions. In short, though, the technique relies on the fact that stage variables are executed in the order (top down) in which they appear in the stage varia...

You need to know precisely how the Japanese characters are encoded (there are many different maps used) and you need to specify that NLS map when processing in DataStage.