DSXchange

Pretty sure Ken has done something similar, maybe not for a telco but from a large volume standpoint.

samuel81 wrote:but it doesn not work and am getting an error

Any error in particular?

You tried with what 'following script'?

What about all the pdf documentation that installs with the Client?

Thanks for that. Implication being that everything has been rolling back. Sheesh. No clue why my original (long gone) developer would have done that...

Strange question but wondering if anyone knows for sure. I found a job with a single statement in the 'After SQL' tab for one link: ROLLBACK; Can anyone confirm for me whether the After SQL runs after the main SQL transaction has been committed or is this actually rolling back everything this link h...

So... "ADS" is "Ascential DataStage" I assume? There is no longer an "Ascential" here, it's "IBM Websphere DataStage". And were you forced to ask this question strictly regarding the Server product as you've marked the post or is the Enterprise Edition / PX a valid option as well? I'd wager anyone h...

You can ignore any errors generated by the 'Reset' process. What you are looking for is a 'From previous run...' log message, it is where any 'additional information' will be.

As do I. Server has no such automatic option. You would, instead, need to code something equivalent 'after sql' or in some manner of separate step.

Thanks for posting that Flash... err, Tom.

Of course, that the actual group number (108) can be different, it is the group name that would be the important part of all this.

In other words, a scripted call to sqlplus with the script launched by the Execute Command stage. Make no assumptions about the runtime environment and ensure it works outside of DataStage first, then add it to your Sequence. Also make sure errors are properly reported back from your proc to sqlplus...

Can you tell me how you have identified error for the STATE code? Is there any manual shows for this error this is the reason? The error codes have been posted here in the past and can be found in the $DSHOME/include/dsapi.h file, from what I recall. Mostly, it's just something you learn, either fi...

Well, at least now it's trying to run the job. What 'state' is it in now? The error tells you the job is not runnable - that can mean it is not compiled or is aborted and needs to be reset first or it may already be running.

You need to figure that one out.

Not DSHOME - $DSHOME

That's all it should take as everything should be set in your dsenv file.

Try this - after doing the previous steps, try running your job like this:


And let us know what happens.