Using Robot Schedule in a PowerHA Environment Using an IASP

 

Before You Begin

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.

Notes:

• 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.”

Step A—Installing Robot Schedule

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.

New Installs

When Robot Schedule is installed, it can be replicated with PowerHA.

The following directory is also installed and should be replicated:

/Help Systems/installs/SCH

The following directory is installed and does not need to be replicated:

/Help Systems/Robot SCHEDULE

Step B—Maintaining Robot Schedule in a PowerHA Environment

Updating product_library_name on a PowerHA System

Stop the version of Robot Schedule that you want to update, then perform the update. The hardware replication handles updating the replicated version.

Converting product_library_name on a PowerHA System

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.

Step C—Switching to the PowerHA Version

1. Call program RBT107 to stop Robot Schedule.

2. If you are tracking user jobs, make note of how they are being tracked by running the following:

   WRKOBJ OBJ(ROBOTLIB/RBT087*) OBJTYPE(*DTAARA)
   

   If dtaara RBT087DA only exists then you are tracking all user jobs.
   If dtaara  RBT087DA and RBT087DA1 both exists, you are only tracking user jobs that are prerequisites to Robot Schedule jobs. 

3. Turn off user job tracking. 

   RBTINSSBM INSTALL(*OFF)

4. Before switching, you must deregister Robot Schedule. 

   ROBOTLIB/RBTDRGAPP PRODUCTLIB(product_library_name) ENDRBT(*YES) DLTQUE(*YES)

5. 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

6. Add the product library name to your library list.

   ADDLIBLE product_library_name

7. 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.

8. 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)

9. After the above command completes, execute the following command to initialize the Robot Schedule database.

   RSLSETOID PRC(RBT)

10. If you were using user job tracking, turn it back on by running on of the following commands:
    RBTINSSBM INSTALL(*ON) to track all user jobs
    RBTINSSBM INSTALL(*ON) PREREQONLY(*YES) to track only user jobs that are prerequisites to Robot Schedule jobs. 

11. 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:

    DLTDTAQ DTAQ(RBTSYSLIB/RBTWMNTFY)

    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.

12. 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.

13. Call the following program to start Robot Schedule:

    CALL RBT103

    Note: If you wish to start Robot Schedule with RBTSLEEPER, make sure to set the autostart feature by calling:

    RBTAUTOSTR AUTOSTR(*YES)

    If you prefer to manually control the starting of Robot Schedule use:

    RBTAUTOSTR AUTOSTR(*NO)

Step D—Cross-System Reactivity with Other Systems

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:

  ADDLIBLE product_library_name

  RBTSWAPRMT PREVIOUS(original_live_system_name) CURRENT(new_live_system_name)

Additional Information

RBTSYSLIB

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.

User Profiles

The RBTADMIN and RBTUSER profiles are created automatically on all systems when you install Robot Schedule. DO NOT modify or replicate them.

High Availability and Other Robot Products

For information about running other Robot products in a high availability environment, see "Mirroring the Robot Products."

Licensing 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.