HelpSystems SEQUEL Software PowerTech Skybot Software ShowCase Bytware CCSS Intermapper Safestone AutoMate

Instructions for Converting Robot/SCHEDULE 9.0 to 10.0


Before You Begin

Read these instructions completely before starting your conversion.

Note: You do not need to change the Initial ASP Group parameter if you use the SETASPGRP command.

  • Robot/SCHEDULE 10 has a new graphical PC interface. See "Installing on a PC" at the end of these instructions.
  • Before converting Robot/SCHEDULE, you have the option of running a pre-conversion check to determine whether the conversion will complete successfully. To do so:
    1. Display the Maintain Help/Systems Products menu by entering the following command:


    2. Select option 5 and enter the following special code:


  • 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.
  • 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 have any network security products, be aware that the GUI version of Robot/SCHEDULE uses the following servers and exit points:
    Servers Exit Points

    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 do not 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 10. 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 in version 10. 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).


    • 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 R09M00 or higher before you can start the conversion. If the version currently on your system is below this level, call  Help/Systems Technical Support to help you convert to Robot/SCHEDULE version 9 so that you can convert to Robot/SCHEDULE 10.
  • If you use any of the following Help/Systems 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 version 10.
    • Robot System Library (RBTSYSLIB) R01M87 (dated 040116)
    • Robot/ALERT R05M38
    • Robot/AUTOTUNE R07M18
    • Robot/NETWORK Host R10M15, Node R10M14
    • Robot/REPORTS R07M27

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

  • If you use Robot/REPLAY, it must be at R03M06 or higher. You must convert Robot/SCHEDULE to version 10 before updating Robot/REPLAY.
  • The conversion process calls a Help/Systems program to create or change the two Help/Systems user profiles, RBTUSER and RBTADMIN. The RBTUSER and RBTADMIN 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 Help/Systems 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, these changes will be lost with any Help/Systems product installation or conversion.

Converting Robot/SCHEDULE

IMPORTANT: Do all of the following steps in the order listed. Skipping one or more steps could result in the conversion not completing properly.

  1. Sign on under a user profile that is 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. Make sure no users are signed on to the product you are converting.
  2. Enter the following command to end Robot/SCHEDULE and the RBTSLEEPER subsystem. Note: The command ends all Robot products.


    Note: This procedure will end the RBTSLEEPER subsystem, which makes all Help/Systems products inactive.

  3. Enter the following command to check for locks on ROBOTLIB:


    If locks exist, they must be removed before the conversion can continue.

  4. Enter the following command:


    This displays the Maintain Help/Systems Products menu.

  5. Select option 4 from the Maintain Help/Systems Products menu and enter the following conversion code:


    Note: The pre-conversion program runs as part of the conversion process.

  6. When the RBTINSTALL prompt panel displays, press Enter to start the conversion process.

After You Are Done

  • When the conversion completes, enter the WRKSPLF command to check the conversion spooled files and job log for errors. Call Help/Systems Technical Support at 952-933-0609 if you have any questions.
  • If you used Robot/SCHEDULE security in version 9.0, refer to the Help/FACTS, Robot/SCHEDULE 10 Secured Object Cross-Reference, when setting up security for the Robot/SCHEDULE 10 graphical interface. 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 10. If you have archived audit log journals and want to display them in version 10, restore the archived journals, then use the Convert R09 Audit Log Journal (RBTCVTJRN) command to convert them to Robot/SCHEDULE version 10 format.
  • The Display Audit Log (RBTDSPAUDL) command has changed in version 10. 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, 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 10 and the product has been running successfully, you can delete the following libraries:
  • You can access an online version of the Robot/SCHEDULE user documentation from the Help/Systems download page and Help/FACTS page.

Installing on a PC

Do the following to install the Robot/SCHEDULE 10 graphical interface on a PC.

  1. Download the Robot/SCHEDULE for Windows installer (setupschedule10.exe).
  2. Close all Windows applications before running the PC installation.
  3. Double-click the setupschedule10.exe file and follow the installation instructions that display.

Note: If you quit the installation process at any time during the installation, a partial install will have occurred. To resolve this, just start the installation process again. All existing files will be replaced and the product will be installed correctly on the PC.


Updated February 22, 2013