Help/Systems SEQUEL Software PowerTech Skybot Software
Help/Systems
The World's Leader in IBM iSeries Software Solutions
Home › Support › Help/FACTS › Moving Robot/CONSOLE to Another System

Moving Robot/CONSOLE to Another System

Product: 
Robot/CONSOLE: iSeries Message Management Software

Before You Begin

If you are moving Robot/CONSOLE to a system that already has Robot/CONSOLE installed, all of the Robot/CONSOLE records on the target system will be overwritten. Therefore, you may want to save the RBTCONLIB and RBTSYSLIB libraries on the target system before proceeding. Robot/CONSOLE should be at R3M37 or higher to make sure it is compatible with your current operating system release level.

Backing Up Robot/CONSOLE on the Current 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 Robot/CONSOLEʼs optional notification window, have each user enter the following command:

    4. RBTCONLIB/RBCENDQ

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

    5. RBCENDCON

  5. Make sure no users are currently using the Robot/CONSOLE menu system.
  6. Enter the following commands to save RBTCONLIB and RBTSYSLIB:

    7. SAVLIB LIB(RBTCONLIB) DEV(device name) SEQ(1)

    SAVLIB LIB(RBCMRGLIB) DEV(device name) SEQ(2)

    SAVLIB LIB(RBTSYSLIB) DEV(device name) SEQ(*END)

    where: device name is the name of the save device.

  7. Verify that the IFS directory /Help Systems/installs exists on the target system. If it does not exist, create it. Then, use Navigator for i (Operations  Navigator) to copy the following objects from this directory on the source system to the same directory on the target system:
    • The Console-Module.jar
    • The RBCINST.jar
    • The /Help Systems/installs/CON directory

      Note: Verify that this directory contains the objects, gui.relmod and setupconsole5.exe.

  8. Use Navigator for i to copy the directory /Help Systems/Robot CONSOLE to the same directory on the target system.

Notes:

  • Make sure all objects from all libraries are saved.
  • Save RBTSYSLIB only if the target system does not have any other Help/Systems products installed.

Restoring Robot/CONSOLE on the Target System

Note: 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, do the following:

  • Enter the following command and press Enter:

    • WRKSYSVAL system_value

  • On the Work with System Values panel, enter a 2 to change the value. Check that the values are set as described above.
  1. Load the tape you created with the saved libraries.
  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, *SECADM, and *JOBCTL.

    3. If there are no other Help/Systems products installed on your system, continue with Step 3. If you have other Help/Systems products installed, skip to Step 7.

  3. Enter the following command to restore RBTSYSLIB from your tape:

    4. RSTLIB LIB(RBTSYSLIB) DEV(device name) MBROPT(*ALL) ALWOBJDIF(*ALL)

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

    5. CHGSYSLIBL LIB(RBTSYSLIB) *ADD

  5. Sign off and then sign back on using the same user profile to place RBTSYSLIB in your library list.
  6. Then, enter the following command:

    7. CALL RSL062

    This creates two new user profiles, RBTADMIN and RBTUSER, on your system.

  7. Enter the following commands to restore RBTCONLIB and RBCMRGLIB from your tape:

    8. RSTLIB LIB(RBTCONLIB) DEV(device name) MBROPT(*ALL) ALWOBJDIF(*ALL)

    RSTLIB LIB(RBCMRGLIB) DEV(device name) MBROPT(*ALL) ALWOBJDIF(*ALL)

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

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

    9. RSLCHGSYSN BEFORE(old system name) AFTER(new system name) + PRODUCT(CONSOLE)

  9. Add RBTCONLIB to your library list by entering the following command:

    10. ADDLIBLE RBTCONLIB

  10. Display the subsystem description for RBTSLEEPER by entering the following command:

    11. DSPSBSD RBTSLEEPER

    • Select option 3 (Autostart Job Entries).
    • Look for an entry for STRCONSOLE (if one does NOT exist, call Technical Support).
    • Select option 6 (Job Queue Entries).
    • Look for entries for RBTSLEEPER, RBCJOBQ, and OPALJOBQ (if they do NOT exist, call Technical Support).
  11. If you want to reactivate the User to Notify and SYSREQ features, enter the following commands:

    12. RBCSTRQ

    RBCSYSREQ

  12. Verify that all message queues defined in Robot/CONSOLE exist on the target system.
  13. You must recompile the OPAL code in your message sets. Use the following command:

    14. RBCOPLREGN

  14. Display the Robot/CONSOLE Menu by entering the following command:

    15. RBC

  15. Select option 4 to display the Control Menu and start Robot/CONSOLE.
  16. Go to a command line and enter the following command:

    17. 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, call Technical Support.

  17. If the new system is at a different operating system level than the previous system, enter the following command to update all message files in Robot/CONSOLE that have different dates:

    18. RBTCONLIB/RBCCRTMFD MSGF(*REBUILD) 

  18. Create a function to use the Robot/CONSOLE Explorer (the graphical interface):

    CREATE FUNCTION RBTCONLIB/RBCGETMSGTXT ( MSGFILE VARCHAR (10) ,
    MSGFLIB VARCHAR (10) , MSGID VARCHAR (7) , MSGDTA VARCHAR (3072) ,
    GETFMT VARCHAR (1) ) RETURNS CHAR (256) LANGUAGE RPGLE
    PARAMETER STYLE GENERAL NOT DETERMINISTIC
    NO SQL RETURNS NULL ON NULL INPUT
    EXTERNAL NAME 'RBTCONLIB/RBC772(RBCGETMSGTXT)' NOT FENCED

Updated May 15, 2012