Clearing job logs in director for multiple instance of a job

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
snt_ds
Premium Member
Premium Member
Posts: 280
Joined: Wed Oct 18, 2006 11:53 am
Location: Pune, India

Clearing job logs in director for multiple instance of a job

Post by snt_ds »

All,

I am using a unique id(for ex: batch_id)as a invocation id for my master sequence.

Every time I run the job sequence for multiple times in a day, it is creating the multiple job logs(in status view-DS DIrector) with batch id as invocation id.
For ex: My sequence name is 'ABC' and it is checked with option 'allow multiple instance' and I am passing batch_id as the invocation id.

so if I run this sequence 20 times a day,it is creating logs and showing the logs in status view for 20 instances.

abc.1001
abc.1002
......
.....
....
abc.1020

Requirement is to cleanup the logs for all above instances from director's status view.
I hope Autopurge will not work in status view.

Can some one help me to solve this?

Thanks
snt_ds
Pagadrai
Participant
Posts: 111
Joined: Fri Dec 31, 2004 1:16 am
Location: Chennai

Re: Clearing job logs in director for multiple instance of a

Post by Pagadrai »

'Autopurge' will clear up the log files as you expected.
But what I understand is that you want to remove the job status list.

You can try doing a 'job reset' command at the beginning of a sequence
execution.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

There's still only one log for the job but the Director will create multiple 'views' into it, one for each invocation id. If you look at the log for the main job, you'll see all of the log messages for all invocations there, jumbled together.

There are a number of posts here on how to remove those invocations from the Director's status view, as you've found simply purging the logs isn't the answer. Off the top of my head, a recompile of the job will clear them and I believe a 'Reset Status File' will do so as well. There may be another, but I don't recall it at the moment, a search should turn up other discussions on this topic.
-craig

"You can never have too many knives" -- Logan Nine Fingers
dsuser_cai
Premium Member
Premium Member
Posts: 151
Joined: Fri Feb 13, 2009 4:19 pm

Post by dsuser_cai »

just compile the main job that will take care.
Thanks
Karthick
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Already noted.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply