Job Multiple Instance Fail

Mike · Post by **Mike** » Tue Mar 10, 2009 2:22 pm

It seems to me that you understand how multi-instance is supposed to work.

It still sounds more like the auto-purge bug to me. When you tested with auto-purge turned off, did you turn it off at the individual job level? Turning it off at the project level has no effect on pre-existing jobs.

Mike

marcelo_almeida · Post by **marcelo_almeida** » Wed Mar 11, 2009 6:31 am

Mike,

I turned off the level of project in Administrator.
How can I do it a level of job?
When I open the Director, the box "Auto-purge" is always unchecked.

Thanks

Mike · Post by **Mike** » Wed Mar 11, 2009 5:11 pm

The job inherits its auto-purge settings from the project when the job is created. The property appears to remain unchecked when auto-purge was inherited from the project. Quick way to see if auto-purge is actually happening... go to the director log for the base entry of your multi-instance job (the one without an invocation id). Look for log entries containing auto-purge. For example: "Project-level auto-purge, XX log entries removed". Should be about the last log entry.

Mike

chulett · Post by **chulett** » Wed Mar 11, 2009 6:34 pm

Mike wrote:The property appears to remain unchecked when auto-purge was inherited from the project.

That's... not really true unless this is changed behaviour in the 8.x version. What I've seen pre-8 is auto-purge always checked when it is on, regardless of how that was set - manually or via inheritance. Unchecked is off. Nothing in-between.

If one's auto-purge settings are "always off" at the job level, to me that implies that that is the default at the project level. As noted, the project level default only applies to newly created / imported jobs, on-the-fly changes to it do not affect existing jobs.

Mike · Post by **Mike** » Thu Mar 12, 2009 5:37 am

New behavior in 8.0.1... just noticed it when I went to check it in my own jobs. I have jobs that auto-purge and have that property unchecked at the job level.

Since it appears to be off, I'm not sure how you would actually turn it off at the job level in 8x... maybe check it and change... then uncheck it again?

Mike

Mike · Post by **Mike** » Thu Mar 12, 2009 8:37 am

That's not the only new behavior. Out of curiosity, I played around with some settings...

Changes in auto-purge settings at the project level now apply to pre-existing jobs.

To disable auto-purge at the job level: disable it at the project level.

It looks like it really can't be disabled at the job-level when it is enabled at the project level. You can enable it at the job level and spin up to 99 job runs or 99 days, but that's about it... The reverse is no problem... it can be disabled at the project-level and enabled at the job-level.

I don't have any multi-instance or auto-purge patches in my installation, so I have no idea if this new behavior is working as designed.

Mike

chulett · Post by **chulett** » Thu Mar 12, 2009 10:40 am

Sheesh... will have to keep that in mind, it seems, when people post 8.x questions on this topic.

marcelo_almeida · Post by **marcelo_almeida** » Thu Mar 19, 2009 7:43 am

The support of IBM suggested a workaround that worked perfectly.

Follow the link:
http://www-01.ibm.com/support/docview.w ... -8&lang=en

Thank you everyone for your help!

chulett · Post by **chulett** » Thu Mar 19, 2009 7:51 am

Ah... this has been discussed here before. So, I assume you enabled the RTLogging option, yes? Did you also end up running the mentioned script to create the auto-purge task?

marcelo_almeida · Post by **marcelo_almeida** » Thu Mar 19, 2009 8:22 pm

No, I just modify the following 2 lines in the DSParams file:

RTLogging=1
ORLogging=0