Help/Systems SEQUEL Software PowerTech Skybot Software
Help/Systems
The World's Leader in IBM iSeries Software Solutions
Home › Support › Help/FACTS › Backing up the Robot Products

Backing up the Robot Products

Purpose

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

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 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 (RSLSHUTDWN) command 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 products except Robot/AUTOTUNE need RBTSYSLIB backed up.

Note: The commands shown in this document may be too long to fit on one line. A plus (+) sign at the end of the line indicates a continuation of the command. You should not enter the plus sign when entering the command on a command line.

Robot/ALERT

Do the following to back up Robot/ALERT.

  1. Enter the following command to end the paging monitoring job:
  2. RBTALRLIB/RBAEND
  3. Enter the following command to prevent Robot/ALERT from starting if someone sends a page:
  4. RBTALRLIB/RBALOCK ACTION(*LOCK)
  5. Enter the following command to delay the job:
  6. DLYJOB 180
  7. Enter the following command to save the Robot/ALERT library:
  8. SAVLIB LIB(RBTALRLIB) DEV(*SAVF) SAVF(QGPL/RBTALRLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  9. Enter the following to start the pager monitoring job:
  10. RBTALRLIB/RBALOCK ACTION(*UNLOCK) RBTALRLIB/RBASTR
  11. Enter the following command to save the save files to media.
  12. 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 e-mail message during the backup to alert you to mount a tape.

Robot/AUTOTUNE

Do the following to back up Robot/AUTOTUNE:

  1. End Robot/AUTOTUNE using either of the following commands:
  2. ATLIB/CNLAT or ATLIB/ENDAT
  3. These commands end the ATMONITOR subsystem and all jobs running in the subsystem.
  4. Note: If you are using dynamic pools, you must wait for the jobs in the dynamic pools to end before continuing.
  5. Enter the following to delay the job:
  6. DLYJOB 180
  7. Enter the following command to back up the Robot/AUTOTUNE library:
  8. SAVLIB LIB(ATLIB) DEV(*SAVF) SAVF(QGPL/ATLIB) SAVACT(*LIB) SAVACTWAIT(1) + ACCPTH(*YES)
  9. Start Robot/AUTOTUNE using the following command:
  10. ATLIB/STRAT
  11. Enter the following command to save the save files to media.
  12. SAVSAVFDTA SAVF(QGPL/ATLIB) DEV(TAP01)

Robot/AUTOTUNE Backup Tips

  • Many customers use Robot/AUTOTUNE to control system performance during save operations. If you are 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 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

Do the following to back up Robot/CLIENT:

  1. End the monitoring job using the following command:
  2. RBTRCLLIB/RCLENDMON
  3. Enter the following to delay the job:
  4. DLYJOB 180
  5. Enter the following command to back up the Robot/CLIENT library:
  6. SAVLIB LIB(RBTRCLLIB) DEV(*SAVF) SAVF(QGPL/RBTRCLLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  7. Start the monitor job:
  8. RBTRCLLIB/RCLSTRMON
  9. Enter the following command to save the save files to media.
  10. 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 re-create the data queue if it does not exist.

This process does not back up the Robot/CLIENT PC software. You do not 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

Do the following to back up Robot/CONSOLE:

  1. Shut down Robot/CONSOLE by entering the following command:
  2. RBTCONLIB/RBCENDCON
  3. Enter the following to delay the job:
  4. DLYJOB 180
  5. Save the library RBTCONLIB to a save file:
  6. SAVLIB LIB(RBTCONLIB) DEV(*SAVF) SAVF(QGPL/RBTCONLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  7. Save the library RBTMRGLIB to a save file: SAVLIB
  8. LIB(RBCMRGLIB) DEV(*SAVF) SAVF(QGPL/RBCMRGLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES).
  9. Note: This is optional. You only need to back up RBTMRGLIB if you are using the import/export feature of Robot/CONSOLE.
  10. Restart Robot/CONSOLE by executing the following command: RBTCONLIB/RBCSTRCON
  11. Back up the save file at a later time using the following commands:
  12. SAVSAVFDTA SAVF(QGPL/RBTCONLIB) DEV(TAP01)
  13. SAVSAVFDTA SAVF(QGPL/RBCMRGLIB) DEV(TAP01)

Robot/CONSOLE Backup Tips

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

Robot/CORRAL

Do the following to back up Robot/CORRAL:

  1. Enter the following command:
  2. SAVLIB LIB(RBTROLLIB) DEV(*SAVF) SAVF(QGPL/RBTROLLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  3. Enter the following command to save the save file to media:
  4. SAVSAVFDTA SAVF(QGPL/RBTROLLIB) DEV(TAP01)

Robot/CORRAL Backup Tips

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

Robot/CPA

Do the following to back up Robot/CPA:

  1. Enter the following command to back up the Robot/CPA library:
  2. SAVLIB LIB(RBTCPALIB) DEV(*SAVF) SAVF(QGPL/RBTCPALIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  3. Enter the following command to save the save files to media.
  4. SAVSAVFDTA SAVF(QGPL/RBTCPALIB) DEV(TAP01)

Robot/CPA Backup Tips

Robot/CPA uses the iSeries 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:
  2. CRTJRNRCV RBTCPALIB/JAJRNRA
  3. Create the journal:
  4. CRTJRN QSYS/QACGJRN
  5. and attach the RBTCPALIB/JAJRNRA journal receiver.
  6. Add a system reply list entry for the message ID CPA7025:
  7. 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

Do the following to back up Robot/LPAR:

  1. Enter the following command:
  2. SAVLIB LIB(RBTLPRLIB) DEV(*SAVF) SAVF(QGPL/RBTLPRLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  3. Enter the following command to save the save file to media:
  4. SAVSAVFDTA SAVF(QGPL/RBTLPRLIB) DEV(TAP01)

Robot/MONITOR

Do the following to back up Robot/MONITOR:

  1. Enter the following command to end the monitoring jobs:
  2. RBTMTRLIB/ENDMTR
  3. RBTMTRLIB/ENDMTRG
  4. Enter the following to delay the job:
  5. DLYJOB 180
  6. Enter the following to back up the Robot/MONITOR library:
  7. SAVLIB LIB(RBTMTRLIB) DEV(*SAVF) SAVF(QGPL/RBTMTRLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  8. Enter the following to start the monitor jobs:
  9. RBTMTRLIB/STRMTR
  10. RBTMTRLIB/STRMTRG
  11. Enter the following command to save the save files to media.
  12. SAVSAVFDTA SAVF(QGPL/RBTMTRLIB) DEV(TAP01) Robot/LPAR

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:
  2. RBTNETLIB/RBNENDHOST
  3. RBTNETNODE/RBNENDNODE
  4. Enter the following to delay the job:
  5. DLYJOB 180
  6. Enter the following command to save the Host library:
  7. SAVLIB LIB(RBTNETLIB) DEV(*SAVF) SAVF(QGPL/RBTNETLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  8. Enter the following command to save the Node library:
  9. SAVLIB LIB(RBTNETNODE) DEV(*SAVF) SAVF(QGPL/RBTNETNODE) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  10. You also should save each Product Master Library periodically. These libraries contain history and product setup data.
  11. Enter the following to save Robot/SCHEDULE Product Master library:
  12. SAVLIB LIB(RBNRBTMST) DEV(*SAVF) SAVF(QGPL/RBNRBTMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  13. Enter the following to save the Robot/CONSOLE Product Master library:
  14. SAVLIB LIB(RBNRBCMST) DEV(*SAVF) SAVF(QGPL/RBNRBCMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  15. Enter the following to save the Robot/UPS Product Master library:
  16. SAVLIB LIB(RBNRBUMST) DEV(*SAVF) SAVF(QGPL/RBNRBUMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  17. Enter the following to save the Robot/SAVE Product Master library:
  18. SAVLIB LIB(RBNRBSMST) DEV(*SAVF) SAVF(QGPL/RBNRBSMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  19. Enter the following to save the Robot/MONITOR Product Master library:
  20. SAVLIB LIB(RBNMTRMST) DEV(*SAVF) SAVF(QGPL/RBNMTRMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  21. Enter the following to save the Robot/REPORTS Product Master library:
  22. SAVLIB LIB(RBNREPMST) DEV(*SAVF) SAVF(QGPL/RBNREPMST) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  23. Enter the following to start the network node and host monitor jobs:
  24. RBTNETLIB/RBNSTRHOST
  25. RBTNETNODE/RBNSTRNODE
  26. Enter the following commands to save the save files to media.
  27. SAVSAVFDTA SAVF(QGPL/RBTNETLIB) DEV(TAP01)
  28. SAVSAVFDTA SAVF(QGPL/RBTNETNODE) DEV(TAP01)
  29. SAVSAVFDTA SAVF(QGPL/RBNRBTMST) DEV(TAP01)
  30. SAVSAVFDTA SAVF(QGPL/RBNRBCMST) DEV(TAP01)
  31. SAVSAVFDTA SAVF(QGPL/RBNRBUMST) DEV(TAP01)
  32. SAVSAVFDTA SAVF(QGPL/RBNMTRMST) DEV(TAP01)
  33. SAVSAVFDTA SAVF(QGPL/RBNRBSMST) DEV(TAP01)
  34. SAVSAVFDTA SAVF(QGPL/RBNREPMST) DEV(TAP01)

Robot/NETWORK Node

Follow these steps to back up each Robot/NETWORK Node system:

  1. End the network monitoring job:
  2. RBTNETNODE/RBNENDNODE
  3. Enter the following to delay the job:
  4. DLYJOB 180
  5. Enter the following command to save the Node library:
  6. SAVLIB LIB(RBTNETNODE) DEV(*SAVF) SAVF(QGPL/RBTNETNODE) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  7. Start the network node monitor job:
  8. RBTNETNODE/RBNSTRNODE
  9. Enter the following command to save the save files to media.
  10. SAVSAVFDTA SAVF(QGPL/RBTNETNODE) DEV(TAP01)

Robot/NETWORK Backup Tips

  • You should back up RBTSYSLIB at the same time you back up Robot/NETWORK to ensure compatibility on restore of the operating system.
  • The Product Master libraries only need to be backed up if you are using them. Sometimes these libraries are loaded during Robot/NETWORK installation, but are never used by the Robot/NETWORK user.

Robot/REPLAY

Do the following to back up Robot/REPLAY:

  1. Enter the following command:
  2. SAVLIB LIB(RBTRPYLIB) DEV(*SAVF) SAVF(RBTRPYLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  3. Enter the following command to save the save file to media:
  4. SAVSAVFDTA SAVF(QGPL/RBTRPYLIB) DEV(TAP01)

Robot/REPORTS

Do the following to back up Robot/REPORTS:

  1. End the output queue monitoring job:
  2. RBTREPLIB/REPENDQMON.
  3. Enter the following to delay the job:
  4. DLYJOB 180
  5. End the monitor job that deletes reports only if the REPDLTMON job is active:
  6. RBTREPLIB/REPSTPDLTQ
  7. Enter the following command to back up the user definitions for handling reports:
  8. SAVLIB LIB(RBTREPLIB) DEV(*SAVF) SAVF(QGPL/RBTREPLIB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  9. Enter the following command to back up any reports that have been archived to short-term storage:
  10. SAVLIB LIB(REPSHTRMLB) DEV(*SAVF) SAVF(QGPL/REPSHTRMLB) SAVACT(*LIB) SAVACTWAIT(1) ACCPTH(*YES)
  11. Start the output queue monitoring job:
  12. RBTREPLIB/REPSTRQMON
  13. Start the delete reports job:
  14. RBTREPLIB/REPSTRDLTQ
  15. Enter the following commands to save the save files to media.
  16. SAVSAVFDTA SAVF(QGPL/RBTREPLIB) DEV(TAP01)
  17. 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 iSeries. 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 five libraries: RBSDTALIB, RBSKEYLIB, RBSPGMLIB, RBSPCBLIB, and RBSTMPLIB. Do the following to make sure 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 are 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 save history exists. RBSKEYLIB is saved automatically after each backup just before RBSDTALIB.

RBSPGMLIB

The RBSPGMLIB library contains all 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 then will report the most current save of RBSPGMLIB, RBSDTALIB, and RBSKEYLIB. For more information about creating an alternate backup set, see the Help/FACTS, “Using Alternate 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 re-creates it automatically when needed.

RBSPCBLIB

Robot/SAVE used the library RBSPCBLIB when backing up PCs. RBSPCBLIB is backed up automatically after a PC backup set.

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 are doing PC or object list backups.
  • You do not 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. Finally, restore RBSPCBLIB if you run PC backups.

Robot/SCHEDULE

Follow these steps to back up Robot/SCHEDULE:

  1. Add the Robot/SCHEDULE library to your library list:
  2. ADDLIBLE ROBOTLIB
  3. Call the following program:
  4. CALL RBT107
  5. Enter the command:
  6. DLYJOB 180
  7. Enter the command:
  8. SAVLIB LIB(ROBOTLIB) DEV(*SAVF) SAVF(ROBOTLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  9. Optionally, enter the following command to back up the RBTMRGLIB library if you are using the import/export feature of Robot/SCHEDULE:
  10. SAVLIB LIB(RBTMRGLIB) DEV(*SAVF) SAVF(RBTMRGLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  11. Call the following program:
  12. CALL RBT103
  13. Enter the following commands to save the Robot/SCHEDULE libraries:
  14. SAVSAVFDTA SAVF(ROBOTLIB) DEV(TAP01) SAVSAVFDTA SAVF(RBTMRGLIB) DEV(TAP01)

Robot/SCHEDULE Backup Tip

The library, RBTSYSLIB, also should be backed up periodically (once a month is sufficient). This library contains no data, but does contain programs that are essential for Robot/SCHEDULE to run.

Robot/SPACE

Do the following to back up Robot/SPACE:

  1. Enter the following command:
  2. 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:
  4. SAVSAVFDTA SAVF(QGPL/RBTSPCLIB) DEV(TAP01)

Robot/TRANSFORM

Do the following to back up Robot/TRANSFORM:

  1. Enter the following command to save the RBTTRNLIB library to a save file:
  2. SAVLIB LIB(RBTTRNLIB) DEV(*SAVF) SAVF(QGPL/ RBTTRNLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  3. Enter the following command to save the save file to media:
  4. SAVSAVFDTA SAVF(QGPL/RBTTRNLIB) DEV(TAP01)
  5. 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:
  6. SAV DEV(‘/qsys.lib/libraryname.lib/savfname.file’) OBJ((‘/Help Systems/Robot Transform’) (‘/Help Systems/Common Java’))
  7. To save the directories to a device, enter the command as follows:
  8. SAV DEV(‘/QSYS.LIB/TAP02.DEVD’) OBJ((‘/Help Systems/Robot Transform’) (‘/Help Systems/Common Java’))

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

Robot/TRAPPER

Do the following to back up Robot/TRAPPER:

  1. Enter the following commands to end the Robot/TRAPPER monitoring jobs
  2. RBTTRPLIB/TRPENDTRPM
  3. RBTTRPLIB/TRPENDMON
  4. Enter the following command to save the Robot/TRAPPER library:
  5. SAVLIB LIB(RBTTRPLIB) DEV(*SAVF) SAVF(QGPL/ RBTTRPLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  6. Enter the following command to save the save file to media:
  7. SAVSAVFDTA SAVF(QGPL/ RBTTRPLIB) DEV(TAP01)
  8. Enter the following commands to start Robot/TRAPPER monitor jobs
  9. RBTTRPLIB/TRPSTRTRPM
  10. RBTTRPLIB/TRPSTRMON

Robot/UPS

Do the following to back up Robot/UPS:

  1. End the monitoring job:
  2. RBTUPSLIB/ENDRBTUPS
  3. Enter the following to delay the job:
  4. DLYJOB 180
  5. Enter the following command to back up the Robot/UPS library:
  6. SAVLIB LIB(RBTUPSLIB) DEV(*SAVF) SAVF(QGPL/RBTUPSLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  7. Start the monitor job:
  8. RBTUPSLIB/STRRBTUPS
  9. Enter the following command to save the save file to media.
  10. 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. Do the following to end the Web server, depending on your platform:
  2. On the iSeries, enter the following command:
  3. RBTPORLIB/PORSHUTDOWN
  4. On a UNIX system, enter the following command (Note: this is case sensitive):
  5. ./stopPortal.sh
  6. 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.
  7. On a PC where the Robot Browser Interface is running as an application, go to Start/Programs/ HelpSystems/Robot Browser Interface/Stop Browser.
  8. Enter the following command to back up the RBTPORLIB library to a save file:
  9. SAVLIB LIB(RBTPORLIB) DEV(*SAVF) SAVF(QGPL/RBTPORLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  10. Enter the following command to save the save file to media:
  11. SAVSAVFDTA SAVF(QGPL/RBTPORLIB) DEV(TAP01)

EASY VIEW

Do the following to back up Easy View:

  1. Enter the following command to back up the Easy View library:
  2. SAVLIB LIB(EZVIEW) DEV(*SAVF) SAVF(QGPL/EZVIEW) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  3. Enter the following command to save the save file to media:
  4. SAVSAVFDTA SAVF(QGPL/EZVIEW) DEV(TAP01)

RBTSYSLIB

Do the following to back up the Robot System Library, RBTSYSLIB:

  1. Enter the following command to back up RBTSYSLIB:
  2. SAVLIB LIB(RBTSYSLIB) DEV(*SAVF) SAVF(QGPL/RBTSYSLIB) SAVACT(*LIB) SAVACTWAIT(2) ACCPTH(*YES)
  3. Enter the following command to save the save file to media.
  4. SAVSAVFDTA SAVF(QGPL/RBTSYSLIB) DEV(TAP01)

RBTSYSLIB Backup Tips

  • This library only needs to be backed up when a new version is applied to the system. Ideally, once a month should be sufficient.
  • You must end the RBTSLEEPER subsystem to back up RBTSYSLIB. RBTSYSLIB

Benefits of the Above Procedures

Following the procedures described in this document gives you the following benefits:

  • Reduce down time for the Robot Products.
  • Speed up the process through the use of save while active processing.
  • You can enter these procedures directly into the Robot/SAVE backup set panels.

Additional Considerations

If you do a SAVLIB LIB(*NONSYS) once a month, that may be the only backup of the Robot Products 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. This 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.

If you have any questions or problems, please call Help/Systems, Inc. Technical Support at 952-933-0609.

Updated Jan 1, 2007