DSXchange

karthi_gana wrote:How to avoid this warning message? what kind of action need to be taken?

Don't map dfloat to float.

The dfloat may be a generated one, for example from an Aggregator stage. In this case use the Preserve Type or Decimal Output property.

Another interview question?

No, the "group starting at address 0x80000000" part of the message indicates the 2GB limit for a hashed file with 32-bit addressing has been encountered.

I had thought that DSRID is a column name in the DS_JOBOBJECTS table. It turns out that that's an alias I had created for @ID. So substitute @ID for DSRID in my previous response.

Can't you stop people providing you with such crappily structured files?

Field(InLink.TheString, "|", 1, 1) gives the first field from the delimited string, Field(InLink.TheString, "|", 2, 1) gives the second field, and so on. Parse into separate fields then Pivot.

What drop-down list box? The float data type can more formally be described as a "single precision floating point number". Storage arrangements for these is described in an IEEE standard, and occupies four bytes. The dfloat data type can accommodate much larger floating point numbers, and ...

Job monitor app not running, or "performance statistics" not enabled in Designer.

I would suggest either that the interviewer is incompetent (thinks - "pointy haired boss" from Dilbert) or the strategy is to test your depth of knowledge about what is and isn't part of the product.

Four ways.

Are you also totally new to the C++ programming language? If so, you're about to embark on a fairly steep learning curve.

(I don't have any code that performs this task.)

There is no environment variable of this name in DataStage.

Is this an interview question?

It may be some time before U responds, and it may well be a small question for U. However I have never encountered these terms in more than 12 years working with ETL tools. Is it an interview question?

Possibly a timeout. Try opening a new instance of the client or, if that fails, re-booting the client machine (the "Microsoft solution").

Well, you can always re-start the engine tier.

I think this is a reasonable suggestion because Parameter Sets will never be locked in any environment where they're not being edited. There should, I believe, be scope for re-starting a development environment.

Did they happen to mention what this environment variable does?