Distributed DFSMShsm solutions for MainView AutoOPERATOR
The following solutions are provided for MainView AutoOPERATOR:
DFSMShsm automation events are generated by MainView AutoOPERATOR Rules.
A Rule is a two-part conditional statement. When the conditions that are specified in the first part of the statement are met, the actions in the second part of the statement are performed. Some Rules use variables and some Rules are time-initiated. Rules are organized in the MainView AutoOPERATOR Rules Processor. RULSRS is the MainView AutoOPERATOR Rule Set for predefined MainView SRM Automation solutions.
The following table lists the predefined storage events. You can modify Rules by using the MainView AutoOPERATOR Rules Processor. For more information, see the MainView AutoOPERATOR Basic Automation Guide.
Predefined storage events
Event to modify | MainView AutoOPERATOR PARMLIB member to edit |
---|---|
Initialization solution | SRSVARG |
HSM Held Resource solution | SRSVARH |
HSM Waiting solution | SRSVARW |
HSM Duplicate Request solution | SRSVARD |
HSM Commands and Replies solution | None |
HSM Alert solution | None |
HSM Message Suppression solution | None |
ADSM Hung Session solution | SRSVARA |
Note
MainView AutoOPERATOR PARMLIB member SRSVARG is a prerequisite for all of the solutions.
If you modify parameters in a MainView AutoOPERATOR PARMLIB member, you can restore variable values by using the following MainView AutoOPERATOR console command:
F AOAS,%SRSVAR parmlibMember,parmlibMember...
The parmlibMember variables represent the names of one or more PARMLIB members that contain the changed values.
Initialization solution
The Initialization solution is used to initialize variables for the following solutions:
- HSM Held Resource
- HSM Waiting
- HSM Duplicate Request
- ADSM Hung Session
The following table presents the elements that this solution uses.
Initialization solution elements
Solution element | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Prerequisites | Initialization solution | ||||||||
Invocation | The Initialization solution is invoked when MVS issues the following message:
The Rule that invokes this solution runs an EXEC (SRSVAR) that reads PARMLIB members and sets the solution variables in the members. | ||||||||
Rules | SRSVAR Traps BBI startup message PM0010I and calls the SRSVAR EXEC. This Rule is distributed as enabled in Rule Set RULSRS. | ||||||||
EXECs | SRSVAR reads PARMLIB members and sets variables; any parameters that are passed are appended with the characters VAR to complete the name of the member to be read. | ||||||||
Parameters | The PARMLIB member for this solution is SRSVARG. The parameters in SRSVARG apply to multiple solutions.
|
HSM Held Resource solution
The HSM Held Resource solution checks for held resources and for the largest free areas above and below the line.
When an automated action is held, an event will be generated and displayed in the MainView AutoOPERATOR Active Alerts display.
The following table presents the elements that this solution uses.
HSM Held Resource solution elements
Solution element | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Prerequisites | Initialization solution | ||||||||||
Invocation | This solution is invoked by a time-initiated Rule. It can also be invoked manually by issuing the following MainView AutoOPERATOR console command:
| ||||||||||
Rules | HSMHELD is a time-initiated Rule that executes every hour at one minute past the hour. Note: You can change the interval by using the MainView AutoOPERATOR Rules. This Rule is distributed as enabled in Rule Set RULSRS. | ||||||||||
EXECs | The HSM Held Resource solution uses the following EXECs:
| ||||||||||
Parameters | The PARMLIB member for this solution is SRSVARH. The parameters are read by the Initialization solution and saved as shared variables.
|
HSM Waiting solution
The HSM Waiting solution checks the number of waits on each resource and compares it to the parameters that you specify.
You can establish warning thresholds for the following conditions:
- MIGRATE waits
- RECALL waits
- DELETE waits
- BACKUP waits
- RECOVER waits
- COMMAND waits
- ABACKUP waits
- ARECOVER waits
- TOTAL waits
If any of the values that you specify are exceeded, a warning condition is issued. If you specify 0 (zero) for any condition, a threshold warning is not issued.
The following table presents the elements that this solution uses.
HSM Waiting solution elements
Solution element | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Prerequisites | Initialization solution | ||||||||||||||||||||||||
Invocation | This solution is invoked by a time-initiated Rule. It can also be invoked manually by issuing the following MainView AutoOPERATOR console command:
| ||||||||||||||||||||||||
Rules | HSMWAIT is a time-initiated Rule that executes every hour at one minute past the hour. Note: You can change the interval by using the MainView AutoOPERATOR Rules. This Rule is distributed as enabled in Rule Set RULSRS. | ||||||||||||||||||||||||
EXECs | HSMWAIT issues the HSM QUERY WAITING command and parses through the output, analyzing the number of waits for each resource and comparing it to the threshold that you specify for the resource. Each time that HSMWAIT finds a value over the threshold, HSMWAIT issues an alert. | ||||||||||||||||||||||||
Parameters | The parameters for this solution are in PARMLIB member SRSVARW. The parameters are read by the Initialization solution and saved as shared variables.
|
HSM Duplicate Request solution
The HSM Duplicate Request solution checks for duplicate requests. When a duplicate request is found, the duplicate request is canceled or an alert is issued, depending on what you specify.
This solution addresses only duplicate requests for data sets. It ignores all other resources that are reported in response to the QUERY REQUEST command.
The following table presents the elements that this solution uses.
HSM Duplicate Request solution elements
Solution component | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Prerequisites | Initialization solution | ||||||||
Invocation | This solution is invoked by a time-initiated Rule. It can also be invoked manually by issuing the following MainView AutoOPERATOR console command:
| ||||||||
Rules | HSMDUPR is a time-initiated Rule that executes every hour at one minute past the hour. Note: You can change the interval by using the MainView AutoOPERATOR Rules. This Rule is distributed as enabled in Rule Set RULSRS. | ||||||||
EXECs | HSMDUPR issues the HSM QUERY REQUEST command and parses through the output, comparing requests. Each time that HSMDUPR finds more than one request for the same data set, an alert is issued (in test mode), or the second request is canceled. | ||||||||
Parameters | The parameters for this solution are in PARMLIB member SRSVARD. The parameters are read by the Initialization solution and saved as shared variables.
|
HSM Commands and Replies solution
The HSM Commands and Replies solution traps write-to-operator-with-reply (WTOR) messages that are issued by DFSMShsm and automates replies in response to them.
The following table presents the elements that this solution uses.
HSM Commands and Replies solution elements
Solution component | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Prerequisites | Initialization solution | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Invocation | This solution is invoked when DFSMShsm issues the WTOR messages to be trapped. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Rules | The HSM Command and Replies solution uses the following Rules. Note: These Rules are distributed as disabled in Rule Set RULSRS and must be enabled to implement the solution.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
EXECs | No EXECs exist for this solution. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Parameters | No parameters exist for this solution. |
HSM Message Suppression solution
The HSM Message Suppression solution traps DFSMShsm messages and suppresses them.
The following table presents the elements that this solution uses.
HSM Message Suppression solution elements
Solution component | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Prerequisites | Initialization solution | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Invocation | This solution is invoked when DFSMShsm issues the messages to be trapped. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Rules | The HSM Message Suppression solution uses the following Rules. Note: These Rules are distributed as disabled in Rule Set RULSRS and must be enabled to implement the solution.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
EXECs | No EXECs exist for this solution. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Parameters | No parameters exist for this solution. |
HSM Alert solution
The HSM Alert solution traps messages that are issued by DFSMShsm and issues alerts in response to them.
The following table presents the elements that this solution uses.
HSM Alert solution elements
Solution component | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Prerequisites | Initialization solution | ||||||||||||||||||||||||||||||||||||||||||||||||||
Invocation | This solution is invoked when DFSMShsm issues the messages to be trapped. | ||||||||||||||||||||||||||||||||||||||||||||||||||
Rules | HSM Alert solution has the following Rules. Note: These Rules are distributed as disabled in Rule Set RULSRS and must be enabled to implement the solution.
| ||||||||||||||||||||||||||||||||||||||||||||||||||
EXECs | No EXECs exist for this solution. | ||||||||||||||||||||||||||||||||||||||||||||||||||
Parameters | No parameters exist for this solution. |
ADSM Hung Session solution
The ADSM Hung Session solution checks for outstanding ADSM sessions.
When the solution finds an outstanding session that is older than the user-specified threshold, the session is canceled, or an alert is issued.
The following table presents the elements that this solution uses.
ADSM Hung Session solution elements
Solution component | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Prerequisites | Initialization solution | ||||||||||
Invocation | This solution is invoked by a time-initiated Rule. It can also be invoked manually by issuing the following MainView AutoOPERATOR console command:
| ||||||||||
Rules | ADSMHUNG is a time-initiated Rule that executes every hour at four minutes past the hour. Note: You can change the interval by using the MainView AutoOPERATOR Rules. This Rule is distributed as enabled in Rule Set RULSRS. | ||||||||||
EXECs | ADSM Hung Session solution uses the following EXECs.
| ||||||||||
Parameters | The ADSM Hung Session solution parameters are in PARMLIB member SRSVARA. The parameters are read by the Initialization solution and saved as shared variables.
|
Comments
Log in or register to comment.