DSXchange

My problem just went away.
I can now compile the jobs, I do not know why this happened.

Thanks to everyone who helped me.

I also cannot compile a job without a transformer. It behaves the same just an hourglass and then it goes away.

The job does not throw any error and the status in the director does not change. I will try to do some more checking and post the results.

I can run a job which is compiled with the same credentials. I will check on the dumps and the xml

Thanks

Nothing that I know of.

I am not able to compile any jobs. When I try the hourglass come up and then after a few seconds goes away.

Force compile is also the same.

I was able to compile jobs a few days ago

Any help or suggestions will be appreciated

Joseph

Are you using any null functions on a previously defined and calculated stage variable?

Could someone please let me know how this property is set. I could not find any place to set the link properties. I have checked the output tab of the upsteam stage (in my case a transformer)

Thanks

The default execution mode of the ODBC stage is sequential and this cannot be changed.

So the open command will be executed only once

The only optiion now in my opinion is to run these jobs individually. However if you had selected the "Add checkpoints so sequence is restartable on failure" in the job properties, you could have restarted the sequence job and only the jobs that did not run in the previous attempt would run

We have a job which uses Netezza for input and output, with a Transformer in between. This job runs fine in the Development environment but fails in the Production environment with the error : ERROR from ExecDirect: Error occured while
writing into file
Any help will be appreciated

Greg, Thanks for the suggestion. It works when you enter a space. Still the question remains why does it compile without the space on one PC and requires a space on another PC.

Could it be a setting on the Client side of datastage?

Hi, I have a job with an SCD stage which we are using to capture Type 1 changes. As we are not interested in generating keys, there is no surrogate key state file and the source name in the Surrogate key tab is blank. This job compiles fine on some PC's but on some other PC's it gives an error "...

I don't have access rights on my current machine to check if this is reproduceable since it sounds too strange. Are the numeric contents that come across as NULL all of a similar tpye, i.e. with leading zeroes or negative values? Do values such as "123" not get transferred correctly? Ther...

I don't have access rights on my current machine to check if this is reproduceable since it sounds too strange. Are the numeric contents that come across as NULL all of a similar tpye, i.e. with leading zeroes or negative values? Do values such as "123" not get transferred correctly? Ther...

That sounds really strange. If you select all cells and remove formatting in the document, does the error persist? Removing the formatting OR removing the formatting and reformatting as text does not help. The only way for this to show up as I have found is to have the numeric value prefixed with a...