Author Topic: Writing CMoD data to tape rather than DASD  (Read 1756 times)

XCS6335

  • Guest
Writing CMoD data to tape rather than DASD
« on: February 03, 2016, 02:39:37 PM »
Our initial environment was set up to load reports to DB2 LOB tables.   There was no planned migration to Tape (we don’t have Optical).   This is quickly becoming unmanageable and we want to change our loads to go directly to Virtual Tape.  Obviously, ACS code must be added/changed to send new reports to Tape and to transition existing reports to Tape from DB2 LOB storage, but my concern is about what changes may need to be made on the CMOD Admin side of the house, if any, to make sure that the changes on the Storage side are actually coordinated with the CMOD Admin setup of the Report Groups, etc. to achieve the desired result.

That said,

What is the best practice for writing Report Objects directly to Virtual Tape?  What are the caveats?  We have the CMOD Best Practices Document from March 2015, but it mostly addresses setup and config on the CMOD Admin side and OAM related info is mostly cut and pasted from the OAM PISA of Objects.

CMOD is responsible for all expiration of data.   No ACS/SMS management is involved other than the addition of transition to Tape in our proposed environment.  What do we need to check on the CMOD Admin side to make sure setup environments are not in conflict and will produce the required results?   For example,  if CMOD Report Groups were set up without migration to Tape in mind and only expiration at End of Life, what options do we have to accomplish our goal of moving Reports to Tape?