Author Topic: .AOD Files Left Behind on MSG 88 Load Failure  (Read 1508 times)

JJeffrey

  • Guest
.AOD Files Left Behind on MSG 88 Load Failure
« on: August 22, 2017, 07:08:39 AM »
We're running (currently) CMOD V9.0.0.7 on RHEL5. When we experience a load failure for a document there is an .AOD file left behind in the working storage filesystem (arsacif/acif1). If I delete the .AOD file because the input was bad and replaced, ARSLOAD (running as daemon) stops on the next set of documents set to load.
 
1. Does anyone know what these leftover files are?
2. Why would deleting them from working storage cause ARSLOAD to stop?

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2230
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: .AOD Files Left Behind on MSG 88 Load Failure
« Reply #1 on: August 24, 2017, 09:02:39 AM »
You should be able to change your ARSTMP parameter in ars.cfg to put those temporary files into a different filesystem where they won't clutter up your working directories.  You'll have to restart IBM CMOD for the change to take effect.  Then you could empty that directory of it's contents when you run your IBM CMOD startup scripts, or when your server is rebooted.

-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