Help/Systems SEQUEL Software PowerTech Skybot Software
Help/Systems
The World's Leader in IBM iSeries Software Solutions

Converting Robot/NETWORK Version 9 to Version 10

Product: 
Robot/NETWORK

Before You Begin

Keep the following items in mind before you convert Robot/NETWORK 9 to Robot/NETWORK 10.

Robot Product Considerations

  • Robot/NETWORK 10 uses a point-and-click graphical user interface that replaces its previous graphical and green screen interfaces.
  • Make sure you have your new Robot/NETWORK security codes for your Host(s) and Nodes. If you do not, please contact your Regional Sales Manager.
  • If there are any firewalls between your PC and the System i, verify that your System i user profile has access to the PC. Also, if you have any firewalls between your System i servers, they must allow access to the RBTNETPT profile.
  • If you have any network security products, be aware that the GUI version of Robot/NETWORK uses the following servers and exit programs:
  • Servers Exit Points
    RMTCMD QIBM_QZRC_RMT
    SIGNON QIBM_QZSO_SIGNONSRV

    We recommend that both the exit points listed above be open to RBTUSER, RBTADMIN, RBTNETPT, and the user logging into the Robot/NETWORK Explorer.

    Robot/NETWORK Explorer also uses the DDM TCP/IP server.

  • Robot/NETWORK does not support mirroring. Do not mirror the RBTNETLIB library, the RBTNETNODE library, the RBTNETPT user profile, or the Robot/NETWORK IFS directory (Help/Systems/Robot NETWORK).
  • You cannot convert to Robot/NETWORK 10 while your system is in restricted state.
  • You must convert the Robot/NETWORK 9 Host to Robot/NETWORK 10 before you convert any of its Nodes.
  • You do not have to convert your Robot/NETWORK 9 Node(s) at the same time that you convert your Robot/NETWORK 9 Host. However, only the following network functions are supported between a Robot/NETWORK 10 Host and a Robot/NETWORK 9 Node:
    • Product statuses
    • Cross-system reactivity using Robot/SCHEDULE
    • Cross-system redirection using Robot/CONSOLE
    • The RBNPOLL command
    • No other Robot/NETWORK 10 functions, including packets, are supported between a Robot/
      NETWORK 10 Host and a Robot/NETWORK 9 Node.

  • If you are converting a Robot/NETWORK 9 Node configured as an Alternate Host, you have two options:
    • If you want the Node to be an Alternate Host after the conversion, convert it as a Host by using the HLPCNET10 conversion code (see Converting Robot/NETWORK).
    • Note: You must convert the Host and the Alternate Host before you convert any of the other Nodes.

    • If you do not want the Node to be an Alternate Host after the conversion, remove Robot/NETWORK 9 from the Node (see the Help/FACTS, Removing NETWORK 9) and install Robot/NETWORK 10, configuring the System i as a Robot/NETWORK 10 Node.
  • If you are converting to other Robot products at the same time, usually you must convert Robot/NETWORK last. However, you must convert to Robot/NETWORK 10 before you convert to Robot/SCHEDULE 10.
  • Make sure that no one is using Robot/NETWORK.
  • Back up your current RBTNETLIB, RBTNETNODE, and RBTSYSLIB libraries on all systems—the conversion process updates these libraries.
  • If you are using Robot/SAVE in a data center, you must end the Robot/SAVE monitors on all systems before you start the conversion.
  • To run Robot/NETWORK 10 with any of the following Help/Systems products, you need the indicated release/modification levels (or higher) for these products:
  • Robot/ALERT R05M00
    Robot/AUTOTUNE R07M19
    Robot/CONSOLE R04M30
    Robot/MONITOR R07M08
    Robot/NETWORK 9 Node R09M62
    Robot/REPORTS R07M31
    Robot/SAVE* R10M22
    Robot/SCHEDULE R10M12 for a Robot/NETWORK 10 Host or Node

    * If you have set up a Robot/SAVE data center, you must update all of the systems that are part of the data center to Robot/SAVE 10.22, or higher.

    To display the release and modification levels of these products, type RBTSYSLIB/RSLVER and press Enter.

  • Two Robot/NETWORK 9 user profiles, RBTNETH and RBTNETN, are deleted during the conversion to Robot/NETWORK 10. The Robot/NETWORK 10 user profile, RBTNETPT, created during the conversion, uses the group profile RBTUSER to communicate between systems in the network.
  • The conversion process calls a Help/Systems program to create or change the two Help/Systems user profiles, RBTUSER and RBTADMIN. The RBTUSER and RBTADMIN 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 Help/Systems products from IBM changes to the QPGMR or QSECOFR profile defaults.
  • Note: If you have made any manual changes to the RBTUSER or RBTADMIN user profiles and their authorities, these changes will be lost with any product installation or conversion.

TCP/IP Considerations

Robot/NETWORK 10 uses TCP Host Servers and Java to communicate between a Host and a Node. You may have to change your initial startup program to allow more time for these services to start before starting the RBTSLEEPER subsystem. For example, you might need to delay the job several minutes (DLYJOB) between the time the TCP Host Servers start and the time the RBTSLEEPER subsystem is started.

Enterprise Monitoring

If you are escalating statuses as SNMP traps from your Robot/NETWORK Host system to enterprise monitoring software (or plan to), you must configure your SNMP trap structure using the new MIB that was created for Robot/NETWORK 10. After the installation or conversion of a Host, you must define the Trap Manager information using the Robot/NETWORK 10 Explorer to activate the SNMP escalation. Refer to the Help/FACTS, How Robot/NETWORK 10 Supports SNMP Traps for complete information.

