Use the following procedures to help you clean up your IBM i system for each of the Robot products you have installed. Deleting history files and other records regularly can help your system run more efficiently.

Deleting Product History

After Installing, Updating, or Converting a Robot Product

The Deployment Manager process creates two libraries on the system: HSLOADMGR and HSLOADMGRW. Once you are done installing, updating, or converting a Robot product using HSLOADMGR/HSWRKLOAD, you can delete theses libraries.

If you are working with an older version of a Robot product that uses the LODRUN process there will be several libraries that remain on your system. You can delete the following libraries from your system after you have finished all of your product installs, updates, or conversions: RBTCDRLIB, HSSAVF, and HSBOOT.

Robot Alert

Robot Alert contains message history and transmission log history that need to be cleaned up on a regular basis. To display the History Menu, select option 5 from the Robot Alert Administration Menu. To delete Robot Alert history, select option 4 on the History Menu. You can choose to delete message history and/or history kept in the Transmission Log. Specify if you want to delete the history immediately (option 1), or schedule the deletion using Robot Schedule (option 2). If you leave the date and time parameters blank, all history is deleted, including any pending messages.

You can also schedule history cleanup using Robot Schedule. See "Deleting Robot Alert History Automatically" for complete information on using a reserved command variable to retain the last 7 days of history.

Robot Autotune

Robot Autotune can save three types of statistics: pool, job, and interactive job. All statistics are controlled by the parameter: Number of days to retain statistics. Select option 3 on the Auto Tune Menu to display the Control Values Menu. Then, select option 1 to display the Control Values. Specify the number of days that statistics objects should remain in the library, ATLIB, before Robot Autotune automatically deletes them. Robot Autotune deletes statistics automatically at midnight of the last day specified by the Number of days to retain statistics field.

Robot Browser Interface

There is no history or other cleanup required to maintain the Robot Browser Interface.

Robot Client

Robot Client keeps track of your completed tasks on the IBM i. To remove this history, select option 2 to display the Control Menu. Select option 4 to display the command prompt panel for the RCLCLEANUP command. The RCLCLEANUP command deletes completed tasks. You can specify the number of days of completed tasks you want to keep. If you have Robot Schedule, you can schedule a job to purge completed tasks regularly.

On the PC client, you can use the Robot Client Event Viewer to see events that occurred on the client and diagnose problems in your client procedures. You must open the Event Viewer to initiate the automatic cleanup. To open the Event Viewer, go to Start Menu\Programs\Help Systems\Robot Client\ Robot Client Event Viewer. Click the GoTo menu and select Configurations Options. On the Configuration Options dialog box, check the values specified for the following parameters: Maximum records to display per log and Retention period for all logs.

Robot CPA

The PURGESTATS function deletes statistical records, both detail and summary, according to the values you selected in the Statistical Setup panel (it also deletes one-time charges). The purge/delete of history records is determined by where you define the PURGESTATS function in your CPA procedures (Maintain CPA Procedures).

Robot Console

Robot Console writes a history record for every message it processes and for any log monitoring it's performing. Depending on the message traffic on your system, the message history files can become very large. After you print the message history reports you need, you should delete the old message history records. We recommend keeping a minimum of 7 days of message history and running the delete message history command daily.

Delete Message History lets you delete message history records that fall within a specified age or severity range. You can use this command to delete outdated message records on a regular basis to save disk space, and reduce storage and processing overhead.


The Delete Message History command can be run in batch by scheduling it in a Robot Schedule job or using the IBM command SBMJOB.

Robot Corral

There are no records or history to purge in Robot Corral.

Easy View

Do the following to clean up Easy View records:

  1. Clean up stored DDS. If you selected to store DDS (specified Y in the Save Retrieved DDS in EZVIEW Database on the Profile Tailoring panel), Easy View stores the DDS of every file it displays. It continues to store the DDS even if the file is deleted.


    The CLNDDS command removes the DDS for files that no longer exist. You can submit the CLNDDS command from Easy View by selecting option 8, EZVIEW Setup and Initialization, from the EZVIEW menu, and then option 2, Clear out all EZVIEW Data Description Files, from the Easy View Setup menu.

  2. Purge the Easy View audit log.


    Use the PRGAUDIT command to purge audit information that is no longer needed. Or, select option 8 from the Easy View menu, and then option 5, Purge Audit File, from the Easy View Setup menu.

  3. Clear Easy View work files.


    The CLREZVIEW command lets you clear all or part of the Easy View work files: *DDSONLY clears only the stored DDS; *ALL clears everything, including user options, and resets Easy View to its shipped state. You can submit the CLREZVIEW command from Easy View by selecting option 8 from the Easy View menu and option 4, Clear EZVIEW Library (DDS or user settings) from the Easy View Setup menu.

