Use this document as a guide to set up and manage Robot Replay with your mirroring application. Throughout this document, the source system refers to the base system where Robot Replay is installed; the target system refers to the mirrored high availability (HA) system where the second copy of Robot Replay is installed.

Note: The source and target systems must be at the same release/modification level.

Installing Robot Replay on Your Systems

Use the following information to make sure your systems are set up properly.

New Installs

If Robot Replay is currently not installed on the source or target system, you must install Robot Replay on both the source and target systems.

Currently Running Robot Replay on the Source System

If Robot Replay is currently installed on the source system, we recommend that you follow the instructions for moving Robot Replay to another system. For details, see "Moving Robot Replay to Another System."

Replicating Robot Replay Objects

The tables below are for customers who are planning for HA applications. These tables define the Robot Replay objects and specify which objects you must replicate to run Robot Replay with HA software.

Table 1 below lists the types of objects that you should mirror.

Table 1: Object Specifier for High Availability - Objects that Should Be Mirrored

Object NameObject TypeObject Attributes

Table 2 below lists specific objects that you should exclude from mirroring. These objects may be the same type as the objects shown in Table 1, but they should be defined as exceptions and excluded from mirroring.

Table 2: Object Specifier for High Availability - Objects to Exclude from Mirroring

Object NameObject TypeObject Attributes
No*RPY999*USRSPCSee note below

*  The user space, RPY999, can be replicated if your release/modification level is R03M20 or higher, and you are using the multiple-entry license screens.

Mirroring Robot Replay

The following prerequisites are necessary to mirror Robot Replay from the source system to the target system. For details, see "Moving Robot Replay to Another System."

  • Robot Schedule must be installed and configured on the target system with the jobs that are necessary to process your Replay objects.

  • The following items must be identical on both the source and target systems in order for Robot Replay to work correctly:

    Note: Be sure to check the operational attributes and workstation entries on your subsystem descriptions.

    • The IBM i OS levels.

    • The PTF cume levels.

    • All user profiles that Robot Replay uses.

    • Authorities for all of the system objects being used in your Robot Replay objects.

    • The descriptions of the devices Robot Replay uses.

    • The device types that Robot Replay uses (or the system value QAUTOCFG must be set to ON).


    • All system objects, such as subsystem and job descriptions, must exist with identical attributes.

    • Any third-party software that Robot Replay executes must be installed and configured identically.

Additional Information


The Robot System Library, RBTSYSLIB, is a general purpose library that contains common modules for the Robot Automated Operations Solution. You do not have to replicate this library; however, the library must be updated when the source or target system is updated with new modifications. RBTSYSLIB is updated automatically during conversions, upgrades, and new installations. There is no dynamic data stored in this library.

User Profiles

The RBTADMIN and RBTUSER profiles are created automatically on all systems when you install Robot Replay. DO NOT modify or replicate them.

High Availability and Other Robot Products

For information about running other Robot products in a HA environment, see "Mirroring the Robot Products."

Licensing Fortra Products

All Fortra products must be licensed on each system before using them in a HA environment. Discuss product licensing with your Regional Sales Manager.

Updating or Converting Robot Replay

When you update or convert Robot Replay on the source system, you also must make the same changes on the target system. We recommend that you end the mirroring product, perform the update or conversion on the source system, update or convert the target system, then restart the mirroring process. Different mirroring software products may have options to synchronize the libraries, or to send all changed objects to the source system. To make sure that all the necessary added or updated objects are on the target system, we recommend that you follow the normal update or conversion process on both systems.


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