Prerequisite IBM i Software

To use Robot/NETWORK 10, you must have the following software installed on your System i:

OS Level
Software Required

Any*

QSHELL - product option 0030

CCA Cryptographic Service Provider - option 0035

V7R1

Portable App Solutions Environment, product option 33

Java SE 6 32 bit - 5761JV1, option 11 or J2SE 5.0 32 bit - 576JV1, option 8

V6R1

Java Developer Kit 5.0 - 5761JV1, option 7 (minimum) or J2SE 5.0 32 bit - 5761JV1, option 8, with 5761SS1 option 33

PTF 5761SS1 - SI30973

PTF 5761SSI - SI31025

V5R4

Java Developer Kit 5.0 - 5722JV1, option 7 (minimum) or J2SE 5.0 32 bit - 5722JV1, option 8, with 5722SS1 option 33

PTF SI24672 for Java Developer Kit 5.0

* Robot/NETWORK 10 is supported for IBM i V5R4 and higher.

Fully Qualified Host Name

For successful network communications, Robot/NETWORK 10 requires a fully qualified TCP/IP host name in the format of system_name.domain_name to be in the local directory and/or the DNS server. You can use the command CFGTCP and options 10 and 12 to set up host names. For more information, contact your system administrator or Help/Systems Technical Support.

Pre-Conversion Checker

Before converting Robot/NETWORK, you can run a pre-conversion utility to determine whether the conversion will complete successfully.

  1. Display the Maintain Help/Systems Products menu by entering the following command:
  2. RBTCDRLIB/HLPCDMENU

  3. Select option 5 from the Maintain Help/Systems Products menu and enter the following code:
  4. HLPSNET10 (for a Host)

    HLPSNOD10 (for a Node)

Converting Robot/NETWORK

To convert Robot/NETWORK 9 to 10, do the following:

  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, *JOBCTL, and *IOSYSCFG.
    • This user profile should have Limit capabilities set to *NO.
    • Make sure no users are signed on to the product you are converting.
  2. End all Help/Systems products on the current system. The conversion process stops the RBTSLEEPER subsystem, which is used by other Help/Systems products. Stopping RBTSLEEPER interrupts processing by these products.
  3. Note: If you have RBTSYSLIB, R01M87 or later, you can use the RSLSHUTDWN command to end all Help/Systems products and the RBTSLEEPER subsystem.

  4. If you are converting a Host, end all of its Nodes.
  5. If the current system is part of a Robot/SAVE data center, end Robot/SAVE on all of the systems that are part of the data center.
  6. Remove the RBTNETLIB and RBTNETNODE libraries from all library lists. The conversion program must be able to rename these libraries.
  7. Display the Maintain Help/Systems Products menu by entering the following command:
  8. RBTCDRLIB/HLPCDMENU

  9. Select option 4 from the Maintain Help/Systems Products menu and enter one of the following conversion codes:
  10. HLPCNET10 (to convert a Host)

    HLPCNOD10 (to convert a Node)

After You Are Done

At the end of the conversion you will see a series of messages indicating the status of the conversion.

  • If the conversion was successful:
    • You can enter your new Robot/NETWORK Host security code from a command prompt on the Robot/NETWORK Host system. Enter the commands ADDLIBLE RBTNETLIB and CALL RBN394 to display the Robot/NETWORK License setup panel. Enter the code, or press function key 11 to paste it. Then, install Robot/NETWORK on the PC using the instructions below.
    • You must enter you new Node security code(s) using the Robot/NETWORK Explorer (see Installing Robot/NETWORK 10 On A PC).
  • If the conversion was unsuccessful, examine the job log to determine what went wrong, fix the problem(s), and retry the process. You can enter the WRKSPLF command and check the conversion spooled files and job log for errors. Call Help/Systems Technical Support if you have any questions.

Deleting Libraries

The conversion process creates two libraries, RBTHOSTV9 and RBTNODEV9. After you are satisfied that the conversion was a success, you can delete these libraries. Also, if you have Robot/SAVE version 11 on your Host system, you can delete the RBNRBSMST library.

Installing Robot/NETWORK 10 On A PC

After you have finished the System i portion of the conversion, do the following to install the Robot/NETWORK 10 graphical interface on a PC.

  1. Close all Windows applications.
  2. Download the Robot/NETWORK for Windows installation file (setupnetwork10.exe) from the Help/Systems Web site.
  3. Note: If you quit the installation process at any time during the installation, a partial install will have occurred. To resolve this, just start the installation process from Step 2. All existing files will be replaced and the product will be installed correctly on the PC.

  4. When the installation program completes, view the README file to see any last-minute information about the product.
  5. Note: After the conversion is complete, the Robot/NETWORK Explorer may not immediately reflect a Node converted from Robot/NETWORK 9. Each converted Node must start Java processes and servers, and pass new configuration data to the Host. This process may take a few minutes before the Robot/NETWORK Explorer can display the changes. To verify the changes to your network configuration, wait a few minutes and click Refresh in the Robot/NETWORK Explorer.

  6. Enter the new security codes for your Robot/NETWORK Node systems. Select Product License Manager from the Tools menu to display the Product License Manager window. On this window you can select each Node, right-click to display the menu, select Edit License to display the Product License window, and select View 1 to enter your security code, or View 2 to paste it.

 Updated Jan. 20, 2011