During this procedure, you may need to refer to the Robot Schedule User Guide and the instructions for removing Robot Schedule from your system (contact Technical Support for those instructions).

Before You Begin

Follow the instructions in this topic if either of the following is true:

  • You're using Robot Schedule R12M04 or higher, and you’re not using the default library names (ROBOTLIB and RBTMRGLIB).

  • You’re using Robot Schedule R12M04 or higher, and you’re running Robot Schedule in an independent ASP (IASP).

If neither of the above statements apply to your system, see Moving Robot Schedule to a Different System (Standard Installations) for instructions. Note: If you’re running Robot Schedule R12M03 or lower, and ROBOTLIB resides in an IASP, contact Technical Support for assistance in moving Robot Schedule.

Note: Robot Replay, Robot Schedule Enterprise, Robot Schedule EnterpriseOne, and Robot Schedule Interface to SAP will not interface with Robot Schedule in an iASP.

If you use the Robot Schedule graphical PC interface, you must end it before proceeding.

Beginning with R12M04, you can install Robot Schedule using library names other than the default product library name ROBOTLIB and the default merge library name RBTMRGLIB. However, be aware that using a non-default product library name may render some product interfaces unusable with Robot Schedule. For example, both the Robot Network and Robot Schedule Enterprise interfaces require that the Robot Schedule product library be named ROBOTLIB.

WARNING! If you're moving Robot Schedule to a system where Robot Schedule is already installed, all of the Robot Schedule records on the target system will be overwritten. Therefore, if Robot Schedule is installed on the target system, we recommend you perform a full save of ROBOTLIB and RBTSYSLIB on the target system before proceeding. After you create the backup, you must either rename or delete ROBOTLIB on the target system before proceeding. Do not restore the source system’s product library over the top of the existing product library on the target system.

Backing Up Robot Schedule on the Source System

  1. Make sure there aren’t any users currently using the Robot Schedule menu system or the Robot Schedule GUI.

  2. Sign on under a user profile that is a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ and *SECADM.

  3. If you’re not already in the ASP group of the instance of Robot Schedule you want to save, execute the following command to set your ASP group:

    SETASPGRP asp_group_name

    If you’ll be working out of the system ASP, enter *NONE for the asp_group_name parameter.

  4. Add the product library name to the library list:

    ADDLIBLE product_library_name

  5. Execute the following command to turn off the Robot Schedule Submit Job feature:

    RBTINSSBM *OFF

    Note: Use this command even if you're not sure whether or not you're using this feature, because the feature must be off when the library is restored to the target system.

  6. Use the following commands to check for jobs in submitted (S) or running (R) statuses:

    CALL PGM(RBT650) PARM('S000000000000bbbbbbbbbbbbbbbbbbbbbbbbbX')

    CALL PGM(RBT650) PARM('R000000000000bbbbbbbbbbbbbbbbbbbbbbbbbX')

    where the string of b's indicates 25 blank spaces.

    If you find submitted or running jobs, allow them to complete before continuing, so that those history records can be displayed on the target system.

  7. Execute the following command to stop Robot Schedule:

    CALL RBT107

  8. Do the following to save the data in the IFS directory:

    1. Use the following command to create a save file to hold the IFS data:

      CRTSAVF FILE(product_library_name/RBTSAVIFS)

    2. Use the following command to save the data to the save file:

      SAV DEV('/QSYS.LIB/product_library_name.LIB/RBTSAVIFS.FILE') OBJ(('/Help Systems/installs/SCH'))

      Note: If you’re saving an instance from an IASP, specify the name of the ASP group in the OBJ parameter. For example: OBJ(('/asp_group_name/Help Systems/installs/SCH'))

  9. Execute the following commands to save the Robot Schedule libraries and RBTSYSLIB. Note: Back up RBTSYSLIB only if there are no other Robot products on the target system, or if the release/modification level for RBTSYSLIB on the target system is lower than it is on the source system.

    SAVLIB LIB(RBTSYSLIB) DEV(device_name)

    SAVLIB LIB(product_library_name) DEV(device_name)

    SAVLIB LIB(merge_library_name) DEV(device_name)

    where device_name is the name of your save device.

    Note: Make sure all objects from all libraries are saved.

