DSXchange

In the column generator go to the colum options for the generated column and select type as cycle with initial value 1 and increment 0. This will ensure every record has the same 1 for this colum and as posted sum it up in the aggregator

Yes Thanks Ray, but there appears to be a subtle difference in the way both are treated. The lookup stage dedups records based on key columns and retains the first record (multiple rows from reference link disabled) and generates a warning for the same but the look up fileset has an option to store...

Hi

Is the look up table created by look up stage and the look up table created by look up fileset the same ?

how about having a column generator to generate a column with '1' as its value and sum it up for record count ?

if your source is truly 123 i see no reason for data overflow for integer target. Is this happening for every record ? could you share more information regarding source and target stages ? give a try by making the integer column unsigned and see what happens .

For complete information refer to infosphere information server planning installation and configuration guide

We were provided with the basic information of datastage infrastructure and was trying to find out complete information of datastage topology. I recollect the installation information is captured in a response file but wondering where it exists (it's location is specified during installation I guess)

It looks like the director guide does not list all possible job run status, I guess the same should be available as a part of header files some where on the engine. Could some one throw some light over this

Thanks

Craig is right. From 8.5 onwards stage variables can hold null (but the nullability YES/NO option is not available in stage variable properties) from what I recall having read what's new in this release. I have also checked this by explicitly putting nulls using setnull and passing this stage variab...

We are running version 8.5.0.1 and I have mapped a nullable field to a loop variable and found that this loop variable always passes default values to the output colum when the input column is NULL . Ran a check by applying SetNull() to see if the loop variables can hold NULLS (i dont see any proper...

I have read the Redbook "Deploying the Grid Solution with the Infosphere Information Server" though its on linux I guess things are same on AIX too and I have also gone through the code of osh_conductor Dynamic_grid.sh *_PID.wait.sh *_PID.sh But few things are still unclear which are menti...

What I was thinking is, Let the update occur and in worst case none gets updated but all updates were a part of single transaction and now that we are left with 10 inserts let the inserts run in single transaction rather than performing then one by one (good to have one insert transaction for all fa...

Thanks Ray, and the naming convention 'alt_call_name' have any expansion/significance

Was just wondering that it would be more efficient if the update failures would have been collected and inserted in one go rather than each being immediately inserted.

Is there any specific reason which prohibits an efficient approach

Ohhh ! I am starting to recollect having read what is specified as alt_call_name for each function in DSParams as function name equivalent in modify stage and also the same in tranformer generated code.