DSXchange

Search the forum for URL/filepath for other conversations on this issue.

Make it work. Load it into a work table in your database so you can do this - a pretty common technique, actually.

Search the forums for "project currently locked", you'll see it has been discussed a number of times. Got nothing to do with a project being 'protected', btw.

No, not a 'bug' per se, more of a limitation of the GUI. This has been debated here in the past, some people will happily do what you did and others won't. In any case, it does work - at least up through through the 7.5.x version, but can't say if it will keep on working in future versions.

Any 'calculation' in particular or do we get to figure that out?

Forgot to post the resolution. I asked one of our webservice wiz boys about combining the two wsdls, which he did for me and which could then be imported successfully.

And, last but not certainly least, used successfully as well. :D

That would happen if you failed to mark a Key field as a Key.

nick.bond wrote:It has been working fine for a very long time and suddenly as we are performing the real migration it is falling over when trying to call some jobs.

Could you explain that for us, please?

Looked promising. It shows 'PDF Bookshelf' links for all major products, including Orchestrate. However, each link either takes me to the same generic eSupport page or says the linked page does not exist.

Could be a client error rather than anything with the job itself. Can others open it just fine and this error is yours alone? If so, try re-installing your client software.

Is there a question here somewhere?

Why not put all of your parameter values in a flat file, read that and call the SP once for each record? Or better yet, dump the whole 'stored procedure' thing and build a job that loads your temp table.

I would think you would need to get a list of job names from the desired category and script a looping structure to compile them one by one. I don't believe there is any 'automatic' way to do it.

No, this should not in any way be related to your ODBC config changes. People delete files, that or things like wayward scripts. We've also seen reports here on Windows servers where anti-virus programs removed critical DataStage files, but that's obviously not the issue here. Are filesystem backups...

Yes, it has been seen before and discussed here. However, never did get an answer as to what it means and why it went away (for me) as quickly as it appeared...

http://www.dsxchange.com/viewtopic.php? ... status+141