DSXchange

No. The bitmap is taken from the design-time metadata not from the run-time metadata.

What does it matter what U tried? U did not ask the question.

The second person personal pronoun in nominative case is spelled "you" in English, not "u". Please strive for a professional standard of written English on DSXchange.

And the resolution was ... ?

U (one of our posters) did not ask the question.

The second personal pronoun in the nominative case in English is spelled "you", not "u". Please strive for a professional standard of written English on DSXchange.

Don't you need to name the job activity, specify its $JobStatus activity variable and compare that to the appropriate DataStage constants for a status of OK or warning? For example, if the job activity is captioned MyJob: MyJob.$JobStatus = DSJS.RUNOK Or MyJob.$JobStatus = DSJS.RUNWARN

NEVER use -9 (SIGKILL) to remove DataStage processes. Use -15 at worst. Be aware, also, of the hierarchy of processes involved in executing a DataStage job - if you kill the parent, the child turns into a zombie, and these are much more difficult to get rid of.

No. Any such documents I may have produced are restricted by non-disclosure agreements with the clients for whom I produced them. I think you will find this to be universal among consultants.

Yes, therefore it can't be any faster than sqlldr, therefore the client's expectations have been incorrectly set.

By default the Transformer stage will execute in all nodes of the default node pool specified in the current configuration file (named in $APT_CONFIG_FILE). You can choose to override this if you wish, but it's not necessary in the job design you specified unless you are doing some task that require...

The problem seems to be between the keyboard and the chair, and your belief that the XML Input stage is a "reader" stage. Not so. You need something else, maybe a Sequential File stage, to do the reading, and the XML Input stage to convert the XML that has been read into rows and columns of data.

Why did you make those particular choices? What were the goals of this match pass? You are aware, I assume, that you are potentially making 80 million comparisons (10,000 x 8,000) - on that basis is not 30 minutes reasonable?

If this were a parallel job it would work like that because the parallel Lookup stage, for other than a sparse lookup, loads the entire reference Data Set into a virtual Data Set - and is documented thus, so it is not a bug. You marked your job type as 390, however, so I'm not sure. I can not even r...

Which of the characters is "special"? Oconv() and Iconv() are not available in parallel jobs. Convert() is. The way I would go about this is to set up a stage variable which is initialized to contain a list of all the special characters. In an output column derivation I would use something like Conv...

Not unit, but uint, which stands for "unsigned integer". The job is showing it as whatever you (or its designer) programmed it to show. If you imported the Bit type from a database, then the database reported it as, and probably stores it as, uint16 rather than uint8. What you think is immaterial.

That value only has eighteen "9" characters and is therefore legal as a BigInt.