Before You Begin

Read these instructions completely before you begin.

  • This document provides specific instructions on how to convert Robot Console using the HelpSystems Product Loader. For general information about the HelpSystems Product Loader, see “Using the HelpSystems Product Loader.”

  • When you’re finished, read the After You Are Done section for additional information.

  • Before loading Robot Console, we check if RBTSYSLIB needs to be updated. If it does, you’ll be asked to bring down the subsystem RBTSLEEPER. This ends all Robot products running on your system. When the update completes, the subsystem will restart automatically.

  • The Robot Console conversion process creates or changes two user profiles: RBTUSER and RBTADMIN. These profiles were created for the following reasons:

    • They satisfy requests from corporate auditors that our objects be owned differently from IBM objects.

    • They allow us to build a secure product for your environment.

    • They isolate the Robot products from IBM changes to the QPGMR or QSECOFR profile defaults.

    Note: If you've made any manual changes to the RBTUSER or RBTADMIN user profiles or their authorities, these changes will be lost with any product installation or conversion.

  • If you've made any manual changes to the job descriptions in Robot Console, these changes will be lost with any product conversion.

  • Robot Console enables you to convert into an independent ASP (IASP), and allows you to have an instance of Robot Console running in *SYSBAS, as well as one in each ASP group. Here are some things to consider prior to converting into an IASP:

    • You can convert directly from the *SYSBAS copy of version 6 Robot Console into an IASP, using the RBCINSTALL command

    • When converting Robot Console in *SYSBAS, the version 6 library names are: RBTCONV6, RBCMRGV6, and RBNRBCMST6.

      When converting Robot Console in an IASP, the version 6 library names are: RBTCONV6IA and RBCMRGV6IA.

    • Each Robot Console instance must be licensed and must have a unique library name, unless the library is in an IASP. Since libraries in ASP groups reside in their own namespace, they may have duplicate names across ASP groups.

    • System-based objects like QSYSOPR message queue, log monitoring, and FTP monitoring should be monitored from *SYSBAS because your IASP may become unavailable.

    • Robot Console users will need to use the SETASPGRP command, or have their user profile’s JOBD specify the INLASPGRP, prior to using Robot Console.

      Important: QDFTJOBD should never set INLASPGRP, because ASP groups are not available until after IPL, and may cause your system to fail to IPL.

      The Robot Console Explorer has advanced connection information that allows users to specify the ASP group and library name if users do not have their ASP group set by their job description.

  • If you have any network security products, be aware that the GUI version of Robot Console uses the following servers and exit points:

    Servers Exit Points
    RMTCMD QIBM_QZRC_RMT
    SIGNON QIBM_QZSO_SIGNONSRV
    DATABASE QIBM_QZDA_SQL1 and QIBM_QZDA_SQL2
    FILE QIBM_QPWFS_FILE_SERV

    We recommend that all the exit points listed above be open to RBTUSER, RBTADMIN, and the user logging into the Robot Console Explorer.

    These exit points are for Robot Console standalone connections only. For Host mode, refer to the exit points for your version of Robot Network.

  • Read through the questions in the following table. If you answer “yes” to a question in the first column, follow the instructions in the second column. If you answer “no” to a question, skip the corresponding instructions.

    If you answer Yes... Read this...

    Do you have data you don’t want to lose?

    Use the following command to make a backup copy of the RBTCONLIB library before continuing:

    SAVLIB LIB(RBTCONLIB) DEV(TAP01) VOL(*MOUNTED)

    Note: The product must be inactive before saving the library. Make sure that all of the objects in the library are saved.

    Have you placed objects or data in your Robot Console version 6 library?

    The conversion will not copy or move objects you have placed in RBTCONLIB. Save these objects before starting the conversion.

    Do you import or export message sets to other systems?

    No data in RBCMRGLIB is converted. Complete any import or export of Robot Console message sets before converting. You cannot transfer files from version 6 to version 7.

    Do you use other Robot products in addition to Robot Console?

    For other Robot products to work properly with Robot Console version 7, they must be at the following release/modification levels or higher:

    • Robot Network
      • Host R12M00, node R12M00
      • You must update Robot NETWORK to the versions shown on all systems before continuing the conversion.

    Note: Convert Robot Console on your Robot Network host and alternate host systems first. Then, convert Robot Console on the node systems to provide full cross-system redirection. If you use the Robot Console Product Master, be sure to make a backup copy of the product master library RBNRBCMST on the host system before upgrading.

    • Robot Alert R05M66
    • Robot Trapper R01M23

    If you have the following products they must all be converted at the same time and in the following order:
    Robot Network
    Robot Console
    Robot Schedule
    Robot Schedule Enterprise

    Are you retaining large amounts of history?

    We recommend that you purge Robot Console 6 history records to 14 days before proceeding with the conversion. See the Robot Console User Guide for complete information.

    Do you use Robot Network and is this the host system?

    We recommend that you purge Robot Console history from Robot Network using the following command:

    RBNDLTSTS FRSY(*ALL) PRNM(CONSOLE) DAYS(007)

    End the Robot Network host by using the following command, before you start the conversion:

    RBTNETLIB/RBNENDHOST

    Do you have RBTCONLIB or RBCMRGLIB in the system value QSYSLIBL or QUSRLIBL?

    Remove them. Enter these commands to see if any jobs have a lock on RBTCONLIB or RBCMRGLIB:

    WRKOBJLCK RBTCONLIB *LIB

    WRKOBJLCK RBCMRGLIB *LIB

    End all jobs that have a lock on either library and then restart them.

    Do you use Robot Console resource monitoring?

    Resource Monitoring—and the first-level and second-level message text for resource monitoring—has been enhanced. Refer to the Robot Console 6 Enhancements document for details on the new features and any changes to Robot Console that may affect your setup.

    Note: Message IDs CPU0001 and CPU0002 were removed from the message file RBCRSCF. You'll need to updated any message sets or message tables that reference these message IDs.

    Do you plan to use Robot Console log monitoring (FTP, QHST, and/or security audit journal)?

    Robot Console writes a history record for every message it processes. Log monitoring can significantly increase the amount of disk space used for message history. We recommend that you delete message history records regularly to prevent disk space problems. See "Selecting Message History Records to Purge," in the "Message History" section of the Robot Console User Guide for complete information on deleting message history.

    Do you monitor message queues from a third-party software vendor?

    Check the authority for the message queues being monitored before converting to Robot Console 7. *PUBLIC or RBTUSER must have *CHANGE authority to the message queues.

    Do you use SNDSNMPMSG in OPAL to escalate messages to your Enterprise Monitor?

    You must restart Robot Console and the SNMP server after you convert. To do so, execute the following commands:

    1.  RBTCONLIB/RBCENDCON
    2.  ENDTCPSVR *SNMP
    3.  STRTCPSVR *SNMP
    4.  RBTCONLIB/RBCSTRCON

 

