These instructions contain the rules for installing a Robot product in an independent auxiliary storage pool (independent ASP or IASP) environment.

Notes on Installing Robot Schedule in an IASP (R12M04 and higher)

Note: Robot Replay, Robot Schedule Enterprise, Robot Schedule EnterpriseOne, and Robot Schedule Interface to SAP will not interface with Robot Schedule in an iASP.

Robot Schedule can now be installed into *SYSBAS and in an IASP. When installing into an IASP, you must have an IASP-enabled license.

When installing into an IASP, you can choose the Robot Schedule product and merge library names instead of using the default names (ROBOTLIB and RBTMRGLIB).

If you wish to run an instance of Robot Schedule with Robot Network or Robot Schedule Enterprise, Robot Schedule must be installed into *SYSBAS, using library ROBOTLIB.

In order to facilitate multiple instances of Robot Schedule, there’s a new Help Systems exit point: HELPSYS_FYI_ADEX. An install, update, or conversion of Robot Schedule registers the instance with the new exit point.

  • If you restore a copy of Robot Schedule manually, use the RBTREGAPP command to register the instance after it’s restored.

  • In addition to registering with the HELPSYS_FYI_ADEX exit point, the RBTREGAPP command does the following:

    • Changes all the source (data) library references in our files to the library name you’re registering. Note: If you use the Robot Schedule library name in your object types, you need to manually change those references.

    • Updates the PRDLIB on all Robot Schedule commands that don’t use PRDLIB(*NONE).

    • Updates product library references in job descriptions.

    • Sets up database triggers, stored procedures, and functions.

    • Sets up command analyzer and work management exit points.

    • Sets up the RBTSLEEPER autostart feature.

  • If you installed Robot Schedule into an IASP, make sure you have your ASP group set by using *JOBD INLASPGRP or by using the SETASPGRP command. If switching between IASP and *SYSBAS, use SETASPGRP ASPGROUP(*NONE) before working with an instance in *SYSBAS.

  • You can use RSLVER, or RBO followed by pressing F10, to view the installed products. Depending on how your ASP group is set, you might see multiple instances of a product.

  • If you have multiple instances of Robot Schedule installed and your ASP group is set, press F11 to toggle through the screens to see the instance name, the release of the product, or the installed library name. To change the instance description, enter option 2 next to the Robot Schedule instance you wish to change.

To connect to the graphical user interface (GUI), you have multiple choices.

  • If the user-specified JOBD uses INLASPGRP(*NONE), and you wish to connect to a Robot Schedule instance in library ROBOTLIB in *SYSBAS, you can connect using the GUI without any changes.

  • If the user-specified JOBD uses INLASPGRP(*NONE), and you wish to connect to an instance of Robot Schedule in an IASP, click the Advanced button on the Connections Properties window in the GUI to specify the ASP group of the instance you want to connect to.

  • If the user-specified JOBD uses INLASPGRP(asp_group_name) to connect to an instance of Robot Schedule in an IASP, you can connect using the GUI without any changes.

From the IBM i, the JOBD determines which version of Robot Schedule you see when you issue the RBO command. If your JOBD specifies *NONE and you want to work in an instance of Robot Schedule in an ASP group, simply use the IBM command to set your ASP group SETASPGRP(asp_group_name) and execute the RBO command.

If you wish to move your currently installed *SYSBAS ROBOTLIB to an IASP, see “Moving Robot Schedule 12 to a Different System (Non-Standard Installation).”

Notes on Installing Other Versions of Robot Schedule in an IASP

In Robot Schedule 10, 11, and 12 (up to R12M03), IASPs can be controlled by a job, job environment, or job description.

Notes on Installing Robot Console in an IASP

Robot Console may now be installed into *SYSBAS and in an IASP. Our recommendation is to install Robot Console into *SYSBAS since its function is to monitor system message queues and monitor system logs. However, if you wish to install an instance of Robot Console on your IASP to monitor third party applications on the IASP, you can install directly into an IASP. To do so, you will be required to have an IASP enabled license.

We recommend that you place the *DEFAULT named libraries in the *SYSBAS instance. Currently, Robot Network will only work with *DEFAULT named libraries in *SYSBAS.

To connect to the graphical user interface (GUI), you have two choices. If the user connecting has a JOBD that set INLASPGRP and is in the *DEFAULT location, the user can connect using the GUI without any changes. If the library name is a custom name, or the user-specified JOBD uses INLASPGRP(*NONE), click the Advanced button on the Connections Properties window to specify the ASP Group and the Product Library name.

From the IBM i, the JOBD determines which version of Robot Console you see when you execute the RBO command. If your JOBD specifies *NONE, simply use the IBM command to set your ASP Group SETASPGRP(asp_group name) and execute the RBO command.

If you wish to move your current installed *SYSBAS RBTCONLIB to an IASP, see “Moving Robot Console to a Different System (Non-Standard Installations).”

 


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: March 08, 2018