Moving Robot Reports to Another System

 

These instructions describe how to move Robot Reports from its current system (the source system) to another IBM i system (the target system).

Before You Begin

• If you’re using Robot Alert or Robot Client to email reports, you must have these products installed and configured on the target system.

• If you are using a report processing type of ROBOT on the source system, Robot Schedule must be installed and configured on the target system with the correct jobs needed to process reports.

• You will need to back up and restore some libraries on the two systems. However, the only time you must back up and restore the RBTSYSLIB library is if there are no Fortra products currently installed on the target system (see steps 1 and 3 under On the Source System, and step 1 under On the Target System).

On the Source System

1. Verify that there are no object locks on your critical libraries by entering the following command:

   WRKOBJLCK OBJ(libraryname) OBJTYPE(*LIB)

   where: libraryname is RBTREPLIB, REPSHTRMLB, REPMRGLIB (if you have Robot Network installed), RBNREPMST (if you have Robot Network installed), and RBTSYSLIB (if you have no Fortra products installed on the target system).

2. End Robot Reports by performing the following steps:

   • From the Robot Reports Main Menu, select option 4, Control Menu.

   • From the Control Menu, select option 2, End Output Queue Monitoring.

   • In the RBTSLEEPER subsystem, check whether the Robot Reports job, REPDLTMON, is running. If it is running, end it.

3. Back up some or all of the following libraries based on your software configuration, as described below:

   Library	Description
   RBTREPLIB, REPSHTRMLB	Back up these libraries for Robot Reports.
   REPMRGLIB, RBNREPMST	Back up these libraries if you have Robot Network installed.
   RBTSYSLIB	Back up this library only if there are no Fortra products installed on the target system.

On the Target System

1. Perform the following tasks based on your target system configuration.

   If...	Then...
   Robot Reports is installed on the target system	Verify that there are no product locks on your Robot Reports libraries by using the following command: WRKOBJLCK OBJ(libraryname) OBJTYP(*LIB) where: libraryname is RBTREPLIB or REPSHTRMLB Back up and then delete the RBTREPLIB and REPSHTRMLB libraries on the target system.
   The RBTUSER and RBTADMIN user profiles are not on the target system	Make sure that the user profiles RBTADMIN and RBTUSER are valid user profiles on the target system or partition. If they do not exist on the IBM i, run the following to create the user profiles: RSTOBJ (RSL062) SAVLIB(RBTSYSLIB) DEV(*SAVF) SAVF(savflib/RBTSYSLIB) RSTLIB(QGPL) CALL PGM(QGPL/RSLO62) DLTOBJ OBJ(QGPL/RSL062) TYPE(*PGM)
   Robot Network is installed on the target system	Verify that there are no product locks on your Robot Network libraries by using the following command: WRKOBJLCK OBJ(libraryname) OBJTYP(*LIB) where: libraryname is RBNREPMST or REPMRGLIB Back up and then delete the RBNREPMST and REPMRGLIB libraries on the target system.
   The RBTSYSLIB library is not on the target system Important: Perform these steps only if there are no Fortra products installed on the target system.	Restore the RBTSYSLIB library from the source system. Add the RBTSYSLIB library to the top of your system library list by editing the QSYSLIBL system value. Enter the following command: WRKSYSVAL QSYSLIBL Select option 2 to change the system value. Make RBTSYSLIB the first library in the system library list. Sign off and back on the system to make the new system value active.

2. Restore the following libraries from the source system:

   • RBTREPLIB

   • REPSHTRMLB

   • RBNREPMST (if you use Robot Network)

   • REPMRGLIB (if you use Robot Network)

3. Verify that the following libraries, user profiles, and so forth exist on the target system and match the ones from the source system:

   • Robot Reports user profiles

   • Output queues that Robot Reports monitors and distributes reports to

   • Archiving—verify that your storage options are correct.

   • From the Robot Reports Main Menu select option 6, System Setup Menu. From the System Setup Menu, select option 1, System Defaults, and verify that your short term and long term storage options are set correctly.

   • Robot Alert email options

   • Any folders to which Robot Reports distributes Portable Document Format (pdf), client (txt), or spreadsheet (cvs, xls) files.

   • Any compare data values specified in a report set must be valid on the new system.

After You Are Done

If the name of the target system is different than the name of the source system, run the following command on the target system to update Robot Reports files with the new target system name:

RSLCHGSYSN BEFORE(sourcesystem) AFTER(targetsystem) PRODUCT(REPORTS)

where: sourcesystem is the name of the original system; targetsystem is the name of the destination system.

New License Code

You must enter a new license code on the target IBM i system to make Robot Reports active.

1. Contact your Fortra Regional Sales Manager to obtain your new license code.

2. On the target IBM i system, enter the following commands:

   ADDLIBLE RBTREPLIB

   CALL REP280

3. When the Robot Reports License Setup panel displays, enter your new license code and press Enter.