Terms
Review the following terms to familiarize yourself with basic terminology for event identification and the automation process:
Term | Definition |
---|---|
AUTO commands | Console commands that are used to initiate automation: AUTOAPPL, AUTODS, AUTOPOOL, and AUTOVOL |
AUTO functions | Functions that are used to define and activate storage automation: AUTOAPPL, AUTODS, AUTOPOOL, AUTOVOL, and AUTOHMSG |
Event | A user-defined message that is sent by MainView SRM Automation to one or more user-specified destinations. User-defined storage occurrences can cause events to be sent to one of the following destinations, where actions can be initiated in response to the storage condition:
|
FLST/RLST | FLST refers to SMFLST xx parameters that control selection of resources for a function. RLST refers to SMRLST xx parameters that can further filter resources and define the actions to be taken when the filter criteria is met. |
MainView AutoOPERATOR | MainView automated-operations product that automates routine operator tasks. MainView AutoOPERATOR can be used in conjunction with MainView SRM Automation to perform powerful automation in response to storage problems. |
Multilevel Automation (MLA) | In MainView SRM Automation, user-defined multi-step process that implements solutions in a tiered approach, where solutions are invoked sequentially until the condition is resolved. |
Pool | Either an SMS storage group, a pool that is defined by MainView SRM, or an SMS pool that is defined by MainView SRM |
SET result group | Group of records that matched the same AUTO function FLST/RLST SET statement. The AUTO function FLST/RLST is processed differently than most other MainView SRM Automation functions. For AUTO functions that are associated with AUTO commands, the filter and rule lists create a group of records according to the INC/EXC statements of the SET. The SET statement keywords then determine how to process the group of records called the SET result group. This allows sorting of the result group and actions implemented in sort order. |
Skeleton tailoring | Facility that allows skeleton JCL to be used during job submission. Skeleton JCL can contain variables within the JCL statements. At job submission time, these variables are substituted with data values. Directive statements can be used in the skeleton JCL to cause the repetition of a set of skeleton statements. This facility is similar to the TSO skeleton tailoring facility. |
Solution | A SET statement within an AUTO function RLST member that defines conditions or thresholds and defines actions to take when the conditions or thresholds are detected. Solutions can be requested through the AUTO console commands or, in the case of the AUTOHMSG function, in response to DFSMShsm messages. A solution either submits a job to manipulate resources or generates events that can analyze the condition, notify someone of the condition, or initiate actions within an automated-operations package. |