Overview

Use this document to help you define a consistent strategy for backing up the products of the Robot Automated Operations Solution.

Benefits of Backing Up Your Robot Products

Using these procedures to back up your Robot products can benefit you in multiple ways.

  • Reduces down time for the Robot products.
  • Speeds up the process through the use of save while active processing.
  • Simplifies use because you can enter these procedures directly into the Robot Save backup set panels.

Backup Assumptions

  • You must end the product being backed up before executing the save command.
  • The save-while-active feature will be used to capture any active files.
  • You still need to review your backups for locked objects. Save-while-active is not always a guarantee that all objects are backed up.
  • Save to a Save file will be used instead of saving directly to tape. This prevents the backup from waiting for a tape mount that could occur if you write directly to tape.
  • Try to avoid having to end all the products for a backup. If you plan to back up all Robot products, you can use the RBTSLEEPER shutdown command RSLSHUTDWN to end all products running in the RBTSLEEPER subsystem, and then end the subsystem.
  • SAVLIB LIB(*NONSYS) will back up all of the Robot products. This may be your best choice.
  • All the Robot products except for Robot Autotune need RBTSYSLIB backed up.

Note: A number of the commands shown in this document are too long to fit on one line. However, this document is set up so that if you copy the entire command, it will paste correctly on one line.

Additional Considerations

If you do a SAVLIB LIB(*NONSYS) once a month, that may be the only backup of the Robot products that you need. Many customers treat these products like the operating system. Once installed and operating on a daily basis, the products do not change that much. The exception is the report data for Robot Reports, and that is backed up as you archive to long-term storage. The short-term and online data are backed up only by following the procedures described in the Robot Reports section below.

 

Robot Alert

Follow these steps to back up Robot Alert:

  1. Enter the following command to end the paging monitoring job:

    RBTALRLIB/RBAEND

  2. Enter the following command to prevent Robot Alert from starting if someone sends a page:

    RBTALRLIB/RBALOCK ACTION(*LOCK)

  3. Enter the following command to delay the job:

    DLYJOB 180

  4. Enter the following command to save the Robot Alert library:

    SAVLIB LIB(RBTALRLIB) DEV(*SAVF) SAVF(QGPL/RBTALRLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  5. Enter the following command to start the pager monitoring job:

    RBTALRLIB/RBALOCK ACTION(*UNLOCK) RBTALRLIB/RBASTR

  6. Enter the following command to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTALRLIB) DEV(TAP01)

Robot Alert Backup Tips

  • The device/controller/line definition objects actually are stored in the QSYS library. These objects are backed up by your SAVSYS or SAVCFG operations.
  • The Robot Alert library is saved to a save file so that no tape mounts are required during the backup. Remember, Robot Alert is not able to send a pager or email message during the backup to alert you to mount a tape.

 

Robot Autotune

Follow these steps to back up Robot Autotune:

  1. End Robot Autotune using either of the following two commands:

    ATLIB/CNLAT or ATLIB/ENDAT

    These commands end the ATMONITOR subsystem and all jobs running in the subsystem.

    Note: If you're using dynamic pools, you must wait for the jobs in the dynamic pools to end before continuing.

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. Enter the following command to back up the Robot Autotune library:

    SAVLIB LIB(ATLIB) DEV(*SAVF) SAVF(QGPL/ATLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  4. Start Robot Autotune using the following command:

    ATLIB/STRAT

  5. Enter the following command to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/ATLIB) DEV(TAP01)

Robot Autotune Backup Tips

  • Many customers use Robot Autotune to control system performance during save operations. If you're using dynamic pools and enter the CNLAT command, you should allow time for any jobs running in dynamic pools to finish. You cannot get a complete backup of ATLIB if jobs still are running in the ATMONITOR subsystem.
  • Performing a RSTLIB of a Robot Autotune backup, either at a hot site or a recovery site, will probably result in problems. Because a hot site will have a different memory pool configuration and total main storage than your system, you should perform a new install of Robot Autotune at the hot site.
  • The Performance Factors and Control Values report contains detailed information on your Robot Autotune setup. This is your best tool for recovery. Keep a copy of the report along with your installation CD (or DVD) in off-site storage as a record of your setup values. Select option 6 from the Auto Tune Reporting Menu to print a copy of the report.

 

Robot Client

