1
z/OS Server / How to trouble shoot CMOD OAM reports when they do not transition from OAM DASD
« on: June 26, 2020, 08:30:32 AM »
I am having a challenge with CMOD and OAM. We have a large number of reports in OAM DASD. But most of them should have transitioned to OAM TAPE
We have worked on the ACS Code with IBM L2 SMS. We have tried to set up reports to see if they actually transition.
I am looking for an easy way to diagnose the ACS routines to see how the transition process works
We thought when we set up CMOD with OAM the process was working. Instead, some of the OAM Objects just keep growing on DASD and consuming everything they can.
I also need a refresher on the process used that tells OAM that the report should go to TAPE.
Our ACS routines are not complex. but I think sometimes the logic flow in SMS for CMOD/OAM can get confusing for me
Thanks
Lizette
We have worked on the ACS Code with IBM L2 SMS. We have tried to set up reports to see if they actually transition.
I am looking for an easy way to diagnose the ACS routines to see how the transition process works
We thought when we set up CMOD with OAM the process was working. Instead, some of the OAM Objects just keep growing on DASD and consuming everything they can.
I also need a refresher on the process used that tells OAM that the report should go to TAPE.
Our ACS routines are not complex. but I think sometimes the logic flow in SMS for CMOD/OAM can get confusing for me
Thanks
Lizette