The number of logs for a mult-instantiated parallel job
Moderators: chulett, rschirm, roy
The number of logs for a mult-instantiated parallel job
Hello,
I have a multi-instantiated parallel job that is executed repeatedly in many sequence jobs. The problem I have is that I seem to be able to retain the logs for the latest 6 executions. That is, if there are 10 sequence jobs, each calling the multi-instantiated job once, I expect to see 10 logs, one for each invocation id. Yet I see only the latest 6.
Is there a limit that needs to be set? If so, how?
Thanks
I have a multi-instantiated parallel job that is executed repeatedly in many sequence jobs. The problem I have is that I seem to be able to retain the logs for the latest 6 executions. That is, if there are 10 sequence jobs, each calling the multi-instantiated job once, I expect to see 10 logs, one for each invocation id. Yet I see only the latest 6.
Is there a limit that needs to be set? If so, how?
Thanks
Yes, each as a different invocation id.
As suggested, I plan to view log for the multi-instantiated job, check auto-purge and "auto purge enabled for this job" and select 25 for "Up to previous (job runs)", as it requires a number from 1 thru 25.
I assume this is what the suggestion implied.
I will report back with my results in the next 1 hour.
Thanks
As suggested, I plan to view log for the multi-instantiated job, check auto-purge and "auto purge enabled for this job" and select 25 for "Up to previous (job runs)", as it requires a number from 1 thru 25.
I assume this is what the suggestion implied.
I will report back with my results in the next 1 hour.
Thanks
Craig - Yes. I should have explained it. There is a sporadic issue with enabled auto-purge at 8.x which causes jobs to abort. We have 4 multiinstance jobs, each running with several instances and the jobs start once a minute or so and sometimes nothing (bad) happens for a day or two, but once issues start they don't disappear until the logs are either cleared or purge is turned off.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
In order to disable auto-purge, I selected "view log", then Job====>clear log. I checked "Auto-purge" and unchecked "Auto purge enabled for this job".
However, after saving, I return to clear log, and I see "Immediate purge" still checked.
I can do the same, without going to view log. Just highlight the job and select clear log from the job tab. When I return to clear log, I find "Immediate purge" still checked.
What could I be doing wrong?
Thanks
However, after saving, I return to clear log, and I see "Immediate purge" still checked.
I can do the same, without going to view log. Just highlight the job and select clear log from the job tab. When I return to clear log, I find "Immediate purge" still checked.
What could I be doing wrong?
Thanks
Hello,
That solution did not work. What was curious though, was that on some occassions, as I went about disabling auto-auto purge, it would return with an error message "Unable to return an attached job, Cannot open file RT_LOG". I assume it is due to the log being locked at that point in time, though I am not sure, as at other times it has saved the settings with no such error message.
Anyhow, the results are negative.
That solution did not work. What was curious though, was that on some occassions, as I went about disabling auto-auto purge, it would return with an error message "Unable to return an attached job, Cannot open file RT_LOG". I assume it is due to the log being locked at that point in time, though I am not sure, as at other times it has saved the settings with no such error message.
Anyhow, the results are negative.
Did not work in what sense? What exact problem are you trying to solve again? Your RT_LOG issue sounds more like a corruption issue with the log hashed files themselves. I would suggest exporting and reimporting any job that does that to fix things of that nature.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Sorry that I didn't quite explain myself.
In disabling the auto-purge, I occassionally got RT LOG error I mentioned. On attempting to do so again, it would apply the change without giving any errors.
Once it did not give any errors, I assumed the auto-purge had been disabled. Then I ran the sequence jobs that call the multi-instantiated job, expecting to see all 10 (or more) logs, one per invocation id.
When I said that the results were negative, I meant that I did not see as many logs as the invocation id's.
Thanks
In disabling the auto-purge, I occassionally got RT LOG error I mentioned. On attempting to do so again, it would apply the change without giving any errors.
Once it did not give any errors, I assumed the auto-purge had been disabled. Then I ran the sequence jobs that call the multi-instantiated job, expecting to see all 10 (or more) logs, one per invocation id.
When I said that the results were negative, I meant that I did not see as many logs as the invocation id's.
Thanks