How MainView SRM AUTO functions work
Solutions can be initiated in response to almost any storage condition or by user request through the use of AUTO console commands.
Solutions are defined in FLST/RLST statements of the AUTO functions. These statements use INC/EXC statements to select the resources or elements on which to act, and then the statements use SET statement keywords to specify the actions to be taken on the selected elements. These actions can be used to perform one of the following actions:
Issue an event
Tailor skeleton JCL to include statements for each selected element
This JCL can be saved and manually reviewed, submitted, or scheduled to submit at a later time.
Skeleton tailoring can invoke any utility software. The skeleton tailoring facility can be used to drive:
Other vendor disk-management systems
Standard IBM utilities
Your site’s utilities
Skeleton tailoring can be used to:
Migrate selected data sets
Perform first-level space management
Defragment one or more volumes
Reorganize one or more data sets
Issue DFSMShsm commands
Perform any pool, volume, or data set function you can invoke in a batch job
Console commands can be issued:
Manually, to initiate solutions for ad hoc requests
Automatically, through MainView AutoOPERATOR Rules or any other mechanism that allows console commands (MainView Alarm Manager, MainView API within MainView AutoOPERATOR, MainView AutoOPERATOR REXX EXECs, and so on)
From an AUTOPOOL, AUTODS, AUTOVOL, or AUTOAPPL function solution
The command syntax is processed replacing any variables coded within it with values from the solution set of the function, and the command is issued.
For example, the solution of the AUTO function AUTOPOOL issues a SVOS command to initiate the AUTOVOL function against each of the volumes that are identified in the solution list of the AUTOPOOL function.
MainView SRM Automation solutions can be used in the following ways:
An AUTO command can be scheduled or manually entered, and the requested solution looks for certain conditions and then tailors JCL and submits a job to resolve the condition.
For example, an AUTODS DELDUMP solution examines data set names that are used for dump data sets on a test system and deletes any data sets that are more than five days old. This solution would be manually requested by way of an AUTO command when space is needed, or the solution would be scheduled to occur every certain number of days at a particular time. The solution detects the data sets, tailors JCL, and submits a job to delete the data sets.
Another MainView SRM function notes a condition and issues an event. The event is sent to MainView AutoOPERATOR (or another automation package), where a rule notes the event and issues an AUTO command to resolve the situation.
A multilevel tiered approach is used, where solutions run successively until a situation is resolved.
With the exception of the AUTOHMSG function, the AUTO commands are used to drive MainView SRM Automation solutions.