Delays between Job Sequences / Calling Next Job

bmouton · Post by **bmouton** » Fri Apr 10, 2009 12:39 pm

Actually, sometimes the obvious bites you on the butt!!!

After spending countless hours and not sleeping for three days, I took a wild stab and change the prune setting on the log files to 1 day. Then, I cleaned the log files ...

Started my cycles ... Run Times for my environments went from 30 - 40 minutes to under 2 minutes for the small databases ... 7 minutes for the larger one ....

Additionally, the log file process was causing collisions in DB2 preventing our BI interface to work ....

Amazing how the simple things get you!!

Thanks for all of your input!

chulett · Post by **chulett** » Fri Apr 10, 2009 2:24 pm

Interesting... which 8.x version are you running? Specifically, is this 8.1 where the job logs are in the XMETA repository or are they still hashed files in the project? Known issue, if the former, and there's a way to force them back to the "Universe" layer.

bmouton · Post by **bmouton** » Fri Apr 10, 2009 3:10 pm

They are still HASH files ... I believe we are on 8.1 for SUSE

ray.wurlod · Post by **ray.wurlod** » Sat Apr 11, 2009 4:02 pm

In version 8.1 you get the choice of where the logs are. It's my understanding that the default is to put them in the unified metadata repository (that is, the XMETA database if you didn't select a different name).

chulett · Post by **chulett** » Sat Apr 11, 2009 4:42 pm

Exactly, and why I asked. The issue and the setting changes you'd need to make (or at least check) are documented here:

viewtopic.php?t=125607

ray.wurlod · Post by **ray.wurlod** » Sat Apr 11, 2009 9:02 pm

bmouton wrote:They are still HASH files

No they're not. They are HASHED files.

A hash file is a tool used for shaping a block of hash. Whether that means ground meat or something else to you is immaterial.