Multilevel automation (MLA) processing

Up to 10 different actions can be taken or actions can occur until no more actions are defined.

For more information, see the following sections:

To use MLA

1. Specify MLA=Y on the AUTOPOOL, AUTOVOL, or AUTOAPPL console request.

   MLA=Y sets AUTOLEV to 1, indicating the first step in the MLA request. On completion of each submitted job, AUTOLEV is incremented and the request is redriven for the resource or resources.

2. Filter on the AUTOLEV value to control the actions that are taken at each level.

   You can filter on the AUTOLEV value in the RLST statements for the solution or by specifying AUTOLEV in the event message text and specify AUTOLEV in MainView AutoOPERATOR Rules.

3. Ensure that the last action of each step, or automation level, is a solution that uses the ACT_JOB keyword.

   The initial automation request is redriven only when a job that is submitted through the ACT_JOB keyword is completed. The request is not redriven when a solution results in an event being issued. Events can be issued in an MLA solution; however, a MainView AutoOPERATOR Rule should be set up to fire on that event and issue another request on the resource to continue automation processing. For more information, see Automation level.

4. Enable an additional MainView AutoOPERATOR Rule to notify automation processing when a submitted job ends.

   Whenever the ACT_JOB keyword is used, the MainView AutoOPERATOR Rules in Rule Set RULSRS01 must be enabled. For an example, see the following figure.

   AUTOPOOL multilevel automation example

   

Automation level

The automation level indicates the level, or step, in the action sequence that is being performed on the resource. With the initial MLA=Y request, the automation level is set to 1. The MLA indicator (as seen on the AUTO view for the resource) is set to Y, and the Repeat Function and Repeat Solution (as seen in the AUTO view) are set to the current request. As each action is completed, the automation level is incremented and the initial AUTO request, in Repeat Function and Repeat Solution, is redriven for the resource. The automation level value is available in AUTO functions RLST INC/EXC statements and can also be included in event message text for filtering in MainView AutoOPERATOR Rules. The automation level is used to control the actions that are taken at each level.

MLA termination

MLA processing is stopped when an event is generated or when the RLST condition filters are no longer met as described in the following:

• When an event is generated, the automation level remains at the level that caused the event to be generated, the MLA indicator remains set to Y, and the repeated function and solution (as seen on the AUTO view) remain for the request. If another request that does not specify the MLA parameter is received for the resource, it is considered in the same automation level. If another request that specifies MLA=N is received, the automation level is set back to zero, MLA is set to N, and the repeat function and solution values are cleared, as can be seen in the AUTO view. In the Pool Space Management Automation solution, MLA processing stops when the event is issued at AUTOLEV4. As there are no MainView AutoOPERATOR Rules to fire on AUTOLEV4 no other actions are initiated for the resource.

• When the RLST condition filters are no longer met, the automation level is set to 0, MLA is set to N, and the repeat function and solution are cleared (as can be seen in the AUTO view).

MLA parameter specifications

• MLA=Y starts MLA processing. The AUTO function and solution that are requested on the AUTO command was redriven at the end of each action, until one of the conditions that are described in Automation level is encountered.

• MLA=N ensures that multilevel automation does not take place for a request. This specification can be used to set the AUTOLEV to AUTOLEV0 and clear the Repeat Function and Repeat Solution values as seen on the AUTO view in situations where an MLA request did not run through the condition being resolved.

• If an MLA parameter is not specified, the request runs with the current MLA attributes of the resource. This can be used when issuing an event from an MLA solution that fires a MainView AutoOPERATOR Rule to issue another AUTO request on the resource. This subsequent AUTO request should not specify the MLA parameter, because this request will be part of the current MLA automation level for the resource. In the AUTOPOOL multilevel automation example, event AP092 causes MainView AutoOPERATOR Rule SRS03002 to fire, which issues the AUTODS DELUNCAT solution on the pool. This AUTODS command does not specify MLA, and, therefore, runs as part of the current automation level for the resource. In the example, this process is done on the first automation level for the resource. When the job that was submitted by the AUTODS DELUNCAT solution ends, the automation level is incremented and the Repeat Function and Repeat Solution values are redriven (in this case, the AUTOPOOL function) with solution 90TO85.