Moving old data from production tables to historic tables in another library

In an active production system such as we have being in a 24 hour service financial environment, we have an issue with old data that exists in many of our database tables. Every second new data is being recorded in this tables and old the old data that exists is no longer being used but keeps acumulating and increases the size of the table impacting in our backups such as the time that takes creating a backup of all of the tables with unnecesary data, the time of restoration if we need to restore one of this files, and of course the logical file that keeps growing in this tables, which we cannot execute a RGZPFM because

many of these files are constantly being used. To resolve this, we need a CL to helps us with the logic of moving old data to secondary offline tables, and being System Administrators we dont have the knowledge to create the CL that adjust with our requirements.

My idea, in short, is that we need that IBM provides us (System administrators) with a tool to create scheduled jobs to automatically moving old data to secondary offline tables that could exist in another library with SQL sentences and therefore eliminating the migrated data from the original tables so we don't have to depend of creating a CL from scratch for this maintenance process, and more important we dont have to depend of our development team or assign a budget to hire a third party developer to helps us with this.

As I already mentioned, being in a financial enviroment, there's hundred of requirements that our development team are assigned to, and the top priority is the financial core applications for our end customers, creating a CL that we need for what I already explained, is not a top priority when you consider the business impact, there's always new requirements that have more priority.