Before You Begin

Read these instructions completely before starting your conversion.

  • This document provides specific instructions on how to convert Robot Schedule using the HelpSystems Product Loader. For general information about the HelpSystems Product Loader, see “Using the HelpSystems Product Loader.”

  • Before loading Robot Schedule , we check if RBTSYSLIB needs to be updated. If it does, you’ll be asked to bring down the subsystem RBTSLEEPER. This ends all Robot products running on your system. When the update completes, the subsystem will restart automatically.

  • When you’re finished, read the After You Are Done section for additional information.

  • There cannot be any Robot Schedule jobs with a status of R (Running) or S (Submitted to Queue) during the conversion. The pre-conversion check program looks for these jobs and notifies you of any jobs in either status. You can either end the jobs or wait for them to complete.

  • Be sure to back up ROBOTLIB before beginning the conversion process. The library is updated during the conversion.

  • If you're on V7R1 and using Robot Schedule Enterprise, you must apply the IBM PTFs: SI52159, which was superseded by SI52733.

  • If you have any network security products, be aware that the GUI version of Robot Schedule uses the following servers and exit points:

    Servers Exit Points
    RMTCMD QIBM_QZRC_RMT
    SIGNON QIBM_QZSO_SIGNONSRV
    DATABASE QIBM_QZDA_SQL1 and QIBM_QZDA_SQL2
    FILE QIBM_QPWFS_FILE_SERV
    NETPRT QIBM_QNPS_ENTRY

    We recommend that all the exit points listed above be open to RBTUSER, RBTADMIN, and the user logging into 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.

  • If you mirror ROBOTLIB, make sure to turn off mirroring before starting the conversion.

  • If you journal any Robot Schedule files to your own libraries, you should remove the journals before starting the conversion.

  • If you don't purge Robot Schedule history on a regular basis, we recommend that you perform a purge prior to starting the conversion.

  • If you use Robot Schedule auditing, the conversion process calls a program to convert your audit log journal receivers from version 9 to version 12. The maximum number of journal receivers allowed is 500. If you have more than 500 journal receivers in the journal RBTJRN, you must save and delete them prior to running the conversion. The pre-conversion check program indicates how many journal receivers you have over the limit of 500.

  • During the conversion, any jobs with the same name will be changed to have a shared command set. Although shared command sets are visible from the green screen, you can modify them only through the GUI. See the Robot Schedule GUI User Guide for complete information on defining and using shared command sets.

  • Robot Schedule file structures have been changed since version 9. If you have queries or programs written over Robot Schedule files, they may no longer work. You should review your programs and queries, and recompile them as necessary.

  • If you referenced ASP Groups using the Job Description in a Robot Schedule 9 job, you must do one of the following after the conversion completes:

    • Set the Initial ASP Group parameter to *JOBD (instead of the default, *NONE).

      OR

    • Set the Initial ASP Group parameter to *RBTDFT and update the Initial ASP Group field to *JOBD in the appropriate environment.

  • Robot Schedule must be at R09M08 or higher before you can start the conversion. If the version currently on your system is below this level, contact Technical Support for help in converting to Robot Schedule R09M08, so that you can then convert to Robot Schedule 12.

  • If you use any of the following Robot products, they must be at the release/modification levels shown, or higher, for the conversion to complete properly, and for the other products to work properly with Robot Schedule 12.

    • Robot Schedule Enterprise R01M27

    • Robot Alert R05M38

    • Robot Autotune R07M18

    • Robot Network host R10M15, node R10M14

    • Robot Reports R07M27

    Note: To find the release/modification level of the Robot products on your system, enter the command RSLVER on a command line.

  • If you use Robot Replay, it must be at R03M18 or higher. If you're converting Robot Schedule at the same time you're updating Robot Replay, the order matters:

    • If Robot Replay is below R03M18, you must update Robot Replay before converting to Robot Schedule 12.

    • If Robot Replay is at R03M18 or higher, you must convert Robot Schedule to version 12 before updating Robot Replay.

  • The Robot Schedule conversion process creates or changes the 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 Robot product installation or conversion.

 

