DSXchange

DataStage keeps information internally on whether or not the transform stages have changed and will save compilation time by skipping over unchanged stages. If, for some reason, the stage has changed but DataStage hasn't flagged it then a normal compile might result in an incorrect runtime object.

Basically you can use DataStage code to parse the bitmap portion or use an external program to do so (c++ or perhaps PERL or the like). Is the BITMAP contents actually binary or just variably structured text? The first step should be to define your rules in "clear text" so that you know th...

Use the checksum function and then examine the output character field. Do you think that can be converted to an integer or bigint?

The terms are not fixed, each installation has a different definition of the terms based on context. If you could explain your context for the question then you would (perhaps) get a more definitive answer.

Is this 3 different columns or one string of value "1,15,201"? or 3 different values for one column?

Assuming the latter, "IF LEN(In.Col)=3 THEN '5':In.Col[2,2] ELSE In.Col"

That last post is a bit confusing; you say that the data is the same because "winmerge" show different number of records

Use "diff" to compare your two source files to see if they are indeed the same.

The function you are looking for is SEQ(), which will return the numeric representation of the input single character, the function that returns a character given a numeric representation is CHAR(). Both can be looked up in the documentation and exist in both Server and Parallel versions.

You first need to determine what is taking 6 minutes. Is it the "SELECT" on the database? Make a simple copy of your job that doesn't do a join or a database write, just your 2 database reads going straight to PEEK stages? How long does that take?

Was DataStage reading from the database when it was failed over? If DataStage doesn't get an error from the DB then it cannot know that there is an error. Normally during a write the DB must return information, either an OK or an ERROR; but during a read where DataStage doesn't know how long it migh...

I'm in Germany right now... I have a PLZ.

In your case, have you talked to your DBA and asked what your limits are on number of cursors? Are they per-user or per-system? Can you DBA monitor or view open cursors?

What is the exact COBOL data type and the DataStage Datatype into which it is going?

I would add the "reset if required" check mark to the job activity in the sequence, as recompiling is not really an option.

The "Job Activity" in job sequences has an automatic wait-for-job-to-end attached to it, so you would start your jobs by executing the appropriate command line dsjob. You could put a before-job call in the instance jobs that update the table with status of "In Progress" and an af...

Now I'm curious as well - which document did the quote come from?

I have seen this issue and been hurt by it several times. You need to clock on the column twice before hitting the delete button, otherwise the first column in the list is selected. This is a nasty front-end glitch.