DSXchange

Hi, I just want to know if the behavior described below is normal? I defined my ODBC data sources in the .odbc.ini file for all my DS projects. Then I added only the data sources for the DS projects in their respective uvodbc.config (project directory). Now when I import metadata using Designer and ...

... I all understand this. But does answer any questions I have.

I don't think the LANG env variable is used for file default file encoding. When NLS is enabled the Project/Job/Stage NLS seetting is used for that.

Is LANG value only used when NLS is not enabled?

Piyadarshikunal, are you sure about the error messages and instructions part?

Thanks, but I already read that. It still doesn't specify for what it is used for.

I know, what's the purpose of overriding it in the dsenv file?

Hi,

After reading all I could find about NLS for DataStage, it is still unclear to me for what purpose the LANG environment variable is used for?

How DataStage uses it?

Thanks

Hi everyone, I just a simple question about the SCD stage. Question : Does the SCD stage guarantees that the dimension table record will be inserted prior to inserting the fact table record with the dimension's SK? Referential integrity is implemented between the 2 tables so that's why I'm concerned...

For those interested, IBM's patch is JR39963 (currently not available for 8.5.1 but just for 8.5). The patch for 8.5.1 will be available later this year.

Yes exactly

Hi,

I'm just wondering if there is a way to determine easily if a parameter is not used in a job? I'm reviewing some jobs and I find the process tidious...

Thanks

IBM confirmed this is a bug... Waiting for solution. I will post it once received

I'm aware of FP1 but did not find anything related to this in the release notes. I'll wait for IBM's response and post here.

asorrell wrote:No - I haven't seen that - but what release are you on exactly?

On version 8.5

When using the LastRowInGroup function, the data in the non-key fields get corrupted with control characters. At first I thought it was an input data quality issue but I was even able to reproduce the problem with a RowGenerator stage. The job I used to reproduce the problem is very simple: RowGener...