Before You Begin

Only use these instructions if:

  • You're on R05M25 or higher of Robot Console, or

  • You're running Robot Console in an independent ASP (IASP) environment.

If neither of the above statements applies to your system, see Moving Robot Console to Another System (Standard Installations).

WARNING! If you move Robot Console to a system where Robot Console already is installed, all Robot Console records on the target system will be overwritten. Therefore, we recommend you perform a full save of your Robot Console library and RBTSYSLIB on the target system before proceeding. Contact Technical Support for instructions on removing Robot Console from your target system.

 

Backing Up Robot Console on the Source System

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

  2. Make sure no Robot Console message sets are currently running.

  3. If your users have issued the RBCSTRQ command to use the optional notification window in Robot Console, have each user enter the following command:

    product_library_name/RBCENDQ

  4. Make Robot Console inactive. Display the Control Menu and select option 4, or enter the following command on a command line:

    product_library_name/RBCENDCON

  5. Make sure no users are currently using the Robot Console menu system.

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

    • Enter the following command to create a save file to hold the IFS data:

      CRTSAVF FILE(product_library_name/RBCIFS)

    • Enter the following command to save the data to the save file:

      SAV DEV('/QSYS.LIB/product library name.LIB/RBCIFS.FILE') OBJ(('/Help Systems/INSTALLS/CON'))

      Example: Following is an example of saving the IFS directory from an ASP group into a save file in QGPL. Specify the name of the ASP group in the asp_group parameter.

      SAV DEV('/asp_group/QSYS.LIB/product library name.LIB/RBCIFS.FILE') OBJ(('/asp_group/Help Systems/INSTALLS/CON'))

  7. Do the following to save the Robot Console libraries and RBTSYSLIB:

    • Enter the following commands to create the save files:

      CRTSAVF FILE(QGPL/RBCCON)

      CRTSAVF FILE(QGPL/RBCMRG)

      CRTSAVF FILE(QGPL/RBTSYS)

    • Enter the following commands to save the data to the save files:

      SAVLIB LIB(product_library_name) DEV(*SAVF)SAVF(QGPL/RBCCON)

      SAVLIB LIB(merge_library_name) DEV(*SAVF)SAVF(QGPL/RBCMRG)

      SAVLIB LIB(RBTSYSLIB) DEV(*SAVF) SAVF(QGPL/RBTSYS)

  8. Transfer the save files to the target system using FTP. Note the following:

    • Make sure all objects from all libraries are saved.

    • Save RBTSYSLIB only if the target system does not have any other Robot products installed or the release/modification level on the target system is less than R01M971130529.

      Note: If the RBTSYSLIB on the target system has a release/modification level less than R01M971130529, then the RBTSYSLIB on the target system may be incompatible with the Robot Console library from the source system.

 

Restoring Robot Console on the Target System

If your operating system release level is 5.1 or higher, the system values QALWOBJRST and QVFYOBJRST must be set to the following values: QALWOBJRST(*ALL) and QVFYOBJRST(1). To check the system values, enter the following command:

  • WRKSYSVAL system_value

  • On the Work with System Values panel, enter a 2 to change the value. Check that the values are set correctly.

Restoring Robot Console

