DSXchange

And while the tool is free the patch is one million dollars.

arun_im4u wrote:Resolved.

Excellent. Then please mark the post the same by using the big button at the top of the page.

Does it have to be a job? You can do this in SQL... and I'd suggest you save the unique records in a new table and then rename (if possible) rather than all of those deletes if the number to save is smaller than the number to get rid of.

Me again. :wink: Thought it might be worth mentioning that while the category can be just that in the versions prior to 8 it needs to be fully qualified for 8. So for a category called 'Fred' you'd need to specify it as follows: 7.x: Fred 8.x: \Jobs\Fred And I'm pretty sure this code will only work ...

That... works ok? Seems to me that the auto purge read is too late being after the 'clear' and that you'd need to read it first, then clear and then lastly write it back out, but perhaps I'm missing something. :? Or does this work because it is version 8? I vaguely recall something about a fundament...

I believe that was introduced in the 8.1 release, which is why you can't find it. A search here for "istool" should confirm or deny that.

Right, you have to check the job's environment not your command line environment even if they are 'the same user'. You'll see they are (or can be) different.

And if your exports are in mulitple files, you could script something to iterate through them and do a series of individual imports automagically. Or you could just cat them together and do one import.

In other words, a hashed file.

As who said, you done what? Switched to using $PROJDEF?

For the record, that job is part of the "Utility" suite of jobs supplied with the "KBA Job Control Utilities" and have been around for... well, forever. I know you said you used a Parallel job and I don't know if that really makes any difference but I've always had them as Server...

You can't reset a job 'after job' as it actually hasn't finished yet. Why do you think you need to do this? Your job control should reset before running, not after. IMHO.

That just builds a single column of output, if you want a comma delimited list you need to try using the 'm' option from what I recall.

What 7.x version? Earlier ones required a recompile in that situation but later ones fixed that issue.

Search here for METASTAGE_LOC_INFO and see if any of the previous conversations help.