Types of Data Retained

Objects in RunMyJobs generate data which is saved on the central server. Depending on the process type, the output can also be saved on the Platform Agent for OS jobs or on the spool host, which is also a Platform Agent assigned to store data from ERP jobs. All of these objects must be taken into account for healthy housekeeping.

Execution Data

Each process generates output and log files for each execution. This includes, but is not always limited to:

• The RunMyJobs log file
• An entry in the RunMyJobs history
• A potential log from an automated application

To put this in context, here are some examples of frequency and number of executions over a period of time if you do not set retention.

Note: These are single executions. If you have a Chain with three processes, you must multiply this number by at least three. (A Chain is a process, as well as each of the Steps in the process, so a Chain of three Steps with one process in each Step generates seven processes in the Redwood repository.)

• A single process that runs every 5 minutes generates 288 daily, 2.016 weekly, about 8.640 monthly, and 105.120 yearly runs.
• A single process that runs every 15 minutes generates 96 daily, 672 weekly, about 2.880 monthly, and 35.040 yearly runs.
• A single process that runs 8 times a day during business hours generates 8 daily, 56 weekly, about 240 monthly, and 2.920 yearly runs.
• A single process that runs weekly generates 1 weekly, 4-5 monthly, and 52 yearly runs.

Looking at the more frequent processes the size of log (output of the script or application) will add up in the actual size of the total data, it shows the importance of thinking about retention. For example, keeping just the last five completed runs is enough for a process that runs every five minutes.

Static Data

In addition to execution data, there is static data to archive, including Events, Operator Messages, Audits, and logging information. For more information, see Purging Static Data.