Robot Schedule Pre-Checker

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:

  1. Use the "Converting Robot Schedule" instructions to download everything to your PC.

  2. When you reach the Product Load Options panel, select Staged Load (step 5b below) and wait until the processing completes.

  3. On the IBM i, execute the following command to display the Work with Loads panel:

    HSLOADMGR/HSWRKLOAD

  4. Enter option 2, Run pre-checker, next to the Load Name for Robot Schedule and press Enter.

  5. Review the information on the Pre-check Robot Schedule panel. Select *UPGRADE for the conversion, then press Enter.

Note: A pre-checker automatically runs during the first part of the Robot Schedule conversion process, but we recommend you run it in advance to identify any potential problems before attempting a full conversion.

 

Converting Robot Schedule

The Robot Schedule conversion process downloads everything to your PC and transfers the objects to the IBM i. This process is described in the following section.

  1. Download the Robot Schedule installer (setupSchedule12.exe) from My Downloads page on our website. Double-click it to start it.

  2. On the Choose Components panel, select which components you want to load. You can choose the Software for Windows (the GUI and the Manuals) and the Software for the IBM i. Click Next.

  3. If you’re 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 12\manuals

    If you’re loading the Software for IBM i (with or without the Software for Windows), continue to step 4.

  4. On the IBM i Details panel:

    1. Select or enter the IBM i where you want to install Robot Schedule .

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

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

      • Enter the name of a destination ASP group if you want to change the ASP group to something other than the default group *SYSBAS.

    4. Click Next.

  5. You have two options on the Product Load Options panel:

    1. Click Immediate Load if you’d like to load the product on the IBM i now.

      Note: This ends Robot Schedule until the product load completes. After you are done, we’ll restart the product.

    2. Click Staged Load if you’d like to transfer the objects now and load them on the IBM i at a later time.

      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.

  6. The Product Load Progress panel for Robot Schedule launches. When the processing is complete, you have two choices:

    • If this is the only conversion of Robot Schedule 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.

 

Loading Staged Objects on the IBM i

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.

  1. Execute the following command to make sure no users are signed on to the product you're installing:

    WRKOBJLCK OBJ(ROBOTLIB) OBJTYPE(*LIB)

  2. Execute the following command to display the Work with Loads panel:

    HSLOADMGR/HSWRKLOAD

  3. Enter option 1, Load, next to the Load Name for Robot Schedule and press Enter.

 

After You Are Done

  • After the conversion completes, enter the WRKSPLF command to check the spooled files for any errors that may have occurred. If you have any questions, call Technical Support.

  • You can access the Robot Schedule User Guide and other documentation on our website.

  • If you used Robot Schedule security in version 9, refer to "Robot Schedule Secured Objects Cross-Reference" on our website when setting up security for the Robot Schedule graphical user interface (Robot Schedule Explorer). This document helps ensure you have the proper authority in place for objects in the new interface.

  • The conversion process automatically converts audit log journals from version 9 to version 12. If you have archived audit log journals and want to display them in version 12, restore the archived journals, then use the Convert R09 Audit Log Journal command (RBTCVTJRN) to convert them to Robot Schedule 12 format.

  • The Display Audit Log command (RBTDSPAUDL) has changed since version 9. If you have Robot Schedule jobs or CL programs that use the command, you should check the command for the following parameters:

    • A new parameter, Print Field Legend, was added. Use this parameter to print the field legend used in the audit log.

    • The *OUTLIB value was removed from the Output parameter. In version 10 and higher, audit log data is stored in a physical file instead of a journal receiver (as in previous versions). You can display the audit log or create a spooled file.

  • After you convert to Robot Schedule 12 and the product has been running successfully, you can delete the following libraries:

    • ROBOTLIBV9

    • ROBOTMRGV9

    • ROBOTV9JRN

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

Last Modified On: February 13, 2019