You can use your automation product to clear / manage log files. You can schedule it to be cleared during shutdown or at any time that you desire.
You call this a log file but it is just a file. Contact the vendor of this daemon for recommendations on maintaining their log files because there is not a utility specifically for this purpose unless they built one. If none exists, then you need to write something to extract the last 30 days of data. As for clearing the file, it's a simple process. UNIX files are not locked even though it is allocated. You should be able to remove or rename the file. Then use TOUCH to create the file and chmod/chown/chgrp to set the files attributes. FYI, the file will be created automatically if it tries to write before you do the TOUCH and touch won't harm the file if it already has data. As for leaving 30 days of data, why not just rename the file once a week or daily and delete the ones you no longer want. Jon Perryman On Thursday, July 3, 2014 10:37 AM, Fred Kaptein <[email protected]> wrote: \tmp\daemon.log.b > >This file has grown very large over time, as it is not being cleared out on a >regular basis. >What commands can we issue during a shutdown of our z/OS system that would do >the following: > - clear all but the previous 30 days data > - clear all data > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
