Authorizing EXECs scheduled by an operator or the Rule Processor

EXECs can be scheduled from one BBI-SS PAS to another BBI-SS PAS in the following ways:
  • using the MVS MODIFY command, a terminal operator on one BBI-SS PAS can schedule an EXEC on another BBI-SS PAS

  • a Rule responding to an event can schedule an EXEC that schedules to run an EXEC on a different BBI-SS PAS

In both cases, the BBI-SS PAS where the EXEC is scheduled to run must be authorized by a BBPARM member. The BBPARM member name is the subsystem ID (SSID) of the BBI-SS PAS that sent the EXEC.

For example, if a terminal operator on BBI-SS PAS SS01 issues this command:

F SS01,%execname

and EXEC named %execname starts an EXEC on a BBI-SS PAS named SS02, the SS02 BBI-SS PAS must have a BBPARM member SS01.

Also, if the EXEC %execname issues an EXEC from SS02 to be scheduled on SS01, SS01 must have a BBPARM member SS02. This is because MainView AutoOPERATOR sends the ORIGIN of each step in an EXEC to the receiving BBI-SS PAS to verify authorization.

If the required BBPARM authorization member does not exist, MainView AutoOPERATOR issues error message AM3119W and does not schedule the EXEC.

Was this page helpful? Yes No Submitting... Thank you