Job Multiple Instance Fail
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 46
- Joined: Wed Jun 28, 2006 9:54 am
- Location: BrasÃlia - Brazil
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
Mike
Mike wrote:The property appears to remain unchecked when auto-purge was inherited from the project.
![Confused :?](./images/smilies/icon_confused.gif)
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.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
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
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
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
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
-
- Premium Member
- Posts: 46
- Joined: Wed Jun 28, 2006 9:54 am
- Location: BrasÃlia - Brazil
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!
Follow the link:
http://www-01.ibm.com/support/docview.w ... -8&lang=en
Thank you everyone for your help!
-
- Premium Member
- Posts: 46
- Joined: Wed Jun 28, 2006 9:54 am
- Location: BrasÃlia - Brazil