Page 1 of 6 June 2, 2008

Using Robot/SCHEDULE in a
High Availability Environment
(Continued)
Note: The Source and Target systems must be at the same release/modifcation level. Use the following
information to make sure your systems are set up properly.
New Installs
If Robot/SCHEDULE is currently not installed on the Target or Source system, follow the installation
instructions on the CD shipped with the product. You must perform the install on both the Source and
Target systems.
Currently Running Robot/SCHEDULE on the Source System
We recommend that you follow the instructions on moving Robot/SCHEDULE to another system. See
the appropriate Help/FACTS for complete information: Moving Robot/SCHEDULE 9 to a Different
System or Moving Robot/SCHEDULE 10 to a Different System.
Use this document as a guide to set up and manage Robot/SCHEDULE with your mirroring application.
Note: If you use the Robot/SCHEDULE 10 graphical PC interface, you must end it before proceeding.
Introduction
Step 1Installing Robot/SCHEDULE on Your Systems
Page 2 of 6 June 2, 2008
Table 1
Object Specifer for High Availability
Replicate?
Yes or No Object Name Object Type
Object
Attributes
Yes ROBOTLIB/*ALL *DTAARA N/A
Yes ROBOTLIB/*ALL *JOBD N/A
Yes ROBOTLIB/*ALL *PGM *ALL
Yes ROBOTLIB/*ALL *FILE *ALL
Yes ROBOTLIB/*ALL *MSGF N/A
Yes ROBOTLIB/*ALL *CMD N/A
The tables below are for customers who are planning for high availability applications. The tables
defne the Robot/SCHEDULE objects and specify which objects you must replicate to run Robot/
SCHEDULE with high availability software.
Table 1 lists the types of objects that you should mirror.
(Continued)
Step 2Replicating Robot/SCHEDULE Objects
Table 2
Object Specifer for High Availability
Replicate?
Yes or No Object Name Object Type
Object
Attributes
No ROBOTLIB/*ALL *OUTQ
No ROBOTLIB/*ALL *MSGQ
No ROBOTLIB/*ALL *FILE LF
No ROBOTLIB/*ALL *SRVPGM N/A
No ROBOTLIB/*ALL *PNLGRP N/A
No ROBOTLIB/*ALL *USRSPC N/A
No ROBOTLIB/RBT090DA *DTAARA N/A
No ROBOTLIB/RBT660 *DTAARA N/A
No ROBOTLIB/RBT635 *DTAARA N/A
No ROBOTLIB/RBT542DA *DTAARA N/A
No ROBOTLIB/RBT695DA *DTAARA N/A
No ROBOTLIB/CNLIDLEF *FILE PF
No ROBOTLIB/DISKUSE *FILE PF
Table 2 lists specifc objects that you should exclude from mirroring. Although these objects may be
the same type as objects shown in Table 1, they should be defned as exceptions and excluded from
mirroring.
Page 3 of 6 June 2, 2008
(Continued)
Table 2
Object Specifer for High Availability
Replicate?
Yes or No Object Name Object Type
Object
Attributes
No ROBOTLIB/RBTJT* *FILE *ALL
No ROBOTLIB/RBTWMNTFY *DTAQ N/A
No RB0*RB9* (Robot/REPLAY) *DTAARA N/A
No RJ* (EnterpriseOne Interface) *DTAQ N/A
No RJ* (EnterpriseOne Interface) *DTAARA N/A
The Objects Below Apply to Robot/SCHEDULE 9 Only
No ROBOTLIB/RBTJRN *JRN N/A
No ROBOTLIB/RBTJRNxxx *JRNRCV N/A
Notes:
1. Robot/SCHEDULE 10 also includes IFS objects. These objects must exist on the target system, but
should not be mirrored. Read Step 1, Installing Robot/SCHEDULE on Your Systems, and the in-
formation in Updating and Converting Robot/SCHEDULE in the Additional Information section to
make sure that these IFS objects are set up properly.
2. You probably will replicate objects into the ROBOTLIB library on the target system. However, if
Robot/SCHEDULE is active on the target system, the mirrored library will have a different name.
Read Step 3, Considerations When Switching to a Target System, for more information.
Page 4 of 6 June 2, 2008
If you are mirroring Robot/SCHEDULE to a target system on which Robot/SCHEDULE is already
running, you must do the following on the target system before performing Step 4, Switching from the
Source System to the Target System:
Stop Robot/SCHEDULE. Call the RBT107 program in ROBOTLIB.
Rename the Robot/SCHEDULE library ROBOTLIB to another name.
Rename the mirrored library on the target system to ROBOTLIB.
You then can continue with Step 4.
Note: If you are running Robot/SCHEDULE version 9 and Robot/SCHEDULE auditing is active on
the target system, you must delete the journals and journal receivers before renaming the ROBOTLIB
library. Do the following to save the library and journal receivers before deleting them:
Stop Robot/SCHEDULE and enter one of the following commands to save the journal objects or
library:
SAVOBJ OBJ(RBTJRN*) LIB(ROBOTLIB) DEV(*SAVF)
SAVF(SAVFILELIB/SAVE_FILE)
SAVLIB LIB(ROBOTLIB) DEV(*SAVF) SAVF(SAVFILELIB/SAVE_FILE)
End Robot/SCHEDULE Auditing.
Enter the following commands:
DLTJRN JRN(ROBOTLIB/RBTJRN)
DLTJRNRCV JRNRCV(ROBOTLIB/RBTJRN*)
Note: Remember to turn auditing on again when you go back to the source system.
Step 3 Considerations When Switching
to a Target System
(Continued)
Page 5 of 6 June 2, 2008
On the Source System:
Call the RBT107 program in ROBOTLIB to stop Robot/SCHEDULE for a planned switchover.
On the Target System:
You must change the system name in our database fles before running Robot/SCHEDULE on the
target system. You can run the RSLCHGSYSN command in RBTSYSLIB, which modifes the name,
in batch or interactively. Use the RTVNETA command to retrieve the target system name and then
enter it on the RSLCHGSYSN command:
RSLCHGSYSN BEFORE(system_name) AFTER(system_name) PRODUCT(ROBOT)
After the RSLCHGSYSN command completes, run the following command to initialize the Robot/
SCHEDULE database. (Do this only if RBTSYSLIB is at R01M96, dated 071119, or higher. Enter
the command RSLVER to see the release/modifcation level of RBTSYSLIB.)
RSLSETOID PRC(RBT)
Delete the object RBTWMNTFY *DTAQ in ROBOTLIB. This object is created again when you
start Robot/SCHEDULE.
When the switchover occurs, you must start Robot/SCHEDULE on the target system. Call the
program RBT103 in ROBOTLIB to start Robot/SCHEDULE.
Cross-System Reactivity Considerations:
If the source system and the target system have the same system name, cross-system reactivity will
continue to work without any further actions.
If the source system and target system have different system names and you want to continue using
cross-system reactivity, you must run the RSLCHGSYSN command on all systems in the network
that have either a reactive job or a prerequisite job from the original source system. Enter the com-
mand as follows:
RSLCHGSYSN BEFORE(source_system_name) AFTER(target_system_name) PRODUCT(ROBOT)
The command will change only the records that contain the original source system name to the target
system name.
Step 4Switching from the Source System
to the Target System
(Continued)
Page 6 of 6 June 2, 2008
If you have any questions or problems, please call
Help/Systems, Inc. Technical Support at 952-933-0609.
RBTSYSLIB
The Robot System Library, RBTSYSLIB, is a general purpose library that contains common modules for
the Robot Automated Operations Solution. You do not have to replicate this library; however, the library
must be updated when the source or target system is updated with new modifcations. RBTSYSLIB is
updated automatically by conversions, upgrades, and new installations. There is no dynamic data stored
in this library.
User Profles
The RBTADMIN and RBTUSER profles are created automatically on all systems when Robot/
SCHEDULE is installed. DO NOT modify or replicate them.
High Availability and Other Help/Systems Products
For information about running other Help/Systems products in a high availability environment, see the
Help/FACTS, Mirroring Help/Systems Products.
Licensing Help/Systems Products
All Help/Systems products must be licensed on each system before using them in a high availability
environment. Discuss product licensing with your Regional Sales Manager.
Updating or Converting Robot/SCHEDULE
When you update or convert Robot/SCHEDULE on the Source system, you also must make the same
changes on the Target system. We recommend that you end the mirroring product, perform the update
or conversion on the Source system, update or convert the Target System, then re-start the mirroring
process. Different mirroring software products may have options to synchronize the libraries, or to send
all changed objects to the Source system. However, to make sure that all the necessary added or updated
objects are on the Target system, we recommend that you follow the normal update or conversion pro-
cess on both systems.
Additional Information