Robot LPAR

Statistics are purged at the collection of the first statistics after midnight of the last retention day. You can specify any value between 1 day and 365 days, inclusive. The default is 10 days. Specify the Number of Days to Retain Statistics on the Robot LPAR Configuration dialog box.

Robot Monitor

You should delete statistics regularly to free disk space. To delete performance statistics stored on the node system, select option 3, Delete Statistics, from the Statistics Menu. You can choose to delete statistics immediately, or schedule a Robot Schedule job to delete the statistics.

Robot Network

Robot Network produces a history record for each event status that occurs. After you are sure that a status history record is no longer needed, you can delete the record.

You can delete the status history records either in the green screen or from the Robot Network Explorer. Note: Only status records that have been acknowledged are deleted.

Follow these instructions:

Green screen - Use the RBTNETLIB/RBNDLTSTS command to delete the records. You can purge status history by product and node.

Robot Network Explorer - Right-click the record and select Delete.


If messages are being acknowledged in the Status Center, you won't need to manually run the RBNDLTSTS command. Status messages will be deleted based on the value specified in Host Properties.

If status messages aren't being acknowledged, you'll need to run RBTNETLIB/RBNACK prior to running the RBNDLTSTS command in order to remove messages.

If Robot Network is used to send packets, you can purge packet history from the host using command RBTNETLIB/RBNPURGE.

Robot Replay

There are no records or history to clean up in Robot Replay.

Robot Reports

Robot Reports contains archive history, processing history, and access history.

Purging processing and access history

From the Robot Reports Main Menu, select option 3, Report History Menu. Select option 4, Delete Report Processing and Access History. This displays the command prompt panel for the Clear the History Records REPCLRHIST command. The Only Remove Access Records field allows you to specify the type of records to purge: enter Y to purge access records only; enter N to purge both access and processing records. Then, specify how old (in days) records must be to be purged.

You also can display the command prompt panel by entering the RBTREPLIB/REPCLRHIST command on a command line and pressing F4.

Once you've decided on a purging scheme, the easiest way to keep your files clean is to schedule a Robot Schedule job to run the REPCLRHIST command regularly. We recommend that you run the REPCLRHIST command monthly to delete report processing and access history records over 30 days old.

Deleting archive history

The REPCLRHIST command does not affect report archive history.

The REPARCHIVE command checks archive dates based on the number of days a report should remain in each archive stage, as specified on the Report Set panel. It then moves reports to their next archive stage when it is appropriate.

From the Robot Reports Main Menu, select option 4, Control Menu. Select option 5, Move Reports to Next Archive Stage. When the REPARCHIVE command prompt panel displays, enter an option to specify the types of reports that Robot Reports will examine.

You also can display the command prompt panel by enter the RBTREPLIB/REPARCHIVE command on a command line and press F4 to display the prompt panel.

You can select from the following options:

BOTH Move reports from online to short-term and from short-term to long-term storage.
SHORTTERM Move reports from online to short-term storage.
LONGTERM Move reports to long-term storage.
EXPIRED Move all reports that are past their retention days.

The REPARCHIVE command also triggers a job named REPDLTMON that cleans up the old objects on your system.

RBTREPLIB and REPSHTRMLB hold archive history. During the initial setup of Robot Reports, it is common to see these libraries grow. Once new report sets are not being added, the size should stabilize.

We recommend you run the REPARCHIVE command on the following schedule:






Notes: If you will be running the REPCLRHIST and REPARCHIVE commands within the same job, run REPCLRHIST first, then run REPARCHIVE.

Robot Save