Follow these steps to back up Robot Client:

  1. End the monitoring job using the following command:

    RBTRCLLIB/RCLENDMON

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. Enter the following command to back up the Robot Client library:

    SAVLIB LIB(RBTRCLLIB) DEV(*SAVF) SAVF(QGPL/RBTRCLLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  4. Start the monitor job:

    RBTRCLLIB/RCLSTRMON

  5. Enter the following command to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTRCLLIB) DEV(TAP01)

Robot Client Backup Tips

If individual PCs are still running Robot Client, executing the RCLENDMON command does not unlock the data queue for each client. These data queues exist in the library RBTRCLLIB. You do not need to be concerned about these data queues. The PC job will recreate the data queue if it does not exist.

This process does not back up the Robot Client PC software. You don't have to worry about this. We recommend that you just register the PC again to Robot Client if you lose a disk on a PC. Keep a copy of the software in a shared folder or on a file server.

 

Robot Console

Follow these steps to back up Robot Console:

  1. Shut down Robot Console by entering the following command:

    RBTCONLIB/RBCENDCON

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. Save the library RBTCONLIB to a save file:

    SAVLIB LIB(RBTCONLIB) DEV(*SAVF) SAVF(QGPL/RBTCONLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  4. Save the RBCMRGLIB to a save file: SAVLIB

    LIB(RBCMRGLIB) DEV(*SAVF) SAVF(QGPL/RBCMRGLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

    Note: This is optional. You only need to back up RBCMRGLIB if you are using the import/export feature of Robot Console.

  5. Restart Robot Console by executing the following command:

    RBTCONLIB/RBCSTRCON

  6. Back up the save file at a later time using the following two commands:

    SAVSAVFDTA SAVF(QGPL/RBTCONLIB) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/RBCMRGLIB) DEV(TAP01)

Robot Console Backup Tips

Message queue locks will still occur if interactive users are signed on while backups are running. This isn't a problem as long as the locked message queues have the following naming convention: RBCQ999999, where 999999 equals the IBM i job number that the user signed on with. These message queues are recreated every time the user executes the RBCSTRQ command in an interactive sign on.

 

Robot Corral

Follow these steps to back up Robot Corral:

  1. Enter the following command:

    SAVLIB LIB(RBTROLLIB) DEV(*SAVF) SAVF(QGPL/RBTROLLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  2. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/RBTROLLIB) DEV(TAP01)

Robot Corral Backup Tips

You must save the RBTROLLIB library if you perform object list backups (saving selected objects in libraries, documents, or IFS files).

 

Robot CPA

Follow these steps to back up Robot CPA:

  1. Enter the following command to back up the Robot CPA library:

    SAVLIB LIB(RBTCPALIB) DEV(*SAVF) SAVF(QGPL/RBTCPALIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  2. Enter the following command to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTCPALIB) DEV(TAP01)

Robot CPA Backup Tips

Robot CPA uses the IBM i job accounting facility, which is enabled by changing the system value QACGLVL to *JOB *PRINT. You then need to create a journal receiver, a journal, and add a message to the reply list. Enter the following commands:

  1. Create the journal receiver:

    CRTJRNRCV RBTCPALIB/JAJRNRA

  2. Create the journal:

    CRTJRN QSYS/QACGJRN

    and attach the RBTCPALIB/JAJRNRA journal receiver.

  3. Add a system reply list entry for the message ID CPA7025:

    ADDRPYLE MSGID(CPA7025)

You may need to do all, or only some, of these steps when recovering Robot CPA. You may find that the operating system information was not properly backed up or that your hot site does not have this information turned on.

 

Robot LPAR

Follow these steps to back up Robot LPAR:

  1. Enter the following command:

    SAVLIB LIB(RBTLPRLIB) DEV(*SAVF) SAVF(QGPL/RBTLPRLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  2. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/RBTLPRLIB) DEV(TAP01)

 

Robot Monitor

Follow these steps to back up Robot Monitor:

  1. Enter the following commands to end the monitoring jobs:

    RBTMTRLIB/ENDMTR

    RBTMTRLIB/ENDMTRG

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. Enter the following command to back up the Robot Monitor library:

    SAVLIB LIB(RBTMTRLIB) DEV(*SAVF) SAVF(QGPL/RBTMTRLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  4. Enter the following commands to start the monitor jobs:

    RBTMTRLIB/STRMTR

    RBTMTRLIB/STRMTRG

  5. Enter the following command to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTMTRLIB) DEV(TAP01)

 

Robot Network

Robot Network Host

Follow these steps to back up the Robot Network host system:

  1. Enter the following commands to end the network monitoring jobs:

    RBTNETLIB/RBNENDHOST

    RBTNETNODE/RBNENDNODE

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. Enter the following command to save the host library:

    SAVLIB LIB(RBTNETLIB) DEV(*SAVF) SAVF(QGPL/RBTNETLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  4. Enter the following command to save the node library:

    SAVLIB LIB(RBTNETNODE) DEV(*SAVF) SAVF(QGPL/RBTNETNODE) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  5. Enter the following command to back up the IFS objects:

    SAV DEV('/qsys.lib/qgpl.lib/networkifs.file') OBJ(('/Help Systems/Robot Network') ('/Help Systems/installs/NET'))

  6. You should also periodically save each Product Master library. These libraries contain history and product setup data.

    Enter the following to save the Robot SCHEDULE Product Master library:
    SAVLIB LIB(RBNRBTMST) DEV(*SAVF) SAVF(QGPL/RBNRBTMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

    Enter the following to save the Robot CONSOLE Product Master library:
    SAVLIB LIB(RBNRBCMST) DEV(*SAVF) SAVF(QGPL/RBNRBCMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

    Enter the following to save the Robot MONITOR Product Master library:
    SAVLIB LIB(RBNMTRMST) DEV(*SAVF) SAVF(QGPL/RBNMTRMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

    Enter the following to save the Robot REPORTS Product Master library:
    SAVLIB LIB(RBNREPMST) DEV(*SAVF) SAVF(QGPL/RBNREPMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  7. Enter the following commands to start the network node and host monitor jobs:

    RBTNETLIB/RBNSTRHOST

    RBTNETNODE/RBNSTRNODE

  8. Enter the following commands to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTNETLIB) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/RBTNETNODE) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/RBNRBTMST) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/RBNRBCMST) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/RBNMTRMST) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/RBNREPMST) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/NETWORKIFS) DEV(TAP01)

