Author Topic: Automated Directory Maintenance  (Read 2114 times)

dstrong

  • Newbie
  • *
  • Posts: 8
    • View Profile
Automated Directory Maintenance
« on: August 19, 2013, 07:02:35 AM »
Hi all,

We're currently in the process of moving from OnDemand v8.0.4 on z/OS to v9 on AIX. I was wondering if anyone had any suggestions on best practices or scripts for keeping the processed and error directories cleaned up. We are using the ARSJESD process to upload reports from the mainframe to the server, and the ARSLOAD process gets triggered from there. It's been about a month now with just a few reports so far, and I can see the log files getting out of hand quick.

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2231
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Automated Directory Maintenance
« Reply #1 on: August 19, 2013, 07:19:23 AM »
arsload shouldn't leave log files behind.  Maybe you have an intermittent script that produces them.  If you have files left over after the fact, you might want to remove the '-n' option from arsload if you're using it.

Otherwise, the way a lot of my customers handle this sort of thing is to create a script that removes files one they reach a certain age, and schedule it to be run via cron.  You can also add the step of compressing the files (compress/gzip/bzip2) after they're processed in order to keep the space requirements to a minimum.

If you can give us some more information about what types of files, or what commands you're running, we might be able to suggest more solutions.

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR