Read these instructions completely before you begin.
This document provides specific instructions on how to convert Robot Alert using the HelpSystems Product Loader. For general information about the HelpSystems Product Loader, see “Using the HelpSystems Product Loader.”
All of the Robot products must be inactive during the conversion; and in fact, Robot Alert will be locked. Plan your conversion for a time when this will have little effect on your operations.
Make sure that no users have the library RBTALRLIB in their library list.
Make sure you have a complete backup of the RBTALRLIB library.
During the conversion process, if any messages are sent to Robot Alert, both Robot Alert and the RBTSLEEPER subsystem will become active. To prevent this from happening, you must lock Robot Alert before you begin the conversion (see Loading Staged Objects on the IBM i below), and then unlock it afterward (see After You Are Done below).
The conversion process deletes and recreates your line descriptions in Robot Alert. If you've made any changes to these line descriptions, note them before you begin the conversion, so you can reapply them afterward.
Job descriptions are replaced during the conversion process. If you've made changes to RBAJOBD, RBAMON, or RBARPT, you must reapply them following the conversion.
Physical file descriptions are replaced during the conversion process. If you've made changes to any of the descriptions, such as the maximum number of records, you must reapply them following the conversion.
We recommend that you use the Robot Alert History Menu option to delete the history in both the transmission log and message history files before you begin the conversion.
To use Robot Alert's paging feature with Robot Save's Restricted State Utility (RSU), you must have Robot Save version 8.35 or higher.
To use Robot Alert's two-way paging feature with Robot Console, you must have Robot Console version 6 or higher.
Before loading Robot Alert, we check if RBTSYSLIB needs to be updated. If it does, we will automatically update it prior to updating Robot Alert.
Once the conversion process completes, read the After You Are Done section for additional information.
The Robot Alert conversion process 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've made any manual changes to the RBTUSER or RBTADMIN user profiles or their authorities, these changes will be lost with any product installation or conversion.
The Robot Alert conversion process downloads everything to your PC and transfers the objects to the IBM i. This process is described in the following section.
Download the Robot Alert installer (setupAlert.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 load. You can choose the Manuals and the Software for IBM i. Click Next.
If you’re only installing the manuals, the process completes and the installer closes. The manuals were installed at the following location, and you can skip the rest of these steps.
C:\Program Files (x86)\Help Systems\Robot ALERT 6\manuals
If you’re loading the Software for IBM i (with or without the manuals), continue to step 4.
On the IBM i Details panel:
Select or enter the IBM i where you want to convert Robot Alert.
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 converting Robot Alert 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.
You have two options on the Product Load Options panel:
Click Immediate Load if you’d like to load the product on the IBM i now.
Note: This ends Robot Alert and holds it until the product load completes. After you are done, we’ll release and 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 Alert launches. When the processing is complete, you have two choices:
If this is the only conversion of Robot Alert that you're doing, click Finish.
If you have conversions 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 conversion process, do the following to manually load them on the IBM i you identified above.
If you are loading Robot Alert into an IASP:
Run the following command to set the ASP group:
Execute the following command to verify that no users are signed on to the product you’re converting:
WRKOBJLCK OBJ(RBTALRLIB) OBJTYPE(*LIB)
Execute the following command to lock Robot Alert so it doesn’t become active during the conversion process:
Note: Be sure to unlock it after the conversion is complete.
Execute the following command to display the Work with Loads panel:
Enter option 1, Load, next to the Load Name for Robot Alert and press Enter.
After the conversion completes, execute the WRKSPLF command to check the spooled files for any errors that may have occurred. If you have any questions, contact Technical Support.
Remember to unlock Robot Alert by executing the following command when the conversion is complete:
RBTALRLIB/RBALOCK ACTION (*UNLOCK)
If you're using an internal modem, the conversion process deletes the line description that Robot Alert uses for the modem. You must recreate the line description after the conversion completes by entering the following command:
CRTLINASC LIND(RBALXX) RSRCNAME(XXXXXX) INTERFACE(*INTMODEM) CNN(*SWTPP) VRYWAIT(60) SWTCNN(*DIAL) AUTOANS(*NO) AUTODIAL(*YES) DIALCMD(*OTHER) INACTTMR(*NOMAX) TEXT('R/ALERTLINE') AUT(*ALL)
If the library RBTALRV5 was not deleted from your system, and you feel comfortable deleting it now, enter the following command:
Three libraries were restored to your system for use during the conversion process: HSLOADMGR, HSLOADMGRW, and RBTCDRLIB. We don't remove them from your system in case you're doing multiple conversions. 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 conversions. For more information, see “Using the HelpSystems Product Loader.”
Still have questions? We can help. Submit a case to Technical Support.