Robot Network Node

Follow these steps to back up each Robot Network node system:

  1. End the network monitoring job:

    RBTNETNODE/RBNENDNODE

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. Enter the following command to save the node library:

    SAVLIB LIB(RBTNETNODE) DEV(*SAVF) SAVF(QGPL/RBTNETNODE) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  4. Enter the following command to back up the IFS objects:

    SAV DEV('/qsys.lib/qgpl.lib/netnodifs.file') OBJ(('/Help Systems/Robot Network') ('/Help Systems/installs/NET'))

  5. Start the network node monitor job:

    RBTNETNODE/RBNSTRNODE

  6. Enter the following commands to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTNETNODE) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/NETNODIFS) DEV(TAP01)

Robot Network Backup Tips

  • You should back up RBTSYSLIB at the same time that you back up Robot Network to ensure compatibility upon restore of the operating system.
  • The Product Master libraries only need to be backed up if you're using them. Sometimes these libraries are never used by the Robot Network user, even though they're loaded during the Robot Network installation.

 

Robot Replay

Follow these steps to back up Robot Replay:

  1. Enter the following command:

    SAVLIB LIB(RBTRPYLIB) DEV(*SAVF) SAVF(RBTRPYLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  2. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/RBTRPYLIB) DEV(TAP01)

 

Robot Reports

Follow these steps to back up Robot Reports:

  1. End the output queue monitoring job:

    RBTREPLIB/REPENDQMON

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. If it is active, use the following command to end the job that deletes the reports (REPDLTMON):

    RBTREPLIB/REPSTPDLTQ

  4. Enter the following command to back up the user definitions for handling reports:

    SAVLIB LIB(RBTREPLIB) DEV(*SAVF) SAVF(QGPL/RBTREPLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  5. Enter the following command to back up any reports that have been archived to short-term storage:

    SAVLIB LIB(REPSHTRMLB) DEV(*SAVF) SAVF(QGPL/REPSHTRMLB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  6. Start the output queue monitoring job:

    RBTREPLIB/REPSTRQMON

  7. The REPDLTMON job will start the next time an archive is run or you can issue the following command to start REPDLTMON:

    RBTREPLIB/REPSTRDLTQ

  8. Enter the following commands to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTREPLIB) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/REPSHTRMLB) DEV(TAP01)

Robot Reports Backup Tips

  • The archive process should be run at least weekly. This purges old reports automatically and reduces the amount of backup data.
  • RBTREPLIB can exceed the maximum size for backup on the IBM i. This is an IBM limitation. Running the archive process and purging old history helps prevent your save job from running into this problem.
  • Do not define new reports while the backup is running. We do save-while-active to capture the data, but if a report is added after the save starts it will not be part of the backup.

 

Robot Save

