Use this topic as a guide to help set up and manage Robot Schedule with your hardware replication in a PowerHA® environment using an IASP.
You must be running Robot Schedule R12M04 or higher to use these instructions.
Throughout this topic, product_library_name is used to represent the Robot Schedule product library. When following instructions, replace product_library_name with your Robot Schedule library name, regardless of whether or not you use the default name ROBOTLIB. For more information on using non-default product library names, see “Running the Robot Products in an IASP Environment.”
When installing Robot Schedule, a product library and a merge library are installed. You can use the default names, ROBOTLIB and RBTMRGLIB, or you can choose different library names during the install. These libraries are installed to the ASP device you choose at installation time.
In addition to the product and merge libraries, the Robot system library RBTSYSLIB is also installed/updated as needed when Robot Schedule is installed. Library RBTSYSLIB resides in the system ASP.
When Robot Schedule is installed, it can be replicated with PowerHA.
The following directory is also installed and should be replicated:
The following directory is installed and does not need to be replicated:
/Help Systems/Robot SCHEDULE
Stop the version of Robot Schedule that you want to update, then perform the update. The hardware replication handles updating the replicated version.
Stop the version of Robot Schedule that you want to convert, then perform the conversion. The hardware replication handles the changes to the replicated version.
Call program RBT107 to stop Robot Schedule for a switchover.
After the PowerHA version has been made the live version, but before starting Robot Schedule, complete these steps to ensure non-replicated items (that is, Robot Schedule exit points) are in place. Note: Since RBTSYSLIB is a *SYSBAS library, you must ensure that it’s at a release/modification level equal to or higher than the RBTSYSLIB that was running with the Live Robot Schedule product before the switchover
Add the product library name to your library list.
Execute the following command to register the Robot Schedule product library and merge library with the Help Systems exit point HELPSYS_FYI_ADEX:
product_library_name/RBTREGAPP PRODUCTLIB(product_library_name) MERGELIB(merge_library_name)
If you don’t have a merge library on this system, enter *NONE for the MERGELIB parameter. If you used the default merge library name, enter RBTMRGLIB.
If you’re using cross-system reactivity from the original live system to other systems in the network, you must change the system name in our database files if you’re now running the live Robot Schedule (the PowerHA version) with a different system name.
Execute the following command:
RBTSWAPSYS SOURCESYS(original_live_system_name) TARGETSYS(new_live_system_name)
After the above command completes, execute the following command to initialize the Robot Schedule database.
If the PowerHA version is running on a different system from where the original live version was running, execute the following command to delete the data queue RBTWMNTFY (if it exists) from library RBTSYSLIB on the new live system:
Note: If you’re running this instance of Robot Schedule in an IASP, the data queue name is the same as the ASP group name. In that case, substitute the actual data queue name for RBTWMNTFY in the above command.
If you have an environment where there’s reactivity between the original live system and other systems in the network, see “Step D—Cross-System Reactivity with Other Systems” before starting Robot Schedule in step 9 below.
Call the following program to start Robot Schedule:
Note: If you wish to start Robot Schedule with RBTSLEEPER, make sure to set the autostart feature by calling:
If you prefer to manually control the starting of Robot Schedule use:
If you have an environment where there is reactivity between the original live system and a different system, follow the directions in the option below that apply for your environment.
If you’re unsure which systems have reactive jobs or remote group members, the following reports can help. Be sure to check for the target system name since the original source system name has already been changed. Look for other networked systems with reactive jobs or remote group members.
Cross System Prerequisite Jobs
Cross System Reactive Jobs
Remote Group Member Jobs
Option 1: If the original live system and the new live system have the same system name, cross-system reactivity will continue to work without any further action.
Option 2: If the original live system and new live system have different system names and you want to continue using cross-system reactivity, do one of the following:
If your remote system is running Robot Schedule 11M10 or lower, use the RSLCHGSYSN command on the remote system that has either a reactive job or a prerequisite job from the original live system. Execute the following command on the remote system:
RSLCHGSYSN BEFORE(original_live_system_name) AFTER(new_live_system_name) PRODUCT(ROBOT)
If your remote system is running Robot Schedule 11M11 or higher, use the RBTSWAPRMT command on the remote system that has either a reactive job or a prerequisite job from the original live system. Execute the following commands on the remote system:
RBTSWAPRMT PREVIOUS(original_live_system_name) CURRENT(new_live_system_name)
The Robot System Library, RBTSYSLIB, is a general purpose library that contains common modules for the Robot Automated Operations Solution. When doing a switchover to the PowerHA version, the library must be at the same release/modification level (or higher) as the original live system. RBTSYSLIB resides in the system asp.
The RBTADMIN and RBTUSER profiles are created automatically on all systems when you install Robot Schedule. DO NOT modify or replicate them.
For information about running other Robot products in a high availability environment, see "Mirroring the Robot Products."
All Robot products must be licensed on each system where they’ll be running. Discuss product licensing for PowerHA with your Regional Sales Manager.
Still have questions? We can help. Submit a case to Technical Support.