Job Log

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
yiminghu
Participant
Posts: 91
Joined: Fri Nov 14, 2003 10:09 am

Job Log

Post by yiminghu »

Hi,

I have twp dummy questions about job Log. How do you automatically clear the log every time you run a job? How do you increase the limits so you can see more entries in the log?

Thanks,

Carolo
Marley777
Premium Member
Premium Member
Posts: 316
Joined: Tue Jan 27, 2004 3:26 pm

Post by Marley777 »

For Project wide auto purge
1) Bring up the DatatStage Administrator Window (if you have access)
2) Click Properties
3) On the General page select the (auto-purge of job log) check box
4) select the auto purge action you wish to take

or

for setting auto purge for a specific job
1) Bring up Datastage Managaer Window
2) Click on job
3) Click on (clear Log option) to bring up the Clear Log dialog box
4) Select the (auto Purge Option)
5) Select the (enable for this job) option
6) select auto purge action you wish to take

You can increase job log entries in this same manor as mentioned above. Just select different actions where needed, but it's all in the same place. Hope this helps.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Keep in mind the fact that when you set and/or change the 'Project Wide' auto purge defaults via the Administrator it only applies to new jobs created after the change.

For existing jobs, you'll need to make the change in the job itself as already noted.

You may also have a filter on the number of log entries shown if you can't see all of them. When viewing the Log of any job, go to 'View/Filter Entries' and check to see if any limits have been established there.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The hot key for invoking the Filter dialog is Ctrl-T
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
nsm
Premium Member
Premium Member
Posts: 139
Joined: Mon Feb 09, 2004 8:58 am

Post by nsm »

Hi,

Can I clear log after each run from unix?

nsm.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Yes, but why would you want to?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
nsm
Premium Member
Premium Member
Posts: 139
Joined: Mon Feb 09, 2004 8:58 am

Post by nsm »

I am using dsjob lognewest command to find out if I have any errors or warnings in the last run.

For ex:
I ran a job for 3 times, first time I have errors , second and third time it ran fine.

then if i do the log newest entry on that job for errors its still giving me NON_ZERO value .

To make sure its giving from 1st run, i cleared the log for first and second runs then i did the same command then its giving me ZERO value.

to avoid all this i wanted to clear the log after each successful run.

nsm.
Last edited by nsm on Mon Feb 16, 2004 9:36 am, edited 1 time in total.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You can set this up with auto-purge.

In director, choose the Job menu, then Clear Log.

Instead of choosing immediate purge, choose to enable auto-purge. This opens the auto-purge options frame, in which you can set "clear up to last run". Director will ask you to confirm that you want to override the project defaults that were set in Administrator. You do.

Auto purge does not occur unless a job run was successful.

You don't need to check the log to determine whether there were any warnings. The exit status of the job itself will tell you this. Its possible values from a normal run are 1 (ran OK), 2 (ran with warnings) or 3 (aborted). You can get this by specifying the -jobstatus option when running the job, or subsequently by using the -jobinfo option.
It's the first line in the output from

Code: Select all

dsjob -jobinfo project jobname
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Teej
Participant
Posts: 677
Joined: Fri Aug 08, 2003 9:26 am
Location: USA

Post by Teej »

The way we do it:

Set auto-purge on the project level to the last 10 run.

Set it as Director | View Menu | Filter Entries (You need to be looking at a job's log before you do this) | Start of Last Run.

That way, you automatically purge after 10 runs, yet only watch the most current job's run.

This way would be VERY helpful for developers when something fails, but they have to re-run the job for other reasons.

Also, the Limits are within the same window -- "Select all entries".

And young man, FIX YOUR WARNING MESSAGES! For Server jobs, it is incredibly rare to have a 'valid' warning message.

-T.J.
Developer of DataStage Parallel Engine (Orchestrate).
Post Reply