Robot Save uses four libraries: RBSDTALIB, RBSKEYLIB, RBSPGMLIB, and RBSTMPLIB. Be aware of the following to ensure that Robot Save is backed up properly.

RBSDTALIB

RBSDTALIB contains backup setup, volume tracking, and guided system restoration information; and library archive data. The RBSDTALIB library is saved automatically after each backup and is the last library on the tape.

Note: If you're running concurrent saves, RBSDTALIB is saved on the tape used by the last save to complete.

RBSKEYLIB

RBSKEYLIB is used by Robot Save 11 if encryption has been enabled. The library contains encryption keys (in encrypted format) for all backup sets where a save history exists. RBSKEYLIB is saved automatically after each backup just before RBSDTALIB.

RBSPGMLIB

The RBSPGMLIB library contains all the object-level archive information. This information is especially important if you save, and need to restore, Robot Corral object lists. The object-level archive is created by the RBSARCHIVE job that runs automatically after each backup completes. Thus, RBSPGMLIB contains object-level archive information only after the RBSARCHIVE job completes.

If you need to restore object list type backups through Robot Save, we recommend that you save and append RBSPGMLIB to the object list backup set as a type 1 alternate backup set. This ensures that the most current versions of RBSPGMLIB, RBSKEYLIB, and RBSDTALIB are the last libraries saved together on that volume. The RBS410 system restoration reports will then report the most current save of RBSPGMLIB, RBSDTALIB, and RBSKEYLIB. For more information about creating an alternate backup set, see “Using Alternate Backup Sets.”

Note: RBSPGMLIB is always saved to a save file and then to tape using the SLSD save code.

RBSTMPLIB

RBSTMPLIB is created automatically by Robot Save during the save process. You do not need to back up this library. If the library is deleted, Robot Save automatically recreates it when needed.

Robot Save Backup Tips

  • RBSKEYLIB and RBSDTALIB are backed up automatically every time someone executes a backup through Robot Save.
  • RBSTMPLIB does not need to be backed up.
  • RBSPGMLIB cannot be backed up if another Robot Save backup job is running.
  • Back up the Robot Corral library, RBTROLLIB, if you're doing object list backups.
  • You don't need to end the Robot Save monitor jobs prior to saving the Robot Save libraries.
  • When restoring Robot Save to a new system, be sure to restore RBTSYSLIB first. Then, restore RBSDTALIB, RBSPGMLIB, and RBSKEYLIB in that order.

 

Robot Schedule

Follow these steps to back up Robot Schedule:

  1. Add the Robot Schedule library to your library list:

    ADDLIBLE ROBOTLIB

  2. Call the following program to end the product:

    CALL RBT107

  3. Enter the command:

    DLYJOB 180

  4. Enter the command:

    SAVLIB LIB(ROBOTLIB) DEV(*SAVF) SAVF(ROBOTLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  5. Optionally, enter the following command to back up the RBTMRGLIB library if you are using the import/export feature of Robot Schedule:

    SAVLIB LIB(RBTMRGLIB) DEV(*SAVF) SAVF(RBTMRGLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  6. Call the following program to start the product:

    CALL RBT103

  7. Enter the following commands to save the Robot Schedule libraries:

    SAVSAVFDTA SAVF(ROBOTLIB) DEV(TAP01)

    SAVSAVFDTA SAVF(RBTMRGLIB) DEV(TAP01)

Robot Schedule Backup Tips

If Robot Schedule is being backed up, then RBTSYSLIB should be backed up as well. See the RBTSYSLIB section below for instructions.

 

Robot Schedule Enterprise

Follow these steps to back up Robot Schedule Enterprise:

  1. End the monitoring jobs:

    RBTENTLIB/RBEENDENT

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. Enter the following command to back up the Robot Schedule Enterprise library:

    SAVLIB LIB(RBTENTLIB) DEV(*SAVF) SAVF(QGPL/RBTENTLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)

  4. Enter the following command to back up the IFS objects:

    SAV DEV('/qsys.lib/qgpl.lib/entfs.file') OBJ(('/Help Systems/SCHEDULE ENTERPRISE') ('/Help Systems/installs'))

  5. Start the Robot Schedule Enterprise monitor job:

    RBTENTLIB/RBESTRENT

  6. Enter the following commands to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTENTLIB) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/ENTIFS) DEV(TAP01)

 

Robot Space

