DSXchange

kumar_s wrote:Arnd - May I know what is the intention of RESIZE DS_JOBS * * * Will it give out the integrity of the indecies. It seems it requires an Exclusive access to DS_JOBS, so I could not test it now.

Kumar

REINDEX requires exclusive access as well otherwise the indexes get deleted and not rebuilt.

Have a (url=http://dsxchange.com/viewtopic.php?t=100006&highlight=dsjobs+dsjobobjects&sid=651bb606acba5eba6916a5bd82f8e8da)look(/url) at this discussion regarding the renaming job. Kumar - you cannot post links from your search results, they won't work for anyone else. See how it has a '&am...

Here is the original post. http://www.dsxchange.com/viewtopic.php?t=93365

Congratulations, I think you got there faster than anyone else.

Originally I downloaded DSJobReport from ADN as an example of how to use a filter command. It failed on a regular basis. Abort hard with goofy error messages like this. It was hard to debug. I figured out a lot of limitations of XML from trying to make this job stable. I changed this filter stage in...

No, absolutely not. I think daily exporting all the jobs is important in a busy development environment. Weekly is good enough for exporting production projects. You cannot reindex all files without exclusive access. Nor is there a need for reindexing or CLEAN.ACCOUNT unless something unusual shows ...

Besides in DS7.0 it had lots of bugs. You need 7.5 or above before it worked well. You need to upgrade.

CLEAN.ACCOUNT will clean the VOC. It can be dangerous if you delete some of the file pointers that DataStage needs. This is another TCL command.

Even if you could do a find then you would still have problems with multiple instance jobs.

If you had EtlStats working then it would be easy to select from ETL_JOB_HIST.

Do not think this is easy. Arnd has been using Universe for many years. This is something he has a great deal of knowledge about.

katz wrote:Thanks for you replies.
I was thinking that there is perhaps a better method to abort the job, which I was unaware of.

katz

Not really.

I would guess it is ACLs. What are the user groups? Make sure and do id at the AIX level to see what is the default group. Make sure the default group is the same as dsadm. I am not sure on AIX if you can force all files in a directory to owned by the same group with chmod -R g+s ProjectDir Permissi...

It could also be your source select. It can only update as fast as it is being read.

What is Netezza?

DSLogFatal will log a message before it fails the job. I think it would be cleaner.