Recommendations for Running Help/Systems Products in an IASP Environment

These instructions explain the rules for installing a Help/Systems product in an Independent Auxiliary Storage Pool (IASP) environment. Help/Systems products cannot be installed in an IASP outside of the *SYSBASE pool.

Notes on Installing Robot/SCHEDULE V9 in an IASP

Note: In Robot/SCHEDULE Version 10, IASPs can be controlled by a job, environment, or job description

System Base Pool (*SYSBASE) Installation

ROBOTLIB typically is installed in ASP 01 of the *SYSBASE pool. Therefore, it cannot be installed in an IASP as ROBOTLIB. When ROBOTLIB is in the *SYSBASE pool, all jobs submitted by Robot/SCHEDULE have access to ROBOTLIB because it resides in *SYSBASE.

For user jobs submitted by Robot/SCHEDULE to access user objects in an IASP, the jobs must be submitted with the correct ASP group. Or, the user must add the SETASPGRP command to the job’s command list.

Accessing User Objects

Users objects referenced by Robot/SCHEDULE should be in *SYSBASE or in an ASP group used by the user’s submitted job. In addition, users who access Robot/SCHEDULE through menus or commands must use the correct ASP group.

Submitting Jobs

When submitting jobs, keep the following in mind:

• The INLASPGRP parameter on the SBMJOB command defaults to *CURRENT. Therefore, all jobs submitted by Robot/SCHEDULE use the ASP group of the job that does the submitting.
• When the Robot/SCHEDULE monitor job starts, it starts with the current ASP group of the user’s job.
• When the Robot/SCHEDULE monitor job submits a user job, it is submitted with the current ASP from the monitor job.
• If a user enters a DO override code on a job in Robot/SCHEDULE, the job is submitted with the current ASP of the user’s job.

Using OPAL

When using OPerator Assistance Language (OPAL), keep the following in mind:

• When the Robot/SCHEDULE monitor job submits a job with Before OPAL, the OPAL is executed by the monitor job, using the monitor job’s current ASP group.
• When a user executes a DO Special override code with OPAL for a job with Before OPAL, the OPAL is executed by the user’s job and uses the current ASP group of the user’s job.
• When a job is submitted with After OPAL, the OPAL is executed by the submitted job with the current ASP group of the submitted job.
• OPAL can check the status of an IASP device with the DEVSTS variable and AVAILABLE, which is implemented in OPAL.

Notes on Installing Robot/CONSOLE in an IASP

System Base Pool (*SYSBASE) Installation

RBTCONLIB typically is installed in ASP 01 of the *SYSBASE pool. Robot/CONSOLE monitors message queues in *SYSBASE or the current ASP group; it does not monitor multiple ASP groups. You must modify the job description RBTCONLIB/RBCJOBD to include the ASP group name. Robot/CONSOLE cannot be installed in an IASP as RBTCONLIB.

When Robot/CONSOLE is installed in *SYSBASE, all OPAL runs in the same ASP group as the monitor job. For OPAL to access user objects in an IASP, the OPAL program must specify the ASP group using the SETASPGRP command. Ensure that you are getting the messages from *SYSBASE or the ASP group associated with job.

Notes on Installing Robot/NETWORK in an IASP

System Base Pool (*SYSBASE) Installation

RBTNETLIB and RBTNETNODE should be installed in ASP 01 of the *SYSBASE pool.

Updated Oct. 29, 2009