Read these instructions completely before attempting an installation or update.
Note: Robot Replay, Robot Schedule Enterprise, Robot Schedule EnterpriseOne, and Robot Schedule Interface to SAP will not interface with Robot Schedule in an iASP.
This document provides specific instructions on how to install or update Robot Schedule using the HelpSystems Product Loader. For general information about the HelpSystems Product Loader, see “Using the HelpSystems Product Loader."
The Robot Schedule installation creates or changes two user profiles: RBTUSER and RBTADMIN. These profiles were created for the following reasons:
They satisfy requests from corporate auditors that our objects be owned differently from IBM objects.
They allow us to build a secure product for your environment.
They isolate the Robot products from IBM changes to the QPGMR or QSECOFR profile defaults.
Note: If you have made any manual changes to the RBTUSER or RBTADMIN user profiles and their authorities for another product, these changes will be lost with any product installation or conversion.
No other Robot products can be active while Robot Schedule is installed or updated. End the RBTSLEEPER subsystem before starting the process. For minimal impact on your operations, plan to install at a time when your Robot products do not need to be active.
For installs only: When you are finished loading Robot Schedule, follow the steps below to enter the license code.
Once the installation or update process completes, read the After You Are Done section for additional information.
If you are currently on 12.00 through 12.03, you cannot have jobs in an 'S' (submitted) status when updating from below 12.04, but you can have jobs in an 'R' (running) status and successfully update in this scenario.
If you have any network security products, be aware that Robot Schedule Explorer (the graphical user interface) uses the following servers and exit points:
|DATABASE||QIBM_QZDA_SQL1 and QIBM_QZDA_SQL2|
We recommend that all the exit points listed above be open to RBTUSER, RBTADMIN, and the user logging on to the Robot Schedule Explorer.
These exit points are for Robot Schedule standalone connections only. For Host mode, refer to the exit points for your version of Robot NETWORK.
Important:We’ve greatly improved the bundled installers to make them easier to use. However, we recommend you read the installation/update/conversion instructions carefully before proceeding.
Robot provides integrated solutions to your systems management needs. There are often dependencies between the software you are about to download and other HelpSystems products you may have installed. Please review the instructions listed above carefully. You may need to update other products for a successful update or conversion.
IBM i (i5/OS, OS/400) version 7.2 or higher
If you use any of the following Robot products, you must convert them to the release/modification levels shown, in the order shown, for the conversion to complete properly, and for the other products to work properly with Robot Schedule 13.
|Product Name||Version Required|
|Robot Replay||3.06 (or higher)|
|Robot Autotune||7.18 (or higher)|
|Robot Reports||7.27 (or higher)|
|Robot Network Host and Node||12.00 (or higher)|
|Robot Alert||5.38 (or higher)|
Note: To find the release/modification level of the Robot products on your system, enter the command RSLVER on a command line.
Robot Schedule enables you to install into an independent ASP (IASP), and allows you to have an instance of Robot Schedule running in *SYSBAS, as well as one in each ASP group. Review the following prior to installing into an IASP:
Each Robot Schedule instance must be licensed and have a unique library name, unless the library is in an IASP. Since libraries in ASP groups reside in their own namespace, they may have duplicate names across ASP Groups.
You need to use the SETASPGRP command, or have your user profile’s JOBD specify the INLASPGRP, prior to using Robot Schedule.
Important: QDFTJOBD should never set INLASPGRP, because ASP groups are not available until after IPL, and may cause your system to fail to IPL.
In the Robot Schedule Explorer, you can specify the ASP group on the Advanced Connection Properties window if users don’t have their ASP group set by their job description.
Note: Only run the pre-checker before a new installation. Do not run the pre-checker before an update.
Before you load Robot Schedule, you can run a pre-checker to determine whether or not the load will complete successfully. To run the pre-checker, do the following:
Use the "Installing or Updating Robot Schedule" instructions to download everything to your PC.
When you reach the Product Load Options panel, select Staged Load (step 5b below) and wait until the processing completes.
On the IBM i, execute the following command to display the Work with Loads panel:
Enter option 2, Run pre-checker, next to the Load Name for Robot Schedule and press Enter.
Review the information on the Pre-check Robot Schedule panel. Select *NEW for the installation, then press Enter.
Note: A pre-checker automatically runs during the first part of the Robot Schedule installation, but we recommend you run it in advance to identify any potential problems before attempting a full installation.
Use these instructions to install or update Robot Schedule. This process downloads everything to your PC and loads the objects on the IBM i. Read the following steps carefully to proceed.
Download the Robot Schedule Installer (setupSchedule13.exe) from My Downloads page on our website. Double-click it to start it.
On the Choose Components panel, select which components you want to install. You can choose to install the Software for Windows (the GUI and the Manuals) and the Software for IBM i. Click Next.
If you are only installing the Software for Windows, the process completes and the installer closes. The Software for Windows has been installed. You can skip the rest of these steps.
Note: The manuals were installed at the following location.
C:\Program Files (x86)\Help Systems\Robot SCHEDULE 13\manuals
If you’re loading the Software for IBM i (with or without the Software for Windows), continue to step 4.
On the Choose a Destination IBM i panel:
Select or enter the IBM i where you want to load Robot Schedule.
Enter a user profile and password that’s a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ, *SECADM, *JOBCTL, and *IOSYSCFG. The user profile should have Limit capabilities set to *NO. This profile will be used to restore and copy objects, and for product maintenance on the IBM i.
Note: If you are installing or updating Robot Schedule in an IASP, your user profile’s JOBD must have the IASP specified to it.
(Optional) In the Advanced Settings section:
Enter a port number or use the arrows if you want to change the FTP port number to something other than the default of 21.
Select Secure File Transfer if you want to use FTPS (FTP over SSL) during the file transfer. The default FTPS secure port is 990, but it can be changed to the required secure port for your environment.
In the Timeout (seconds) field, enter the number of seconds the session should be kept active during an FTP transfer. You can choose anywhere between 25 and 1800 seconds (30 minutes).
Note: If the transfer takes longer than the amount of time specified, the session will expire.
Change the name of the destination ASP group, if it’s different from the default group *SYSBAS.
You have two options on the Product Load Options panel:
Click Immediate Load if you would like to load the product on the IBM i now.
Note: If you are doing an update, this ends Robot Schedule until the product load completes. After you are done, we will restart the product.
Note: See “Loading Staged Objects on the IBM i” below for instructions on how to load the staged objects on your selected IBM i system.
The Product Load Progress panel for Robot Schedule launches. When the processing is complete, you have two choices:
If this is the only installation or update of Robot Schedule that you are doing, click Finish.
If you have installs or updates to do on other IBM i systems, click Restart. Then, return to step 4.
Note: If the Product Load Progress panel ends with an overall Failed message, the product upload could not complete properly. To find the reason the upload failed, click View Logs and review your logs. You can also use Download at the top of the logs to save the information for future review.
If you chose to stage your objects during step 5b of the installation or update process, do the following to manually load them on the IBM i you identified above.
If you are loading Robot Schedule into an IASP:
Run the following command to set the ASP group:
Execute the following command to display the Work with Loads panel:
Enter option 1, Load, next to the Load Name for Robot Schedule and press Enter.
The installation program installs Robot Schedule, the RBTSYSLIB library (as needed), and two user profiles (RBTADMIN and RBTUSER). It adds RBTSYSLIB to the system portion of your library list, if required.
Review the information on the Robot Schedule Installation panel and make changes as needed, then press Enter.
Note: You only need to enter a license code after installing Robot Schedule. If you updated Robot Schedule, skip these steps.
After you load Robot Schedule, you must enter a license code in order to use the product. If you have not received a license code, contact your Regional Sales Manager.
Execute the following command on the IBM i to open the Installed Robot Products panel:
Enter option 1 by Robot Schedule to open the Robot Schedule License Setup panel.
Copy your new license code. Then, paste it into the first entry field under License Code (it will automatically fill the other fields).
Enter the following command to display the ROBOT Main Menu:
Set up Robot Schedule on your system as described in the Robot Schedule User Guide. If you did not install the manuals on your PC, you can download them from our website.
Three libraries were restored to your system for use during the installation or update process: HSLOADMGR, HSLOADMGRW, and RBTCDRLIB. We don't remove them from your system in case you're doing multiple installations. You can delete them when you're finished.
Note: You can move the library HSLOADMGR to a different system on the IBM i and use it to complete additional installs or updates. For more information, see “Using the HelpSystems Product Loader."
Still have questions? We can help. Submit a case to Technical Support.