Robot Console Pre-Checker

Before you load Robot Console, you can run a pre-checker to determine whether or not the load will complete successfully. To run the pre-checker, do the following:

  1. Use the "Converting Robot Console" instructions to download everything to your PC.

  2. When you reach the Product Load Options panel, select Staged Load (step 5b below) and wait until the processing completes.

  3. On the IBM i, execute the following command to display the Work with Loads panel:

    HSLOADMGR/HSWRKLOAD

  4. Enter option 2, Run pre-checker, next to the Load Name for Robot Console and press Enter.

  5. Review the information on the Pre-check Install Console 6 panel. Select *UPGRADE for the conversion, then press Enter.

Note: A pre-checker automatically runs during the first part of the Robot Console conversion process, but we recommend you run it in advance to identify any potential problems before attempting a full conversion.

 

Converting Robot Console

The Robot Console conversion process downloads everything to your PC and transfers the objects to the IBM i. This process is described in the following section.

  1. Download the Robot Console installer (setupConsole7.exe) from My Downloads page on our website. Double-click it to start it.

  2. On the Choose Components panel, select which components you want to load. You can choose the Software for Windows (the GUI and the Manuals) and the Software for the IBM i. Click Next.

  3. If you’re only installing the Software for Windows, the process completes and the installer closes. The Software for Windows has been installed. You can skip the rest of these steps.

    Note: The manuals were installed at the following location.

    • C:\Program Files (x86)\Help Systems\Robot CONSOLE 7\manuals

    If you’re loading the Software for IBM i (with or without the Software for Windows), continue to step 4.

  4. On the IBM i Details panel:

    1. Select or enter the IBM i where you want to install Robot Console.

    2. Enter a user profile and password that’s a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ, *SECADM, *JOBCTL, and *IOSYSCFG. The user profile should have Limit capabilities set to *NO. This profile will be used to restore and copy objects, and for product maintenance on the IBM i.

    3. (Optional) In the Advanced Settings section:

      • Enter a port number or use the arrows if you want to change the FTP port number to something other than the default of 21.

      • Select Secure File Transfer if you want to use FTPS (FTP over SSL) during the file transfer. The default FTPS secure port is 990, but it can be changed to the required secure port for your environment.

      • In the Timeout (seconds) field, enter the number of seconds the session should be kept active during an FTP transfer. You can choose anywhere between 25 and 1800 seconds (30 minutes).

        Note: If the transfer takes longer than the amount of time specified, the session will expire.

      • Enter the name of a destination ASP group if you want to change the ASP group to something other than the default group *SYSBAS.

    4. Click Next.

  5. You have two options on the Product Load Options panel:

    1. Click Immediate Load if you’d like to load the product on the IBM i now.

      Note: This ends Robot Console until the product load completes. After you are done, we’ll restart the product.

    2. Click Staged Load if you’d like to transfer the objects now and load them on the IBM i at a later time.

      Note: See “Loading Staged Objects on the IBM i” below for instructions on how to load the staged objects on your selected IBM i system.

  6. The Product Load Progress panel for Robot Console launches. When the processing is complete, you have two choices:

    • If this is the only conversion of Robot Console that you're doing, click Finish.

    • If you have conversions to do on other IBM i systems, click Restart. Then, return to step 4.

    Note: If the Product Load Progress panel ends with an overall Failed message, the product upload could not complete properly. To find the reason the upload failed, click View Logs and review your logs. You can also use Download at the top of the logs to save the information for future review.

 