Restoring Robot Schedule on the Target System

  1. Load the media containing the product library (default is ROBOTLIB), merge library (default is RBTMRGLIB), and RBTSYSLIB.

  2. Sign on under a user profile that is a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ and *SECADM.

    If there are no other Robot products installed on the target system, or if the release/modification level of RBTSYSLIB on the target system is below the release/modification level on the source system, continue with step 3. Otherwise, skip to step 4.

  3. Do all of the following only if RBTSYSLIB doesn't already exists on the target system (it has no Robot products installed on it). However, if RBTSYSLIB is already on the target system, complete only the second bullet point below (restoring RBTSYSLIB).

    • Make sure that the user profiles RBTADMIN and RBTUSER are valid user profiles on the target system or partition. If they aren't, use the following commands to create the user profiles:

      RSTOBJ OBJ(RSL062) SAVLIB(RBTSYSLIB) DEV(*SAVF) SAVF(savflib/RBTSYSLIB) RSTLIB(QGPL)

      CALL PGM(QGPL/RSL062)

      DLTOBJ OBJ(QGPL/RSL062) OBJTYPE(*PGM)

    • Execute the following command to restore RBTSYSLIB:

      RSTLIB SAVLIB(RBTSYSLIB) DEV(device_name) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(RBTSYSLIB)

      If any messages about security or data format changes occur, review your job log and make sure all objects for the library were restored.

    • Execute the following command to place RBTSYSLIB in your system library list:

      WRKSYSVAL QSYSLIBL

      Then, do the following:

      1. Enter option 2, Change, next to QSYSLIBL to update the system library list.

      2. Add RBTSYSLIB at the same sequence number position as it was on the source system.

      3. Sign off the system, then sign on for this change to take effect for your session.

  4. If you’re not already in the ASP group you’ll be restoring the libraries to, enter the following command to set the ASP group:

    SETASPGRP asp_group_name

    If you’ll be working out of the system ASP, enter *NONE for the asp_group_name.

  5. Restore the Robot Schedule product and merge libraries to the ASP group.

  6. Execute the following commands to create database triggers, stored procedures, and functions, and to register the product libraries with the HelpSystems exit point HELPSYS_FYI_ADEX:

    ADDLIBLE target_product_library_name

    target_product_library_name/RBTREGAPP PRODUCTLIB(target_product_library_name MERGELIB(target_merge_library_name)

    Note: If you don't have a merge library on this system, enter *NONE for the MERGELIB parameter.

  7. Execute the following commands to restore the data to the IFS /Help Systems directory:

    • If there isn't already a /Help Systems directory on the target system, create one using the following command:

      CRTDIR DIR('/Help Systems') DTAAUT(*RX) OBJAUT(*NONE)

    • Enter the following command to change the object owner to RBTUSER:

      CHGOWN OBJ('/Help Systems') NEWOWN(RBTUSER)

    • Enter the following command to create the INSTALLS directory:

      CRTDIR DIR('/Help Systems/INSTALLS') DTAAUT(*RWX) OBJAUT(*NONE)

    • Enter the following command to change the object owner to RBTUSER:

      CHGOWN OBJ('/Help Systems/INSTALLS') NEWOWN(RBTUSER)

    • Restore the data to the IFS directory using the following command:

      RST DEV('/QSYS.LIB/ROBOTLIB.LIB/RBTSAVIFS.FILE') OBJ(('Help Systems/installs/SCH'))

    Note: If you’re creating the /Help Systems directory in an ASP group, then include the ASP group in the above commands as:

    /asp_group/Help Systems

  8. Verify the data was restored to the IFS.

  9. Use the following command to remove the save file containing the IFS objects:

    DLTF target_product_library_name/RBTSAVIFS

  10. If this product library is a mirroring target (you’re setting up a copy of the product library for mirroring purposes), skip this step.

    If you're restoring this copy of the product library to run the product, do the following:

    1. Use the following command to change the system name in the Robot product files:

      RBTSWAPSYS SOURCESYS(source_system_name) TARGETSYS(target_system_name)

    2. After the above command completes, execute the following command to initialize the Robot Schedule database:

      RSLSETOID PRC(RBT)

  11. Display the subsystem description for RBTSLEEPER by using the following command:

    DSPSBSD RBTSLEEPER

  12. Execute the following command to set whether or not you want Robot Schedule to automatically start when the subsystem RBTSLEEPER starts. Valid values are *SAME, *YES, or *NO.

    RBTAUTOSTR AUTOSTART(*SAME)

  13. You must enter a new license code because the target machine has a different serial number and/or model number than the source system. Display a command line and execute the following command:

    CALL RBT240

    If you receive a message that your security code is expiring or has expired, or if your code displays as a series of Xs, call your Regional Sales Manager.

  14. To turn on the optional Robot Schedule Submit Job feature, use the following command:

    RBTINSSBM *ON

    You may need to end and restart any subsystems you want monitored by this command. For more information, see the help on the IBM i for the RBTINSSBM command.

  15. Display the Robot Schedule Main Menu by executing one of the following commands:

    RBM

    or

    RBO

  16. Display the Control Menu and start Robot Schedule.

  17. After you're certain that the product is functioning correctly on the target system, you can delete Robot Schedule from the source system. For complete information, see the instructions for removing Robot Schedule from your system (contact Technical Support for the instructions).

 


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

Last Modified On: March 08, 2018