DSXchange

Welcome aboard! :D

As you can guess, this isn't the first time a question of this nature has been asked. A quick search of the forum turned up this post, and if that doesn't answer things for you there are others waiting to be found.

Ok. What happens after the job aborts and you reset (not recompile) the job? Is there any kind of message in the log that says 'From previous run...'? If so, that can give more clues as to what is going on.

Is your target database on the same server as DataStage? I'm pretty sure that is a requirement for the 'Automatic' option.

Do it on a smaller job first. It's a general setting, not a job specific setting.

There is a SYSTEM call you need to make to accomplish that. Check out this post from Ray for the details.

Actually, there is a patch. The document you mentioned has been available for awhile, while the patch is fairly new.

As I said, check the Software Updates / Downloads section of the eServices site after you log in. It's called dsclient_xpsp2.zip.

Just coincidence or is this the same issue as posted in this thread?

Wow. Very strange. I've been using Version Control since you had to pay for the darn thing, since the 4.0 days at multiple sites and I've never seen this particular issue. Any of the issues mentioned, actually. I'd be very curious of the outcome as well. The only thing that I wonder about is the use...

Welcome, wandering Samurai. This boils down to what you mean by 'call'. I don't believe that this is possible from inside job control or via 'normal' means. Perhaps a search might turn up more answers or others will step in to help. You could do something from the command line via 'dsjob', if that w...

As Ray implies, the complexity of the job shouldn't be the cause of the problem... at least not directly.

Do you know how to access DS.TOOLS? If you are ok on the permissions Ray mentions, I'd go there and rebuild the repository indexes to see if that fixes the problem.

First off, forgive me if some of this is bass-akwards, it's all from memory... Do you want a timestamp that is consistant across the entire run of the job or one that changes second by second in 'real time'? There are functions and system variables that can get the information for you, it's up to yo...

Well, that's a bummer. That was the only SP2-related patch that I was aware of. Have either of you reported it to Ascential support? Is it yet-another-known-issue with SP2?

There is a patch available for the problem from what I understand. Haven't had a need to go hunt it down myself, however. Check Ascential's eServices site or perhaps ADN.

Edit: just double-checked and the client patch *is* available as a downloadable Software Update on the eServices website.

No problem. It's not like I've ever done that or anything...

Are you sure the parameter is defined as a string everywhere it is used? That error should only happen when the parameter type is set to a Date.