Controlling resource usage in BMC AMI Storage operator services
Because BMC AMI Storage uses IBM z/OS enclaves, you can use z/OS Workload Manager (WLM) to assign performance goals for selected work that the SVOS address space performs.
BMC AMI Storage enclaves start when the SVOS Started Task starts and stops when the Started Task stops. Therefore, only single-period velocity goals are appropriate.
Within the WLM definitions, you can create a new subsystem type of BMCS to assign service classes. The following table lists WLM process names that you can use to further delineate goals for various work that is performed in the SVOS Started Task. If no WLM definitions exist for the BMCS subsystem type, all work is assigned to the default service class (usually SYSSTC) for Started Tasks.
Important
Assigning an SVOS enclave to a discretionary goal or at a very low priority can cause the product to take longer when shutting down.
Process-name definitions in WLM
Process name | Description |
---|---|
SCAN | Controls the goals for VTOC Scan (VSCAN), Tape Scan (TSCAN), MCDS Scan (MSCAN), Catalog Scan (CSCAN), and BCDS Scan (BSCAN) processes Note: The VTOC Scan process underlies all policy collection intervals. For pool policy collection intervals, any logging of data to the space collector database or automation performed on the collected data occurs outside of any enclave. |
SPACECOL | Controls the goals for the SPSUM, DAILYSUM, and APPLMON commands The actual logging of the data to the space collector database or automation performed on the collected data occurs outside of any enclave. |
VIEWS | Controls the goals for all BBI3 view processing All work that is associated with views, either from MVI or MVE displays, is performed under this enclave, with the following exceptions:
|
Important
Use uppercase letters when defining process names in WLM.
To create the subsystem type
Comments
Log in or register to comment.