DSXchange

Use a "Wait For File Activity" to wait 1 second for the file to appear, then have a link output for "success" and for "failure" and branch your sequence logic accordingly.

Sudheer,

could you explain the problem a bit more. You said you have a comma delimiter and that is working. What is the format of the rows that are different? Do the rows have the value "..." for just one column?

There are at least two basic approaches. One way is to use a UNIX command one liner to get the filelist and cat all the results to stdin for the DataStage PX job. Another is to work through a DataStage Sequence and get the directory contents and call up your processing job once for each input file. ...

I had something similar happen with my workstation and it turned out that the automatic software update package had kicked in overnight and installed some package which had messed up my libraries on my PC. Please post your answers once you get them sorted out so that others can benefit from your pai...

I thought so as well, but haven't had time to test this circular one to see if the compiler misses it. But it seems to be a logical explanation of the behaviour.

(There is no need to quote whole posts!!!) The problem is that you have a circular dependancy in your job. DataStage is looking at your job and a transformer2 is going to wait for the portion of the job that writes the Hash1 to complete before continuing. This is fine until at transformer3 that proc...

If you strip out everything except the ODBC -> HF from you job and save that as new one do you get the two different results (n.b. Don't just create a new job with this, but use the original as a template)? This might help in narrowing down the source of the error.

Usha, the problem is odd from your explanation; meaning that even though you have reinstalled DS on your workstation the error persists. Did you actually un-install your software and then re-install it or just overwrite the existing installation - if the latter then try a clean install by deleting t...

Do a job reset and look at the entry for "from previous run". This happens when a job aborts and cannot handle the exception/error itself.

A sequential file is just a long sequential list of bytes; the concept of "columns", "rows" and lines are no physical separations to the data just special characters that let programs interpret the ordering of the data. In your case you are sending the file using FTP as logical blocks of 1,000 chara...

A very common cause for this message is that you have runtime column propagation turned on and this column is being explicitly defined as well as being inherited from upstream. Do you have rcp turned on?

Ramesh, no matter what answer you get here, the only official one will come from your support provider - remember that there is a difference between "its working" and "its supported"

olgc - this is thread mismanagement; as it doesn't apply to this thread at all! Both will work in parallel jobs, but will return unique sequential numbers for their respective node. There are several recent threads on how to use these in parallel jobs.

ewartpm - a DataStage PX project includes all of the server functionality; so the answer to your question is Yes, you can import your existing server jobs into PX. But in order to use the full power of PX you will need to re-write those existing server jobs, and the development time for converting a...

Do you have the LENGTH and the DISPLAY set to 2700 in your stage definitions? If you have display set to your maximum data length you shouldn't see the warning, I just tried it at 7.5