Perform the following steps to restore Robot Console.

  1. Send the Save Files to the target system and put them in QGPL.

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

    If there are no other Robot products installed on your system or the release/modification level of RBTSYSLIB on the target system is less than R01M971130529, continue with step 3; otherwise, skip to step 7.

  3. Verify that RBTADMIN and RBTUSER are valid user profiles on the target system or partition. If these profiles do not exist on the target system or partition, enter the following commands to create them:

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

    CALL PGM(QGPL/RSL062)

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

  4. Enter the following command to restore RBTSYSLIB:

    RSTLIB SAVLIB(RBTSYSLIB) DEV(*SAVF) SAVF(QGPL/RBTSYS) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(RBTSYSLIB)

  5. Enter the following command to place RBTSYSLIB in your system library list:

    WRKSYSVAL QSYSLIBL

    Then, enter a 2 to change the value and add RBTSYSLIB on the panel. Press Enter.

  6. Sign off and then sign back on using the same user profile. This places RBTSYSLIB in your system library list.

  7. Enter the following commands to restore the Robot Console product library and Robot Console merge library:

    RSTLIB SAVLIB(source_product_lib_name) DEV(*SAVF) SAVF(QGPL/RBCCON) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(target_product_lib_name)

    RSTLIB SAVLIB(source_merge_lib_name) DEV(*SAVF) SAVF(QGPL/RBCMRG) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(target_merge_lib_name)

    Note: If any messages relating to security or data format changes occur, review your job log and make sure all objects from the libraries were restored.

    Example: Following is an example of restoring the saved libraries into an ASP group. Specify the name of the ASP group in the parameters.

    SETASPGRP ASPGRP(asp_group)

    RSTLIB SAVLIB(source_product_lib_name) DEV(*SAVF) SAVF(QGPL/RBCCON) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(target_product_lib_name) RSTASPDEV(asp_group)

    RSTLIB SAVLIB(source_merge_lib_name) DEV(*SAVF) SAVF(QGPL/RBCMRG) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(target_merge_lib_name) RSTASPDEV(asp_group)

  8. 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)

    • Enter the following command to restore the data to the IFS directory:

      RST DEV('/QSYS.LIB/product_library_name.LIB/RBCIFS.FILE') OBJ('/Help Systems/INSTALLS/CON')

    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

  9. Enter the following command to add the Robot Console product library to your library list:

    ADDLIBLE target_product_lib_name

  10. Enter the RBCREGAPP command to register this instance of Robot Console with the Help Systems Exit Point HELPSYS_FYI_ADEX.

    • If this is a Robot NETWORK host, use *YES for the NETWORK parameter. You must use the default library name for PRODUCTLIB and MERGELIB parameters.

      RBTCONLIB/RBCREGAPP PRODUCTLIB(RBTCONLIB) MERGELIB(RBCMRGLIB) NETWORK(*YES)

      Notes:

      • If you wish to run both Robot Console and Robot NETWORK, Robot Console must be installed into *SYSBAS. This is because Robot NETWORK is classed as a "system tool" and isn't modified to install into an IASP environment.

      • Only one instance of Robot Console can be registered with the Robot NETWORK host.

    • If this is not a Robot NETWORK host machine, use *NO for the NETWORK parameter.

      RBTCONLIB/RBCREGAPP PRODUCTLIB(RBTCONLIB) MERGELIB(RBCMRGLIB) NETWORK(*NO)

      Note: If you chose alternate naming for your product libraries, be sure to replace the library names in the command with the ones you selected.

  11. Enter the following command to display the subsystem description for RBTSLEEPER:

    DSPSBSD RBTSLEEPER

    Then, do the following:

    1. Select option 3 (Autostart Job Entries).

    2. Look for an entry for RSLSTART (if one doesn't exist, contact Technical Support).

      Note: Beginning with Robot Console R05M25 (Robot Console HA version), the STRConsole autostart job entry has been replaced with the RSLSTART autostart job entry.

    3. Select option 6 (Job Queue Entries).

    4. Look for entries for RBTSLEEPER, RBCJOBQ, and OPALJOBQ (if they don't exist, contact Technical Support.)

  12. Enter the following command to change the system name:

    RSLCHGSYSN BEFORE(old_system_name) AFTER(new_system_name) PRODUCT(Console)

  13. If you want to reactivate the ‘User to Notify’ and SYSREQ features, enter the following commands:

    RBCSTRQ

    RBCSYSREQ

  14. Verify that all message queues defined in Robot Console exist on the target system.

  15. If there are no other Robot products installed on your system, enter the following command to start the RBTSLEEPER subsystem as it will need to be active to run the OPAL recompilation in the next step:

    STRSBS RBTSLEEPER

  16. You must recompile the OPAL code in your message sets. Use the following command:

    RBTCONLIB/RBCOPLREGN

  17. Display the Robot Console Menu by entering the following command:

    RBC

  18. Select option 4 to display the Control Menu and start Robot Console.

  19. Go to a command line and enter the following command to display your product license:

    CALL RBC245

    Note: If you receive a message that your security code is expiring or has expired, or if your code has turned into a series of Xs, contact Technical Support.

  20. If you created any resources in the source library (for example, Resource Monitors, OPAL, and so on.) where the library name is hard-coded, you will need to change them on the target system if you restored the product library (and merge library) to library names that are different from your source system.

 


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

Last Modified On: March 08, 2018