Loading Staged Objects on the IBM i

If you chose to stage your objects during step 5b of the conversion process, do the following to manually load them on the IBM i you identified above.

  1. Execute the following command to make sure no users are signed on to the product you're installing:

    WRKOBJLCK OBJ(RBTCONLIB) OBJTYPE(*LIB)

  2. Remove RBTCONLIB from all library lists. There should be no object locks on the RBTCONLIB library.

  3. Execute the following command to display the Work with Loads panel:

    HSLOADMGR/HSWRKLOAD

  4. Enter option 1, Load, next to the Load Name for Robot Console and press Enter.

 

After You Are Done

  • After the conversion completes, enter the WRKSPLF command to check the spooled files for any errors that may have occurred. If you have any questions, contact Technical Support.

  • You can start the Robot Console Explorer from the PC (refer to the Robot Console User Guide for more information).

  • Both Robot Console 6 GUI and Robot Console 7 GUI can be installed on a PC at the same time. You can, however, use the Robot Console 7 GUI to connect to Robot Console 6 on the IBM i.

    • If you decide to remove Robot Console 6 from your PC, you must perform the process manually—the conversion process does not remove Robot Console 6 from your PC.

    • When you run Robot Console on your PC, you can view help text directly from the PC by pressing F1, or by selecting Robot Console Help from the Help menu.

  • After you've successfully converted Robot Console and are satisfied the product is running well, you can delete the following libraries: RBTCONV6, RBCMRGV6, and RBNRBCMST6 (if Robot Console is on a machine where Robot Network is also installed)

  • You can access the Robot Console User Guide and other documentation from our website.

  • Three libraries were restored to your system for use during the conversion process: HSLOADMGR, HSLOADMGRW, and RBTCDRLIB. We don't remove them from your system in case you're doing multiple conversions. You can delete them when you're finished.

    Note: You can move the library HSLOADMGR to a different system on the IBM i and use it to complete additional conversions. For more information, see “Using the HelpSystems Product Loader.”


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

Last Modified On: July 19, 2019