Avoid Multiple Instances of Jobs in Director Log.

Aquilis · Post by **Aquilis** » Mon Dec 31, 2007 12:28 pm

Hi all,
I have Multiple Instance JobControl Code which Executes again 4 Multiple Instances Jobs.I can't guess how many multiple instances of job control can be invoked at a time,It may vary from 10 to 20 Instances at a time.So which will inturn invoke more number of multi instance jobs involved in it.
So all these instances are clearly viewable in Director log.Assuming if i have nearly triggering 30 instances all jobs,then all these are clearly viewed from Director log,which i dont want to happen.I know if compile my base jobs then all the instances will get deleted.But i cant go ahead with it,since my jobcontrol is triggered continously 24*7 from MQ message pulling job.Continuously my MQ plugin will pullout the messages and triggers the jobcontrol.So in this case my instances will keep on increasing.
So i cant guess when should i compile my base jobs,i cant predict the Time Lag.

So, is there any way so that i can revoke the viewable picture of creation of instances in the Director Log. Can i do like just showing the Base Jobs other than all the instances log viewable.
You suggestions will really help me out in this regard.

Thank you all,

ArndW · Post by **ArndW** » Mon Dec 31, 2007 12:34 pm

I can think of 2 things:
a) filtering Director entries
b) Automatic purging - this will remove the instance name when the log is purged.

ray.wurlod · Post by **ray.wurlod** » Mon Dec 31, 2007 3:03 pm

I agree. Other than filtering by job name (for example not matching *.*)there is no means in Director to achieve what you appear to be asking. But what is it you really want? If all runs supply an invocation ID the "base job" will contain no entries. Also, you won't be aware that the log table for the multi-instance job may be growing and growing - auto-purge does not occur unless the job finishes normally (no errors).

shawn_ramsey · Post by **shawn_ramsey** » Mon Dec 31, 2007 3:17 pm

ArndW wrote:I can think of 2 things:
a) filtering Director entries
b) Automatic purging - this will remove the instance name when the log is purged. ...

Unfortunately automatic purging only clears logs and will not remove the invocation information.

ArndW · Post by **ArndW** » Tue Jan 01, 2008 6:08 am

Shawn - I remember now, I had to write a short DS/BASIC program that goes into the log and cleanses "orphaned" information. I think that might be fixed at V8 and can check that next week. I might also have the code on my PC which cleans up the log and can post it here.

Aquilis · Post by **Aquilis** » Tue Jan 01, 2008 8:17 am

Except the Base Jobs,all other instances of these jobs should not list in the Director Log.That's what my question is ?.
Is there any option in DS to Hide all executing and executed instances of jobs from director list.

chulett · Post by **chulett** » Tue Jan 01, 2008 8:35 am

From the Status view in the Director, Control-T or View/Filter Entries will show you all of the available options to filter the display of jobs there.

shawn_ramsey · Post by **shawn_ramsey** » Wed Jan 02, 2008 4:53 pm

ArndW wrote:Shawn - I remember now, I had to write a short DS/BASIC program that goes into the log and cleanses "orphaned" information. I think that might be fixed at V8 and can check that next week. I might also have the code on my PC which cleans up the log and can post it here.

Good news is that runtime information is still stored in Universe in V8 so the old work around will still work around. :D

JoshGeorge · Post by **JoshGeorge** » Wed Jan 02, 2008 5:15 pm

If "Hide all executing and executed instances of jobs from director list" is what you want then I think as noted by Ray and Craig filtering by job name will be your only option.

Aquilis wrote:Except the Base Jobs,all other instances of these jobs should not list in the Director Log.That's what my question is ?.
Is there any option in DS to Hide all executing and executed instances of jobs from director list.