Before You Begin
This document is meant as a guide to help set up and manage Robot Console with your hardware replication in a PowerHA® environment.
You must be running Robot Console R05M25 or higher to use these instructions.
We use product_library_name to represent the Robot Console product library. When following the instructions below, replace product_library_name with your Robot Console library name, regardless of whether you used RBTCONLIB or another, non-default name, for your library.
If you are running Robot Console with other products, use the Robot Console *DEFAULT library names: RBTCONLIB, RBCMRGLIB, and if Robot Network is installed, RBNRBCMST.
If you wish to run both Robot Console and Robot Network, then Robot Console must be installed into *SYSBAS. This is because Robot Network is classed as a "system tool" and, therefore, is not modified to install into an IASP environment.
- Robot Console may have more than one instance installed. In order to facilitate this, we have created a Fortra registry (HELPSYS_FYI_ADEX). An install or update of Robot Console will register the instance with the new Fortra registry.
If you restore a copy of Robot Console, use the RBCREGAPP command to register the instance.
To remove a registry entry, use the RBCDRGAPP command.
- In addition to registering with the HELPSYS_FYI_ADEX exit point, the RBCREGAPP command does the following:
Changes all of the source (data) library references in our files to the new target library name. Note: If you use the Robot Console library in your object types, you will need to manually change those references.
Updates the PRDLIB on all Robot Console commands that do not use PRDLIB(*NONE).
Changes any Message Table references from the source library to the target library.
Executes the RBCOPLREGN command to recompile the OPAL source.
Executes the RBCCRTMFD command to refresh the message files that Robot Console will monitor.
If you installed Robot Console into an independent ASP (IASP) in a PowerHA environment, make sure you have your ASP Group set by using *JOBD INLASPGRP or by using the SETASPGRP command. If switching between IASP and *SYSBAS, make sure to use SETASPGRP ASPGROUP(*NONE) before working with commands in *SYSBAS.
You can use RSLVER, or RBO followed by pressing F10, to view the installed products. Depending on how your ASP Group is set, you may see multiple instances.
If you have multiple instances installed, and your ASP group is set, press F11 to toggle through the screens to see the instance name, the release of the product, or the installed library name.
To change the instance description, enter option 2 next to the Robot Console PowerHA instance you wish to change.
Step 1—Installing Robot Console on Your Systems
Note: The source and target systems must be at the same release/modification level. Use the following information to make sure your systems are set up properly.
If Robot Console is not currently installed on the source or target system, see “Installing or Updating Robot Console” for instructions on installing it. You must perform the installation on both the source and target systems.
If you are currently running Robot Console on the source system
We recommend that you follow the instructions for moving Robot Console to another system. For complete information, see “Moving Robot Console to Another System.”
Converting Robot Console in a PowerHA environment
We recommend that you follow the instructions for converting Robot Console from version 5 to version 6. For complete information, see “Converting Robot Console 5 to 6.”
Working with product_library_name
Installing product_library_name on a PowerHA system
Install Robot Console on the PowerHA system, exactly as you would on your production system. Note: The product release/modification levels must be the same on both the source and the target systems.
If you choose to install by using a Save/Restore method, refer to the appropriate “Moving Robot Console to Another System“ instructions.
Updating product_library_name on a PowerHA system
Stop the version of Robot Console that you want to update, and then perform the update. The hardware replication handles updating the replicated version.
Converting product_library_name on a PowerHA system
Note: Do not use the mirroring or journaling process to perform the conversion.
Stop the version of Robot Console that you want to convert, and then run the conversion.
Restart the product.
Step 2—Switching from the Source System to the Target System
On the source system
Use the following command to stop Robot Console for a planned switchover:
On the target system
You must change the system name in our database files before running Robot Console on the target system. To do this, run the RSLCHGSYSN command in RBTSYSLIB, which modifies the name, in batch or interactively. Use the DSPNETA command to retrieve the target system name and then enter it on the RSLCHGSYSN command:
RSLCHGSYSN BEFORE(source_system_name) AFTER(target_system_name) PRODUCT(CONSOLE)
After the command completes, 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)
Note: 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.
Use the following command to start Robot Console:
Note: If you wish to start Robot Console with RBTSLEEPER, make sure to set the auto-start feature by calling:
If you prefer to manually control the starting of Robot Console use:
The Robot System Library, RBTSYSLIB, is a general purpose library that contains common modules for the Robot Automated Operations Solution. The library must be updated when the source or target system is updated with new modifications. RBTSYSLIB is updated automatically by conversions, upgrades, and new installations. No dynamic data is stored in this library.
The RBTADMIN and RBTUSER profiles are created automatically on all systems when Robot Console is installed. DO NOT modify them.
High availability and other Robot products
For information about running other Robot products in a PowerHA environment, see "Mirroring the Robot Products."
Licensing Robot products
All Robot products must be licensed on each system before using them in a PowerHA environment. Discuss product licensing with your Regional Sales Manager. Robot Console now supports multiple license codes for use in a PowerHA environment.