Make sure there aren’t any users currently using the Robot Schedule menu system or the Robot Schedule GUI.
Sign on under a user profile that is a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ and *SECADM.
Add the product library name to the library list:
ADDLIBLE product_library_name
Execute the following commands to determine if Robot Schedule’s Submit Job feature is being used and if so, which level. This information will be needed later within the Restoring on the Target System section.
WRKOBJ ROBOTLIB/RBT087DA1 *DTAARA - If the object is found, the submit job feature is active and only logging batch jobs currently defined as prerequisites to reactive Robot jobs.
WRKOBJ ROBOTLIB/RBT087DA *DTAARA - If the object is found, the submit job feature is active.
Note: Run the following command to ensure the feature is off when the library is restored to the target system
RBTINSSBM *OFF
Use the following commands to check for jobs in submitted (S) or running (R) statuses:
CALL PGM(RBT650) PARM('S000000000000bbbbbbbbbbbbbbbbbbbbbbbbbX')
CALL PGM(RBT650) PARM('R000000000000bbbbbbbbbbbbbbbbbbbbbbbbbX')
where the string of b's indicates 25 blank spaces.
If you find submitted or running jobs, allow them to complete before continuing, so that those history records can be displayed on the target system.
Execute the following command to stop Robot Schedule:
CALL RBT107
If you are moving Robot Schedule into an IASP, run the following command to deregister the product:
ROBOTLIB/RBTDRGAPP PRODUCTLIB(product_library_name) ENDRBT(*NO) DLTQUE(*YES)
Do the following to save the data in the IFS directory:
Use the following command to create a save file to hold the IFS data:
CRTSAVF FILE(ROBOTLIB/RBTSAVIFS)
Use the following command to save the data to the save file:
SAV DEV('/QSYS.LIB/ROBOTLIB.LIB/RBTSAVIFS.FILE') OBJ(('/Help Systems/installs/SCH'))
Execute the following commands to save the Robot Schedule libraries, RBTSYSLIB, and RBNRBTMST. Notes: Back up RBTSYSLIB only if there are no other Robot products on the target system, or if the release/modification level for RBTSYSLIB on the target system is lower than it is on the source system. Back up RBNRBTMST only if both the source and target systems are host systems.
SAVLIB LIB(RBTSYSLIB) DEV(device_name) OMITOBJ((RBTSYSLIB/RBTWMNTFY *DTAQ))
SAVLIB LIB(ROBOTLIB) DEV(device_name)
SAVLIB LIB(RBTMRGLIB) DEV(device_name)
SAVLIB LIB(RBNRBTMST) DEV(device_name)
where device_name is the name of your save device.
Note: Make sure all objects from all libraries are saved.
Load the media containing ROBOTLIB, RBTSYSLIB, and RBTMRGLIB.
Sign on under a user profile that is a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ and *SECADM.
If there are no other Robot products installed on the target system, or if the release/modification level of RBTSYSLIB on the target system is below the release/modification level on the source system, continue with step 3. Otherwise, skip to step 4.
Do all of the following only if RBTSYSLIB doesn't already exists on the target system (it has no Robot products installed on it). However, if RBTSYSLIB is already on the target system, complete only the second bullet point below (restoring RBTSYSLIB).
Make sure that the user profiles RBTADMIN and RBTUSER are valid user profiles on the target system or partition. If they aren't, use the following commands to create the user profiles:
RSTOBJ OBJ(RSL062) SAVLIB(RBTSYSLIB) DEV(*SAVF) SAVF(savflib/RBTSYSLIB) RSTLIB(QGPL)
CALL PGM(QGPL/RSL062)
DLTOBJ OBJ(QGPL/RSL062) OBJTYPE(*PGM)
Execute the following command to restore RBTSYSLIB:
RSTLIB SAVLIB(RBTSYSLIB) DEV(device_name) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(RBTSYSLIB)
If any messages about security or data format changes occur, review your job log and make sure all objects for the library were restored.
Execute the following command to place RBTSYSLIB in your system library list:
WRKSYSVAL QSYSLIBL
Then, do the following:
Enter option 2, Change, next to QSYSLIBL to update the system library list.
Add RBTSYSLIB at the same sequence number position as it was on the source system.
Sign off the system, then sign on for this change to take effect for your session.
Use the following commands to restore ROBOTLIB, RBTMRGLIB, and RBNRBTMST (if this is a Robot Network host system):
RSTLIB SAVLIB(ROBOTLIB) DEV(device_name) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(ROBOTLIB)
RSTLIB SAVLIB(RBTMRGLIB) DEV(device_name) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(RBTMRGLIB)
RSTLIB SAVLIB(RBNRBTMST) DEV(device_name) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(RBNRBTMST)
If any messages about security or data format changes occur, review your job log and make sure all objects for the libraries were restored.
What you do next depends on the Robot Schedule release/modification level.
For R12M04 and higher, execute the following commands to create database triggers, stored procedures, and functions, and to register the product libraries with the Fortra exit point HELPSYS_FYI_ADEX:
ADDLIBLE ROBOTLIB
ROBOTLIB/RBTREGAPP PRODUCTLIB(ROBOTLIB) MERGELIB(RBTMRGLIB)
Note: If you don't have a merge library on this system, enter *NONE for the MERGELIB parameter.
For R12M03 and lower, execute the following commands to create exit points, database triggers, stored procedures, and functions:
ADDLIBLE ROBOTLIB
CALL RBT108
CALL PGM(ROBOTLIB/RBTINST3) PARM('ROBOTLIB' 'ROBOTLIB' '0' '0' '*')
Execute the following commands to restore the data to the IFS /Help Systems directory:
If there isn't already a /Help Systems directory on the target system, create one using the following command:
CRTDIR DIR('/Help Systems') DTAAUT(*RX) OBJAUT(*NONE)
Enter the following command to change the object owner to RBTUSER:
CHGOWN OBJ('/Help Systems') NEWOWN(RBTUSER)
Enter the following command to create the INSTALLS directory:
CRTDIR DIR('/Help Systems/INSTALLS') DTAAUT(*RWX) OBJAUT(*NONE)
Enter the following command to change the object owner to RBTUSER:
CHGOWN OBJ('/Help Systems/INSTALLS') NEWOWN(RBTUSER)
Restore the data to the IFS directory using the following command:
RST DEV('/QSYS.LIB/ROBOTLIB.LIB/RBTSAVIFS.FILE') OBJ(('/Help Systems/installs/SCH'))
Verify that the data was restored to the IFS.
Use the following command to remove the save file containing the IFS objects:
DLTF ROBOTLIB/RBTSAVIFS
If this library is a mirroring target (you’re setting up a copy of ROBOTLIB for mirroring purposes), skip this step.
If you're restoring this copy of ROBOTLIB to run the product, complete this step to change the system name in the Robot product files. Which of the following two commands you execute depends on the release/modification level of Robot Schedule.
For R11M11 and higher, use the following command:
RBTSWAPSYS SOURCESYS(source_system_name) TARGETSYS(target_system_name)
For R11M10 and lower, use the following command:
RSLCHGSYSN BEFORE(source_system_name) AFTER(target_system_name) PRODUCT(ROBOT)
After the RSLCHGSYSN or RBTSWAPSYS command completes, execute the following command to initialize the Robot Schedule database.
RSLSETOID PRC(RBT)
If you have Robot Network and cross system reactivity you must run the ROBOTLIB/RBTSWAPRMT command on your remote nodes as well to indicate the system name change: ROBOTLIB/RBTSWAPRMT PREVIOUS(source_system_name) CURRENT(target_system_name).
For R12M03 and lower, do the following:
Display the subsystem description for RBTSLEEPER by using the following command:
DSPSBSD RBTSLEEPER
On the Display Subsystem Description panel, select option 3, Display Autostart job entries.
Look for an entry for RBT103. If one does NOT exist, execute the following command:
ADDAJE SBSD(RBTSYSLIB/RBTSLEEPER) JOB(RBT103) JOBD(ROBOTLIB/SLEEPSTART)
Return to the Display Subsystem Description panel. Select option 6, Job queue entries.
Look for an entry for RBTSLEEPER. If one does NOT exist, execute the following command:
ADDJOBQE SBSD(RBTSYSLIB/RBTSLEEPER) JOBQ(RBTSYSLIB/RBTSLEEPER) MAXACT(*NOMAX)
Add ROBOTLIB to your library list by using the following command:
ADDLIBLE ROBOTLIB
If Robot Schedule is at release/modification R12M04 or higher, execute the following command to set whether or not you want Robot Schedule to automatically start when the subsystem RBTSLEEPER starts. Valid values are *SAME, *YES, or *NO.
RBTAUTOSTR AUTOSTART(*SAME)
You must enter a new license code because the target machine has a different serial number and/or model number than the source system. Display a command line and execute the following command:
CALL RBT240
If you receive a message that your security code is expiring or has expired, or if your code displays as a series of Xs, call your Regional Sales Manager.
If the submit job feature referenced in Step #4 of the section titled “Backing Up Robot Schedule on the Source System” was on, use the following commands:
If DTAARA RBT087DA1 was found, therefore the submit job feature was active and only logging batch jobs currently defined as prerequisites to reactive Robot jobs, run the command:
ROBOTLIB/RBTINSSBM PREREQONLY(*YES)
OR
If DTAARA RBT087DA was found, therefore the submit job feature was active, run the command:
ROBOTLIB/RBTINSSBM INSTALL(*ON)
IMPORTANT: It is recommended that after activating the Submit Job feature to end and restart any IBMi subsystems where batch jobs will run that Robot Schedule should capture. You may need to end and restart any subsystems you want monitored by this command. For more information, see the help on the IBM i for the RBTINSSBM command.
Display the Robot Schedule Main Menu by executing one of the following commands:
RBM
or
RBO
Display the Control Menu and start Robot Schedule.
After you're certain that the product is functioning correctly on the target system, you can delete Robot Schedule from the source system. For complete information, see the instructions for removing Robot Schedule from your system (contact Technical Support for the instructions).
