How to delete documents from OAM on ZOS v1r11 CMOD 8.4.0.3?

[plb3945]

I need information please about deleting documents from OAM when the life of data and indexes is finish.
ARSEXOAM must have a database table which created at the install of the product (not installed in our CMOD)
ARSEXPIR must use the storage manager parameter in AG (all our AG have load parameter selected)
How can we proceed to delete our expired documents from OAM? We have a lot of K7 !!
We can't create database for ARSEXOAM, it's too late.
And it's impossible to change the parameter from "load" to "storage manager" to use ARSEXPIR !!
I can't find the correct parameter for ARSMAINT in "Administration Guide Zos Cmod Version 8.4.pdf", is it possible with ARSMAINT?
Thanks for your help.
Best regards
Philippe

[ewirtz]

Hi Philippe,

if you configure a retention period in the application group, you can delete everything with arsmaint. Using this you should configure OAM in a way, that it never expires.

please loook for http://www.odusergroup.org/forums/index.php?topic=739.0. The deletion logic ist true as well for using simple retention manager (if you ignore the hold logic)


Regards

Egon

[plb3945]

Hi Ewirtz,

Thanks for your reply, I have an another question about OAM. What should we configure in OAM to delete with ARSMAINT -d ?
Thanks for your help.
Best regards
Philippe

[ewirtz]

Hi Philippe,

I think yo should congifure OAM as 'never expire'. This makes things easy. Only retention manager is involved in retention management.

Regards

Egon

[PasiPK]

Hi Philippe,
here is some information, if SMS managed deletion is planned.

- OAM manages objects according to SMS management class definitions,
  which also includes information about when to delete
- OAM "management cycle"   OSMC is run daily,
  it will check which objects need to be deleted and deletes them
- however OAM is usually installed so, that IBM delivered user exit CBRHADUX
  does not allow deletions
- if you want to let OSMC delete objects, CBRHADUX needs to be modified
  (this is precaution by IBM, so that objects do not get deleted easily)
- when object deletion is done by OSMC, there is DB2 trigger in object directory
  which writes info about the deleted objet to DB2 table ARSOAM_DELETE
- Ondemand ARSEXOAM reads ARSOAM_DELETE and deletes index data from OnDemand
- ARSEXOAM can be scheduled to run after after OSMC

It should not be a problem, if table ARSOAM_DELETE and triggers etc. are creeated later than basic OnDemand installation.

Regards,  Pasi