clearing log files at one shot

major · Post by **major** » Tue Oct 21, 2008 7:14 am

Hi,

I have read somewhere that clear.&ph& command would clear all log files of a particular project at one shot, if executed at command line at datastage admin .

I tried in vain.Any suggestions about that command would be helpful

DS_SUPPORT · Post by **DS_SUPPORT** » Tue Oct 21, 2008 7:22 am

CLEAR.&PH& wont clear the log files, as you are thinking.

For clearing the log file , you need to execute the command

Code: Select all

CLEAR.FILE RT_LOGXXX

where XXX is the job number. you can get the job number by querying DS_JOBS. but if you just execute this , it will clear your auto purge settings also.

For clearing the Job log, with preserving Auto Purge Settings, Our DS Masters have posted the routines already, Do a search in the forum.

chulett · Post by **chulett** » Tue Oct 21, 2008 7:24 am

"CLEAR.FILE &PH&" simply clears that "phantom" directory in the attached project. There is no command to "clear all log files in one shot".

kduke · Post by **kduke** » Tue Oct 21, 2008 12:53 pm

There was one on the ADN. It would take a while and each each job's log file. It might be on my tips page. If not then I could post it.

JeroenDmt · Post by **JeroenDmt** » Thu Jan 08, 2009 4:30 am

kduke wrote:There was one on the ADN. It would take a while and each each job's log file. It might be on my tips page. If not then I could post it.

Could you post it? I've been searching in dsxchange and found several references to the ADN one, but haven't been able to find any solution to clear all the log files in a project.
I don't see it on your tips page.

chulett · Post by **chulett** » Thu Jan 08, 2009 8:44 am

viewtopic.php?t=82586

JeroenDmt · Post by **JeroenDmt** » Thu Jan 08, 2009 9:27 am

Thanks!

chulett · Post by **chulett** » Thu Jan 08, 2009 10:00 am

Be aware of what it is doing - getting a list of job numbers and issuing a CLEAR.FILE for each one in a loop, which means you'll lose all of your auto purge information. However, there is another Ken Bland utility out there to set them all as well. Not 'preserve' but set.

JeroenDmt · Post by **JeroenDmt** » Thu Jan 08, 2009 10:42 am

Do you accidentally know where to find that one?

chulett · Post by **chulett** » Thu Jan 08, 2009 10:47 am

Accidentally? As a matter of fact...

viewtopic.php?t=106690

:D

JeroenDmt · Post by **JeroenDmt** » Thu Jan 08, 2009 12:48 pm

Great! Thanks :D

sbass1 · Post by **sbass1** » Thu Jul 23, 2009 1:19 am

(May as well just add to this thread rather than starting a new one)

So I read this thread, and also
viewtopic.php?t=82586, and
viewtopic.php?t=106690

See also
viewtopic.php?t=128396&highlight=

Plagiarizing from viewtopic.php?t=82586 above, I've written this simple routine:

Code: Select all

TCL = "CLEAR.FILE RT_LOG" : pJobNumber
Call DSExecute("TCL", TCL, ScreenOutput, SystemReturnCode) 
Ans = ScreenOutput : @VM : SystemReturnCode

Using the same approach as in viewtopic.php?t=128396&highlight= to loop over the jobs in the project, I can clear the desired logs in the project. Further enhancements are parsing the Ans text to write to the log or sequential file, etc.

However, I read this also deletes auto purge settings, etc.

Is there a better way, or is this best practice to, as the subject says, "clear logs files in one shot"?

Thanks,
Scott

ArndW · Post by **ArndW** » Thu Jul 23, 2009 1:27 am

I just spent weeks writing a program which manages log files - you can choose whether by date, or runs or number of log entries and it cleans up broken multi-instance and job run data plus it reorganizes remaining data and performs other housekeeping. Entries removed are archived to an Oracle database. All this work because this site doesn't want to lose log entries. The CLEAR.FILE approach works quite well and is fast and efficient. If you wanted to be clean, you could read or copy the //PURGE.SETTINGS record prior to clearing the file and then writing it back to the new and pristine log file. The other control records in the log file, "//SEQUENCE.NO" and "//JOB.STARTED.NO" don't need to be kept if all of the log entries that they refer to are cleared.

ray.wurlod · Post by **ray.wurlod** » Thu Jul 23, 2009 4:51 pm

Scott wrote:Is there a better way, or is this best practice to, as the subject says, "clear logs files in one shot"?

Use the auto-purge settings. Maybe with tighter rules than you currently have in place. That's what I'd regard as best practice.

sbass1 · Post by **sbass1** » Thu Jul 23, 2009 5:33 pm

ray.wurlod wrote:
Scott wrote:Is there a better way, or is this best practice to, as the subject says, "clear logs files in one shot"?
Use the auto-purge settings. Maybe with tighter rules than you currently have in place. That's what I'd regard as best practice.

Thanks Ray. I'm currently just using this utility in our DEV environment, where job creation is very dynamic, and the large logs (usually due to thousands of warnings) make reading the logs slow.

I'll ensure we set proper auto-purge settings for our PRD environment.