Robot Save purges most history (object and library archive) automatically when a volume expires and moves to the scratch pool. However, the following history records should be cleaned up manually, as well.

  1. Object archive history. This history is purged automatically when a volume expires and is released to the scratch pool. Make sure the class is set up to automatically release expired tapes to the scratch pool. Manually removing a volume from the Volume Inquiry panel using option 9 also moves the volume to the scratch pool and purges any archive history.
  2. Delete save status message history. Save Status messages tell you when a backup set was executed and whether or not it was successful. Robot Save creates Save Status message records whenever a backup set save executes. In addition to displaying save status messages, the Operations Menu also provides options to print or delete messages for a given time range or type of message. From the Main Menu, select option 1, Operations Menu. Then, select option 4, Delete Save Status Messages.
  3. Delete Move history. Because each move of each media volume creates a record, you should purge the move history regularly. From the Robot Save Main Menu, select option 2, Save Media Management Menu. Then, select option 10, Purge Move History.
  4. Remove old libraries from Robot SAVE. From the Robot Save Main Menu, select option 5, Automated Backup Setup Menu. Then, select option 5, Library Maintenance. Use option 6 to delete the library and all its history from Robot Save.

Robot Schedule

Unused Jobs

Robot Schedule has an Unused Jobs report that shows jobs that have not been run since a particular date. It uses the job history to determine which jobs meet the criteria. This report can help you find jobs that are candidates for removal.

Cleaning up history

Robot Schedule's Job Completion History gives you instant information on all batch jobs currently running or completed. You can track all jobs, including those not submitted by Robot Schedule.

To have Robot Schedule clean up history automatically, select option 4 on the Robot Main Menu to display the System Setup Menu. Select option 1 to display the General System Defaults panel. Enter a value in the Number of runs to retain for Job History.

Robot Schedule can purge runs beyond this number automatically if you enter a Y in the next field (Do you want Robot to automatically delete Job History). When using automatic cleanup, Robot Schedule tracks the number of C and T completion codes for the number of runs to track. For example, if there are 50 W statuses, the W statuses are not cleaned up until it has exceeded the number of runs for C or T statuses.

For certain jobs, you might want to retain a greater number of runs than defined in the System Defaults. You also can define the number of runs of history to be maintained at the individual job level. The value specified at the job level overrides the System Defaults value. Select option 5 on the job from the Job Schedule List (JSL) to display the Control Options panel. Enter a value in the Number of runs to track for Job History field.

Another way you can delete completion history in Robot Schedule is to create a Robot Schedule job to delete job completion messages automatically. To delete messages, have the job call program RBT655. If you do not pass a parameter string on the program call, the program deletes all messages. To limit the messages deleted by completion code and/or date range, you must pass the completion code as a parameter value in position 1. Only the C and T completion codes are used for the date range and number of runs to track.

Code Deletes
Blank All codes
C Normal completion
E Error on setup
R Running
S Submitted to batch
T Abnormal termination
W Warning message
K Skipped
D Delayed
P Pending

Specify the date range, as follows:

  • Beginning date: Six digits in system date format (or 000000 for no beginning date).
  • Ending date: Six digits in system date format (or 000000 for no ending date).

Assuming the system date format is mmddyy, the following command deletes all messages dated before November 1, 2014:

CALL PGM(RBT655) PARM(' 000000110114')

Robot Space

Use the History Purge window to submit or schedule the deletion of short and long-term collection statistics, threshold history records, and storage audit history records. Select Setup, then History Purge.

  1. Purge Collection Statistics. This purge deletes short-term and long-term statistics based on the retention settings set up for each collection group.
  2. Purge Threshold History. This purge process deletes threshold history created by storage collections and the ASP and job monitor jobs. We recommend you keep the last 60 to 90 days of history.
  3. Purge Storage Audit History. This purge deletes history records created by storage audits.

Robot Trapper

See Robot Console. Purging Robot Console history removes messages from the Robot Trapper message queue.

Robot Transform

Robot Transform maintains conversion history for spooled files, IFS files, and on-demand conversions. Use the Setup option to define the Robot Transform system and conversion defaults. Right-click on System Setup and select Properties to display the System Setup window. Use the Standard Setup tab for history purge options. Specify the number of days to keep history records of the converted files. Any history records older than the number of days you specify are deleted from Robot Transform. Click Submit to run the purge job immediately. Click Schedule to set up a Robot Schedule job to purge the history.

Use the Purge History (TRNPURGE) command to purge Robot Transform history records from your system. You can specify the number of days of history to retain. You should schedule the TRNPURGE command to run on a regular basis to remove unneeded history records.

Robot UPS

Robot UPS keeps a history record of UPS activity on your IBM i. You can delete a single history record, or all or part of the Robot UPS history for your system.

From the Robot UPS Main Menu, select option 2 to display the Control Menu. Next, select option 5 to Delete Robot UPS History and then enter in a date and time range to be removed.

Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case