Follow these steps to back up Robot Space:

  1. Enter the following command to stop the monitors:

    RBTSPCLIB/SPCENDMON

  2. Enter the following command:

    SAVLIB LIB(RBTSPCLIB) DEV(*SAVF) SAVF(QGPL/RBTSPCLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  3. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/RBTSPCLIB) DEV(TAP01)

  4. Enter the following command to start the monitors:

    RBTSPCLIB/SPCSTRMON

 

Robot Transform

Follow these steps to back up Robot Transform:

  1. Enter the following command to save the RBTTRNLIB library to a save file:

    SAVLIB LIB(RBTTRNLIB) DEV(*SAVF) SAVF(QGPL/ RBTTRNLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  2. To save a directory, you must use the SAV command. Enter the following command to save the /Help Systems/Robot Transform directory and the /Help Systems/Common Java directory to a save file:

    SAV DEV('qsys.lib/qgpl.lib/transform.file') OBJ(('/Help Systems/Robot Transform') ('/Help Systems/Common Java'))

  3. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/RBTTRNLIB) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/TRANSFORM) DEV(TAP01)

Note: The Robot Transform library and directories are also saved during a full system backup.

 

Robot Trapper

Follow these steps to back up Robot Trapper:

  1. Enter the following commands to end the Robot Trapper monitoring jobs:

    RBTTRPLIB/TRPENDTRPM

    RBTTRPLIB/TRPENDMON

  2. Enter the following command to save the Robot Trapper library:

    SAVLIB LIB(RBTTRPLIB) DEV(*SAVF) SAVF(QGPL/ RBTTRPLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  3. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/ RBTTRPLIB) DEV(TAP01)

  4. Enter the following commands to start Robot Trapper monitor jobs:

    RBTTRPLIB/TRPSTRTRPM

    RBTTRPLIB/TRPSTRMON

 

Robot UPS

Follow these steps to back up Robot UPS:

  1. End the monitoring job:

    RBTUPSLIB/ENDRBTUPS

  2. Enter the following command to delay the job:

    DLYJOB 180

  3. Enter the following command to back up the Robot UPS library:

    SAVLIB LIB(RBTUPSLIB) DEV(*SAVF) SAVF(QGPL/RBTUPSLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  4. Start the monitor job:

    RBTUPSLIB/STRRBTUPS

  5. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/RBTUPSLIB) DEV(TAP01)

 

Robot Browser Interface

To back up the Robot Browser Interface, you must end the web server and save the RBTPORLIB library.

  1. Follow the instructions below (for your platform) to end the web server:

    On the IBM i, enter the following command:
    RBTPORLIB/PORSHUTDWN

    On a UNIX system, enter the following command (Note: This is case sensitive):
    ./stopPortal.sh

    On a PC where the Robot Browser Interface is running as a service, display the Task Manager and manually end the service called Robot Browser Interface.

    On a PC where the Robot Browser Interface is running as an application, go to: Start/Programs/HelpSystems/Robot Browser Interface/Stop Browser.

  2. Enter the following command to back up the RBTPORLIB library to a save file:

    SAVLIB LIB(RBTPORLIB) DEV(*SAVF) SAVF(QGPL/RBTPORLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  3. If the web server is running on the IBM i, enter the following command to copy the IFS objects:

    SAV DEV('/qsys.lib/qgpl.lib/browser.file') OBJ(('/helpsystems'))

  4. Enter the following commands to save the save files to media:

    SAVSAVFDTA SAVF(QGPL/RBTPORLIB) DEV(TAP01)

    SAVSAVFDTA SAVF(QGPL/BROWSER) DEV(TAP01)

 

Easy View

Follow these steps to back up Easy View:

  1. Enter the following command to back up the Easy View library:

    SAVLIB LIB(EZVIEW) DEV(*SAVF) SAVF(QGPL/EZVIEW) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  2. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/EZVIEW) DEV(TAP01)

 

RBTSYSLIB

The Robot System Library RBTSYSLIB contains programs that are essential for all of the Robot products to run. It also contains some products’ data queues that need to be in a library in *SYSBAS. Follow these steps to back up this library:

  1. Enter the following command to back up RBTSYSLIB:

    SAVLIB LIB(RBTSYSLIB) DEV(*SAVF) SAVF(QGPL/RBTSYSLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)

  2. Enter the following command to save the save file to media:

    SAVSAVFDTA SAVF(QGPL/RBTSYSLIB) DEV(TAP01)

RBTSYSLIB Backup Tips

  • If Robot Schedule is being backed up, then RBTSYSLIB should be backed up as well.
  • You must end the RBTSLEEPER subsystem to back up RBTSYSLIB.

 


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: April 16, 2019